Status storing system, status storing method, and computer readable medium

Abstract

To provide a status storage system and a program capable of approaching a user who is a potential customer of the next event and urging the user to participate.SOLUTION: The status storage system 100 includes user terminals 110A to 110C and a server 120, and the server issues a non-fungible token to a user based on an event participation operation in the user terminals, adds user information to the non-fungible token based on a user information inputting operation to update and change the non-fungible token, and stores the non-fungible token as status information. On the basis of a predetermined action operation set in advance, information about the predetermined action is added to the updated non-fungible token to update and change the non-fungible token, and the non-fungible token is stored as status information, and in the next event, guide information (NTV) of the next event is transmitted to the user terminal on the basis of the user information according to the setting.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a status saving system that includes a user terminal and a server and saves status information corresponding to an action of an event on the user terminal, and a program for the system. [Background technology]

[0002] In the past, for example, in offline stamp rallies, the organizer would simply distribute stamp cards to participants and exchange the stamp cards for prizes from participants who collected stamps, making it difficult for the organizer to obtain personal information about participants and making it difficult to approach potential customers for the next event. For example, in so-called online stamp rallies, participants visit checkpoints, scan 2D codes with their smartphones to collect stamps, and then show them to the organizer to exchange for prizes; this is a one-time event, so just like offline events, it is difficult to approach potential users at the next event. Furthermore, a digital token provision system is known that, when a participant visits a checkpoint, compares the current location information of the participant's smartphone with predetermined location information and provides a digital token if it is determined that the participant has reached the checkpoint (for example, Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent No. 7204272 Summary of the Invention [Problem to be solved by the invention]

[0004] However, the conventional digital token distribution system described above was configured to simply provide digital tokens when it was determined that a participant had reached a checkpoint, making it difficult to approach potential users at the next event.

[0005] Therefore, the present invention solves the problems of the prior art as described above, and the object of the present invention is to provide a status saving system and a program therefor that can approach users who are potential customers for an upcoming event and encourage them to participate, and can also provide proof of the status of events that they have participated in in the past at any time. [Means for solving the problem]

[0006] The invention of claim 1 is a status saving system comprising a user terminal and a server, which saves status information corresponding to an event action on the user terminal, wherein the server issues a non-fungible token to the user based on an event participation operation on a browser on the user terminal, the server adds user information to the non-fungible token and updates the non-fungible token based on a user information input operation on the user terminal, changes the non-fungible token by updating it, and saves it as status information, and based on a predetermined action operation set on the user terminal, the server adds information related to the predetermined action to the updated non-fungible token by updating it, and saves it as status information, and at the time of the next event, the server sends information about the next event to the user terminal based on the user information in accordance with the settings, thereby solving the above-mentioned problem.

[0007] The invention of claim 2 further solves the above-mentioned problem by configuring the status saving system as described in claim 1, in addition to the configuration of the system, in which the server notifies other user terminals of event invitation information based on an input operation of other user information in the browser of the user terminal, and the server issues non-fungible tokens to other users based on an event participation operation in the browser of the other user terminal, and associates the user information with other user information and registers them as a group.

[0008] The invention of claim 3 further solves the above-mentioned problem by being configured in addition to the configuration of the status saving system described in claim 2, in that the non-fungible token is displayed as an image in the browser of the user terminal, and the image relating to the non-fungible token changes as the non-fungible token is updated or changed.

[0009] The invention of claim 4 further solves the above-mentioned problem by, in addition to the configuration of the status saving system described in any one of claims 1 to 3, the specified action operation being one of a specified operation when a predetermined position is reached, an operation to read a near-field wireless communication tag, an operation to read a one-dimensional code or a two-dimensional code, a payment operation using a user terminal, an operation to upload photo image data or video data taken with a user terminal to a social networking service, and an operation to tag and share on a social networking service.

[0010] The invention of claim 5 further solves the above-mentioned problem by having a code reader in addition to the configuration of the status saving system described in claim 4, and when the user's status information is a preset status and a predetermined code display operation is performed on the user terminal, the server generates a one-dimensional or two-dimensional code based on the updated non-fungible token and transmits it to the user terminal, the user terminal displays the received one-dimensional or two-dimensional code, and when the code reader reads the one-dimensional or two-dimensional code displayed on the user terminal, transmits information about the read one-dimensional or two-dimensional code to the server, and the server registers information that the code has been read and user information contained in the received one-dimensional or two-dimensional code information in a database.

