Delivery assistance device and delivery assistance method

Abstract

[Problem] There has been an inability to assist in delivering, to a user, a commodity which serves as a memento of an event. [Solution] A delivery assistance device 3 includes: a printing assistance unit 336 that, by referring to an event management unit 313 for storing event information including an image related to an event in association with at least one event identifier, performs printing assistance in printing, on a printing medium, content including an image included in event information corresponding to an acquired event identifier; a user information acquisition unit 335 that acquires user information which includes an address and corresponds to a user identifier included in a delivery request received from a user terminal 2; and a delivery assistance unit 337 that performs delivery assistance in delivering, to a place indicated by the address acquired by the user information acquisition unit 335, at least one commodity which has a printing medium corresponding to the event identifier attached to a commodity container thereof. With said delivery assistance device, it is possible to provide a platform for assisting in delivering, to a user, a commodity which serves as a memento of an event.

Description

Delivery support device and delivery support method

[0001] The present invention relates to a delivery support device or the like that realizes a system that allows users to purchase products on which images related to an event are printed.

[0002] There has been a conventional product sales system that can more reliably forecast sales of products 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 payment processing unit that processes payments 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 quantity 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 payment processing in the payment processing unit is completed.

[0003] Japanese Patent Application Laid-Open No. 2019-21059

[0004] However, the prior art has not been able to support the delivery of commemorative items for an event to users.

[0005] The delivery support device of the first invention is a delivery support device that includes 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, to acquire content including images 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, each having a print medium corresponding to the event identifier included in the delivery request attached to its product container, to a location indicated by the address corresponding to the user information acquired by the user information acquisition unit.

[0006] This configuration provides a platform that supports the delivery of merchandise that will commemorate an event to users. The delivery support device of the second invention differs from the first invention in that the delivery support unit provides delivery support only to users who are event participants. This configuration provides a platform that supports the delivery of merchandise that will be a memento of an event to users.

[0007] Furthermore, the delivery support device of the third invention differs from the first invention in that the event identifier included in the delivery request is information included in a medium sold to the user.

[0008] This configuration makes it possible to provide a platform that supports the delivery of commemorative products to users for an event.

