Program, method and information processing device

Abstract

To provide a program for further improving a relationship between performers and fans in an event where the number of participants is limited.SOLUTION: A program for operating a computer, causes a processor of the computer to execute the steps of: acquiring not a ticket purchase history for participating in an event where the number of participants is limited due to a size of a venue, but information regarding user behavior taken by a user related to a performer of the event; and outputting a first parameter for the user on the basis of the information regarding the user behavior.SELECTED DRAWING: Figure 20

Description

Technical Field

[0001] The present disclosure relates to a program, a method, and an information processing apparatus.

Background Art

[0002] There is a technology for improving the relationship between performers who appear in an event and fans.

[0003] For example, Patent Document 1 describes a technology in which when a viewing user performs a promotion operation on a distribution user, points corresponding to the amount of action according to the promotion operation are given, the points given are added to the acquired points stored in the memory, and a first reward corresponding to the added acquired points is given to the viewing user. Thereby, it is said that the willingness of the viewing user to view the video of the distribution user can be improved.

[0004] In Patent Document 1, a distribution user who is a performer distributes a video to a viewing user who is a fan on a distribution site. Such a video distribution event on a distribution site has no limit on the number of participants.

[0005] On the other hand, in an event where there is an upper limit on the number of participants due to the size of the venue, if the number of applicants for event participation exceeds the upper limit of the number of participants who can participate, a lottery is conducted, and participation tickets are sold to the winners. Since popular events have a high scarcity of tickets, there are cases where tickets can be resold to other users at a high price. Therefore, there is an increasing number of users who apply for the lottery for the purpose of reselling, even though they are not fans. Then, tickets do not reach the fans who really want to participate in the event, and the opportunity to participate in the event and improve the relationship between the performer and the fans is lost.

Prior Art Documents

Patent Documents

[0006]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0007] For the above reasons, in an event with a limited number of participants, there is a need for a technology to further improve the relationship between performers and fans.

[0008] In view of the above problems, an object of the present invention is to further improve the relationship between performers and fans in an event with a limited number of participants.

Means for Solving the Problems

[0009] A program for operating a computer, which causes a processor of the computer to execute steps of: obtaining information regarding user actions taken by a user related to an event performer, rather than a purchase history of tickets for participating in an event with an upper limit on the number of participants due to the size of the venue; and outputting a first parameter for the user based on the information regarding the user actions.

Effects of the Invention

[0010] According to the present disclosure, in an event with a limited number of participants, the relationship between performers and fans can be further improved.

Brief Description of the Drawings

[0011]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

Figure 19

Figure 20

Figure 21

Mode for Carrying Out the Invention

[0012] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings. In the following description, the same parts are denoted by the same reference numerals. Their names and functions are also the same. Therefore, detailed descriptions thereof will not be repeated.

[0013] <Summary> The system according to this embodiment acquires information regarding actions taken by the user in relation to the performer (particularly, actions taken by the user as a fan of the performer), and outputs a first parameter for the user according to the information. The system grants a privilege to the user according to the first parameter. The privilege is, for example, a privilege for increasing the user's opportunity to participate in an event in which the performer appears. Thereby, the relationship between the event performer and the user can be improved according to the actions taken by the user who is a fan of the performer in relation to the performer.

[0014] In this embodiment, an event is an event in which there is an event performer and fans who support the performer. The events in this embodiment include, for example, the following events. In this embodiment, the event may be an event with an upper limit on the number of participants due to the size of the venue, or may be an event held at an actual venue. · Music events such as concerts and live shows · Sports events such as ball games, swimming, and martial arts (including professional leagues and amateur competitions) · Game convention · Entertainment events including stage plays, stand-up comedy, rakugo, and other performing arts

[0015] In the present embodiment, the performers include those who perform arts, acting, or performances in a predetermined event, and athletes who participate in sports events and game conventions.

[0016] In the present embodiment, the first parameter is a numerical value related to the relationship between the performer and the user. The system according to the present embodiment visualizes the record of the actions taken by the user in relation to the performer (user actions) as the first parameter. User actions include actions taken by the user as a fan of the performer.

[0017] In the present embodiment, the users include users who are fans of the performer and users who are not fans of the performer.

[0018] <1 Configuration diagram of the entire system> FIG. 1 is a block diagram showing an example of the overall configuration of the system 1. The system 1 shown in FIG. 1 includes, for example, a terminal device 10, a server 20, and a distributed ledger system 90. The terminal device 10, the server 20, and the distributed ledger system 90 are communicatively connected via, for example, a network 80.

[0019] In the present embodiment, there may be a plurality of terminal devices 10 included in the system 1.

[0020] In the present embodiment, a collection of a plurality of devices may be regarded as one server. The way of distributing the plurality of functions required to implement the server 20 according to the present embodiment for one or a plurality of hardware can be appropriately determined in consideration of the processing capabilities of each hardware and / or the specifications required for the server 20.

[0021] The terminal device 10 shown in FIG. 1 is an information processing device operated by a user. The terminal device 10 is realized by, for example, a mobile terminal such as a smartphone or a tablet. The terminal device 10 may be a stationary PC (Personal Computer) or a laptop PC. The terminal device 10 may also be a wearable terminal such as an HMD (Head Mount Display) or a wristwatch-type terminal.

[0022] The terminal device 10 includes a communication IF (Interface) 12, an input device 13, an output device 14, a memory 15, a storage 16, and a processor 19. The input device 13 is a device for receiving an input operation from a user (for example, a pointing device such as a touch panel, a touch pad, a mouse, etc., a keyboard, etc.). The output device 14 is a device for presenting information to the user (a display, a speaker, etc.).

[0023] The server 20 shown in FIG. 1 is an information processing device that receives a connection from the terminal device 10 and executes processing requested by the terminal device 10. The server 20 is, for example, an information processing device realized by a computer connected to a network 80. As shown in FIG. 1, the server 20 includes a communication IF 22, an input / output IF 23, a memory 25, a storage 26, and a processor 29. The input / output IF 23 functions as an interface between an input device for receiving an input operation from a user and an output device for outputting information to the user.

[0024] The distributed ledger system 90 manages a distributed ledger. As an example, the distributed ledger system 90 manages the history of transactions related to the transfer of cryptographic assets or tokens (which may include NFTs (Non-Fungible Tokens)). In particular, the distributed ledger system 90 manages digital content in association with NFTs by a distributed application realized using a predetermined smart contract. For example, the smart contract is executed in response to a request from the terminal device 10. The management of digital content may include at least one of the following. ·Issuance of NFTs associated with digital content ·Transfer of NFTs from the wallet of the issuer of digital content (such as the service operator, event operator, performer, etc. according to the present disclosure) to other wallets ·Transfer of NFTs from other wallets to the wallet of the issuer

[0025] The distributed ledger is, for example, a blockchain. The distributed ledger system 90 includes a plurality of computers (which may include the terminal device 10) connected to each other.

[0026] <1.1 Configuration of the terminal device> FIG. 2 is a block diagram showing a configuration example of the terminal device 10 shown in FIG. 1. As shown in FIG. 2, the terminal device 10 includes a communication unit 120, an input device 13, an output device 14, an audio processing unit 17, a microphone 171, a speaker 172, a camera 160, a position information sensor 150, a storage unit 180, and a control unit 190. Each block included in the terminal device 10 is electrically connected, for example, by a bus or the like.

[0027] The communication unit 120 performs processes such as modulation / demodulation processing for the terminal device 10 to communicate with other devices. The communication unit 120 performs transmission processing on the signal generated by the control unit 190 and transmits it to the outside (for example, the server 20). The communication unit 120 performs reception processing on the signal received from the outside and outputs it to the control unit 190.

[0028] The input device 13 is a device for a user operating the terminal device 10 to input instructions or information. The input device 13 is realized, for example, by a touch-sensitive device 131 in which an instruction is input by touching an operation surface. When the terminal device 10 is a PC or the like, the input device 13 may be realized by a keyboard, a mouse, etc. The input device 13 converts the instruction input by the user into an electrical signal and outputs the electrical signal to the control unit 190. Note that the input device 13 may include, for example, a reception port for receiving an electrical signal input from an external input device.

[0029] The output device 14 is a device for presenting information to the user who operates the terminal device 10. The output device 14 is realized by, for example, a display 141 or the like. The display 141 displays data according to the control of the control unit 190. The display 141 is realized by, for example, an LCD (Liquid Crystal Display), an organic EL (Electro-Luminescence) display, or the like.

[0030] The audio processing unit 17 performs, for example, digital-to-analog conversion processing of an audio signal. The audio processing unit 17 converts the signal given from the microphone 171 into a digital signal and gives the converted signal to the control unit 190. Also, the audio processing unit 17 gives the audio signal to the speaker 172. The audio processing unit 17 is realized by, for example, a processor for audio processing. The microphone 171 receives an audio input and gives an audio signal corresponding to the audio input to the audio processing unit 17. The speaker 172 converts the audio signal given from the audio processing unit 17 into audio and outputs the audio to the outside of the terminal device 10.

[0031] The camera 160 is a device that receives light by a light receiving element and outputs it as a shooting signal.

[0032] The position information sensor 150 is a sensor that detects the position of the terminal device 10 and is, for example, a GPS (Global Positioning System) module. The GPS module is a receiving device used in a satellite positioning system. In the satellite positioning system, signals from at least three or four satellites are received, and based on the received signals, the current position of the terminal device 10 equipped with the GPS module is detected. The position information sensor 150 may detect the current position of the terminal device 10 from the position of the wireless base station to which the terminal device 10 is connected.

