Information processing system, information processing method and server

Abstract

To display and utilize an optically readable object with both convenience and security. [Solution] The information processing system includes a server that generates a data set for simultaneously displaying different objects in each of multiple display sections, in which different objects are successively displayed by switching them at the expiration of a fixed rotation time, with the switching timing for each of the multiple display sections being different, and all objects being optically readable objects of the same format that represent different random character strings, and a service provider-side browser that draws the objects based on the data set and displays them on a display device.

Description

[Technical Field]

[0001] The present disclosure relates to an information processing system, an information processing method, and a server that display optically readable objects (two-dimensional codes, one-dimensional codes, number sequences, character strings, etc.). [Background technology]

[0002] Displaying optically readable objects (two-dimensional codes, one-dimensional codes, number sequences, character strings, etc.) and reading them with a terminal device or visually is utilized in various fields and applications. For example, a staff member from the organizer uses a reader to read a two-dimensional code displayed on the mobile device of an event participant to allow entry to the event, a customer uses their mobile device to read a two-dimensional code printed on paper in a store to perform code payment, and a time-limited one-time password is displayed on a mobile device and the user reads it visually and manually enters it into an input window. [Prior art documents] [Patent documents]

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

[0004] The above use cases have the following challenges. In an example where event organizer staff use a reader to read a 2D code displayed on an event participant's mobile device to allow entry to the event, participants may have difficulty displaying the 2D code on their mobile device, which could result in queues (traffic jams) and disrupt smooth entry. Furthermore, if the 2D code displayed on a mobile device is time-limited to prevent fraud, the reader may take time to read it, delaying the timing of the read and having to wait for the next new 2D code to appear, further increasing the time it takes. In an example where a customer uses their mobile device to scan a 2D code printed on paper in a store for code payment, a malicious individual could easily commit fraud by replacing the genuine 2D code with a fake one, posing a security problem. In an example where a time-limited one-time password is displayed on a mobile device and the user visually reads it and manually enters it into the input window, some users, such as elderly people, may find it difficult to visually read, memorize, and manually enter the one-time password within the expiration date.

[0005] In view of the above circumstances, an object of the present disclosure is to display and utilize optically readable objects in a manner that is both convenient and secure. [Means for solving the problem]

[0006] An information processing system according to an embodiment of the present disclosure includes: a server that generates a data set for simultaneously displaying different objects in each of a plurality of display sections, wherein different objects are successively displayed in each display section by switching them at the expiration of a fixed rotation time, the timing of switching between the plurality of display sections being different, and all of the objects are optically readable objects of the same format in which different random character strings are expressed; a service provider-side browser that renders the object based on the data set and displays it on a display device; It is equipped with: [Effects of the Invention]

[0007] According to the present disclosure, it is possible to display and utilize optically readable objects with both convenience and security.

[0008] The effects described here are not necessarily limited to those described herein, and may be any of the effects described in this disclosure. [Brief explanation of the drawings]

[0009] [Figure 1] 1 illustrates a schematic overview of an information processing system according to a first embodiment of the present disclosure. [Figure 2] 1 shows an information processing system. [Figure 3] An example of a database design is shown below. [Figure 4] 1 shows the functional configuration of an information processing system for realizing the first operation (displaying a two-dimensional code). [Figure 5] 10 shows the operation flow of the information processing system for realizing the first operation (displaying a two-dimensional code). [Figure 6] A screen of the service provider's browser is shown. [Figure 7] 10 shows the functional configuration of an information processing system for realizing the second operation (entry of a participant). [Figure 8] 10 shows the operational flow of the information processing system for realizing the second operation (entrance of a participant). [Figure 9] 10 shows the ticket information display screen before activation. [Figure 10] 11 shows the ticket information display screen after validation. [Figure 11] 10 is a schematic diagram illustrating an information processing system according to a second embodiment of the present disclosure. [Figure 12] 10 shows a display screen according to a third embodiment of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0010] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings.

[0011] I. First Embodiment

[0012] 1. Information Processing System

[0013] FIG. 1 schematically illustrates an overview of an information processing system according to a first embodiment of the present disclosure.

[0014] An overview of this embodiment will be described. As shown in FIG. 1A, typically, at the entrance to an event venue, organizer staff use a reader to read an object (e.g., a two-dimensional code) displayed on the mobile device of an event participant to allow entry to the event. However, if participants have difficulty displaying the object on their mobile device, there is a risk that participants will not be able to enter smoothly and at a good pace, resulting in a queue (traffic jam). Furthermore, if the object displayed on the mobile device is time-limited to prevent fraudulent activities, the reader may take time to read it, delaying the timing, and consciously waiting for the next new object to appear, which can further increase the time it takes.

