Information processing device, information processing method, and program

Abstract

To provide an information processing device, an information processing method, and a program by which an event can be smoothly changed.SOLUTION: An event management device 101 includes: a storage unit 301 that stores event information indicating a plurality of events including a first event that is held in a first holding form and a second event that is held in a second holding form, basic participation information that is associated with the event information and indicates a participation right of a participant user to at least one of the plurality of events, first participation information that is allocated to the participant user on the basis of the basic participation information and indicates a participation right for the first event, and second participation information that is allocated to the participant user on the basis of the basic participation information and indicates a participation right for the second event; a rate information acquisition unit 305 that acquires, from a management user, rate information indicating a conversion rate between the first participation information and the second participation information; and a participation information conversion unit 306 that converts the first participation information about the participant user to the second participation information about the participant user on the basis of the rate information.SELECTED DRAWING: Figure 3

Description

[Technical Field]

[0001] The present invention relates to an information processing device, an information processing method, and a program. [Background technology]

[0002] At various events, participation in the events is managed using electronic tickets issued to event participants. Patent Document 1 discloses a program that enables purchasers of electronic tickets to visually distinguish features such as relevance and superiority from other electronic tickets. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Publication No. 2018-26077 Summary of the Invention [Problem to be solved by the invention]

[0004] One type of event managed using electronic tickets is an interaction event between artists, entertainers, professional athletes, etc. (hereinafter referred to as "artists, etc.") and their fans. The interaction event takes the form of, for example, conversations between the artists, etc. and fans, taking photos, receiving autographs from the artists, etc. These interaction events are often held as real events where the artists, etc. and fans meet face-to-face at the event venue.

[0005] Real-life events are often held at venues where artists and fans gather, and there are cases where the event has to be canceled or its content changed due to, for example, natural disasters or infection control measures. When an event is canceled or its content is changed, resulting in an event with different content than originally planned, the event administrator may need to reschedule the event. In such cases, rescheduling the event places a significant burden on the administrator.

[0006] Therefore, an object of the present invention is to provide an information processing device, an information processing method, and a program that can promote smooth event transfers. [Means for solving the problem]

[0007] An information processing device according to one embodiment of the present invention includes a memory unit that stores event information indicating a plurality of events including a first event held in a first holding mode and a second event held in a second holding mode; basic participation information associated with the event information and indicating a participating user's participation right in at least one of the plurality of events; first participation information assigned to the participating user based on the basic participation information and indicating the participating user's participation right in the first event; and second participation information assigned to the participating user based on the basic participation information and indicating the participating user's participation right in a second event; a rate information acquisition unit that acquires rate information indicating a conversion rate between the first participation information and the second participation information from a management user that manages the plurality of events; and a participation information conversion unit that converts the participating user's first participation information into the participating user's second participation information based on the rate information.

[0008] In the above aspect, the first event and the second event may be events held on different days.

[0009] In the above aspect, the first event and the second event may be events held on the same day at different times.

[0010] In the above aspect, in the information processing device, the first event and the second event are associated with multiple providing users who provide the first event and the second event, the first participation information indicates the participation rights of participating users associated with each of the multiple providing users to the first event, and the second participation information indicates the participation rights of participating users associated with each of the multiple providing users to the second event, and the participation information conversion unit may convert the first participation information into the second participation information between common providing users.

[0011] In the above aspect, in the information processing device, the first event and the second event are associated with a plurality of providing users who provide the first event and the second event, the first participation information indicates the participation rights of participating users associated with each of the plurality of providing users to the first event, and the second participation information indicates the participation rights of participating users associated with each of the plurality of providing users to the second event, and the participation information conversion unit may convert the first participation information associated with some of the plurality of providing users into second participation information associated with some of the providing users.

[0012] In the above aspect, the information processing device may further include a ticket information sending unit that sends ticket information to the user terminal for displaying the first electronic ticket based on the first participation information and the second electronic ticket based on the second participation information on the user terminal of the participating user.

[0013] In the above aspect, in the information processing device, the rate information may indicate a non-equivalent conversion rate between the first participation information and the second participation information. Also, in the information processing device, the rate information may indicate an equivalent conversion rate between the first participation information and the second participation information.

[0014] An information processing method according to another aspect of the present invention includes a computer storing in a memory unit event information indicating a plurality of events including a first event held in a first holding mode and a second event held in a second holding mode; basic participation information associated with the event information and indicating the participating user's participation right in at least one of the plurality of events; first participation information assigned to the participating user based on the basic participation information and indicating the participating user's participation right in the first event; and second participation information assigned to the participating user based on the basic participation information and indicating the participating user's participation right in a second event; obtaining rate information indicating a conversion rate between the first participation information and the second participation information from a management user who manages the plurality of events; and converting the participating user's first participation information into the participating user's second participation information based on the rate information.

[0015] A program according to another aspect of the present invention causes a computer to execute a rate information acquisition process that acquires rate information indicating a conversion rate between the first participation information and the second participation information from a management user who manages multiple events based on event information indicating multiple events including a first event held in a first holding mode and a second event held in a second holding mode, basic participation information associated with the event information and indicating the participating user's participation right in at least one of the multiple events, first participation information assigned to the participating user based on the basic participation information and indicating the participating user's participation right in the first event, and second participation information assigned to the participating user based on the basic participation information and indicating the participating user's participation right in a second event, and a participation information conversion process that converts the participating user's first participation information into the participating user's second participation information based on the rate information. [Effects of the Invention]

