Fan information management device, fan information management system, fan information management program, and fan information management method

Abstract

This device provides a fan information management system that can improve the convenience of managing fan information for artists who are active in a wide range of fields, including solo, group, and inter-group activities. [Solution] The present invention is a fan information management device 2 for managing information about fans of a group to which an artist belongs, comprising: a member management unit 10e that manages members belonging to the group in association with the group; an event management unit 10c that manages information related to the group's events; and a fan list management unit 10f that lists information about fans participating in events and manages it as a fan list. In this case, the device further comprises a message sending unit 20b that sends messages to fans, the fan list management unit 10f manages the contact information of fans as fan information, and the message sending unit 20b may send messages to the contact information.

Description

Technical Field

[0001] The present invention relates to a fan information management device, a fan information management system, a fan information management program, and a fan information management method, and particularly to a fan information management device, a fan information management system, a fan information management program, and a fan information management method for managing fan information of a group such as a band or a session to which a musician belongs.

Background Art

[0002] A band, which is a group that performs music, is composed of a plurality of members who perform music. In general bands, when holding a music live at a live house or a store, unlike professional artists who utilize large-scale ticket sales services, many band members use SNS or direct messages for announcements and customer acquisition, and directly accept reservations. The fees for music lives are often exchanged at the live house or store on the day of the live. For this reason, each band member has difficulty in customer acquisition management due to problems such as assigned responsibilities and duplicate announcements when contacting customers who are expected to attend and managing reservations.

[0003] ​ [Prior art documents] [Patent Documents]

[0004] [Patent Document 1] Japanese Patent Publication No. 2002-189870 (Abstract, Claim 3, Paragraphs 0021-0029, etc.) [Overview of the project] [Problems that the invention aims to solve]

[0005] In actual musical activities, one artist may belong to multiple bands (groups). However, in Patent Document 1, the registered artists that can be registered in the system are individuals or groups, and individual artists and musician groups must be registered separately as one artist. For example, if artist A is active as a solo artist and also belongs to bands B and C, artist A as an individual, and bands B and C must be registered in the system three times. In other words, in the system of this document, individual artists cannot be registered across their solo activities and group activities, or across multiple groups, which is inconvenient for artists who are active in a wide range of activities, whether solo or in groups.

[0006] Furthermore, the system described in this document involves uploading and registering music data, and then distributing the music data according to user requests; it is not managed on an event-by-event basis, such as a live performance. Furthermore, in the system described in this document, registration data is stored on the email newsletter server when a person who wishes to subscribe to the email newsletter specifies an artist and registers. In other words, the accumulation of registration data is passive and dependent on the actions of those who wish to subscribe, and fan information is not automatically accumulated. Furthermore, while this document states that user registration data can be used as a mailing list for information such as live concert announcements, it does not specifically describe how the list will be managed and used for each concert (event). If it is simply a list of email newsletter subscribers, the number of subscribers on the list will not increase unless users subscribe to the email newsletter, making it difficult to expect an increase in attendees or expansion of the fan base at events.

[0007] This invention has been made in view of the above-mentioned problems, and aims to provide a fan information management device, a fan information management system, a fan information management program, and a fan information management method that can improve the convenience of managing fan information for artists who are active in a wide range of fields, including solo and group activities, and between groups. [Means for solving the problem]

[0008] [1] A fan information management device for managing information about fans of a group to which an artist belongs, A member management department manages members belonging to a group in association with the aforementioned group, The event management department manages information related to the events of the aforementioned group, A fan information management device characterized by comprising: a fan list management unit that lists fan information related to the aforementioned event and manages it as a fan list.

[0009] According to the present invention, it is possible to manage artist members as a group. Therefore, it is possible to flexibly manage individual artists and groups in association, such as registering one artist across multiple groups. Furthermore, this invention allows for the management of information related to events such as group concerts. Therefore, information about fans related to the event, such as event participants, can be compiled into a fan list. Furthermore, since fans interested in an event can be registered to a fan list, a fan list can be automatically created without relying on fans voluntarily joining mailing lists or similar platforms. This also reduces the effort required of artists to create fan lists. These configurations can improve the convenience of managing fan information for artists who are active both as solo artists and in groups, or across different groups.

[0010] [2] It is further equipped with a message sending unit that sends messages to fans, The aforementioned fan list management unit manages the contact information of the aforementioned fans as information about the aforementioned fans. The fan information management device according to [1] above, characterized in that the message sending unit sends the message to the contact.

[0011] In this way, information such as live performances can be provided to fans on the fan list, making it easy to disseminate information such as event announcements and artist introductions.

[0012] [3] The event management unit manages multiple events, including the first event and the second event, The fan information management device according to [2] above, characterized in that the message transmission unit transmits the message to both the contact information of the fan on the first fan list corresponding to the first event and the contact information of the fan on the second fan list corresponding to the second event.

[0013] In this way, messages can be sent to both fan lists for multiple events, meaning the number of fans to whom messages are sent increases with each event. This makes it easier to promote events individually and manage fans as a group.