[0015] In consideration of the above circumstances, in this embodiment, as shown in FIG. 1B, first, to prevent congestion caused by participants taking time to display the object on their user devices, an object (in this example, a two-dimensional code) is displayed on a monitor at the venue, and participants photograph the object with their mobile devices. Second, to prevent fraudulent activity, the displayed object is time-limited and changes every certain period of time. Third, to prevent the photographer (participant) from missing the opportunity to take a photo due to time spent launching a camera app, etc., and having to wait for the next new object to appear, multiple valid objects are always displayed simultaneously, and at least one of these objects has sufficient time remaining until its expiration date. When a participant photographs the object with their mobile device, the pre-purchased ticket is validated and displayed on the mobile device. Organizer staff visually confirm the validated ticket and allow the participant to enter.

[0016] FIG. 2 shows an information processing system.

[0017] The information processing system 1 is an event management system 1. The event management system 1 is a system that allows participants who have purchased tickets for an event in advance to enter the event at the venue on the day of the event. The event may be any event, whether paid or free, such as a seminar, exam, concert, etc.

[0018] The information processing system 1 includes a server 10 that executes a web application 16, a service provider-side browser 22 that runs on a service provider-side terminal 20, and a user terminal-side browser 32 that runs on a user terminal 30. The server 10, the service provider-side terminal 20, and the user terminal 30 are connected via a network N such as the Internet.

[0019] The server 10 manages tickets and participants for various events managed by the event management system 1. The server 10 cooperates with a service provider browser 22 running on a service provider terminal 20 and a user terminal browser 32 running on a user terminal 30 to enable participants to enter the event. Various data managed by the server 10 is stored in a database 40. The database 40 may be provided in a local storage device of the server 10, or may be connected to the server 10 via a network N.

[0020] The service provider terminal 20 is a device used by staff of the service provider (in this example, the event organizer) at the venue on the day of the event. The service provider terminal 20 is, for example, a personal computer, a tablet computer, etc. The service provider browser 22 executed by the service provider terminal 20 displays an object (two-dimensional code, one-dimensional code, number sequence, character string, etc.) used in the entrance process on the display device 21. In this embodiment, the object used in the entrance process is a two-dimensional code, specifically a QR code (registered trademark). The display device 21 may be a display built into the service provider terminal 20 or an external monitor.

[0021] The user terminal 30 is a mobile device such as a smartphone or tablet computer. Participants use the user terminal 30 to purchase tickets for an event in advance. The user terminal 30 has a built-in camera 31, and on the day of the event, the camera 31 photographs an object displayed on the display device 21. A user terminal-side browser 32 executed on the user terminal 30 transmits data related to the photographed object to the server 10 and accepts a validation process for the ticket purchased in advance from the server 10. This allows the event participant, who is the owner of the user terminal 30, to participate in the event.

[0022] 2. Database design example

[0023] Figure 3 shows an example of a database design.

[0024] A description will be given of design examples of various tables stored in the database 40. The database 40 stores a host table 410, a participant table 420, an event table 430, and a ticket table 440.

[0025] The organizer table 410 contains an organizer ID 411, an organizer name 412, an organizer login ID 413, and a password 414. The organizer ID 411 is a primary key that uniquely identifies an organizer. The organizer name 412 identifies each organizer who uses the event management system 1. The organizer login ID 413 is an ID unique to the organizer identified by the organizer name 412. The password 414 may be hashed.

[0026] The participant table 420 contains a participant ID 421, a participant name 422, a participant login ID 423, and a password 424. The participant ID 421 is a primary key that uniquely identifies a participant. The participant name 422 identifies each event participant. The participant login ID 423 is an ID unique to the participant identified by the participant name 422. The password 424 may be hashed.

[0027] The event table 430 contains an event ID 431, an event name 432, a host foreign key 433, a rotation time 434, a number of partitions 435, and a ticket validity period 436. The event ID 431 is a primary key that uniquely identifies an event. The event name 432 identifies each event managed by the event management system 1. The host foreign key 433 is linked to the host ID 411 in the host table 410 and uniquely identifies the host of the event to which the host ID 411 is assigned. The rotation time 434 is the interval at which the display of the object (two-dimensional code) displayed on the display device 21 is switched, and its initial value may be 60 (unit: seconds). The number of partitions 435 is the number of partitions of the object displayed on the display device 21 (in other words, the number of objects displayed simultaneously), and is an integer equal to or greater than 2, and its initial value may be 2. The ticket validity period 436 is the time from when the ticket is validated to when it is invalidated, and its initial value may be 600 (unit: seconds).