[0016] According to the present invention, it is possible to provide an information processing device, an information processing method, and a program that can promote smooth event transfers. [Brief explanation of the drawings]

[0017] [Figure 1]1 is a diagram illustrating an overview of an event management system according to an embodiment of the present invention. [Figure 2] 10A and 10B are diagrams illustrating conversion of participation information in the event management system according to the present embodiment. [Figure 3] 1 is a block diagram showing a configuration of an event management device according to an embodiment of the present invention. [Figure 4] FIG. 4 is a diagram illustrating an example of user information according to the embodiment. [Figure 5] FIG. 10 is a diagram showing an example of event group information according to the embodiment. [Figure 6] FIG. 10 is a diagram illustrating an example of face-to-face event information according to the present embodiment. [Figure 7] FIG. 10 is a diagram showing an example of online event information according to the present embodiment. [Figure 8] FIG. 4 is a diagram showing an example of ticket information according to the embodiment. [Figure 9] FIG. 2 is a diagram illustrating processing in the event management system according to the embodiment. [Figure 10] 10 is a flowchart of a conversion process according to the present embodiment. [Figure 11] FIG. 10 is a diagram illustrating an example of a conversion process according to the present embodiment. [Figure 12] FIG. 10 is a diagram illustrating another example of the conversion process according to the embodiment. [Figure 13] 10A to 10C are diagrams illustrating an example of a ticket display screen generation process according to the embodiment. [Figure 14] 10 is an example of a ticket display screen according to the embodiment. [Figure 15] 10 is another example of a ticket display screen according to the embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0018] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS A preferred embodiment of the present invention will be described with reference to the accompanying drawings. In the drawings, components with the same reference numerals have the same or similar configurations.

[0019] (1. Overview) 1 shows a schematic diagram of an event management system 10 according to this embodiment. The event management system 10 includes an event management device 101, a management user terminal, participating user terminals 103a, 103b, . . . 103n, and a sales management device 104. Note that unless there is a need to distinguish between them, the participating user terminals 103a to 103n will be referred to as participating user terminals 103.

[0020] The event management device 101 is an information processing device such as a server that executes a predetermined program to perform the processes described below and manage events. The event management device 101 manages, for example, interaction events between artists and fans.

[0021] The administrator user terminal 102 is an information processing device such as a computer or a smartphone operated by an administrator user who manages events.

[0022] The participating user terminal 103 is an information processing device such as a computer or smartphone operated by a user participating in the event. The user receives an electronic ticket distributed from the event management device 101 on the participating user terminal 103 and can confirm their right to participate in the event using the electronic ticket.

[0023] The sales management device 104 is an information processing device such as a server that manages the sale of participation rights when a user participating in an event needs to purchase a participation right for the event.

[0024] The event management device 101 is communicably connected to a management user terminal 102, a participating user terminal 103, and a sales management device 104 via a network N.

[0025] An overview of event management by the event management device 101 will be described with reference to FIG. 2. An event is held with the participation of participating users who participate in the event, providing users who provide specific details of the event such as conversations, photography, or autographs at the event, and a management user who manages the event. For example, the providing users are artists, and the participating users are their fans. If the providing users are an event related to a group with multiple members (for example, a music group such as an idol group or a professional sports team), multiple providing users will participate in the event. More specifically, each providing user is a member of a music group or a player on a professional sports team. Note that a providing user may also be a single artist such as a solo singer or an athlete who performs solo. Furthermore, multiple participating users may participate in an event.

[0026] Here, an example of a social event between a participating user A who is one of a plurality of participating users and a providing user X who is one of a plurality of providing users will be described.

[0027] An interaction event between participating user A and providing user X includes a face-to-face event (real event or face-to-face event) where the participating user and providing user meet face-to-face at an event venue, or an online event (online event) where conversations, photographs, etc. are conducted via terminals connected via the Internet, etc.

[0028] For example, participating users are informed of whether the event will be face-to-face or online when they apply for the event, and they apply to participate in the event before it begins. An application for an event is made, for example, by purchasing a participation right through the sales management device 104. At the time of purchase, the event date and time and the providing user are selected by the participating user. Note that the participating user may select only the event date and time, and the providing user may be randomly assigned by the administrative user through the administrative user terminal 102 or the sales management device 104. Also, if there is only one providing user, the providing user may not be selected.

[0029] The event management device 101 stores basic participation information indicating the right to participate in the event in association with each participating user. The basic participation information is information indicating the number of participation rights each participating user has purchased, for example, via the sales management device 104.

[0030] In step (A), the administrative user transmits to the event management device 101 rate information indicating the difference in value between the first participation information indicating the right to participate in a face-to-face event and the second participation information indicating the right to participate in an online event. For example, the rate information is information resulting from the fact that, when a face-to-face event is compared with an online event, the value that an artist or the like provides to fans is higher for the face-to-face event than for the online event. Here, the administrative user transmits rate information so that the conversion rate between the face-to-face and online events is (face-to-face):(online)=1:3. Note that the rate information is not limited to the above example; for example, the conversion rate between face-to-face and online events may be 2:3. Furthermore, the rate information may be information indicating that the conversion rate is (face-to-face):(online)=1:1. In other words, the conversion rate may be a non-equivalent rate or an equivalent rate.

