Delivery assistance device, delivery assistance system, delivery assistance method, and program

Abstract

To make it possible to assist delivering a commemorative commodity of an event to a user.SOLUTION: A platform assists delivering a commemorative commodity of an event to a user by a delivery assistance apparatus 3, the delivery assistance apparatus including: a printing support unit 336 which performs printing support to support printing, on a printing medium, content including an image included in event information corresponding to an acquired event identifier, by referring to an event management unit 313 which stores event information including images related to events, in association with one or more event identifiers; a user information acquisition unit 335 which acquires user information having an address, the user information corresponding to a user identifier included in a delivery request received from a user terminal 2; and a delivery support unit 337 which performs delivery support to support delivering at least one commodity with printing medium corresponding to the event identifier attached to a container thereof, to a location indicated by the address acquired by the user information acquisition unit 335.SELECTED DRAWING: Figure 3

Description

[Technical field]

[0001] The present invention relates to a delivery support device or the like that realizes a mechanism by which a user can purchase a product on which an image related to an event is printed. [Background technology]

[0002] Conventionally, there has been a product sales system that can make more reliable sales forecasts for products sold at an event venue (see Patent Document 1). This product sales system includes a product sales server and a terminal device, the system including an order receiving unit that receives product orders from customers, a settlement processing unit that performs settlement processing for the orders, an order identification information output unit that outputs order identification information that identifies the orders for the customers, a counting unit that counts the number of orders received by the order receiving unit for each product, an order number output unit that outputs the counted number of orders for each product, and a first order content output unit that outputs the content of the order identified by the order identification information to a terminal device installed at the event venue after settlement processing in the settlement processing unit is completed. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2019-21059 A Summary of the Invention [Problem to be solved by the invention]

[0004] However, the conventional technology does not support the delivery of merchandise commemorating an event to a user. [Means for solving the problem]

[0005] The delivery support device of the first invention is a delivery support device comprising: an event identifier acquisition unit that acquires an event identifier that identifies an event; a printing support unit that refers to an event management unit in which event information including images related to the event is stored corresponding to each of one or more event identifiers, acquires content including an image included in the event information corresponding to the event identifier acquired by the event identifier acquisition unit, prints the content on a print medium, and performs printing support, which is support for acquiring the print medium; a request receiving unit that receives a delivery request having an event identifier and a user identifier that identifies the user from a user terminal; a user information acquisition unit that corresponds to the user identifier included in the delivery request and acquires user information having the user's address; and a delivery support unit that performs delivery support, which is support for delivering one or more products having print media corresponding to the event identifier included in the delivery request attached to their product containers, to a location indicated by an address corresponding to the user information acquired by the user information acquisition unit.

[0006] This configuration makes it possible to provide a platform that assists in delivering commemorative products for an event to users. Further, in the delivery support device of the second invention, in comparison with the first invention, the delivery support unit provides delivery support only to users who are participants in the event. This configuration makes it possible to provide a platform that assists in delivering products that will serve as mementos of an event to users.

[0007] Further, in a delivery support device according to a third aspect of the present invention, compared to the first aspect of the present invention, the event identifier included in the delivery request is information included in a medium sold to a user.

[0008] This configuration makes it possible to provide a platform that assists in delivering commemorative products for an event to users.

[0009] Furthermore, the delivery support device of the fourth invention is different from the delivery support device of the third invention in that the medium is medium that is sold at the venue of an event in which the user has participated.

[0010] This configuration makes it possible to provide a platform that assists users who purchase media sold at an event venue in delivering a merchandise as a memento of their participation in the event.

[0011] Furthermore, the delivery support device of the fifth invention is a delivery support device according to any one of the first to fourth inventions, wherein event information corresponding to one event identifier includes two or more images, the printing support unit refers to the event management unit to acquire content including each of the two or more images included in the event information corresponding to the event identifier acquired by the event identifier acquisition unit, and prints each of the two or more contents on a print medium, thereby providing printing support, which is support for acquiring the two or more print media, and the delivery support unit provides delivery support, which is support for delivering two or more products having two or more print media affixed to product containers, to a location indicated by an address corresponding to the user information acquired by the user information acquisition unit.

[0012] Such a configuration can provide a platform that assists in the delivery of two or more products printed with different content related to an event to a user.

[0013] In addition, the delivery support device of the sixth invention is a delivery support device according to any one of the first to fifth inventions, in which a delivery request has a product identifier that identifies a product, and a printing support unit refers to a product management unit in which product information regarding products that pair with one or more product identifiers is stored, acquires product information regarding the product identified by the product identifier in the delivery request, acquires content that also has product information, prints the content on a print medium, and performs printing support, which is support for acquiring the print medium.

[0014] This configuration allows the user to select the products to be delivered.

[0015] In addition, the delivery support device of the seventh invention is a delivery support device that, compared to any one of the first to sixth inventions, performs printing support by referring to a specific information management unit in which image specific information identifying one or more images is stored in correspondence with each of two or more course identifiers, acquiring the course identifier held by the delivery request, acquiring content having one or more images identified by the image specific information paired with the course identifier, printing each of the one or more contents on a print medium, and acquiring the one or more print media.

[0016] With this configuration, the user can select a course regarding the image to be printed on the product container.

[0017] In addition, the delivery support device of the eighth invention is different from the third invention in that the medium sold to the user includes a unique medium identifier, and the delivery request includes the medium identifier, and refers to a media management unit that manages one or more media identifiers that correspond to each of one or more event identifiers, and further includes an authentication unit that determines whether the event identifier and the media identifier contained in the delivery request received by the request receiving unit correspond to each other, and the delivery support device does not provide delivery support if the authentication unit determines that the event identifier and the media identifier do not correspond to each other.

[0018] With this configuration, by authenticating the medium, the product can be delivered only to the proper user.

[0019] A delivery support system according to a ninth aspect of the present invention is a delivery support system having one or more media including an event identifier, a delivery support device, and one or more printers that print on the print media.

[0020] This configuration makes it possible to provide a platform that assists in delivering commemorative products for an event to users.

[0021] The delivery support method of the tenth invention is a delivery support method comprising an event information preparation step, a medium preparation step, a product creation step, and a product delivery step, in which the event information preparation step comprises an image receiving substep of receiving one or more images related to the event, and an image storage substep of storing one or more images in pairs with an event identifier of the event, the medium preparation step comprises a medium creation substep of acquiring an event identifier and a unique medium identifier, and creating one or more media having an event identifier and a medium identifier, the product creation step comprises a printing substep of acquiring content including one or more images corresponding to the event identifier, and printing the one or more contents on a printed medium, and an attaching substep of attaching the one or more printed media to a product container, and the product delivery step comprises a request receiving substep of receiving a delivery request having the event identifier and a user identifier that identifies the user from a user terminal, a user information acquisition substep of acquiring user information having the user's address corresponding to the user identifier included in the delivery request, and a user information output substep of outputting the user information.

[0022] This configuration makes it possible to provide a platform that assists in delivering commemorative products for an event to users. Effect of the Invention

[0023] The delivery assistance device according to the present invention can provide a platform that assists in the delivery of commemorative products for an event to users. [Brief description of the drawings]

[0024] [Figure 1] Conceptual diagram of delivery support system A in embodiment 1 [Diagram 2] Block diagram of the delivery support system A [Diagram 3] Block diagram of the delivery support device 3 [Figure 4] 1 is a flowchart illustrating a first operation example of the delivery support device 3. [Diagram 5] A flowchart illustrating an example of the event information preparation process. [Figure 6] A flowchart illustrating an example of the medium preparation process. [Figure 7] A flowchart illustrating an example of the authentication process. [Figure 8] A flowchart illustrating an example of the product creation process. [Figure 9] A flowchart illustrating an example of the product delivery process [Figure 10] 11 is a flowchart illustrating a second operation example of the delivery support device 3. [Figure 11] A flowchart for explaining an example of the event product creation process [Figure 12] A flowchart illustrating an example of the product delivery process [Figure 13] A diagram showing the product management table [Figure 14] FIG. 2 shows the specific information management table. [Figure 15] A diagram showing the event management table [Figure 16] A diagram showing the media management table [Figure 17] A diagram showing an example of the medium 1 [Figure 18] The user management table [Figure 19] A diagram showing an example of the screen [Figure 20] A diagram showing an example of the product DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0025] Hereinafter, an embodiment of a delivery support device and the like will be described with reference to the drawings. Note that components with the same reference numerals in the embodiments perform similar operations, and therefore repeated description may be omitted.