[0011] The invention of claim 6 is a program for a status saving system that saves status information corresponding to an event action on a user terminal, and solves the above-mentioned problem by having a computer execute the following steps: an issuance step in which a server issues a non-fungible token to a user based on an event participation operation on a browser on the user terminal; a first non-fungible token mutation step in which the server adds user information to the non-fungible token, updates the non-fungible token, and saves it as status information, based on a user information input operation on the user terminal; a second non-fungible token mutation step in which the server adds information related to a predetermined action to the updated non-fungible token, updates the non-fungible token, and saves it as status information, based on a predetermined action operation on the user terminal; and an event announcement sending step in which, at the time of the next event, the server sends announcement information for the next event to the user terminal based on the user information in accordance with the settings. [Effects of the Invention]

[0012] The status saving system of the present invention is equipped with a user terminal and a server, and is not only able to communicate between the user terminal and the server to save status information corresponding to the action of an event on the user terminal, but also has the following unique effects.

[0013] According to the status saving system of the invention of claim 1, when the next event is held, information about the next event is sent to users who participated in the previous event according to the settings, so that users who are potential customers for the next event can be approached and encouraged to participate, thereby maintaining retention. Furthermore, information about the next event can be sent all at once to a large number of users who are potential attendees of the next event, making it easy for event organizers to attract attendees. In addition, a non-fungible token containing the status of the user's actions in the event is stored on the server, and the status of the user's actions in the event can be proven at any time after the event using the non-fungible token, so the user can prove the status of events they have participated in in the past at any time.

[0014] According to the status saving system of the invention of claim 2, in addition to the effect of the invention of claim 1, when a user inputs information about other users such as friends, family, and lovers, the other users are notified of an event invitation, and when the other users take action to participate in the event, non-fungible tokens are issued for the other users, so it is expected that events that adopt non-fungible tokens will become more widely known among other users.

[0015] According to the status saving system of the invention of claim 3, in addition to the effect of the invention of claim 2, the image related to the non-fungible token changes according to the change in the status of the action of the event, and the changed image is displayed in the browser of the user's terminal, so that the user can check and enjoy the change in his / her own status in the event he / she is participating in. Furthermore, the event organizer can set the content of the image changes in advance so that the event organizer's logo or message information appears or changes in the image, allowing for intended marketing advertising.

[0016] According to the status saving system of the invention of claim 4, in addition to the effects achieved by the invention of any one of claims 1 to 3, the user's status changes when, for example, a predetermined operation is performed when reaching a checkpoint at an event that the user is participating in, a reading operation of a short-range wireless communication tag installed anywhere within the event venue, a reading operation of a one-dimensional code or two-dimensional code installed anywhere within the event venue, a payment operation within the event venue, an operation to upload photo image data or video data taken with a user terminal at the event venue to a social networking service, or an operation to tag and share the event on a social networking service, so that the user can enjoy changing their status at the event venue in accordance with the intentions of the event organizer.

[0017] According to the status saving system of the invention of claim 5, in addition to the effect of the invention of claim 4, for example, when a user reaches a status where they can receive a special gift such as a prize at an event, they can have the code read at a special gift receiving counter or the like, and at the same time receive the special gift, information indicating that the code has been read, which also serves as information to the user that the special gift has been given to them, is associated with the user information and registered on the server, making it easy for the event organizer to manage logs of the gift delivery.

[0018] According to the program of the status saving system of the invention of claim 6, similar to the effect achieved by the invention of claim 1, when the next event is held, information about the next event is sent to users who participated in the previous event according to the settings, so that users who are potential customers for the next event can be approached and encouraged to participate, thereby maintaining retention. Furthermore, information about the next event can be sent all at once to a large number of users who are potential attendees of the next event, making it easy for event organizers to attract attendees. In addition, a non-fungible token containing the status of the user's actions in the event is stored on the server, and the status of the user's actions in the event can be proven at any time after the event using the non-fungible token, so the user can prove the status of events they have participated in in the past at any time. [Brief explanation of the drawings]