[0031] Specifically, the rate information is expressed as information on the number of basic participation rights required to participate in a face-to-face event and information on the number of basic participation rights required to participate in an online event. For example, the rate information is transmitted to the event management device 101 as information indicating that three basic participation rights are required to participate once in the event indicated by the first participation information, and one basic participation right is required to participate once in the event indicated by the second participation information. This allows the conversion rate to be (face-to-face):(online) = 1:3.

[0032] The first and second participation information are assigned to participating users based on the basic participation information and stored. The initial first and second participation information are generated in advance by, for example, the sales management device 104 or the management user terminal 102 and stored in the event management device 101. The first and second participation information may be assigned based on the basic participation information of participating user A and the event date and time and providing user selected by the participating user.

[0033] At this time, the first participation information and the second participation information are assigned according to the number of participation rights in the basic participation information. For example, based on the above-mentioned rate information, suppose that a participating user whose number of basic participation rights is 9 has applied for a face-to-face event indicated in the first participation information for providing user X. At this time, the first participation information is assigned with the number of times the participating user can participate in the event being 3. Also, suppose that the participating user has not applied for an online event indicated in the second participation information for providing user X. At this time, the second participation information is assigned with the number of times the participating user can participate in the online event being 0 for providing user X.

[0034] In step (B), participating user A receives from the event management device 101, at his / her terminal D1, an electronic ticket ET generated based on the first participation information and the second participation information.

[0035] In step (C), Participating User A proves his / her right to participate using the electronic ticket ET and participates in the social event. For example, Participating User A can participate in the social event with Providing User X three times using the electronic ticket ET generated based on Participating User A's three-time limit for participating in face-to-face events.

[0036] Here, let us assume that the face-to-face event indicated in the first participation information is canceled due to factors such as a natural disaster, infectious disease countermeasures, or the providing user's poor health.

[0037] In this case, the administrative user transmits a participation information conversion request to the event management device 101. In step (D), the event management device 101 converts the first participation information for the face-to-face event into second participation information for the online event based on the rate information.

[0038] In the example of FIG. 2, the first participation information indicating the participation rights for three face-to-face events for the providing user X is converted into the second participation information indicating the participation rights for nine online events for the providing user X. The event indicated in the second participation information is held on a different date or time from the event indicated in the first participation information that the providing user X was scheduled to attend.

[0039] As in step (B), participating user A receives an electronic ticket based on the second participation information from the event management device 101. Participating user A proves his / her right to participate using the electronic ticket ET and participates in the social event. In the case of an online event, the interaction takes place through communication between terminal D2 used by participating user A and terminal D3 used by providing user X. In this case, terminal D2 used by participating user A may be the same terminal as terminal D1 used to receive the electronic ticket.

[0040] In this way, even if the event is canceled or the content is changed, the event administrator can easily reschedule the event by changing the first participation information and second participation information of each participating user based on the rate information.

[0041] (2. Configuration of the Event Management Device) 3 shows a block diagram of the event management device 101. The event management device 101 has, as its physical configuration, a CPU (Central Processing Unit) that performs processing required for control, RAM (Random Access Memory), ROM (Read Only Memory), or HDD (Hard Disk Drive) as a storage area, and a communication device that performs various communications.

[0042] The event management device 101 has, as its functional configuration, a storage unit 301, a communication unit 302, a user management unit 303, an event management unit 304, a rate information acquisition unit 305, a participation information conversion unit 306, and a ticket information transmission unit 307. Each unit of the event management device 101 is realized, for example, by using a storage area such as RAM or ROM, or by the CPU executing a program stored in the storage area.

[0043] The storage unit 301 is a storage area that stores programs and information required for various processes in the event management device 101. The storage unit 301 includes a user database 3011, an event database 3012, and a ticket database 3013.

[0044] 4 shows an example of information stored in the user database 3011. The user database 3011 stores participating user information, providing user information, and management user information.

[0045] Participating user information has the fields "Participating user name" and "Participating user ID." The "Participating user name" field stores the name of the participating user who will participate in the event. The "Participating user ID" field stores information for identifying the participating user. For example, for a participating user whose "Participating user name" is participating user A1, F001 is associated and stored as the "Participating user ID."

[0046] The providing user information has the fields "Providing User Name" and "Providing User ID". The "Providing User Name" field stores the name of the providing user who provides the event. The "Providing User ID" field stores information for identifying the providing user. For example, for a providing user whose "Providing User Name" is providing user X1, M001 is associated and stored as the "Providing User ID".

[0047] The management user information has the fields "management user name" and "management user ID." The "management user name" field stores the name of the management user who manages the event. The "management user ID" field stores information for identifying the management user. For example, for a management user whose "management user name" is management user P1, AD001 is associated and stored as the "management user ID."

[0048] The items of participating user information, providing user information, and administrative user information stored in the user database 3011 are not limited to the example shown in FIG. 4, and various items of attributes related to each participating user, providing user, and administrative user may be provided. For example, a "nickname" item may be provided in the participating user information, and a nickname set by the participating user may be stored. Also, a "group to which the providing user belongs" item may be provided in the providing user information, and when the providing user performs activities as part of a group, information indicating the group may be stored. Alternatively, a "affiliation" item may be provided in the administrative user information, and the affiliation of the administrative user may be stored.

[0049] Event group information, face-to-face event information, and online event information are stored in the event database 3012. Fig. 5 shows an example of event group information, which is one type of information stored in the event database 3012. Event group information is, for example, information for collectively managing multiple events that are held on different dates.

[0050] The event group information has the following items: "Event group name", "Event group ID", "Event period", "Event name", and "Event ID".