[0026] (Embodiment 1) In this embodiment, a delivery support system that realizes a mechanism for delivering products with images related to an event printed thereon to users involved in the event will be described. Note that users involved in an event are usually users who have participated in the event. However, users involved in an event may also include members of a fan club of a person who implements the event (for example, a performer at the event).

[0027] In addition, in this embodiment, we will describe a delivery support system that receives an event identifier contained in media sold to a user at an event venue from a user terminal, and delivers a product printed with an image related to the event identified by the event identifier to the user.

[0028] In addition, in this embodiment, a delivery support system is described that assists in printing two or more pieces of content, each of which includes two or more images related to an event, onto a print medium, and realizes a mechanism for delivering two or more products having the two or more print media to a user.

[0029] In this embodiment, a delivery support system in which a user can select one or more products from two or more products will be described.

[0030] In addition, in this embodiment, a delivery support system will be described in which a user can select a course for a set of one or more images to be displayed on a product container.

[0031] Furthermore, in this embodiment, a delivery support system will be described which uses a medium identifier input by a user to authenticate whether or not the medium is authentic.

[0032] In this specification, information X being associated with information Y means that information Y can be obtained from information X, or information X can be obtained from information Y, and the method of association is not important. Information X and information Y may be linked, may exist in the same buffer, information X may be included in information Y, or information Y may be included in information X, etc.

[0033] Furthermore, in this specification, selecting or determining information Z means obtaining information Z, obtaining a pointer to information Z, obtaining the ID of information Z, setting a flag for information Z, etc., and is sufficient as long as information Z can be accessed.

[0034] 1 is a conceptual diagram of a delivery support system A according to the present embodiment. The delivery support system A includes one or more media 1, one or more user terminals 2, a delivery support device 3, and one or more printers 4.

[0035] Medium 1 indicates the right for a user to obtain a product. Medium 1 is, for example, paper, but may be electronic data. Medium 1 is, for example, a card. However, the material and means of realization of medium 1 are not important. Medium 1 may be a so-called ticket. Medium 1 is, for example, an event ticket. Medium 1 is usually an object that a user purchases in order to obtain a product. Medium 1 is usually sold at an event venue that the user has attended. Medium 1 usually includes an event identifier. Medium 1 has, for example, a medium identifier.

[0036] An event identifier is information that identifies an event, such as the event name, the event ID, or a URL or URI that identifies a web page for inputting a delivery request for products for the event.

[0037] An event can be, for example, a concert, a live performance, a professional sports game, a fireworks display, or a play, but the type of event is not important. An event venue, which will be described later, is a venue where an event takes place. Event venues can be, for example, sports venues such as baseball stadiums, soccer fields, and golf courses, concert venues, play venues, theme parks, exposition venues, art galleries, museums, observation decks, parks, and tourist facilities. However, an event venue can be any place where an event takes place, and the type of event is not important.

[0038] Incidentally, an event may be called, for example, leisure. Leisure is entertainment. Leisure may be broadly understood to include sightseeing and recreation. Leisure may be, for example, watching sports, concerts, plays, playing sports, etc., but the type of leisure is not important.

[0039] The medium identifier is unique information for identifying a medium. The medium identifier is different information for each of two or more media 1. The medium identifier is, for example, a serial number, a serial code, or a unique character string. The medium identifier may also serve as an event identifier.

[0040] The user terminal 2 is a terminal used by a user who requests delivery of a product. Such a user is usually a person who has purchased the medium 1, but may also be a person who has received the medium 1 from a person who has purchased the medium 1. The user terminal 2 is, for example, a personal computer, a tablet terminal, or a smartphone, but the type of the terminal is not important.

[0041] The delivery support device 3 is a device that supports a process of delivering at least one or more products to a user. The delivery support device 3 is usually a server. The delivery support device 3 is, for example, a so-called cloud server or an ASP server.

[0042] The printing device 4 is a printer. It is preferable that the printing device 4 is a label printer, but the type of printer is not important. The printing device 4 is a device that prints content, which will be described later, on a printing medium, which will be described later. It is preferable that the printing medium is a sticker that is affixed to a product delivered to a user, but it may be paper or other material, and the material, etc., is not important. The printing medium may be a product container. A product container is a container that contains a product. The product may be, for example, a food product, but it is not important. The food may be, for example, a beverage, but it is not important. The container is, for example, a can, but it may be made of paper, and the means of realizing it is not important.

[0043] Fig. 2 is a block diagram of the delivery support system A in this embodiment. Fig. 3 is a block diagram of the delivery support device 3.

[0044] The user terminal 2 includes a terminal storage unit 21, a terminal reception unit 22, a terminal processing unit 23, a terminal transmission unit 24, a terminal reception unit 25, and a terminal output unit .

[0045] The delivery support device 3 includes a storage unit 31, a receiving unit 32, a processing unit 33, and a transmitting unit 34. The storage unit 31 includes a product management unit 311, a specific information management unit 312, an event management unit 313, a medium management unit 314, and a user management unit 315. The receiving unit 32 includes an image receiving unit 321 and a request receiving unit 322. The processing unit 33 includes a medium creation unit 331, an image accumulation unit 332, an event identifier acquisition unit 333, an authentication unit 334, a user information acquisition unit 335, a printing support unit 336, and a delivery support unit 337.

[0046] Various types of information are stored in the terminal storage unit 21 constituting the user terminal 2. The various types of information are, for example, a user identifier. Note that the user identifier may be input by the user and temporarily stored in the terminal storage unit 21.

[0047] The user identifier is information that identifies a user. The user identifier is, for example, an address, a telephone number, or a name. The user identifier may be, for example, a medium identifier. The user identifier is, for example, a member ID of a user who is a member of a fan club.

[0048] The terminal reception unit 22 receives various instructions and information, such as an event identifier, a delivery request, and user information.

[0049] A delivery request is an instruction to request delivery of a product. A delivery request is usually an instruction to request delivery of a product based on a medium 1 purchased by a user. A delivery request usually has an event identifier and a user identifier. A delivery request has, for example, one or more product identifiers. A delivery request has, for example, a course identifier described below. It is preferable that a delivery request has a medium identifier. The medium identifier here is, for example, a serial number or serial code. Note that two or more pieces of information constituting a delivery request do not need to be accepted at the same time, and may be accepted at different times.

[0050] The delivery request may include user information. User information is information about the user of the delivery destination. User information is, for example, an address, a telephone number, and a name. User information is information that can identify a user, so it may be a user identifier.

[0051] An event identifier is information that identifies an event. The event identifier may be included in the medium identifier, or may be the medium identifier. The event identifier is, for example, a URI or a URL. When the event identifier is a URI or a URL, a web page that can be identified by the URI or URL is usually a web page for requesting delivery of a product at the event, or a web page that can transition to the web page.

[0052] A product identifier is information that identifies a product. The product identifier included in a delivery request is information that identifies a product selected by a user. The product identifier is, for example, information that indicates the type of product (e.g., "coffee," "water," "lemon flavor," "peach flavor").

[0053] Means for inputting instructions and information may be any means, such as a code reader, a touch panel, a keyboard, a mouse, or a menu screen.

[0054] The terminal receiving unit 22 acquires a delivery request based on, for example, reading a code in which an event identifier is embedded. The terminal receiving unit 22 accepts a delivery request inputted on a screen displayed using a webpage acquired using a URL acquired by reading the code in which the event identifier is embedded. The terminal receiving unit 22 accepts, for example, an event identifier inputted by a user. The terminal receiving unit 22 accepts, for example, user information inputted by a user.