[0019] [Figure 1] 1 is a diagram showing the concept of a status saving system according to an embodiment of the present invention; [Figure 2] 1 is a chart showing an example of the operation of a status saving system according to an embodiment of the present invention; [Figure 3] 10A and 10B are diagrams showing examples of an event guide top screen and a login screen of a browser on a user terminal of the status saving system according to an embodiment of the present invention. [Figure 4] 10A and 10B are diagrams showing examples of an event information details screen and a participation form selection screen on a browser of a user terminal of the status saving system according to an embodiment of the present invention. [Figure 5] FIG. 10 is a diagram showing an example of an initial screen of an event currently being attended on a browser of a user terminal of the status saving system according to an embodiment of the present invention. [Figure 6] FIG. 10 is a diagram showing an example of an attending events screen on a browser of a user terminal of the status saving system according to an embodiment of the present invention. [Figure 7] FIG. 10 is a diagram showing an example of information about an upcoming event displayed on a browser of a user terminal of the status saving system according to an embodiment of the present invention. [Figure 8] FIG. 10 is a diagram showing the status saving system according to an embodiment of the present invention when the "Group" tab is selected on the participating events screen of the browser on the user terminal. [Figure 9]FIG. 10 is a diagram showing the status saving system according to an embodiment of the present invention when the "Timeline" tab is selected on the currently participating events screen of the browser on the user terminal. [Figure 10] FIG. 10 is a diagram showing a state when a two-dimensional code generation and display operation is performed on the participating events screen of the browser on the user terminal of the status saving system according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0020] The status saving system of the present invention comprises a user terminal and a server, and based on an event participation operation on the user terminal's browser, the server issues a non-fungible token to the user, and based on a user information input operation on the user terminal, the server adds user information to the non-fungible token, updating the non-fungible token and saving it as status information, and based on a predetermined action operation set on the user terminal, the server adds information related to the predetermined action to the updated non-fungible token, updating the non-fungible token and saving it as status information, and at the time of the next event, the server sends information about the next event to the user terminal based on the user information in accordance with the settings, so that users who are potential customers for the next event can be approached and encouraged to participate, event organizers can easily attract attendees, and users can prove the status of events they have previously participated in at any time.Any specific implementation is acceptable. Furthermore, the program for the status saving system of the present invention has a computer execute the following steps: an issuing step in which a server issues a non-fungible token to a user based on an event participation operation on the browser of the user terminal; a first non-fungible token changing step in which, based on a user information input operation on the user terminal, the server adds user information to the non-fungible token, updates the non-fungible token, and changes it, saving it as status information; a second non-fungible token changing step in which, based on a predetermined action operation set in the user terminal, the server adds information related to a predetermined action to the updated non-fungible token, updating the non-fungible token, and changes it, saving it as status information; and an event invitation sending step in which, at the time of the next event, the server sends invitation information for the next event to the user terminal based on the user information in accordance with the settings.By doing so, it is possible to approach users who are potential customers for the next event and encourage them to participate, the event organizer can easily attract customers, and users can prove the status of events they have previously participated in at any time. Any specific implementation is acceptable.

[0021] For example, the user terminal may be a desktop personal computer terminal, a notebook personal computer terminal, a smartphone terminal, a tablet terminal, a wristwatch terminal, an eyeglass terminal, or any other terminal that displays data on a screen in a browser on the display unit of the user terminal and connects to a server via a communication network including a wide area network such as the Internet, a local network, or a telephone line to send and receive data. Furthermore, the server may be a cloud server created in a cloud environment, and the number of physical servers that make up the server may be one or more. Furthermore, in the present invention, a non-fungible token (NTF) is a so-called dynamic non-fungible token that changes, and the non-fungible token (NTF) may be one and only digital data designed based on "blockchain technology" after the first update, and in the initial state of issuance before the first update, it may be a brand new token and may be the same data as other users. [Example]

[0022] A status saving system 100 according to an embodiment of the present invention will be described below with reference to FIGS. 1 is a diagram showing the concept of a status saving system 100 according to an embodiment of the present invention, FIG. 2 is a chart showing an example of the operation of the status saving system 100 according to an embodiment of the present invention, FIG. 3 is a diagram showing examples of an event information top screen 112 and a login screen 113 on the browser 111 of the user terminal 110A of the status saving system 100 according to an embodiment of the present invention, FIG. 4 is a diagram showing examples of an event information details screen 114 and a participation form selection screen 115 on the browser 111 of the user terminal 110A of the status saving system 100 according to an embodiment of the present invention, FIG. 5 is a diagram showing an example of an attending event initial screen 116 on the browser 111 of the user terminal 110A of the status saving system 100 according to an embodiment of the present invention, and FIG. 6 is a diagram showing an example of an attending event details screen 114 on the browser 111 of the user terminal 110A of the status saving system 100 according to an embodiment of the present invention. 7 is a diagram showing an example of a screen 117, in which FIG. 7 is a diagram showing an example of next event guidance information NTV displayed on the browser 111 of the user terminal 110A of the status saving system 100, which is an embodiment of the present invention; FIG. 8 is a diagram showing the screen when the "Group" tab 117c is selected on the attending events screen 117 on the browser 111 of the user terminal 110A of the status saving system 100, which is an embodiment of the present invention; FIG. 9 is a diagram showing the screen when the "Timeline" tab 117b is selected on the attending events screen 117 on the browser 111 of the user terminal 110A of the status saving system 100, which is an embodiment of the present invention; and FIG. 10 is a diagram showing the screen when a two-dimensional code generation and display operation is performed on the attending events screen 117 on the browser 111 of the user terminal 110A of the status saving system 100, which is an embodiment of the present invention.