[0051] The "Event Group Name" field stores the name of the event group. An event group name is a collective name that refers to, for example, an artist's music release, a celebrity's book or photo book release, or a series of events held during a professional sports team's training camp. The "Event Group ID" field stores information for identifying the event group.

[0052] The "Event Period" field stores the period during which a series of events are held, from the date of the first event to the date of the last event. The "Event Name" field stores the names of the events included in each event group. The "Event ID" field stores information for identifying each event.

[0053] In the example of Figure 5, an event with an "event group name" of event group EG1 is assigned an "event group ID" of EG001. The "event period" of event group EG1 is from August 1, 2021 to February 13, 2022. The individual "event names" stored are "Real Event R1," "Online Event ON1," and "Hybrid Event HV1," and each is assigned an "event ID" of EV001, EV002, and EV003. A hybrid event is an event in which both a face-to-face event and an online event are held on the same day.

[0054] An example of face-to-face event information is shown in Fig. 6. The face-to-face event information is information showing details of each event that is held in a face-to-face format.

[0055] The face-to-face event information has the following fields: "Event name," "Event ID," "Event date," "Time period name," "Time period ID," "Event holding mode," "Event details," "Number of required participation rights," "Provided user name," and "Provided user ID."

[0056] The "event name" and "event ID" items store information similar to the event name and event ID stored in the event group information.

[0057] The "Event Date" field stores information indicating the date on which the event will be held. The "Time Period Name" field stores information indicating the time period during which an actual event will be held within a certain event. The "Time Period ID" field stores information for identifying the time period.

[0058] The "event holding mode" item stores information indicating the holding mode of the event held in each time period. In face-to-face event information, the "event holding mode" is always stored as face-to-face. The "event details" item stores information indicating details of the event held in each time period. For example, the "event details" item stores specific content of the activities provided at the event, such as "talk," "two-shot," or "autograph."

[0059] The "Number of Required Participation Rights" field stores information indicating the number of basic participation rights required to participate in each event. The "Number of Required Participation Rights" is input and stored by the administrative user. The "Number of Required Participation Rights" may be set for each individual event for each time period, or may be set according to the event holding style or event details. In other words, if the event holding style is face-to-face, the number of required participation rights may be set uniformly to 3. Also, if the event details are a talk, the number of required participation rights may be set to 3, and if the event details are a two-shot, the number of required participation rights may be set uniformly according to the event details. Also, the number of required participation rights may be set for each providing user.

[0060] The "Providing User Name" and "Providing User ID" items are associated with a plurality of providing users who provide events for each time period and their IDs.

[0061] In the example of Figure 6, for an event with an "event name" of real event R1 and an "event ID" of EV001, 2021 / 8 / 1 is stored as the "event date." As the "time slot name," time slot A1, time slot B1, etc. for real event R1 are stored in association with "time slot IDs" T001, T002, etc.

[0062] The "Event holding mode" of the event in time slot A1 is stored as "Face-to-face" and its "Event details" is recorded as "Talk." Also, the "Number of required participation rights" for the event in time slot A1 is stored as 3.

[0063] The "Providing User" and "Providing User ID" fields store the IDs of providing users such as providing user X1, providing user X2, etc., as well as the IDs of each providing user, as users providing face-to-face talk events during time period A1. In other words, face-to-face talk events held during time period A1 include a social event provided by providing user X1 and a social event provided by providing user X2. The same applies to hybrid event HV1.

[0064] FIG. 7 shows an example of online event information. Online event information is information showing details of each event held online. Online event information has the same items as face-to-face event information. Face-to-face event information and online event information differ in the "event date," "event holding format," or "required number of participation rights," etc.

[0065] For example, for online event ON1, the "event date" is December 5, 2021, and the "event format" is online. Furthermore, the "event details" are stored as "talk" for time slot A2 and "two-shot" for time slot B2. Furthermore, the "required number of participation rights" is stored as "1" for the event in time slot A2 and "2" for the event in time slot B2. Furthermore, the "event details" are stored as "group talk" for time slot C2. Here, group talk refers to an event in which multiple providing users talk simultaneously. Figure 7 shows an example of an event in which providing users X1, X2, and X3 talk simultaneously. The "required number of participation rights" for the event in time slot C2 is stored as "3," which is equivalent to the "required number of participation rights" for a face-to-face event.

[0066] Furthermore, hybrid events HV1, which include both face-to-face and online events, are stored in both face-to-face event information and online event information. The face-to-face event information and online event information may be managed as a single combined event. The items in the face-to-face event information and online event information are not limited to those exemplified, and any items may be provided to store information related to the event. For example, information such as the duration of each talk event, the duration of each two-shot event, or the number of photos taken may be stored.

[0067] 8 shows an example of ticket information stored in the ticket database 3013. The ticket information has the following fields: "Participating user ID," "Number of basic participation rights," "Number of allocated basic participation rights," "Event group ID," "Event name," "Time period name," "Event holding mode," "Event details," "Providing user name," "Number of required participation rights," "Participating ticket ID," "Number of tickets," and "Ticket usage status."

[0068] The items "Participating user ID," "Event group ID," "Event name," "Time period name," "Event holding mode," "Event details," "Providing user name," and "Number of required participation rights" store information similar to the items of event information stored in the event database 3012.

[0069] The "Number of Basic Participation Rights" field stores information (basic participation information) indicating the number of basic participation rights held by a participating user for an event in a certain event group. The number of basic participation rights is information indicating the number of participation rights purchased by each participating user from, for example, the sales management device 104.