[0055] The code is, for example, a two-dimensional code, but may be a barcode or the like, and the type does not matter. The two-dimensional code is, for example, a QR code (registered trademark), but may be a color code or the like, and the type does not matter.

[0056] When a delivery request includes two or more pieces of information, the terminal reception unit 22 does not need to receive the two or more pieces of information at once.

[0057] The device processing unit 23 performs various types of processing, such as processing for changing instructions, information, etc. received by the terminal reception unit 22 into instructions, information, etc. with a structure to be transmitted, processing for changing information received by the terminal reception unit 25 into a structure for outputting information, processing for constructing a screen from screen information received by the terminal reception unit 25, etc.

[0058] The terminal transmission unit 24 transmits various information, instructions, etc. The various information, instructions, etc. are, for example, a delivery request. When the delivery request has two or more pieces of information, the terminal transmission unit 24 does not need to transmit all of the information at once, and may transmit the information at two or more timings.

[0059] The terminal receiving unit 25 receives various information. For example, the terminal receiving unit 25 receives various information from the delivery support device 3. The various information is, for example, screen information and information indicating that a delivery request has been accepted.

[0060] The terminal output unit 26 outputs various information. The various information is, for example, information received by the terminal receiving unit 25 and changed to a structure to be output by the terminal processing unit 23, such as a screen or information that a delivery request has been accepted.

[0061] Here, output is a concept that includes display on a display, projection using a projector, printing on a printer, sound output, transmission to an external device, storage on a recording medium, and handing over the processing results to other processing devices or other programs, etc.

[0062] Various types of information are stored in the storage unit 31 constituting the delivery support device 3. The various types of information include, for example, product information (to be described later), image specification information (to be described later), event information (to be described later), a medium identifier, and user information (to be described later).

[0063] The product management unit 311 stores one or more pieces of product information. Product information is information related to a product. Product information has, for example, one or more product attribute values. The product attribute values ​​are, for example, the type of product, the product name, and the ingredients of the product. Each of the one or more pieces of product information is paired with a product identifier. The product identifier is information that identifies a product. The product identifier is, for example, the product ID, the JAN code, the product name, and the product type.

[0064] The identification information management unit 312 stores two or more pieces of image identification information. The image identification information is information that identifies one or more images. Each of the one or more images identified by the image identification information is an image to be printed on a print medium. The image identification information has, for example, an image identifier, but it is sufficient if it is information that can identify one or more images. The image identifier is information that identifies an image. The image identifier is, for example, information that identifies people appearing in an image. The image identifier is, for example, information that indicates that the image includes all members of a group.

[0065] Each of the two or more pieces of image specifying information corresponds to a course identifier. The course identifier is information that identifies the image specifying information. The course identifier is, for example, an ID or a course name. The course identifier is, for example, "everyone in a group" performing an event (e.g., a concert), or "Mr. A" indicating a specific member of a group.

[0066] The event management unit 313 stores one or more pieces of event information. Event information is information related to an event. Event information has one or more event attribute values. The event attribute values ​​include, for example, the event name, the date the event was held, the time period when the event was held, the location where the event was held, and the like. It is preferable that the event information is associated with one or more images related to the event. The image related to the event is, for example, a photograph taken at the event, but may also be a video taken at the event, an illustration of the event, and the like. For example, an image identifier is associated with the image. The image identifier is information that identifies the image. It is preferable that the event information is associated with the event identifier.

[0067] The medium manager 314 stores one or more medium identifiers corresponding to one or more event identifiers. The medium identifier is, for example, a serial number. When a medium identifier corresponds to an event identifier, the medium identifier may be considered to include the event identifier.

[0068] The user management unit 315 stores one or more pieces of user information. User information is information about a user. User information corresponds to a user identifier. User information usually has one or more user attribute values. User attribute values ​​are, for example, a name, an address, and a telephone number. It is preferable that the user information includes information indicating a delivery address of a product to the user. The user information may include information identifying one or more events in which the user participated. The information identifying an event is, for example, an event identifier.

[0069] The receiving unit 32 receives various instructions or information. The various information is, for example, an image, an instruction to prepare event information, an instruction to prepare a medium, a delivery request, and an instruction to create a product. The receiving unit 32 receives, for example, an instruction to prepare event information, an instruction to prepare a medium, or an instruction to create a product from an operator terminal (not shown).

[0070] The operator terminal is a terminal used by the operator of the delivery support device 3. The operator may be a part-time worker or the like, and the term is broadly understood regardless of the operator's position.

[0071] The instruction to prepare event information is an instruction to store the event information in the event management unit 313. The instruction to prepare event information includes, for example, an event identifier and the event information.

[0072] The medium preparation instruction is an instruction to create one or more media 1 to be handed over to a user. The medium preparation instruction includes, for example, an event identifier, event information, and additional information. Note that the medium 1 is usually an object to be sold to a user.

[0073] The product production instruction is an instruction to produce a product. The product production instruction includes, for example, an event identifier.

[0074] The image receiving unit 321 receives one or more images. It is preferable that the image receiving unit 321 receives an image corresponding to one or more pieces of information among an event identifier, one or more event attribute values, and an image identifier. For example, the image receiving unit 321 receives an image (photo or video) taken by a camera (not shown). For example, the image receiving unit 321 receives an image taken by a camera (not shown) from the camera. It is preferable that the image taken by the camera is an image of the event while the event is being carried out.

[0075] The request receiving unit 322 receives a delivery request having an event identifier and a user identifier from the user terminal 2. The request receiving unit 322 does not need to receive the event identifier and the user identifier at the same time. It is preferable that the user terminal 2 is a terminal of a user who is a participant of the event.

[0076] The processing unit 33 performs various types of processing. The various types of processing are, for example, processing performed by a medium creation unit 331, an image storage unit 332, an event identifier acquisition unit 333, an authentication unit 334, a user information acquisition unit 335, a printing support unit 336, and a delivery support unit 337.

[0077] The medium creation unit 331 creates one or more media 1. The medium creation unit 331 acquires, for example, a unique medium identifier. The medium creation unit 331 also acquires, for example, a code in which an event identifier (for example, a URL) is embedded. The medium creation unit 331 also acquires, for example, additional information stored in the storage unit 31. The additional information is, for example, a fixed phrase. Next, the medium creation unit 331 prints, for example, the acquired medium identifier, code, and additional information on one or more media. As a result, one or more media 1 including a medium identifier and an event identifier are created. Note that the medium 1 does not have to have additional information.

[0078] Note that the medium creation unit 331 may use any algorithm to acquire a unique medium identifier, and may generate a new medium identifier by, for example, adding 1 to the latest medium identifier. The medium creation unit 331 may acquire an unused medium identifier from a set of two or more unique medium identifiers, for example.

[0079] It is preferable that the medium creation unit 331 creates one or more media 1 upon receiving a medium preparation instruction from the administrator terminal.

[0080] The image storage unit 332 stores each of the one or more images received by the image receiving unit 321 in the event management unit 313 in association with the event identifier. It is preferable that the image storage unit 332 stores each of the one or more images received by the image receiving unit 321 in the event management unit 313 in association with the image identifier.

[0081] The event identifier acquisition unit 333 acquires an event identifier that identifies an event. For example, the event identifier acquisition unit 333 acquires an event identifier included in a delivery request received by the request receiving unit 322. For example, the event identifier acquisition unit 333 acquires an event identifier received from a terminal (not shown). For example, the event identifier acquisition unit 333 acquires one or more event identifiers from the event management unit 313.