[0023] A status storage system 100 according to an embodiment of the present invention includes user terminals 110A to 110C and a server 120, as shown in FIG. Of these, user terminals 110A to 110C will be described as three terminals, namely, user terminal 110A of the user, user terminal 110B (number 1) of another user, and user terminal 110C (number 2) of another user, as an example, but the number may be one, two, or four or more. Furthermore, the server 120 will be described as one unit as an example, but it may be a distributed cloud server.

[0024] The status storage system 100 is configured to store status information corresponding to the action of the event of the user terminal 110A. More specifically, based on an event participation operation on browser 111 of user terminal 110A, server 120 issues a non-fungible token to the user. Here, the initial non-fungible tokens issued may be brand new and may contain the same data as other users.

[0025] Subsequently, based on a user information input operation on user terminal 110A, server 120 adds user information to the initial non-fungible token to update the non-fungible token, thereby changing it and storing it as status information. Here, after the first update, the non-fungible token becomes a unique piece of digital data. In addition to user information, event information to be participated in may also be added to the initial non-fungible token. This ensures that even if the same user participates in different events, the non-fungible tokens will be unique digital data for each event.

[0026] Furthermore, based on a predetermined action operation set in advance in user terminal 110A, server 120 adds information about the predetermined action to the updated non-fungible token, thereby updating and changing the non-fungible token, and stores it as status information. In other words, the non-fungible token is a so-called dynamic non-fungible token that changes. When the next event occurs, server 120 is configured to transmit guide information NTV for the next event to user terminal 110A based on the user information in accordance with the settings. Here, "depending on the setting" allows the event organizer, manager, or company to freely select whether or not to send the information based on their own wishes. Although the user terminal 110A has been described above, the same applies to the other users' user terminals 110B and 110C, and their description will be omitted.

[0027] As a result, when the next event is held, guide information NTV for the next event is sent to users who participated in the previous event according to the settings. As a result, you can approach potential users for your next event and encourage them to attend, maintaining retention. Furthermore, information NTV about upcoming events can be freely sent in bulk to a large number of users who are potential customers for the upcoming event. As a result, event organizers can easily attract customers. Additionally, a non-fungible token containing the status of the user's actions in the event is stored on the server 120, and the status of the user's actions in the event can be verified by the non-fungible token at any time after the event. As a result, users can always prove the status of events they have previously attended.

[0028] Next, an example of the operation of the status saving system 100 will be described in detail. As shown in FIG. 2, in step S1, as an event participation operation presence / absence determination step, browser 111 of user terminal 110A determines whether or not the user has performed an event participation operation on browser 111 of user terminal 110A. More specifically, as shown in FIG. 3, the browser 111 of the user terminal 110A accesses the server 120 based on the predetermined URL information and displays the event information top screen 112.

[0029] Here, the event guide top screen 112 displays various types of event information 112a. Additionally, the event information top screen 112 is provided with a login button 112b. When the user operates the login button 112b, the browser 111 of the user terminal 110A displays the login screen 113. When the user inputs user ID information and password information, the input information is sent to the server 120 and authenticated, completing the login process. Also, for example, it is assumed that the user selects desired event information 112a on the event information top screen 112.

[0030] Then, as shown in FIG. 4, user terminal 110A communicates with server 120, and browser 111 of user terminal 110A displays event information details screen 114. The event information details screen 114 displays detailed information about the event selected by the user. The event information details screen 114 also has a participation button 114a. When the user operates the participation button 114a on the event information details screen 114, the browser 111 of the user terminal 110A determines that an operation to participate in the event has been performed. In this way, if the browser 111 of the user terminal 110A determines that an operation to participate in the event has been performed, the process proceeds to step S2, and if it determines that no operation has been performed yet, step S1 is repeated.

[0031] In this embodiment, as an example, when the participation button 114a on the event information details screen 114 is operated, the browser 111 of the user terminal 110A displays the participation form selection screen 115. The participation type selection screen 115 displays options to participate alone, or if invited by another user, to participate at the invitation of another user XX, or to participate at the invitation of another user XX. Furthermore, the participation form selection screen 115 is provided with a participation button 115a. When the user operates participation button 115a on participation form selection screen 115, browser 111 of user terminal 110A may be configured to determine that an operation to participate in the event has been performed.

[0032] In step S2, which is an issuing step, the server 120 issues a non-fungible token to the user. Here, as mentioned above, the initial non-fungible tokens issued may be brand new and may contain the same data as other users. At this time, as shown in FIG. 5, for example, the browser 111 of the user terminal 110A displays an initial screen 116 of the event in progress.

[0033] The participating event initial screen 116 displays an image related to a non-fungible token (DNFT). Here, the non-fungible tokens that are issued at the beginning are blank images and contain the same data as other users, so the image of this non-fungible token (DNFT) will also be the same as that of other users. As an example, the participating event initial screen 116 shown in FIG. 5 is provided, but the participating event initial screen 116 may be omitted and not displayed on the browser 111.

