WO2011030386A1 - Système d'impression et procédé d'impression - Google Patents

Système d'impression et procédé d'impression Download PDF

Info

Publication number
WO2011030386A1
WO2011030386A1 PCT/JP2009/004537 JP2009004537W WO2011030386A1 WO 2011030386 A1 WO2011030386 A1 WO 2011030386A1 JP 2009004537 W JP2009004537 W JP 2009004537W WO 2011030386 A1 WO2011030386 A1 WO 2011030386A1
Authority
WO
WIPO (PCT)
Prior art keywords
print
image
user
ticket
application
Prior art date
Application number
PCT/JP2009/004537
Other languages
English (en)
Japanese (ja)
Inventor
清水知幸
Original Assignee
株式会社アイ・シー・ティー
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 株式会社アイ・シー・ティー filed Critical 株式会社アイ・シー・ティー
Priority to PCT/JP2009/004537 priority Critical patent/WO2011030386A1/fr
Publication of WO2011030386A1 publication Critical patent/WO2011030386A1/fr

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce

Definitions

  • the present invention relates to a printing system and a printing method using variable printing.
  • variable printing has been used in which information that is commonly printed on a plurality of printed materials and information that can be changed according to the printed materials are combined. This variable printing is often used for printed materials such as direct mails and bills that are produced for the purpose of distribution to individuals.
  • Personal insurance system is known as a related technology.
  • a plurality of insurance policies are selected by the customer terminal, the insurance server receives the insurance application data transmitted from the customer terminal, and transmits the received plurality of insurance application data to the printing terminal. Further, the printing terminal prints the transmitted insurance application data as a single policy and security.
  • a variable system is also known in which electronic data is generated by substituting data retrieved from a database into a variable part of a form stored in a repository, and transmitted to a printer together with a print instruction.
  • the present invention provides a system and method for easily printing a printed matter including an image according to the preference and needs of each user.
  • a printing system is a printing system that is operated by a business operator that delivers a printed material to a user, and is applied to the application information acquisition unit that acquires the application information designated by the user, and is printed on the printed material.
  • Data creation means for generating print character information based on the application information; and a print target image to be printed on the printed material is selected based on the application information, and the print target image and the print character information are arranged.
  • a print image generation unit that generates the print data, and a print unit that prints the print data.
  • FIG. 1 is a diagram illustrating an example of a printing system according to a first embodiment. It is a figure which shows an example of an application screen. It is a figure which shows an example of a charge table. It is a figure which shows an example of a form ID table. It is a figure which shows the example of application data. It is a flowchart explaining an example of operation
  • FIG. 10 is a flowchart for explaining an example of the operation of the print image data generation apparatus according to the second embodiment. It is a figure which shows an example of the printing system which concerns on 3rd Embodiment. It is a figure which shows an example of an application history database. It is a figure which shows an example of user information data. 6 is a flowchart illustrating an example of an operation of the print image data generation apparatus. It is a figure which shows an example of hardware constitutions, such as an image design selection apparatus.
  • FIG. 1 is a diagram illustrating an example of a printing system according to the first embodiment.
  • the printing system includes an image design selection device 2, a print image data generation device 4, and a printer 6.
  • the system shown in FIG. 1 is an example, and the image design selection device 2, the print image data generation device 4, and the printer 6 can be combined into one device according to the implementation. Further, two of the image design selection device 2, the print image data generation device 4, and the printer 6 can be integrated into one device.
  • the user 1 inputs ticket application information to the image design selection device 2.
  • the ticket application information includes, for example, information for selecting an image to be printed on the ticket (image to be printed) and information indicating the number of tickets purchased.
  • the image design selection device 2 generates application data 3 based on the input information.
  • the application data 3 includes data determined based on the application information such as a ticket price.
  • the print image data generation device 4 receives the application data 3 from the image design selection device 2, the print image data generation device 4 generates data indicating the image of the ticket to be printed (print image data 5).
  • the print image data 5 indicates an image in which a print target image and character information are arranged along a print form used for ticket printing.
  • the printer 6 prints the print image data 5 to generate a ticket.
  • the application data 3 received by the print image data generation device 4 includes information specifying the print target image selected by the user 1
  • the generated print image data 5 includes the user 1.
  • the specified print target image is included. Accordingly, the business operator can print a ticket including an image in accordance with the preference and needs of each user 1 without conducting a survey of the preferences and needs of the user 1.
  • the image design selection device 2 includes an application information acquisition unit 21, a storage unit 22, and an application data creation unit 23.
  • the application information acquisition unit 21 displays an application screen and acquires application information input from the user 1.
  • FIG. 2 is a diagram illustrating an example of an application screen.
  • the application information acquisition unit 21 specifies the user 1 and sends the ticket, such as the charge type of each ticket, the information specifying the image to be printed, the user's 1 name, phone number, e-mail address, address, etc., on the application screen.
  • the user 1 is requested to input data used for the process.
  • the application information acquisition unit 21 can also request input such as the number of purchased tickets and the membership number of the user 1.
  • the application information acquisition unit 21 displays a list of selectable images when the user 1 selects an image to be printed on the ticket.
  • the application information acquisition unit 21 displays a list of selectable images and waits for the user 1 to input.
  • the user 1 selects an image to be printed on the ticket from the images listed. For example, in the example of FIG. 2, when the user 1 selects “image E” on the list, the character string “image E” is displayed in the “ticket image” column.
  • the application information acquisition unit 21 acquires information input on the input screen as application information.
  • the information specifying the image to be printed can be, for example, the image ID of the image corresponding to the character string displayed in the “ticket image” field.
  • each ticket The image ID is acquired in association with.
  • the user 1 can directly access the image design selection device 2 and can also access via an arbitrary communication network such as the Internet.
  • the user 1 When the user 1 is directly accessing the image design selection device 2, the user 1 inputs a name, an address, and the like using a display device and an input / output device provided in the image design selection device 2.
  • the user 1 accesses the image design selection device 2 via the Internet or the like, the user 1 inputs data via a communication device such as a computer or a mobile phone, and the image design selection device 2 via the network. Get the data.
  • the input screen displayed by the application information acquisition unit 21 can include, for example, input of a name and an e-mail address in a plurality of places for confirmation of an input error, and is described in FIG.
  • the application screen can display a list including contents other than the character string, such as displaying thumbnails of selectable images as a list of selectable images. Further, the application screen can be changed so that a list of selectable images is not displayed and the user wants to input an image to be printed in the “ticket image” field.
  • the storage unit 22 stores information used for the operation of the application data creation unit 23.
  • the storage unit 22 can also store information preset by an operator or an operator, such as a fee table or a form ID table.
  • FIG. 3 is a diagram illustrating an example of a charge table. In the fee table, as illustrated in FIG. 3, the relationship between the ticket fee type and the ticket fee is recorded.
  • FIG. 4 is a diagram illustrating an example of the form ID table. In the form ID table, a correspondence relationship between a ticket identifier (ticket ID) and a print form identifier (form ID) used in the ticket is recorded.
  • the application data creation unit 23 recognizes a form ID indicating a print form to be applied to each ticket, using a ticket ID assigned to each ticket and a form ID table.
  • the ticket ID is an identifier assigned by the application information acquisition unit 21 to each ticket for which information on a charge type, an image, and the like is input.
  • the print form is a template applied to the print image data 5 and is stored in a database held by the print image data generation device 4 as described later.
  • the application data creation unit 23 generates the application data 3 using the application information acquired by the application information acquisition unit 21 and the information stored in the storage unit 22.
  • FIG. 5A and FIG. 5B are diagrams showing examples of the application data 3. First, an example of operations of the application information acquisition unit 21, the storage unit 22, and the application data creation unit 23 will be described with reference to FIG.
  • the user 1 accesses the application information acquisition unit 21 and applies for a ticket.
  • First ticket Price type General Image: A Second ticket Price type: General Image: B 3rd ticket Price type: kids Image: A 4th ticket Price type: Kids Image: E Number of tickets purchased 4 Membership number 123
  • the application information acquisition unit 21 assigns a ticket ID to each applied ticket, and acquires information specifying the charge type and image in association with the ID of each ticket.
  • the ticket ID is “1” for the first ticket, “2” for the second ticket, “3” for the third ticket, and “4” for the fourth ticket. To do.
  • the number of tickets and membership number are also acquired.
  • the application information acquisition unit 21 notifies the application data creation unit 23 of the acquired information and ticket ID.
  • the application data creation unit 23 records the data received from the application information acquisition unit 21 as application data 3.
  • the ticket ID, the image ID, the member number, and the charge type are recorded.
  • the application data creation unit 23 obtains the receipt number and records the obtained value as the application data 3.
  • the reception number can be obtained, for example, as the cumulative number of applied tickets.
  • the method of assigning the receipt number is arbitrary. For example, a different receipt number can be given for each ticket, and the same receipt number can be given to the ticket that the user 1 has applied for in one application. In the following description, an example will be described in which the same receipt number is given to the ticket that the user 1 applied for at one time.
  • the application data creation unit 23 refers to the form ID table and obtains a form ID for identifying a print form to be applied to each ticket.
  • the application data creation unit 23 transmits the application data 3 to the print image data generation device 4.
  • the application data creation unit 23 can also store the application data 3 in the storage unit 22 before transmitting the application data 3.
  • the application data 3 can be data including data corresponding to an application from one or a plurality of users 1.
  • the application data creation unit 23 outputs application data 3 corresponding to one application of the user 1 to the storage unit 22 in step (7).
  • the application data 3 for a certain number of people is stored in the storage unit 22, they are collected and transmitted to the print image data generation device 4 by the application data creation unit 23.
  • the image design selection device 2 can handle a plurality of types of tickets such as sports watching tickets and concert tickets.
  • the application information acquisition unit 21 stores a plurality of application screens
  • the storage unit 22 stores the types of application screens and the types of tickets to be handled (ticket types). Is stored.
  • application data 3 including the contents of applications made by three users 1 (1a to 1c) is shown. In this application data 3, it is assumed that the user 1a whose membership number is “123” applied for a ticket from the application screen corresponding to the ticket type “soccer_A”.
  • the application information acquisition part 21 calculates
  • the application data creation unit 23 records the ticket type in the application data 3 in step (3).
  • the application information acquisition unit 21 notifies the application data creation unit 23 that the ticket type is “soccer_B”, and the application data creation unit 23 adds the user 1c of the membership number “678” to the application data 3. Record the ticket type you applied for.
  • the application data 3 shown in FIG. 5B is created.
  • the ticket type can be obtained after recording the application information record of the user 1, the ticket price, the form ID of the form to be used, etc. in the application data 3.
  • the application data creation unit 23 inquires of the application information acquisition unit 21 about the ticket type after recording the application information and the like.
  • the procedure described above is an example, and for example, the procedures (3) to (6) can be interchanged.
  • the application data 3 shown in FIGS. 5A and 5B is an example, and the application data creation unit 23 creates application data 3 that is recorded together with other information according to the implementation. be able to.
  • FIG. 6 is a flowchart for explaining an example of the operation of the image design selection device 2.
  • the application information acquisition unit 21 acquires information for identifying the user 1, the charge type of the ticket desired by the user 1, the image ID designated by the user 1, the total number of tickets, member information, and the like (steps S1 to S5).
  • the application information acquisition unit 21 notifies the application data creation unit 23 of the acquired information in association with the ticket ID.
  • the application data creation unit 23 obtains an acceptance number (step S6).
  • the application data creation unit 23 refers to the charge table and the form ID table stored in the storage unit 22 and obtains the price of the applied ticket and the form ID used for printing the ticket (steps S7 and S8). .
  • the application data creation unit 23 requests the application information acquisition unit 21 for the ticket type, and records the notified ticket type in the application data 3 (step S9).
  • the application data creation unit 23 transmits the created application data 3 to the print image data generation device 4 (step S10).
  • the order of steps S1 to S5 can be changed, the order of steps S6 to S8 can be changed, and the like.
  • the print image data generation device 4 includes a reception unit 41, a print image data generation unit 42, a print form database 43, an image database 44, and a transmission unit 45.
  • the receiving unit 41 receives data transmitted to the print image data generating device 4 such as application data 3.
  • the receiving unit 41 outputs it to the print image data generating unit 42.
  • the application data 3 includes the data shown in FIG. 5A, the ticket destination desired by the user 1, and ticket purchase details.
  • the print image data generation unit 42 Upon receiving the application data 3, the print image data generation unit 42 refers to the print form database 43 and the image database 44 to generate the print image data 5.
  • the print form database 43 stores a ticket print form in association with the form ID.
  • images that can be designated as print targets are recorded in association with image IDs.
  • Fig. 7 shows an example of a print form.
  • the form 7a shown in FIG. 7A includes a destination 71, a greeting 72, a ticket purchase description 73, an image 74a, a charge type 75a, and an amount 76a.
  • the form 7b in FIG. 7B includes a caution item 77, an image 74b, a charge type 75b, and an amount 76b.
  • the image 74 (74a, 74b) is arranged with the image data acquired from the image database 44 by the print image data generation unit 42 based on the image ID recorded in the application data 3. Is done.
  • Data extracted from the application data 3 is arranged in the charge type 75 (75a, 75b) and the amount 76 (76a, 76b).
  • the print image data generation unit 42 also extracts and arranges the destination 71 desired by the user 1 and the ticket purchase details 73 of the user 1 from the application data 3.
  • the print form 7 includes the greeting 72, the notes 77, and the date and place where the game to be watched is played.
  • FIG. 8 is a flowchart for explaining an example of the operation of the print image data generation device 4. Operation when print image data 5 is generated using the data shown in FIG. 5A, the ticket destination desired by the user 1a, and the application data 3 in which the ticket purchase details are recorded with reference to FIG. Will be described.
  • the print image data generation unit 42 receives the application data 3 via the reception unit 41 (step S21).
  • the print image data generation unit 42 since the form A is designated as the form of the first ticket, the print image data generation unit 42 reads the print form 7 a from the print form database 43.
  • the print image data generation unit 42 extracts information to be arranged on the print form 7a from the application data 3, and arranges it at a predetermined position (steps S25 and S26).
  • the print image data generation unit 42 extracts these pieces of information from the application data 3.
  • a delivery destination 71 is provided with a desired ticket delivery destination designated by the user 1a, and a ticket purchase specification 73 is provided with a description representing the ticket purchase specification of the user 1a.
  • step S27 After processing for tickets with ticket IDs 3 and 4, it is determined in step S27 that there is no ticket for which print image data has not been created. Then, the print image data generation unit 42 outputs the print image data 5 to the printer 6 via the transmission unit 45 (step S28).
  • the printer 6 includes a printing unit 61 and prints the print image data 5 received from the print image data generation device 4.
  • a ticket with an image selected by each user 1 can be printed. Therefore, the user 1 can obtain a printed matter to which the image selected by the user 1 is attached, and can obtain a ticket including an image according to the preference and needs of the user 1. If the effect of this embodiment is seen from the provider side, the willingness to purchase of the user 1 can be enhanced by selling a ticket including an image that matches the preference and needs of the user 1. Furthermore, even if competitors sell tickets for the same game, the willingness to purchase tickets printed using this embodiment will increase, so it can be expected to increase the sales share to other sellers. .
  • the business operator can generate a ticket that prints an image that matches the user 1's preference and the like without investigating the user's 1 preference and needs in advance. The burden of investigating the user 1's preferences and the like is reduced. Further, for example, the business operator can print a ticket that suits the taste of the user 1 even if the operator does not hold a stock of paper for ticket printing on which a plurality of types of images are printed in advance.
  • FIG. 9 is a diagram illustrating an example of an application screen when a plurality of tickets are sold as a set.
  • the application information acquisition unit 21 can accept applications for up to three tickets, with three tickets as one set.
  • the application information acquisition unit 21 can also request data used for processing such as specifying the user 1 and sending a ticket, such as the name, telephone number, e-mail address, address, and membership number of the user 1.
  • a ticket such as the name, telephone number, e-mail address, address, and membership number of the user 1.
  • the user 1 accesses the application information acquisition unit 21 and applies for a ticket through an application screen on which a plurality of ticket sets can be applied.
  • the application information acquisition unit 21 assigns a ticket ID to each applied ticket, and acquires information specifying the charge type and image in association with the ID of each ticket.
  • the ticket ID attached to each ticket by the application information acquisition unit 21 is an ID that can identify which set number and number of tickets. For example, as shown below, the number of sets can be identified by the highest digit among four digits, and the number of tickets can be identified by the lowest digit.
  • the application information acquisition unit 21 notifies the application data creation unit 23 of the acquired information and the ticket ID, and the application data creation unit 23 records the received data as application data 3.
  • the application information acquisition unit 21 obtains and records the price and receipt number of each ticket using a fee table or the like.
  • the application data creation unit 23 refers to the form ID table and obtains a form ID for identifying a print form to be applied to each ticket.
  • FIG. 10 shows an example of a print form including a plurality of tickets.
  • the print form 8a (form a) includes a delivery address 81, a greeting 82, a ticket purchase description 83, an image 84 (84a to 84c), a fee type 85 (85a to 85c), and an amount 86 (86a to 86c).
  • the first ticket includes an image 84a, a fee type 85a, and an amount 86a
  • the second and third tickets also have an image 84, a fee type 85, and an amount 86, respectively. include.
  • the application data creation unit 23 determines the print form 8 using the form ID table shown in FIG.
  • the form ID table shown in FIG. 11 is held in the storage unit 22.
  • the print image data generating unit 42 Upon receiving the application data 3 via the receiving unit 41, the print image data generating unit 42 reads the print form 8 to be used. For example, the print form 8a is read for tickets with ticket IDs 1001 to 1003.
  • the print image data generation unit 42 reads the print form 8b with reference to the form ID table. Further, an image designated for each ticket is read and arranged as follows.
  • the print image data generation unit 42 arranges a character string indicating data read from the application data 3 for each ticket, and generates print image data.
  • FIG. 12 is a flowchart for explaining an example of the operation of the print image data generation device 4 according to the second embodiment.
  • FIG. 12 is a flowchart for an example in which three tickets are set as one set.
  • the print image data generation unit 42 reads the application data 3 and reads the print form 8 according to the designation of the application data 3 (steps S31 and S32).
  • the print image data generation unit 42 confirms whether or not an image ID is specified for the first ticket of the set being processed in the application data 3, and acquires the specified image (step S33). , S34). Similar operations are performed on the second and third tickets of the set to be processed (steps S35 to S38).
  • Step S39, 40 When the images designated by the first to third tickets are acquired, the respective images are arranged on the print form 8, and the data included in the application data 3 is also arranged on the print form 8 (step S39, 40). Steps S32 to S41 are repeated until there are no more ticket sets for which print image data 5 has not been created, and the created print image data 5 is output to the printer 6 (steps S41 and S42). If no image ID is specified in any ticket, an error message is output and the process ends (steps S33, S35, S37, and S43).
  • FIG. 13 shows an example of a printing system according to the third embodiment.
  • a text printed together with a ticket such as a greeting text or notes can be changed according to the user 1.
  • the print image data generation device 9 is used.
  • the image design selection device 2 and the printer 6 are the same as those used in the first and second embodiments. In the following description, a case where the greeting is changed according to the user 1 will be described.
  • the print image data generation device 9 includes a reception unit 91, a user information extraction unit 92, an application history database 93, a print image data generation unit 94, a print form database 95, an image database 96, a character information database 97, and a transmission unit 98.
  • the reception unit 91 receives the application data 3 from the image design selection device 2 and outputs it to the user information extraction unit 92.
  • the user information extraction unit 92 extracts information about the user 1 (user information) from the application data 3.
  • the user information can be data including one or more pieces of information that can be used to identify the user 1 such as the member number, name, telephone number, and address of the user 1.
  • the membership number of the user 1 is used as user information.
  • the user information extraction unit 92 searches the application history database 93 using the extracted user information.
  • FIG. 14 is a diagram showing an example of the application history database 93.
  • the application history database 93 records the member number of the member who applied for the ticket and the type of ticket applied by the member in association with each other.
  • the user information extraction unit 92 searches the application history database 93 using the membership number of the user 1 (1a to 1c) as a keyword, and obtains the number of times that the user 1 who applied for the ticket to be processed previously applied for the ticket. For example, the user information extraction unit 92 confirms from the application history database 93 shown in FIG. 14 that the member (user 1c) with the member number “678” has applied for the ticket six times.
  • the user information extraction unit 92 compares the number of times of application with the threshold used to determine the greeting, and determines the greeting used for the application from the user 1c with the member number “678”. Further, when the greeting is determined, the user information extraction unit 92 adds the corresponding greeting text ID to the application data 3 to generate the user information data 31.
  • FIG. 15 shows an example of the user information data 31. Note that the threshold used to determine the greeting is stored in advance in the application history database 93, and an arbitrary number of thresholds can be provided according to the type of greeting.
  • User information data 31 is output from the user information extraction unit 92 to the print image data generation unit 94.
  • the print image data generation unit 94 recognizes the form ID, image ID, and greeting text ID included in the user information data 31. Thereafter, a print form used for the ticket is acquired from the print form database 95 using the form ID, and an image to be printed is acquired from the image database 96 using the image ID.
  • the greeting text is recorded in the character information database 97. Therefore, the print image data generation unit 94 acquires a greeting text corresponding to the recognized greeting text ID from the character information database 97.
  • the print image data generation unit 94 generates the print image data 10 by arranging the acquired image and greeting on the acquired print form and acquiring and arranging other information from the user information data 31.
  • the generated print image data 10 is transmitted from the transmission unit 98 to the printer 6 and printed by the printing unit 61.
  • FIG. 16 is a flowchart illustrating an example of the operation of the print image data generation device 9.
  • An example of the operation of the print image data generation apparatus 9 that has received the application data 3 in FIG. 5B will be described with reference to FIG.
  • Steps S51 to S58 are operations of the user information extraction unit 92
  • steps S59 to S64 are operations of the print image data generation unit 94.
  • greetings shall be used properly as follows.
  • the user information extracting unit 92 receives the application data 3 via the receiving unit 91 and reads the application data 3 (step S51).
  • the user information extraction unit 92 acquires a membership number from the application data 3, and refers to the application history database 93 to determine the number of past applications of the user 1 (step S52). For example, when recognizing the application of the user 1a with the member number “123”, the user information extracting unit 92 checks the application history database 93 to check the past application status of the user 1a with the member number “123”. As shown in FIG. 14, the user 1a with the membership number “123” recognizes that the number of applications is 0 because the past application status is not recorded.
  • the user information extraction unit 92 compares the number of applications with Th 1 (step S53). Since the user 1a with the membership number “123” has not applied for in the past, the user information extraction unit 92 sets the greeting text ID to 1 and records it in the user information data 31 (step S56). Furthermore, the user information extraction part 92 confirms whether the user 1 which does not attach
  • the application data 3 includes data of the user 1 (1b, 1c) with the member numbers “345” and “678”, the number of past applications is also returned to step S52 for other members. Ask for. Since the user 1b whose membership number is “345” has applied for once, the number of applications is equal to or more than Th 1 but less than Th 2. Therefore, the user information extraction unit 92 has a greeting ID Is set to “2” and recorded in the user information data 31 (steps S53, S54, S57).
  • the user information extraction unit 92 confirms the past application count for the user 1c with the member number “678” (step S58, S52). Since the user 1c with the membership number “678” has applied for six times so far, the number of applications is Th 1 or more, and further Th 2 or more. Is set to “3” and recorded in the user information data 31 (steps S53 to S55).
  • the user information extraction unit 92 outputs the user information data 31 to the print image data generation unit 94 (step S58).
  • the print image data generation unit 94 reads the user information data 31, acquires the form ID and image ID, and acquires the corresponding print form and image from the print form database 95 and the image database 96 (steps S59 to S61).
  • the user information extraction unit 92 reads the greeting text ID from the user information data 31 and acquires the designated greeting text (step S62).
  • the user information extraction unit 92 creates the print image data 10 in which the acquired image, greeting, and user information are arranged on the acquired print form (steps S63 to S65).
  • the print image data generation unit 94 repeats the processes of steps S59 to S65 until the print image data 10 is created for all applications (steps S63 to S66). When the print image data 10 is generated for all applications, the print image data generation unit 94 outputs the print image data 10 (step S67). When the print image data 10 is received from the print image data generation unit 94, the transmission unit 98 transmits the print image data 10 to the printer 6, and the printing unit 61 prints the print image data 10 and issues a ticket.
  • the third embodiment it is expected that by changing the greeting for each user 1, it is possible to increase the favorability from the user 1 and to help increase the company's share with competitors.
  • the greeting is changed according to the user 1, but the advertisement of an event to be held in the future can be changed according to the user 1.
  • the user 1 who frequently applies for a ticket can be notified of the event schedule until one year later, and the user 1 who has purchased the ticket for the first time can be notified of the event schedule until six months later.
  • the user information extraction unit 92 refers to the application history database 93 and confirms the type of ticket applied and the number of applications for each ticket. Further, the user information extraction unit 92 holds a threshold for selecting a text such as a greeting or a promotion to be printed according to the type of each ticket, and compares the number of applications with the threshold for each type of ticket. In accordance with the comparison result, the user information extraction unit 92 determines the greeting text and the content of the advertisement to be printed, and records them in the user information data 31 shown in FIG.
  • FIG. 17 is a diagram illustrating an example of a hardware configuration of an image design selection device and the like.
  • the image design selection device 2, the print image data generation device 4, and the print image data generation device 9 can all have a hardware configuration as shown in FIG.
  • the CPU 101 of the image design selection device 2 includes an application information acquisition unit 21 and an application data creation unit 23.
  • the memory 102 includes a storage unit 22 and stores data such as a form ID table and a fee type table, a program executed by the CPU 101, and the like.
  • the input device 103 receives information from an administrator who performs setting of the printing system and the like with respect to the image design selection device 2.
  • the output device 104 is used, for example, when notifying an administrator of an error message.
  • the storage device 105 is a hard disk, for example, and stores a program executed by the CPU 101 and the like.
  • the storage device 105 can also record the content recorded in the memory 102.
  • the reading device 106 accesses the portable storage medium 107 in accordance with an instruction from the CPU 101.
  • the portable storage medium 107 includes, for example, a semiconductor device (such as a PC card) and a medium through which information is input / output by a magnetic action or an optical action.
  • the network connection device 108 transmits and receives data via the network according to instructions from the CPU 101.
  • the image design selection device 2 uses the network connection device 108 when receiving data from the input device used by the user 1 via the network, or when transmitting data to the print image data generation devices 4 and 9. .
  • the CPU 101 of the print image data generation device 4 includes a print image data generation unit 42.
  • the CPU 101 of the print image data generation device 9 includes a user information extraction unit 92 and a print image data generation unit 94.
  • the CPU 101 of each of the print image data generation apparatuses 4 and 9 uses the memory 102 to execute a program.
  • Databases such as the print form database 43, the image database 44, the application history database 93, the print form database 95, the image database 96, and the character information database 97 are recorded in the memory 102 and the storage device 105.
  • the input device 103 and the output device 104 provided in the print image data generation devices 4 and 9 are used for data input from an administrator of the print image data generation device, display of an error message, and the like.
  • the print image data generation devices 4 and 9 receive the application data 3 from the image design selection device 2 via the network connection device 108 and transmit the print image data 5 and 10 to the printer 6.
  • any of the first to third embodiments it is possible to generate a printed matter on which an image or the like selected by the user 1 is printed. Therefore, a printed matter that meets the preference and needs of the user 1 can be easily obtained. Can be printed. In addition, the business operator can enclose the user 1 by matching the printed image and the like with the preference and needs of the user 1.
  • the information to be changed according to the number of applications by the user 1 is not limited to greetings or advertisements, but may be an image printed on a ticket.
  • the image identification method and the information elements recorded in the user information data 31 are changed.
  • the image group includes one or more images that can be printed on the ticket.
  • the image group selection method can be the same as the image selection method described with reference to FIG. Therefore, in order to make it easy for the user 1 to select an image group, it is desirable that the user 1 can predict images included in the image group from data displayed in, for example, a list.
  • an identifier image group ID
  • the application data 3 is output to the print image data generation device 9, and the user information extraction unit 92 refers to the application history database 93 as described above and identifies the number of applications of the user 1.
  • the user information extraction unit 92 outputs data obtained by adding the number of applications to the application data 3 to the print image data generation unit 94.
  • the print image data generation unit 94 specifies an image to be printed on the ticket according to the image group ID and the number of applications.
  • the player name of the A group can be displayed on the list of image groups and can be selected by the user 1.
  • an image group ID for identifying the image group of “player a” is recorded in the application data 3.
  • the application data 3 is output to the print image data generation device 9, and the user information extraction unit 92 outputs information obtained by adding the number of applications of the user 1 to the application data 3 to the print image data generation unit 94.
  • an image a1 there are three types of images included in the image group of “player a”: an image a1, an image a2, and an image a3.
  • the number of applications and each image are preliminarily set in the print image data generation unit 94 as follows. Assume that they are associated. Note that n is a positive integer.
  • the print image data generation unit 94 recognizes information indicating the selected image group ID and the number of applications from the input data, determines which of the images a1 to a3 is to be printed on the ticket, and prints. Image data 10 is generated.
  • Such a modification can give variations to the image printed on the ticket within the range of the user 1's preference and needs, and can increase the user's 1 interest.
  • the business operator can increase the purchase intention of the user 1 for the ticket handled by the business operator.
  • the ID of the image used for the ticket purchased by the user 1 can be recorded in the application history database 93.
  • the user information extraction unit 92 can notify the print image data generation unit 94 of the image ID used for the ticket purchased by the user 1.
  • the print image data generation unit 94 searches the designated image group for an image that has been used less frequently and generates the print image data 10. You can also
  • the method in which the user 1 selects an image group and the print image data generation unit selects a print target image from the image group can be used in any of the first to third embodiments.
  • the print image data generation unit 42 selects a print target image from the image group by, for example, a method of selecting an image corresponding to the generated random number.
  • the application information acquisition unit 21 can also request the user 1 to input data specifying the type of ticket to be handled on the application screen.
  • the date and place where the game to be watched is held is included in the print form 7, but the application data creation unit 23 uses the data of the application information acquisition unit 21 as a basis. It is also possible to create character data to be printed. The created character data is recorded in the application data 3 and output from the image design selection device 2 to the print image data generation device 4. In this case, the storage unit 22 also stores information used by the application data creation unit 23 to create character data.
  • print forms shown in FIG. 7 and the like are merely examples, and different print forms can be used depending on the implementation.
  • a column for recording the name of the user 1 can be provided on the print form 7 or the print form 8, which can be used to suppress ticket purchase for resale purposes. That is, since a ticket displaying the name of the user 1 is generated, it is possible to make it difficult for the user 1 to resell the purchased ticket.
  • ticket printing is described as an example.
  • the printing system according to the first to third embodiments can be used for printing arbitrary printed matter.
  • the user 1 can select an image to be printed on a brochure of a material.