[0028] The ticket table 440 contains a ticket ID 441, a participant foreign key 442, an event foreign key 443, and an activation time 444. The ticket ID 441 is a primary key that uniquely identifies a ticket. The participant foreign key 442 is linked to the participant ID 421 in the participant table 420, and uniquely indicates the participant who purchased the ticket to which the ticket ID 441 is assigned. The event foreign key 443 is linked to the event ID 431 in the event table 430, and uniquely indicates the event to which the event ID 431 is assigned. The activation time 444 indicates the time when the ticket identified by the ticket ID 441 was activated, and its initial value is NULL (i.e., not activated).

[0029] 3. First operation of the information processing system (displaying two-dimensional code)

[0030] Fig. 4 shows the functional configuration of an information processing system for realizing the first operation (displaying a two-dimensional code). Fig. 5 shows the operational flow of the information processing system for realizing the first operation (displaying a two-dimensional code).

[0031] Using the service provider-side browser 22 installed in the service provider-side terminal 20, the organizer opens the organizer login form of the information processing system 1 (step S201). The organizer enters the organizer login ID and password into the organizer login form (step S202).

[0032] The web application 16 of the server 10 (hereinafter simply referred to as the server 10) receives the organizer login ID and password from the service provider browser 22, queries the database 40 (step S101), and collates them with the combination of the organizer login ID 413 and password 414 in the organizer table 410 (step S102). If the entered combination of login ID and password is incorrect, the server 10 displays an error message on the service provider browser 22 and prompts the user to enter the organizer login ID and password again (return to the beginning). On the other hand, if the entered combination of organizer login ID and password is correct, the server 10 stores the value of the organizer ID 411 linked to the combination of the organizer login ID 413 and password 414 in a cookie of the service provider browser 22 (step S103).

[0033] The server 10 reads out from the event table 430 the combination (one or more) of the event ID 431 and the event name 432 for which the organizer ID 411 is registered as the organizer external key 433 (step S104), and displays it as a list of events (list of event names 432) on the service provider side browser 22 (step S105).

[0034] The organizer selects the event name 432 of a specific event for which admission processing is to begin from the list of events (list of event names 432) displayed on the service provider-side browser 22 (step S203).

[0035] The server 10 sends the program 23 (typically a JavaScript program) for drawing a two-dimensional code on the screen of the service provider browser 22 to the service provider browser 22 (step S106). The service provider browser 22 executes the program 23 received from the server 10 (step S204).

[0036] The program 23 and the server 10 start synchronization. The synchronization is achieved by polling (periodic inquiry) from the program 23 to the server 10 or by two-way communication via WebSocket. Whether synchronization is by polling or by two-way communication via WebSocket, the first communication is executed from the program 23 to the server 10. At the first communication from the program 23 to the server 10, the program 23 sends the event ID 431 paired with the event name 432 to the server 10 (step S205). The server 10 receives the event ID 431.

[0037] The server 10 queries the database 40 using the received event ID 431 (step S107), obtains data on the event identified by the event ID 431 in the event table 430, and reads out the organizer ID 411 linked to the organizer foreign key 433 linked to the event ID 431 (step S108). The server 10 checks whether the value of the read-out organizer ID 411 matches the value of the organizer ID 411 stored in the cookie (step S103) (step S109), and terminates the processing if they do not match. On the other hand, if the value of the read-out organizer ID 411 matches the value of the organizer ID 411 stored in the cookie (step S103) (step S110), the server 10 performs the following processing.

[0038] The server 10 allocates an area 12 on the memory 11 (step S111). An area 12 is allocated for each event. The area 12 is an area for storing a variable 13, an event ID 14, and a dataset 15. The variable 13 is an integer value indicating the number of times a two-dimensional code has been issued. The event ID 14 is the same as the event ID 431 in the event table 430. The dataset 15 is a combination of a partition number 151, a random integer 152 (random character string), and an expiration date 153. The length of the array of the dataset 15 (the number of datasets 15) is equal to the value of the number of partitions 435 in the event table 430.

[0039] The server 10 generates a dataset 15 (step S112) and stores it at the beginning of the array of datasets 15 in the area 12 (step S113-1). The rules for dataset 15 are as follows: The partition number 151 is the remainder when the value of variable 13 is divided by the number of partitions 435 in the event table 430. The random integer 152 (random string) can have any number of digits, but it is recommended to use a UUID (128-bit integer). The expiration date 153 is the value obtained by adding the rotation time 434 in the event table 430 to the current time.