[0014] [4] When an artist belongs as a member across multiple groups, including the first group and the second group, the member management unit manages the member by associating him with both the first group and the second group. The fan information management device according to [2] above, characterized in that the message transmission unit transmits the message to both the contact information of the fan in the fan list corresponding to the first group and the contact information of the fan in the fan list corresponding to the second group.

[0015] Thus, when an artist belongs to multiple groups, they can send messages not only to fans on their own group's fan list but also to fans on other groups' fan lists. This allows them to attract fans from other groups and is expected to expand their fanbase.

[0016] [5] If a member leaves the second group, the member management unit shall remove the association of the member with the second group. The fan information management device according to [4] above, characterized in that the fan list management unit does not send the message to the contact information of the fan in the fan list corresponding to the second group.

[0017] In this way, if an artist leaves a group, no message is sent to the fans on that group's fan list. This prevents the artist who left a group from using the fan list of another group.

[0018] [6-1] A fan information management system for managing information about fans of a group to which an artist belongs, It includes member terminals operated by members belonging to the group, event participant terminals operated by participants attending events, and a fan information management server for managing fan information. The aforementioned member terminal is A member registration unit that registers members belonging to a group in association with the group, An event creation instruction unit that gives an instruction to create an event of a group, and is provided with The event participant terminal An event display unit that displays information about an event, An event reservation unit that reserves participation in the event displayed by the event display unit, and is provided with The fan information management server A member management unit that manages the members registered by the member registration unit in association with the group, An event management unit that manages information about the event of the group created by the event creation instruction unit, A fan list management unit that lists the information of the participants who have reserved participation in the event by the event reservation unit as fan information and manages it as a fan list, and is characterized by a fan information management system comprising

[0019] According to this invention, it becomes possible to provide a fan information management system having the same functions as the fan information management device described in [1] above by a client / server system.

[0020] 〔6-2〕 Further comprising a message transmission unit that transmits a message to a fan, The fan list management unit manages the contact information of the fan as the information of the fan, The message transmission unit transmits the message to the contact information, and is characterized by the fan information management system according to [6-1] above.

[0021] 〔6-3〕 The event management unit manages a plurality of events including a first event and a second event, The fan information management system according to [6-2] above, characterized in that the message sending unit sends the message to both the contact information of the fan on the first fan list corresponding to the first event and the contact information of the fan on the second fan list corresponding to the second event.

[0022] [6-4] When an artist belongs as a member across multiple groups, including the first group and the second group, the member management unit manages the member by associating him with both the first group and the second group. The fan information management system according to [6-2] above, characterized in that the message sending unit sends the message to both the contact information of the fan in the fan list corresponding to the first group and the contact information of the fan in the fan list corresponding to the second group.

[0023] [6-5] If a member leaves the second group, the member management unit shall remove the association of the member with the second group. The fan information management system according to [6-4] above, characterized in that the fan list management unit does not send the message to the contact information of the fan in the fan list corresponding to the second group.

[0024] [7-1] A fan information management program for managing fan information of a group to which an artist belongs, using a fan information management device or fan information management system comprising at least one storage means, calculation means and display means, A member management step that manages members belonging to a group in association with the aforementioned group, An event management step that manages information about the events of the aforementioned group, A fan list management step involves compiling fan information related to the aforementioned event and managing it as a fan list. A fan information management program characterized by being executed by the fan information management device or the fan information management system.

[0025] According to this invention, it is possible to provide a fan information management program for managing fan information of a group to which an artist belongs, using the fan information management device described in [1] and the fan information management system described in [6].

[0026] [7-2] It also includes a message sending step for sending messages to fans, The aforementioned fan list management step manages the contact information of the fans as the fan information, The fan information management program according to [7-1] above, characterized in that the message sending step sends the message to the contact.

[0027] [7-3] The event management step manages multiple events, including the first event and the second event. The fan information management program according to [7-2] above, characterized in that the message sending step sends the message to both the contact information of the fan on the first fan list corresponding to the first event and the contact information of the fan on the second fan list corresponding to the second event.

[0028] [7-4] In the member management step, if an artist belongs as a member across multiple groups, including the first group and the second group, the member is managed by associating him with both the first group and the second group. The fan information management program according to [7-2] above, wherein the message sending step is characterized by sending the message to both the contact information of the fan in the fan list corresponding to the first group and the contact information of the fan in the fan list corresponding to the second group.

[0029] [7-5] In the member management step, if the member leaves the second group, the association of the member with the second group is removed. The fan information management program according to [7-4] above, characterized in that the fan list management step does not send the message to the contacts of the fans in the fan list corresponding to the second group.

[0030] [8-1] A fan information management device or fan information management system comprising at least one storage means, display means, and calculation means, for managing information about fans of a group to which an artist belongs, A member management step that manages members belonging to a group in association with the aforementioned group, An event management step that manages information about the events of the aforementioned group, A fan list management step involves compiling fan information related to the aforementioned event and managing it as a fan list. A fan information management method characterized by having the fan information management device or the fan information management system perform the operation.