[0082] The authentication unit 334 refers to the medium management unit 314 and judges whether the event identifier contained in the delivery request received by the request receiving unit 322 corresponds to the medium identifier contained in the delivery request. Then, the authentication unit 334 acquires the judgment result (for example, "authentication permitted" or "authentication not permitted"). It is preferable that the event identifier and medium identifier contained in the delivery request are information contained in the medium 1 sold to the user, for example. The authentication unit 334 may determine whether or not the user who sent the delivery request received by the request receiving unit 322 is a user who participated in the event corresponding to the delivery request. For example, the authentication unit 334 refers to the user management unit 315 and determines whether or not the event identifier of the delivery request received by the request receiving unit 322 is included in the event identifiers that are paired with the user identifier corresponding to the delivery request.

[0083] The user information acquisition unit 335 acquires user information having a user address corresponding to a user identifier included in the delivery request. The user information corresponding to a user identifier may be regarded as a user identifier. The user information acquisition unit 335 acquires, for example, user information included in the delivery request. For example, the user information acquisition unit 335 acquires user information paired with the user identifier included in the delivery request from the user management unit 315.

[0084] The printing support unit 336 performs printing support. The printing support is a process for acquiring a print medium including content. The content is information to be printed on the print medium. The content usually has one image. The content may have two or more images. The content has, for example, one or more of the following information: user information, artist name, date, time period, venue name, and serial number. The user information here is, for example, a name.

[0085] More specifically, the printing support unit 336 refers to the event management unit 313 and acquires content including an image included in the event information corresponding to the event identifier acquired by the event identifier acquisition unit 333. Next, the printing support unit 336 prints the content on a print medium. As a result, a print medium on which the content is printed is obtained. The print medium is, for example, a sticker. The print medium on which the content is printed is attached to, for example, a product container.

[0086] For example, the printing support unit 336 refers to the event management unit 313 to acquire content including two or more images included in the event information corresponding to the event identifier acquired by the event identifier acquisition unit 333. Next, the printing support unit 336 prints the two or more contents on a print medium. As a result, two or more print media on which different contents are printed are acquired.

[0087] The printing support unit 336, for example, refers to the product management unit 311, acquires product information on the product identified by the product identifier included in the received delivery request, acquires content that also includes the product information, and prints the content on a print medium. Note that the product information here may include the product identifier, or may be just the product identifier.

[0088] The printing support unit 336, for example, refers to the specific information management unit 312, acquires a route identifier included in the delivery request, and acquires content having one or more images identified by image specific information paired with the route identifier. Next, the printing support unit 336 prints the one or more contents on a print medium, and acquires one or more print media.

[0089] The printing support unit 336 performs printing support, for example, when an event identifier is received. It is preferable that the printing support unit 336 performs printing support in response to a delivery request including an event identifier being received from the user terminal 2. However, the printing support unit 336 may also perform printing support when an event identifier is received from the operator terminal.

[0090] After one or more print media are created by the processing of the printing support unit 336, each of the one or more print media is usually attached to a product container. This work is performed, for example, by a person, but may also be performed by a robot (not shown). After the print media are attached to the product container, work such as packing one or more products into a box for delivery to a user may also be performed. This work is performed, for example, by a person, but may also be performed by a robot (not shown).

[0091] Furthermore, it is preferable that the printing support unit 336 does not perform the above-mentioned printing support when the authentication unit 334 determines that the event identifier and the medium identifier do not correspond to each other.

[0092] The delivery support unit 337 provides delivery support, which is support for delivering one or more products having printed media affixed to a product container corresponding to the event identifier contained in the received delivery request, to a location indicated by an address corresponding to the user information acquired by the user information acquisition unit 335. It is preferable that the delivery support unit 337 provides delivery support only to users who are participants in an event. It is preferable that the delivery support unit 337 does not provide delivery support when, for example, the authentication unit 334 determines that the user who sent the delivery request received by the request receiving unit 322 is not a user who participated in the event corresponding to the delivery request. It is preferable that, when a user is not a user who participated in an event, a screen for sending a delivery request corresponding to the event is not output to the terminal device 2 of the user.

[0093] The delivery support unit 337 provides delivery support, which is support for delivering two or more products, each of which has two or more printed media affixed to a product container, to a location indicated by an address corresponding to the user information acquired by the user information acquisition unit 335.

[0094] The delivery support is, for example, a process of outputting information including an address and a name included in the user information. Here, output is a concept including, for example, display on a display, projection using a projector, printing on a printer, sound output, transmission to an external device, storage on a recording medium, and delivery of the processing result to another processing device or another program. In other words, the delivery support is, for example, a process of printing information including an address and a name included in the user information on a delivery slip. The delivery support is, for example, a process of displaying information including an address and a name included in the user information on a display that is viewed by a worker who fills out the delivery slip. The delivery support is, for example, a process of printing information including an address and a name included in the user information on paper (for example, a label, a sticker) that is affixed to the delivery slip.

[0095] It is preferable that the delivery support unit 337 does not provide delivery support if the authentication unit 334 determines that the event identifier and the medium identifier do not correspond to each other. It is preferable that the printing support unit 336 does not provide printing support if the delivery support unit 337 does not provide delivery support.

[0096] The transmission unit 34 transmits various types of information. The transmission unit 34 transmits, for example, various types of information to the user terminal 2. The various types of information are, for example, information that indicates that the product delivery request has been accepted, and an error message. The error message is information that indicates that the delivery request has not been authenticated.

[0097] The terminal storage unit 21, storage unit 31, product management unit 311, specific information management unit 312, event management unit 313, media management unit 314, and user management unit 315 are preferably implemented as non-volatile recording media, but can also be implemented as volatile recording media.

[0098] There is no restriction on the process by which information is stored in the terminal storage unit 21, etc. For example, information may be stored in the terminal storage unit 21, etc. via a recording medium, information transmitted via a communication line, etc. may be stored in the terminal storage unit 21, etc., or information inputted via an input device may be stored in the terminal storage unit 21, etc.

[0099] The terminal reception unit 22 can be realized by a device driver for an input means such as a code reader, a touch panel, or a keyboard, or by control software for a menu screen.

[0100] The terminal processing unit 23, processing unit 33, medium creation unit 331, image storage unit 332, event identifier acquisition unit 333, authentication unit 334, user information acquisition unit 335, print support unit 336, and delivery support unit 337 can usually be realized by a processor, memory, etc. The processing procedures of the terminal processing unit 23, etc. are usually realized by software, and the software is recorded in a recording medium such as a ROM. However, they may also be realized by hardware (dedicated circuit). The processor may be a CPU, MPU, GPU, etc., and the type is not important.

[0101] The terminal transmitting unit 24 and the transmitting unit 34 are usually realized by wireless or wired communication means, but may also be realized by broadcasting means.

[0102] The terminal receiving unit 25, the receiving unit 32, the image receiving unit 321, and the request receiving unit 322 are usually realized by wireless or wired communication means, but may also be realized by means for receiving broadcasts.

[0103] The terminal output unit 26 may or may not include an output device such as a display, a speaker, etc. The terminal output unit 26 etc. may be realized by driver software for an output device, or a combination of driver software for an output device and an output device, etc.

[0104] Next, a first operation example of the delivery support device 3 will be described with reference to the flowchart of Fig. 4. The first operation example is a case where a product is produced in response to receiving a delivery request.

[0105] (Step S401) The receiving unit 32 judges whether or not a preparation instruction for event information has been received from the administrator terminal. If the preparation instruction has been received, the process proceeds to step S402, and if not, the process proceeds to step S403.

[0106] (Step S402) The processing unit 33 performs an event information preparation process. Return to step S401. The event information preparation process is a process for preparing event information and one or more images of the event. An example of the event information preparation process will be described with reference to the flowchart of FIG.

[0107] (Step S403) The receiving unit 32 judges whether or not a medium preparation instruction has been received from the operator terminal. If the medium preparation instruction has been received, the process proceeds to step S404, and if not, the process proceeds to step S405.

[0108] (Step S404) The medium creation unit 331 performs a medium preparation process. Return to step S401. The medium preparation process is a process for preparing the medium 1 to be sold to the user. An example of the medium preparation process will be described with reference to the flowchart of FIG.