[0040] The server 10 generates a URL in which the selected event ID 14 and a random integer 152 are embedded (step S114-1). The server 10 converts the URL into image data (bitmap data or SVG data) for drawing a two-dimensional code (step S115-1). The server 10 sends the image data, partition number 151, and expiration date 153 to the program 23 by the above-mentioned synchronization (step S116-1).

[0041] The server 10 repeats the following process every n seconds from the end time of step S116-1. The server 10 adds 1 to the variable 13 (increments it), generates a random integer 152, generates a dataset 15 according to the above-mentioned rules, and stores it as the m-th element of the array of datasets 15 in the area 12 (step S113-2). m is equal to the partition number 151 of the dataset 15. n is the value of the rotation time 434 divided by the number of partitions 435 in the event table 430; in this example, n = 60 divided by 2 = 30 (seconds). The server 10 generates a URL in which the selected event ID 14 and the random integer 152 are embedded (step S114-2). The server 10 converts the URL into image data (bitmap data or SVG data) for drawing a two-dimensional code (step S115-2). The server 10 sends the image data, the partition number 151 and the expiration date 153 to the program 23 in accordance with the above-mentioned synchronization (step S116-2).

[0042] FIG. 6 shows the screen of the browser on the service provider side.

[0043] The screen of the display device 21 of the service provider-side browser 22 is divided into a plurality of display sections 24. The number of display sections 24 is equal to the number of sections 435 in the event table 430. The program 23 of the service provider-side browser 22 draws an object 26 (two-dimensional code) and displays it in the display section 24 on the screen of the service provider-side browser 22 that corresponds to the section number 151 received from the server 10, using the image data received from the server 10 (step S206).

[0044] The program 23 of the service provider's browser 22 periodically (typically every second) displays in each display section 24 a numerical value 25 indicating the time remaining until the expiration date of each of the multiple objects 26 simultaneously displayed in the multiple display sections 24. The numerical value 25 indicating the time remaining until the expiration date is the difference between the expiration date 153 received from the server 10 and the current time. All of the numerical values ​​25 simultaneously displayed in the multiple display sections 24 are different. In this example, n=30 (seconds), so the difference between the two numerical values ​​25, 25 indicating the time remaining until the expiration date of each of the two objects 26 is always 30 (seconds). In the example shown in the figure, it is 43-13=30 (seconds).

[0045] The program 23 of the service provider-side browser 22 displays the object 26 while changing the display mode over time from the point when the difference between the expiration date 153 of each object 26 and the current time reaches a first threshold (e.g., 50% = 30 seconds) until the expiration date 153. For example, changing the display mode over time may be achieved by changing the color density, hue, saturation, and / or brightness of the object 26 in multiple stages.

[0046] Changing the color density of the object 26 in multiple stages typically involves changing it in multiple stages from a dark color to a light color. Changing the hue of the color of the object 26 in multiple stages may involve changing the color of the object 26 in multiple stages (three or more stages in this example) in the order of blue, purple, and red, for example. On the other hand, in consideration of the possibility that participants may have color vision deficiencies, it is preferable to avoid expressing that the expiration date is approaching by changing the hue. The method of expressing that the expiration date is approaching by changing the color in multiple stages from a dark color to a light color is preferable, as it is likely that the majority of participants will be able to intuitively understand that the expiration date is approaching.

[0047] Furthermore, the program 23 of the service provider-side browser 22 hides the object 26 when the difference between the expiration date 153 and the current time reaches a second threshold (the second threshold is smaller than the first threshold) (for example, 5 seconds) before the expiration date 153 of each object 26. In short, the program 23 of the service provider-side browser 22 adjusts the color of each object 26 so that it becomes lighter as the difference between the expiration date 153 and the current time falls below 50% of the rotation time 434 in the event table 430 and the expiration date 153 approaches 0, and the object 26 becomes completely invisible just before the expiration date 153.

[0048] The second threshold value for hiding the object 26 (i.e., the number of seconds remaining until the expiration date 153) is preferably at least 5 seconds. This is because the participant needs to tap the URL displayed on the screen of the user terminal browser 32 within the expiration date (within 5 seconds in this example) of the object 26 optically read by the camera 31 of the user terminal 30 (step S306, described below).

[0049] As described above, the server 10 generates a data set 15 for simultaneously displaying different objects 26 in each of multiple display sections 24 identified by section numbers 151. All of the objects 26 are optically readable objects 26 of the same format (two-dimensional codes such as QR codes) that express different random character strings (random integers 152). Note that, although the "optically readable objects that express random character strings" are two-dimensional codes (specifically, QR codes) in this embodiment, they may also be one-dimensional codes (barcodes), number strings, or character strings (optically readable by the human eye or software).