[0033] The storage unit 180 is realized by, for example, a memory 15 and a storage 16 or the like, and stores data and programs used by the terminal device 10. The storage unit 180 stores, for example, user information 181 and ticket information 182.

[0034] User information 181 includes information about the user who uses the terminal device 10, for example. Information about the user includes, for example, a user ID. The user information 181 may include an email address, a wallet address, and the like.

[0035] Ticket information 182 is, for example, information on an electronic ticket downloaded to the terminal device 10. The ticket information 182 includes, for example, a ticket ID of the ticket. The ticket information 182 may include a user ID of the user who owns the ticket and an event ID of the event related to the ticket.

[0036] The control unit 190 is realized by the processor 19 reading a program stored in the storage unit 180 and executing instructions included in the program. The control unit 190 controls the operation of the terminal device 10. By operating according to the program, the control unit 190 functions as an operation reception unit 191, a transmission / reception unit 192, and a presentation control unit 194.

[0037] The operation reception unit 191 performs processing for receiving an instruction or information input from the input device 13. Specifically, for example, the operation reception unit 191 receives an instruction or information input from the touch-sensitive device 131 or the like.

[0038] In addition, the operation reception unit 191 receives a voice instruction input from the microphone 171. Specifically, for example, the operation reception unit 191 receives a voice signal input from the microphone 171 and converted into a digital signal by the voice processing unit 17. The operation reception unit 191 obtains an instruction from the user, for example, by analyzing the received voice signal and extracting a predetermined noun.

[0039] The transmission / reception unit 192 performs processes for the terminal device 10 to transmit and receive data from an external device such as the server 20 according to a communication protocol. Specifically, for example, the transmission / reception unit 192 transmits information input by the user or an instruction from the user to the server 20. Also, the transmission / reception unit 192 receives information provided from the server 20.

[0040] The presentation control unit 194 controls the output device 14 to present predetermined information to the user. Specifically, for example, the presentation control unit 194 causes the display 141 to display information regarding the user's actions related to the user. Also, the presentation control unit 194 causes the display 141 to display information regarding a predetermined event. Also, the presentation control unit 194 causes the display 141 to display information regarding digital content associated with the user's actions.

[0041] <1.2 Functional Configuration of Server> FIG. 3 is a diagram showing an example of the functional configuration of the server 20. As shown in FIG. 5, the server 20 functions as a communication unit 201, a storage unit 202, and a control unit 203.

[0042] The communication unit 201 performs processes for the server 20 to communicate with an external device.

[0043] The storage unit 202 has, for example, a user table 202a, a performer table 202b, an event table 202c, a ticket table 202d, an application history table 202e, an NFT type table 202f, an NFT management table 202g, a point condition table 202h, and the like. The tables stored in the storage unit 202 are not limited to these. For example, the storage unit 202 may store a table for accumulating the history of the user's actions.

[0044] The user table 202a is a table that stores information regarding the user. Details will be described later.

[0045] The performer table 202b is a table that stores information regarding the performer. Details will be described later.

[0046] The event table 202c is a table that stores information about events. Details will be described later.

[0047] The ticket table 202d is a table that stores information about event participation tickets. Details will be described later.

[0048] The application history table 202e is a table that stores information about the history of event participation applications. Details will be described later.

[0049] The NFT type table 202f is a table that stores information about the types of NFTs. In this embodiment, an NFT associated with predetermined digital content is assigned to a user who has performed a specific user action. For example, an NFT for proving that a user has visited a specific event is assigned to a user who has visited the event. In this case, the NFTs assigned to the users are distinguished from each other by the serial numbers associated with the NFTs. In this way, NFTs that are distinguished from each other by serial numbers are defined as NFTs of the same type. Note that, in the information associated with NFTs of the same type, information other than the serial number may be different for each NFT.

[0050] Note that, in this embodiment, by creating different tables for each performer as the NFT type table 202f, the NFT types are managed for each performer. Specifically, an NFT type table 202f-A is created for performer A, and an NFT type table 202f-B is created for performer B. For example, when defining a new type of NFT for performer A, a new record is added to the NFT type table 202f-A.

[0051] The NFT management table 202g is a table that stores information about NFTs. Details will be described later. In this embodiment, by creating different tables for each NFT type as the NFT management table 202g, information about NFTs is managed for each NFT type. Specifically, for the NFT with the NFT type ID "C001", the NFT management table 202g-C001 is created, and for the NFT with the NFT type ID "C002", the NFT management table 202g-C002 is created, respectively.

[0052] The point condition table 202h is a table that stores information about the conditions for points given to a predetermined NFT type when calculating the first parameter. Details will be described later. In this embodiment, different tables are created for each event held as the point condition table 202h. For example, for event A, the point condition table 202h-A is created, and for event B, the point condition table 202h-B is created, respectively.

[0053] The control unit 203 is realized by the processor 29 reading the program stored in the storage unit 202 and executing the instructions included in the program. By operating according to the program, the control unit 203 exhibits the functions shown as the reception control module 2031, the transmission control module 2032, the event management module 2033, the ticket management module 2034, the behavior information acquisition module 2035, the parameter calculation module 2036, the lottery module 2037, and the presentation control module 2038.

[0054] The reception control module 2031 controls the process of the server 20 receiving a signal from an external device according to the communication protocol.

[0055] The transmission control module 2032 controls the process of the server 20 transmitting a signal to an external device according to the communication protocol.

[0056] The event management module 2033 manages information on events related to the services of the present disclosure. Specifically, the event management module 2033 receives the registration of information on each event transmitted to the server 20 and updates the event table 202c.

[0057] The ticket management module 2034 manages information on tickets for participating in events. Specifically, the ticket management module 2034 receives the registration of information related to applications for events, information related to lottery results of tickets, information related to purchases of tickets, information related to transfers of tickets, etc., and updates the ticket table 202d.

[0058] The behavior information acquisition module 2035 acquires information on user behaviors taken by a user in relation to event performers. In particular, the behavior information acquisition module 2035 acquires information on user behaviors taken by a user as a fan of event performers. Specifically, the information on user behaviors includes information for identifying the user who took the user behavior and information for identifying the type of NFT related to the user behavior. The information on user behaviors includes, for example, identification information of the user behavior, the user ID of the user related to the user behavior, and the NFT type ID related to the NFT related to the user behavior (the NFT type ID of the NFT assigned to the user who took the user behavior). Note that the behavior information acquisition module 2035 may not acquire information on the purchase history of tickets for participating in an event with an upper limit on the number of participants due to the size of the venue as information on user behaviors.

[0059] The action information acquisition module 2035 may acquire information regarding user actions shown below, for example. As a result, it becomes possible to assign NFTs to users who have taken the user actions shown below, and the achievements of user actions can be treated as irreplaceable assets. Furthermore, although details will be described later, the control unit 203 calculates a first parameter based on the NFTs assigned to the users. Therefore, the control unit 203 can acquire information regarding the user actions shown below and calculate the first parameter based on the acquired information.

[0060] Note that the action information acquisition module 2035 may acquire information regarding user actions for a predetermined one or more types of user actions among the user actions shown in this disclosure. Also, the action information acquisition module 2035 may not acquire information regarding user actions for a predetermined one or more types of user actions among the types of user actions shown in this disclosure. The types of user actions for which information is acquired may vary depending on the event operator, performer, etc.

[0061] Also, the control unit 203 may be the target for NFT assignment and / or the target for calculation of the first parameter for a predetermined one or more types of user actions among the user actions for which information has been acquired by the action information acquisition module 2035. Also, the control unit 203 may not be the target for NFT assignment and / or the target for calculation of the first parameter for a predetermined one or more types of user actions among the user actions for which information has been acquired by the action information acquisition module 2035. The types of user actions that are the target for NFT assignment and / or the target for calculation of the first parameter may vary depending on the event operator, performer, etc.

[0062] (1) Application for participation in an event The action information acquisition module 2035 may acquire information regarding an application to participate in a predetermined event related to the performer. For example, when information regarding an application to participate in an event is transmitted from the terminal device 10 operated by the user who applies for the event to the server 20, the action information acquisition module 2035 acquires information including the event ID of the event related to the application to participate and the user ID of the user related to the application to participate.

[0063] In addition, the action information acquisition module 2035 may acquire information regarding actions performed regarding the following as information regarding an application to participate in an event. · Applying for a lottery to participate in an event · The number of times of applying for the lottery of the same event. By acquiring this information, it can be estimated that a user who has applied for the same event multiple times is an enthusiastic fan of the performer. · Whether or not winning the lottery. By acquiring this information, different processes can be performed according to the winning or losing of the lottery. For example, by increasing the points for the user who lost the lottery, the opportunity to participate in the next event can be increased. · Whether or not the user who won the lottery actually obtained the ticket. By acquiring this information, it can be determined whether or not the user who won the lottery has actually obtained the ticket without forgetting the payment procedure or the like. · The user who applied for participation transferred the obtained ticket to another company by appropriate means. By acquiring this information, it can be evaluated as a user action that the user is taking appropriate actions regarding the transfer of the ticket. For example, when the user transfers the ticket through the official ticket transfer service implemented by the organization operating the event, the action information acquisition module 2035 identifies the ticket transferor from the user ID associated with the transferred ticket. Then, the action information acquisition module 2035 acquires information indicating that the transferor has transferred the ticket by appropriate means.

[0064] (2) Participation in the event The action information acquisition module 2035 may acquire information regarding the participation of a performer in a predetermined event. The action information acquisition module 2035 may acquire the following information regarding user actions as information regarding the participation of a performer in an event.