[0034] In step S3, as a user information input operation presence / absence determination step, browser 111 of user terminal 110A determines whether or not a user information input operation has been performed by the user in browser 111 of user terminal 110A. Regarding the user information input operation, since the user has already logged in, the operation may be an operation that reflects the logged-in user information, or the input operation of the user ID information and password information at the time of login may be the input operation of the user information. If it is determined that the user information has been input, the process proceeds to step S4, and if it is determined that the user information has not yet been input, step S3 is repeated.

[0035] In step S4, as a first non-fungible token changing step, the server 120 changes the non-fungible token by adding user information to the non-fungible token and updating the non-fungible token, and stores the changed non-fungible token as status information. As mentioned above, not only user information but also event information to be participated in may be added to the initial non-fungible token. This ensures that even if the same user participates in different events, the non-fungible tokens will be unique digital data for each event. In this way, the non-fungible tokens of the present invention are liquid, dynamic non-fungible tokens. At this time, the browser 111 of the user terminal 110A displays an attending event screen 117, as shown in FIG. The participating event screen 117 displays an image DNFT relating to dynamic non-fungible tokens.

[0036] As an example, comparing the image (DNFT) of a non-fungible token shown in Figure 5 with the image DNFT of a dynamic non-fungible token shown in Figure 6, the images are different because the initially issued non-fungible token was updated to a dynamic non-fungible token by adding user information. As shown in FIG. 6, for example, the image relating to the non-fungible token (DNFT) shown in FIG. 5 may basically be configured to include an icon image or a portrait image of the user.

[0037] That is, the non-fungible token is displayed as an image on the browser 111 of the user terminal 110A. The system is configured so that the image of the non-fungible token (DNFT) changes as the non-fungible token is updated or changed. As a result, the image relating to the non-fungible token (DNFT) changes in accordance with the change in the status of the action of the event, and the changed image is displayed on the browser 111 of the user terminal 110A. As a result, users can see and enjoy changes in their status during events they are participating in. Furthermore, the event organizer can set the content of the image changes in advance so that the event organizer's logo or message information appears or changes in the image, allowing for intended marketing advertising.

[0038] The participating events screen 117 also has a "check-in" tab 117a, a "timeline" tab 117b, and a "group" tab 117c. When the "Check-in" tab 117a is selected, the participating event screen 117 is configured to display position / place information 117d of the user in the event. More specifically, information on check-in locations preset by the event organizer is displayed, and furthermore, locations where users have already checked in are displayed separately from locations where users have not yet checked in. Then, when the user arrives at a preset check-in location, the user operates a check-in button as a check-in operation for that location, which is an example of a predetermined action operation.

[0039] In step S5, as a step of determining whether or not a predetermined action has been performed, the browser 111 of the user terminal 110A determines whether or not a predetermined action has been performed. If it is determined that a predetermined action has been operated, the process proceeds to step S6, and if it is determined that no predetermined action has been operated, step S5 is repeated. In this embodiment, the specified action operation is any one of a specified operation when reaching a predetermined position set in advance, an operation for reading a short-range wireless communication tag, an operation for reading a one-dimensional code or a two-dimensional code, a payment operation using the user terminal 110A, an operation for uploading photo image data or video data taken with the user terminal 110A at an event venue to a social networking service, and an operation for tagging and sharing information related to the event on a social networking service.

[0040] This allows the user's status to change, for example, by performing a specified operation when reaching a checkpoint at an event they are participating in, by reading a short-range wireless communication tag installed anywhere within the event venue, by reading a one-dimensional or two-dimensional code installed anywhere within the event venue, by making a payment within the event venue, by uploading photo image data or video data taken with user terminal 110A within the event venue to a social networking service, or by tagging and sharing the data with information related to the event on a social networking service. As a result, users can enjoy themselves at the event venue by changing their status in accordance with the intentions of the event organizer.

[0041] In step S6, as a second non-fungible token changing step, server 120 changes the non-fungible token by adding information about a predetermined action to the updated non-fungible token, and stores the changed non-fungible token as status information. At this time, similarly to the first non-fungible token changing step described above, the content of the image DNFT relating to the dynamic non-fungible token on the participating event screen 117 changes as shown in FIG. As a result, users can enjoy the changes in the content of the image DNFT, which is a dynamic non-fungible token, linked to changes in status at the event venue in line with the intentions of the event organizer. The predetermined action operation presence / absence determination step S5 and the second non-fungible token change step S6 may be set to be repeated multiple times according to settings made by the event organizer.