[0109] (Step S405) The request receiving unit 322 determines whether or not a delivery request has been received from the user terminal 2. If a delivery request has been received, the process proceeds to step S406, and if not, the process returns to step S401.

[0110] (Step S406) The authentication unit 334 performs authentication processing. The authentication processing is processing for determining whether or not the received delivery request is valid. An example of the authentication processing will be described with reference to the flowchart of FIG.

[0111] (Step S407) The processing unit 33 judges whether the result of the authentication process in step S406 was “authentication permitted” or “authentication not permitted.” If the result is “authentication permitted,” the process proceeds to step S408, and if the result is “authentication not permitted,” the process proceeds to step S410.

[0112] (Step S408) The processing unit 33 performs a product creation process. The product creation process is a process for supporting the creation of a product to be delivered to a user. An example of the product creation process will be described with reference to the flowchart of FIG. 8. The product creation process usually includes printing support.

[0113] (Step S409) The delivery support unit 337 performs a product delivery process. Return to step S401. The product delivery process is a process for supporting the delivery of a product to a user. An example of the product delivery process will be described with reference to the flowchart of FIG. 9. The product delivery process includes delivery support.

[0114] (Step S410) The processing unit 33 acquires an error message indicating that the authentication was not permitted. The transmission unit 34 transmits the error message to the user terminal 2 that transmitted the delivery request. The process returns to step S401.

[0115] In the flowchart of FIG. 4, the process ends when the power is turned off or an interrupt is issued to end the process.

[0116] Next, an example of the event information preparation process in step S402 will be described with reference to the flowchart in FIG.

[0117] (Step S501) The processing unit 33 acquires an event identifier that is unique to an event. For example, the processing unit 33 acquires the event identifier included in the received preparation instruction. For example, the processing unit 33 generates a unique event identifier.

[0118] (Step S502) The processing unit 33 acquires one or more event attribute values ​​included in the received preparation instruction.

[0119] (Step S503) The processing unit 33 configures event information having an event identifier and one or more event attribute values. The processing unit 33 accumulates the event information in the event management unit 313.

[0120] (Step S504) The image receiving unit 321 judges whether or not an image has been received from a camera (not shown) or the like. If an image has been received, the process proceeds to step S505. If an image has not been received, the process proceeds to step S506. Note that the image here corresponds to an event identifier and one or more image attribute values.

[0121] (Step S505) The image storage unit 332 stores the image received in step S504 in the event management unit 313 in association with the event identifier and one or more image attribute values. The process returns to step S504.

[0122] (Step S506) The processing unit 33 judges whether or not to end preparation of the event information. If preparation of the event information is to be ended, the processing unit 33 returns to the upper processing, and if preparation of the event information is not to be ended, the processing unit 33 returns to step S504. Preparation of the event information is ended when information of the end of the event is received, when a predetermined time has arrived, when an instruction to end preparation of the event information is received from the operator terminal, etc. However, any condition is required to end preparation of the event information.

[0123] Next, an example of the medium preparation process in step S404 will be described with reference to the flowchart in FIG.

[0124] (Step S601) The medium creation unit 331 acquires an event identifier corresponding to a medium preparation instruction.

[0125] (Step S602) The medium creation unit 331 creates a code (for example, a two-dimensional code) in which the event identifier is embedded.

[0126] (Step S603) The medium creation unit 331 acquires from the event management unit 313 one or more event attribute values ​​that are paired with the event identifier.

[0127] (Step S604) The medium creation unit 331 acquires additional information associated with the event identifier in the event management unit 313.

[0128] (Step S605) The medium production unit 331 assigns 1 to a counter i.

[0129] (Step S606) The medium creation unit 331 judges whether or not to create the i-th medium 1. If the i-th medium 1 is to be created, the process proceeds to step S607, and if the i-th medium 1 is not to be created, the process returns to the upper process. Note that, for example, the number of media 1 to be created is determined in advance. The number of media 1 to be created is the planned number of media 1 to be sold.

[0130] (Step S607) The medium creation unit 331 acquires a medium identifier that is unique to the i-th medium 1.

[0131] (Step S608) The medium creation unit 331 composes output information having the medium identifier acquired in step S607, the code acquired in step S602, and one or more event attribute values ​​acquired in step S603. The output information is information that is displayed on the medium 1. It is preferable that the output information has additional information.

[0132] (Step S609) The medium creation unit 331 prints the output information on a medium, and acquires the i-th medium 1 on which the output information is printed.

[0133] (Step S610) The medium creation unit 331 stores the medium identifier acquired in step S607 in the medium management unit 314 in association with the event identifier. The counter i is incremented by 1. The process returns to step S606.

[0134] (Step S611) The medium production unit 331 increments the counter i by 1. The process returns to step S606.

[0135] Next, an example of the authentication process in step S406 will be described with reference to the flowchart in FIG.

[0136] (Step S701) The authentication unit 334 acquires a medium identifier.

[0137] (Step S702) The authentication unit 334 acquires an event identifier.

[0138] (Step S703) The authentication unit 334 judges whether or not information pairing the medium identifier acquired in step S701 and the event identifier acquired in step S702 exists in the medium management unit 314. If information pairing the medium identifier and the event identifier exists, the process proceeds to step S704, and if not, the process proceeds to step S705.

[0139] (Step S704) Authentication unit 334 assigns "authentication permitted" to the variable "result", and returns to the upper level process.

[0140] (Step S705) Authentication unit 334 assigns "authentication not permitted" to the variable "result", and returns to the upper level process.

[0141] Next, an example of the product creation process in step S408 will be described with reference to the flowchart in FIG.

[0142] (Step S801) Event identifier acquisition unit 333 acquires an event identifier corresponding to the received delivery request. Event identifier acquisition unit 333 acquires event information corresponding to the event identifier from event management unit 313.

[0143] (Step S802) The user information acquisition unit 335 acquires user information corresponding to the received delivery request.

[0144] (Step S803) The print support unit 336 acquires the medium identifier included in the received delivery request.

[0145] (Step S804) The print support unit 336 acquires the route identifier included in the received delivery request.

[0146] (Step S805) The print support unit 336 acquires, from the identification information management unit 312, image identification information paired with the course identifier acquired in step S804.

[0147] (Step S806) The print support unit 336 acquires from the event management unit 313 one or more images that are identified by the image identification information acquired in step S805 and that are paired with the event identifier.

[0148] (Step S807) The print support unit 336 assigns 1 to a counter i.

[0149] (Step S808) The printing support unit 336 determines whether or not to create the i-th print medium. If the i-th print medium is to be created, the process proceeds to step S809. If not, the process proceeds to step S813. Note that the number of print media to be created is predetermined, or is determined based on information included in the delivery request (e.g., product identifier).

[0150] (Step S809) The printing support unit 336 acquires one or more images to be used for the i-th print medium, which are among the one or more images acquired in step S806. Note that the one or more images to be used for the i-th print medium are, for example, the i-th image among the one or more images acquired in step S806.

[0151] (Step S810) The print support unit 336 composes content including one or more images acquired in step S809. Note that it is preferable that such content includes one or more of the following information: an event identifier, event information, user information, and a medium identifier.

[0152] (Step S811) The print support unit 336 prints the content configured in step S810 on a print medium. The printing is performed by the printing device 4.

[0153] (Step S812) The print support unit 336 increments the counter i by 1. The process returns to step S808.

[0154] (Step S813) The delivery support unit 337 acquires one or more product identifiers contained in the received delivery request.

[0155] (Step S814) The delivery support unit 337 outputs one or more product identifiers acquired in step S813. The process returns to the upper level. The output here is, for example, a transmission to a terminal (not shown) of a worker who attaches a print medium (e.g., a sticker) to the product.

[0156] In the flowchart of FIG. 8, the processes in steps S813 and S814 may be considered as part of the delivery support process.

[0157] Next, an example of the product delivery process in step S409 will be described with reference to the flowchart in FIG.

[0158] (Step S901) The delivery support unit 337 acquires the name, postal code, address, and telephone number contained in the acquired user information.