[0065] ·Entry into the event venue When the user enters the event venue, for example, the terminal device 10 of the user participating in the event displays an image of the entry ticket (electronic ticket) on the display 141. The event staff uses up the electronic ticket by operating the terminal device 10. The terminal device 10 transmits information indicating that the electronic ticket has been used up, that is, information indicating that the user has entered the event venue, to the server 20. The information includes, for example, the user ID of the user entering, the event ID of the event being held, the ticket ID of the used ticket, and the entry date and time (for example, the date and time when the ticket was used up).

[0066] At this time, as described above, by acquiring the entry date and time, it is possible to determine whether the user has entered according to the rules specified by the event organizer.

[0067] Also, for example, when the user exits, information indicating the user's exit date and time may be transmitted to the server 20 by the event staff operating the terminal device 10. The action information acquisition module 2035 may acquire the information indicating the exit date and time. Thereby, it is possible to determine whether the user has exited according to the rules specified by the event organizer, such as a regulated exit.

[0068] ·Purchase of goods at the event venue For example, when a user purchases a predetermined good within an event venue, the good is attached with a code storing the event ID of the event being held at the venue. When the terminal device 10 reads the code in response to an operation from the user, it transmits information such as the user ID of the user, the event ID stored in the code, information on each good purchased by the user, and information indicating the purchase date and time of the good to the server 20. The behavior information acquisition module 2035 acquires these information, that is, as the history of the user actually visiting the event venue.

[0069] (3) Purchase of Goods Related to Performers The behavior information acquisition module 2035 may acquire information regarding the history of purchasing goods related to performers as information regarding user behavior. Goods related to performers include, for example, the following goods. · Media (such as CDs, DVDs, etc.) recording the content in which the performer appears · Goods related to the performer (such as clothes, towels, penlights, accessories, stickers, etc.). The goods may be goods associated with the event in which the performer appears.

[0070] For example, the above goods may be attached with a printed matter on which a code storing the identification information of the goods and the NFT type ID is printed. After purchasing the goods, the user reads the code printed on the printed matter attached to the goods with the camera of the terminal device 10. Thereby, the terminal device 10 accesses the server 20 and transmits information indicating that the goods have been purchased. The information includes the user ID of the user, the identification information of the goods stored in the code, and the NFT type ID. The behavior information acquisition module 2035 acquires the information transmitted from the terminal device 10.

[0071] (4) Information Transmission Regarding Performers The behavior information acquisition module 2035 may acquire information regarding the history of information transmission regarding performers. The behavior information acquisition module 2035 may acquire the following information regarding user behavior as information regarding the fact of information transmission regarding performers.

[0072] · Posts regarding performers on a given social networking service (SNS) For example, the user operates the terminal device 10 in advance to associate the user ID on the SNS (hereinafter referred to as the SNS user ID) with the user ID of the service of the present disclosure (the user ID stored in the user table 202a) via the server 20.

[0073] The server 20 accesses the server that operates the SNS at a predetermined timing and acquires the SNS posting history regarding the performer and the SNS user ID of the user who made the post based on a predetermined search condition. The predetermined search condition is, for example, that a specific word tag related to the performer is attached, that a word related to the performer is included, etc. Also, the search condition and the NFT type ID of the NFT assigned according to the post related to the search condition are associated in advance. Thereby, it becomes possible to evaluate the post that meets the search condition as a user action and assign an NFT related to the NFT type ID associated with the search condition to the target user.

[0074] · Creation of content regarding performers The server 20 associates in advance the user ID on a predetermined platform for the user to post content with the user ID of the service of the present disclosure.

[0075] For example, the user creates content regarding a performer and posts it on a predetermined platform on the Internet by operating the terminal device 10 or the like. The server 20 accesses the server that operates the platform at a predetermined timing and acquires the post based on a predetermined search condition. The predetermined search condition is, for example, that a specific word tag related to the performer is attached, that a word related to the performer is included, etc. Also, the search condition and the NFT type ID of the NFT assigned according to the post related to the search condition are associated in advance. Thereby, it is possible to evaluate the post that meets the predetermined search condition as a user action and assign an NFT to the target user.

[0076] Examples of content related to the performers created by the user are shown for each type of content. Note that the examples of content are not limited to those shown below. · Text content: Articles or the like that summarize information about the performer · Video content: Videos that introduce the performer, videos that are re-edited from other videos related to the performer, etc. · Still image content: Illustrations, photos, etc. · Audio content: Radio content that introduces the performer, etc. · Music content: Edited music related to the performer, etc. · Content that translates at least some of the above content into other languages

[0077] In addition, the predetermined platforms where the content is posted include, for example, the following platforms. · Websites officially operated by the performer or a person related to the performer · Websites unofficially operated by a person not related to the performer · SNS

[0078] Note that the user may create content related to the performer and sell (for example, sell magazines at a direct sale event), post (for example, post advertisements at a predetermined facility such as a station), etc. on a real predetermined platform. In this case, for example, the user transmits information indicating that the content is to be sold, posted, etc. to the server 20 via a predetermined application web page. The action information acquisition module 2035 acquires information regarding the user creating the content related to the performer and selling, posting, etc. at a real location, in association with the NFT type ID associated with the web page.

[0079] (5) Actions to publicize the existence of the performer The action information acquisition module 2035 may acquire information regarding actions for notifying the presence of the performer as information regarding user actions. The action information acquisition module 2035 may acquire the following information regarding user actions as information regarding actions for notifying the presence of the performer.

[0080] · A request for the content of the performer (such as music content or video content in which the performer was involved in creation) in a predetermined medium (such as a radio program or a TV program). If the content of the performer is played in response to the request, the presence of the performer will be generally known. · The playback of the content of the performer in a predetermined streaming service that provides music content, video content, etc. When the user plays the content in the streaming service and the number of times the content is played in the streaming service increases, the chance of entering the ranking, etc. in the service increases, so the presence of the performer is generally known.

[0081] For example, the user operates the terminal device 10 in advance to associate the user ID in the above medium or streaming service with the user ID of the service of the present disclosure (the user ID stored in the user table 202a) via the server 20. Then, the user logs in to the above medium or streaming service and posts a request to the medium or performs playback in the streaming service.

[0082] The action information acquisition module 2035 accesses the server that operates the above medium or the above streaming service at a predetermined timing and acquires the history of requests posted to the medium or playback in the streaming service. The action information acquisition module 2035 identifies the NFT type to be assigned to the user from the title of the medium, the artist name, etc. included in the acquired information.

[0083] Note that the above-mentioned "information transmission regarding the performer" may be included in the actions for notifying the presence of the performer.

[0084] (6) Actions related to the membership service for performers The action information acquisition module 2035 may acquire information related to actions related to the membership service for performers as information on user actions. Actions related to the membership service for performers include, for example, operations related to joining (including new joining and re - joining), leaving, and continuing membership in the membership service for performers.

[0085] For example, the user may operate the terminal device 10 in advance to associate the user ID in the membership service (hereinafter referred to as the membership ID) with the user ID in the service of the present disclosure via the server 20.

[0086] The server 20 accesses the server that operates the membership service at a predetermined timing and acquires information related to at least one of the membership date (which may distinguish between new membership date and re - membership date), leaving date, and membership period of the user related to the membership ID.

[0087] From the membership date, leaving date, and membership period of the membership service, it is possible to estimate the period during which the user has been active as a fan of the performer. Thereby, it is possible to estimate whether the user is a new fan or an old - timer fan. Therefore, the user's fan history can be distinguished and the user actions can be evaluated.

