JP2019125171A - Ticketing system - Google Patents

Abstract

To provide a ticketing system for offering a flexible ticketing service in terms of distribution and robustness.SOLUTION: A ticketing system comprises an information management server and one or more terminal devices. The information management server includes a management unit that manages one or more pieces of one information page associated with one user code, and manages one or more service identifiers that can be associated with the user code. The terminal device includes an input unit that reads the user code from a ticket in which the user code is recorded, and a transmission unit that transmits the read user code to the information management server. The information management server transmits to the terminal device the service associated with the service identifier managed by the terminal device according to a request from the terminal device, to be presented, and associates the service identifier associated with the presented service selected by an instruction from the terminal device with the user code.SELECTED DRAWING: Figure 1

Description

  The present invention relates generally to a system and the like for electronically issuing tickets and the like, and more particularly to a ticketing system and the like capable of managing payment for payment.

  Heretofore, various electronic payment methods, card systems, and the like for managing change (changes) have been developed.

  For example, a method and system have been proposed to prevent coins from being included in change (Patent Document 1).

  That is, in the patent document 1, when the price is larger than the amount of deposit change of the payer being held and managed, a provisional bill amount calculation step of subtracting the deposit amount of change from the price to calculate a provisional bill amount; The billed amount calculation step of rounding up the provisional billed amount to the minimum bill denomination unit to calculate the billed amount charged to the payer, and the deposit change amount calculation step of computing the deposit change amount by subtracting the billed amount from the billed amount. The deposit change amount calculated by the deposit change amount calculating step is stored as a new deposit change amount for the payer, and the change to the payer does not include coins in the change to the payer. A change management method is disclosed which comprises determining the billed amount.

  In addition, it is possible to transfer information on customer goods and services such as change and savings amounts at the time of purchase to the change and savings management server, and create a database so that information can be obtained for grasping the customer's purchase tendency. A change change savings service system has also been proposed (Patent Document 2).

  That is, Patent Document 2 is a system in which the sales side includes a sales processing device, a card reader connected thereto, and a management server to which the sales processing device is communicatively connected, and the customer side has a member card issued by the sales side. The card reader has means for reading information of a membership card possessed by a customer, and the sales processing device receives the read information and determines whether the customer to be processed is a change savings member. A means of calculating the total amount of goods and services purchased by the customer and subtracting this amount from the deposit amount and calculating the amount of change, if the customer is a change savings member, if the amount of change is a positive amount If the amount is a negative amount, the absolute amount is taken as the withdrawal amount, and it has means for transmitting it to the management server together with the member identification, and the management server is for identification of each member, password, individual Information, holds exact change account information as a database, the corresponding exact change savings service system characterized in that it comprises means for updating the change due account balance of the member are disclosed in and out amounts received from the sales processing device.

  Moreover, even if it is a sales system that requires a clearing process after offering a product using a non-contact type Prika, the clearing process can be performed on the offering side without losing the convenience of the customer's Prika. A sales system or the like using a contactless prepaid card has also been proposed (Patent Document 3).

  That is, Patent Document 3 shows a change processing method in a sales system using a contactless prepaid card in a sales form of a product or the like in which the amount and the amount of goods for sale are not determined until the end of the sales act. The card information data including at least an identification ID for identifying the noncontact prepaid card recorded in the contact prepaid card as the other and a commodity purchase available balance are read by the noncontact contactor processing machine and designated by the customer by the POS device. The amount equivalent to the planned purchase is deducted from the commodity purchaseable balance of the contactless prepaid card, and the commodity vending machine controls the supply of goods etc. up to the planned purchase amount debited by the POS device, and the POS device Furthermore, with the end of the supply control of the goods etc., the purchase scheduled equivalent amount and the actual supply amount The difference amount is calculated, and the change amount is added to the balance of the prepaid card at the time of reading the card information data of the noncontact prepaid card again by the noncontact preca processor, and the payment is made by adding the change amount to the balance of the prepaid card. A change handling method in a vending system using a contactless prepaid card is disclosed.

  Also, when shopping with cash and charging change to electronic money, if the charge upper limit amount exceeds a certain amount, the change amount is not charged, for example, an electronic money charge shop terminal etc. that returns a bill as a change It is proposed (patent document 4).

  That is, in Patent Document 4, the amount information stored in the IC card is read and written, and when a change occurs for the cash payment amount of the user, the monetary value equivalent to the change amount is converted to the amount information As an IC card reader / writer for writing to the IC card, and storage means for storing the minimum unit for returning change in cash as the minimum unit for cash change, and further, a monetary value equivalent to the change amount as the amount information When the money amount information of the IC card exceeds a predetermined amount by writing in the IC card, the cash change minimum unit stored in the storage unit and the cash change unit are stored without writing the monetary value into the IC card. The electronic money management system further comprises a control unit that controls the IC card reader / writer to subtract the difference between the change amount and the amount information stored in the IC card. Charge the shop terminal is disclosed.