[0042] In step S7, as a step of determining whether or not there is next event guide information, the server 120 determines whether or not there is guide information NTV for the next event. If it is determined that there is guidance information NTV for the next event, the process proceeds to step S8, and if it is determined that there is not yet guidance information NTV, step S7 is repeated. In step S8, as an event announcement transmission step, server 120 transmits announcement information NTV for the next event to user terminal 110A based on the user information in accordance with the settings. Then, as shown in FIG. 7, the browser 111 of the user terminal 110A displays the guide information NTV for the next event. Here, "depending on the setting" is set so that the event organizer, manager, or company can freely select whether or not to send the information based on their wishes, as described above. Although the user terminal 110A has been described above, the same applies to the other users' user terminals 110B and 110C, and their description will be omitted.

[0043] As a result, as described above, when the next event is held, guide information NTV for the next event is sent to users who participated in the previous event according to the settings. As a result, you can approach potential users for your next event and encourage them to attend, maintaining retention. Furthermore, information NTV about upcoming events can be freely sent in bulk to a large number of users who are potential customers for the upcoming event. As a result, event organizers can easily attract customers. Additionally, a non-fungible token containing the status of the user's actions in the event is stored on the server 120, and the status of the user's actions in the event can be verified by the non-fungible token at any time after the event. As a result, users can always prove the status of events they have previously attended.

[0044] Furthermore, since the present invention is a web service that displays information on browser 111 of user terminal 110A, there is no need to install event-specific application software. In other words, there is no need for event-specific application software. Furthermore, information NTV about upcoming events can be displayed on the browser 111 of the user terminal 110A as an invitation to a limited event from a company that wants to hold an event, which can lead to attracting customers. The notification of the next event guidance information to NTV may be sent by email from server 120 to user terminal 110A, or may be sent while logged in on event guidance top screen 112, which is an example of a website displayed on browser 111.

[0045] Furthermore, in this embodiment, as shown in FIG. 8, when a "Group" tab 117c is selected on the participating events screen 117, member information 117e of the group to which the user belongs is displayed. For example, suppose that the user selects any event information 112a on the event information top screen 112 of the status saving system 100 and performs an operation to participate in the event. As mentioned above, a non-fungible token is then issued to the user. Users who are issued non-fungible tokens are free to invite other users to the event.

[0046] When the user inputs the other user's information and performs a predetermined invitation operation, the server 120 transmits to the other user terminals 110B, 110C, based on the other user's information, a message indicating that the other user has been invited by the user, along with link information for participating in the event. Then, the browsers (111) of the other user terminals 110B and 110C display the event information details screen 114 as shown in FIG. 4, based on the operation of the link information. Then, it is assumed that another user operates the participation button 114a on the event information details screen 114 as an example of an operation to participate in an event in response to an event invitation from the user. Then, the browsers (111) of the other user terminals 110B and 110C display a participation form selection screen 115.

[0047] Then, it is assumed that the other user selects participation at the invitation of the introducing user XX on participation form selection screen 115 and operates participation button 115 a on participation form selection screen 115 . Then, the information is transmitted from the other user terminals 110B and 110C to the server 120, and the user and the other users are registered as part of the same group, and the server 120 issues a non-fungible token to the other users. When the "Group" tab 117c on the participating events screen 117 is selected, the user information and other user information are displayed as members of the same group.

[0048] In this case, the image DNFT relating to the dynamic non-fungible token displayed on the participating event screen 117 by the browser (111) of the other user terminals 110B and 110C is different from the image DNFT relating to the dynamic non-fungible token displayed on the participating event screen 117 by the browser 111 of the user terminal 110A. The reason is that the user information attached to the non-fungible token is different. In addition, the content of the image DNFT related to the dynamic non-fungible token may be configured so that, if participating as a group, icon images or portrait images of the members in the group are added and displayed in a size that indicates a master-slave relationship. This allows you to keep a record of who you attended each event with.

[0049] In this way, in this embodiment, based on the input operation of other user information in the browser 111 of the user terminal 110A and the event participation operation in response to an event invitation from a user in the browsers (111) of the other user terminals 110B and 110C, the server 120 is configured to issue a non-fungible token to the other user and associate the user information with the other user information to register the group.

[0050] This means that when a user enters information about other users, such as friends, family, or lovers, the other users will be notified of an event invitation, and when the other users participate in the event, non-fungible tokens will be issued for the other users. As a result, we can expect events that adopt non-fungible tokens to become more widely known among other users. By participating in events together, you can especially enjoy "friend travel" and "pair activities" with friends and colleagues.

[0051] In addition, in this embodiment, as shown in FIG. 9, when a "Timeline" tab 117b is selected on the participating events screen 117, log information 117f within the group to which the user belongs is displayed. For example, the system is configured to display date and time information, status information, and information regarding predetermined actions for members in the group.