[0070] The "number of allocated basic participation rights" field stores information indicating the number of basic participation rights to which participation tickets, which will be described later, have been allocated.

[0071] The "Participation ticket ID" field stores information for identifying a participation ticket that indicates the participating user's right to participate in an event. The "Number of tickets" field stores the number of each ticket. The number of tickets is the number of times a participating user can participate in each event. The "Ticket usage status" field stores information indicating whether a ticket has been used to participate in an event. The information stored in the "Participation ticket ID" and "Number of tickets" fields becomes the first participation information or the second participation information.

[0072] For example, a user with a participating user ID of F001 has 24 basic participation rights to participate in an event with an event group ID of EG001. A "participation ticket ID" and "number of participation tickets" are assigned to each of the events in the event group with the event group ID of EG001: the real event R1, the online event ON1, and the hybrid event HV1. At this time, all of the basic participation rights held by the user with the participating user ID of F001 have been assigned, so the "number of assigned basic participation rights" field stores information indicating that 24 of the 24 rights have been assigned, such as "24 / 24."

[0073] For example, it is recorded that user F001 has five and three participation tickets to the face-to-face talk event provided by providing user X1 in time slots A1 and B1 for real event R1, respectively. It is also recorded that user F001 has no participation tickets for online event ON1 and hybrid event HV1.

[0074] Selection of each event and the providing user for each event is performed, for example, by the participating user selecting the event date and time and the providing user when purchasing the participation right through the sales management device 104.

[0075] The number of tickets indicates not only the number of times participants can participate, but also the available participation time. For example, the available talk time per ticket for a participating user may be preset by the administrative user. In this case, a participating user can use multiple participation tickets to participate in a single talk event. This allows the participating user to change the length of their talk time depending on the number of tickets used at one time.

[0076] The communication unit 302 controls communications between the event management device 101 and the managing user terminal 102 , participating user terminal 103 , and sales management device 104 .

[0077] The user management unit 303 registers and authenticates participating users, providing users, and management users, and manages access to the event management device 101. The user management unit 303 also updates the information in the user database 3011.

[0078] The event management unit 304 updates the information in the event database 3012 and the ticket database, or updates the "ticket usage status" of the ticket information while an event is being held.

[0079] The rate information acquisition unit 305 acquires rate information indicating the conversion rate between the face-to-face event and the online event from the administrative user. Specifically, the rate information is transmitted as information on the "required number of participation rights" in the face-to-face event information and information on the "required number of participation rights" in the online event information.

[0080] When a conversion request is received from the administrative user, the participation information conversion unit 306 converts the participation information for the face-to-face event and the participation information for the online event in the ticket information, and vice versa, based on the rate information. Details of the conversion will be described later.

[0081] The ticket information sending unit 307 references the ticket database 3013 and sends the participation information associated with the participating user as an electronic ticket to the participating user terminal 103. For example, the ticket information sending unit 307 generates information for displaying an electronic ticket based on the face-to-face event information and an electronic ticket based on the online event information on the participating user terminal 103, and sends this information to the participating user terminal 103.

[0082] (3. Processing in the event management system 10) The processing in the event management system 10 will be described with reference to FIG.

[0083] In step S 901 , the management user terminal 102 transmits event group information to the event management apparatus 101 .

[0084] In step S 902 , the event management unit 304 stores the event group information in the event database 3012 .

[0085] In step S903, the administrative user terminal 102 transmits the face-to-face event information and the online event information to the event management device 101. At this time, the administrative user terminal 102 transmits the face-to-face event information and the online event information excluding the item "Number of required participation rights."

[0086] In step S904, the event management unit 304 stores the face-to-face event information and the online event information in the event database 3012.

[0087] In step S 905 , the management user terminal 102 transmits the rate information to the event management apparatus 101 .

[0088] In step S906, the rate information acquisition unit 305 updates the face-to-face event information and the online event information based on the rate information. Specifically, the rate information acquisition unit 305 updates the information on the "number of required participation rights" in the face-to-face event information and the information on the "number of required participation rights" in the online event information. Note that the transmission and storage of the rate information may be performed as part of the processing in steps S903 and S904.

[0089] Through the processing up to this point, the event information described with reference to FIGS. 5 to 7 is stored in the event management device 101.

[0090] In step S907, the new user transmits the new user ID, purchase information, and selection information to the sales management device via the new user terminal 103. The purchase information here is information for purchasing basic participation rights to each event sold by the sales management device 104, such as information indicating the number of basic participation rights to be purchased. The selection information is information for selecting the date of each event in a certain event group, the time period of the event, and the user providing the event in each time period.

[0091] In step S908, the sales management device 104 associates the participating users with basic participation information based on the purchase information.

[0092] In step S909, the sales management device 104 transmits to the management user terminal 102 the new user ID, the basic participation information of each new user, and the selection information of each new user.

[0093] In step S910, the management user terminal 102 transmits the participating user ID, the basic participation information of each participating user, and the selection information of each participating user to the event management device 101. Note that in step S909, the sales management device 104 may transmit the participating user ID, the basic participation information of each participating user, and the selection information of each participating user to the event management device 101, and the processing of step S310 may be omitted.

[0094] In step S911, the event management unit 304 assigns participation information for a face-to-face or online event to the participating user based on the basic participation information and selection information. Specifically, the event management unit 304 stores the ticket information described with reference to Fig. 8 in the ticket database 3013. The ticket information at this time is the initial ticket information before the conversion of the participation information.