JP 2002-236975 A Unexamined-Japanese-Patent No. 2004-234091 JP, 2009-193558, A JP, 2009-237665, A

  However, in the conventional system and method, when the user uses the service, the user terminal is always required, and for old people and children who do not feel easy to use, the threshold is often high.

  In particular, in addition to electronic processing such as electronic settlement and fishing management in the conventional system and method, expectations for services such as easier ticketing are increasing.

  Therefore, a ticket issuing system according to an embodiment of the present invention is a ticket issuing system including an information management server and one or more terminal devices, and the information management server is one piece of information associated with one user code. The terminal includes a management unit that manages one or more pages and manages one or more service identifiers that can be associated with the user code, and the terminal device is an input that reads the user code from a ticket in which the user code is recorded. Unit, and a transmission unit for transmitting the read user code to the information management server, the information management server, in response to a request from the terminal device, the service associated with the service identifier managed by itself. It is sent to a terminal device to be presented and associated with the presented service selected by an instruction from the terminal device The service identifier that is characterized by attaching the cord to the user code.

  Further, the management unit manages the price of the service, and the terminal device presents a plurality of discrete payment amounts, and the price of the service is instructed by the terminal device according to an instruction from the terminal device. When the payment amount is higher than the price of the service and one of the plurality of discrete payment amounts is selected, the information management server is the amount of fishing obtained by subtracting the price of the service from the one payment amount. The management unit is characterized by associating a service identifier associated with the service selected according to an instruction from the terminal device and the amount of fishing with the user code.

  According to the ticketing system and the like according to the embodiment of the present invention, a person who is not accustomed to information equipment and the like can feel free to use the terminal without using the terminal at the time of using the service. The special effect of being able to provide a good ticketing service etc. is achieved.

It is an explanatory view explaining an example of the whole system configuration concerning one embodiment of the present invention. It is an explanatory view explaining a functional block of an information management server included in a system concerning one embodiment of the present invention. It is explanatory drawing explaining the external appearance structure and functional block of a tablet terminal as a typical terminal device contained in the system concerning one Embodiment of this invention. It is a flowchart explaining the operation flow of the system concerning one embodiment of the present invention. It is a flowchart explaining the operation flow of the system concerning one embodiment of the present invention. It is a flowchart explaining the operation flow of the system concerning one embodiment of the present invention. It is an explanatory view explaining an example of a screen of a terminal unit in a system concerning one embodiment of the present invention. It is an explanatory view explaining an example of a screen of a terminal unit in a system concerning one embodiment of the present invention. It is an explanatory view explaining an example of a screen of a terminal unit in a system concerning one embodiment of the present invention. It is an explanatory view explaining an example of a screen of a terminal unit in a system concerning one embodiment of the present invention. It is an explanatory view explaining an example of a screen of a terminal unit in a system concerning one embodiment of the present invention.

  A ticketing system according to an embodiment of the present invention will be described in detail with reference to the drawings.

  FIG. 1 shows an example of the overall configuration of a system according to an embodiment of the present invention. The ticket issuing system 10 includes an information management server (hereinafter, also simply referred to as a “server”) 101 and terminal devices 102 a to 102 d such as one or more tablet terminals as a typical basic configuration. Further, tickets 103a to 103f are included as an information input medium to the ticket issuing system. In one embodiment of the present invention, the tickets 103a-103f are paper media, but the present invention is not limited thereto. For example, a two-dimensional code 104 can be adopted as an information input format, and the recording medium (not shown) (such as pin badges and goods) printed or attached can be included. In addition to the tablet terminal, the terminal device also includes various information processing devices such as a personal computer (not shown), a mobile phone, a personal digital assistant (PDA) (hereinafter, these may be generically referred to as "user terminal"). be able to.

  In the embodiment of the present invention, the information management server 101 can also be accessed from any information terminal (PC, tablet terminal, mobile phone, mobile information terminal, etc.) not shown. One form of access in this case includes access to information pages (URL and the like) managed on the information management server 101 (details will be described later).