[0031] According to this invention, it is possible to provide a fan information management method for managing fan information of a group to which an artist belongs, using the fan information management device described in [1] and the fan information management system described in [6].

[0032] [8-2] It further includes a message sending step for sending messages to fans, The aforementioned fan list management step manages the contact information of the fans as the fan information, The fan information management method according to [8-1] above, characterized in that the message sending step sends the message to the contact.

[0033] [8-3] The event management step manages multiple events, including the first event and the second event. The fan information management method according to [8-2] above, characterized in that the message sending step sends the message to both the contact information of the fan on the first fan list corresponding to the first event and the contact information of the fan on the second fan list corresponding to the second event.

[0034] [8-4] In the member management step, if an artist belongs as a member across multiple groups, including the first group and the second group, the member is managed by associating him with both the first group and the second group. The fan information management method according to [8-2] above, characterized in that the message sending step sends the message to both the contact information of the fan in the fan list corresponding to the first group and the contact information of the fan in the fan list corresponding to the second group.

[0035] [8-5] In the member management step, if the member leaves the second group, the association of the member with the second group is removed. The fan information management method according to [8-4] above, characterized in that the fan list management step does not send the message to the contact information of the fan in the fan list corresponding to the second group. [Effects of the Invention]

[0036] According to the present invention, it is possible to provide a fan information management device, a fan information management system, a fan information management program, and a fan information management method that can improve the convenience of managing fan information for artists who are active in a wide range of fields, including solo and group activities, and across groups. [Brief explanation of the drawing]

[0037] [Figure 1] This is a functional block diagram of the fan information management system according to the first embodiment. [Figure 2]This is an overall configuration diagram of the fan information management system according to the first embodiment. [Figure 3] This is a functional diagram showing an overview of the functions in the fan information management system. [Figure 4] This is a functional diagram showing an overview of the functions in the fan information management system. [Figure 5] This is a flowchart showing the processing flow in the fan information management system. [Figure 6] This is a flowchart showing the processing flow in the fan information management system. [Figure 7] This is the screen displayed on member terminal 40 (PC version). [Figure 8] This is the screen displayed on member terminal 40 (SP version). [Figure 9] This is a flowchart showing the processing flow in the fan information management system. [Figure 10] This is a functional diagram showing an overview of the functions in the fan information management system. [Figure 11] This is a functional diagram showing an overview of the functions in the fan information management system. [Modes for carrying out the invention]

[0038] One embodiment of the present invention will be described below with reference to the figures. Note that the components, arrangements, etc., described below are not limiting to the present invention and can be modified in various ways in accordance with the spirit of the present invention.

[0039] In this disclosure, "artist" refers to a person who expresses themselves in fields such as music, art, theater, film, and literature. "Group" refers to an organization to which one or more artists belong, and in the case of music, examples include bands and sessions. In this disclosure, even if an artist is a single person (solo), they can be registered as a group. "Event" refers to an artist's external activities, and in the case of music, examples include live performances and concerts. Furthermore, "information" provided to fans may include the date, time, location, and price of events, event reservations, and introductions and activities of the group or its members. Furthermore, the system disclosed herein can be used for events other than music events. For example, it can be used for any type of event that does not violate public order and morals, such as talk events, workshops, cultural shows, and community gatherings. In that case, the definitions of terms may be reinterpreted as follows, depending on the purpose of the event. (a) Artist: A person who posts information about their activities on this website. (i) Group: An organization that hosts an event. (c) Events: Events hosted by the group

[0040] The following describes a fan information management device and fan information management system according to one embodiment of the present disclosure. In this embodiment, the "group" in the present disclosure refers to a "band," "artist" and "member" refer to "band members," and "event" refers to a "live performance." In this example, the "fans related to the event" in the present disclosure refer to "fans who have made a reservation for the event," and "message" refers to "an email with a link to the reservation form."

[0041] As shown in Figure 2, the fan information management system 1 of this embodiment is a client / server type distributed system. The fan information management system 1 consists of an application server 10, a message transmission server 20, a database server 30, a member terminal 40, and an event participant terminal 50, which are interconnected via a network N. The application server 10, the message transmission server 20, and the database server 30 jointly constitute the fan information management device 2 (fan information management server 2).

[0042] Each server constituting the fan information management device 2 (application server 10, message transmission server 20, database server 30; hereinafter sometimes referred to as servers 10, 20, and 30) is composed of a computer. Each of these computers is equipped with a computing means such as a CPU, a storage means such as a hard disk or memory, an input means such as a touch panel or keyboard, and a display means such as a liquid crystal display. Although servers 10, 20, and 30 in this embodiment are composed of computers, they are not limited to computers and can be composed of any device that has server functionality.