[0050] In each display section 24 specified by section number 151, different objects 26 are displayed successively, switching at regular rotation time expiration times 153. The switching timing of each of the multiple display sections 24 specified by section number 151 differs due to differences in the timing of image data transmission (step S116-2). Due to differences in the timing of image data transmission (step S116-2), the program 23 of the service provider-side browser 22 displays the objects 26 so that the display modes (color intensities) of the multiple objects 26 displayed simultaneously in the multiple display sections 24 all differ due to differences in the timing of image data transmission (step S116-2).

[0051] As a result, the image data for rendering each different object 26 is different, and all objects 26 displayed on the display device 21 are different. Therefore, the displayed objects 26 are time-limited and can be switched at regular intervals, contributing to preventing fraud. Furthermore, multiple valid objects 26 are always displayed simultaneously, and at least one of the objects 26 (dark-colored objects) has sufficient time remaining until the expiration date 153. This eliminates the need for the photographer (participant) to miss the opportunity to take a photo due to time spent launching a camera app, and then wait until the next new object is displayed. Participants may photograph either the dark-colored object 26-1 or the light-colored object 26-2. However, because the dark-colored object 26-1 has a longer time remaining until the expiration date 153, a message encouraging the participant to photograph the dark-colored object 26-1 may be displayed on the display device 21 or broadcast by audio.

[0052] Note that if the organizer logs in using the service provider browser 22 running on multiple service provider terminals 20, the server 10 has already reserved the area 12 for the relevant event when synchronization with the second or subsequent service provider browser 22 begins. In this case, the server 10 does not generate a new data set 15, but instead creates combinations of image data, partition numbers 151, and expiration dates 153 from all data sets 15 existing in the area 12, and sends these combinations together to the program 23. The program 23 then displays multiple objects 26 with a density corresponding to each expiration date 153.

[0053] 4. Second Operation of Information Processing System (Participant Entry)

[0054] Fig. 7 shows the functional configuration of the information processing system for realizing the second operation (entrance of a participant). Fig. 8 shows the operational flow of the information processing system for realizing the second operation (entrance of a participant).

[0055] Using the user terminal browser 32 installed in the user terminal 30, the participant opens a participant login form of the information processing system 1. The participant enters a participant login ID and password in the login form (step S301). The user terminal browser 32 sends the entered participant login ID and password to the server 10 via HTTP communication (step S302).

[0056] The server 10 receives the participant login ID and password from the user terminal browser 32, queries the database 40 (step S121), and compares them with the participant table 420 (step S122). If the combination of participant login ID and password received from the user terminal browser 32 is incorrect compared to the participant login ID 423 and password 424 in the participant table 420, the server 10 displays an error message on the user terminal browser 32 and prompts the user to enter the participant login ID and password again (return to the beginning). On the other hand, if the entered combination of participant login ID and password is correct, the server 10 stores the value of the participant ID 421 linked to the combination of participant login ID 423 and password 424 in a cookie of the user terminal browser 32 (step S123).

[0057] The server 10 reads out from the ticket table 440 the event foreign key(s) 443 in which the participant ID 421 is registered as the participant foreign key 442, and reads out from the event table 430 the event name(s) 432 linked to the read event foreign key 443 (step S124). The server 10 displays the read event name(s) 432 as a list of events (list of event names 432) on the user terminal side browser 32 (step S125).

[0058] The participant selects the event name 432 of a specific event for which admission processing is to begin from the list of events (list of event names 432) displayed on the user terminal browser 32 (step S303). The user terminal browser 32 sends the selected event name 432 to the server 10 (step S304). The server 10 receives the event name 432.

[0059] The server 10 queries the database 40 using the received event name 432 (step S126) and reads out the event ID 431 linked to the event name 432 in the event table 430. The server 10 reads out the ticket ID 441 linked to the event foreign key 443 linked to the read event ID 431 and the participant foreign key 442 linked to the participant ID 421 in the ticket table 440 (step S127). The server 10 stores the read ticket ID 441 in a cookie of the user terminal browser 32 (step S128).

[0060] FIG. 9 shows the ticket information display screen before validation.

[0061] The server 10 displays the pre-validation ticket information (event name 432, participant name 422, etc.) on the user terminal browser 32 as a pre-validation ticket information display screen 323 (step S129). The ticket information includes the event name 432 in the event table 430 linked to the event foreign key 443 in the ticket table 440, and the participant name 422 in the participant table 420 linked to the participant foreign key 442 in the ticket table 440.

[0062] One of the multiple objects 26 (typically a dark-colored object 26-1) displayed on the screen of the display device 21 of the service provider side browser 22 is optically read by the camera 31 of the user terminal 30 operated by the participant.