As shown in FIG. 1, these servers and terminal devices and information terminals are communicably connected to each other via a dedicated line or a public line such as the Internet 109. Note that the line may be wired or wireless, and in the case of wireless, it can be connected to the Internet 109 via a wireless router or a base station (not shown), and can communicate with the information management server 101 via the line. Can be connected to
Therefore, although in FIG. 1 the terminal devices 102a to 102d are expressed as if they are wired into the Internet 109, they may be wired into the Internet 109 by wireless via a wireless router or the like (not shown).

  Many user terminals such as tablet terminals at the time of filing of the present application have the same processing capability (such as communication processing speed and image processing capability) as a PC, and should be referred to as a small computer.

  The software or program necessary for the implementation of the present invention is usually installed or stored and stored in an HDD or an SSD or the like in a storage unit of a terminal device such as a server, a PC, or a portable information terminal. When the software or program is executed, it is read out as a whole or a part of the software module or program module on the memory in the storage unit as necessary, and is appropriately calculated and executed in the CPU.

  Note that the execution of calculations need not necessarily be performed by a central processing unit such as a CPU, and an auxiliary calculation device such as a digital signal processor (DSP) (not shown) may be used.

  In addition, the hardware block configuration of the information management server 101 can basically adopt a PC. Although the present invention is not limited to this, the information management server 101 processes a large-scale data by operating a plurality of PCs in parallel in improving the hardware specifications as needed. It can also take a configuration suitable for

  FIG. 2 shows a functional block diagram of the information management server in the ticket issuing system according to the embodiment of the present invention. Illustratively, the operation of the information management server is realized by the individual operations of hardware described below, and the coordinated operation of software and these hardware.

  In FIG. 2, the information management server 200 as the entire hardware block can be roughly divided into a CPU 201 for performing various comparison / calculation processing, a storage unit 202 such as a RAM, a ROM, a flash memory, a keyboard, a pointing device, etc. , An output unit 204 such as a display or a speaker, a control unit 205 for controlling various signals, and a communication (interface) unit 206 (wireless or wired), for measuring time and the like. It comprises a clock unit 207 and a power supply unit 208.

  These modules are connected as needed by communication buses and feeders (in FIG. 2, for convenience, the lines are collectively represented as connections 299 appropriately divided).

  Further, programs or software executed on the information management server 200 necessary for the implementation of the present invention are usually installed or stored in a hard disk, a solid state drive (SSD), a flash memory, etc. constituting the storage unit 202 At the time of execution of a program or software, it is read out as a whole or a part of a software module in a memory in the storage unit 202 as necessary, and operation is executed in the CPU 201.

  The execution of the operation does not necessarily have to be performed by the central processing unit such as the CPU 201, and an auxiliary operation device such as a digital signal processor (DSP) (not shown) can be used.

  FIG. 3 shows an appearance configuration (FIG. 6A) and a functional block (FIG. 3B) of a tablet terminal as a representative terminal device included in a system according to another embodiment of the present invention. In FIG. 3A, the tablet terminal (information processing apparatus) 30 includes a housing 301, a display 302, and hardware buttons 303 provided at the lower center of the housing 301. The display 302 is typically composed of a liquid crystal display (LCD) or the like, and can display various information such as characters and images. In addition, a menu button or a software keyboard can be displayed on the display 302, and this can be used as an instruction (command) to the tablet terminal 30 by touching it with a finger or a touch pen (not shown) or the like. Although the hardware button 303 is not an essential component in this respect, it is implemented as a button having a certain function for the convenience of the description of the present invention. Of course, it is also possible to substitute these hardware buttons 303 with menu buttons displayed on a part of the display 302.

  In addition, a multi-touch input panel is incorporated in the display 302, and touch input position coordinates on the touch input panel are transmitted to a processing system (such as a CPU) of the tablet terminal 30 via an input device interface (not shown). And processed. The multi-touch input panel is configured to be able to simultaneously sense a plurality of touch points on the panel. The detection (sensor) can be realized by various methods, and is not necessarily limited to the contact sensor. For example, it is also possible to extract an indicated point to the panel using an optical sensor. Furthermore, as the sensor, in addition to a contact sensor and an optical sensor, it is also possible to use a capacitive sensor that senses the touch of human skin.

  Further, although not shown in FIG. 3A, the tablet terminal 30 can also be provided with a microphone and a speaker. In this case, it is also possible to determine the voice of the user picked up from the microphone and use it as an input command. Furthermore, although not shown in FIG. 3A, a camera device such as a CMOS can be mounted on the back of the tablet terminal 30 or the like.

  The functional block diagram of the hardware which comprises the tablet terminal 30 shown to FIG. 3 (A) by FIG. 3 (B) is illustrated. The operation of the terminal 30 is realized by the individual operations of hardware described below, and the coordinated operation of these hardware and software.

  In FIG. 3B, the functional block 35 as the entire hardware block of the tablet terminal as the terminal device can be roughly divided into hardware buttons (not shown) in each device of FIG. 3A, and a multi-touch input panel An input unit 3501 (provided in the display 302 in FIG. 3A or the display unit 3504 in FIG. 3B) or a microphone not shown, a hard disk for storing programs, data, etc., and a RAM And / or a central processing unit 3503 comprising a storage unit 3502 comprising a ROM etc., a CPU for performing various numerical calculations and logical operations according to a program, a display unit 3504 comprising a display 302 etc., a chip Control unit 3505 for controlling the electrical system etc., and for accessing the Internet A communication interface unit 3506 including a lot and a port for performing optical communication, and a communication interface, an output unit 3507 such as a speaker and a vibration, and a clock unit or a clock unit 3508 for performing timekeeping and timer timing. And a sensor unit 3509 composed of an image sensor such as a CMOS, and a power supply unit 3510 for supplying power to each module in the apparatus. In (B), for the sake of convenience, the respective lines are collectively connected by appropriately divided connections 3511).

  The sensor unit 3509 may include a GPS sensor module for specifying the position of the tablet terminal. Further, a signal detected by an image sensor such as a CMOS constituting the sensor unit 3509 is processed as input information in the input unit 3501.

  Further, programs or software necessary for the implementation of the present invention are usually installed or stored in a hard disk or the like constituting the storage unit 3502, and all of them are stored in the memory in the storage unit 3502 when necessary. Alternatively, it is read out as a part of program modules or software modules, and is appropriately operated by the CPU 3503.

  The execution of the operation does not necessarily have to be performed by the central processing unit 3503 such as a CPU, and an auxiliary operation device such as a digital signal processor (DSP) not shown can be used.

  Next, with reference to FIGS. 4 to 6, an operation flow of the server and the terminal device included in the system according to the embodiment of the present invention will be described. The system according to the embodiment of the present invention performs new ticket issue processing or ticket management processing by the cooperation operation of the server and the terminal device described above.

  First, FIG. 4 illustrates a processing flow when reading a user code (also referred to as “Usercode”) printed on a paper medium via a terminal device (tablet terminal or the like) according to an embodiment of the present invention. Specifically, the terminal device according to the embodiment of the present invention is characterized in that the medium to be delivered to the user may be a paper medium such as a ticket (hereinafter referred to as "ticket medium") and may not necessarily be an electronic device. have. That is, it is not essential to record the service value in the user terminal. First, the basic concept of the present invention will be described as follows.