[0159] (Step S902) The delivery support unit 337 acquires delivery time information included in the delivery request, or delivery time information based on today's date. Delivery time information is information that specifies the date on which the product will be delivered to the user, or the date and time period. Delivery time information based on today's date is information that includes a date that is a predetermined day or later (e.g., two days later) from today's date.

[0160] (Step S903) The delivery support unit 337 creates delivery information having the name, postal code, address, telephone number, and delivery time information.

[0161] (Step S904) The delivery support unit 337 outputs the delivery information configured in step S903. The output here is, for example, printing the delivery information on a delivery slip for home delivery, or sending it to the terminal of a worker who makes arrangements for home delivery of the product to the user.

[0162] Next, a second operation example of the delivery support device 3 will be described with reference to the flowchart of Fig. 10. In the flowchart of Fig. 10, the explanation of the same steps as those in the flowchart of Fig. 4 will be omitted. Note that the second operation example is a case where a product is created before receiving a delivery request. Note that the creation of the product here does not have to include packaging of the product.

[0163] (Step S1001) The receiving unit 32 judges whether or not a product creation instruction has been received from the operator terminal. If a product creation instruction has been received, the process proceeds to step S1002, and if not, the process proceeds to step S405.

[0164] (Step S1002) The print support unit 336 performs support processing for creating a product identified by the event identifier included in the product creation instruction. Return to step S401. An example of such an event product creation processing will be described with reference to the flowchart of FIG.

[0165] (Step S1003) The delivery support unit 337 performs product delivery processing. Return to step S401. An example of the product delivery processing will be described with reference to the flowchart of FIG.

[0166] In the flowchart of FIG. 10, the process ends when the power is turned off or an interrupt is issued to end the process.

[0167] Next, an example of the event product creation process in step S1002 will be described with reference to the flowchart in Fig. 11. The event product creation process is a process for creating a product before receiving a delivery request from a user.

[0168] (Step S1101) The event identifier acquisition unit 333 acquires an event identifier corresponding to the received product production instruction. The event identifier acquisition unit 333 acquires event information corresponding to the event identifier from the event management unit 313.

[0169] (Step S1102) The print support unit 336 acquires from the event management unit 313 one or more images that are paired with the event identifier acquired in step S1101.

[0170] (Step S1103) The print support unit 336 assigns 1 to a counter i.

[0171] (Step S1104) The printing support unit 336 judges whether or not to create the i-th print medium. If the i-th print medium is to be created, the process proceeds to step S1105. If not, the process returns to the upper process. Note that the number of print media to be created is predetermined, or is the number of images acquired in step S1102.

[0172] (Step S1105) The print support unit 336 acquires one or more images which are among the one or more images acquired in step S1106 and are to be used for the i-th print medium.

[0173] (Step S1106) The print support unit 336 composes content including one or more images acquired in step S1109. The content preferably includes event information. Also, the image included in the content preferably is the ith image among the images acquired in step S1109.

[0174] (Step S1107) The printing support unit 336 prints the content created in step S1110 onto a print medium. The printing is performed by the printing device 4. The printing support unit 336 usually prints the content created in step S1110 onto a print medium a predetermined number of times or a number of times included in the product production instructions.

[0175] (Step S1108) The print support unit 336 increments the counter i by 1. The process returns to step S1104.

[0176] Next, an example of the product delivery process in step S1003 will be described with reference to the flowchart in Fig. 12. In the flowchart in Fig. 12, the description of the same steps as in the flowchart in Fig. 8 or 9 will be omitted.

[0177] (Step S1201) The delivery support unit 337 acquires image identification information corresponding to the acquired route identifier from the identification information management unit 312.

[0178] (Step S1202) The delivery support unit 337 configures work information, which is information for identifying a product to be delivered to a user and is information for a worker to package the product to be delivered to a user. The work information includes, for example, one or more types of information among a course identifier, one or more product identifiers, and image identification information.

[0179] (Step S1203) The delivery support unit 337 transmits the work information constructed in step S1202 to the worker's terminal (not shown). The process returns to the upper level process. The work information is received and output by the worker's terminal. As a result, the worker looks at the work information, selects and acquires one or more products that are to be delivered to the user and that display an image of the event, and prepares for delivery.

[0180] From the above description, it can be said that the delivery support system A realizes the following delivery support method, which includes an event information preparation step, a medium preparation step, a product creation step, and a product delivery step.

[0181] The event information preparation step is a step of preparing event information for selling products on which images related to the event are printed. The event information preparation step includes an image reception substep of receiving one or more images related to the event, and an image storage substep of storing the one or more images in association with an event identifier of the event.

[0182] The medium preparation step is a step of preparing the medium 1 to be sold to users. Such medium 1 is usually sold at an event venue to users who have participated in the event. The medium preparation step includes a medium creation substep of acquiring an event identifier and a unique medium identifier, and creating one or more pieces of media having the event identifier and the medium identifier.

[0183] The product creation step is a step of supporting the creation of a product to be delivered to a user. The product creation step includes a printing sub-step of acquiring content including one or more images corresponding to the event identifier and printing the one or more contents on a print medium, and an attaching sub-step of attaching the one or more print media to a product container. The attaching sub-step may be performed manually.

[0184] The product delivery step is a step of supporting delivery of products to a user. The product delivery step includes a request receiving sub-step of receiving a delivery request having an event identifier and a user identifier for identifying the user from the user terminal 2, a user information acquisition sub-step of acquiring user information having the user's address corresponding to the user identifier included in the delivery request, and a user information output sub-step of outputting the user information.

[0185] A specific example of the operation of the delivery support system A in this embodiment will be described below.

[0186] The product management unit 311 of the delivery support device 3 stores a product management table shown in FIG. 13. The product management table is product information for beverages sold at the event. The product management table here is a table that manages information related to products sold at the event "Concert A." In other words, the product management table corresponds to an event identifier, for example. The product management table has three records having an "ID," "product identifier," and "product attribute value." The "product attribute value" here is the "maximum quantity" and "cost." The "maximum quantity" is the maximum quantity that can be sold for each product. The "ID" is information that identifies the records in the table.

[0187] The specific information management unit 312 stores the specific information management table of FIG. 14. The specific information management table here is a table that manages image specific information for the event "Concert A." The specific information management table corresponds to an event identifier, for example. The specific information management table is a table that manages image specific information for each course. The specific information management table manages two or more records having an "ID," "course identifier," and "image specific information." The "image specific information" here has one or two or more image identifiers.

[0188] The event management unit 313 stores the event management table of Fig. 15. The event management table is a table that manages event information and one or more images related to an event. The event management table manages one or more records having an "ID", "event identifier", "event information", and "image information". "Event information" has an "event name", "date", "time period", and "location". "Image information" has an "image identifier" and an "image".

[0189] Each record in the event management table in Fig. 15 is information stored in the event management table by the event information preparation process in Fig. 5. Each image in the event management table in Fig. 15 is a variety of photographs taken during a concert by the band "Group G." Each photograph is associated with an event identifier and an image identifier, transmitted to the delivery support device 3, and stored in the event management table by the image storage unit 332 of the delivery support device 3.

[0190] The media management unit 314 stores the media management table of Fig. 16. The media management table is a table that manages one or more media identifiers for each event. In other words, the media management table is a table that manages media 1 that are scheduled to be sold or have been sold for each event. The media identifier here is a serial code. The serial code, such as "SC1" or "SC2", is, for example, a numeric string of a predetermined number of digits.

[0191] The medium identifier of each record in the medium management table in FIG. 16 is information stored in the medium management table by the medium preparation process in FIG. 6. FIG. 17 shows an example of the medium 1 created by the medium preparation process in FIG. 6. Reference numeral 1701 in FIG. 17 is a medium identifier, which is a 12-digit serial code in this case. Reference numeral 1702 is a two-dimensional code in which an event identifier is embedded. The event identifier here is a URL. The URL specifies a web page to be sent to the user terminal 2 when a delivery request corresponding to an event is received. The web page is a page on which a user inputs a delivery request and sends the delivery request to the delivery support device 3. The medium 1 in FIG. 17 is, for example, a paper card.