[0063] As described above, multiple objects 26 that can be read as a certain character string are displayed in parallel on the display device 21 of the computer of the service provider's browser 22. Each object 26 has an expiration date 153 that differs by a certain interval, and as the expiration date 153 approaches, the display mode (color density) of the object 26 changes (the color gradually becomes lighter). By scanning the dark-colored object 26-1 with the camera 31 of the user terminal 30, participants can unconsciously capture an image with a long expiration date 153.

[0064] The two-dimensional code reader application 33 of the user terminal 30 converts one optically read object 26 into a URL (step S305). This URL is the original URL that is converted into image data of the two-dimensional code (step S115), and is the URL in which the event ID 14 and a random integer 152 are embedded (step S114). When a participant taps the URL displayed on the screen of the user terminal-side browser 32 of the user terminal 30 within the expiration date of the object 26 optically read by the camera 31, the user terminal-side browser 32 accesses the URL (step S306).

[0065] The server 10 obtains from the user terminal browser 32 the participant ID 421 of the participant table 420 stored in the cookie (step S123), the event ID 14 embedded in the URL, and a random integer 152 (step S130). The server 10 searches the ticket table 440 for a corresponding record (ticket ID 441) using the participant foreign key 442 linked to the participant ID 421 and the event foreign key 443 linked to the event ID 14 embedded in the URL as keys (step S131). If there is no corresponding record (ticket ID 441 linked to the participant ID 421 and event ID 14) in the ticket table 440, the server 10 displays an error message on the user terminal browser 32 and ends the process.

[0066] On the other hand, if there is a corresponding record (ticket ID 441 linked to participant ID 421 and event ID 14) in the ticket table 440 (step S132), the server 10 searches the memory 11 for an area 12 having the event ID 14 linked to the event foreign key 443 linked to the corresponding record (ticket ID 441) (step S133). If there is no area 12 having the event ID 14 in the memory 11, the server 10 displays an error message on the user terminal browser 32 and ends the process.

[0067] On the other hand, if the memory 11 contains an area 12 having the event ID 14 (step S134), the server 10 searches the arrays of the data sets 15 stored in the area 12 for one data set 15 having the same random integer 152 as the random integer 152 embedded in the URL (step S135).If the area 12 does not contain a data set 15 having the same random integer 152, the server 10 displays an error message on the user terminal browser 32 and ends the process.

[0068] FIG. 10 shows the ticket information display screen after validation.

[0069] On the other hand, if a data set 15 having the same random integer 152 is present in the area 12 (step S136), the server 10 performs the following process: The server 10 writes the current time into the activation time 444 linked to the ticket ID 441 of the corresponding record in the ticket table 440 (step S137). The server 10 reads the ticket validity period 436 linked to the event ID 431 that is the same as the event ID 14 from the event table 430 (step S138).

[0070] The server 10 displays information about the event identified by the event ID 14 on the user terminal browser 32 as a post-validation ticket information display screen 324. Specifically, the server 10 displays, as post-validation ticket information, the event name 432, participant names 422, etc. that have already been displayed (step S129), as well as the validation time 444 (check-in time), admission deadline 321, animation 322, etc. on the post-validation ticket information display screen 324 of the user terminal browser 32 (step S139). The admission deadline 321 is the time obtained by adding the ticket validity period 436 (e.g., 600 seconds) to the validation time 444. The animation 322 is a measure to prevent unauthorized entry to the event by using a screenshot (still image) of the post-validation ticket information screen. The animation 322 may be, for example, a change in color gradation.

[0071] The participant shows the organizer staff the post-validation ticket information display screen 324 displayed on the user terminal browser 32. The organizer staff visually checks the post-validation ticket information display screen 324 (particularly the admission time limit 321 and animation 322), and allows the participant to enter if the admission time limit 321 is not exceeded and the animation 322 is moving (not a still image).

[0072] The server 10 periodically scans all areas 12 in the memory 11 and discards (releases) areas 12 where the corresponding event has ended. To efficiently manage admission to a large number of events, the data set 15 is preferably stored in an area 12 in the memory 11, but may also be stored in a database 40.

[0073] According to this embodiment, first, an object (in this example, a two-dimensional code) is displayed on a monitor at the venue, and participants photograph the object with their mobile devices. This eliminates congestion caused by participants struggling to display the object on their user devices. Second, the objects are time-limited and are switched at regular intervals. Multiple valid objects are always displayed simultaneously, and at least one of the objects has sufficient time left until its expiration date. This prevents fraudulent activity and eliminates the need for the photographer (participant) to miss the opportunity to photograph due to time consuming tasks such as launching a camera app and waiting for the next new object to appear. When a participant photographs the object with their mobile device, the pre-purchased ticket is validated and displayed on the mobile device. Since organizer staff simply visually confirm the validated ticket and allow the participant to enter, congestion caused by organizer staff struggling to confirm the ticket is eliminated. In this way, this embodiment allows optically readable objects to be displayed and utilized with both convenience and security.