[0095] In step S912, the management user terminal 102 transmits a participation information conversion request to the event management apparatus 101.

[0096] In step S913, the participation information conversion unit 306 performs conversion processing of the participation information.

[0097] In step S914, the participating user terminal 103 transmits a ticket display request to the event management device 101.

[0098] In step S915, the event management apparatus 101 performs ticket display processing based on the converted participation information. The ticket display processing will be described later.

[0099] (4. Conversion process) The conversion process by the participation information conversion unit 306 will be described with reference to the flowchart of Fig. 10 and Fig. 11 and Fig. 12. Here, the process after a conversion request is acquired will be described.

[0100] The conversion request includes, for example, information identifying the source event and the destination event. In the case of conversion on an event-by-event basis, the conversion request includes the source event ID and the destination event ID. In the case of conversion on a time-zone basis for a portion of an event, the conversion information may include the source event ID and time-zone ID, and the destination event ID and time-zone ID. In the case of conversion on a providing user basis, the conversion information may include the source event ID, time-zone ID, and providing user ID, and the destination event ID, time-zone ID, and providing user ID.

[0101] Here, an example of conversion in which the ticket information in Fig. 11(a) is updated to the ticket information in Fig. 11(b) will be described. In this case, the conversion converts participation information (ticket) for the event of providing user X1 in real event R1 into participation information (ticket) for the event of providing user X1 in online event ON1. More specifically, for tickets associated with providing user X1 in time period A1 and time period B1, the ticket for time period A1 is converted into a ticket for time period A2, and the ticket for time period B1 is converted into a ticket for time period B2.

[0102] In step S1001, the participation information conversion unit 306 refers to the event information of the source event and the destination event in the event database 3012.

[0103] In step S1002, based on the event information, the participation information conversion unit 306 extracts ticket information including participating users who have participation tickets for the original event from the ticket database 3013. An example of the extracted ticket information is shown in Figure 11(a).

[0104] In step S1003, the participation information conversion unit 306 acquires the first required number of participation rights of the source event information and the second required number of participation rights of the destination individual event information, which correspond to the referenced participation ticket.

[0105] 11(a), when converting from time slot A1 to time slot A2, the participation information conversion unit 306 obtains "3" as the first required number of participation rights and "1" as the second required number of participation rights. When converting from time slot B1 to time slot B2, the participation information conversion unit 306 obtains "3" as the first required number of participation rights and "2" as the second required number of participation rights.

[0106] In step S1004, the participation information conversion unit 306 calculates a conversion rate between the source and destination based on the first required number of participation rights and the second required number of participation rights. Specifically, the conversion rate is calculated by dividing the first required number of participation rights by the second required number of participation rights.

[0107] In Fig. 11(a), a conversion rate of 3 (=3÷1) is calculated for conversion from time period A1 to time period A2, and a conversion rate of 1.5 (=3÷2) is calculated for conversion from time period B1 to time period B2.

[0108] In step S1005, the participation information conversion unit 306 multiplies the number of participation tickets to be converted by the conversion rate to generate information indicating the number of participation tickets to be converted.

[0109] In Figure 11(a), when converting from time slot A1 to time slot A2, the number of participation tickets "5" is multiplied by the conversion rate 3 to calculate the number of tickets after conversion "15." Also, when converting from time slot B1 to time slot B2, the number of participation tickets "3" is multiplied by the conversion rate 1.5 to calculate the number of tickets after conversion 4.5.

[0110] If the converted number of tickets contains a fraction after the decimal point, the participation information conversion unit 306 rounds down the converted number of tickets and sets the converted number of tickets to 4. In this case, the participation information conversion unit 306 updates the number of allocated basic participation rights by treating the basic participation rights equivalent to the fraction 0.5 as not being allocated. Specifically, the number of not being allocated basic participation rights is calculated by multiplying the value calculated by dividing the fraction by the conversion rate by the number of participation rights required for the event before conversion. For example, if the conversion rate is 1.5 and the fraction is 0.5, the number of basic participation rights that will be set to not being allocated is 1 (= 0.5 ÷ 1.5 × 3). In this case, the participation information conversion unit 306 updates the number of allocated basic participation rights from "33 / 33" to "32 / 33." Furthermore, the participation information conversion unit 306 updates the ticket information by setting the number of participation tickets for time slot B1 to 0. Note that conversion may be performed by rounding up any fraction.

[0111] In step S1006, the participation information conversion unit 306 updates the ticket information. For example, the ticket information shown in FIG. 11(a) is updated to the ticket information shown in FIG. 11(b). The conversion of the participation information is performed without changing the number of basic participation rights before and after the conversion. Therefore, the conversion of the participation information is performed while avoiding refunds of the purchase costs of the number of basic participation rights due to changes in the number of basic participation rights. This allows the event manager to hold the event while reducing the risk of refunds that may arise due to cancellation of the event, etc.

[0112] Note that conversion can also be performed in a similar manner when the conversion rate is set to convert participation rights at an equivalent rate. For example, the first required number of participation rights and the second required number of participation rights may be set to the same value, "3." In this case, basic participation rights allocated to the event before conversion can be allocated to the converted event without creating any surplus basic participation rights. Because conversion is performed without creating any surplus basic participation rights, the event administrator can convert (transfer) the event so that all basic participation rights allocated to the event before conversion are converted. This allows the event administrator to hold the event while reducing the risk of refunds arising from event cancellations, etc., and also reducing the burden of making adjustments to surplus basic participation rights.