[Basic concept of the present invention]
(1) Ticket media in which user code is recorded (The present invention is not limited to this, but paper media such as cards may be mentioned, and in addition, goods such as badges and fan fans in which user code is recorded are Is associated with one or more services in the information management server that manages the user code, and has a value such as an entrance ticket to an amusement facility such as an amusement park or It becomes a ticket. The ticket is read as an admission ticket or the like by a reader (not shown) provided in a facility or the like, so that whether the ticket or the like has a value is checked and processed on the server.
In the above sense, even if the user does not possess an electronic device such as a smartphone, it can be used as long as it has enough ticket media, so it can be a friendly medium for the elderly and children. Moreover, since the person who gives out the ticket does not need the device operation more than necessary, he can feel it freely.
At this point, the ticket medium is not tied to the owner, and has a feature as a secret service ticket.

(2) A plurality of services can be linked to the same ticket medium by a mechanism to be described later. For example, one ticket medium links an amusement park entrance ticket (first service) and a plurality of vehicle tickets (second service) available in the amusement park, or a movie admission ticket (1 The second service) is linked to a drink ticket (second service).

(3) When linking (selling) a service to a ticket medium, the user code of the ticket medium is read by a terminal device described later, and the service prepared in advance in the information management server is linked to the user code Although it is carried out by this method, it is possible to link the payment for the money to be paid at this time (temporarily cash payment here) to the user code as electronic money. The linked electronic money can be stored, and can be used for payment at a place where predetermined payment processing can be performed.
At this point, since the ticket medium is an anonymous service ticket, even if one or more services lose their associated ticket medium and another person has picked it up and used it, tracking, service lock, etc. Can not. That is the same as losing a paper ticket (unsigned) or bill.

(4) Since the user code is recorded on the ticket medium (the present invention is not limited to this, for example, it is printed or affixed in the form of a two-dimensional code), any user-owned The information page (for example, the web page specified by the URL) associated with the user code can be accessed by the information terminal, and the balance of the balance when the currently linked service content and fishing are stored You can check etc.

(5) And, in the above situation (4), it is possible to register an account later. Although this invention is not limited to this, it is setting registration of personal information, such as a name and a mail address, and authentication information, such as a password, as an example.
At this point, the ticket medium is changed from the anonymous type service ticket to the registered type service ticket. If the ticket medium, which has become a registered service ticket, is temporarily lost, the information terminal associated with the user code is accessed by the user's information terminal, and the lock processing or cancellation (cancellation) processing of the service, Alternatively, the reissue process can be performed, and the system can be operated as a robust and flexible ticket medium.

  Here, the registration type does not necessarily make it necessary to register personal information such as a real name, but may be a pseudonym such as a nickname or a user name. In addition, in the case of making a bearer type service ticket a registered type, in principle anybody can make a registered type as long as the bearer type service ticket is obtained. For example, a user who has received a ticket can not change to a registered type, and the user who has received a ticket presents (transfers) to another user, and the other user is associated with the user code of the ticket. You can change to a registered service ticket by accessing the information page and registering the account.

  When the process is started by activating an application of the terminal or the like in step S401 in FIG. 4, a user code recorded in a ticket medium such as a paper medium is read in step S402 via the terminal device 102a. At this time, the terminal device 102a does not necessarily have to be the terminal of the user himself, for example, a terminal device possessed by a ticket issuing side such as a salesman at a hotel house or a souvenir shop, or a salesperson at a gaming facility. You may do it (following on that premise, continue explanation).

  In addition, although only the user code is usually recorded in the ticket medium and the service is not linked, there may be a case where a predetermined service is linked in advance (in that case, as will be described later) Can handle additional services).

  In step S403, the user code read in the previous step is transmitted to the information management server 101, and the information page (My page) corresponding to the user code is accessed. Although the present invention is not limited to this, one aspect of the information page includes a user information area on an information management server that can be specified and accessed by a URL.

  In step S404, if there is a service etc. that has already been linked in the accessed information page, this is sent to the terminal device side, and displayed on the display unit of the terminal device (this is shown in FIG. 7A). See below, etc.).

  The processing steps so far are processing such as reading of a user code from one ticket medium and access to an information page corresponding to the user code. In this flow, related information can be read from a plurality of ticket media at one time. Specifically, the process proceeds to step S405, in which it is determined whether the user code has been read from all the media. If the result is Yes, the process proceeds to step S406, and the process ends as this flow, but if No, the process proceeds to step S402. To return.

  FIG. 5 is a process typically performed following the flow illustrated and described in FIG. 4 and illustrates a process flow for linking a service to a ticket medium via a terminal device (screen on terminal device An example will be described later with reference to FIG. 7A etc.).

  When the process is started in step S501 of FIG. 5, the process proceeds to step S502, where it is determined whether or not the settlement (payment) process for the already linked service is to be performed by an instruction from the terminal device or the like. The process advances to step S507, but if No, the process advances to step S503 (of course, if there is no target to be settled at this time, an alert or the like not shown can be displayed on the display unit of the terminal device).

  In step S503, it is determined from the already read user code whether or not there is a selection of a user code for linking a service described later based on an instruction from the terminal device, etc. If No, the process skips to step S505. In the case of Yes, the process proceeds to step S504, and a user code to be linked with a service on the terminal device is selected. Then, the process proceeds to step S505.

  In step S505, it is determined whether or not there is an additional process of a service (which can also be called itself a ticket) to the target user code by an instruction from the terminal device or the like. If No, the process returns to step S502. However, in the case of Yes, the process proceeds to step S506, and a service linked to the target user code is selected from the services managed on the information management server and read in advance in the terminal device as necessary.