[0043] Furthermore, in this embodiment, each terminal (member terminal 40, event participant terminal 50; hereinafter sometimes referred to as terminals 40 and 50) is composed of a computer equipped with a processing unit, storage device, input device, and display device, similar to servers 10, 20, and 30. Although terminals 40 and 50 in this embodiment are desktop computers, they are not limited to desktop computers and may also be notebook computers, tablet PCs, smartphones, mobile phones, or other mobile communication terminals.

[0044] The storage devices of servers 10, 20, and 30, and terminals 40 and 50, have the operating system, application software such as an internet browser, and software related to fan information management (applications, hereinafter sometimes simply referred to as "apps") installed. These devices then work together to execute programs and process information. The following describes servers 10, 20, and 30 and terminals 40 and 50.

[0045] (1) Application Server 10 The application server 10 has the function of performing various processes in response to requests from member terminals 40 and event participant terminals 50, and sending the results to these terminals. In addition, the application server 10 is connected to the message sending server 20 and the database server 30, and has the function of instructing each server to process and store information.

[0046] As shown in Figure 1, the application server 10 includes a communication unit 10a, a login status management unit 10b, an event management unit 10c, a message management unit 10d, a member management unit 10e, and a fan list management unit 10f. The communication unit 10a is capable of communicating with the message transmission server 20 and the database server 30, and has the function of communicating with member terminals 40 and event participant terminals 50 via the network N.

[0047] The login status management unit 10b has the function of managing logins for both members of the member terminal 40 and event participant terminals 50. Specifically, the login status management unit 10b manages user logins using IDs and passwords, maintaining login status, and termination of login status due to logoff, timeouts, etc. Event Management Department 10c is responsible for creating and deleting events such as live performances and sessions.

[0048] The message management unit 10d manages the creation, editing, and registration of messages to be sent to event participant terminals 50 via the message transmission server 20. The Member Management Department 10e manages the registration and deletion of members belonging to a group. The fan list management unit 10f manages the generation of fan lists stored in the database server 30, as well as the addition, modification, and deletion of fan information.

[0049] Next, we will describe the main functions performed within the application server 10. The application server 10 includes an event reservation input unit 10g for event (live) participants, an event creation unit 10h, a message creation unit 10i, a member editing unit 10j, and a fan list editing unit 10k for groups (bands). The event reservation input unit 10g has the function of receiving and processing event reservation information transmitted from the event participant terminal 50.

[0050] The event creation unit 10h has the function of creating and registering a new event based on event information transmitted from the event creation instruction unit 40c of the member terminal 40. Based on the event information, the event creation unit 10h creates a dedicated event page that contains the details of the event (group name, date and time, location, content, etc.). The message creation unit 10i has the function of creating messages, such as event reservation information, to be sent to the event participant terminal 50, based on instructions from the message management unit 10d. The Member Editorial Department 10j has functions for adding and removing group members, and modifying member information. The Fan List Editorial Department 10k adds or removes fans and modifies information about fans in the fan list registered in Fan List Information 30e.

[0051] (2) Message sending server 20 The message sending server 20 comprises a communication unit 20a and a message sending unit 20b. The communication unit 20a is connected to the application server 10, and transmits information via the communication unit 10a of the application server 10. The message transmission unit 20b has the function of receiving messages created by the message creation unit 10i of the application server 10 from the message management unit 10d and sending these messages to the event participant terminal 50.

[0052] (3) Database server 30 The database server 30 includes a communication unit 30a and various databases. These databases (hereinafter sometimes referred to as DB) include member information DB30b, event information DB30c, event participant information DB30c, and fan list information DB30e. The communication unit 30a is connected to the application server 10, and transmits information via the communication unit 10a of the application server 10.

[0053] The member information database 30b stores information about groups and their members, and this information is transmitted from the member management unit 10e of the application server 10. Member information stored in the member information database 30b can be edited, such as by deleting, adding, or modifying, according to instructions from the member management unit 10e.

[0054] The event information database 30c stores information about events created by the event creation unit 10h (such as group name, date and time, location, and content) as event pages, and this information is transmitted from the event management unit 10c of the application server 10. The event information stored in the event information database 30c can be edited, such as by deleting, adding, or modifying, according to instructions from the event management unit 10c.

[0055] The event participant information database 30d stores information such as the names and email addresses of event participants, associating them with unique event identification information. This information is transmitted from the event management unit 10c of the application server 10. The event participant information stored in the event participant information database 30d can be edited, such as by deleting, adding, or modifying, according to instructions from the event management unit 10c. The information in the event participant information database 30d is created for each event and is retained even after the event has ended, and is used for creating fan lists and other purposes.

[0056] The fan list information DB30e stores information about the group's fans, and this information is transmitted from the fan list management unit 10f. The fans in the fan list information DB30e are the event participants stored in the event participant information DB30d. As described later, as the number of events increases, the participants of each event are accumulated as fans and form a single list. The fan information stored in the fan list information DB30e can be edited, such as by deleting, adding, or modifying, according to instructions from the fan list management unit 10f. Alternatively, the fans in the fan list information DB30e may be created by extracting participants who actually attended the event from the event participants stored in the event participant information DB30d.