[0088] Also, the action information acquisition module 2035 can specify whether the user was a member of the membership service at a specific time from the membership date, leaving date, and membership period of the membership service. Thereby, it is possible to estimate whether the user was active as a fan at a specific time. The specific time can be appropriately determined by the performer or the like, for example, a predetermined anniversary related to the performer (such as the performer's birthday, founding anniversary, start date of activities, etc.). Or the specific time may be a period related to a specific event held in the past (such as the event date, the period of a series of event holding periods, etc.).

[0089] (7) Other actions for improving the relationship between the performer and the user The action information acquisition module 2035 may acquire information related to, for example, the following actions as information related to user actions. · Participating in social support activities related to the performer. For example, participating in volunteer activities, charity events, etc. that the performer is holding, endorsing, supporting, or sponsoring. · Participating in events organized by a group (e.g., sponsor) that supports the performer at the event venue, etc.

[0090] For example, when the user participates in the above activities, etc., the terminal device 10 reads, using the camera of the terminal device 10, the identification information of the above activities and the code in which the NFT type ID is stored. Thereby, the terminal device 10 transmits information indicating that the user has participated in the above activities, etc. to the server 20 in association with the user ID. The action information acquisition module 2035 acquires information indicating that the user has participated in the above activities, etc. together with the type ID of the NFT to be assigned to the user.

[0091] As described above, the action information acquisition module 2035 acquires information related to the user actions exemplified above. Thereby, the control unit 203 can assign an NFT corresponding to the user actions performed by the user, and can handle the achievements of the user actions as non-fungible assets.

[0092] The parameter calculation module 2036 calculates a first parameter based on information related to the user actions of the user. Specifically, the parameter calculation module 2036 acquires the holding status of the NFTs assigned to the user actions performed by the user, and calculates the first parameter by summing up the points defined for each NFT. The points related to each NFT are defined, for example, for each event for which the first parameter is to be calculated in the point condition table 202h.

[0093] The lottery module 2037 conducts a lottery for applications to an event and determines the participants in the event. Specifically, the lottery module 2037 conducts a lottery while changing the winning probability according to the first parameter of the users who applied for the lottery, and determines the participants. For example, the lottery module 2037 obtains the first parameter related to the performers of the event to be lottery for the users who applied for the lottery. The lottery module 2037 weights the winning probability of each user by increasing or decreasing the winning probability of the corresponding user according to the first parameter. The lottery module 2037 conducts a lottery based on the weighted winning probability and determines the winners. As a result, since the winning probability for the lottery changes according to the performance of user actions, the more enthusiastic fans with a record of user actions, the more improved the opportunity to participate in the event, and the relationship between the fans and the performers can be improved.

[0094] The presentation control module 2038 presents the information extracted from the storage unit 202 to the user.

[0095] <1.3 Configuration of the Distributed Ledger System 90> FIG. 4 is a diagram showing the configuration of the distributed ledger system 90. As shown in FIG. 4, the distributed ledger system 90 includes a plurality of node computers 90A to 90E.

[0096] The node computers 90A to 90E are connected to each other via a network (which may include the network 80 in FIG. 1). In the present embodiment, the network may include a public network, a private network, a dedicated line, a VPN (Virtual Private Network), or a combination thereof. The node computers 90A to 90E are connected to the network, for example, by wire or wirelessly. The node computers 90A to 90E communicate with each other in a peer-to-peer manner.

[0097] The node computers 90A to 90E manage a distributed ledger using, for example, blockchain technology. Specifically, any of the node computers 90A to 90E acquires data related to the transaction of the cryptographic assets or tokens to be recorded. The node computers 90A to 90E create a block containing the acquired data and add it to the blockchain. The node computers 90A to 90E send the information of the added block to the other node computers 90A to 90E. The other node computers 90A to 90E verify the correctness of the received block, and if the verification is successful, add the block to the blockchain. The node computers 90A to 90E determine the blockchain according to, for example, the number of connected blocks (approval number). As a result, the same distributed ledger is stored across the plurality of node computers 90A to 90E constituting the distributed ledger system 90. Note that the data to be stored is encrypted as appropriate.

[0098] The configuration of the distributed ledger system 90 is not limited to that shown in FIG. 4. For example, the distributed ledger system 90 may include six or more node computers, or may include two to four node computers. Also, the number of node computers constituting the distributed ledger system 90 may vary over time.

[0099] The hardware configuration of the node computers 90A to 90E may be the same as or similar to that of the terminal device 10, so a detailed description thereof is omitted. As an example, the node computers 90A to 90E include a processor, a storage device, an input / output interface, a communication interface, an input device, an output device, or a combination thereof.

[0100] <2 Data Structure> FIGS. 5 to 12 are diagrams showing the data structure of the tables stored in the server 20. Note that FIGS. 5 to 12 are examples and do not exclude data not described. Also, even data described in the same table may be stored in separate storage areas in the storage unit 202.

[0101] FIG. 5 is a diagram showing the data structure of the user table 202a. The user table 202a includes an item "user ID", an item "user name", an item "email address", an item "wallet address", and an item "NFT type ID".

[0102] The item "user ID" is an item for storing a user ID that identifies a user.

[0103] The item "user name" is an item for storing the name of a user. The user name may be set to any string such as the user's surname, nickname, etc.

[0104] The item "email address" is an item for storing the email address of a user.

[0105] The item "wallet address" is an item for storing the wallet address of a user. A wallet address is an address for uniquely identifying a wallet for managing the holding of tokens on a blockchain.

[0106] The item "NFT type ID" is an item for storing the NFT type ID of the NFTs held by a user.

[0107] FIG. 6 is a diagram showing the data structure of the performer table 202b. The performer table 202b includes an item "performer ID" and an item "performer name".

[0108] The item "performer ID" is an item for storing a performer ID that identifies a performer. The performer ID may be assigned in units of a group composed of multiple members (for example, a music group, an idol group, a sports team, etc.), or different performer IDs may be assigned to each member of the group, or both. The performer ID assigned to a predetermined group and the performer ID assigned to the members of the group may be associated with each other.

[0109] The item "Performer Name" is an item that stores the name of the performer. The performer name can be set to any string, such as the performer's real name, stage name, group name, etc.

[0110] Figure 7 is a diagram showing the data structure of the event table 202c. The event table 202c includes an item "Event ID", an item "Event Name", an item "Event Type", an item "Performer ID", an item "Venue", an item "Organizer ID", an item "Holding Date and Time", an item "Application Conditions", and an item "NFT Type ID".

[0111] The item "Event ID" is an item that stores the ID for identifying an event.

[0112] The item "Event Name" is an item that stores the name of the event.

[0113] The item "Event Type" is an item that stores the type of the event. Specifically, the item "Event Type" stores information indicating the type of the event, such as "Music Live", "Talk Live", etc. The item "Event Type" may store information indicating multiple types.

[0114] The item "Performer ID" is an item that stores the performer ID of the performer who performs in the event related to the event ID. The item "Performer ID" may store multiple performer IDs.

[0115] The item "Venue" is an item that stores information indicating the venue of the event, for example, a string indicating the name of the venue.

[0116] The item "Organizer" is an item that stores information for identifying the organizer of the event, for example, the name of the organizer.

[0117] The item "Holding Date and Time" is an item that stores the holding date and time of the event.

[0118] The item "Application Conditions" is an item that stores information indicating the application conditions regarding the eligibility to apply for an event. Specifically, the item "Application Conditions" stores information regarding the conditions of the first parameter that the user has regarding the eligibility to apply for an event. The item "Application Conditions" stores information regarding conditions based on, for example, the comparison between the first parameter and a predetermined value. Examples of the conditions are as follows. · Whether the first parameter related to a predetermined event of the user is greater than or equal to or less than a predetermined value · Whether the first parameter related to a predetermined event of another user who is a companion of the user is greater than or equal to or less than a predetermined value

[0119] Also, the application conditions may be that the user holds a specific NFT, that is, a specific NFT is associated with the user's wallet address.

[0120] In the case where no conditions are particularly set regarding the eligibility to apply for an event, the item "Application Conditions" stores information indicating that no application conditions are stored in this item, such as a blank or a null value.

[0121] The item "NFT Type ID" is an item that stores the NFT type ID of the NFT assigned to a user who has performed a predetermined user action regarding the event related to the event ID. For example, the item "NFT Type ID" stores the NFT type ID of the NFT assigned to a user who has come to the event related to the event ID. In the case where no NFT is assigned to the user in relation to the event related to the event ID, the item "NFT Type ID" stores information indicating that no NFT type ID is stored in this item, such as a blank or a null value.

[0122] Figure 8 is a diagram showing the data structure of the ticket table 202d. The ticket table 202d includes an item "Ticket ID", an item "Event ID", an item "Application ID", an item "Holder", and an item "Status".

[0123] The item "Ticket ID" is an item that stores the ticket ID for identifying the ticket.

[0124] The item "Event ID" is an item that stores the event ID of the event associated with the ticket.

[0125] The item "Application ID" is an item that stores the application ID that identifies the participation application associated with the ticket.

[0126] The item "Purchase Date and Time" is an item that stores the date and time when the user purchased the ticket.

[0127] The item "Holder" is an item that stores information about the user who is the holder of the ticket. Specifically, the item "Holder" stores the user ID of the user who holds the ticket. When the ticket is transferred from the user who is the holder to another user, the information in the item "Holder" is updated with the user ID of the other user who is the transferee. The item "Holder" may store information about the original user who was the holder of the ticket and the history of ticket transfers.

[0128] The item "Status" is an item that stores the usage status of the ticket related to the ticket ID. Specifically, the item "Status" stores information indicating whether the ticket is unused or has been used.

[0129] Figure 9 is a diagram showing the data structure of the application history table 202e. The application history table 202e includes the item "Application ID", the item "Event ID", the item "User ID", the item "Application Date and Time", and the item "Lottery Result".

[0130] The item "Application ID" is an item that stores the application ID that identifies the participation application to the event.

[0131] The item "Event ID" is an item that stores the event ID of the event that is the subject of the application.

[0132] The item "User ID" is an item that stores the user ID of the user who made the application.

[0133] The item "Application Date and Time" is an item that stores the date and time when the application was made.

[0134] The item "Lottery Result" is an item that stores the lottery result of the event participation tickets. Specifically, the item "Lottery Result" stores information indicating whether the application was selected or not. In the case of an event where participants are determined by a method other than the lottery method, the item "Lottery Result" stores information indicating that no lottery result is stored in this item, such as a blank or a null value.

[0135] Figure 10 is a diagram showing the data structure of the NFT type table 202f. The NFT type table 202f includes an item "NFT Type ID" and an item "NFT Type Name".

[0136] The item "NFT Type ID" is an item that stores the NFT type ID for identifying the NFT type.

[0137] The item "NFT Type Name" is an item that stores information regarding the name of the NFT type. Specifically, the item "NFT Type Name" stores the name of a specific event associated with the NFT related to the NFT Type ID. For example, the item "NFT Type Name" stores a string related to the content and type of user actions associated with the NFT, such as "Proof of Attendance for the XX Event", "Proof of Purchase of XX Goods", etc., the title of the event, the name of the goods, etc. Or, the item "NFT Type Name" stores a string related to a specific event associated with the NFT, such as "1st Anniversary". Note that the information stored in the "NFT Type Name" can also be said to be the name given to each NFT itself related to the NFT type.

[0138] Figure 11 is a diagram showing the data structure of the NFT management table 202g. The NFT management table 202g includes an item "NFT ID", an item "Serial Number", and an item "Grant Status".

[0139] The item "NFT ID" is an item that stores the NFT ID for identifying the NFT.

[0140] The item "Serial Number" is an item that stores the serial number associated with the NFT. Specifically, the item "Serial Number" stores information indicating a number for identifying NFTs with the same NFT type from each other.

[0141] The item "Grant Status" is an item that stores information regarding the grant status of the NFT related to the NFT ID. Specifically, the item "Grant Status" stores information indicating whether the NFT related to the NFT ID has been transferred to a predetermined user or has not been transferred (remained in the possession of the NFT issuer).

[0142] Figure 12 is a diagram showing the data structure of the point condition table 202h. The point condition table 202h includes an item "Condition ID", an item "Condition", and an item "Granted Points".

[0143] The item "Condition ID" is an item that stores the condition ID for identifying the point grant condition.

[0144] The item "NFT Type ID" is an item that stores the NFT type ID of the NFT type that is the target of point grant.

[0145] The item "NFT Type Name" is an item that stores the NFT type name that is the target of point grant.

[0146] The item "Points" is an item that stores the numerical value of the points associated with the NFT related to the NFT type ID stored in the item "NFT Type ID". The numerical value of the item "Points" can also be said to be the numerical value of the points given to the user who holds the NFT related to the NFT type ID stored in the item "NFT Type ID". In the example shown in Figure 12, 100 points are given to the user who holds the NFT related to the NFT type ID "C001". By summing up the points given to the NFTs held by the user, the first parameter related to the user is calculated.

[0147] As described above, in this embodiment, as the point condition table 202h, different tables are created for each event to be held. For example, a point condition table 202h-A is created for event A, and a point condition table 202h-B is created for event B, respectively. Therefore, the conditions for the point values associated with the types of NFTs held by the user differ for each event to be held. For example, in the table shown in FIG. 12, points are associated with NFT type IDs "C001", "C010", "C003", ···, respectively. On the other hand, in other tables (other events), different values of points may be associated with these NFT type IDs, or no points may be associated (i.e., it may be 0 points). The point conditions can be appropriately determined by the performers of the event, etc. for each event. Note that the point conditions may not differ for each event to be held.

[0148] That is, in this embodiment, by determining the point conditions for each event to be held, the value of the NFTs held by the user can be determined for each event to be held. For example, when the organizer or performer of event A wants to highly evaluate users who have a track record of performing user actions related to a specific event a, the points associated with the NFT type related to event a (e.g., "proof of attendance for event a", "proof of purchase of goods for event a", etc.) are set higher than those for other NFT types, while for NFT types not related to event a, the associated points may be set lower or no points may be associated.

[0149] <Information Associated with NFTs in the Distributed Ledger System 90> FIG. 13 is a diagram showing an example of information associated with NFTs in the distributed ledger system 90. The information shown in FIG. 13 is recorded on the distributed ledger system 90 in association with the NFT when the NFT is issued in the distributed ledger system 90, for example.

[0150] 「NFT ID」is information indicating the NFT ID of an NFT, corresponding to information such as the item "NFT ID" in the NFT management table 202g.

[0151] 「NFT type ID」is information indicating the NFT type ID of an NFT, corresponding to information such as the item "NFT type ID" in the NFT type table 202f.

[0152] 「NFT type name」is information indicating the type name of an NFT, corresponding to information such as the item "NFT type name" in the NFT type table 202f.

[0153] 「Digital content address」is information for specifying digital content associated with an NFT. For example, when the digital content is stored in a predetermined server, the digital content address is information indicating the reference destination of the digital content. For example, when the digital content is managed by a distributed storage system, the digital content address is information (such as the identification ID of the content) for identifying the digital content in the distributed storage system.

[0154] Note that the information associated with an NFT may directly include the data of the digital content. At this time, the data of the digital content may be converted into any format. Also, when the information associated with an NFT directly includes the data of the digital content, the information associated with the NFT may not include information corresponding to the "digital content address".

[0155] 「Serial number」is information indicating the serial number associated with an NFT, corresponding to information such as the item "serial number" in the NFT management table 202g.

[0156] 「Issuance date and time」is information indicating the date and time when the NFT was issued. The "issuance date and time" is, for example, information indicating the date and time when a transaction related to the issuance of the NFT is recorded in the distributed ledger system 90.

[0157] Note that the information associated with the NFT may include information other than the information shown in FIG. 13. For example, the information associated with the NFT may include information regarding the transferability of the NFT. The information regarding transferability is information regarding whether or not the NFT is permitted to be further transferred from the user to another user after being transferred from the issuer to a predetermined user.

[0158] <3 Operations> The operations of the terminal device 10 and the server 20 will be described.

[0159] (Process of Assigning NFT to User) FIG. 14 is a flowchart showing an example of the operations of the server 20 and the distributed ledger system 50 when assigning an NFT corresponding to a user action to a user who has performed a predetermined user action.

[0160] Note that when explaining the content of the process shown in FIG. 14, the entry into the event venue related to a predetermined performer will be taken as an example of the user action for explanation.

[0161] First, when the user performs a predetermined user action, a predetermined information processing device related to the user action transmits information related to the user action to the server 20. The information related to the user action includes at least information for identifying the user who has performed the user action and information for identifying the NFT related to the user action. For example, when the user enters the event venue, the user operates the terminal device 10 at the entrance and causes the electronic ticket to be displayed on the display 141. When the electronic ticket is used by the event venue entrance staff or the like, the terminal device 10 transmits information including the ticket ID related to the electronic ticket and the user ID of the user to the server 20.

[0162] In step S11, the control unit 203 of the server 20 acquires information regarding user behavior. Specifically, the control unit 203 acquires information regarding user behavior transmitted from a predetermined information processing device. For example, the control unit 203 acquires information including a ticket ID and a user ID transmitted from the terminal device 10. Further, the control unit 203 searches the ticket table 202d based on the acquired ticket ID, acquires the information of "event ID" of the corresponding record, and sets the item "status" to "used".

[0163] In step S12, the control unit 203 identifies the NFT type related to the user behavior. Specifically, for example, the control unit 203 searches the event table 202c based on the acquired event ID, and acquires the information of the item "performer ID" and the item "NFT type ID" of the corresponding record. Thereby, the type of NFT to be assigned to the user who performed the user behavior is identified.

[0164] In step S13, the control unit 203 identifies the NFT to be assigned to the user. Specifically, for example, in the NFT management table related to the acquired NFT type ID, the control unit 203 selects one record from the records whose assignment status is "unassigned", and acquires the information of the items "NFT ID" and "serial number" of the record. Thereby, the NFT to be assigned to the user who performed the user behavior is identified. At this time, the control unit 203 may select the record with the smallest value in the "serial number" item among the records whose status is "unassigned".

[0165] The control unit 203 searches the user table 202a based on the user ID acquired from the terminal device 10 in step S11, and acquires the information of the item "wallet address". Thereby, the wallet of the user who is the transfer destination of the NFT is identified.

[0166] In step S14, the control unit 203 gives an instruction to the distributed ledger system 50 to assign an NFT to the user. Specifically, the control unit 203 transmits information including the identification information of the NFT to be assigned to the user, the wallet address of the transfer source of the NFT, and the wallet address of the user who is the transfer destination of the NFT to the distributed ledger system 50 by designating a predetermined contract address, thereby giving an instruction to assign the NFT. Note that the transfer source of the NFT is, for example, the operator of the service according to the present disclosure, the operator of the event, the performer, etc., and the wallet address of the transfer source is stored in the server 20 in advance.

[0167] In step S15, the distributed ledger system 50 assigns an NFT to the user. Specifically, the NFT is transferred to the user's wallet by executing a transaction that transfers the NFT from the transfer source's wallet to the user's wallet. When the NFT is assigned to the user, the digital content associated with the NFT is also substantially assigned to the user. When the NFT is transferred, the distributed ledger system 50 notifies the server 20 to that effect.

[0168] Note that the NFT assigned to the user in step S15 does not have to be created in advance. For example, the distributed ledger system 90 may assign the NFT to the user by issuing a new NFT associated with the information received from the server 20 to the user's wallet.

[0169] In step S16, the control unit 203 updates the NFT holding status of the user. Specifically, for example, the control unit 203 searches the user table 202a based on the user ID of the user and adds the NFT type ID of the NFT assigned to the user in step S15 to the item "NFT type ID".

[0170] In step S17, the control unit 203 notifies the user that an NFT has been assigned to the user due to the user's action. Specifically, for example, information indicating that the NFT has been assigned is transmitted to the user's terminal device 10. The information may include information such as the NFT type name, serial number, and reference destination of the digital content related to the NFT assigned to the user.

[0171] Note that the assigned NFT can be transferred to other users. As a result, the digital content associated with the NFT will also be substantially transferred to other users. For example, a user who wants to transfer an NFT operates the terminal device 10, specifies the NFT ID of the NFT to be transferred and the user ID of the other user who will receive the NFT, and transmits information indicating that the NFT is to be transferred to the server 20.

[0172] The control unit 203 searches the user table 202a to identify the user's wallet address and the wallet address of the other user. The control unit 203 transmits the wallet address of each user and the information of the NFT related to the transfer to the distributed ledger system 50 to execute the process of transferring the NFT. When the transaction related to the transfer is recorded on the blockchain, the NFT is registered in the wallet of the other user, and the registration of the NFT in the user's wallet is cancelled.

[0173] The control unit 203 may manage the circulation of NFTs in the server 20, for example, by storing the following information in the storage unit 202. · The NFT ID of the transferred NFT · The user ID of the user who is the transfer source · The user ID of the user who is the transfer destination · The timestamp of the transaction related to the transfer of the NFT

[0174] In addition, the control unit 203 may acquire information regarding the transfer of NFTs by a user to other users as information related to the user's behavior. Thereby, the transfer of NFTs can be evaluated as user behavior, and the target of NFT granting and the target of output of the first parameter can be determined. As a case of evaluating the transfer of NFTs as user behavior, for example, a case where a user transfers an NFT to another user who is not familiar with the performer or event is assumed for the purpose of conveying the charm of the performer or event.

[0175] The digital content is associated with the NFT. Therefore, when the NFT is transferred, the digital content can be substantially transferred to others, and the transfer history is recorded.

[0176] (Lottery process) Among events, there are events that require prior application for participation, and when the number of applications exceeds the upper limit of the number of participants, participants (those with the right to participate, those with the right to purchase event tickets) are determined by lottery. Hereinafter, such events may be referred to as lottery events. FIG. 15 is a flowchart showing an example of the operations of the server 20 and the distributed ledger system 90 when calculating the first parameter based on the NFTs held by the user and conducting a lottery while changing the winning rate for the lottery event according to the first parameter.

[0177] The lottery process shown in FIG. 15 is started, for example, when the control unit 203 of the server 20 acquires the event ID of the event from the storage unit 202 at a predetermined timing after the application period for the lottery has ended.

[0178] In step S21, the control unit 203 of the server 20 acquires the user ID of the user (applying user) who has applied for the lottery to participate in the event targeted for the lottery process from the storage unit 202. Specifically, for example, the control unit 203 searches the application history table 202e based on the event ID of the event targeted for the lottery process and acquires the information of the item "user ID".

[0179] In step S22, the control unit 203 searches the user table 202a based on the acquired user ID and acquires the wallet address of the applying user. The control unit 203 inquires the distributed ledger system 90 about the NFT holding status of the wallet related to the acquired wallet address.

[0180] In step S23, the distributed ledger system 90 identifies the wallet of each applying user based on the acquired wallet address and acquires a list of NFT type IDs of the NFTs held by each applying user. The distributed ledger system 90 transmits information regarding the list of NFT type IDs of the NFTs held by each applying user to the server 20 for each user ID of the applying user.

[0181] In step S24, the control unit 203 acquires information regarding the list of NFT type IDs of the NFTs held by each applying user from the distributed ledger system 90. The control unit 203 updates the NFT holding status of the applying user based on the acquired information. Specifically, the control unit 203 searches the user table 202a by the user ID acquired from the distributed ledger system 90 and updates the information in the item "NFT type ID" with the NFT type ID acquired from the distributed ledger system 90.

[0182] In step S25, the control unit 203 identifies the point condition table 202h related to the event to be selected based on the event ID of the event to be selected. Note that the point condition table 202h related to the event to be selected may not be created in advance, and in this step, the point condition table 202h related to the event to be selected may be created by a terminal device operated by an event operator or the like.

[0183] The control unit 203 calculates a first parameter related to the applicant user. Specifically, for example, the control unit 203 searches the point condition table 202h based on the NFT type ID of each NFT held by the applicant user acquired in step S24, and sums up the values stored in the item "points" of the corresponding record. Thereby, the first parameter related to the NFT held by the applicant user in the event to be subject to the lottery is calculated.

[0184] Here, the NFTs held by the applicant user are assigned to the applicant user based on the information regarding the user behavior of the applicant user as per the process shown in FIG. 14. Therefore, it can be said that in step S25, the first parameter is output for the applicant user based on the information regarding the user behavior of the applicant user.

[0185] In step S26, the control unit 203 changes the winning probability of the applicant user in the lottery based on the calculated first parameter. Specifically, the control unit 203 changes the winning probability of the applicant user by weighting the original winning probability of the user according to the first parameter. For example, the control unit 203 calculates the weight of the winning probability for the applicant user by adding the value obtained by dividing the numerical value of the first parameter by a predetermined number to the original winning probability. Then, the control unit 203 calculates the new winning probability of the applicant user by dividing the weight of the winning probability of the applicant user by the sum of the weights of the winning probabilities of each applicant user. Note that the method of changing the winning probability is merely an example, and the control unit 203 may change the winning probability using any method.

[0186] Note that in step S26, the control unit 203 may change the winning probability of the users who hold a specific one or more types of NFTs without calculating the first parameter. For example, the winning probability of the applicant user may be changed by multiplying the winning probability by a predetermined magnification by the number of users who hold a specific type of NFT. Thereby, the winning probability can be changed according to the NFT holding status without calculating the first parameter.

[0187] In step S27, the control unit 203 conducts a lottery to determine the winners and losers. Specifically, for example, a lottery is conducted according to an arbitrary lottery algorithm based on the new winning probability. As a result, a winning user who is the winner and a losing user who is the loser are determined from the applicant users.

[0188] In step S27, the control unit 203 may allow a user whose first parameter is greater than or equal to a specific value and / or a user who holds a specific one or more types of NFTs to win without being subject to the lottery, thereby granting the user the right to participate in the event. All winners may be determined in this way, that is, the lottery may not actually be conducted. If there are remaining winning slots, a lottery for the remaining winning slots may be conducted for other users other than the said users. In this case, the winning probability may or may not be changed.

[0189] Also, the control unit 203 may prevent a user whose first parameter is less than or equal to a specific value and / or a user who does not hold a specific one or more types of NFTs from winning without being subject to the lottery, thereby denying the user the right to participate in the event.

[0190] Also, the control unit 203 may prevent a user who holds a specific one or more types of NFTs from winning without being subject to the lottery, thereby denying the user the right to participate in the event. For example, the control unit 203 may prevent a user who holds an NFT related to participating in an event held within a predetermined period or within a predetermined number of event sessions retroactively from the event related to the lottery from winning without being subject to the lottery.

[0191] The control unit 203 searches the application history table 202e based on the user ID of the applicant user and the event ID of the event related to the lottery, and stores information indicating winning or losing in the item "lottery result" according to the lottery result of each applicant user.

[0192] The control unit 203 may manage information about the applicant user by creating an application list as shown in FIG. 16. In the application list, the item "User ID" stores the user ID of the applicant user. The item "Owned NFT" stores the NFT type ID of the NFTs owned by the applicant user. The item "Parameter" stores the value of the first parameter calculated for the applicant user. The item "Lottery result" stores information indicating the lottery result of the applicant user.

[0193] In step S28, the control unit 203 acquires information of the winning user from the storage unit 202. Specifically, for example, the control unit 203 acquires the information of the item "Application ID" and the item "User ID" of the record in which the information indicating "winning" is stored in the item "Lottery result" in step S24.

[0194] The control unit 203 generates ticket information for the winning user. Specifically, for example, the control unit 203 stores the event ID of the event related to the lottery, the application ID acquired in step S25, and the user ID acquired in step S25 in a new record in the ticket table 202d. Note that the ticket information may be created when the winning user performs the purchase process of the ticket.

[0195] In step S29, the control unit 203 notifies the applicant user of the lottery result. Specifically, the control unit 203 transmits information regarding whether or not the applicant user has won the lottery to the terminal device 10.

[0196] The terminal device 10 receives the information transmitted from the server 20. The terminal device 10 notifies the user of the lottery result, for example, by displaying information regarding the lottery result on the display 141. The terminal device 10 may present the user with information for receiving a ticket for participating in the event for the winning user via the display 141.

[0197] As described above, in the lottery process, a first parameter is calculated based on the NFTs held by the user, and a lottery is conducted while changing the winning rate for the lottery event according to the first parameter. As described above, NFTs are assigned according to the achievements of user actions. Therefore, in other words, the more actively a user acts (actively acquires NFTs), the more the winning probability for the event changes (increases). Therefore, users who have taken user actions can increase their chances of participating in the event and improve their relationship with the performer.

[0198] In the above description, an example of a mode of conducting a lottery for determining event participants has been illustrated and described, but the target of the lottery is not limited to this. The lottery process can be applied to any lottery that determines winners and losers. For example, the lottery process can be applied to a lottery conducted when the number of people wishing to purchase is greater than the actual number of products. In this case, the product may be a product associated with the performer (for example, limited goods). As a result, the more actively a user acts (actively acquires NFTs), the easier it is to obtain the product. On the other hand, those who are not fans of the performer, for example, those who aim to resell the product at a high price, will find it difficult to obtain the product.

[0199] Note that the product does not have to be a product related to the performer as long as it is a product that requires a lottery to obtain, such as a lottery sale. Examples of products include, but are not limited to, brand products, quantity-limited products, period-limited products, new products, high-value products, etc.

[0200] (Special Event Notification Process) FIG. 17 is a flowchart showing an example of the operations of the server 20 and the distributed ledger system 90 when calculating a first parameter based on the NFTs held by the user, determining whether to apply for participation in an event (hereinafter sometimes referred to as a special event) whose application eligibility is determined according to the first parameter, and notifying the special event information to users eligible to apply for the special event.

[0201] First, the operator of the special event, etc. operates a predetermined terminal to transmit information regarding the special event to the server 20. The information regarding the special event includes information corresponding to each item of the event table 202c (at least information corresponding to the item "application conditions"). Further, the information regarding the special event includes information for generating the point condition table 202h related to the special event (information corresponding to each item of the point condition table 202h).

[0202] In step S31, the control unit 203 of the server 20 receives information regarding the special event from the above terminal. The control unit 203 stores the received information in a new record of the event table 202c. Further, the control unit 203 generates a point condition table 202h related to the special event based on the received information.

[0203] In step S32, the control unit 203 refers to the user table 202a to obtain the user's wallet address. The control unit 203 inquires of the distributed ledger system 90 about the NFT holding status of the wallet related to the obtained wallet address.

[0204] In step S33, the distributed ledger system 90 identifies the user's wallet based on the obtained wallet address and obtains a list of NFT type IDs of the NFTs held by the user. The distributed ledger system 90 transmits information regarding the list of NFT type IDs of the NFTs held by the user to the server 20 for each user ID.

[0205] In step S34, the control unit 203 obtains information regarding the list of NFT type IDs of the NFTs held by each user from the distributed ledger system 90. The control unit 203 updates the NFT holding status of each user based on the obtained information. Specifically, the control unit 203 searches the user table 202a by the user ID obtained from the distributed ledger system 90 and updates the information in the item "NFT type ID" with the NFT type ID obtained from the distributed ledger system 90.

[0206] In step S35, the control unit 203 identifies the users who hold the NFTs related to the special event. Specifically, for example, the control unit 203 obtains the list of items "NFT type ID" in the point condition table 202h related to the special event, and searches the user table 202a based on each obtained NFT type ID, thereby obtaining the user IDs of the users who hold the NFTs related to each NFT type ID.

[0207] In step S36, the control unit 203 calculates the first parameter for the users who hold the NFTs related to the special event. Specifically, the control unit 203 searches the point condition table 202h based on the NFT type IDs of each NFT held by the users who hold the NFTs related to the special event, and calculates the first parameter by summing up the values stored in the item "points" of the corresponding records.

[0208] Here, as shown in the process of FIG. 14, the NFTs related to the special event are assigned to the users who hold the NFTs related to the special event based on the information on the user actions of the users who hold the NFTs related to the special event. Therefore, in step S36, it can be said that the first parameter is output for the users who hold the NFTs related to the special event based on the information on the user actions of the users who hold the NFTs related to the special event.

[0209] In step S37, the control unit 203 identifies the users who can apply for the special event based on the first parameter. Specifically, the control unit 203 compares the information of the item "application condition" in the event table 202c related to the special event with the calculated first parameter of each user, and extracts the user IDs of the users who meet the application conditions. For example, when the application condition is "the first parameter is 100 or more", the user IDs of the users whose calculated first parameter is 100 or more are extracted to identify the users who can apply for the special event.

[0210] The control unit 203 may manage information about users who can apply for special events by creating a guidance list as shown in FIG. 18. In the guidance list, the item "User ID" stores the user ID of users who can apply for special events. The item "Owned NFT" stores the NFT type ID of the NFTs owned by the user. The item "Parameter" stores the value of the first parameter calculated for the user.

[0211] In step S38, the control unit 203 notifies users who can apply for special events that they can apply for the special event. For example, the control unit 203 sends a message indicating that the user can apply for the special event to the email address associated with the user ID of the user who can apply for the special event. The terminal device 10 of the user who can apply for the special event notifies that the user can apply for the special event, for example, by displaying information indicating that the message has been received on the display 141. Note that users who cannot apply for the special event are not notified that they can apply for the special event.

[0212] Also, when a user who can apply for a special event operates the terminal device 10 and accesses the my page prepared for each user in the service of this embodiment, the control unit 203 causes the display 141 of the terminal device 10 to display information indicating that the user can apply for the special event, thereby notifying or presenting to the user who can apply for the special event that they can apply for the special event. Note that the user ID stored in the storage unit 202 may be associated in advance with a user ID stored and managed in another system different from the system 1 (for example, a predetermined customer management system). The association between user IDs may be performed by any method using, for example, a predetermined API. Then, the server 20 may transmit information regarding users who can apply for the special event to the other system. As a result, the other system can also store and manage information regarding whether a user can apply for the special event. Therefore, in the service provided by the other system, it becomes possible to control whether a user can apply for the special event and provide information regarding whether a user can apply for the special event to the user.

[0213] Even if a user who cannot apply for the special event operates the terminal device 10 and accesses the my page, information indicating that the user who cannot apply for the special event can apply for the special event is not notified or presented. However, at least one of the following information may be presented on the my page of a user who cannot apply for the special event: information indicating that the special event will be held, information indicating that the user cannot apply for the special event, and information indicating that an opportunity to participate in the special event will be given by taking a predetermined user action (user action for obtaining a predetermined NFT). Thereby, a user who does not have the right to participate in the special event can increase their motivation to take user actions in order to participate in the next special event.

[0214] The special event may be a lottery event. In this case, the number of users who can apply for the lottery of the special event varies according to the conditions stored in the item "application conditions" of the event table 202c. Therefore, the control unit 203 sets the conditions of the first parameter stored in the item "application conditions" based on the condition information of the first parameter regarding the application conditions transmitted from the terminals of the organizer, operator, etc. of the special event to the server 20, for example, so that the control unit 203 can set the population of users who can apply for the lottery of the special event. For example, if the conditions of the first parameter are set so that the population of users who can apply for the lottery decreases, the winning probability of the special event will increase. Therefore, the control unit 203 can increase the winning probability of the lottery of the special event compared to the winning probability of the lottery of an event that is not a special event.

[0215] (When the mere possession of NFTs is a condition for application) In the special event guidance process shown in FIG. 17, the conditions regarding the first parameter were set as the application conditions. However, in a special event, instead of the conditions regarding the first parameter, the mere possession of a specific one or more types of NFTs may be set as the application condition. In this case, in the item "application conditions" of the event table 202c, it is stored as a condition that one or more NFTs related to a specific one or more NFT type IDs are possessed, rather than the conditions regarding the first parameter. For example, in the item "application conditions", it may be stored as a condition that an NFT related to the history of participating in a specific event a is possessed.

[0216] FIG. 19 is a flowchart showing an example of the operations of the server 20 and the distributed ledger system 90 in the special event guidance process when the mere possession of a specific one or more types of NFTs is set as the application condition.

[0217] The processes of steps S41 to S44 are the same as the processes of steps S31 to S34 shown in FIG. 17.

[0218] In step S45, the control unit 203 identifies the users who hold the NFTs related to the special event by the same process as in step S35. However, in step S45, unlike the process shown in FIG. 17, all users who hold the NFTs related to the special event are identified as users who can apply for the special event. As a result, the users who hold the NFTs related to the special event can equally acquire the right to apply for the special event.

[0219] The process of step S46 is the same as the process of step S38.

[0220] In addition, in the process shown in FIG. 19, when the special event is a lottery event, if the conditions for holding NFTs are set so that the number of users eligible to apply for the lottery decreases, the winning probability for the special event will increase. Therefore, the control unit 203 can increase the winning probability of the special event lottery compared to the winning probability of the lottery for events that are not special events.

[0221] In the above description, an example has been described in which the first parameter is calculated based on the NFTs held by the users, and the eligibility to apply to participate in the special event is determined according to the first parameter. However, the server 20 can apply the above process in a scenario where a certain number of users are selected from a predetermined number of users and the number of selected users is less than or equal to the predetermined number. For example, the above process can be applied when it is desired to grant the right to apply to purchase a specific product (for example, a product related to a predetermined performer (especially limited goods)) to a limited number of users. As a result, it becomes easier for users who have actively taken user actions (actively acquired NFTs) to obtain the product. On the other hand, those who are not fans of the performer, for example, those who aim to resell the product at a high price, will have difficulty obtaining the product.

[0222] <Example Screen> FIG. 20 is a schematic diagram showing an example of a screen that shows information associated with NFTs held by a user, which is displayed on the terminal device 10 when the terminal device 10 accesses the my page prepared for each user in the service of this embodiment.

[0223] The user name display section 1411 is an area for displaying the user name of the user who accessed the my page.

[0224] The performer name display section 1412 is an area for displaying the name of the performer related to the NFT held by the user.

[0225] The NFT information display section 1413 is an area for displaying information associated with the NFTs held by the user for each NFT. The NFT information display section 1413 includes a date display section 14131, an NFT type name display section 14132, and a content display section 14133.

[0226] The date display section 14131 is an area for displaying the date on which the user acquired the NFT. The date display section 14131 may display the date on which the user performed a user action related to the grant of the NFT.

[0227] The NFT type name display section 14132 is an area for displaying the NFT type name. Specifically, the NFT type name display section 14132 displays a character string indicating the NFT type name related to the NFT.

[0228] The content display section 14133 is an area for displaying digital content associated with the NFT.

[0229] FIG. 21 is a schematic diagram showing an example of a screen that shows information about an event displayed on the terminal device 10.

[0230] The event display section 1415 displays, for each event, the date on which the event is held, the name of the event, and an application button for causing the screen to transition to the event application screen. In the example shown in FIG. 19, the event display section 1415 includes areas 1415A, 1415B, 1415C, and 1415D for displaying information on individual events.

[0231] The event display section 1415 displays information on events whose winning probability changes according to a first parameter and information on events whose application eligibility is determined according to the first parameter in a distinguishable manner from other events. Hereinafter, the information regarding NFTs is, for example, information stored in the user tables 202a to 202h and the point condition tables 202h regarding NFTs.

[0232] For example, the icon 14151B included in the area 1415B indicates that the event for which information is displayed in the area 1415B is a lottery event and that the winning probability of the user changes (increases) according to the first parameter of the user. The event display section 1415 may display information regarding NFTs that contributed to the increase in the winning probability by receiving a selection operation of the icon 14151B from the user.

[0233] Also, for example, the icon 14152C indicates that the event for which information is displayed in the area 1415C is an event whose application eligibility is determined according to the first parameter and that the user can apply for the event. The event display section 1415 may display information regarding NFTs that contributed to the determination of the application eligibility by receiving a selection operation of the icon 14152C from the user.

[0234] Also, for example, the icon 14153D indicates that the event for which information is displayed in the area 1415D is an event whose application eligibility is determined according to the first parameter, is a lottery event, and that the user can apply for the event. The event display section 1415 may display information regarding NFTs that contributed to the determination of the application eligibility by receiving a selection operation of the icon 14153D from the user.

[0235] <Modification Example>

[0236] In the above embodiment, the control unit 203 assigned NFTs of a type corresponding to the user action to the user who performed the user action. Then, the first parameter was calculated according to the type of NFT held. However, the assignment of NFTs to users is not essential. For example, the control unit 203 may store information regarding the history of user actions (for example, information such as the attendance history at events, the purchase history of goods, the posting history on SNS, etc., information obtained by the above-described action information acquisition module 2035) in the storage unit 202. Then, the first parameter of each user may be calculated based on the history of user actions stored in the storage unit 202.

[0237] Also, in the above embodiment, the user action was an action that increased the evaluation as a fan. However, the action information acquisition module 2035 may acquire information regarding an action that decreases the evaluation as a fan as the user action. Then, for a user who has performed an action that decreases the evaluation as a fan, the control unit 203 may calculate a new first parameter so that the calculated first parameter becomes lower, for example, by multiplying the first parameter by a predetermined magnification less than 1.

[0238] The user actions in this modification example are illustrated below. · Despite obtaining a ticket, not participate in the event. For example, the control unit 203 acquires the acquisition history of tickets for a predetermined event from the ticket table 202d. Then, after the event is held, the entry history data of the event is acquired. The control unit 203 identifies users who did not participate in the event despite obtaining a ticket by comparing the ticket acquisition history and the event entry history. · The obtained ticket is transferred to others on an unofficial distribution site. For example, the control unit 203 obtains the ticket ID of the ticket registered for sale on the unofficial distribution site from the server of the distribution site, and collates it with the ticket ID stored in the ticket table 202d to identify the user who has transferred the ticket on the distribution site. · Obtaining a ticket on an unofficial distribution site. For example, the control unit 203 obtains the ticket ID of the ticket registered for sale on the unofficial distribution site from the server of the distribution site, and collates it with the admission history data of the event venue related to the ticket to identify the user who has obtained the ticket from the distribution site.

[0239] In addition, the control unit 203 may set an action such that the first parameter becomes low (it becomes difficult to receive the privilege according to the first parameter), even if the action is not necessarily an action with a low evaluation as a fan. For example, from the user participation history data of an event in which a specific performer appears, a user who has participated in the event a predetermined number of times or more may be identified. And the first parameter may be calculated to be low for the user. Thereby, the opportunity for a user with a small number of participations in the event in which the performer appears or a user who has not participated yet to participate in the event relatively increases. Therefore, it is possible to promote the increase of new fans and the establishment of fans with a short fan history.

[0240] As described above, some embodiments of the present disclosure have been described. However, these embodiments can be implemented in various other forms, and various omissions, replacements, and changes can be made without departing from the gist of the invention. These embodiments and their modifications are included in the scope and gist of the invention, and are also included in the invention described in the claims and the equivalent scope thereof.

[0241] <Supplementary Note> The matters described in each of the above embodiments are appended below. (Supplementary Note 1) A program for operating a computer, the program causing the computer's processor to perform steps of: obtaining information on user actions taken by a user in relation to event performers, rather than a purchase history of tickets for an event with a limit on the number of participants due to the venue size; and outputting a first parameter for the user based on the information on user actions. (Appendix 2) The event requires prior application for participation, and if the number of applications exceeds the upper limit of the number of participants, participants are determined by lottery. The program causes the processor to perform a step of changing the winning probability of the lottery according to the first parameter, which is the program described in Appendix 1. (Appendix 3) For the event, the eligibility for application is determined according to the first parameter. The program causes the processor to perform a step of identifying users eligible to apply for the event based on the first parameter, which is the program described in Appendix 1 or Appendix 2. (Appendix 4) The program causes the processor to perform a step of notifying users eligible to apply for the event that they are eligible to apply for the event, which is the program described in Appendix 3. (Appendix 5) The event requires prior application for participation, and if the number of applications exceeds the upper limit of the number of participants, participants are determined by lottery. Also, the lottery winning probability is higher than that of an event where the eligibility for application is not determined according to the first parameter. This is the program described in Appendix 3 or Appendix 4. (Appendix 6) In the step of outputting the first parameter, the first parameter is output based on NFTs (Non-Fungible Tokens) held in the user's wallet and granted to the user's wallet in relation to user actions. This is the program described in any of Appendices 1 to 5. (Appendix 7) The program according to Supplementary Note 6, wherein in the step of outputting the first parameter, the first parameter is output based on the value of a predetermined point associated with the NFT. (Supplementary Note 8) The program according to Supplementary Note 7, wherein different point values are associated with the NFT for each event. (Supplementary Note 9) The program according to any one of Supplementary Notes 1 to 8, wherein in the step of outputting the first parameter, the first parameter is output based on the history of the user's participation in a predetermined event related to the performer of the event. (Supplementary Note 10) The program according to any one of Supplementary Notes 1 to 9, wherein in the step of outputting the first parameter, the first parameter is output based on the history of the user's purchase of a predetermined item related to the performer of the event. (Supplementary Note 11) The program according to any one of Supplementary Notes 1 to 10, wherein in the step of outputting the first parameter, the first parameter is output based on the history of the user's posting related to the performer of the event on a social networking service. (Supplementary Note 12) The program according to any one of Supplementary Notes 1 to 11, wherein in the step of outputting the first parameter, the first parameter is output based on the history of the user's translation of a predetermined content related to the performer into another language. (Supplementary Note 13) The program according to any one of Supplementary Notes 1 to 12, wherein in the step of outputting the first parameter, the first parameter is output based on the user's membership period in a predetermined membership service related to the performer. (Supplementary Note 14) The program according to any one of Supplementary Notes 1 to 13, wherein in the step of outputting the first parameter, the first parameter is output based on whether the user is a member of a predetermined membership service related to the performer at a specific time. (Supplementary Note 15) A method executed by a computer including a processor, the method comprising: a step in which the processor obtains information regarding user actions taken by a user in relation to performers of an event, rather than a purchase history of tickets for participating in an event with an upper limit on the number of participants due to the size of the venue; and a step in which the processor outputs a first parameter for the user based on the information regarding the user actions. (Appendix 16) An information processing apparatus including a control unit, the control unit performing: a step of obtaining information regarding user actions taken by a user in relation to performers of an event, rather than a purchase history of tickets for participating in an event with an upper limit on the number of participants due to the size of the venue; and a step of outputting a first parameter for the user based on the information regarding the user actions.

Explanation of Signs

[0242] 1…System 10…Terminal device 120…Communication unit 13…Input device 131…Touch-sensitive device 14…Output device 15…Memory 16…Storage 19…Processor 20…Server 22…Communication IF 23…Input / output IF 25…Memory 26…Storage 29…Processor

Claims

1. A program for operating a computer, the program causing a processor of the computer to obtain information regarding user actions taken by a user in relation to performers of the event, rather than a purchase history of tickets for participating in an event with an upper limit on the number of participants due to the size of the venue, output a first parameter for the user based on the information regarding the user actions, and execute the program.

2. For the event, prior application is required for participation, and when the number of applications exceeds the upper limit on the number of participants, participants are determined by lottery, the program causing the processor to change the winning probability of the lottery according to the first parameter, The program according to claim 1.

3. For the event, the eligibility for participation is determined according to the first parameter, the program causing the processor to identify users eligible to apply for the event based on the first parameter, The program according to claim 1.

4. The program causing the processor to notify users eligible to apply for the event that they are eligible to apply for the event, The program according to claim 3.

5. For the event, prior application is required for participation, and when the number of applications exceeds the upper limit on the number of participants, participants are determined by lottery, and the winning probability of the lottery is higher than that of an event where the eligibility for participation is not determined according to the first parameter, The program according to claim 3.

6. In the step of outputting the first parameter, output the first parameter based on non-fungible tokens (NFTs) held in the user's wallet and assigned to the user's wallet in relation to user actions, The program according to claim 1.

7. In the step of outputting the first parameter, output the first parameter based on the value of points associated with the NFT, The program according to claim 6.

8. Different point values are associated with the NFTs for each event, The program according to claim 7.

9. In the step of outputting the first parameter, the user outputs the first parameter based on a history of participating in a predetermined event related to the performers of the event. The program according to claim 1.

10. In the step of outputting the first parameter, the user outputs the first parameter based on a history of purchasing a predetermined item related to the performers of the event. The program according to claim 1.

11. In the step of outputting the first parameter, the user outputs the first parameter based on a history of posting about the performers of the event on a social networking service. The program according to claim 1.

12. In the step of outputting the first parameter, the user outputs the first parameter based on a history of translating a predetermined content related to the performer into another language. The program according to claim 1.

13. In the step of outputting the first parameter, the user outputs the first parameter based on the user's membership period in a predetermined membership service related to the performer. The program according to claim 1.

14. In the step of outputting the first parameter, the user outputs the first parameter based on whether the user was a member of a predetermined membership service related to the performer at a specific time. The program according to claim 1.

15. A method executed by a computer including a processor, the processor acquiring information related to user actions taken by the user related to the performers of the event, rather than a purchase history of tickets for participating in an event with an upper limit on the number of participants due to the size of the venue; outputting a first parameter for the user based on the information related to the user actions; and a method of executing the same.

16. An information processing apparatus including a control unit, wherein the control unit acquires information related to user actions taken by the user related to the performers of the event, rather than a purchase history of tickets for participating in an event with an upper limit on the number of participants due to the size of the venue; outputs a first parameter for the user based on the information related to the user actions; An information processing apparatus that executes

Images