Here, various services are classified and managed by service identifiers as illustrated in the following table on the information management server.

  In addition, tying a service to a user code is synonymous with selling a ticket to a user (a trade is established by payment from a user to a terminal device operator).

  In step S507, the terminal device transmits the service selected in the previous step as a service requested to be added to the information management server, and the service is added to the user code managed on the information management server (specifically, Is tied up).

  Then, the process returns to step S502.

In step S508 (if YES in step S502), a settlement process is performed on unpaid tickets (services). A specific example of this process will be described later with reference to FIGS. 7D and 7E.
Next, the process proceeds to step S509, and the flow ends.

  6 is a process typically performed following the flow illustrated and described in FIG. 5, and the information management server is accessed via the terminal device 102a or the like and any other information terminal, A process flow in the case of performing the above registration (hereinafter referred to as "account registration") will be described.

  When the process is started by reading the user code recorded in the ticket medium by the terminal device 102a or the like or another arbitrary information terminal in step S601 in FIG. 6, the read user code (the present invention is not limited to this Although it is not a case, the My page (which is an aspect of the information page) on the information management server associated with the user code is accessed based on the code including the URL for accessing the information page). Ru.

  Next, the process proceeds to step S603, and the terminal user who has accessed the My page on the information management server can check the ticket and the service content linked to the user code corresponding to the My page. The ticket referred to here is also a type of service, and is a service that takes an entrance ticket to an amusement park or a movie theater as a typical example, and is temporarily distinguished from a fishing (balance) charge service etc. described later.