[0057] (4) Member terminal 40 (labeled "Artist terminal" in Figure 1) Member terminal 40 is a terminal operated by artists, such as group administrators or group members. Member terminal 49 is equipped with a communication unit 40a, a member registration unit 40b, an event creation instruction unit 40c, and a fan list selection unit 40d. The communication unit 40a has the function of communicating with the communication unit 10a of the application server 10 to send and receive various types of information.

[0058] The member registration unit 40b has the function of registering terminal users as members. The member registration unit 40b can register itself (a member) in association with a group, send invitations to other artists to join a group, or directly register members to a group. The member information registered by the member registration unit 40b is managed by the member management unit 10e of the application server 10.

[0059] The event creation instruction unit 40c has the function of outputting instructions to create an event to the application server 10, and can input event details (date and time, location, etc.). The fan list selection unit 40d has the function of selecting a fan list to send messages to fans, such as invitations to events. Information about events created by the event creation instruction unit 40c is managed by the event management unit 10c of the application server 10.

[0060] With this configuration, member terminals 40 can manage events, messages, and group members by logging into application server 10.

[0061] (5) 50 event participant terminals The event participant terminal 50 is a terminal operated by event participants and includes a communication unit 40a, an event display unit 50b, and an event reservation unit 50c. The communication unit 40a has the function of communicating with the communication unit 10a of the application server 10 to send and receive various types of information.

[0062] The event display unit 50b has the function of displaying event information transmitted from the application server 10. The event information includes information such as the group name, member names, date and time, location, and fee, as well as a reservation form for entering participants' names, addresses, email addresses, etc., and a participation button for joining the event. If there are companions in addition to the user, the reservation form also allows for entering the companions' names, email addresses, etc.

[0063] The event reservation unit 50c has the function of selecting a displayed event and applying to participate. By pressing the participation button, information such as the participant's name and email address entered in the reservation form is sent to the application server 10. When an event participant reserves participation in an event using the event reservation unit 50c, the participant's information is transmitted to the event management unit 10c of the application server 10 and stored in the event participant information DB 30d of the database server 30.

[0064] With this configuration, the event participant terminal 50 can receive event-related messages from the application server 10 and, in response, send event participant information such as the participant's email address to the application server 10. Furthermore, the event participant terminal 50 may be configured to either receive or not receive messages from the application server 10. For example, a fan operating the event participant terminal 50 can create a My Page and configure it to opt out (reject) emails from the application server 10. The My Page may be stored in the event participant information DB 30d. Alternatively, even without a personal account, you can set your email settings to reject incoming emails when reserving participation in an event using the Event Reservation Section 50c, etc. By doing so, fans can avoid receiving unsolicited information, and operations can be conducted in accordance with the Act on Specified Electronic Mail and the Act on Protection of Personal Information.

[0065] Next, we will explain the various functions and information flow in the fan information management system. Figure 3 is a conceptual diagram schematically showing each function of the created group. When a group (in this case, group a101) is created, members (in this case, artist A102a, artist B102b, and artist C102c) are registered according to the flow described later. Each member (artists A to C) can be added or deleted by the member management function 102. The member management function 102 is executed by the member management unit 10e in Figure 1.

[0066] The group has an event management function 103. The event management function 103 includes the following functions: event creation 103a, reservation form creation 103b, reservation acceptance 103c, reservation management 103d, and mass messaging 103e. Event creation 103a has the function of creating an event based on instructions from the event creation instruction unit 40c of the member terminal 40. Event creation 103a is executed by the event management unit 10c. Information on the created event is stored in the event information DB 30c of the database server 30 via the event management unit 10c of the application server 10.

[0067] Reservation form creator 103b has the function of creating reservation forms. The reservation reception unit 103c has the function of accepting reservations from event participants based on instructions from the event reservation unit 50c of the event participant terminal 50.

[0068] The reservation manager 103d has the function of managing event participants. Information on event participants whose reservations have been accepted by the reservation reception 103c is stored in the event participant information DB30d of the database server 30 via the event management unit 10c of the application server 10. The reservation manager 103d also manages cancellations of event participants, and if a cancellation occurs, it deletes the reservation holder's information from the event participant information DB30d. The creation of the reservation form 103b, the acceptance of reservations 103c, and the management of reservations 103d are all performed by the event management department 10c.

[0069] The mass message 103e has the function of sending a message to event participant terminals simultaneously. The mass message 103e is executed by the message management unit 10d. The mass message 103e sends the message created by the message creation unit 10i to the event participant terminals 50 via the message transmission unit 20b of the message transmission server 20.

[0070] The group has a fan list a104. Fan list a104 is a database that stores information about the fans of group a101, and is stored in the fan list information DB30e of the database server 30.