[0074] II. Second Embodiment

[0075] In the following embodiments and examples, the same configurations and operations as those already described will be denoted by the same reference numerals, and explanations thereof will be omitted, with differences being mainly described.

[0076] FIG. 11 schematically illustrates an information processing system according to the second embodiment of the present disclosure.

[0077] The first embodiment described above can be applied to code-based payment in stores. As shown in Figure 1(A), code-based payment is typically performed by reading a two-dimensional code printed on paper media in a store with a customer's mobile device. However, this poses a security problem, as a malicious person could easily commit fraud by replacing a genuine two-dimensional code with a fake one.

[0078] In consideration of the above, in this embodiment, as shown in FIG. 1B, first, a code payment object (in this example, a two-dimensional code) is presented on a display device (such as a tablet computer) in the store, and the customer photographs the code payment object with their mobile device. Second, to prevent fraudulent activity, the displayed code payment object is time-limited and changes every certain period of time. Third, to prevent the photographer (customer) from missing the opportunity to take a photo due to time spent launching a camera app and having to wait for a new object to be displayed, multiple valid objects are always displayed simultaneously, and at least one of these objects has sufficient time remaining until its expiration date. This enables code payment to be performed with high security and usability. The mechanism for displaying the code payment object is the same as in the first embodiment.

[0079] III. Third Embodiment

[0080] FIG. 12 shows a display screen according to the third embodiment of the present disclosure.

[0081] It is common for token software to display a time-limited one-time password on a mobile device, etc., and for the user to visually read it and manually enter it into an input window. However, some users, such as elderly people, may find it difficult to visually read, memorize, and manually enter the one-time password into the input window within the expiration date. Furthermore, if the one-time password displayed by token software on a mobile device is time-limited, if the user is late in reading it, they may have to wait consciously until the next new one-time password is displayed, which can take even more time.

[0082] In view of the above, in this embodiment, the displayed object (a character string such as a numeric sequence serving as a one-time password) is time-limited and is switched every fixed time. Furthermore, to avoid a delay in the user's reading and the need to wait for the next new object to be displayed, multiple valid objects are always displayed simultaneously, and at least one of these objects has sufficient time remaining until its expiration date. This allows the one-time password to be displayed with high security and usability.

[0083] The method by which the token software generates the character string (sequence) that forms the image (i.e., the algorithm for generating the one-time password) is not limited and may be any method. For example, as in the first embodiment, the server may periodically generate one-time passwords and transmit them to the token software (mobile terminal application) by synchronization. However, this method cannot be realized unless the server and the mobile terminal application are connected via the Internet.

[0084] Another method is TOTP (Time-based One-time Password). In TOTP, the token software holds a shared secret key issued by the server, and one-time passwords can be generated using the shared secret key and a counter (an integer value derived from the current time). Because the token software (mobile terminal application) and the server share a secret key, the same one-time password can be generated if the counter value is the same. This method can be used to achieve two-factor authentication.

[0085] TOTP uses a counter obtained by dividing UNIX time (the number of seconds elapsed since 00:00:00 on January 1, 1970 in UTC time) by a time called the "time step." The "time step" can be 30 seconds. The algorithm for deriving a one-time password from a shared secret key and a counter is published as RFC4226.

[0086] The token software according to this embodiment uses two counters to generate two one-time passwords. When the current UNIX time is t and the time step is s, the values ​​of each counter can be calculated as follows: where floor is a function that rounds down to an integer.

[0087] First counter (c1): floor((ts*0.5) / s)

[0088] Second counter (c2): floor (t / s)

[0089] The first counter is a counter generated 15 seconds ago using the original TOTP method. The expiration date 153 of the one-time password generated using the first and second counters is calculated as follows:

[0090] The expiration date of the one-time password generated using the first counter c1 is 153(e1):(c1+0.5)*s

[0091] The expiration date of the one-time password generated using the second counter c2 is 153(e2):(c2+1)*s

[0092] For example, if the current time is 9:46:42 on February 18, 2025, then t = 1739872002. If s = 30, then c1 = 57995732 and c2 = 57995733. e1 = 1739872005, which corresponds to 18:46:45 on February 18, 2025. e2 = 1739872020, which corresponds to 18:47:00 on February 18, 2025.