An example of confirmation items such as service contents in step S603 is as shown in the following table.
That is, service identifiers 0001 (tour ticket A (adult)), 00003 (movie admission ticket B), 0004 (drink ticket), and 0005 (remaining charge) are linked to the user code C1.

Further, the balance is linked as follows by a link or the like (not shown) as the balance of the remaining charge of the user code C1.
As shown in the above table, the balance charge associated with the user code C1 is associated with 1870 (yen) as the quantity. This balance can be used as electronic money in a suitable payment system or facility (not shown) equipped with a payment device.

Next, proceeding to step S604, it is determined whether or not account registration is required by the operation of the terminal device 102a or the like or any other information terminal. In the case of No in the same step, the process skips to step S608, but in the case of Yes, the process proceeds to step S605.
The operation of an arbitrary information terminal or the like here is pressing of a registration procedure start button or the like for executing account registration.

In step S605, account registration is performed in accordance with a normal guidance procedure (not shown). The contents of registration here are as shown in the following table.
Here, the user name may not necessarily be a real name, but may be a temporary name such as a nickname. The username acts like a login ID for accessing the server. The password is a login password for accessing the server, which improves the robustness of account registered ticket media. An e-mail address etc. can be optionally registered in the contact address (it is also possible to adopt an e-mail address as the user name). The electronic account information is an optional registration item prepared for linking the balance of the ticket medium to the existing user account.

  In the present embodiment, the ticket medium for which the user name is set and the account is registered is not necessarily a real name, but a ticket medium of a registered type or a service ticket of a registered type may be used. The service that can be requested from the management server is called a registered service (details will be described later).

  Then, when the registration process is completed in step S605, the information is managed on the information management server, and the process proceeds to step S606.

  In step S606, it is determined whether the registered service is received by the operation of an arbitrary information terminal or the like that has accessed the My page (these are realized by a specific service execution operation not shown), and in the case of No The process skips to S608, but in the case of Yes, the process proceeds to step S607.