[0071] Next, we will explain how the fan list grows by holding multiple events. If group a101 has only recently been created and no events have been held, the fan list a104 will contain no fan information. When a member of group a101 creates an event (in this case, "Event 1": the first event) using event creation 103a and accepts reservations for it (S41), the information of the fans who made reservations is compiled into a list, and a new fan list 104a for Event 1 is created in fan list a104. In this embodiment, the fans registered in the fan list are those who made event reservations from the event participant terminal 50 and are stored in the fan list information DB. However, the fans are not limited to these; they can also be fans who actually participated in the event or fans recruited independently by the members.

[0072] After Event 1 (the first event) is completed, Event 2 (the second event) is to be held. When a member of group a101 creates a new event (in this case, Event 2) using event creation 103a and accepts reservations for it (S42), a new fan list 104b for Event 2 is created in fan list a104. The fan list 104a for Event 1 and the fan list 104b for Event 2 are merged into a single fan list. However, this disclosure is not limited to this, and fan lists 104a and 104b may be kept separately in the fan list information DB 30e. From this point onward, with each subsequent event, information about the new fans gained at each event will be registered in fan list a104, and the number of fans in fan list a104 will increase. After n events are held, fan lists for n events will be accumulated.

[0073] Next, we will explain the case where an artist belongs to another group. Figure 4 is a conceptual diagram that schematically shows the functions of multiple groups, the affiliations of their members, and the flow of information. Here, we will explain an example in which artist B, who is a member of group a101 (the first group), is also a member of group b111 (the second group) (S51 in the figure), and artist C, who is a member of group a101, is also a member of group c121 (S52).

[0074] As described above, group a101 (the first group) has a member management function 112, an event management function 113, and a fan list b114 (the first fan list). Similar to group a101, group b111 (the second group) also has a member management function 112, an event management function 113, and a fan list b114 (the second fan list). Fan list b114 stores the fan list 114a that group b111 has collected by independently holding events. Similarly, group c121 also has a member management function 122, an event management function 123, and a fan list c124. Fan list c124 stores the fan list 124a that group c121 has collected by independently holding events.

[0075] When Event 3 is to be held in group a101, the event management function 103 creates information for Event 3 as described above (S53). When sending a mass message to the event participant terminals 50 in Event 3 (S54), it is possible to select not only the fan list a104 of group a101, but also the fan lists of other groups to which members of group a101 belong, and send the message.

[0076] Artist B from group a101 also belongs to group b111, and artist C belongs to group c121. Therefore, a message can be sent simultaneously to fans in three fan lists: fan list a104, fan list b114, and fan list c124 (S55). Based on the sent message, for fans who reserve participation in event 3 through the reservation form from the event participant terminal 50, a new fan list 104c is created and merged with fan list a104.

[0077] In this way, it is possible to send messages to fans not only from the group an artist belongs to, but also from other groups they belong to, thereby increasing attendance at events.

[0078] (Flow for creating a new group) Next, the information processing flow in this system will be explained with reference to Figures 1 and 5-9. First, artists (members) register as new members with the application server 10 via the member terminal 40. When registering a new member, members enter member information such as their name, address, and email address, as well as login information such as their login ID and password. The entered member information is sent to the application server 10, where the member management unit 10e assigns a unique identification information (member ID), and it is stored in the member information DB 30b of the database server 30.

[0079] Next, one of the members creates a group on the member terminal 40 (S01 in Figure 5). The member creates the group by pressing the group creation button on the member terminal 40 and registering the required information (such as the group name). Furthermore, the member selects on the screen of the member terminal 40 whether or not to add members to the group (S02). If they choose to add members (Yes), they invite the members by entering the names, email addresses, IDs, invitation messages, etc. of the other members to be added (S03).

[0080] When an invited member logs into the application server 10, their member terminal 40 displays information indicating that they have been invited to the group. Alternatively, an email informing the member of the invitation is sent to their email address. The group invitation includes the group name, the name of the inviting member, and a button to accept joining the group. When this button is pressed, that information, along with the member's ID, is sent to the application server 10. The member management unit 10e of the application server 10 accesses the member information DB 30b of the database server 30 and stores the member's information, adding the group name, ID, and other information.

[0081] This makes the invited members members of the group. If no members are added (No in S02) or if all members have been added, the group creation is complete (S04). The member who initially created the group automatically becomes the group administrator, but the member management unit 10e can later change other members to group administrators. These steps S01 to S04 constitute the "member management step".

[0082] (Flow for selecting a fan list and sending a mass message) Next, referring to Figure 6, the flow of event creation and mass message sending will be explained. When any member wants to host an event (in this case, a live event), they first create a new event (in this case, Event 1) (S11 in Figure 6: Event Management Step). An event can be created on the member terminal 40 by entering event information (group, event name, event start date and time, event venue (location), participation fee, payment method, etc.) and system settings (reservation start date and time, reservation cancellation deadline date and time, reservation deadline date and time, provisional reservation validity period, maximum number of people accepted, maximum number of people on the waiting list, etc.) and pressing the Create Event button. When the Create Event button is pressed, an event page reflecting the event information and a reservation form are automatically created (S12). The contents of the event page and reservation form can be modified by the member on the member terminal 40 as needed.

[0083] Next, the user selects whether or not to send a mass message (S13). Figure 7(a) shows the display screen 60 on the member terminal 40 in the personal computer (PC) version. A menu area 61 is displayed on the left side of the screen, and an information display area 62 is displayed in the center. Menu area 61 contains a "My Page" button to display member registration information, a "Group" button to display group information, and a "Group" button to display event information.

[0084] The information display area 62 displays various information, such as event reservations and staff information. Within this area is a "Notification" button 62a for sending a mass message. Pressing this "Notification" button allows users to send a mass message. Figure 8(a) shows the display screen 70 of the member terminal 40 in the smartphone (SP) version. Similarly, in the SP version, the menu area 71 and information display area 72 are displayed, and mass messaging can be used by pressing the notification button 72a.

[0085] Returning to Figure 6, if mass messaging is not used (No in S13), event creation is complete. In this case, members will recruit attendees individually via email, flyers, etc. If mass messaging is used (Yes in S13), the groups to which members belong are checked (S14). In the example in Figure 4, artist B, who belongs to group a101, also belongs to group b111, and artist C also belongs to group c121. Next, we check the fan list for each group (S15). First, we check the fan list a104 for group a101. If there is no data in the fan list (No. in S16), we check for the existence of the fan list b114 for other groups to which members of group a101 belong (in this case, group b111 to which artist B belongs).

[0086] If a fan list exists for a group (Yes in S16), it is added to the list of fan lists to which messages will be sent (S17), and the process moves on to checking the fan list of the next group. This process is repeated until all members of the group have added the fan lists of other groups they belong to, and the fan list checking process ends when there are no more target fan lists (S19). In the example in Figure 4, fan list 104 of group a101, fan list 114 of group b111, and fan list 124 of group c121 will be added to the list.

[0087] Figure 7(b) shows the display screen 60 on the member terminal 40 in the PC version. The screen displays a fan list selection area 63a for selecting a fan list. In this example, three fan lists and checkboxes are displayed. By checking the checkboxes, you can select the fan list to which you want to send a message. In addition, a message input box 63b is displayed on the display screen 60, where you can enter a message to send as a mass message.

[0088] Figure 8(b) shows the display screen 70 of the member terminal 40 in the SP version. Similarly, in the SP version, the fan list selection area 73a and the message input box 73b are displayed, allowing users to select a fan list and enter a message, respectively.

[0089] Returning to Figure 6, selecting a fan list and entering a message will send a mass message (S21). The mass message includes the message entered in the message input box 63b, as well as a URL or QR code (registered trademark) to the event page and a link to the reservation form. Before sending the mass message, the system checks for duplicates in the fan list (S22). In the example in Figure 4, it checks whether there are any duplicate fans in fan lists a104 to c124. Duplicates can be checked by comparing information such as name, address, and email address; if one or more items match, it can be considered a duplicate.

[0090] Next, it is checked whether a message has already been sent to each fan list (S23). If a message has not been sent (No), a message is sent to the fans in that fan list (S25). In this embodiment, a mass message is sent via email to the email addresses that are contacts stored in the fan list. However, the mass message is not limited to this, and may also be sent by mail or other means to the registered address (contact).

[0091] If a message has already been sent (Yes in S23), the system checks whether the message has been sent to the next fan list. This allows the system to sequentially send messages to fans registered in multiple fan lists. In the example in Figure 4, messages are sent in the order of fan list a104 → fan list b114 → fan list c124. Messages are not sent to fans who have already received a message because it is a duplicate (S26). The above process allows you to send messages to the fans on the fan list. This completes the creation of the event (S27).

[0092] (Flow of accumulating fan information in the fan list) Next, referring to Figure 9, we will explain the flow of how the fan list increases with each event. When an event is created, members independently send emails with links to the reservation form to acquaintances and others to attract attendees. Also, as mentioned above, they send a mass message with a link to the reservation form to fans on their fan list (S31). When an event participant makes a reservation for the event using the reservation form, the system checks whether that event participant is already registered on the fan list (S33). If the fan who made the reservation for the event is not registered on the fan list (No), the event participant is newly registered on the fan list (S34: Fan List Management Step); if they are already registered (Yes), they are not registered. Next, the information of that event participant is stored in the event participant information DB30d using the reservation manager 103d function in Figure 3 (S35).

[0093] (New launch) Next, referring to Figure 10, we will explain the case where an artist creates a new group. When artist B, who belongs to groups a101 and b111, creates a new group d131 (S71), the fan list d134 for group d131 does not yet contain any fan data. In this case, when group d131 creates a new event 3 (S73), the mass message can be sent (S74) to the fan list a104 of group a101, to which artist B belongs, and to the fan list b114 of group b111 (S75). As a result, fans who have reserved event 3 through the reservation form will be registered as new fans in the fan list d134.