[0113] In the example of FIG. 11, during time period A1 of real event R1, the ticket information associated with providing user X1 is updated, but the ticket information associated with providing user X2 is not updated. In this way, the participation information conversion unit 306 can convert between events related to some providing users, even if the events are held on the same day and in the same time period. The participation information conversion unit 306 may also update the ticket information associated with providing user X2 according to the content of the conversion request. In other words, the participation information conversion unit 306 can convert all participation information for an event held on a certain day into participation information for an event held on a different day. It is also possible to add another event to the event information and then convert the participation information for the added event.

[0114] The participation information conversion unit 306 can also convert the participation information in a format different from the example of FIG. 11 depending on the content of the conversion request. An example of conversion will be described in which the ticket information in FIG. 12(a) is updated to the ticket information in FIG. 12(b). In this case, the conversion converts a ticket for providing user X1 for time slot B3 of hybrid event HV1 into a ticket for providing user X1 for time slot A3 of hybrid event HV1. In this case, the participation information conversion unit 306 also updates the ticket information using the processing in FIG. 10.

[0115] The example in Figure 12 shows how to update ticket information to allow for same-day transfers when an in-person event is canceled for various reasons. Even in this case, the conversion is performed without changing the number of basic tickets, and the transfer can be completed on the same day. This allows the event manager to hold the event while reducing the risk of refunds and the risk of having to arrange a separate venue.

[0116] (5. Ticket display processing) The ticket display process performed by the ticket information transmitting unit 307 will be described with reference to FIGS.

[0117] In step S 1301 , the ticket information transmitting unit 307 receives a ticket display request from the new user terminal 103 .

[0118] In step S1302, the ticket information transmitting unit 307 searches the ticket database 3013 based on the user ID of the participating user.

[0119] In step S1303, the ticket information transmitting unit 307 generates screen display information for displaying a ticket screen showing the electronic ticket on the participating user terminal 103 based on the ticket information found as a result of the search.

[0120] In step S 1304 , the ticket information transmitting unit 307 transmits the screen display information to the new user terminal 103 .

[0121] FIG. 14 shows a ticket screen 1401A before conversion and a ticket screen 1401B after conversion when the conversion described with reference to FIG. 11 is performed.

[0122] The ticket screen displays electronic tickets for each event and each time period in a distinguishable manner. Users who initially managed their own electronic tickets by referring to ticket screen 1401A can now see that their electronic tickets have been transferred by referring to updated ticket screen 1401B.

[0123] Fig. 15 shows a ticket screen 1501A before conversion and a ticket screen 1501B after conversion when the conversion described with reference to Fig. 12 is performed. In this case, too, the user can refer to the ticket screen 1501A and the ticket screen 1501B and know that the transfer of his / her electronic ticket has been performed.

[0124] (6. Summary of this embodiment) The above describes an embodiment of the present invention. The event management device 101 according to the present embodiment includes a storage unit 301 that stores: event information indicating a plurality of events, including a face-to-face event (first event) held in a face-to-face format (first holding mode) and an online event (second event) held online (second holding mode); basic participation information associated with the event information and indicating the participation rights of participating users in at least one of the plurality of events; first participation information assigned to the participating users based on the basic participation information and indicating the participation rights of the participating users in the first event; and second participation information assigned to the participating users based on the basic participation information and indicating the participation rights of the participating users in the second event; a rate information acquisition unit 305 that acquires rate information indicating a conversion rate between the first participation information and the second participation information from a management user who manages the plurality of events; and a participation information conversion unit 306 that converts the first participation information of the participating users into the second participation information of the participating users based on the rate information.

[0125] According to this aspect, participation information for a face-to-face event stored in the storage unit 301 is converted into participation information for an online event based on rate information indicating a conversion rate. As a result, if a transfer to a face-to-face event becomes necessary, the first participation information can be converted into second participation information for a second event held online. By using the rate information during the conversion, transfer can be performed without going through procedures such as refund processing based on the first participation information and re-application for the second event, depending on the difference in value provided between the events, such as when the value provided by an artist or the like to fans at a social event, such as a real event, is different from that provided at an online event, or when the value provided is equivalent. This promotes smooth event transfers. Note that the conversion of the event mode is not limited to a conversion from face-to-face to online, but may also be a conversion from online to face-to-face. In this case, the first event becomes an online event, and the second event becomes an in-person event.

[0126] In the event management device 101 according to this embodiment, the face-to-face event and the online event may be events held on different days. Furthermore, in the event management device 101 according to this embodiment, the face-to-face event and the online event may be events held on the same day at different time slots. In this way, by making it possible to convert the source event and the destination event between different dates or between different time slots on the same day, the event management user can increase the options for the transfer destination to select. By being able to select an appropriate transfer destination depending on the situation, smooth event transfers are promoted.

[0127] In the event management device 101 of this embodiment, face-to-face events and online events are associated with multiple providing users who provide the face-to-face events and online events, participation information for the face-to-face event indicates the right to participate in the face-to-face event associated with each of the multiple providing users, and participation information for the online event indicates the right to participate in the online event associated with each of the multiple providing users, and the participation information conversion unit 306 may convert the participation information for the face-to-face event into information for the online event between common providing users.

[0128] By using the same providing user before and after the conversion, participating users who have the participation rights related to the converted participation information can accept the conversion with a sense of satisfaction. This allows the event management user to transfer the event while satisfying the wishes of the participating users, making it easier to transfer events. This promotes smooth event transfers.