Abstract

L'invention porte sur un système et un procédé d'impression permettant d'imprimer facilement un matériau imprimé qui comprend une image adaptée aux préférences ou aux besoins de chaque utilisateur. Avec un système d'impression exploité par un vendeur qui transfère un matériau imprimé à un utilisateur, un moyen de collecte d'informations d'application collecte des informations d'application désignées par un utilisateur. Sur la base des informations d'application, un moyen de création de données crée des informations de caractères imprimés devant être imprimés sur le matériau imprimé. Un moyen de création d'image d'impression sélectionne une image devant être imprimée sur le matériau imprimé sur la base des informations d'application et crée des données d'impression dans lesquelles sont agencées l'image devant être imprimée et les informations de caractères imprimés. Un moyen d'impression imprime les données d'impression.
PCT/JP2009/004537 2009-09-11 2009-09-11 Système d'impression et procédé d'impression WO2011030386A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/JP2009/004537 WO2011030386A1 (fr) 2009-09-11 2009-09-11 Système d'impression et procédé d'impression

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2009/004537 WO2011030386A1 (fr) 2009-09-11 2009-09-11 Système d'impression et procédé d'impression

Publications (1)

Publication Number Publication Date
WO2011030386A1 true WO2011030386A1 (fr) 2011-03-17