In step S 607, it is possible to make a processing request (name service request) for various tickets and services linked to the My page by the operation of an arbitrary information terminal or the like that has accessed the My page. An example is shown in the following table.
The service lock process is to lock the target service ticket so that it can not be used. For example, when the circulation ticket A (adult) is locked, the service (use of the circulation ticket A (adult)) linked to (the user code of) the ticket medium is stopped.
The service cancellation process is for canceling the service ticket that has been targeted. For example, when the circulation ticket A (adult) is canceled, the service (use of the circulation ticket A (adult)) linked to (the user code of) the ticket medium is deleted.
The service reissuing process is for reissuing a service ticket that has been canceled once. For example, when the circulation ticket A (adult) that has been canceled once is reissued, the service (use of the circulation ticket A (adult)) is linked to the ticket medium (user code thereof). In the embodiment of the present invention, in the reissuing process, a list of tickets or services canceled in the past is presented by a presenting unit (not shown) so that the ticket or service to be reissued can be selected.

  Next, in step S608, it is determined whether or not access to the My page is to be ended, and if it is determined that the user instruction or the like is ended (Yes), the process proceeds to step S609 and this flow ends. If No, the process returns to step S603.

  After the account registration, steps S604 and S605 in the flow shown in FIG. 6 are omitted. Although not shown, it is also possible to delete the content once registered for account (registration cancellation processing). The ticket medium subjected to the deregistration process returns to the anonymous type service ticket.

  7A to 7E show screen examples of the terminal device in the system according to the embodiment of the present invention. FIG. 7A shows an example of the screen of the terminal when reading the user code recorded in the ticket medium (step S402 in FIG. 4 and the like), and FIG. 7B shows when the user code is read from a plurality of ticket media ( FIG. 7C shows an example of the screen of the terminal device immediately after completing step S405 in FIG. 4 and FIG. 7C shows No when the ticket or service is added to the read user code (No in step S502 in FIG. 5) 7D and 7E show an example of the screen of the terminal device of the loop to return to step S502 again through S506, and FIGS. 7D and 7E show the time of the settlement process after adding the ticket or service to the user code (step S508 of FIG. 5). 7 shows an example of the screen of the terminal device of FIG.

  In FIG. 7A, on the screen 711 of the terminal device, a moving image being shot is displayed as an example, and it is going to catch a ticket medium 7111 to be read. In the figure, the media ticket 7111 is stored at the center of the screen, and the two-dimensional code 71111 recorded on the media ticket 7111 is read by a known scan function (not shown). In one embodiment of the present invention, the user code is embedded in the two-dimensional code 71111, and the user code read by the terminal device is transmitted to the information management server.

In FIG. 7B, the read user codes 7211 and 7213 are visibly displayed on the screen 721 of the terminal device (this may be the URL itself for the information page, or a code for specifying the information page). It may be any corresponding character code). In the figure, since tickets and services are not yet associated with each user code, ticket (service) addition buttons 7212 and 7214 are displayed below the respective code display fields. In one embodiment of the present invention, pressing the add button displays a menu screen (not shown) in which addable tickets and / or services are listed. The user selects a ticket or service to be added for each user code.
At the bottom of the screen 721, a payment button 7215 is displayed. When this button is pressed, the process proceeds to payment processing as described later with reference to FIGS. 7D and 7E.
In one embodiment of the present invention, cash payment is assumed, and a payment amount selection button 7217 is provided so that processing can be easily performed even if a single good amount (1000 yen, 1500 yen, 2000 yen, etc.) is received. It is prepared. When the payment amount selection button 7217 is pressed, a plurality of discrete payment amounts are presented as described later with reference to FIG. 7D.

In FIG. 7B, when the payment is completed, pressing of the payment receipt button 7216 electronically issues the ticket or service added (at this point, the ticket or service linked to each user code is Alternatively, at this point, a ticket issued flag (not shown) for a ticket or service linked to each user code may be processed to be turned off from on).
Reference numeral 7218 denotes a target card reading button. When the button is pressed, the scan screen as shown in FIG. 7A is returned as an example, and the user code recorded in a new ticket medium can be read.

  In FIG. 7C, the terminal device screen 731 displays tickets (including unpaid cases) or services added to each user code. Specifically, a ticket 7312 (tour ticket A (adult)) and a service 7313 (remaining charge) are added to the user code 7311, and a user code 7314 has a ticket 7315 (tour ticket A (little person) ) Has been added. For each user code, tickets and / or services can be added by pressing the add button 7314 and 7316 respectively.

The buttons 7137 to 7320 correspond to the buttons 715 to 7218, respectively.
Further, in the lower central part of the screen 731 in FIG. 7C, a total of “2250 yen” at the present time is exemplarily displayed.

FIG. 7D illustrates an example screen during the payment procedure. On the screen 741 of the terminal device, for example, the payment amount is selected on the terminal device which has shifted to the payment mode by pressing the payment button 7416 or the like. Specifically, from the amounts in the payment amount list 7415 where a plurality of discrete payment amounts displayed by pressing the payment amount selection button 7418 or the like are listed, they were received as payment for 2500 yen (total payment 2250 yen Cash) is selected and reflected on button 7418.
Next, the ticket issue processing is completed by pressing the payment receipt button 7417, and the linking of the ticket or service added to each user code is determined.
The buttons 7416 to 7419 correspond to the buttons 7137 to 7320, respectively.

  Here, the processing for fishing can be processed as follows through screen transition (not shown). That is, with regard to the fishing (2500 yen to 2250 yen = 250 yen) in the present embodiment, an inquiry to the user is generated where to charge by a guidance dialog not shown, etc., the remaining charge charging service already added, and other not shown. By instructing management of the transfer service etc., the amount of money for the fishing is sent to the information management server. Then, in the information management server, the service identifier associated with the ticket or service selected by the instruction from the terminal device and the amount of fishing are associated with the corresponding user code and managed.