[0129] In the event management device 101 of this embodiment, face-to-face events and online events are associated with multiple providing users who provide the face-to-face events and online events, participation information for the face-to-face event indicates the right to participate in the face-to-face event associated with each of the multiple providing users, and participation information for the online event indicates the right to participate in the online event associated with each of the multiple providing users, and the participation information conversion unit 306 may convert participation information for the face-to-face event associated with some of the multiple providing users into participation information for the online event associated with some of the providing users.

[0130] In this way, by making the source and destination events the events of some of the providing users, conversion can be performed only for the providing users for whom transfer is necessary. Therefore, by being able to select an appropriate source and destination depending on the situation of the providing user, smooth event transfers can be promoted.

[0131] The event management device 101 according to this embodiment may further include a ticket information sending unit 307 that sends ticket information to the participating user terminal 103 for displaying the first electronic ticket based on the participation information for the face-to-face event and the second electronic ticket based on the participation information for the online event on the participating user terminal 103 of the participating user. This allows the user to know that their electronic ticket has been transferred from the ticket information displayed on the participating user terminal 103.

[0132] In the event management device 101 according to this embodiment, the rate information may indicate a non-equivalent conversion rate between the first participation information and the second participation information. Also, in the event management device 101 according to this embodiment, the rate information may indicate an equivalent conversion rate between the first participation information and the second participation information.

[0133] The above-described embodiments are intended to facilitate understanding of the present invention and are not intended to limit the present invention. The elements of the embodiments, as well as their arrangement, conditions, size, etc., are not limited to those illustrated and can be modified as appropriate. Furthermore, configurations shown in different embodiments can be partially substituted or combined with each other. [Explanation of symbols]

[0134] 10...Event management system, 101...Event management device, 102...Management user terminal, 103...Participating user terminal, 104...Sales management device, 301...Memory unit, 302...Communication unit, 303...User management unit, 304...Event management unit, 305...Rate information acquisition unit, 306...Participation information conversion unit, 307...Ticket information transmission unit

Claims

1. event information indicating a plurality of events including a first event held in a first event mode and a second event held in a second event mode; basic participation information associated with the event information and indicating the participation rights of participating users in at least one of the plurality of events; First participation information assigned to the participating user based on the basic participation information and indicating the participating user's right to participate in the first event; a storage unit that stores second participation information that is assigned to the participating user based on the basic participation information and indicates the participating user's right to participate in the second event; a rate information acquisition unit that acquires rate information indicating a conversion rate between the first participation information and the second participation information from a management user who manages the plurality of events; a participation information conversion unit that converts the first participation information of the new user into the second participation information of the new user based on the rate information; An information processing device comprising:

2. 2. The information processing device according to claim 1, The information processing device, wherein the first event and the second event are events held on different days.

3. 2. The information processing device according to claim 1, The information processing device, wherein the first event and the second event are events held at different time slots on the same day.

4. 4. The information processing device according to claim 1, a plurality of providing users who provide the first event and the second event are associated with the first event and the second event; the first participation information indicates the participation rights of the participating users associated with each of the plurality of providing users to the first event; the second participation information indicates the participation rights of the participating users associated with each of the plurality of providing users in the second event; The participation information conversion unit converts the first participation information into the second participation information between common providing users.

5. 5. The information processing device according to claim 1, a plurality of providing users who provide the first event and the second event are associated with the first event and the second event; the first participation information indicates the participation rights of the participating users associated with each of the plurality of providing users to the first event; the second participation information indicates the participation rights of the participating users associated with each of the plurality of providing users in the second event; The participation information conversion unit converts the first participation information associated with some of the plurality of providing users into second participation information associated with the some of the providing users.

6. 6. The information processing device according to claim 1, The information processing device further includes a ticket information sending unit that sends ticket information to the user terminal of the participating user for displaying a first electronic ticket based on the first participation information and a second electronic ticket based on the second participation information on the user terminal of the participating user.

7. 7. The information processing device according to claim 1, An information processing device, wherein the rate information indicates a non-equivalent conversion rate between the first participation information and the second participation information.

8. 7. The information processing device according to claim 1, An information processing device, wherein the rate information indicates an equivalent conversion rate between the first participation information and the second participation information.

9. The computer event information indicating a plurality of events including a first event held in a first event mode and a second event held in a second event mode; basic participation information associated with the event information and indicating the participation rights of participating users in at least one of the plurality of events; First participation information assigned to the participating user based on the basic participation information and indicating the participating user's right to participate in the first event; storing second participation information in a storage unit, the second participation information being assigned to the participating user based on the basic participation information and indicating the participating user's right to participate in the second event; acquiring rate information indicating a conversion rate between the first participation information and the second participation information from a management user who manages the plurality of events; and converting the first participation information of the new user into the second participation information of the new user based on the rate information.

10. On the computer, event information indicating a plurality of events including a first event held in a first event mode and a second event held in a second event mode; basic participation information associated with the event information and indicating the participation rights of participating users in at least one of the plurality of events; First participation information assigned to the participating user based on the basic participation information and indicating the participating user's right to participate in the first event; second participation information assigned to the participating user based on the basic participation information and indicating the participating user's right to participate in the second event, a rate information acquisition process for acquiring rate information indicating a conversion rate between the first participation information and the second participation information from a management user who manages the plurality of events; a participation information conversion process for converting the first participation information of the new user into the second participation information of the new user based on the rate information; A program that executes.

Images