[0192] The user management unit 315 stores a user management table as shown in FIG. 18. The user management table is a table that manages one or more pieces of user information. The user management table manages one or more records that have an "ID," "membership number," and "user information." The "user information" has "name," "postal code," "address," and "telephone number." The "membership number" is a user identifier. The user management table here is a table that manages members of the fan club of "Group G," a band that will be performing an event called Concert A.

[0193] In the above situation, the following two specific examples will be described. Specific example 1 is a case where a user purchases medium 1 (FIG. 17) at an event venue. Medium 1 is used to request delivery of a set of drinks. Specific example 2 is a case where a user who is a member of the fan club of the band "Group G" but was unable to attend the event uses his / her fan club membership number to request delivery of a product.

[0194] (Example 1) Assume that user U attends concert A of the band "Group G" and wants a drink set with an image of Group G printed on it at the concert venue as a memento of concert A, so purchases medium 1 of FIG.

[0195] Assume that after returning home, user U reads the two-dimensional code 1702 on medium 1 (FIG. 17) with his / her user terminal 2. As a result, the user terminal 2 accesses the delivery support device 3 using the URL embedded in the two-dimensional code 1702, receives screen information for making a delivery request from the delivery support device 3, configures a screen using the screen information, and outputs the screen. An example of such a screen is shown in FIG. 19.

[0196] It is assumed that the user inputs information into each field of the screen (FIG. 19) output to the user terminal 2 and selects the "Apply" button 1903. The user terminal 2 then accepts the delivery request and transmits the delivery request to the delivery support device 3. Here, it is assumed that the transmitted delivery request is "<event identifier>URL1 <medium identifier>XXXX···· <gender>1 <age>38 <email address>abc@X.jp <name>Yamada X-man <zip code>1004567 <address>Tokyo···· <telephone number>08098765432 <product identifier>Melon flavor <course identifier>C1". In other words, it is assumed that the user U inputs "Melon flavor" into field 1901 and "C1" into field 1902.

[0197] Next, the request receiving unit 322 of the delivery support device 3 receives the delivery request from the user terminal 2.

[0198] Next, the authentication unit 334 performs authentication processing as follows. That is, the authentication unit 334 obtains "<event identifier>URL1 <medium identifier>XXXX..." contained in the delivery request. Next, the authentication unit 334 determines that the pair of the event identifier and medium identifier exists in the event management table (FIG. 16), and obtains the result "authentication permitted."

[0199] Next, the processing unit 33 performs the product creation process according to the flowchart of FIG. 8 as follows. That is, the event identifier acquisition unit 333 acquires the event identifier "URL1" that the delivery request has. Next, the event identifier acquisition unit 333 acquires the event information "<Event name> Concert A <Date> August 10, 2023 <Time period> 17:00-20:00 <Location> Dome X" that is paired with the event identifier "URL1" from the event management table (FIG. 15). In addition, the user information acquisition unit 335 acquires the user information "<Name> Yamada X-o <Postal code> 1004567 <Address> Tokyo ···· <Telephone number> 08098765432" that the received delivery request has. Here, the user information acquired may be only the information necessary for the delivery of the product. Next, the print support unit 336 acquires the medium identifier "XXXX····" that the received delivery request has. Next, the printing support unit 336 acquires the route identifier "C1" of the received delivery request. Next, the printing support unit 336 acquires the image identification information "Everyone in Group, Member A, Member B, ..." that pairs with the route identifier "C1" from the identification information management table (FIG. 14). Here, it is assumed that the printing support unit 336 acquires the image identifiers of 12 images from the identification information management table (FIG. 14).

[0200] Next, the printing support unit 336 composes a content including the image, event information, user information, and a medium identifier for each of the one or more acquired images. That is, the printing support unit 336 composes 12 contents, each of which has a different image. Then, the printing support unit 336 prints each of the 12 contents on a separate printing medium. It is assumed that the printing medium is a label, which is a sticker.

[0201] Next, the processing unit 33 acquires the product identifier "Melon flavor" contained in the received delivery request. Next, the processing unit 33 transmits the product identifier "Melon flavor" to a worker's terminal (not shown).

[0202] Next, the worker's terminal receives and outputs the product identifier "Melon flavor." The worker then removes 12 unlabeled beverage cans containing "Melon flavor" beverage from the shelf. The worker then attaches a label, which is a different print medium, to each of the 12 cans. The worker then places the 12 labeled beverage cans into a box for delivery, completing the product to be delivered. An example of such a product is shown in FIG. 20.

[0203] Next, the delivery support unit 337 performs product delivery processing according to the flowchart of FIG. 9 as follows. That is, the delivery support unit 337 acquires user information "<Name> Yamada X-man <Postal Code> 1004567 <Address> Tokyo··· <Phone Number> 08098765432". Next, the delivery support unit 337 acquires delivery time information that is dated two days after today's date. Next, the delivery support unit 337 composes delivery information that includes the user information "<Name> Yamada X-man <Postal Code> 1004567 <Address> Tokyo··· <Phone Number> 08098765432" and the delivery time information. Next, the delivery support unit 337 prints the delivery information on a delivery slip.

[0204] Then, the worker packages the created product (FIG. 20) and attaches a delivery slip to deliver the drink set to user U. The worker then hands the product over to a delivery company. In this way, the product related to the event is delivered to user U in response to the delivery request from user U.

[0205] (Example 2) Next, assume that a user "Tanaka A. Mr.," who was unable to attend the concert A as a privilege for being a member of the fan club of group G, accesses a web page for members of the fan club corresponding to the event "concert A." Then, the web page is displayed on the user terminal 2 of Tanaka A. Mr. Tanaka.

[0206] Then, Tanaka A enters the member password "10001", the product identifier "Melon flavor", and the course identifier "C1" on the web page and selects the "Order" button. Then, Tanaka A's user terminal 2 transmits a delivery request "<member password>10001 <product identifier>Melon flavor <course identifier>C1" to the delivery support device 3.

[0207] Next, the request receiving unit 322 of the delivery support device 3 receives the delivery request from the user terminal 2 of Mr. Tanaka A.

[0208] Next, the authentication unit 334 performs authentication processing as follows: That is, the authentication unit 334 detects that "<member password>10001" contained in the delivery request exists in the user management table (FIG. 18), and as a result, acquires "authentication permission."

[0209] Next, the processing unit 33 performs a product creation process according to the flowchart in Fig. 8. Also, the delivery support unit 337 performs a product delivery process according to the flowchart in Fig. 9. The delivery support unit 337 obtains user information paired with the member code "10001" from the user management table (Fig. 18), and uses the user information to create a delivery slip for delivering the product to Tanaka A.

[0210] As a result of the above process, the product shown in Figure 20 is delivered to Mr. Tanaka A.

[0211] As described above, according to the present embodiment, a platform that supports the delivery of commemorative products for an event to users can be provided. It is preferable that such users are users who have participated in the event, but there may be cases where such users are users who have not participated in the event.

[0212] Furthermore, according to the present embodiment, a platform can be provided that supports the delivery of a merchandise commemorating participation in an event to a user who purchased a medium 1 sold at the event venue.

[0213] Furthermore, according to this embodiment, it is possible to provide a platform that supports the delivery of two or more products printed with different contents related to an event to a user.

[0214] Furthermore, according to this embodiment, the user can select the product to be delivered.

[0215] Furthermore, according to this embodiment, the user can select a course regarding the image to be printed on the product container.

[0216] Furthermore, according to this embodiment, by authenticating the medium, the product can be delivered only to an authorized user.