An example screen for completing the payment procedure is shown in FIG. 7E. In the ticketing system according to one embodiment of the present invention, since payment procedure can be performed for each user code, all the screens shown on the same screen for instructing the ticketing system to complete the payment procedure for the user code To complete the payment procedure.
That is, when the payment completion button (not shown) is pressed, a payment completion confirmation dialog 7511 is displayed, and it is confirmed whether the payment procedure may be really completed. When the affirmation button 75111 is pressed, the payment procedure is completed, but when the negation button 75112 is pressed, the screen returns to the screen illustrated in FIG. 7C as an example.
Buttons 7512 to 7515 correspond to buttons 7416 to 7419, respectively.

  Although the embodiment of the ticket issuing system and the like according to the embodiment of the present invention has been described above based on the specific example, the embodiment of the present invention is a program other than a method or program for implementing the system or apparatus. It is also possible to take an embodiment as a recorded storage medium (for example, an optical disc, a magneto-optical disc, a CD-ROM, a CD-R, a CD-RW, a magnetic tape, a hard disk, a memory card) or the like.

  Also, the implementation form of the program is not limited to application programs such as object code compiled by a compiler and program code executed by an interpreter, and may be a form such as a program module incorporated in an operating system. good.

  Furthermore, the program does not necessarily have to carry out all the processing only in the CPU on the control board, and an expansion board added to the board or another processing unit (DSP etc.) mounted on the expansion unit as needed. ) May be configured to be implemented partially or entirely.

  These features are mutually exclusive with respect to all the constituent elements described in the specification (including the claims, the abstract, and the drawings) and / or all steps of all the disclosed methods or processes. Except for the combination which is

  Also, each of the features described in this specification (including the claims, abstract, and figures) serves the same purpose, an equivalent purpose, or an analogous purpose, unless explicitly denied. Alternative features can be substituted. Thus, unless expressly stated to the contrary, each of the disclosed features is only an example of a generic series of identical or equivalent features.

  Furthermore, the present invention is not limited to any specific configuration of the above-described embodiment. The present invention comprises all novel features or combinations thereof described herein (including claims, abstracts and figures), or all novel methods or process steps described, or Can be extended to combinations of

10 Ticketing system 101 Information management server 102a-102d Terminal device (tablet terminal etc.)
103a to 103f tickets (usercode printed or recorded)
104 Other two-dimensional code with usercode printed on it (possible to attach to media other than paper)
109 Public Line (Dedicated Line, Internet etc.)

Claims (4)

A ticketing system comprising an information management server and one or more terminal devices,
The information management server includes a management unit that manages one or more information pages associated with one user code, and manages one or more service identifiers that can be associated with the user code.
The terminal device includes an input unit that reads the user code from a ticket in which the user code is recorded, and a transmission unit that transmits the read user code to the information management server.
The information management server transmits to the terminal device to present the service associated with the service identifier managed by the terminal device according to a request from the terminal device, and presents the service selected by the instruction from the terminal device. A ticket issuing system characterized by associating a service identifier associated with a service that has been made with the user code. The management unit manages the price of the service,
The terminal device presents a plurality of discrete payment amounts, and
From the one payment amount when the payment amount for the service is higher than the price of the service according to an instruction from the terminal device and one of the plurality of discrete payment amounts is selected Send the amount of fishing minus the price of the service to the information management server,
The system according to claim 1, wherein the management unit associates a service identifier associated with the service selected according to an instruction from the terminal device and the amount of the fishing to the user code. The one information page associated with the one user code managed by the information management server is configured to be accessible from any information terminal via a ticket in which the user code is recorded,
The system according to claim 1 or 2, wherein account registration is enabled for the user code of 1 by a request from the arbitrary information terminal. For the one user code registered in the account, it is possible that lock processing, cancellation processing and re-issuance processing of the already linked service are possible by the request from the arbitrary information terminal. The system according to claim 3, characterized in that: