Management device, management method, and program

Abstract

Direct communication between users participating in the event, and between users and performers. To provide technology that makes it possible to take. [Solution] A memory unit that stores event information about the event to be held, and performers And the management of channels, which are communication tools established on an event-by-event basis. The department obtains ticket information regarding the event tickets owned by the user. By matching the ticket information with the event information, the user can obtain the ticket. It has an ownership verification unit that verifies ownership, and the management unit controls the event Users who have been confirmed to possess the ticket and performers at the event will be given the aforementioned ticket. A management device is provided that allows posting to a channel and viewing posts on the channel.

Description

Technical Field

[0001] The present invention relates to a management device, a management method, and a program.

Background Art

[0002] Currently, various events using real venues such as live shows and sports are being held. Also, when issuing tickets for events, concerts, etc., a ticket issuing system that enables easy receipt of tickets has been disclosed (Patent Document 1).

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] By purchasing tickets for an event and participating in the event, users can feel the performers up close. Such a real experience can only be obtained by users who actually participate in the event. Also, in order for users participating in the event to feel the performers even closer and to reduce the distance between users and the distance between users and performers, a mechanism that enables direct communication between users participating in the event and between users and performers is required.

[0005] Therefore, an object of the present invention is to provide a technology that enables direct communication between users participating in an event and between users and performers.

[0006] <<ID=54>>

Means for Solving the Problems

[0006] A management device according to one aspect of the present invention records event information regarding events to be held. It is a memory-based system and a communication tool established on a per-performer and per-event basis. The management unit manages the channels and the ticketing of the event tickets owned by the user. By obtaining ticket information and matching the obtained ticket information with the event information, The system includes an ownership verification unit that verifies that the user possesses the ticket, and the management The department has confirmed that users possess tickets to the aforementioned event and the event The performers are permitted to post to and view posts on the aforementioned channel. [Effects of the Invention]

[0007] According to the present invention, users participating in the event and users and performers can communicate directly with each other. It becomes possible to remove the unit. [Brief explanation of the drawing]

[0008] [Figure 1] This figure shows an example of a communication management system according to this embodiment. [Figure 2] This figure shows an example of the hardware configuration of the management server. [Figure 3] This figure shows an example of the functional block configuration of the management server. [Figure 4] This figure shows an example of an event management database. [Figure 5] This figure shows an example of an account management database. [Figure 6] This figure shows an example of a ticket management database. [Figure 7] This figure shows an example of a channel management database. [Figure 8] This figure shows an example of a post management database. [Figure 9] It is a diagram showing an example of the processing procedure performed by the management server. [Figure 10] It is a diagram showing an example of the processing procedure performed by the management server. [Figure 11] It is a diagram showing an example of a screen for ticket registration. [Figure 12] It is a diagram showing an example of a posting display screen.

Mode for Carrying Out the Invention

[0009] Embodiments of the present invention will be described with reference to the accompanying drawings. In each figure, those assigned the same reference numerals have the same or similar configurations.

[0010] <System Configuration> FIG. 1 is a diagram showing an example of a communication management system 1 according to the present embodiment. The communication management system 1 includes a management server 10 (also referred to as a management device), one or more terminals 20, and a blockchain network 30. The management server 10, one or more terminals 20, and the blockchain network 30 are connected via a wireless or wired communication network N and can communicate with each other.

[0011] The communication management system 1 is a system that provides a service (hereinafter referred to as the "communication service" that enables communication between the performers of an event and the participants who purchase tickets and participate in the event, and between the participants who purchase tickets and participate in the event). Heretofore, it has been possible for the performers of an event to convey a message to the participants by transmitting information via SNS or the like. However, the information transmitted via SNS can be viewed not only by the event participants but also by an unspecified large number of people. However, the information transmitted via SNS can be viewed not only by the event participants but also by an unspecified large number of people. Because it was a Noh play, there was a problem in that it was difficult to understand who the information was addressed to. Also, event participation Even if a person posts on social media, it can be viewed not only by the performers but also by an unspecified number of people. Therefore, information known only to event participants will be disseminated to an unspecified number of people. There was a problem.

[0012] Therefore, the communication management system 1 according to this embodiment communicates The content is made public to the outside, or the content of the communication is not made public to the outside. While providing a good condition, it can be confirmed that you possess a ticket to participate in the event. Between the participants and performers, and between the participants who were confirmed to possess tickets. It enables direct communication.

[0013] In the following explanation, users who utilize communication services will be referred to as "users." Users include performers and staff of the event (such as performers' managers and those involved in event management). This includes people (including performers and related personnel) and users other than performers and related personnel (hereinafter referred to as "general users"). Furthermore, when referring to a user who is also a performer, it should be written as User (Performer) or Performer. When referring to a related party among the attendees, please write "User (Related Party)" or "Related Party". Also, performers If there is no distinction between stakeholders and general users, simply write "user".

[0014] An "event" is one in which performers are present and participation is open to those who possess an event ticket. It is an event. Specifically, the event includes live performances, concerts, shows, movies, and plays. This includes talk shows, sports matches, esports matches, etc. Note that performances are special events. This means that performers perform at a specific venue for a set period of time. This includes events held online in addition to events held at physical venues. It is also acceptable to do so if multiple performances are held under the same title, such as in a tour. An "event" can refer to a tour unit or a performance unit.

[0015] Furthermore, among general users, it is confirmed that they possess tickets to participate in the event. Users who have been confirmed to own a ticket are called "ticket-owning users," and it is confirmed that they own a ticket. Users who have not been verified and users who do not possess a ticket are referred to as "Users without a ticket". That's what they say.

[0016] In this embodiment, the management server 10 communicates performers and ticket holders over the internet. A tool that enables two-way communication between users (hereinafter referred to as "channel") It will be provided. The channel will allow users to post text, images, audio, and video, etc. Any channel is fine, if available. Channels include, for example, social media. This includes bulletin boards, SNS (Social Networking Services), and video sharing services. .

[0017] Channels are created on a per-performer and per-event basis, and include channels for performers, staff, and ticket holders. Users can post messages that include any text, images, and videos. For example, an event X held in Tokyo in which performer A (e.g., artist A) will perform (example) An event held in Osaka featuring performer B (e.g., artist B) and performer B. If there is a channel Y (for example, Live Y), then different channels will be opened for each. Yes.

[0018] Furthermore, if multiple performers appear in one event, each performer will be broadcast on a different channel. A channel may be created, or a channel common to multiple performers may be created. For example, performers The same event X (for example, a rock festival) is held in which A, B, and C perform. In that case, the channel of performer A regarding event X, and the channel of performer B regarding event X. Alternatively, channels could be created for each performer C regarding Event X. A common channel for performers A through C regarding Event X may be established. If there is a group of performers, a separate channel may be created for each performer. Channels may be opened on a group basis. Also, performer X may perform in performance A, performance B and public If you are conducting a tour Y that includes performance C, the channels will be like the channels for performer X and tour Y. Alternatively, one channel may be created for each performer and tour, or a channel for performer X and performance A. Channels for performer X and performance B, and channels for performer X and performance C, etc. Multiple venues may be established for each performance.

[0019] Furthermore, the timing of channel creation and termination is arbitrary. For example, The channel will be opened on the event start date or a specified date before the event start date, and will close after the event ends. It may also be decided that the program will end a specified number of days after the scheduled start date.

[0020] The management server 10 performs various processes related to the provision of channels. For example, the management server 10 This is a communication management system that manages the posting of messages on channels. Account management for using the service, and pages that users refer to (web pages and app screens). Provides services such as displaying pages on the website.

[0021] Terminal 20 is a terminal used to access the management server 10, for example, Examples include smartphones, tablet devices, mobile phones, and personal computers (PCs). It is possible.

[0022] Blockchain Network 30 manages NFTs (Non-Fungible Tokens) The contract is executed. Management server 10 receives an NFT indicating participation in the event. It issues and grants it to ticket holders. The NFT issued by management server 10 is for performers And it may be at the event level (i.e., at the channel level), or at the event level. Good. Ticket holders will be granted NFTs, which proves they are fans of the performers. It can be proven.

[0023] <Hardware Configuration> Figure 2 shows an example of the hardware configuration of the management server 10. The management server 10 is C Processors such as PU (Central Processing Unit) and GPU (Graphics Processing Unit) 11. Memory (for example, RAM (Random Access Memory) or ROM (Read Only Memory)) )), storage devices such as HDDs (Hard Disk Drives) and / or SSDs (Solid State Drives) 12. Network Interface (IF) for wired or wireless communication 13. Input operation It has an input device 14 that receives data and an output device 15 that outputs information. Examples include a keyboard, touch panel, mouse, and / or microphone. Output device 1 5 is, for example, a display, touch panel and / or speaker.

[0024] <Functional Block Configuration> Figure 3 shows an example of the functional block configuration of the management server 10. The management server 10 is described as follows: Memory unit 100, management unit 101, ownership confirmation unit 102, assignment unit 103, display control unit 10 4 includes. The storage unit 100 is implemented using the storage device 12 provided by the management server 10. This is possible. In addition, the management unit 101, ownership verification unit 102, assignment unit 103, and display control unit are also included. 104 refers to the program stored in the storage device 12, which is processed by the processor 11 of the management server 10. This can be achieved by executing [this]. Furthermore, the program can be stored on a storage medium. It is possible. The storage medium containing the program is computer-readable. It may be a non-transitory computer-readable medium. Temporary storage media are not particularly limited, but for example, USB (Universal Serial Bus) memory It may also be a storage medium such as a CD-ROM (Compact Disc Read-Only Memory).