[0093] The token software according to this embodiment displays multiple one-time passwords (typically two) on the display. However, the image density (opacity) is adjusted so that the image becomes lighter as the expiration date 153 approaches, and becomes completely invisible just before the expiration date 153. The server similarly generates two one-time passwords using two counters, and determines that authentication is successful if either one matches the character string entered by the user.

[0094] In this embodiment, multiple objects (character strings such as number sequences) that can be read as a certain character string are displayed in parallel on a display device. Each object (character strings such as number sequences) has an expiration date that differs by a certain interval, and as the expiration date approaches, the display mode (color density) of the object (character strings such as number sequences) changes (the color gradually becomes lighter). By visually reading the dark-colored objects (character strings such as number sequences), the user can unconsciously visually read the character string with a long expiration date.

[0095] According to each embodiment, optically readable objects can be displayed and utilized with both convenience and security.

[0096] Although the embodiments and modified examples of the present technology have been described above, the present technology is not limited to the above-described embodiments, and it goes without saying that various modifications can be made within the scope of the gist of the present technology. [Explanation of symbols]

[0097] 1: Information processing system, 10: Server, 11: Memory, 12: Area, 13: Variable, 15: Data set, 16: Application, 20: Service provider side terminal, 21: Display device, 22: Service provider side browser, 30: User terminal, 32: User terminal side browser, 40: Database.

Claims

1. a server that generates a data set for simultaneously displaying different objects in each of a plurality of display sections, wherein different objects are successively displayed in each display section by switching them at the expiration of a fixed rotation time, the timing of switching between the plurality of display sections being different, and all of the objects are optically readable objects of the same format in which different random character strings are expressed; a service provider-side browser that renders the object based on the data set and displays it on a display device; An information processing system comprising:

2. 2. The information processing system according to claim 1, The dataset for displaying each object is A partition number indicating one of the display partitions; The expiration date; Image data for rendering an object, where all objects displayed on the display device are different, and image data for rendering all the different objects are different; and Contains Information processing system.

3. 2. The information processing system according to claim 1, The service provider-side browser displays the object while changing the display mode over time from the time when the difference between the expiration date of each object and the current time reaches a first threshold until the expiration date. Information processing system.

4. 4. The information processing system according to claim 3, The change in the display mode over time means changing the color density, hue, saturation, and / or brightness of the object in multiple stages. Information processing system.

5. 2. The information processing system according to claim 1, The service provider side browser displays the plurality of objects simultaneously displayed in the plurality of display sections so that the display modes of the plurality of objects are all different. Information processing system.

6. 2. The information processing system according to claim 1, The service provider-side browser hides the object when the difference between the expiration date and the current time reaches a second threshold before the expiration date of each object. Information processing system.

7. 2. The information processing system according to claim 1, The service provider side browser displays a numerical value indicating the time remaining until the expiration date of each of the plurality of objects simultaneously displayed in the plurality of display sections, and the numerical values ​​simultaneously displayed in the plurality of display sections are all different. Information processing system.

8. 8. The information processing system according to claim 1, the server generates a URL in which an event ID and a random character string that is different for each of the objects are embedded, and converts the URL into image data for drawing the object, thereby generating image data for each of the objects; one of the plurality of objects displayed on the display device is optically read by a camera of the user terminal, and the optically read object is converted into the URL by a reader of the user terminal; the information processing system further includes a user terminal browser that accesses the URL; The server displays information about the event identified by the event ID embedded in the URL on the browser of the user terminal. Information processing system.

9. 9. The information processing system according to claim 8, The event ID is an event ID that identifies the name of the event for which the participant identified by the participant ID purchased a ticket, The server displays the ticket information before validation on the browser of the user terminal, the user terminal browser accesses the URL converted from any one of the plurality of objects displayed on the display device; When the event ID embedded in the URL is linked to the participant ID, the server displays the validated ticket information as information related to the event ID on the browser of the user terminal. Information processing system.

10. 10. The information processing system according to claim 9, The validated ticket information displayed by the browser on the user terminal includes animation. Information processing system.

11. A server generates a data set for simultaneously displaying different objects in each of a plurality of display sections, and the different objects are successively displayed in each display section by switching them at the expiration of a certain rotation time, the timing of switching between the plurality of display sections being different, and all the objects are optically readable objects of the same format in which different random character strings are expressed; The service provider side browser renders the object based on the data set and displays it on a display device. Information processing methods.

12. A server that generates a data set for simultaneously displaying different objects in each of a plurality of display sections, in which different objects are displayed consecutively by switching them at the expiration of a fixed rotation time in each display section, the timing of switching between the plurality of display sections being different, and all of the objects are optically readable objects of the same format that express different random character strings. server.

Images