Ticket information processing device and control program
The ticket information processing device dynamically adjusts guidance priority based on queue ticket issuance status, addressing inefficiencies in existing systems by prioritizing users with fewer tickets and avoiding those with many tickets, thus optimizing user guidance.
Patent Information
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- MIXI INC
- Filing Date
- 2026-03-31
- Publication Date
- 2026-06-18
AI Technical Summary
Existing systems fail to efficiently address the dynamic adjustment of guidance priorities for users based on the issuance status of queue tickets, leading to inflexible and inefficient user guidance.
A ticket information processing device and method that determines guidance priority by considering the issuance status of queue tickets, including the number of times a ticket has been issued, to dynamically adjust guidance based on this status.
Enables appropriate and efficient user guidance by prioritizing users who have issued fewer queue tickets and avoiding guiding those who have issued a large number of tickets, thereby optimizing the guidance process.
Smart Images

Figure 2026099831000001_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to a digital computing or data processing apparatus or method that is particularly suitable for specific applications.
Background Art
[0002] There is known a reception processing system that queries a server for information presented by a user and issues a ticket for reception guidance according to the query result. For example, Patent Document 1 discloses a reception processing system that determines the guidance priority of a user using information read from an identification card inserted into a terminal, issues a ticket with a priority reception number to a user with a high guidance priority, and issues a ticket with a reception number in a different number series from the priority reception number to a user with a low guidance priority.
Prior Art Documents
Patent Documents
[0003]
Patent Document 1
Summary of the Invention
Problems to be Solved by the Invention
[0004] In the reception processing system described in Patent Document 1, it is determined whether a user corresponds to a premium customer with VIP (Very Important Person) treatment based on information such as the transaction amount and deposit balance stored in association with the identification card, and the guidance priority is determined according to the result of the determination. Therefore, the guidance priority of each user hardly changes.
[0005] The problem to be solved by the present invention is to accurately guide users according to the situation.
Means for Solving the Problems
[0006] To solve the above problems, the present invention determines the priority of guidance for a user by using the status of ticket issuance for a queue ticket as one of the judgment conditions. The present invention encompasses at least the following embodiments.
[0007] [A] A ticket information processing device comprising: identification means for identifying the issuance status of a queue ticket for a user using information to be presented by a user requesting a queue ticket for a service to be provided within a predetermined period; and determination means for determining the priority of guidance for the user to be reflected in the queue ticket for the user based on the issuance status identified by the identification means.
[0008] [B] A control method for an information processing device, comprising: an identification step of identifying the status of issuance of a queue ticket to a user using information to be presented to a user requesting a queue ticket for a service to be provided within a predetermined period; and a determination step of determining the priority of guidance for the user to be reflected in the queue ticket for the user based on the issuance status identified in the identification step.
[0009] [C] A control program that causes the computer of an information processing device to implement a specification function that identifies the issuance status of a queue ticket for a user using information presented to the user requesting a queue ticket for a service to be provided within a predetermined period, and a determination function that determines the priority of guidance for the user to be reflected in the queue ticket for the user based on the issuance status identified by the specification function.
[0010] [D] A recording medium that non-temporarily records a control program that causes the computer of an information processing device to implement the following functions: a specification function that identifies the status of issuance of a queue ticket to a user using presentation information that the user presents to the user requesting a queue ticket for a service to be provided within a predetermined period; and a determination function that determines the priority of guidance for the user to be reflected in the queue ticket for the user based on the issuance status identified by the specification function. [Effects of the Invention]
[0011] By issuing queue tickets that reflect the guidance priority determined by this invention, users can be guided appropriately according to the status of queue ticket issuance.
[0012] The "ticket information processing device" in [A] above may be subject to the following technical limitations. Furthermore, similar technical limitations may be applied to the "control method" in [B] above, the "control program" in [C] above, and the control program recorded in the "recording medium" in [D] above, respectively.
[0013] (1) The identification means identifies the issuance status of the queue ticket for the service which may be provided to the user multiple times within the predetermined period, and the determination means determines the guidance priority such that the guidance priority changes according to the issuance status which includes at least the number of times the queue ticket has been issued to the user in the past. This makes it possible to guide the user appropriately according to the number of times the queue ticket has been issued.
[0014] (2) The determination means sets the guidance priority when the number of issuances is less than or equal to the first value higher than the guidance priority when the number of issuances is greater than the first value. This makes it possible to prioritize guidance for users who have issued fewer queue tickets.
[0015] (3) The determination means determines the guidance priority such that the guidance priority decreases as the number of times the number of tickets issued increases. This makes it possible to give priority to users who have been issued fewer queue tickets.
[0016] (4) The determination means further includes an instruction means that does not determine the guidance priority if the number of times the queue ticket has been issued to the user is equal to or greater than the second value, and instructs the issuing means to issue the queue ticket that reflects the guidance priority only when the guidance priority has been determined by the determination means. This makes it possible to avoid guiding users who have been issued a large number of queue tickets. [Brief explanation of the drawing]
[0017] [Figure 1] It is a configuration diagram illustrating the network configuration of the system. (Example 1) [Figure 2] It is a block diagram illustrating the electrical configuration of the server device and the client device. (Example 1) [Figure 3] It is a block diagram illustrating the electrical configuration of the user device. (Example 1) [Figure 4] It is a block diagram illustrating the functional configuration of the system. (Example 1) [Figure 5] It is an explanatory diagram illustrating the items of the ticket-issuing information. (Example 1) [Figure 6] It is a sequence diagram illustrating the procedure for issuing a two-dimensional code. (Example 1) [Figure 7] It is a sequence diagram illustrating the procedure for issuing a sorting ticket. (Example 1) [Figure 8] It is a floor plan of the interior of the venue where the service is provided. (Example 2) [Figure 9] It is an enlarged view of the peripheral area of the section 832 in FIG. 8. (Example 2) [Figure 10] It is a block diagram illustrating the functional configuration of the system. (Example 2) [Figure 11] It is an explanatory diagram illustrating the items of the seat information. (Example 2) [Figure 12] It is a sequence diagram illustrating the procedure for issuing a sorting ticket. (Example 2) [Mode for Carrying Out the Invention]
[0018] [1. Embodiment] [1-1. Outline] Embodiments 1 and 2 relate to a mechanism for issuing sorting tickets for the provided services. In Embodiments 1 and 2, information is presented to a user who requests a sorting ticket, and a sorting ticket reflecting the guidance priority according to the information stored in association with the presented information is issued to the user.
[0019] In Embodiment 1, in order to guide users appropriately according to the situation, the priority of guiding a user is determined by using the status of ticket issuance for users requesting queue tickets as one of the criteria. In Embodiment 2, in order to guide users smoothly according to their location, the priority of guiding a user is determined by using information about the service provision location for users requesting queue tickets as one of the criteria.
[0020] [1-2. Ticket Information Processing Device] The ticket information processing device according to Embodiment 1 (for example, the ticket issuing device 30a in Figure 4) includes an identification means (for example, an identification unit 423a in Figure 4) that identifies the status of issuing a queue ticket to a user using presentation information to be presented to the user requesting a queue ticket for a service to be provided within a predetermined period, and a determination means that determines the guidance priority of the user to be reflected in the queue ticket for the user based on the issuance status identified by the identification means. (For example, the determination unit 424a in Figure 4) and the following are included.
[0021] The ticket information processing device according to Embodiment 2 (for example, the ticket issuing device 30b in Figure 10) includes an identification means (for example, an identification unit 423b in Figure 10) that identifies information about the location where a service is provided to a user using presentation information to be presented to a user requesting a queue ticket for a service provided in a predetermined space, and a determination means (for example, a determination unit 424b in Figure 10) that determines the guidance priority of the user to be reflected in the queue ticket for the user based on the information identified by the identification means.
[0022] The ticket information processing device according to Embodiments 1 and 2 is preferably configured as a client-side device capable of acquiring predetermined information stored on the server side via a communication network in a client-server type ticket information processing system. In this case, the client-side device may be a device installed near the location where the service is provided, or a device carried by an attendant near the location where the service is provided.
[0023] Furthermore, the ticket information processing device according to Embodiments 1 and 2 may be configured as a server-side device capable of providing predetermined information stored on the server side to a client-side device via a communication network in a client-server type ticket information processing system. In this case, the client-side device may be a device installed near the location where the service is provided, a device carried by an attendant near the location where the service is provided, or a device installed in a convenience store or the like.
[0024] In this specification, the following terms are used:
[0025] (1) "Service" means the services provided to the user. The provision of services to the user may be paid or free of charge. The period during which services are provided may be limited to a specified period. Services limited to a specified period may be all or part of a series of actions performed continuously or intermittently within the specified period, or all or part of a single action repeated within the specified period. Each user may receive the services multiple times within the specified period. The method of determining the specified period is arbitrary. Preferably, the specified period has at least a start date. The specified period may be understood as, for example, the period from the start date to the end date, the period from the start date until a specified time has elapsed, or the period from the start date until the termination condition is met. The termination condition is, for example, the depletion of the items that were to be used by the recipient of the service in the provision of the service. Items that were to be used by the recipient of the service are, for example, items that are transferred or lent to the recipient, or items that are materials for these. The location where the service is provided may be inside a designated space that is isolated from the outside or at least partially partitioned. The service provided in the designated space may be provided simultaneously to multiple users within that space.
[0026] (2) “Queue ticket” means a queue ticket or electronic data equivalent to such a queue ticket that displays queue information regarding the service. The queue information is information that can identify the order in which users will be guided for the specified service. Information that can identify the order of guidance may include, for example, the guidance order, guidance timing, and guidance start conditions for the user or the group including the user. The system of queue information may be common to all queue tickets or may differ for some queue tickets. If the queue information regarding the service is displayed on a qualification ticket that indicates eligibility to receive the service, the qualification ticket also serves as a queue ticket. Qualification tickets may include, for example, airline tickets and admission tickets.
[0027] (3) “Presented information” means a code readable by a reader or data stored in said code. The code may be visible or invisible. Visible codes can be read by a designated reader when printed on paper or displayed on a screen. Visible codes may be in image format or string format. Examples of image format codes are two-dimensional codes (QR code®) and one-dimensional codes (barcodes). Image format codes store corresponding strings. Invisible codes are recorded on a recording medium and can be read by a designated reader. Examples of recording mediums are magnetic stripes attached to portable items such as magnetic cards, and IC chips embedded in portable items such as IC cards, portable devices, and wearable devices. An example of an IC chip is FeliCa. It is a (registered trademark) chip. The information presented may also be a pattern of the user's biometric information that can be read by a reader. Examples of biometric information include fingerprints, palm prints, retinal capillaries, iris, facial features, palm veins, and finger veins.
[0028] (4) "Issuance status" refers to the situation that can be determined from the history of the issuance of queue tickets. The information that can be determined from the history is, for example, the number of times a queue ticket has been issued to a particular user in the past, and the date when a queue ticket was last issued to a particular user. When queue tickets are issued based on the issuance status, the order in which the issuance request (i.e., the presentation of the information to be presented) was received often does not match the order in which the queue information indicates the guidance.
[0029] (5) “Service location” refers to the location where the service is provided to an individual user. In other words, it refers to the location where an individual user receives the service. The timing of determining each user’s service location is when a queue ticket is issued to each user or before. The timing of determination before the issuance of a queue ticket is, for example, when the reservation for receiving the service is confirmed. When the service is provided simultaneously to multiple users within the designated space, the service location within that designated space refers to the subspace allocated to each user. The subspace allocated to a user is, for example, the space available at a seat identified by a seat number, or the area identified by an area number. A seat identified by a seat number may be included in a specific area along with several other nearby seats. When queue tickets are issued based on the service location, the order in which the request for issuance (i.e., the presentation of the information) is received often does not match the order in which the information indicates the guidance.
[0030] (6) "Guidance priority" refers to the degree of priority given to a user when guiding them to the provision of a service or to a place where a service is provided. The degree of priority may be defined by the magnitude of a number, by the order of time, or by the level of a stage. Priority defined by the level of a stage may be represented by one of several strings with a predetermined order. Users with higher guidance priority will be guided earlier. Relatively increasing the guidance priority when a certain condition (the first condition) is met means executing at least one of the following: a process that increases the guidance priority when the first condition is met, and a process that decreases the guidance priority when the first condition is not met. Relatively decreasing the guidance priority when another condition (the second condition) is met means executing at least one of the following: a process that decreases the guidance priority when the second condition is met, and a process that increases the guidance priority when the second condition is not met.
[0031] (7) Not exceeding the first value (i.e., being less than or equal to the first value) means, for example, not reaching the first value. The first value is, for example, the first threshold. The first threshold is an appropriate natural number. If the upper limit on the number of times a service can be provided to one user is set to n (n: an appropriate natural number), the first threshold should be set to n. If there is no upper limit on the number of times a service can be provided to one user, the first threshold can be set arbitrarily.
[0032] (8) Not falling below the second value (i.e., being greater than or equal to the second value) means, for example, reaching the second value. The second value is, for example, the second threshold. The second threshold is a suitable natural number. If the upper limit on the number of times a service can be provided to one user is set to m times (m: a suitable natural number), then the second threshold should be set to m.
[0033] (9) “Entry point” means the location of an entrance or exit used when entering or leaving the designated space which is isolated from the outside or at least partially partitioned off. If there are multiple entrances or exits, the entry point refers to the location of any one of them. Any one of the entrances or exits is selected, for example, so as to be the shortest route to the service location.
[0034] (10) "Entry point" refers to the location of the entrance or exit used when entering or leaving the area including the service area. If there are multiple entrances or exits, the entry point refers to the location of any one of them. The one entrance or exit is selected, for example, so as to be the shortest route from the entry point or to the service area.
[0035] (11) "Guidance priority" refers to the priority given to a service location when guiding a user to that location. The level of priority may be defined by the magnitude of a number, by the order of time, or by the level of stages. Priority defined by the level of stages can be expressed by one of several strings with a predetermined order. It is preferable to change the guidance priority according to the readiness of the guidance. For example, the guidance priority may be changed to a lower level when guidance is not yet ready. Users who receive service at a service location with a lower guidance priority will be guided later in the queue. [Examples]
[0036] [2. Example 1] [2-1. Overview] Example 1 relates to a service (hereinafter referred to as "the pre-service of Example 1") that issues numbered tickets (queue tickets) to guide users to a service (hereinafter referred to as "the service of Example 1") that may be provided to a single user multiple times within a predetermined period. The service of Example 1 is, for example, a service that allows users to use amusement machines at a specific attraction within an amusement park during the park's opening hours. A service that allows users to try out exhibits at a specific booth within an exhibition hall during the exhibition period may also fall under the category of the service of Example 1.
[0037] [2-2. Features] In the pre-service of Example 1, users requesting a numbered ticket are asked to present a two-dimensional code (presentation information), and a numbered ticket is issued to that user that reflects the guidance priority based on the ticketing information (inquiry information) stored in association with the two-dimensional code. In particular, in order to guide users appropriately according to the situation, the guidance priority for a user is determined by using the ticketing status (issuance status) of numbered tickets for users requesting tickets as one of the judgment conditions. In the following explanation, the guidance priority is changed according to the number of numbered tickets issued (issuance count).
[0038] [2-3. System Configuration of Example 1] [2-3-1. Network Configuration] (1) Overview Figure 1 illustrates the network configuration of the system in Example 1. The system in Example 1 provides the pre-services of Example 1 to the user.
[0039] As illustrated in Figure 1, the system of Embodiment 1 includes a management server 10a that manages the pre-service of Embodiment 1, a user DB (Data Base) 20a that manages data related to the pre-service of Embodiment 1, a ticket issuing device 30a installed near the location where the service of Embodiment 1 is provided, an input / output device 40 connected to the ticket issuing device 30a by wire or wireless, and multiple user terminals 50 used by multiple users. The ticket issuing device 30a and the input / output device 40 may each be singular or multiple. Note that in Figure 1, only one of each is shown for the ticket issuing device 30a, the input / output device 40, and the user terminal 50 for the sake of simplicity in the drawing.
[0040] The management server 10a and the ticket issuing device 30a can exchange data via the communication network 60. The management server 10a and the user terminal 50 can exchange data via the communication network 60. The management server 10a can access data managed in the user DB 20a. The ticket issuing device 30a and the input / output device 40 can exchange data.
[0041] The communication network 60 may include at least one of the existing networks such as the Internet, mobile phone networks, wireless WANs (Wireless Wide Area Networks), wireless LANs (Wireless Local Area Networks), and Ethernet (registered trademark).
[0042] (2) Management Server The management server 10a is a server device (computer) on which the web server program is installed. The management server 10a retrieves the necessary data from the user DB 20a in response to a request and provides it to the requester (response). The management server 10a also registers the necessary data in the user DB 20a in response to a request.
[0043] (3) User DB User DB20a is included in or connected to a server device (computer) on which the DB server program is installed, and together with the DB server running on that server device, constitutes a DBMS (Data Base Management System). The DB server provides the necessary data to the requester in response to a request. The DB server also registers the necessary data in response to a request. User DB20a functions as a storage device that stores data related to the pre-service in Example 1. Note that a server system may be configured by linking multiple server devices, distributing the functions of the DB server or balancing the load on the DB server.
[0044] (4) Ticket issuing device The ticket issuing device 30a is a client device on which a predetermined program is installed. It is a computer. A dedicated processing unit or a general-purpose processing unit (for example, a PC (personal computer)) can be used as a client device. The ticket issuing device 30a queries the management server 10a for the necessary data based on the two-dimensional code data received from the input / output device 40, and causes the input / output device 40 to issue a queue ticket according to the query result.
[0045] (5) Input / Output Devices The input / output device 40 has a function to read two-dimensional codes (reader) and a function to print numbered tickets. It has a printer. The reader has the function of taking a picture of the two-dimensional code, converting it into image data, and analyzing the image data to recognize the string data corresponding to the two-dimensional code. The input / output device 40 passes the data of the read two-dimensional code to the ticket issuing device 30a.
[0046] (6) User terminal The user terminal 50 is a user device (computer) on which a predetermined program is installed. In the pre-service of Example 1, the user device is a general-purpose portable device on which a program can be installed (e.g., a mobile phone, smartphone, or tablet). (Tablet) terminals, tablet PCs (personal computers), wearable devices, etc., or general-purpose processing devices (for example, PCs (personal computers)) can be used.
[0047] [2-3-2. Electrical Configuration] (1) Electrical configuration of server and client devices Figure 2 illustrates the electrical configuration of a server and client device. The server and client device illustrated in Figure 2 includes a control processing unit 211 including a CPU (Central Processing Unit) and ROM (Read Only Memory), a main memory 212 including RAM (Random Access Memory), an auxiliary storage device 213 including an HDD (Hard Disk Drive), an input device 214 including a mouse, keyboard, and touch panel display, an output device 215 including a display and speaker, and a communication control device 216 including a network interface card. Note that devices such as an MPU (Micro-Processing Unit) or DSP (Digital Signal Processor) may be used instead of a CPU.
[0048] The main memory 212, auxiliary memory 213, input device 214, output device 215, and communication control device 216 are each connected to the control processing unit 211 via a bus line. The control processing unit 211 (1) reads the program stored in the auxiliary memory 213 into the main memory 212, (2) acquires data from at least one of the input device 214, the auxiliary memory 213, and the communication control device 216 according to the program's instructions, (3) performs calculations and processing on the acquired data according to the procedure specified in the program, and (4) provides the calculated and processed data to at least one of the auxiliary memory 213, the output device 215, and the communication control device 216.
[0049] (2) Electrical configuration of user equipment Figure 3 illustrates the electrical configuration of a user device. The user device illustrated in Figure 3 includes at least a DSP 311 which constitutes the control processing unit, a RAM 312 which constitutes the main memory unit, a ROM 313 and an EEPROM (Electrically Erasable Programmable Read-Only Memory) 314 which constitute the auxiliary memory unit, a touch panel display 315 which constitutes the input unit and display unit, a speaker 316 which constitutes the audio output unit, and a NIC (Network Interface Controller) 317 and a wireless LAN (Local Area Network) chip 318 which constitute the communication control unit.
[0050] RAM312, ROM313, EEPROM314, touch panel display315, speaker316, NIC317, and wireless LAN chip318 are each connected to DSP311 via a bus line. DSP311 (1) reads a program stored in ROM313 or EEPROM314 onto RAM312, (2) acquires data from at least one of the touch panel display315, EEPROM314, NIC317, and wireless LAN chip318 according to the program's instructions, (3) performs calculations and processing on the acquired data according to the procedure specified in the program, and (4) provides the calculated and processed data to at least one of the EEPROM314, touch panel display315, speaker316, NIC317, and wireless LAN chip318.
[0051] [2-3-3. Functional Configuration] Figure 4 illustrates the functional configuration of the system in Embodiment 1. As illustrated in Figure 4, the management server 10a comprises an issuing unit 411a and a providing unit 413a. The user DB 20a comprises a storage unit 412a. The ticket issuing device 30a comprises a identification unit 423a, a determination unit 424a and an instruction unit 425a. The input / output device 40 comprises a recognition unit 421 and a ticketing unit 422.
[0052] The issuing unit 411a and the providing unit 413a are configured to include a control processing unit 211 and a communication control device 216 of the server device which functions as a management server 10a. The storage unit 412a is configured to include a user DB 20a. The identification unit 423a and the instruction unit 425a are configured to include a control processing unit 211 and a communication control device 216 of the client device which functions as a ticket issuing device 30a. The determination unit 424a is configured to include a control processing unit 211 of the client device which functions as a ticket issuing device 30a. The recognition unit 421 is configured to include a reader of the input / output device 40. The ticketing unit 422 is configured to include a printer of the input / output device 40.
[0053] The functions of the management server 10a and the ticket issuing device 30a are realized by installing an OS (Operating System) for the server device or client device, and programs that run on that OS, on the server device or client device, respectively. The programs to be installed on the server device or client device may be distributed in a non-temporarily recorded state on a recording medium such as a CD (Compact Disc), DVD (Digital Versatile Disk), MO disk (Magneto-Optical disk), or flash memory, and read from the recording medium to the server device or client device, or they may be supplied to the server device or client device by superimposing them on a carrier wave via the communication network 60 or other communication network.
[0054] The functions of the user terminal 50 are realized by installing an operating system (OS) for the user device and a web browser program that runs on that OS on the user device. The operating system for the user device is generally pre-installed on the user device from the time of shipment. Other programs to be installed on the user device are generally supplied to the user device via the communication network 60, superimposed on the carrier wave. These other programs to be installed on the user device may also be distributed in a non-temporarily recorded state on recording media such as CDs (Compact Discs), DVDs (Digital Versatile Disks), MO disks (Magneto-Optical disks), or flash memory, and read from these recording media to the user device.
[0055] The issuing unit 411a generates a two-dimensional code embedded with predetermined identification data in response to a request from the user terminal 50 and provides it to the user terminal 50. In the pre-service of Embodiment 1, a two-dimensional code is generated that stores identification data that can identify the user of the service of Embodiment 1. The stored identification data is, for example, a fixed-length alphanumeric string obtained by converting a unique user ID for the user using a predetermined hash function. Note that a simple numerical value may be embedded in the two-dimensional code. The identification data embedded in the two-dimensional code may also be an appropriate numerical value that corresponds one-to-one with the user.
[0056] The memory unit 412a stores ticketing information. Ticketing information is information that manages the ticketing status for each identification data. As illustrated in Figure 5, the ticketing information associates at least the "number of tickets issued" and the "latest ticketing date and time" with the "identification data". The initial value of the "number of tickets issued" is 0. The initial value of the "latest ticketing date and time" is null. The items in the ticketing information are updated each time a ticket is issued. Specifically, the "number of tickets issued" is incremented and the "latest ticketing date and time" is overwritten.
[0057] The provisioning unit 413a responds to inquiries from the ticket issuing device 30a and provides the ticketing information items stored in the storage unit 412a to the ticket issuing device 30a. In the pre-service of Embodiment 1, the number of tickets issued and the latest issuance date and time of the ticketing information corresponding to the identification data obtained from the ticket issuing device 30a are provided. After the ticketing information items are provided to the ticket issuing device 30a by the provisioning unit 413a, the ticketing information items (number of tickets issued and latest issuance date and time) are updated.
[0058] The identification unit 423a obtains from the management server 10a the ticketing information items (inquiry information) corresponding to the identification data stored in the two-dimensional code read by the recognition unit 421 of the input / output device 40. Then, using the inquiry information obtained from the management server 10a, the identification unit 423a identifies the ticketing status, including the number of tickets issued to the user who presented the two-dimensional code. Note that if a predetermined time (for example, 2 hours) has passed since the most recent ticketing date, the number of tickets issued may be set to 0.
[0059] The determination unit 424a determines the priority of guidance for users who present a two-dimensional code, using the ticketing status identified by the identification unit 423a as one of the judgment conditions. In the pre-service of Embodiment 1, the priority when the number of tickets issued is less than or equal to a predetermined value (first value) is set higher than the priority when the number of tickets issued is greater than the predetermined value. The predetermined threshold is, for example, 1, 2, etc.
[0060] The instruction unit 425a instructs the ticket issuing unit 422 of the input output device 40 to issue a numbered ticket containing queueing information that reflects the guidance priority determined by the decision unit 424a.
[0061] [2-4. Procedure for information processing using the system of Example 1] [2-4-1. Procedure for issuing a QR code] Figure 6 illustrates the procedure for issuing a two-dimensional code using the system of Example 1. Here, a two-dimensional code is issued that stores identification data that can identify the user of the service of Example 1. In step S605, the user terminal 50 receives an instruction from the user to issue a two-dimensional code. The instruction to issue a two-dimensional code is made, for example, by tapping the area of the button that displays "Issue Two-Dimensional Code" on the browser screen of the user terminal 50. In step S610, the user terminal 50 instructs the management server 10a to issue a two-dimensional code.
[0062] In step S615, the management server 10a (issuing unit 411a) issues a two-dimensional code. Here, a two-dimensional code is generated that stores identification data that can identify the user of the service in Example 1. In step S620, the management server 10a (issuing unit 411a) sends the two-dimensional code generated in step S615 to the user terminal 50. Specifically, data for displaying a web page containing the generated two-dimensional code (still image) is sent. In step S625, the user terminal 50 displays the two-dimensional code received from the management server 10a on its screen. Specifically, a web page containing the two-dimensional code is displayed on the screen.
[0063] [2-4-2. Procedure for issuing numbered tickets] Figure 7 illustrates the procedure for issuing queue tickets using the system of Embodiment 1. In step S705, the input / output device 40 (recognition unit 421) reads the two-dimensional code presented by the user requesting a queue ticket and recognizes the identification data stored in the two-dimensional code. The object to be read may be the two-dimensional code displayed on the user terminal 50 according to the procedure illustrated in Figure 6, or it may be the displayed two-dimensional code printed on paper. In step S710, the input / output device 40 (recognition unit 421) transmits the identification data recognized in step S705 to the ticket issuing device 30a.
[0064] In step S715a, the ticket issuing device 30a (specification unit 423a) obtains inquiry information (items of ticketing information) corresponding to the identification data received in step S710 from the management server 10a. The management server 10a (providing unit 413a) reads the ticketing information corresponding to the identification data from the user DB 20a (storage unit 412a) and provides those items to the ticket issuing device 30a.
[0065] In step S720a, the ticket issuing device 30a (identification unit 423a) uses the inquiry information received in step S715a to identify the ticket issuance status for the user who presented the two-dimensional code. Here, the ticket issuance status, including the number of tickets issued, is identified. In step S725a, the ticket issuing device 30a (determination unit 424a) uses the ticket issuance status identified in step S720a as one of the judgment conditions to determine the guidance priority. Here, the guidance priority when the number of tickets issued is less than or equal to a predetermined value (first value) is set higher than the guidance priority when the number of tickets issued is greater than the predetermined value.
[0066] In step S730a, the ticket issuing device 30a (instruction unit 425a) instructs the input / output device 40 to issue a numbered ticket containing queueing information that reflects the guidance priority determined in step S725a. In step S735, the input / output device 40 (issuance unit 422) issues a numbered ticket based on instructions from the management server 10a.
[0067] [2-5. Variation 1] [2-5-1. Variation 1-1 (Variation regarding the method for determining guidance priority)] The decision unit 424a may determine the guidance priority for users who present a two-dimensional code, such that the guidance priority decreases as the number of numbered tickets issued to that user increases. This allows users who have been issued fewer numbered tickets to be given priority guidance.
[0068] [2-5-2. Modification 1-2 (Modification regarding the method for determining guidance priority)] The decision unit 424a may choose not to determine the priority of a user who presents a two-dimensional code if the number of numbered tickets issued to that user is high enough to meet predetermined conditions. This makes it possible to avoid guiding users who have been issued numbered tickets a large number of times.
[0069] [2-5-3. Variation 1-3 (Variation regarding the method for determining the number of tickets issued)] The storage unit 412a may store a ticketing history that associates at least the "ticketing date" with the "identification data" instead of the ticketing information. In this case, the identification unit 423a obtains all ticketing history (inquiry information) corresponding to the identification data stored in the two-dimensional code read by the recognition unit 421 of the input / output device 40 from the management server 10a. Then, using the inquiry information obtained from the management server 10a, the identification unit 423a counts the ticketing history to identify the ticketing status, including the number of numbered tickets issued to the user who presented the two-dimensional code. Note that if a predetermined time (for example, 2 hours) has passed since the time included in the latest ticketing history (latest ticketing date), the number of tickets issued may be set to 0.
[0070] [2-5-4. Variation 1-4 (Variations of the presented information)] In the pre-service of Example 1, users requesting a numbered ticket may be asked to present biometric information (presented information), and a numbered ticket reflecting the guidance priority corresponding to the ticketing information (inquiry information) stored in association with the pattern of the biometric information may be issued to the user. In this case, it is not necessary to issue a two-dimensional code in advance. The biometric information may be, for example, the user's facial features or fingerprints. This biometric information is read by a designated reader when the user holds the corresponding part of their body over the reader.
[0071] [3. Example 2] [3-1. Overview] Example 2 relates to a service (hereinafter referred to as "the pre-service of Example 2") that issues numbered tickets (queue tickets) guiding users to enter a venue (a designated space) that is isolated from the outside world, for a service (hereinafter referred to as "the service of Example 2") that is simultaneously provided to multiple users seated in designated seats (provided locations) inside the venue (a designated space). The service of Example 2 is, for example, a service that allows multiple users seated in designated seats inside a theater to watch a play. A service that transports multiple users seated in designated seats inside a means of transport such as an airplane or bus to their destination may also fall under the category of the service of Example 2.
[0072] Figure 8 is a floor plan of the venue where the service of Example 2 is provided. Inside the venue 800 shown in Figure 8, there are two entrances 811 and 812, a stage 820, and a seating area 830. The seating area consists of 12 rows from front to back, with 16 seats per row, for a total of 192 seats. Each seat is identified by a seat number that includes the row name and number. For example, the seat number for seat 831 is "A-1". Each row is divided into two sections (areas), left and right, and each section contains 8 seats arranged in a single row. There is a gap between each section and the section in front of and behind it that is wide enough for a person to pass through. There are aisles on both sides of each section.
[0073] Figure 9 is an enlarged view of the area surrounding section 832 in Figure 8. Section 832 contains eight seats numbered 1 through 8. These eight seats are arranged in a single row with almost no gaps between them, making it difficult for people to pass between them. Therefore, to enter the interior of section 832 from outside, it is necessary to take the route indicated by arrow 834 through entrance 833 from the left or right aisle, or the route indicated by arrow 836 through entrance 835.
[0074] [3-2. Features] In the pre-service of Example 2, users requesting a numbered ticket are asked to present a two-dimensional code (presentation information), and a numbered ticket is issued to the user that reflects the guidance priority based on the seat information (inquiry information) stored in association with the two-dimensional code. In particular, in order to guide users smoothly according to their location, the guidance priority of the user is determined by using information on the location of the designated seat (service location) where the service will be provided to the user requesting a numbered ticket as one of the judgment conditions. In the following explanation, the guidance priority is changed according to the positional relationship (service location information) between the location of the designated seat (service location) and the entrance / exit (entry location) and entry point (entry location).
[0075] [3-3. System Configuration of Example 2] [3-3-1. Network Configuration] The network configuration of the system in Example 2 is the same as the network configuration of the system in Example 1 illustrated in Figure 1. The system in Example 2 provides the pre-services of Example 2.
[0076] [3-3-2. Electrical Configuration] The electrical configuration of the server and client devices in Example 2 is the same as the electrical configuration of the server and client devices illustrated in Figure 2. The electrical configuration of the user device in Example 2 is the same as the electrical configuration of the user device illustrated in Figure 3.
[0077] [3-3-3. Functional Configuration] Figure 10 illustrates the functional configuration of the system in Embodiment 2. As illustrated in Figure 10, the management server 10b comprises an issuing unit 411b and a providing unit 413b. The user DB 20b comprises a storage unit 412b. The ticket issuing device 30b comprises an identification unit 423b, a determination unit 424b, and an instruction unit 425b. The input / output device 40 comprises a recognition unit 421 and a ticketing unit 422. Functions similar to those in Embodiment 1 are denoted by the same reference numerals as in Figure 4.
[0078] The issuing unit 411b and the providing unit 413b are configured to include a control processing unit 211 and a communication control device 216 of the server device which functions as a management server 10b. The storage unit 412b is configured to include a user DB 20b. The identification unit 423b and the instruction unit 425b are configured to include a control processing unit 211 and a communication control device 216 of the client device which functions as a ticket issuing device 30b. The determination unit 424b is configured to include a control processing unit 211 of the client device which functions as a ticket issuing device 30b. The recognition unit 421 is configured to include a reader of the input / output device 40. The ticketing unit 422 is configured to include a printer of the input / output device 40.
[0079] The functions of the management server 10b and the ticket issuing device 30b are realized by installing an operating system (OS) for the server device or client device, and programs that run on that OS, on the server device or client device, respectively. The functions of the user terminal 50 are realized by installing an operating system (OS) for the user device and a web browser program that runs on that OS, on the user device, respectively.
[0080] The issuing unit 411b generates a two-dimensional code embedded with predetermined identification data in response to a request from the user terminal 50 and provides it to the user terminal 50. In the pre-service of Embodiment 2, a two-dimensional code is generated that stores identification data capable of identifying the seat number of the designated seat for the service of Embodiment 2 or a unique reservation ID for the reservation of said designated seat. The stored identification data is, for example, a fixed-length alphanumeric string obtained by converting the seat number or reservation ID with a predetermined hash function. Note that a simple numerical value may be embedded in the two-dimensional code. Furthermore, the identification data embedded in the two-dimensional code may be an appropriate numerical value that corresponds one-to-one with the user.
[0081] The memory unit 412b stores seat information. The seat information is information that manages the positional relationship of the designated seat location with respect to the reference position for each identification data. As illustrated in Figure 11, the seat information associates at least the "identification data" with "first length information" that shows the positional relationship between the designated seat and the entrance / exit, and "second length information" that shows the positional relationship between the designated seat and the entrance / exit. The "first length information" is a numerical value corresponding to the length of the shortest path from the nearest entrance / exit to the nearest entrance / exit of the designated seat. The "second length information" is a numerical value corresponding to the length of the shortest path from the designated seat to the nearest entrance / exit. Note that the "second length information" may also be a numerical value corresponding to the straight-line distance from the designated seat to the nearest entrance / exit.
[0082] The provisioning unit 413b responds to inquiries from the ticket issuing device 30b and provides the ticket issuing device 30b with items of seat information stored in the storage unit 412b. In the pre-service of Embodiment 2, first length information and second length information of seat information corresponding to the identification data obtained from the ticket issuing device 30b are provided.
[0083] The identification unit 423b obtains seat information items (inquiry information) corresponding to the identification data stored in the two-dimensional code read by the recognition unit 421 of the input / output device 40 from the management server 10b. Then, using the inquiry information obtained from the management server 10b, the identification unit 423b identifies the positional relationship between the location of the designated seat where the service will be provided to the user who presented the two-dimensional code and the locations of the entrance and exit.
[0084] The determination unit 424b determines the guidance priority of a user who presents a two-dimensional code, using the positional relationship identified by the identification unit 423b as one of the judgment conditions. In the pre-service of Embodiment 2, the guidance priority is determined according to the length of the shortest path from the nearest entrance to the nearest exit of the designated seat (length indicated by the first length information) and the length of the shortest path from the designated seat to the nearest entrance (length indicated by the second length information). Specifically, the longer the length indicated by the first length information and the longer the length indicated by the second length information, the higher the guidance priority is determined.
[0085] The instruction unit 425b instructs the ticket issuing unit 422 of the input output device 40 to issue a numbered ticket containing queueing information that reflects the guidance priority determined by the decision unit 424b. In the pre-service of Embodiment 2, if there are multiple entrances and exits, it is preferable to configure the system so that information that allows the user to identify which entrance or exit to use upon entry is displayed on the numbered ticket along with the queueing information.
[0086] [3-4. Procedure for information processing using the system of Example 2] [3-4-1. Procedure for issuing a QR code] The procedure for issuing a two-dimensional code using the system in Example 2 is the same as the procedure for issuing a two-dimensional code using the system in Example 1, as illustrated in Figure 6. In this case, a two-dimensional code is issued that stores identification data that can identify the seat number of the designated seat for the service in Example 2 or a unique reservation ID for the reservation of said designated seat.
[0087] [3-4-2. Procedure for issuing numbered tickets] Figure 12 illustrates the procedure for issuing queue tickets using the system of Embodiment 2. In step S705, the input / output device 40 (recognition unit 421) reads the two-dimensional code presented by the user requesting a queue ticket and recognizes the identification data stored in the two-dimensional code. The object to be read may be a two-dimensional code displayed on the user terminal 50 using the same procedure as illustrated in Figure 6, or it may be the displayed two-dimensional code printed on paper. In step S710, the input / output device 40 (recognition unit 421) transmits the identification data recognized in step S705 to the ticket issuing device 30b.
[0088] In step S715b, the ticket issuing device 30b (identification unit 423b) obtains inquiry information (seat information items) corresponding to the identification data received in step S710 from the management server 10b. The management server 10b (providing unit 413b) reads the inquiry information corresponding to the identification data from the user DB 20b (storage unit 412b) and provides it to the ticket issuing device 30b.
[0089] In step S720b, the ticket issuing device 30b (identification unit 423b) uses the inquiry information received in step S715b to identify the location of the designated seat where the service of Embodiment 2 will be provided to the user who presented the two-dimensional code. Here, the length of the shortest path from the nearest entrance to the nearest exit of the designated seat (length indicated by the first length information) and the length of the shortest path from the designated seat to the nearest entrance (length indicated by the second length information) are identified. In step S725b, the ticket issuing device 30b (determination unit 424b) determines the guidance priority based on the information identified in step S720b. Here, the longer the length of the shortest path from the nearest entrance to the nearest exit of the designated seat, and the longer the length of the shortest path from the designated seat to the nearest entrance, the higher the guidance priority.
[0090] In step S730b, the ticket issuing device 30b (instruction unit 425b) instructs the input / output device 40 to issue a numbered ticket containing queueing information that reflects the guidance priority determined in step S725b. The ticket issuance instruction may also include information that identifies the entrance / exit. In step S735, the input / output device 40 (ticket issuing unit 422) issues a numbered ticket based on instructions from the management server 10b.
[0091] [3-5. Variation 2] [3-5-1. Modification 2-1 (Modification regarding the method for determining guidance priority)] The determination unit 424b may determine the guidance priority for a user who presents a two-dimensional code according to the length of the shortest path from the nearest entrance to the designated seat to the nearest exit (the length indicated by the first length information). This allows for smooth guidance of the user according to the positional relationship between the exit and the designated seat. For example, the determination unit 424b may determine the guidance priority for a user who presents a two-dimensional code such that the longer the length indicated by the first length information, the higher the guidance priority.
[0092] [3-5-2. Modification 2-2 (Modification concerning the method for determining guidance priority)] The determination unit 424b may determine the guidance priority for a user who presents a two-dimensional code according to the length of the shortest path from the designated seat to the nearest entrance (the length indicated by the second length information). This allows for smooth guidance of the user according to the positional relationship between the entrance and the designated seat. For example, the determination unit 424b may determine the guidance priority for a user who presents a two-dimensional code such that the longer the length indicated by the second length information, the higher the guidance priority.
[0093] [3-5-3. Modification 2-3 (Modification concerning the method for determining guidance priority)] The seat information stored in the memory unit 412b may also be information that manages the guidance priority of designated seats for each identification data. The guidance priority changes according to the preparation status of the guidance. For example, it is preferable that the guidance priority be lowered when information is entered indicating that guidance is not yet ready. The identification unit 423b may obtain the seat information item (inquiry information) corresponding to the identification data stored in the two-dimensional code read by the recognition unit 421 of the input / output device 40 from the management server 10b, and use the obtained inquiry information to determine the guidance priority (information of the service location) of the designated seat to which the service will be provided to the user who presented the two-dimensional code. The decision unit 424b may determine the guidance priority of the user who presented the two-dimensional code using the guidance priority determined by the identification unit 423b as one of the judgment conditions. For example, it is preferable that the guidance priority be lowered when guidance to the designated seat is not yet ready. This makes it possible to smoothly guide the user according to the guidance priority of the service location.
[0094] [3-5-4. Modification 2-4 (Modification of presented information)] In the pre-service of Example 2, users requesting a numbered ticket may be asked to present biometric information (presented information), and a numbered ticket reflecting the guidance priority corresponding to the seat information (inquiry information) stored in association with the pattern of the biometric information may be issued to the user. In this case, it is not necessary to issue a two-dimensional code in advance. The biometric information may be, for example, the user's facial features or fingerprints. This biometric information is read by a designated reader when the user holds the corresponding part of their body over the reader. [Explanation of Symbols]
[0095] 10a, 10b Management Server 20a, 20b User DB 30a, 30b Ticket issuing device (an example of a ticket information processing device) 40 Input / Output Devices 50 User Terminals 60 Communication Networks 411a, 411b Publishing Department 412a,412b Storage section 413a,413b Providing Department 421 Recognition part 422 Ticketing Department 423a,423b Specific part 424a,24b Decision section 425 Instruction section
Claims
1. A means for identifying the status of the issuance of a queue ticket to a user using information presented by the user requesting a queue ticket for a service to be provided within a predetermined period, A determination means for determining the priority of guidance for the user, which is reflected in the queue ticket for the user, based on the issuance status identified by the identification means, A ticket information processing device equipped with the following features.
2. The identifying means identifies the status of the issuance of the queue ticket to the user for the service that may be provided to the user multiple times within the predetermined period. The determination means determines the guidance priority such that the guidance priority changes according to the issuance status, which includes at least the number of times the queue ticket has been issued to the user in the past. The ticket information processing device according to claim 1.
3. The determination means sets the guidance priority when the number of issuances is less than or equal to a first value to be higher than the guidance priority when the number of issuances is greater than the first value. The ticket information processing device according to claim 2.
4. The determination means determines the guidance priority such that the guidance priority decreases as the number of issuances increases. The ticket information processing device according to claim 2 or claim 3.
5. The determination means does not determine the guidance priority if the number of times the queue ticket has been issued to the user is equal to or greater than the second value. The system further includes an instruction means for instructing the issuing means to issue the queue ticket reflecting the guidance priority, only when the guidance priority has been determined by the determination means. The ticket information processing device according to claim 1.
6. A function to identify the status of the issuance of a queue ticket to a user using information provided by the user requesting the queue ticket for a service to be provided within a specified period, A determination function that determines the priority of guidance for the user, which is reflected in the queue ticket for the user, based on the issuance status identified by the specific function, A control program that enables the computer of an information processing device to implement this.