Family

ID=43732074

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2009/004537 WO2011030386A1 (fr) 2009-09-11 2009-09-11 Système d'impression et procédé d'impression

Country Status (1)

Country Link
WO (1) WO2011030386A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2014048784A (ja) * 2012-08-30 2014-03-17 Konami Digital Entertainment Co Ltd 情報処理装置、情報処理装置の制御方法、及びプログラム

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH08249393A (ja) * 1995-03-13 1996-09-27 Intec:Kk 集中管理システム
JPH10208071A (ja) * 1997-01-17 1998-08-07 Dainippon Printing Co Ltd 可変プリントシステム
JP2000020197A (ja) * 1998-07-02 2000-01-21 Seiko Epson Corp 情報処理状況提示方法及びネットワーク情報送受信システム並びに情報処理状況提示処理プログラムを記録した記録媒体
JP2001167205A (ja) * 1999-10-25 2001-06-22 Iticket Co Ltd あつらえ型商品券発行システム及び方法
JP2001344498A (ja) * 2000-06-02 2001-12-14 Sekido Co Ltd 顧客管理システム
JP2003118279A (ja) * 2001-10-16 2003-04-23 Seiko Epson Corp 証券発券装置および証券発券システム
JP2008538017A (ja) * 2004-12-22 2008-10-02 ホン リー，カン 注文型チケットの発行方法及びその装置

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH08249393A (ja) * 1995-03-13 1996-09-27 Intec:Kk 集中管理システム
JPH10208071A (ja) * 1997-01-17 1998-08-07 Dainippon Printing Co Ltd 可変プリントシステム
JP2000020197A (ja) * 1998-07-02 2000-01-21 Seiko Epson Corp 情報処理状況提示方法及びネットワーク情報送受信システム並びに情報処理状況提示処理プログラムを記録した記録媒体
JP2001167205A (ja) * 1999-10-25 2001-06-22 Iticket Co Ltd あつらえ型商品券発行システム及び方法
JP2001344498A (ja) * 2000-06-02 2001-12-14 Sekido Co Ltd 顧客管理システム
JP2003118279A (ja) * 2001-10-16 2003-04-23 Seiko Epson Corp 証券発券装置および証券発券システム
JP2008538017A (ja) * 2004-12-22 2008-10-02 ホン リー，カン 注文型チケットの発行方法及びその装置

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2014048784A (ja) * 2012-08-30 2014-03-17 Konami Digital Entertainment Co Ltd 情報処理装置、情報処理装置の制御方法、及びプログラム