[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 a medium sold at the venue of an event in which the user has participated.

[0010] This configuration provides a platform that assists users who purchase media sold at the event venue in receiving 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 in which, compared to any one of the first to fourth inventions, 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, prints each of the two or more contents on a print medium, and performs printing support, which is support for acquiring the two or more print media, and the delivery support unit performs delivery support, which is support for delivering two or more products each having two or more print media attached to product containers, to a location indicated by an address corresponding to the user information acquired by the user information acquisition unit.

[0012] This configuration provides a platform that supports the delivery of two or more products to a user, each printed with different content related to an event.

[0013] Furthermore, 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 the delivery request has a product identifier that identifies the product, and the printing support unit refers to a product management unit in which product information relating to products paired with one or more product identifiers is stored, acquires product information relating to 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 provides printing support, which is support for acquiring the print medium.

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

[0015] Furthermore, the delivery support device of the seventh invention is a delivery support device that, compared to any one of the first to sixth inventions, provides printing support in which the delivery request has a course identifier that identifies a course related to the content, and the printing support unit refers to a specific information management unit in which image specific information that identifies one or more images is stored in association 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 paired with the course identifier, prints each of the one or more contents on a print medium, and provides printing support in which the one or more print media are acquired.

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

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

[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 containing 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 supports the delivery of commemorative products to users for an event.

[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, wherein 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 the event identifier of the event, the medium preparation step comprises a medium creation substep of acquiring the event identifier and a unique medium identifier, and creating one or more media having the event identifier and the 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 printed media, and an affixing substep of attaching the one or more printed media to product containers, 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, which corresponds 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 supports the delivery of commemorative products to users for an event.

[0023] The delivery support device according to the present invention can provide a platform that supports the delivery of commemorative products for an event to users.

[0024] FIG. 1 is a conceptual diagram of a delivery support system A in the first embodiment; FIG. 2 is a block diagram of the delivery support device 3; FIG. 3 is a flowchart illustrating a first operation example of the delivery support device 3; FIG. 4 is a flowchart illustrating an example of an event information preparation process; FIG. 5 is a flowchart illustrating an example of a medium preparation process; FIG. 6 is a flowchart illustrating an example of an authentication process; FIG. 7 is a flowchart illustrating an example of a product creation process; FIG. 8 is a flowchart illustrating an example of a product delivery process; FIG. 9 is a flowchart illustrating a second operation example of the delivery support device 3; FIG. 10 is a flowchart illustrating an example of an event product creation process;

[0025] Hereinafter, embodiments 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 will be described that realizes a mechanism for delivering products printed with images related to an event to users involved in the event. Note that users involved in an event are usually users who participated in the event. However, users involved in an event may also include members of a fan club of a person who is organizing 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 a medium sold to a user at an event venue from the 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, we will describe a delivery support system that supports printing two or more pieces of content, each containing two or more images related to an event, onto a print medium, and delivers two or more products having the two or more print media to a user.

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

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

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

[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 on information Z, etc., and it is sufficient if information Z can be accessed.

[0034] 1 is a conceptual diagram of a delivery support system A according to this 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 printing devices 4.

[0035] Medium 1 indicates the right for a user to obtain a product. Medium 1 is, for example, paper, but it may also 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 also 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 is held. Examples of event venues include sports venues such as baseball stadiums, soccer fields, and golf courses, concert venues, play venues, theme parks, exhibition venues, art galleries, museums, observation decks, parks, and tourist facilities. However, an event venue can be any place where an event is held, and the type of event is not important.

[0038] Incidentally, events can also be called leisure activities, for example. Leisure is entertainment. Leisure can be broadly interpreted to include sightseeing, recreation, etc. Furthermore, leisure activities can be, for example, watching sports, concerts, plays, playing sports, etc., but the type of leisure is not important.

[0039] A medium identifier is unique information that identifies 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 the person who purchased the medium 1, but may also be a person who has received the medium 1 from the person who purchased it. The user terminal 2 may be, for example, a personal computer, a tablet terminal, or a smartphone, but the type is not important.

[0041] The delivery support device 3 is a device that supports the process of delivering at least one or more products to a user. The delivery support device 3 is typically 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. Preferably, 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 the contents described below on a printing medium described below. The printing medium is preferably a sticker to be attached to a product delivered to a user, but it can also be paper or other materials, and the material, etc., is not important. The printing medium can also be a product container. A product container is a container that contains a product. The product can be, for example, food, but this is not important. The food can be, for example, a beverage, but this is not important. The container is, for example, a can, but it can also be made of paper, and the means for realizing it is not important.

[0043] 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 26 .

[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] A user identifier is information that identifies a user. A user identifier is, for example, an address, a telephone number, or a name. A user identifier may also be, for example, a medium identifier. A 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 includes an event identifier and a user identifier. A delivery request includes, for example, one or more product identifiers. A delivery request includes, for example, a course identifier, which will be described later. It is preferable that a delivery request includes a medium identifier. The medium identifier here is, for example, a serial number or serial code. Note that the two or more pieces of information that make up a delivery request do not need to be accepted simultaneously, but 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 may be, 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 URL. When the event identifier is a URI or URL, the web page that can be identified by the URI or URL is usually a web page for requesting delivery of a product for the event, or a web page that can lead 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 the product selected by the user. The product identifier is information that indicates, for example, the type of product (e.g., "coffee," "water," "lemon flavor," "peach flavor").

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

[0054] The terminal receiving unit 22 acquires a delivery request by, for example, reading a code in which an event identifier is embedded. The terminal receiving unit 22 accepts a delivery request entered on a screen displayed using a webpage obtained using a URL obtained by reading the code in which the event identifier is embedded. The terminal receiving unit 22 accepts, for example, an event identifier entered by a user. The terminal receiving unit 22 accepts, for example, user information entered 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 processes, such as changing instructions, information, etc. received by the terminal reception unit 22 into instructions, information, etc. with a structure to be transmitted, changing the structure of information received by the terminal reception unit 25 to an output structure, and creating a screen from screen information received by the terminal reception unit 25.

[0058] The terminal transmitting unit 24 transmits various types of information, instructions, etc. The various types of information, instructions, etc. are, for example, delivery requests. When a delivery request includes two or more pieces of information, the terminal transmitting 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 types of information. For example, the terminal receiving unit 25 receives various types of information from the delivery support device 3. The various types of information include, for example, screen information and information indicating that a delivery request has been accepted.

[0060] The terminal output unit 26 outputs various types of information. The various types of information are, for example, information received by the terminal receiving unit 25 and modified to be output by the terminal processing unit 23, such as a screen or information indicating that a delivery request has been received.

[0061] Here, output is a concept that includes displaying 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 processing results to other processing devices or other programs.

[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 (described later), image specification information (described later), event information (described later), medium identifiers, and user information.

[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. 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. A product identifier is information that identifies a product. A product identifier is, for example, a product ID, a JAN code, a product name, or a product type.

[0064] The identification information management unit 312 stores two or more pieces of image identification information. 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 the 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 the group" performing an event (e.g., a concert), or "Mr. A" indicating a specific member of the 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. Event attribute values ​​include, for example, the event name, the date the event was held, the time period the event was held, and the location where the event was held. It is preferable that one or more images related to the event are associated with the event information. An image related to the event is, for example, a photograph taken at the event, but it may also be a video taken at the event, an illustration of the event, etc. An image is associated with, for example, an image identifier. The image identifier is information that identifies the image. It is preferable that the event information is associated with the event identifier.

[0067] The media management unit 314 stores one or more media identifiers corresponding to one or more event identifiers. The media identifiers are, for example, serial numbers. When a media identifier corresponds to an event identifier, the media 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 typically has one or more user attribute values. User attribute values ​​are, for example, name, address, and telephone number. It is preferable that the user information includes information indicating the delivery address of a product to the user. The user information may also 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 includes, for example, images, instructions to prepare event information, instructions to prepare media, delivery requests, and instructions to create products. The receiving unit 32 receives, for example, instructions to prepare event information, instructions to prepare media, and instructions to create products 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 to mean any person regardless of their 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 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 media 1 are typically items to be sold to users.

[0073] The product creation instruction is an instruction to create a product, and 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 images corresponding to one or more pieces of information selected from an event identifier, one or more event attribute values, and an image identifier. For example, the image receiving unit 321 receives images (photos or videos) taken by a camera (not shown). For example, the image receiving unit 321 receives images taken by a camera (not shown) from the camera. It is preferable that the images taken by the camera are images of the event taken 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 simultaneously. It is preferable that the user terminal 2 is a terminal of a user who is a participant in the event.

[0076] The processing unit 33 performs various processes, such as those 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, for example, acquires 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 the acquired medium identifier, code, and additional information on, for example, 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] 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 most recent 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 associates each of the one or more images received by the image receiving unit 321 with an event identifier and stores them in the event management unit 313. It is preferable that the image storage unit 332 associates each of the one or more images received by the image receiving unit 321 with an image identifier and stores them in the event management unit 313.

[0081] The event identifier acquisition unit 333 acquires an event identifier that identifies an event. For example, the event identifier acquisition unit 333 acquires the event identifier included in the delivery request received by the request receiving unit 322. For example, the event identifier acquisition unit 333 acquires the 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 determines whether the event identifier included in the delivery request received by the request receiving unit 322 corresponds to the medium identifier included in the delivery request. The authentication unit 334 then obtains the determination result (e.g., "Authentication Approved" or "Authentication Not Approved"). The event identifier and medium identifier included in the delivery request are preferably information included in the medium 1 sold to the user. The authentication unit 334 may also determine whether 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 the event identifier included in the delivery request received by the request receiving unit 322 is included in the event identifiers that pair with the user identifier corresponding to the delivery request.

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

[0084] The printing support unit 336 performs printing support. Printing support is a process for acquiring a print medium containing content. Content is information to be printed on the print medium. Content typically includes one image. Content may include two or more images. Content includes, for example, one or more of the following information: user information, artist name, date, time period, venue name, and serial number. 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 then attached to, for example, a product container.

[0086] The printing support unit 336, for example, refers to the event management unit 313 and acquires 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 each of the two or more content items on a print medium. As a result, two or more print media on which different content items are printed are acquired.

[0087] The printing support unit 336, for example, refers to the product management unit 311, acquires product information about 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, references the identification information management unit 312 to acquire the route identifier included in the delivery request, and acquires content having one or more images identified by the image identification information paired with the route identifier. Next, the printing support unit 336 prints each of 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 receiving a delivery request including an event identifier 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 typically 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 boxing one or more products may be performed in order to deliver the products to a user. 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 provide the above-described 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, each having a print medium 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 the event. It is preferable that the delivery support unit 337 does not provide delivery support if, 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. If the user is not a user who participated in an event, it is preferable that a screen for sending a delivery request corresponding to the event is not output on the user's terminal device 2.

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

[0094] Delivery support is, for example, processing to output information, including an address and a name, contained in user information. Here, output is a concept that includes, for example, displaying on a display, projecting using a projector, printing using a printer, outputting sound, transmitting to an external device, storing on a recording medium, and transferring processing results to another processing device, another program, etc. In other words, delivery support is, for example, processing to print information, including an address and a name, contained in user information, on a delivery slip. Delivery support is, for example, processing to display information, including an address and a name, contained in user information, on a display that is viewed by a worker filling out the delivery slip. Delivery support is, for example, processing to print information, including an address and a name, contained in user information, on paper (e.g., a label or sticker) that can be 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. If the delivery support unit 337 does not provide delivery support, it is preferable that the printing support unit 336 does not provide printing 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 include, for example, information indicating that the product delivery request has been accepted, and an error message. The error message is information indicating 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 non-volatile recording media, but can also be realized using 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 input 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 device 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 typically be realized by a processor, memory, or the like. The processing procedures of the device processing unit 23, etc., are typically realized by software, and the software is recorded on a recording medium such as a ROM. However, they may also be realized by hardware (dedicated circuitry). The processor may be a CPU, MPU, GPU, or the like, and the type does not matter.

[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 or the like may be realized by driver software for an output device, or a combination of driver software for an output device and the 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 determines whether or not an instruction to prepare for event information has been received from the operator terminal. If the instruction to prepare for event information has been received, the process proceeds to step S402; if not, the process proceeds to step S403.

[0106] (Step S402) The processing unit 33 performs an event information preparation process. The process returns 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 in FIG. 5.

[0107] (Step S403) The receiving unit 32 determines 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; 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 in FIG. 6.

[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 the received delivery request is valid. An example of the authentication processing will be described with reference to the flowchart in FIG. 7.

[0111] (Step S407) The processing unit 33 determines whether the result of the authentication process in step S406 was “authentication permitted” or “authentication not permitted.” If the result is “authentication permitted,” the processing unit 33 proceeds to step S408, and if the result is “authentication not permitted,” the processing unit 33 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 in FIG. 8. Note that the product creation process usually includes printing support.

[0113] (Step S409) The delivery support unit 337 performs product delivery processing. Return to step S401. The product delivery processing is processing for supporting the delivery of products to users. An example of the product delivery processing will be described using the flowchart in FIG. 9. Note that the product delivery processing includes delivery support.

[0114] (Step S410) The processing unit 33 receives an error message indicating that authentication was denied. 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 occurs 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 of FIG.

[0117] (Step S501) The processing unit 33 acquires an event identifier that is unique to the event. For example, the processing unit 33 acquires the event identifier included in the received preparation instruction. For example, the processing unit 33 generates the 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 generates event information having an event identifier and one or more event attribute values, and stores the event information in the event management unit 313.

[0120] (Step S504) The image receiving unit 321 determines whether or not an image has been received from a camera or the like (not shown). If an image has been received, the process proceeds to step S505; if not, 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 determines whether or not to end preparation of the event information. If the preparation of the event information is to be ended, the processing unit 33 returns to the upper processing, and if not, the processing unit 33 returns to step S504. Preparation of the event information may be ended when information indicating the end of the event is received, when a predetermined time arrives, or when an instruction to end preparation of the event information is received from the operator terminal. However, any condition may be used 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 production unit 331 acquires an event identifier corresponding to a medium preparation instruction.

[0125] (Step S602) The medium creating 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 from the event management unit 313.

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

[0129] (Step S606) The medium creation unit 331 determines 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; 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 medium 1 to be created is determined in advance. The number of medium 1 to be created is the planned number of medium 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 creates 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 have 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 associates the medium identifier acquired in step S607 with the event identifier and stores them in the medium management unit 314. The medium creation unit 331 increments the counter i 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 determines 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; 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 of FIG.

[0142] (Step S801) The event identifier acquisition unit 333 acquires an event identifier corresponding to the received delivery request, and acquires event information corresponding to the event identifier from the 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 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 creates content including the one or more images acquired in step S809. Preferably, the 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 created 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 included 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 process. The output here is, for example, sent to a terminal (not shown) of a worker who affixes a print medium (e.g., a sticker) to the product.

[0156] In the flowchart of FIG. 8, the processes of 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 of 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 that 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 including 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 the product to be delivered to the user.

[0162] Next, a second operation example of the delivery support device 3 will be described using the flowchart of FIG. 10. In the flowchart of FIG. 10, the same steps as those in the flowchart of FIG. 4 will not be described again. The second operation example is a case where a product is produced before receiving a delivery request. Note that the production of the product here does not have to include packaging the product.

[0163] (Step S1001) The receiving unit 32 determines 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 this event product creation processing will be described with reference to the flowchart in FIG. 11.

[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 in FIG.

[0166] In the flowchart of FIG. 10, the process ends when the power is turned off or an interrupt occurs 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, and 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 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 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 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 to be used for the ith print medium, which are among the one or more images acquired in step S1106.

[0173] (Step S1106) The print support unit 336 creates content including one or more images acquired in step S1109. The content preferably includes event information. 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 printing medium. The printing is performed by the printing device 4. The printing support unit 336 typically prints the content created in step S1110 onto a printing medium in a predetermined number or in the number included in the product creation 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 of Fig. 12. In the flowchart of Fig. 12, the description of the same steps as those in the flowchart of Fig. 8 or 9 will be omitted.

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

[0178] (Step S1202) The delivery support unit 337 generates work information, which is information for identifying the product to be delivered to the user and information for the worker to package the product to be delivered to the user. The work information includes, for example, one or more types of information from 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 processing. The work information is received and output by the worker's terminal. As a result, the worker views the work information, selects and acquires one or more products to be delivered to the user, which products 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: The delivery support method 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 pairs with the event identifier of the event.

[0182] The media preparation step is a step of preparing media 1 to be sold to users. Such media 1 are typically sold at an event venue to users who have participated in the event. The media preparation step includes a media creation substep of acquiring an event identifier and a unique media identifier, and creating one or more pieces of media each having the event identifier and the media 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 substep of acquiring content including one or more images corresponding to the event identifier and printing the one or more contents on print media, and an attaching substep of attaching the one or more print media to a product container. Note that the attaching substep 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 substep of receiving a delivery request having an event identifier and a user identifier that identifies the user from the user terminal 2, a user information obtaining substep of obtaining user information having the user's address that corresponds to the user identifier included in the delivery request, and a user information output substep 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 the product management table shown in FIG. 13. The product management table contains product information about beverages to be sold at the event. The product management table here is a table that manages information about products to be sold at the event "Concert A." In other words, the product management table corresponds to, for example, an event identifier. The product management table has three records, each having an "ID," "product identifier," and "product attribute value." The "product attribute value" here is "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 record 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, for example, an event identifier. 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 that have an "ID," "course identifier," and "image specific information." Here, the "image specific information" has one or two or more image identifiers.

[0188] The event management unit 313 stores the event management table shown in FIG. 15. The event management table is a table for managing event information and one or more images related to an event. The event management table manages one or more records each having an "ID," "event identifier," "event information," and "image information." The "event information" includes an "event name," "date," "time period," and "location." The "image information" includes 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 shown in 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. "SC １ "," SC ２ The serial code is, for example, a string of numbers with 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 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 with an event identifier embedded in it. 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 the 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 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 a "name," "postal code," "address," and "telephone number." The "membership number" is a user identifier. The user management table here is a table that manages the members of the fan club of the band "Group G" that will be performing the event Concert A.

[0193] In the above situation, the following two specific examples will be described. In specific example 1, a user purchases medium 1 (FIG. 17) at an event venue. Medium 1 is used to request delivery of a set of drinks. In specific example 2, 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) User U attends concert A by the band "Group G" and, at the concert venue, wants a drink set with an image of Group G printed on it as a memento of concert A, so he purchases medium 1 shown in Figure 17.

[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, user terminal 2 accesses delivery support device 3 using the URL embedded in the two-dimensional code 1702, receives screen information for making a delivery request from delivery support device 3, constructs 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 enters information in 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> URL 1 <Medium Identifier> XXXX... <Gender> 1 <Age> 38 <Email Address> abc@X.jp <Name> Yamada X-o <Postal Code> 1004567 <Address> Tokyo... <Telephone Number> 08098765432 <Product Identifier> Melon Flavor <Course Identifier> C1." That is, it is assumed that the user U enters "Melon Flavor" in field 1901 and "C1" in 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 acquires "<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 acquires 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" included in the delivery request. 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" 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-san <Postal Code> 1004567 <Address> Tokyo . . . <Phone Number> 08098765432" included in the received delivery request. Note that the acquired user information here need only be the information necessary for product delivery. Next, the printing support unit 336 acquires the medium identifier "XXXX . . . " included in the received delivery request. Next, the printing support unit 336 obtains the route identifier "C1" included in the received delivery request. Next, the printing support unit 336 obtains the image identification information "All members of the 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 obtains the image identifiers of 12 images from the identification information management table (FIG. 14).

[0200] Next, the printing support unit 336 creates 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 creates 12 pieces of content, each with a different image. The printing support unit 336 then prints each of the 12 pieces of content on a separate printing medium. It is assumed that the printing medium is a label, i.e., a sticker.

[0201] Next, the processing unit 33 acquires the product identifier "melon flavor" from the received delivery request, and then transmits the product identifier "melon flavor" to the 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 a 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 shipping box, completing the product for delivery. 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 in 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 dated two days after today's date. Next, the delivery support unit 337 creates delivery information including 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] The worker then packages the created product ( FIG. 20 ) and attaches a delivery slip to deliver the beverage set to user U. The worker then hands the product over to a delivery company. In this way, the event-related products are delivered to user U in response to the delivery request from user U.

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

[0206] Then, Tanaka A enters the member password "10001," the product identifier "melon flavor," and the course identifier "C1" into the web page and clicks the "Apply" button. Tanaka A's user terminal 2 then sends 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 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 obtains "authentication permission" as a result.

[0209] Next, the processing unit 33 performs product creation processing in accordance with the flowchart of Fig. 8. Furthermore, the delivery support unit 337 performs product delivery processing in accordance with the flowchart of Fig. 9. Furthermore, 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 processing, the product shown in FIG. 20 is delivered to Mr. Tanaka A.

[0211] As described above, according to this embodiment, the delivery support device 3 functions as a platform that supports the delivery of commemorative products for an event to users. While it is preferable that such users are users who participated in the event, there may also be cases where such users are users who did not participate in the event.

[0212] Furthermore, according to this embodiment, the delivery support device 3 functions as a platform that supports the delivery of commemorative products for participating in an event to users who purchased the medium 1 sold at the event venue.

[0213] Furthermore, according to this embodiment, the delivery support device 3 functions as a platform that supports the delivery of two or more products on which different contents related to an event are printed 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 delivery support device 3 can deliver the product 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 this embodiment is the following program. 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, corresponding to each of one or more event identifiers, to acquire content including images 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 from a user terminal, which has an event identifier and a user identifier that identifies the user; a user information acquisition unit that corresponds to the user identifier included in the delivery request and has the user's address; and a delivery support unit that provides delivery support, which is support for delivering one or more products, each having a print medium corresponding to the event identifier included in the delivery request attached to its product container, to a location indicated by the address corresponding to the user information acquired by the user information acquisition unit.

[0218] The computer that executes the program may be a single computer or a plurality of computers, that is, it may perform centralized processing or 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] Furthermore, 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.

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

Claims

1. 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 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, and performs printing support, which is support for printing the content on a print medium; a request receiving unit that receives a delivery request having an event identifier and a user identifier from a user terminal; a user information acquisition unit that acquires user information corresponding to the user identifier included in the delivery request, the user information having a user address; and a delivery support unit that performs delivery support, which is support for delivering one or more products having product containers attached with the print medium corresponding to the event identifier included in the delivery request, to a location indicated by the address included in the user information acquired by the user information acquisition unit.

2. The delivery assistance device according to claim 1, wherein the delivery assistance unit provides the delivery assistance only to users who are participants in the event.

3. 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 assistance device according to claim 3, wherein the medium is a medium sold at the venue of the event in which the user participates.

5. A delivery support device as described in claim 1, wherein the 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 performs printing support in the form of support for printing each of the two or more contents on a print medium, and the delivery support unit performs delivery support in the form of support for delivering two or more products having the two or more print media affixed to the product containers to a location indicated by the address contained in the user information acquired by the user information acquisition unit.

6. The delivery support device of claim 1, wherein the delivery request has a product identifier, and the printing support unit refers to a product management unit in which product information paired with one or more product identifiers is stored, obtains product information identified by the product identifier in the delivery request, obtains content that also has the product information, and provides printing support in the form of support for printing the content on a print medium.

7. A delivery support device as described in claim 1, wherein the delivery request has a course identifier that identifies a course related to the content, and the printing support unit refers to a specific information management unit in which image specific information that identifies one or more images in correspondence with each of two or more course identifiers is stored, acquires the course identifier held by the delivery request, acquires content having one or more images identified by the image specific information paired with the course identifier, and provides printing support in the form of support for printing each of the one or more contents on a print medium.

8. A delivery assistance device as described in claim 3, wherein the medium sold to the user includes a medium identifier unique to the medium, and the delivery request includes a media identifier, and further comprises an authentication unit that refers to a media management unit that manages one or more media identifiers corresponding to each of one or more event identifiers and determines whether the event identifier contained in the delivery request received by the request receiving unit corresponds to the media identifier, and the delivery assistance unit does not provide the delivery assistance if the authentication unit determines that the event identifier does not correspond to the media identifier.

9. A delivery support method comprising an event information preparation step, a medium preparation step, a product creation step, and a product delivery step, wherein the event information preparation step comprises an image receiving substep of receiving one or more images related to an event, and an image storage substep of storing the 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 pieces of medium having the event identifier and the 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 pieces of content on a print medium, and an attaching substep of attaching the one or more print media to a product container, and the product delivery step comprises a request receiving substep of receiving a delivery request having an event identifier and a user identifier from a user terminal, a user information acquisition substep of acquiring user information having a user address, the user information corresponding to the user identifier included in the delivery request, and a user information output substep of outputting the user information.

10. A delivery support method realized by an event identifier acquisition unit, a printing support unit, a request receiving unit, a user information acquisition unit, and a delivery support unit, comprising: 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 images related to the 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, and performs printing support, which is support for printing the content on a print medium; a request receiving step in which the request receiving unit receives a delivery request having an event identifier and a user identifier from a user terminal; a user information acquisition step in which the user information acquisition unit acquires user information corresponding to the user identifier included in the delivery request, the user information having a user address; and a delivery support step in which the delivery support unit performs delivery support, which is support for delivering one or more products having the print medium corresponding to the event identifier included in the delivery request attached to their containers, to a location indicated by the address included in the user information acquired by the user information acquisition unit.

Images