[0052] This will show who did what, when, and what action was taken. As a result, it is easy to understand the behavior of members within a group. For example, when teams compete to complete a mission at an event, it may be necessary for group members to act not only together but also individually. In this case, it is possible to see what each member of the group has done individually, or has not done yet. If necessary, members of the group can help each other to complete the mission.

[0053] Furthermore, in this embodiment, the status saving system 100 further includes a code reader. Also, assume that the user's status information becomes a preset status. Then, as shown in FIG. 10, it is assumed that, for example, a display operation of menu item 118 is performed on participating event screen 117 of browser 111 of user terminal 110A, and two-dimensional code generation and display is selected. Then, the server 120 generates a generated two-dimensional code 119 based on the updated non-fungible token, which is also status information of the user of the user terminal 110A. Then, the server 120 transmits the generated two-dimensional code 119 to the user terminal 110A. Then, the browser 111 of the user terminal 110A displays the generated two-dimensional code 119 that has been received.

[0054] For example, when a code reader installed at an event venue reads the generated two-dimensional code 119 displayed on the user terminal 110A, the information of the read generated two-dimensional code 119 is transmitted to the server 120. The server 120 is then configured to register information indicating that the code has been read and the user information contained in the received information of the generated two-dimensional code 119 in a database. Although an example in which the generated two-dimensional code 119 is generated and displayed has been described, the generated two-dimensional code 119 may be replaced with a one-dimensional code.

[0055] As a result, for example, when a user reaches a status where he or she can receive a special benefit such as a prize at an event, the code is read at a special benefit receiving counter or the like, and the user receives the special benefit. At the same time, information indicating that the code has been read, which also serves as information indicating that the special benefit has been given to the user, is associated with the user information and registered in the server 120. As a result, event organizers can easily manage logs of gift handovers. That is, when the generated two-dimensional code 119 is read by a code reader, the status is changed to one in which a special gift or other benefit has been received. As a result, if a card is read multiple times at the same location, this can be detected and duplicate receipt of a prize or other benefit can be prevented.

[0056] The status saving system 100, an embodiment of the present invention obtained in this manner, comprises user terminals 110A to 110C and a server 120, and based on an event participation operation on browser 111 of user terminal 110A, server 120 issues a non-fungible token to the user, and based on a user information input operation on user terminal 110A, server 120 adds user information to the non-fungible token, updates the non-fungible token, and changes it, saving it as status information, and based on a predetermined action operation set in user terminal 110A, server 120 adds information related to the predetermined action to the updated non-fungible token, updating the non-fungible token, and saving it as status information, and at the time of the next event, server 120 sends information NTV about the next event to user terminal 110A based on the user information in accordance with the settings, so that users who are potential customers for the next event can be approached and encouraged to participate, maintaining retention, allowing event organizers to easily attract customers, and allowing users to prove the status of events they have previously participated in at any time.

[0057] Furthermore, based on the input operation of other user information in browser 111 of user terminal 110A, server 120 notifies other user terminals 110B and 110C of event invitation information, and based on the event participation operation in the browser (111) of other user terminals 110B and 110C, server 120 issues non-fungible tokens to other users and associates the user information with other user information to register the group, so it is expected that events that adopt non-fungible tokens will become more widely known among other users.

[0058] Furthermore, the non-fungible token is displayed as an image in the browser 111 of the user terminal 110A, and the image (DNFT) relating to the non-fungible token changes as the non-fungible token is updated or changed, so that the user can check and enjoy the changes in his / her status in the event he / she is participating in. The event organizer can also set the content of the image changes in advance so that the event organizer's logo or message information appears or changes in the image, thereby promoting the intended marketing.

[0059] Furthermore, since the specified action operation is one of a specified operation when reaching a predetermined position, an operation to read a short-range wireless communication tag, an operation to read a one-dimensional code or a two-dimensional code, a payment operation using user terminal 110A, an operation to upload photo image data or video data taken with user terminal 110A to a social networking service, and an operation to tag and share on a social networking service, users can enjoy changing their status at the event venue in accordance with the intentions of the event organizer.

[0060] In addition, the status saving system 100 further has a code reader, and when the user's status information is a preset status and a predetermined code display operation is performed on the user terminal 110A, the server 120 generates a generated two-dimensional code 119, which is an example of a one-dimensional code or a two-dimensional code, based on the updated non-fungible token and transmits it to the user terminal 110A, the user terminal 110A displays the received generated two-dimensional code 119, and when the code reader reads the generated two-dimensional code 119 displayed on the user terminal 110A, it transmits information about the read generated two-dimensional code 119 to the server 120, and the server 120 registers information that the code has been read and the user information contained in the received information of the generated two-dimensional code 119 in a database. This configuration allows, for example, an event organizer to easily manage logs of the transfer of benefits.