[0025] The memory unit 100 stores information about the event to be held (event information). To access the vent management DB100a and the website provided by the management server 10 The account management DB100b manages the accounts, and tickets owned by general users. The ticket management DB100c manages information, and the system manages information about channels that are currently open. The channel management DB100d and the data posted to the channel (text, image data, It stores the post management DB100e, which stores video data, etc.

[0026] Management Department 101 is a communication tool established on a per-performer and per-event basis. It manages a certain channel. Specifically, the management unit 101 manages posts to the channel and the channel It manages the viewing of posts. Also, when the management unit 101 receives a post to the channel, The submitted data is stored in the submission management DB100e. The management unit 101 also handles the channel. When a user requests to view posted data on the board, the post management DB100e retrieves the posted data. Retrieve the data and display it on the screen of device 20.

[0027] Furthermore, when the management unit 101 accepts posts to a channel and views of posts in a channel, Check whether they have the necessary permissions. For example, Management Department 101 owns the event ticket. Ticket holders and event performers who have been confirmed to have engaged in such activities will be subject to restrictions on posting to the channel and Allow viewing of channel posts.

[0028] The ownership verification unit 102 checks the event tickets owned by users participating in the event. By obtaining ticket information and matching the obtained ticket information with event information, The system verifies that the user possesses a ticket.

[0029] The granting unit 103 is a smart contract that operates on the blockchain network 30. Instruct them to issue an NFT to indicate participation in the event. 103 blocks ticket-owning users who are determined to possess event tickets. Information regarding participation in an event (e.g., event name) should be included in the chain wallet. An NFT is assigned that includes the event date and time and the names of the performers, etc. Furthermore, the assignment unit 103, A badge image will be given to ticket holders as proof of their participation in the event. The image on the badge may also be called an icon.

[0030] The display control unit 104 displays various screens for realizing communication services to the terminal. Display it on 20. Note that the display control unit 104 may be included in the management unit 101.

[0031] Figure 4 shows an example of the event management DB 100a. The event ID is used when the event is held. This indicates an ID that uniquely identifies the event. Event information is used to identify the event that will be held. Includes specific information that identifies the event. The date and time of the event are the date the event is held and the start time of the event. The time is indicated. The venue indicates the location where the event will be held. The event name is the event's The name is shown. The performer ID is an ID that uniquely identifies the performer. It may also include the performer's name corresponding to the performer ID. The seat number list is for the event. Information regarding all seat numbers in the venue (for example, for each of rows A through F) This indicates that there are seats numbered from 1 to 30.

[0032] Figure 5 shows an example of the account management DB100b. The user ID is a community This indicates an ID that uniquely identifies a user registered with the communication service. Login information is: Login information for logging into a communication service (e.g., login ID and This shows the user's (password) and user attributes. User attributes are the attributes of the user (performers, related parties, and general users). It indicates either of the following. Digital badge information (NFT) indicates that general users will participate in the event. If an NFT indicating addition has been granted, the token ID of the granted NFT will be stored. If an NFT is not assigned, the digital badge information (NFT) will contain nothing. It is not stored. Digital badge information (badge image) does not show which event a general user participated in. The ID of the badge image indicating whether it was added is stored. The image of the badge is used in communication. It will be displayed on the service screen, corresponding to a regular user. If a badge is awarded If not present, nothing will be stored in the digital badge information (badge image).

[0033] Figure 6 shows an example of ticket management DB100c. User ID (General User) This indicates an ID that uniquely identifies a regular user. The ticket ownership status indicates whether a regular user has a ticket. This indicates whether or not the ownership of the ticket has been confirmed. "Confirmed" means that the general user has confirmed ownership of the ticket. This indicates that ownership of the ticket has been confirmed. "Under review" means the uploaded ticket... When the image data is being analyzed or reviewed by an administrator, general users may not be able to access it. This indicates that they are verifying that you own the ticket. "Error" means that a regular user is trying to verify the ticket. This indicates that it could not be confirmed that the user owns the item. The Event ID is described below. This shows the event ID identified from the event identification information. Ticket information includes the user's ownership Various information about the ticket is stored. Event-specific information is stored in the ticket image data. This shows event identification information that uniquely identifies the event, as read from the data. The specific details of the report will be described later. The seat number is the seat number indicated on the ticket. The ticket image data contains the image data uploaded to the management server 10. It can be done.

[0034] Figure 7 shows an example of the channel management DB100d. The channel ID is created This indicates an ID that uniquely identifies the channel. User IDs (performers, related parties) are used in communications. I, a unique identifier for performers and related personnel among the users registered in the production management system 1. D is indicated. The Event ID is an ID that uniquely identifies the event. The URL is opened. This shows the URL to access the channel. The start date and time is when the channel is opened. This indicates the date and time of opening. The end date and time indicates the date and time when the channel opening will end (be closed). If it's an event with multiple performers, a separate channel may be created for each performer. Alternatively, it may be opened for multiple performers in common. In the former case, for the same event ID... Multiple different channel IDs will be associated. On the other hand, in the latter case, the same event One channel ID will be associated with each entry ID.

[0035] Figure 8 shows an example of the post management DB100e. The channel ID is the channel being opened. The channel ID is a unique identifier for the channel. The post ID is a unique identifier for the posted data. The posting date and time indicates the date and time the posted data was submitted to the channel. User ID (poster) This stores the ID of the user who posted the data to the channel. For example, if a performer posts... In that case, the poster ID will store the user ID of the performer. Also, the ticket holder user When a post is made, the poster ID will contain the user ID of the ticket-owning user.

[0036] Viewing restrictions indicate whether or not viewing of a post is restricted. In this embodiment, posting to the channel The article contains posts that can only be viewed by a limited number of users (hereinafter referred to as "restricted posts") and... This includes posts that are not restricted in their viewing (hereinafter referred to as "regular posts"). For drafts, "None" is set; for posts that are restricted, "Restricted" is set; The submitted data includes submitted text data, image data, audio data, and / or video data. Data such as "Ta" is stored. Note that limited users (hereinafter referred to as "limited users") can use the ticket This may include users who own tickets and performers at the event. Alternatively, limited users may purchase tickets. This includes users who own the game, performers at the event, and people involved with the event. In other words, "Limited users" refers to a limited number of users, including ticket holders and event performers. It may be justified.

[0037] "Post Attributes" indicates the attributes of the post. In this embodiment, posts to a channel have special attributes. Posts and non-special posts may be included. Special posts can be posted by paying a fee. Messages may also be included. For example, special posts may include images, audio, or video. It may be a message, but is not limited to this. Another example is a special message. Special posts are displayed with higher priority than non-special posts on the list of posts screen. A manuscript is acceptable. On the other hand, a regular submission can be submitted without payment. Messages are also acceptable. For example, non-special posts include images, audio, and video. Messages may be text-only, but are not limited to this. In another post, the "Post Attributes" column will store "Special" as the post's attribute. For posts that are not special, the "Post Attributes" column will store "Normal" as the post attribute.

[0038] Whether a post is special or not applies to both regular and restricted posts. In this embodiment, posts are classified as regular posts (not special), limited posts (not special), and special regular posts. It may be divided into four types: regular posts and special, limited-access posts.

[0039] <Processing Procedure> Figure 9 shows an example of the processing procedure performed by the management server 10. Using Figure 9, the management server This section describes the various processes performed on the communication service provided by -ver10. .

[0040] In step S100, the management unit 101 determines the user who will use the communication service. The system processes login information by accepting it from the user. Management unit 101 accepts login information from the user. The entered login ID and password are compared with the account management DB100b. The login process is then initiated. If the login is complete, proceed to step S101 and log in. If it fails, the process will terminate.

[0041] In step S101, the logged-in user selects ticket registration by operating the screen. If you do so, proceed to step S102. If you do not select ticket registration, Proceed to the processing procedure for step S104.

[0042] In step S102, the ownership verification unit 102 receives ticket information from the terminal 20 used by the user. The system retrieves information and verifies whether the user owns a ticket. Specifically, it checks the user's status. This is an image of a paper ticket, or a screenshot of an electronic ticket, The data is uploaded (registered) from the end 20 to the management server 10. The ownership verification unit 102 confirms that the user The system retrieves image data of the ticket it owns. Next, the ownership verification unit 102 retrieves the ticket By processing the image data with OCR (Optical Character Recognition), the ticket can be converted to By reading the characters written and performing named entity recognition on the read string, The lock information is extracted. The ownership verification unit 102 then performs OCR processing on the image data. Alternatively, a computer that has been trained to output ticket information when an image of a ticket is input. You can also use a learning model to extract ticket information. The service administrator may visually read the ticket information. In this case, ownership The verification unit 102 reads the ticket visually from the communication service administrator. You may allow the system to accept input information.

[0043] Furthermore, if it is possible to purchase tickets within the communication service, that is If the management server 10 issues a ticket itself, the ownership verification unit 102 will verify the issued ticket. Retrieve ticket information for tickets owned by the user from the database that manages ticket information. You may do so.

[0044] Furthermore, ticket purchase data may be stored on other servers that manage ticket sales information (for example, other servers). If it is possible to obtain it from the server of the play guide operated by the company, etc., the ownership verification department 102 retrieves information about the tickets issued from other servers that manage the information about the tickets the user owns. You could also try to retrieve the ticket information.

[0045] Next, the ownership verification unit 102 reads the ticket information from the image data, and the following information is included in it: Event identification information that uniquely identifies an event, and the event information contained in the event management DB100a The event information is cross-referenced with the event information, and the specific event information matches the specific information contained in the event information. If this is the case (i.e., if the event can be uniquely identified), the user will be able to purchase the event ticket. We have determined that we have confirmed ownership of the item.

[0046] On the other hand, the ownership verification unit 102 identifies the event information that is included in the event information. If it does not match (i.e., the event cannot be uniquely identified), the user can use the event It may be decided that the person could not be confirmed to possess a ticket. Furthermore, the ownership verification unit 102 will inform the administrator of the communication service of the ticket You may also request that the image data be visually inspected. The ownership verification unit 102 is a management If the organizer notifies the user that the user possesses an event ticket, the user We have determined that you possess a ticket for the event.

[0047] Furthermore, the ownership verification unit 102 confirms that the ticket owner has the ticket. For the event management database 100a, retrieve the event ID corresponding to the ticket. Next, Management Department 101 will process the acquired event ID, event identification information, and ticket information. The seat number is stored in the ticket-owning user's record in ticket management DB100c.

[0048] Event identification information and event management DB100a read from ticket image data Specific information included in the event information may include, for example, the date and time of the event, the location, and / or it may be the event name. For example, the ownership verification unit 102 is the image data of the ticket. Event identification information read from the data (event date and time, location and event name) Specific information included in the event information of event management DB100a (event date and time, If the venue and event name match, the user owns the event ticket. It may also be possible to determine that it has been confirmed that it is being done. This is event identification information (event date and time and event information) read from the ticket image data. Event name) and specific information included in the event information of event management DB100a (event name) If the date, time, and event name match, the user will own the event ticket. It may also be possible to determine that it has been confirmed that it is doing so. 2 is event identification information (event name) read from the ticket image data and event The specific information (event name) included in the event information of the event management DB100a matches. In such cases, the user will be able to determine that they possess an event ticket. You can do that.

[0049] Furthermore, the specific information included in the event identification information and event holding information also includes performers. It may also include the following. For example, the ownership verification unit 102 may further use the ticket image data. The performer names read are those included in the event information in the event management DB100a. If included, the user is deemed to have confirmed that they own an event ticket. You may do so.

[0050] Furthermore, the specific information included in the event identification information and event holding information also includes seat numbers. The number may be included. For example, the ownership verification unit 102 may further include the ticket image data. The seat number read from the event management DB100a is the seat number included in the event information. If included in the number list, the user can confirm that they own a ticket for the event. It may be possible to determine that this is the case. This would result in fraudulent entries of non-existent seat numbers. This will make it possible to eliminate unnecessary tickets.

[0051] Furthermore, if tickets are sold within the communication service, the tickets will include the event information. It is possible to include an ID. Therefore, if the event ID is printed on the ticket... In total, the specific information included in the event identification information and event holding information is the event ID. It may be done as follows. In this case, the ownership verification unit 102 reads from the ticket image data. The event identification information (event ID) and the event holding information in the event management DB100a are used. If the included specific information (event ID) matches, the user can access the event ticket. It may be considered that ownership has been confirmed.

[0052] Furthermore, when selling tickets within a communication service, or when purchasing tickets... If it is possible to obtain input data from another server that manages ticket sales information In conclusion, the ownership verification unit 102 determines that the user possesses the ticket, and proceeds to step S1. The processing step in step 02 may be omitted, and the process may proceed to the processing step in step S103.

[0053] Here, the ownership verification unit 102 further uses the ticket seat information to upload You may also want to ensure that the downloaded ticket is not a ticket that has already been registered. Furthermore, the ownership verification unit 102 will check if the uploaded ticket is already registered. If it is confirmed that the user does not have a ticket, the user will be deemed to own an event ticket. You may do so.

[0054] Specifically, the ownership verification unit 102 further includes the event information contained in the ticket information. Seat information that uniquely identifies a seat is obtained from ticket image data acquired from other users. If it is not the same as the designated seat information (i.e., if the seat information is not duplicated), The system may determine that the person owns the event ticket. Section 102 contains seat information that uniquely identifies a seat at an event, which is included in the ticket information. However, it is identical to the seat information identified from the ticket image data obtained from other users. In the case of duplicate seat information, the user owns the event ticket. It may be possible to determine that there is no duplicate ticket. This would prevent multiple users from submitting the same ticket. This eliminates the need to register.

[0055] In step S103, the management unit 101 acquires the ticket in the processing procedure of step S102. For ticket-owning users who have been confirmed to be doing so, from ticket management DB100c Next, retrieve the event ID corresponding to the ticket owned by the ticket holder. Then, the management unit 101 accesses the channel management DB 100d and the corresponding event ID Obtain the channel URL and send the obtained URL to the ticket-owning user's device 20. Furthermore, if multiple channels are opened for the same event, the management unit 101 will manage multiple U This will result in obtaining the RL. For example, in the example in Figure 7, if the event ID was E100 In addition, the management unit 101 will obtain the URL of the channel whose channel ID is C110, and the channel ID This will result in obtaining two pieces of information: the URL of the channel which is C210. ​​Next, Management Unit 10 1 sends the acquired URL to the ticket-owning user's device 20. If there are multiple URLs, the management unit 101 sends the multiple URLs to the ticket-owning user's terminal 20. I believe.

[0056] In addition to sending the URL to the terminal 20, the management unit 101 also sends the user The channel list screen, which displays a list of channels corresponding to tickets owned by the user, is displayed on terminal 20. You can also have it displayed there.

[0057] In step S104, the management unit 101, if the user selects to browse channels, If you access the URL, or if you select a channel from the channel list screen, Proceed to step S105. If the user did not select to browse channels, Proceed to the processing procedure for step S109.

[0058] In step S105, the management unit 101 receives the user's selection of the channel they wish to view. To attach. For example, when a user accesses a URL, the management unit 101 will... Alternatively, the management unit 101 may be configured to recognize that a channel has been selected. You may also allow users to select the channel they wish to view from the screen. If the user accesses the URL of a channel that has not yet started or has already ended, the management unit 101 will The message displayed at the end indicates that the accessed channel is either not yet started or has ended. You could also display it on the last 20 screens.

[0059] In step S106, the management unit 101 checks the posted messages that have been posted to the selected channel. The message is displayed on the screen of terminal 20. Specifically, the management unit 101 displays the post management DB 100. From e, configure posting data and viewing restrictions for the channel selected in step S105. The value is retrieved. Next, the management unit 101 displays the posted data as a list on the screen of terminal 20. .

[0060] Here, the management unit 101 provides regular posts and limited access to restricted users of the channels they are viewing. You may also allow viewing of the posts. In addition, the management unit 101 will determine the channels to be viewed. Allowing regular posts to be viewed by users other than restricted users (i.e., users without tickets). You can also choose not to allow access to restricted posts.

[0061] When the management unit 101 displays the posted data in a list on the screen of terminal 20, the channel management DB Access 100d and obtain the event ID of the channel you want to view and the user ID of the performer. To benefit. Next, the management unit 101 refers to the account management DB 100b, Check the attributes of the character.

[0062] Management Unit 101, if the user's attribute is "General User", further, Ticket Management DB By referring to the "Ticket Ownership Status" of 100c, general users can view the channels they are interested in. Check whether the user owns the ticket or not. For example, Admin Section 101, regarding the record of the event ID of the channel being viewed, states "Ticket Office A regular user whose status is "Available" is "Confirmed" is a ticket-owning user, and "Ticket Ownership A regular user whose "Status" is "Under Review" or "Error" is considered a user without a ticket. You may make a judgment. Also, in the ticket management DB100c, the event of the channel to be viewed For general users for whom no record matching their ID and user ID exists, the user will be considered a ticket-less user. It can be concluded that it is a 'za'.

[0063] Furthermore, if the user's attribute is "performer" or "related party", the management unit 101 will channel Refer to the management DB100d and find that the user ID of the user in question is the "user" of the channel being viewed. Check whether the user is included in "The ID (Performers, Staff)". If included, the user If it is determined that the user is a performer or related party of the channel being viewed, and is not included, then the user will Therefore, we will determine that the person is not a performer or related party of the channel being viewed. In the latter case, contact Management Department 101 This means that the user will be treated as a user without a ticket in the channel being viewed. You may do so.

[0064] Next, the management unit 101 retrieves the post management DB 100e from the target channel for viewing. The draft data and access restriction settings are obtained. Subsequently, the management unit 101 determines the user's access targets. If you are a "performer," "related party," or "ticket holder" of the channel, you are eligible to view. Posts on the channel with viewing restrictions set to "None" and "Limited" and display on the screen of terminal 20. Meanwhile, the management unit 101 controls the channel that the user is viewing. If you are a "user without a ticket," then the posts in the channel you are viewing will not have viewing restrictions. The posted data set to "shi" is displayed on the screen of device 20, and the data set to "limited" is displayed. The submitted data will not be displayed on the screen of terminal 20. (Note: Management Department 101) Regarding post data with viewing restrictions set to "limited," if post data exists... It is possible to recognize it, but it is not possible to view or output the posted data itself (for example, text or images). The image may be displayed on the screen of terminal 20 by masking it, etc.

[0065] Furthermore, the management unit 101 controls the restricted users and non-restricted users of the channels being viewed. (That is, all users) are allowed to view both regular posts and special regular posts. It may be made possible.

[0066] In step S107, the management unit 101 sends a message when the user operates the screen. If you select "Post," proceed to step S108. If so, proceed to the processing procedure in step S109.

[0067] In step S108, the management unit 101 receives submissions from users. The management unit 101 The system then associates the posted data obtained from the user's terminal 20 with the user ID of the user (poster). It is then stored in the post management database.

[0068] Here, the management unit 101 restricts the channel of the target of viewing (which may also be called the target of posting) For The, new regular posts and new limited posts will be posted to the channels that are being viewed. Allow. Meanwhile, the management unit 101 allows users other than the limited users of the channel to be viewed ( For users who do not own a ticket, regular posts and restricted posts on the target channel will be posted. You can choose not to allow any of these posts.

[0069] The management unit 101 can access the account management DB 100b to see which users are logged in. Check the user's attributes. Also, if the user's attributes are those of a general user, the management unit 101 will check the user's attributes. By referring to ticket management DB100c, the user can view tickets for the channel they are viewing. Check whether the user owns the ticket or not. Next, Management Department 101 , if the user is a performer, staff member, or ticket holder of the channel being viewed ( If you are a limited user, you can ask the user whether they want to post limited posts or regular posts. The system accepts the user's choice of whether or not to restrict access, and then associates the accepted access restriction settings with the posted data to manage the posting. It is stored in DB100e. Meanwhile, the management unit 101 checks the channel that the user is viewing. If you are a user who does not own a ticket (i.e., a user other than a restricted user), you will not be able to post. Avoid hitting them.

[0070] Furthermore, Management Department 101 will provide users with information on performers, staff, and tickets for the channels they are viewing. If you are the owner user (i.e., a limited user), a regular post that is not special, special You can accept regular posts, non-special limited posts, and special limited posts. The management department 101 associates the settings for viewing restrictions, the settings for posting attributes, and the posting data when posting. Store in management DB100e.

[0071] Furthermore, the management unit 101 will inform users who do not possess a ticket for the channel in question about the channel in question. You can allow regular posts to Nell but not restricted posts. Furthermore, Management Unit 101 will also provide special instructions to users who do not possess tickets for the channels being viewed. I will allow regular posts (not special ones), but I will not allow special regular posts. You can do that.

[0072] In step S109, the management unit 101 terminates the process if the user selects logout. If you do not select "OK" and log out, return to step S101.

[0073] Figure 10 shows an example of the processing procedure performed by the management server 10. Using Figure 10, Server 10 grants ticket holders a badge indicating they participated in the event. The processing procedure in Figure 10 is explained below. Note that the timing of executing the processing procedure in Figure 10 is arbitrary. For example, this may be done when closing a channel, or after the event has ended. This may be done before closing. In the following description, a badge will be used when closing the channel. This will be explained as granting the property.

[0074] In step S200, the granting unit 103 possesses a ticket corresponding to the channel to be closed. Extract the users. Specifically, the assignment unit 103 refers to the channel management DB 100d. Next, the assignment unit 103 obtains the event ID corresponding to the channel to be closed. Then, the assignment unit 103 obtains the ticket Refer to the ticket management DB100c and find the "ticket ownership status" corresponding to the retrieved event ID. Extract users who have been "verified".

[0075] In step S201, the granting unit 103 determines that the extracted ticket holders are block chain It checks whether a wallet has been opened for the user. For example, the granting unit 103 extracts... Enter the blockchain wallet address into the ticket-owning user's device 20. The granting unit 103 will display a screen that shows the ticket holder user's wallet. If you enter the address, the ticket holder will be assumed to have already opened a wallet. Proceed to step S202, where it is determined that the ticket holder does not have a wallet address. If you select this option, the ticket holder will be deemed not to have opened a wallet and will proceed to the next step. Proceed to step S203. Alternatively, the assignment unit 103 assigns to the account management DB 100b. By checking whether the let's address is registered, the extracted ticket holders It would be good to have the system check whether or not a blockchain wallet has already been opened. stomach.

[0076] In step S202, the granting unit 103 grants the blockchain wallet of the ticket-owning user. We will assign an NFT to each user that contains information about their participation in the event. Specifically, The granting unit 103 grants to the smart contract of the blockchain network 30, An NFT is generated by issuing a method to issue an NFT, and the token of the generated NFT is... The ID is the digital record of the ticket-owning user in the account management DB100b. The badge information (NFT) is stored. The granting unit 103 also grants the ticket to the ticket-owning user. Batch images are assigned. Specifically, the assignment unit 103 assigns the image ID corresponding to the batch image. The "digital batch" of the record of the ticket-owning user in the account management DB100b Stored in "Information (badge image)".

[0077] In step S203, the granting unit 103 refers to the account management DB 100b and the user The "Digital Badge Information (NFT)" in the record indicates that an NFT can be issued. The granting unit 103 also grants a batch image to the ticket-owning user. Specifically, the assignment unit 103 assigns the image ID corresponding to the batch image to the account management DB 100. In the record of the ticket-owning user in b, the "Digital Badge Information (Badge Image)" is To deliver.

[0078] In step S204, the granting unit 103 grants the user's terminal 20 the right to open a wallet. Send a prompt message.

[0079] <Screen display example> Figure 11 shows an example of a screen for registering tickets. Screen W10 shows the ticket This is the registration screen. When B10 is pressed, you will be prompted to select an image of the ticket. A screen will appear. The selected ticket image will be displayed in the image display area P10. When the submit button B11 is pressed, the ticket image is uploaded to the management server 10. Once ticket registration is complete and it is confirmed that the user owns the ticket, the screen will appear. The screen will transition to W20. Screen W20 will show the channels for events you can participate in with your registered ticket. A list of items will be displayed.

[0080] Figure 12 shows an example of a post display screen. The selected chat on screen W20 in Figure 11 Nell's posts are displayed in chronological order on the post display screen W30. Post messages M30 and M31 is a regular post message, and post message M32 is a limited post message. This is a message. Posted message M32 is restricted from being viewed, therefore its content cannot be displayed. It is not possible. For example, if the user is a ticket holder, performer, or related party, the posted message In Sage M32, a button B32 appears that displays messages that are otherwise restricted from being viewed. Also, if the user does not have a ticket, message M32 will display button B3. You can choose not to display 2, or to make it so that button B32 cannot be pressed (grayed out). ) may be displayed, or even if button B32 is pressed, the content of the posted message M32 will not be displayed. It is acceptable to avoid showing it.

[0081] When button M32 is pressed, the post message M3 will be displayed as shown on the post display screen W40. The content of item 2 will be displayed.

[0082] Additionally, if the user is a ticket holder, performer, or related party, the post will be displayed on screen W3. Button 0 displays the message submission button B30 and the special message submission button B31. On the other hand, if the user does not own a ticket, buttons B30 and B31 will not be displayed. It may be possible to prevent this from happening, or to configure the buttons B30 and B31 in a way that prevents them from being pressed (Gray It may be displayed as (out), or the posted image may be displayed even if buttons B30 and B31 are pressed. It is also possible to avoid transitioning to surface W50.

[0083] When the message submission button B30 or the special message submission button B31 is pressed, The user is redirected to the posting screen W50. The posting screen W50 contains an area N50 where the user enters the content to be posted. It will be displayed. Also, on the posting screen W50, the user will be able to see the ticket holder, performer, and related parties. If you are a user, the button to post a message that is restricted from being viewed will appear in the post message M32. Button B50 and button B51 for posting an unrestricted message are displayed.

[0084] <Variation> (Variation 1) The ownership verification unit 102 further verifies that the user who owns the ticket actually participated in the event. You may also want to confirm that you own a ticket and that you actually attended the event. Users who have been confirmed to have participated are called "event participants" and own tickets. Users who have not been confirmed to be participating in the event, and those who possess tickets but will not be attending the event. Users who did not participate may be referred to as "non-event participants." In the various processes described, ticket-owning users and ticket-non-owning users are treated as follows: This can be replaced with "Event Participants" and "Event Non-Participants."

[0085] In the processing procedure of step S102, terminal 20, in addition to the ticket image, actually displays the event You may also upload information that can confirm your participation. Section 102 includes information that confirms actual participation in the event, in addition to the ticket image. By verifying that the information is correct, we can confirm that the user participated in the event. You can do that.

[0086] Information that can confirm actual participation in the event is, for example, pre-assigned information for each event venue. It may be predetermined information. Specifically, information from a designated location within the event venue. The image may be a photograph taken in the direction specified, or a photograph taken of a specified object located within the event venue. The image was a photograph of an object (for example, a seating chart or a seat number written on a chair). It is also acceptable to include the event information in the event management DB100a for each event venue. The pre-specified information is stored, and the ownership verification unit 102 uploads it from terminal 20. The information provided, along with the information pre-specified for each event venue stored in the event information, The system will then compare the data, and if both entries match, it will be determined that the user actually participated in the event. That's good too.

[0087] (Modification 2) The login process in step S100 is performed on a server other than the management server 10. It may also be done as follows. For example, in this embodiment, the login process for each user is performed externally. This can also be implemented using an SSO (Single Sign-On) service. 101 received login information from users of the communication service. Transfer the request to another server and retrieve the login result (success / failure) from that server. That's good too.

[0088] (Variation 3) In this embodiment, instead of "seat number," information that can uniquely identify the ticket is used. This prevents multiple users from registering the same ticket multiple times. Alternatively, the "seat number" in this embodiment may be defined as "information that can uniquely identify the ticket." This can be read as "report". Information that uniquely identifies a ticket is, for example, a string and / or It may consist of a combination of numbers. Also, information that uniquely identifies the ticket should be organized. A number is also acceptable. Please note that the reference number will be different for each ticket. For example, it is used to specify the order in which visitors enter a venue.

[0089] (Modification 4) In this embodiment, the system automatically provides a watch to users of the communication service. A Let could be established. For example, an account for a communication service. Creating a wallet may require opening one. In this case, Steps S200, S201, S203 and S204 The processing steps may be omitted.

[0090] (Modification 4) In this embodiment, the term "stakeholders" may be omitted. In this case, communication There will be two types of users who use the service: performers and general users.

[0091] <Summary> According to the embodiments described above, the management server 10 is opened on a per-performer and per-event basis. It manages channels, which are communication tools, and owns event tickets. Users and event performers who have been confirmed to be posting to the channel in question will be subject to restrictions on posting to the channel. The manuscript has been made available for viewing. This will allow users participating in the event to interact with each other, as well as users and performers. It becomes possible for individuals to communicate directly with each other.

[0092] Furthermore, the management server 10 reads ticket information from the ticket image data. By reading ticket information from the ticket image data, the ticket was issued. Even if the ticketing method differs for each company conducting the event, the ticket information must be obtained. This becomes possible. For example, if the ticket is in paper form, the management server 10 is equipped with terminal 20. It will be possible to read ticket information from an image of the ticket taken with a camera. Furthermore, if the ticket is an electronic ticket, the management server 10 will check the screen equipped on terminal 20. The photo capture function will allow ticket information to be read from the resulting image.

[0093] Furthermore, the management server 10 allows both regular posts and restricted posts to be posted to the channel, and restricted Posts will be viewable only by limited users (e.g., performers and ticket holders). This has made it so that users other than authorized users (users without tickets) cannot view it. For example, performers and ticket holders can also use the information of performers and users who actually participated in the event. It allows us to share information that others may not know, making the performers feel more approachable, and also contributes to the event. This will enable closer communication among participating users.

[0094] The embodiments described above are provided to facilitate understanding of the present invention and do not limit the present invention. It is not intended to be interpreted in that way. The flowcharts, sequences, and actuals described in the embodiments The elements of the construction form, as well as their arrangement, materials, conditions, shape, and size, are examples only. It is not limited to this and can be modified as appropriate. Also, the structure shown in different embodiments It is possible to partially substitute or combine the components. [Explanation of symbols]

[0095] 1 Communication management system, 10 Management servers, 11 Processors, 12 13 Storage device, 14 Network interface, 15 Input device, 20 Terminal, 3 0 Blockchain network, 10 Management server, 100 Storage unit, 101 Management Unit 102 Ownership Confirmation Unit 103 Assignment Unit 104 Display Control Unit

Claims

1. A memory unit that stores event information about events that will be held, The channel is a communication tool established on a per-performer and per-event basis. The management department, The system retrieves ticket information related to the event tickets owned by the user, and retrieves the ticket information. By matching the ticket information with the event information, it can be determined that the user owns the ticket. The ownership verification unit confirms that the person is, It has, The aforementioned management department has confirmed that users and previous users possess tickets to the aforementioned event. The performers of the event will be permitted to post to and view posts on the aforementioned channel. do, Management device.

2. The aforementioned event information includes specific information that uniquely identifies the event. The aforementioned ownership verification unit is Obtain image data of the ticket owned by the aforementioned user, The event included in the ticket information read from the aforementioned image data is uniquely identified. The event identification information to be determined is matched with the event holding information, If the aforementioned event identification information matches the identification information included in the aforementioned event holding information The user is determined to possess a ticket for the event. The control device according to claim 1.

3. The aforementioned ownership verification unit further, The seat information included in the aforementioned ticket information, which uniquely identifies the seat for the aforementioned event, The seat information identified from the ticket image data obtained from the user is not the same as the aforementioned seat information. In that case, the user is determined to possess a ticket for the event. Seat information that uniquely identifies a seat at the event, included in the ticket information. However, the seat information identified from the ticket image data obtained from other users is identical. In some cases, it is determined that the user does not possess a ticket for the event. The control device according to claim 2.

4. The posts on the aforementioned channel include comments from users who have been confirmed to possess tickets to the aforementioned event. Limited posts that can only be viewed by a select group of users, including the performers of the aforementioned event, and This includes regular posts that are not restricted in terms of viewing, The management unit allows the restricted users to view the regular posts and the restricted posts. Allowing users other than the aforementioned limited users to view the regular posts before Viewing of restricted posts is not permitted. The control device according to claim 1.

5. The management unit shall allow the limited users to post regular posts to the channel and Allows posting of restricted content, and prevents users other than the restricted users from posting to the channel. In contrast, regular posts and restricted posts will not be permitted. The control device according to claim 4.

6. The regular posts on the aforementioned channel include special regular posts that can be posted by the aforementioned limited users. It is included, The management unit shall, for the limited users and users other than the limited users, Allow viewing of the aforementioned special regular posts. The control device according to claim 4.

7. The blockchain wallet of a user who was determined to possess a ticket for the aforementioned event The granting unit grants an NFT to the net containing information about its participation in the aforementioned event. , has, The control device according to claim 6.

8. The steps include storing event information about the event to be held in the memory unit, The channel is a communication tool established on a per-performer and per-event basis. Steps to manage, The system retrieves ticket information related to the event tickets owned by the user, and retrieves the ticket information. By matching the ticket information with the event information, it can be determined that the user owns the ticket. The steps to confirm that this is happening, Includes, The aforementioned management step involves confirming that the user possesses a ticket for the event. To the performers of the aforementioned event, regarding posts to the aforementioned channel and posts to the aforementioned channel Allow viewing. The management method performed by the management device.

9. On the computer, The steps include storing event information about the event to be held in the memory unit, The channel is a communication tool established on a per-performer and per-event basis. Steps to manage, The system retrieves ticket information related to the event tickets owned by the user, and retrieves the ticket information. By matching the ticket information with the event information, it can be determined that the user owns the ticket. The steps to confirm that this is happening, Make it run, The aforementioned management step involves confirming that the user possesses a ticket for the event. To the performers of the aforementioned event, regarding posts to the aforementioned channel and posts to the aforementioned channel Allow viewing. program.

Images