Similar Documents

Publication Publication Date Title
US8732809B2 (en) System, server device, method, program, and recording medium that enable facilitation of user authentication
JP3929450B2 (ja) 商品販売システム、それに用る商品販売用印刷物及びその印刷方法
US20070022214A1 (en) Transaction management apparatus and method
US20070118441A1 (en) Editable electronic catalogs
WO2011016450A1 (fr) Système de proposition de prix électronique, dispositif de proposition de prix électronique et procédé de proposition de prix électronique
US8554634B2 (en) Methods and systems for issuing tickets
JP2000268093A (ja) 情報提供者への謝礼用クーポン発行方法及び情報提供者への謝礼用クーポン発行システム並びに情報提供者への謝礼用クーポン発行処理プログラムを記録した記録媒体
US20010051893A1 (en) Online shopping system and method
JP2017162377A (ja) 広告動画管理装置、広告動画管理システム、広告動画管理プログラム、および広告動画管理方法
TW200901068A (en) Advertisement server device, advertisement display method and advertisement server program
KR20210043658A (ko) 정보 처리 방법, 정보 표시 방법, 프로그램, 단말 및 서버
JP5034049B2 (ja) アフィリエイト管理サーバ装置、アフィリエイト管理方法、およびアフィリエイト管理サーバプログラム
KR20010000710A (ko) 인터넷 상의 맞춤 광고 시스템 및 그 방법
WO2023286773A1 (fr) Procédé et système de fabrication pour produit fabriqué par impression
JP2008158663A (ja) ネットワークシステム、サーバ装置、情報処理方法及びサーバ装置用プログラム
WO2011030386A1 (fr) Système d'impression et procédé d'impression
WO2001098977A1 (fr) Systeme de signets
JP2009054189A (ja) サーバ、端末装置、プログラム、及び、記録媒体
JP2007087330A (ja) ホームページ提供システム、サーバ、方法、及びプログラム
JP6619114B1 (ja) チケット管理システムおよびプログラム
JP2003168047A (ja) 評価情報提供システム、方法及びプログラム
JP5775313B2 (ja) ポイント交換装置，ポイント交換のためのコンピュータプログラム，ポイント交換方法
JP2012160078A (ja) 広告管理サーバ
JP4253360B2 (ja) アフィリエイトシステム、アフィリエイト装置
JP2006309452A (ja) コンテンツ提供システム、センター側装置、端末装置、コンテンツ提供方法及びカード

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 09849166

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112 (1) EPC (EPO FORM 1205A DATED 21/06/2012)

NENP Non-entry into the national phase

Ref country code: JP

122 Ep: pct application non-entry in european phase

Ref document number: 09849166

Country of ref document: EP

Kind code of ref document: A1