[0094] (Leaving the group) Next, referring to Figure 11, we will explain the case where an artist leaves a group. Artist B belongs to groups a101 and b111 (S61), and artist C belongs to groups a101 and c121 (S62). We will now explain the case where artist C leaves group c121. In this case, when group a101 creates a new event 3 (S63), when sending a mass message (S64), it is not possible to select the fan list c124 of group c121, from which artist C has left. This prevents artists who leave a group from using the group's fan list, thus preventing problems after their departure. Furthermore, even if artist C leaves group c121, if fans of group c121 made reservations for group a101 events prior to artist C's departure, those fans will be recorded in group a101's fan list a104. Therefore, even after artist C leaves group c121, those fans will remain registered in group a101's fan list and can continue to attract fans of group a101 through messaging and other means.

[0095] In summary, according to this disclosure, artists can be managed on a group basis, and fan information stored in the fan list can be utilized in various situations such as live events. [Explanation of Symbols]

[0096] 1 Fan information management system, 2 Fan information management server (fan information management device), N Network, 10 Application server, 10a Communication unit, 10b Login status management unit, 10c Event management unit, 10d Message management unit, 10e Member management unit, 10f Fan list management unit, 10g Event reservation input unit, 10h Event creation unit, 10i Message creation unit, 10j Member editing unit, 10k Fan list editing unit, 20 Message sending server, 20a Communication unit, 20b Message sending unit, 30 Database server, 30a Communication unit, 30b Member information DB, 30c Event information DB, 30d Event participant information DB, 30e Fan list information DB, 40 Member terminal, 40a Communication unit, 40b Member registration unit, 40c Event creation instruction unit, 40d Fan list selection unit, 50 Event participant terminal, 50a Communication unit, 50b Event display unit, 50c Event reservation unit, 60 Screen, 61 Menu area, 62 Information display area, 62a Notification button, 63a Fan list selection area, 63b Message input box, 70 Screen, 71 Menu area, 72 Information display area, 72a Notification button, 73a Fan list selection area, 73b Message input box

Claims

1. A fan information management device for managing information about fans of an artist's group, A member management department manages members belonging to a group in association with the aforementioned group, The event management department manages information related to the events of the aforementioned group, A fan information management device characterized by comprising: a fan list management unit that lists fan information related to the aforementioned event and manages it as a fan list.

2. It also features a message sending function for sending messages to fans. The aforementioned fan list management unit manages the contact information of the aforementioned fans as information about the aforementioned fans. The fan information management device according to claim 1, characterized in that the message transmission unit transmits the message to the contact.

3. The aforementioned event management unit manages multiple events, including the first event and the second event. The fan information management device according to claim 2, characterized in that the message transmission unit transmits the message to both the contact information of the fan on the first fan list corresponding to the first event and the contact information of the fan on the second fan list corresponding to the second event.

4. The member management unit manages the member in association with both the first group and the second group when the artist belongs as a member across multiple groups, including the first group and the second group. The fan information management device according to claim 2, characterized in that the message transmission unit transmits the message to both the contact information of the fan in the fan list corresponding to the first group and the contact information of the fan in the fan list corresponding to the second group.

5. The member management unit, when a member leaves the second group, removes the association of the member with the second group. The fan information management device according to claim 4, characterized in that the fan list management unit does not send the message to the contact information of the fan in the fan list corresponding to the second group.

6. A fan information management system for managing information about fans of the group to which an artist belongs. It includes member terminals operated by members belonging to the group, event participant terminals operated by participants attending events, and a fan information management server for managing fan information. The aforementioned member terminal is The member registration section registers members belonging to a group and associates them with the group, It includes an event creation instruction unit that issues instructions for creating group events, The event participant's terminal is, An event display unit that displays information about the event, The system includes an event reservation unit for reserving participation in events displayed on the event display unit, The aforementioned fan information management server is A member management unit manages the members registered by the member registration unit in association with the group, An event management unit that manages information regarding the group's events created by the event creation instruction unit, A fan information management system characterized by comprising: a fan list management unit that lists the information of participants who have reserved participation in the event by the event reservation unit as fan information and manages it as a fan list.

7. A fan information management program for managing fan information of a group to which an artist belongs, using a fan information management device or fan information management system comprising at least one storage means, a calculation means and a display means, A member management step that manages members belonging to a group in association with the aforementioned group, An event management step that manages information about the events of the aforementioned group, A fan list management step involves compiling fan information related to the aforementioned event and managing it as a fan list. A fan information management program characterized by being executed by the fan information management device or the fan information management system.

8. A fan information management device or fan information management system comprising at least one storage means, display means, and calculation means, for managing fan information of a group to which an artist belongs, and a fan information management method for managing fan information of a group to which an artist belongs. A member management step that manages members belonging to a group in association with the aforementioned group, An event management step that manages information about the events of the aforementioned group, A fan list management step involves compiling fan information related to the aforementioned event and managing it as a fan list. A fan information management method characterized by having the fan information management device or the fan information management system perform the operation.

Images