[0217] The processes in the embodiment may be realized by software. This software may be distributed by software download or the like. This software may also be recorded on a recording medium such as a CD-ROM and distributed. This also applies to the other embodiments in this specification. The software that realizes the delivery support device 3 in the present embodiment is a program such as the following. In other words, this program causes a computer to function as an event identifier acquisition unit that acquires an event identifier that identifies an event; a printing support unit that refers to an event management unit in which event information including images related to the event is stored in correspondence with one or more event identifiers, acquires content including an image included in the event information corresponding to the event identifier acquired by the event identifier acquisition unit, prints the content on a print medium, and provides printing support, which is support for acquiring the print medium; a request receiving unit that receives a delivery request having an event identifier and a user identifier that identifies the user from a user terminal; a user information acquisition unit that corresponds to the user identifier included in the delivery request and acquires user information having the user's address; and a delivery support unit that provides delivery support, which is support for delivering one or more products having print media corresponding to the event identifier contained in the delivery request attached to their product containers, to a location indicated by an address corresponding to the user information acquired by the user information acquisition unit.

[0218] The program may be executed by a single computer or a plurality of computers. That is, the program may be executed by a centralized processing or a distributed processing.

[0219] Furthermore, in each of the above embodiments, it goes without saying that two or more communication means present in one device may be physically realized by one medium.

[0220] In each of the above embodiments, each process may be realized by centralized processing in a single device, or may be realized by distributed processing in a plurality of devices.

[0221] The present invention is not limited to the above-described embodiment, and various modifications are possible, and it goes without saying that these modifications are also included within the scope of the present invention. [Industrial Applicability]

[0222] As described above, the delivery support device 3 according to the present invention has the effect of being able to provide a platform for supporting the delivery of commemorative products for an event to users, and is useful as a server or the like that realizes the platform. [Explanation of symbols]

[0223] 1 medium 2. User terminal 3 Delivery support device 4 Printing device 21 Terminal storage section 22 Terminal Reception 23 Terminal Processing Section 24 Terminal transmitter 25 Terminal receiving section 26 Terminal Output Section 31 Storage area 32 Receiving section 33 Processing section 34 Transmitter 311 Product Management Department 312 Specific Information Management Department 313 Event Management Department 314 Media Management Department 315 User Management Department 321 Image receiving unit 322 Request Reception Department 331 Media Creation Department 332 Image Storage Unit 333 Event Identifier Acquisition Unit 334 Authentication Department 335 User Information Acquisition Unit 336 Printing Support Department 337 Delivery Support Department

Claims

1. an event identifier acquisition unit that acquires an event identifier that identifies an event; a printing support unit that refers to an event management unit in which event information including images related to an event is stored in association with one or more event identifiers, acquires content including an image included in the event information corresponding to the event identifier acquired by the event identifier acquisition unit, prints the content on a print medium, and performs printing support to acquire the print medium; a request receiving unit that receives a delivery request having an event identifier and a user identifier that identifies the user from a user terminal; a user information acquisition unit that acquires user information having a user address corresponding to the user identifier included in the delivery request; and a delivery support unit that provides delivery support, i.e., support for delivering one or more products having a printed medium corresponding to the event identifier contained in the delivery request attached to a product container to a location indicated by an address corresponding to the user information acquired by the user information acquisition unit.

2. The delivery support unit includes: The delivery assistance device according to claim 1 , wherein the delivery assistance is provided only to users who are participants in the event.

3. 2. The delivery support device according to claim 1, wherein the event identifier included in the delivery request is information included in a medium sold to the user.

4. The delivery support device according to claim 3 , wherein the medium is a medium sold at a venue of an event in which the user participates.

5. The event information corresponding to one event identifier includes two or more images, The printing support unit includes: With reference to the event management unit, acquire content including two or more images included in the event information corresponding to the event identifier acquired by the event identifier acquisition unit, print each of the two or more contents on a print medium, and perform printing support, which is support for acquiring two or more print media; The delivery support unit includes: A delivery support device as described in any one of claims 1 to 4, which provides delivery support, i.e. support for delivering two or more products having the two or more printed media attached to product containers to a location indicated by the address corresponding to the user information acquired by the user information acquisition unit.

6. The delivery request includes a product identifier that identifies a product; The printing support unit includes: A delivery support device as described in any one of claims 1 to 5, which refers to a product management unit in which product information regarding products that pair with one or more product identifiers is stored, obtains product information regarding products identified by the product identifiers held by the delivery request, obtains content that also contains the product information, prints the content on a print medium, and provides printing support, which is support for obtaining the print medium.

7. the delivery request has a course identifier that identifies a course related to the content; The printing support unit includes: A delivery support device as described in any one of claims 1 to 5, which performs printing support by referring to a specific information management unit in which image specific information that identifies one or more images is stored in correspondence with each of two or more course identifiers, acquires the course identifier held by the delivery request, acquires content having one or more images identified by the image specific information that pairs with the course identifier, prints each of the one or more contents on a print medium, and provides support for acquiring one or more print media.

8. the medium sold to the user includes a medium identifier that is unique to that medium; the delivery request includes a media identifier; and an authentication unit that refers to a media management unit that manages one or more media identifiers corresponding to each of the one or more event identifiers, and determines whether the event identifier and the media identifier included in the delivery request received by the request receiving unit correspond to each other, The delivery support unit includes:

4. The delivery assistance device according to claim 3, wherein when the authentication unit determines that the event identifier and the medium identifier do not correspond to each other, the delivery assistance is not performed.

9. A delivery assistance system comprising: one or more media including an event identifier; the delivery assistance device according to claim 1; and one or more printers that print onto the print media.

10. A delivery support method including an event information preparation step, a medium preparation step, a product creation step, and a product delivery step, The event information preparation step includes: an image receiving substep of receiving one or more images associated with the event; and storing said one or more images in association with an event identifier of said event; The medium preparing step includes: a media creation substep of obtaining an event identifier and a unique media identifier, and creating one or more pieces of media having the event identifier and the unique media identifier; The product creation step includes: a printing substep of acquiring content including one or more images corresponding to the event identifier and printing the one or more contents on a print medium; a sub-step of attaching each of the one or more print media to a product container; The product delivery step includes: a request receiving sub-step of receiving a delivery request having an event identifier and a user identifier for identifying the user from the user terminal; a user information acquisition sub-step of acquiring user information having a user address corresponding to the user identifier included in the delivery request; A delivery assistance method comprising a user information output substep of outputting the user information.

11. A delivery support method implemented by an event identifier acquisition unit, a print support unit, a request receiving unit, a user information acquisition unit, and a delivery support unit, an event identifier acquisition step in which the event identifier acquisition unit acquires an event identifier that identifies an event; a printing support step in which the printing support unit refers to an event management unit in which event information including an image related to an event is stored in association with each of one or more event identifiers, acquires content including an image included in the event information corresponding to the event identifier acquired by the event identifier acquisition unit, prints the content on a print medium, and performs printing support, which is support for acquiring the print medium; a request receiving step in which the request receiving unit receives a delivery request having an event identifier and a user identifier for identifying the user from a user terminal; a user information acquisition step in which the user information acquisition unit acquires user information having a user address corresponding to the user identifier included in the delivery request; and a delivery support step in which the delivery support unit provides delivery support to deliver one or more products having a printed medium corresponding to the event identifier contained in the delivery request attached to a product container to a location indicated by an address corresponding to the user information acquired by the user information acquisition unit.

12. Computer, an event identifier acquisition unit that acquires an event identifier that identifies an event; a printing support unit that refers to an event management unit in which event information including images related to an event is stored in association with one or more event identifiers, acquires content including an image included in the event information corresponding to the event identifier acquired by the event identifier acquisition unit, prints the content on a print medium, and performs printing support to acquire the print medium; a request receiving unit that receives a delivery request having an event identifier and a user identifier that identifies the user from a user terminal; a user information acquisition unit that acquires user information having a user address corresponding to the user identifier included in the delivery request; A program for functioning as a delivery support unit that provides delivery support, i.e., support for delivering one or more products having a printed medium corresponding to the event identifier contained in the delivery request attached to a product container to a location indicated by an address corresponding to the user information acquired by the user information acquisition unit.

Images