[0061] Furthermore, the program of the status saving system 100 according to the embodiment of the present invention includes issuance steps S1 and S2 in which the server 120 issues a non-fungible token to the user based on an event participation operation on the browser 111 of the user terminal 110A, a first non-fungible token change step S3 and S4 in which the server 120 adds user information to the non-fungible token and updates the non-fungible token based on a user information input operation on the user terminal 110A, and saves the updated non-fungible token as status information, and a second non-fungible token change step S4 in which the server 120 adds information about a predetermined action to the updated non-fungible token based on a predetermined action operation on the user terminal 110A. By having a computer execute second non-fungible token changing steps S5 and S6, which change the non-fungible token by adding the non-fungible token and updating it, and store the changed non-fungible token as status information, and event announcement sending steps S7 and S8, in which the server 120 sends announcement information NTV for the next event to the user terminal 110A based on the user information in accordance with the settings, it is possible to approach users who are potential customers for the next event and encourage them to participate, thereby maintaining retention, allowing the event organizer to easily attract customers, and allowing users to prove the status of events they have previously participated in at any time, resulting in significant effects. [Explanation of symbols]

[0062] 100 ··· Status save system 110A··· (User's) User Terminal 110B... (Other user's) user terminal (part 1) 110C... (Other user's) terminal (part 2) 111 ··· (User's device) browser 112 Event Information Top Page 112a··· Event Information 112b··· Login button 113 ··· Login screen 114 Event information details screen 114a··· Participate button (on the event information details screen) 115 ··· Participation form selection screen 115a··· Participation button (on the participation type selection screen) 116 ··· Initial screen of participating event 117 ··· Participating Event Screen 117a··· "Check-in" tab 117b··· "Timeline" tab 117c... "Groups" tab 117d... Location / location information 117e··· (Group) Member Information 117f Log information (date and time information, status information, information about specified actions) 118 ··· Menu items 119 ··· Generated 2D code 120 Server DNFT··· Dynamic Non-Fungible Token Image NTV ··· Information on upcoming events

Claims

1. A status storage system including a user terminal and a server for storing status information corresponding to an action of an event of the user terminal, The server issues a non-fungible token to the user based on the event participation operation on the browser of the user terminal, The server adds user information to the non-fungible token based on a user information input operation on the user terminal, updates the non-fungible token, and stores the changed non-fungible token as status information; The server updates the non-fungible token by adding information about the predetermined action to the updated non-fungible token based on a predetermined action operation set in the user terminal, and stores the updated non-fungible token as status information; A status saving system characterized in that, at the time of the next event, the server transmits guidance information for the next event to the user terminal based on the user information in accordance with settings.

2. The server notifies the other user terminal of event invitation information based on an input operation of the other user information in a browser of the user terminal; The status saving system of claim 1, characterized in that the server issues a non-fungible token to the other user based on an event participation operation in a browser on the other user's terminal, and associates the user information with the other user information to register the group.

3. The non-fungible token is displayed as an image in a browser on the user device; 3. The status saving system according to claim 2, wherein an image relating to the non-fungible token changes in response to an update or change of the non-fungible token.

4. The status saving system according to any one of claims 1 to 3, characterized in that the specified action operation is one of a specified operation when a predetermined position is reached, an operation for reading a near-field wireless communication tag, an operation for reading a one-dimensional code or a two-dimensional code, a payment operation using a user terminal, an operation for uploading photo image data or video data taken with a user terminal to a social networking service, and an operation for tagging and sharing on a social networking service.

5. Further comprising a code reader; When the user's status information is a preset status and a predetermined code display operation is performed on the user terminal, the server generates a one-dimensional code or a two-dimensional code based on the updated non-fungible token and transmits it to the user terminal; The user terminal displays the received one-dimensional code or two-dimensional code; When the code reader reads the one-dimensional code or the two-dimensional code displayed on the user terminal, the code reader transmits information of the read one-dimensional code or the two-dimensional code to a server; 5. The status saving system according to claim 4, wherein the server is configured to register information indicating that the code has been read and user information contained in the received one-dimensional or two-dimensional code information in a database.

6. A program for a status saving system that saves status information according to an action of an event of a user terminal, an issuing step in which the server issues a non-fungible token to the user based on an event participation operation on the browser of the user terminal; a first non-fungible token changing step in which the server adds user information to the non-fungible token based on a user information input operation on the user terminal, thereby changing the non-fungible token by updating the non-fungible token, and stores the changed non-fungible token as status information; a second non-fungible token changing step in which the server changes the non-fungible token by adding information about the predetermined action to the updated non-fungible token based on a predetermined action operation set in the user terminal, and stores the changed non-fungible token as status information; and an event notification sending step in which, at the time of the next event, the server sends notification information for the next event to the user terminal based on the user information in accordance with the settings.

Images