Seating confirmation system and seating confirmation program

Abstract

To reduce the number of passengers of which tickets are checked by a conductor.SOLUTION: A seating determination system is provided with a server according to an embodiment, in which the server comprises: a reception unit that receives seating information including a seat number of a seat in response to a determination input of the seating to the seat from a user terminal accessing a first Web page designated by a URL included in first two-dimensional code information acquired from a two-dimensional code installed in a seat of a vehicle; a storage unit that stores seat information indicative of whether the seat is booked or not; and a boarding information control unit that, when the seat number included in the seating information is booked, updates information indicative of a user siting on the seat so as to add the information to the seat information, and causes the updated seat information to be stored in the storage unit.SELECTED DRAWING: Figure 9

Description

Technical Field

[0001] Embodiments of the present invention relate to a seating confirmation system and a seating confirmation program.

Background Art

[0002] When using an express train, an express ticket is required. However, there are railway operators who do not operate by passing the express ticket through the ticket gate. Therefore, in order to surely confirm that a user has purchased an express ticket, the conductor needs to check the express ticket of each user (passenger). However, since it takes time to check the express ticket of each user, operations such as checking the express ticket of selected users or not performing ticket inspection when a user is sitting in a reserved seat are carried out.

[0003] There is also a system in which a user holds an IC card over an IC reader installed in each seat at the same time as sitting down to confirm that the user has taken a seat.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] If the conductor does not check the express ticket of the user, there is a problem that it is impossible to confirm whether a user who has actually made a reservation is sitting in the reserved seat. In addition, although it is necessary to modify the vehicle in order to install an IC reader in each seat, there is also a problem that the modification cost is high.

[0006] This invention has been made paying attention to the above circumstances, and an object thereof is to provide a technology capable of reducing the labor of the conductor for ticket inspection and performing boarding confirmation of each user without requiring modification of the vehicle or the like. [Means for solving the problem]

[0007] A seat confirmation system comprising a server according to an embodiment, wherein the server includes: a receiving unit that receives seat information including the seat number of a seat in response to a confirmation input of seating in the seat from a user terminal that accesses a first web page specified by a URL included in first two-dimensional code information obtained from a two-dimensional code installed on a seat of a vehicle; a storage unit that stores seat information indicating whether the seat is reserved or not; and a passenger information control unit that updates the seat information to include information indicating that a user has sat in the seat if the seat number included in the seat information is reserved, and stores the updated seat information in the storage unit. [Brief explanation of the drawing]

[0008] [Figure 1] Figure 1 is a conceptual diagram showing an example of a ticketing system according to the first embodiment. [Figure 2] Figure 2 shows an example of a limited express ticket issued by ticket machine 2. [Figure 3] Figure 3 is a block diagram showing an example of the hardware configuration of the server and ticket machine according to the embodiment. [Figure 4] Figure 4 is a block diagram showing the software configuration of the server and ticket machine in the first embodiment, in relation to the hardware configuration shown in Figure 4. [Figure 5] Figure 5 is a sequence diagram showing an example of the ticketing procedure in the ticketing system shown in Figure 1. [Figure 6] Figure 6 is a conceptual diagram showing an example of a seating confirmation system in the first embodiment. [Figure 7] Figure 7 is a block diagram showing an example of the hardware configuration of the server and user terminal in the first embodiment. [Figure 8] Figure 8 is a block diagram showing the software configuration of Server 1 and User Terminal 3 in the first embodiment, in relation to the hardware configuration shown in Figure 7. [Figure 9] Figure 9 is a sequence diagram showing an example of the seating confirmation procedure in the seating system shown in Figure 6. [Figure 10] Figure 10 is a conceptual diagram showing an example of the configuration of a ticket inspection system according to an embodiment. [Figure 11] Figure 11 shows an example of seat information displayed on the output section of a passenger confirmation terminal. [Figure 12] Figure 12 is a conceptual diagram showing an example of a ticketing system and a seat confirmation system in the second embodiment. [Figure 13] Figure 13 is a block diagram showing the software configuration of the server and user terminal in the second embodiment, in relation to the hardware configuration shown in Figure 7. [Figure 14] Figure 14 is a sequence diagram showing an example of the ticketing procedure in the ticketing system shown in Figure 11. [Figure 15] Figure 15 is a sequence diagram showing an example of the seating confirmation procedure in the seating system shown in Figure 11. [Modes for carrying out the invention]

[0009] The seating confirmation system and seating confirmation program will be described in detail below with reference to the drawings. In the following embodiments, parts with the same numbering perform the same operation, and therefore repeated explanations will be omitted. For example, when there are multiple identical or similar elements, a common reference numeral may be used to describe each element without distinction, or a sub-number may be used in addition to the common reference numeral to describe each element separately.

[0010] [First Embodiment] (Configuration of the ticketing system) Figure 1 is a conceptual diagram showing an example of a ticketing system according to the first embodiment. The ticket issuing system is, for example, a system that issues express tickets required when boarding an express train in a transportation facility such as a railway. Note that the ticket issuing system can also be applied to a system that issues green tickets when using a green car, sleeping car tickets when using a sleeping car, etc., that is, a system that issues additional tickets in addition to the boarding ticket.

[0011] As shown in FIG. 1, the ticket issuing system includes a server 1, a ticket issuing machine 2, etc.

[0012] The server 1 is installed at a predetermined location managed by the railway operator. The server 1 is a server that manages the ticket issuing status of express trains. For example, it stores seat numbers of express trains, reservation status, etc. The server 1 may also store a diagram of the express train, etc. The server 1 can provide the stored information in response to various requests from the ticket issuing machine 2. For example, when the ticket issuing machine 2 receives an inquiry about a predetermined express train, the server 1 transmits information including information such as the reservation status of the seats of the predetermined express train to the ticket issuing machine 2.

[0013] The ticket issuing machine 2 is installed at a predetermined location within the station building. In FIG. 1, only one is shown for simplicity, but a plurality of ticket issuing machines 2 may be installed within the station building. The ticket issuing machine 2 can purchase express tickets, etc. Note that the ticket issuing machine 2 may also be able to purchase boarding tickets, commutation tickets, etc. Also, the ticket issuing machine 2 is not limited to the ticket issuing machine 2 directly operated by the user, and may be a ticket issuing machine 2 operated by a station staff member. Here, the user may be a passenger.

[0014] FIG. 2 is a diagram showing an example of an express ticket TC issued by the ticket issuing machine 2. As shown in FIG. 2, in addition to the ticket information including the express ticket ID, the date of boarding the express train on which the user boards, the departure and arrival stations, the arrival time, the fare, the reserved seat number, etc., the express ticket TC may have a two-dimensional code printed thereon for accessing a predetermined URL.

[0015] FIG. 3 is a block diagram showing an example of the hardware configuration of the server 1 and the ticket issuing machine 2 according to the embodiment. Server 1 comprises a control unit 11, a program storage unit 12, a data storage unit 13, a communication interface 14, and an input / output interface 15. The control unit 11, the program storage unit 12, the data storage unit 13, the communication interface 14, and the input / output interface 15 are connected to each other via a bus so that they can communicate with one another.

[0016] Server 1 can perform various operations using computers such as PCs (Personal Computers).

[0017] The control unit 11 controls the server 1. The control unit 11 includes a hardware processor such as a central processing unit (CPU).

[0018] The program storage unit 12 is configured by combining, for example, a non-volatile memory that can be written to and read at any time, such as an SSD (Solid State Drive), and a non-volatile memory such as a ROM (Read Only Memory), and stores application programs necessary to execute various control processes according to one embodiment, in addition to middleware such as an OS (Operating System). Hereafter, the OS and each application program will be collectively referred to as a program.

[0019] The data storage unit 13 may, for example, be a combination of a non-volatile memory such as an SSD that allows for on-demand writing and reading, and a volatile memory such as RAM (Random Access Memory), as the storage medium.

[0020] The communication interface 14 includes one or more wired or wireless communication modules. For example, the communication interface 14 includes a communication module that connects to the ticket machine 2 via a wired or wireless connection, either directly or via a network. The communication interface 14 may also include a communication module that connects wirelessly to the user terminal 3. The communication interface 14 can be any general communication interface that can communicate with the ticket machine 2 or the user terminal 3 and send and receive various types of information under the control of the control unit 11.

[0021] The input / output interface 15 is connected to the input unit 151 and the output unit 152, etc. The input / output interface 15 is an interface that enables the transmission and reception of information between the control unit 11 and the input unit 151 and the output unit 152. The input / output interface 15 may be integrated with the communication interface 14. For example, the input / output interface 15 may be wirelessly connected to the control unit 11 and the input unit 151 or the output unit 152 using short-range wireless technology, and information may be transmitted and received using said short-range wireless technology.

[0022] The input unit 151 may include, for example, a keyboard or pointing device for an administrator managing the server to input various information to the server 1. The input unit 151 may also include a reader for reading data to be stored in the program storage unit 12 or the data storage unit 13 from a memory medium such as a USB memory, or a disk device for reading such data from a disk medium.

[0023] The output unit 152 includes a display that shows output data to be presented to the administrator from the server 1, and a printer for printing it.

[0024] The ticket dispenser 2 comprises a control unit 21, a program storage unit 22, a data storage unit 23, a communication interface 24, and an input / output interface 25. The control unit 21, the program storage unit 22, the data storage unit 23, the communication interface 24, and the input / output interface 25 are connected to each other via a bus so that they can communicate with one another.

[0025] Ticket machine 2 can perform various operations using a computer such as a PC.

[0026] The control unit 21 controls the ticket dispenser 2. The control unit 21 includes a hardware processor such as a central processing unit (CPU).

[0027] The program storage unit 22 is configured, for example, by combining a non-volatile memory such as an SSD that allows writing and reading at any time as a storage medium, and a non-volatile memory such as ROM, and stores the program.

[0028] The data storage unit 23 may, for example, be a combination of a non-volatile memory such as an SSD that allows for on-demand writing and reading, and a volatile memory such as RAM, as the storage medium.

[0029] The communication interface 24 includes one or more wired or wireless communication modules. For example, the communication interface 24 includes a communication module that connects to the server 1 via a wired or wireless connection, either directly or via a network. The communication interface 24 can be any general communication interface that can communicate with the server 1 and send and receive various types of information under the control of the control unit 21.

[0030] The input / output interface 25 is connected to the input unit 251, the output unit 252, and the ticket issuing unit 253, etc. The input / output interface 25 is an interface that enables the transmission and reception of information between the control unit 21 and the input unit 251, the output unit 252, and the ticket issuing unit 253. The input / output interface 15 may be integrated with the communication interface 14. For example, the input / output interface 15 may be wirelessly connected to the control unit 21 and at least one of the input unit 251, the output unit 252, or the ticket issuing unit 253 using short-range wireless technology, and information may be transmitted and received using said short-range wireless technology.

[0031] The input unit 251 may include, for example, a keyboard or pointing device for the user to input various information to the ticket machine 2. The input unit 251 may also include a reader for reading data to be stored in the program storage unit 22 or the data storage unit 23 from a memory medium such as a USB memory, or a disk device for reading such data from a disk medium.

[0032] The output unit 252 includes a display device, such as a liquid crystal or organic EL display. The display device displays various information received from the server 1 to the user.

[0033] The ticketing unit 253 includes, for example, a printer for printing express train tickets (TC). The printer issues express train tickets (TC) based on input information from the user and various information received from the server 1.

[0034] Figure 4 is a block diagram showing the software configuration of Server 1 and Ticket Machine 2 in the first embodiment, in relation to the hardware configuration shown in Figure 4. The data storage unit 13 of server 1 includes a seat information storage unit 131. The seat information storage unit 131 stores seat information, including whether or not a seat S on each limited express train is reserved, and information related to the reserved seat S. The seat information storage unit 131 may also store ticketing information for reserved limited express tickets TC, linked to each seat S. For example, the ticketing information may include the limited express ticket ID, limited express train information associated with the limited express ticket ID, date of travel, departure and arrival stations, arrival time, fare, seat number, etc.

[0035] The control unit 11 of server 1 includes an information control unit 111 and a URL generation unit 112.

[0036] The information control unit 111 receives a limited express ticket issuance request from the ticketing machine 2 via the communication interface 14, requesting the issuance of a limited express ticket TC. The limited express ticket issuance request includes, for example, information indicating which seat S the user wishes to reserve on the limited express train, the date of travel, the departure and arrival stations, etc. The information control unit 111 outputs the necessary information included in the acquired limited express ticket issuance request to the URL generation unit 112. Here, the necessary information will be described later. Furthermore, the information control unit 111 receives URL information from the URL generation unit 112. The information control unit 111 also updates the seat information stored in the seat information storage unit based on the limited express ticket issuance request and the URL information. Furthermore, the information control unit 111 transmits a limited express ticket issuance response to the ticketing machine 2, which includes the URL information and information indicating that it is OK to issue the limited express ticket TC.

[0037] The URL generation unit 112 generates a unique URL for the express ticket TC based on the express ticket issuance request. The URL generation unit 112 then outputs the URL information, including the generated URL, to the information control unit 111 via the communication interface 14.

[0038] The data storage unit 23 of the ticket vending machine 2 includes an acquired information storage unit 231. The acquired information storage unit 231 stores information entered by the user into the input unit 251, etc. Furthermore, the acquired information storage unit 231 stores necessary information. Necessary information includes, for example, information indicating the date and time of the express train, the seat S to be purchased, the departure and arrival stations, etc.

[0039] The control unit 21 of the ticketing machine 2 comprises a request generation unit 211, a two-dimensional code generation unit 212, and a ticketing control unit 213. The request generation unit 211 generates a limited express ticket issuance request including necessary information and the ticketing machine ID, and transmits the generated limited express ticket issuance request to the server 1.

[0040] The 2D code generation unit 212 receives the express ticket issuance response. The 2D code generation unit 212 then generates a 2D code containing the URL based on the URL included in the received express ticket issuance response. Furthermore, the 2D code generation unit 212 outputs the generated 2D code and the express ticket issuance response to the ticket issuance control unit 213.

[0041] The ticketing control unit 213 generates a ticketing instruction based on the 2D code, the express ticket issuance response, and the necessary information, and outputs the generated ticketing instruction to the ticketing unit 253.

[0042] (Ticket issuance process) Figure 5 is a sequence diagram showing an example of the ticketing procedure in the ticketing system shown in Figure 1. This sequence of operations is realized when the control unit 11 of server 1 and the control unit 21 of ticket machine 2 read and execute the programs stored in the program storage unit 12 and program storage unit 22, respectively.

[0043] First, the user wishes to purchase a limited express ticket (TC), and this sequence begins when the user or a station employee inputs the necessary information for issuing the ticket (TC) using the input section 251 of the ticket vending machine 2. Here, the necessary information includes information indicating the date and time of the limited express train, the desired seat (S), and the departure and arrival stations. The ticket vending machine 2 may also query the server 1 as needed to confirm that there are no reservations for the seat (S) corresponding to the necessary information.

[0044] The request generation unit 211 of the ticket vending machine 2 generates a limited express ticket issuance request (step ST101). The request generation unit 211 obtains necessary information from the input unit 251 through the input / output interface 25. The request generation unit 211 then stores the necessary information in the acquired information storage unit 231. Furthermore, the request generation unit 211 generates a limited express ticket issuance request based on the necessary information. Here, the limited express ticket issuance request may include the ticket vending machine ID, etc., in addition to the limited express ticket information.

[0045] The request generation unit 211 transmits a limited express ticket issuance request (step ST102). The request generation unit 211 transmits the generated limited express ticket issuance request to the server 1 via the communication interface 24. The request generation unit 211 may also output necessary information to the ticket issuance control unit 213.

[0046] The URL generation unit 112 generates a URL (step ST103). The information control unit 111 receives the express train ticket issuance request through the communication interface 14. The information control unit 111 then outputs the necessary information included in the express train ticket issuance request to the URL generation unit 112. The URL generation unit 112 generates a URL that allows access to a predetermined web page that notifies the server 1 that the user of the express train ticket has boarded the specified express train. The URL generation unit 112 outputs the URL information, including the generated URL, to the information control unit 111.

[0047] The information control unit 111 of server 1 updates the seat information (step ST104). Based on the necessary information included in the express ticket issuance request and the URL information received from the URL generation unit, the information control unit 111 updates the seat information stored in the seat information storage unit 131. That is, based on the necessary information included in the express ticket issuance request, the information control unit 111 updates the seat information to change the seat S of the relevant train to a reserved seat S. Furthermore, it links the boarding completion information with the seat information based on the URL information. The information control unit 111 stores the updated seat information in the seat information storage unit 131. Here, the boarding completion information is information indicating that the user has accessed the web page specified by the URL included in the URL information and touched the button indicating that they have boarded the reserved express train.

[0048] The information control unit 111 transmits a limited express ticket issuance response (step ST105). The information control unit 111 identifies the ticketing machine 2 based on the ticketing machine ID included in the limited express ticket issuance request. The information control unit 111 then transmits a limited express ticket issuance response, including the generated URL, the limited express ticket ID, and information indicating that it is OK to issue the limited express ticket TC, to the identified ticketing machine 2 via the communication interface 14.

[0049] The 2D code generation unit 212 generates a 2D code (step ST106). The 2D code generation unit 212 receives a limited express ticket issuance response from the server 1 via the communication interface 24. The 2D code generation unit 212 then generates a 2D code based on the URL included in the limited express ticket issuance response. The 2D code may include the URL. The 2D code generation unit 212 then outputs the generated 2D code and the limited express ticket issuance response to the ticketing control unit 213.

[0050] The ticketing control unit 213 outputs a limited express ticket issuance instruction to the ticketing unit 253 (step ST107). Based on the 2D code received from the request generation unit 211, the limited express ticket issuance response, and the necessary information, the ticketing control unit 213 generates an issuance instruction and outputs the generated issuance instruction to the ticketing unit 253. Upon receiving the issuance instruction, the ticketing unit 253 issues a limited express ticket TC with ticket information and a 2D code printed on the ticket surface, as shown in Figure 2.

[0051] When a user receives a limited express ticket (TC), they will scan the 2D code printed on the ticket (TC) with their user terminal or other device to access a designated webpage before boarding the limited express train. From there, the user will notify server 1 that they have boarded the reserved limited express train.

[0052] (Configuration of the seating confirmation system) Figure 6 is a conceptual diagram showing an example of a seating confirmation system in the first embodiment. The seat confirmation system includes a server 1, a user terminal 3, a limited express ticket TC, and a seat S.

[0053] User terminal 3 is a device used by the user. User terminal 3 is a device that the user can carry with them, such as a smartphone, wearable device, or tablet device. User terminal 3 is a device that can read, for example, the 2D code printed on the express ticket TC and the 2D code assigned to the train seat S.

[0054] Seat S is located inside the express train. Seat S is equipped with a 2D code assigned to it. Here, the 2D code may be placed anywhere on the seat S where the user is scheduled to sit. Alternatively, the 2D code may be placed on the back of the seatback of a seat S located in front of the seat S where the user is scheduled to sit, on a wall inside the train, etc.

[0055] Figure 7 is a block diagram showing an example of the hardware configuration of server 1 and user terminal 3 in the first embodiment. The hardware configuration of Server 1 is the same as that shown in Figure 2. Therefore, a detailed explanation is omitted here.

[0056] The user terminal 3 comprises a control unit 31, a program storage unit 32, a data storage unit 33, a communication interface 34, and an input / output interface 35. The control unit 31, program storage unit 32, data storage unit 33, communication interface 34, and input / output interface 35 are connected to each other via a bus so that they can communicate with one another.

[0057] User terminal 3 can perform various operations using a computer such as a PC.

[0058] The control unit 31 controls the user terminal 3. The control unit 31 includes a hardware processor such as a central processing unit (CPU).

[0059] The program storage unit 32 is configured, for example, by combining a non-volatile memory such as an SSD that allows writing and reading at any time as a storage medium, and a non-volatile memory such as ROM, and stores the program.

[0060] The data storage unit 33 may, for example, be a combination of a non-volatile memory such as an SSD that allows for on-demand writing and reading, and a volatile memory such as RAM, as the storage medium.

[0061] The communication interface 34 includes one or more wireless communication modules. For example, the communication interface 34 includes a communication module that wirelessly connects to the server 1 via a network. The communication interface 34 can be any general communication interface that can communicate with the server 1 and send and receive various types of information under the control of the control unit 31.

[0062] The input / output interface 35 is connected to the input unit 351, the output unit 352, and the reading unit 353, etc. The input / output interface 35 is an interface that enables the transmission and reception of information between the control unit 31 and the input unit 351, the output unit 352, and the reading unit 353. The input / output interface 35 may be integrated with the communication interface 34. For example, the input / output interface 35 may be wirelessly connected to the control unit 31 and at least one of the input unit 351, the output unit 352, or the reading unit 353 using short-range wireless technology, and information may be transmitted and received using said short-range wireless technology.

[0063] The input unit 351 may include, for example, a keyboard or pointing device for the user to input various information to the user terminal. The input unit 351 may also include a reader for reading data to be stored in the program storage unit 32 or the data storage unit 33 from a memory medium such as a USB memory, or a disk device for reading such data from a disk medium.

[0064] The output unit 352 includes a display device, such as a liquid crystal or organic EL display. The display device displays various information received from the server 1 to the user.

[0065] The reading unit 353 includes, for example, a two-dimensional code reader for reading a two-dimensional code printed on a limited express ticket TC or a two-dimensional code provided on a seat S. For example, if the two-dimensional code is a QR code (registered trademark), the reading unit 353 includes, for example, a QR code reader.

[0066] Figure 8 is a block diagram showing the software configuration of Server 1 and User Terminal 3 in the first embodiment, in relation to the hardware configuration shown in Figure 7. In addition to the software configuration shown in Figure 4, the control unit 11 of server 1 includes a passenger information control unit 113.

[0067] The passenger information control unit 113 operates as a receiving unit that receives passenger boarding completion information and seating information from the user terminal 3. Here, passenger boarding completion information and seating information will be described later. Based on the passenger boarding completion information and seating information, the passenger information control unit 113 updates the passenger information stored in the seat information storage unit 131.

[0068] The data storage unit 33 of the user terminal 3 includes a code information storage unit 331. The code information storage unit 331 is used to store the two-dimensional code information acquired by the code information acquisition unit 311, which will be described later.

[0069] The control unit 31 of the user terminal 3 includes a code information acquisition unit 311 and an operation control unit 312.

[0070] The code information acquisition unit 311 controls the reading unit 353 to read the 2D code printed on the express ticket TC or the 2D code installed on the seat S, and acquires the 2D code information. The code information acquisition unit 311 stores the acquired 2D code information in the code information storage unit 331.

[0071] The operation control unit 312 acquires the two-dimensional code information stored in the code information storage unit 331 and outputs the URL included in the two-dimensional code information to the output unit 352. The output unit 352 may display on the screen that the user can access the web page specified by the URL. Furthermore, the operation control unit 312 acquires the information entered by the user in the input unit 351. For example, if the user accesses the specified web page, the output unit 352, which displays the web page, will display a button to confirm that the user has boarded or taken a seat on the express train. The operation control unit 312 receives information indicating that the user has touched the displayed button. The operation control unit 312 sends the boarding completion information or seating information indicating that the button has been touched to the server 1 via the web server that manages the web page.

[0072] (Seating confirmation action) Figure 9 is a sequence diagram showing an example of the seating confirmation procedure in the seating system shown in Figure 6. This sequence of operations is realized when the control unit 11 of server 1 and the control unit 31 of user terminal 3 read and execute the programs stored in the program storage unit 12 and program storage unit 32, respectively.

[0073] First, this sequence begins with the user boarding the express train they have reserved.

[0074] The code information acquisition unit 311 acquires 2D code information (step ST201). First, when the user boards the express train, the reader unit 353 of the user terminal 3 reads the 2D code information from the 2D code printed on the express ticket TC. The code information acquisition unit 311 receives the read 2D code information from the reader unit 353. The code information acquisition unit 311 may store the 2D code information in the code information storage unit 331.

[0075] The operation control unit 312 accesses the specified web page (step ST202). The operation control unit 312 retrieves the 2D code information stored in the code information storage unit 331 and extracts the URL contained in the 2D code information. The operation control unit 312 then outputs the URL to the output unit 352. The output unit 352 displays on the display that the web page specified by the corresponding URL is accessible. The operation control unit 312 receives a signal from the input unit 351 indicating that the user wishes to access the specified web page. The operation control unit 312 accesses the specified web page based on this signal.

[0076] The operation control unit 312 transmits boarding completion information to the server 1 (step ST203). The URL is unique to the limited express ticket TC. Therefore, when the user accesses the web page, the output unit 352 displays information such as the limited express ticket ID, the reserved limited express train, seat S, departure and arrival stations. Furthermore, the output unit 352 displays a button to confirm that the user has boarded. After confirming that the user is on the correct limited express train, the user touches the button. The operation control unit 312 receives information from the input unit 351 indicating that the user has touched the displayed button, that is, that the user has confirmed that the train displayed on the web page matches the train on the limited express ticket held by the user. The operation control unit 312 transmits boarding completion information to the server 1 via the communication interface 34 and the web server that manages the web page, indicating that the user has confirmed that the train displayed on the web page matches the train on the limited express ticket held by the user.

[0077] The passenger information control unit 113 updates the seat information (step ST204). The passenger information control unit 113 receives boarding completion information through the communication interface 14. Based on the boarding completion information, the passenger information control unit 113 updates the seat information stored in the seat information storage unit 131. For example, based on the received boarding completion information, the passenger information control unit 113 obtains the seat information for the seat S reserved by the user from the seat information storage unit 131. Then, the passenger information control unit 113 updates the seat information to include information indicating that the user has boarded the reserved express train, and stores the updated seat information in the seat information storage unit 131.

[0078] In this case, the user may have the reader 353 read the 2D code of the express train ticket TC at a time when it is impossible for the user to board the express train they reserved, and access the web page. In such a case, server 1 determines, based on the seat information, that the user is not on the express train. Server 1 may then display information on the web page prompting the user to access the site again at the correct time and touch the button. Alternatively, the web server managing the web page may control the web page so that the button confirming boarding is not displayed or enabled until the time of arrival at the station the user is boarding. Furthermore, for example, the server managing the web page and server 1 may share the express train timetable, and the web server may obtain the arrival time of the express train at the station the user is boarding according to the timetable.

[0079] The code information acquisition unit 311 acquires 2D code information (step ST205). Next, the user sits down in the reserved seat S. Then, the user terminal 3 has the reader unit 353 read the 2D code information from the 2D code installed on seat S. The code information acquisition unit 311 receives the read 2D code information from the reader unit 353. The code information acquisition unit 311 may store the 2D code information in the code information storage unit 331.

[0080] The operation control unit 312 accesses the specified web page (step ST206). The operation control unit 312 retrieves the 2D code information stored in the code information storage unit 331 and extracts the URL contained in the 2D code information. The operation control unit 312 then outputs the URL to the output unit 352. The output unit 352 displays on the display that the web page specified by the corresponding URL is accessible. The operation control unit 312 receives a signal from the input unit 351 indicating that the user wishes to access the specified web page. The operation control unit 312 accesses the specified web page based on this signal.

[0081] The operation control unit 312 transmits seating information to the server 1 (step ST207). The URL is the unique URL of seat S. Therefore, when the user accesses the web page, the output unit 352 displays information about seat S. Furthermore, the output unit 352 displays a button for the user to confirm that they are seated in seat S. After the user confirms that they are seated in the correct seat S, they touch the button. The operation control unit 312 receives an input from the input unit 351 indicating that the user has touched the displayed button, i.e., an input confirming seating. Here, the confirmation input includes the seat number of seat S. The operation control unit 312 transmits seating information, including the seat number of seat S, to the server 1 via the communication interface 34 and the web server that manages the web page. In other words, the server 1 receives seating information, including the seat number of seat S, from the user terminal 3 in response to the input confirming seating.

[0082] The passenger information control unit 113 updates the seat information (step ST208). The passenger information control unit 113, acting as a receiver, receives seating information through the communication interface 14. The passenger information control unit 113 updates the seat information stored in the seat information storage unit 131 based on the seating information. For example, the passenger information control unit 113 obtains the seat information for the seat number indicated by the seating information from the seat information storage unit 131. If the seat S indicated by the seating information is reserved, the passenger information control unit 113 determines that the user has sat in the correct seat S, updates the seat information to add information indicating that the user has sat in the correct seat S, and stores the updated seat information in the seat information storage unit 131. Alternatively, the passenger information control unit 113 may determine that the user has sat in the correct seat S only when the seat information is updated by the boarding completion information, update the seat information to add information indicating that the user has sat in the correct seat S, and store the updated seat information in the seat information storage unit 131.

[0083] If the seat information obtained from the seating information is not reserved, Server 1 may instruct the user to read the 2D code on the express ticket TC and access the specified web page.

[0084] Furthermore, steps ST201 to ST204 and steps ST205 to ST208 described above may be performed individually. For example, in steps ST201 to ST204, it may be determined that the user has taken up the correct seat S based on the boarding completion information. On the other hand, in steps ST205 to ST208, in addition to seat information, information such as the limited express ticket ID may be entered on the web page, and this information may be sent from the user terminal 3.

[0085] (Ticket inspection) Figure 10 is a conceptual diagram showing an example of the configuration of a ticket inspection system according to an embodiment. The ticket inspection system includes a server 1 and a passenger confirmation terminal 4.

[0086] The passenger verification terminal 4 is a terminal used by the conductor when checking tickets on an express train. The passenger verification terminal is capable of communicating with server 1 and is a device that the conductor can carry, such as a smartphone, wearable device, or tablet. In other words, the passenger verification terminal 4 may have the same hardware and software configuration as the user terminal 3 described above. Therefore, a detailed explanation of the hardware and software configuration of the passenger verification terminal 4 is omitted.

[0087] The passenger confirmation terminal 4 receives seat information of the train on which the conductor is riding from the server 1 at predetermined intervals. For example, the passenger confirmation terminal 4 may receive seat information from the server 1 after the express train has departed from a station. For example, the control unit 11 of the server 1 may acquire the train's seat information stored in the seat information storage unit 131 based on the timetable stored in the data storage unit 13 and transmit it to the passenger confirmation terminal 4. Also, if the passenger confirmation terminal 4 receives an instruction from the conductor that they wish to update the information, it may send an update request to the server 1 and receive seat information from the server 1 in response to the request.

[0088] Figure 11 shows an example of seat information displayed on the output section of the passenger confirmation terminal 4. In the example in Figure 11, each cell represents a seat S. A diagonal cell indicates a reserved seat S, a dot indicates a seat occupied by a user, and a blank cell indicates an unreserved seat S. That is, a user seated in a dotted cell has already completed the seating confirmation process described above, while a user seated in a diagonal cell has not completed the seating confirmation process described above. Note that each cell may be identified by a different color. For example, diagonal cells may be filled with yellow, dotted cells with green, and blank cells with no color.

[0089] The conductor should perform a ticket check on users seated in reserved seats S according to the indicated display. In this case, the user seated in the reserved seat should indicate that they have not sent boarding completion information or seating information to the server 1 using the user terminal 3. That is, it indicates that the user has forgotten to read the 2D code or that the user terminal 3 is a terminal that cannot read 2D codes. The conductor should perform a ticket check only on users seated in these reserved seats. The ticket check may also be performed by having the boarding confirmation terminal 4 read the 2D code printed on the user's express ticket TC or placed on seat S, and performing the same actions as the seating confirmation procedure described above. Of course, the ticket check may also be performed by the conductor visually confirming the express ticket TC.

[0090] (Effects of the first embodiment) According to the embodiment described above, the user terminal 3 reads the 2D code printed on the express ticket TC or placed on the seat S, accesses the web page specified by the 2D code, and sends predetermined information (boarding completion information or seating information) to the server 1. This allows the conductor to confirm that the user is indeed seated in the reserved seat S without having to perform a ticket check. This reduces the number of users that the conductor needs to check on the express train.

[0091] [Second Embodiment] (composition) Figure 12 is a conceptual diagram showing an example of a ticketing system and a seat confirmation system in the second embodiment. The second embodiment describes a case where a user who has issued an express train ticket (TC) online confirms their seat.

[0092] In the second embodiment, the user terminal 3 and the server 1 communicate, and the user purchases a ticketless express train ticket TC. In this case, as described in the first embodiment, it is not possible to print a 2D code on the express train ticket TC. Therefore, in the seat confirmation operation, a 2D code placed on the seat S is used.

[0093] Here, the hardware configuration of server 1 and user terminal 3 in the second embodiment is the same as the configuration described with reference to Figure 7, so its description is omitted here.

[0094] Figure 13 is a block diagram showing the software configuration of Server 1 and User Terminal 3 in the second embodiment, in relation to the hardware configuration shown in Figure 7. Server 1 includes, in addition to the information control unit 111 described in the first embodiment, a ticketing control unit 114 and a verification unit 115.

[0095] The ticketing control unit 114 generates express train ticket information based on the express train ticket issuance request. The express train ticket issuance request will be described later. The ticketing control unit 114 then transmits the generated express train ticket information to the user terminal 3. The ticketing control unit 114 may also update the seat information based on the express train ticket information. That is, the ticketing control unit 114 updates the information for the seat S for which the express train ticket TC was issued to change it to reserved, and stores the updated seat information in the seat information storage unit 131. Furthermore, the ticketing control unit 114 transmits the express train ticket information to the user terminal 3.

[0096] The data storage unit 33 of the user terminal 3 includes a ticket information storage unit 332 in addition to the code information storage unit 331 described in the first embodiment. Furthermore, the control unit 31 includes a request generation unit 313 and an express ticket information control unit 314 in addition to the code information acquisition unit 311 and operation control unit 312 described in the first embodiment.

[0097] The ticket information storage unit 332 is used to store the limited express ticket information received from the server 1. Note that the limited express ticket information is information that can be received via email, etc., and it is not necessary to install any special applications on the user terminal 3 and receive it using those applications.

[0098] The verification unit 115 receives personal information and seating information from the user terminal 3. The verification unit 115 uses the personal information to retrieve the seating information stored in the seating information storage unit 131. The verification unit 115 checks whether the seat number included in the seating information matches the seat number included in the seating information. If it is confirmed that the seat numbers are the same, the verification unit 115 transmits the confirmation information to the user terminal 3.

[0099] The request generation unit 313 of the user terminal 3 generates a limited express ticket issuance request. The request generation unit 313 obtains the necessary information from the input unit 351 and generates a limited express ticket issuance request that includes the obtained necessary information. Then, the request generation unit 313 sends the limited express ticket issuance request to the server 1.

[0100] The express ticket information control unit 314 receives express ticket information from server 1 in response to an express ticket issuance request. The express ticket information control unit 314 then stores the received express ticket information in the ticket information storage unit 332.

[0101] (Ticket issuance process) Figure 14 is a sequence diagram showing an example of the ticketing procedure in the ticketing system shown in Figure 11. This sequence of operations is realized when the control unit 11 of server 1 and the control unit 31 of user terminal 3 read and execute the programs stored in the program storage unit 12 and program storage unit 32, respectively.

[0102] First, the user wishes to purchase a limited express ticket TC and enters the necessary information for issuing the limited express ticket TC using the input unit 351 of the user terminal 3. Here, in addition to the necessary information described in the first embodiment, the user may also enter personal information such as an email address, telephone number, or user terminal ID, and credit card information.

[0103] The request generation unit 313 of the user terminal 3 generates a limited express ticket issuance request (step ST301). The request generation unit 313 obtains necessary information from the input unit 251 through the input / output interface 25. Furthermore, the request generation unit 211 generates a limited express ticket issuance request that includes personal information and necessary information.

[0104] The request generation unit 313 transmits a limited express ticket issuance request (step ST302). The request generation unit 313 transmits the generated limited express ticket issuance request to the server 1 via the communication interface 24.

[0105] The information control unit 111 of server 1 updates the seat information (step ST303). The information control unit 111 receives a limited express ticket issuance request from the user terminal 3 via the communication interface 14. The information control unit 111 updates the seat information stored in the seat information storage unit 131 according to the necessary information included in the limited express ticket issuance request. That is, the information control unit 111 changes the available seats S for the train on the date and time included in the necessary information to reserved seats S. Furthermore, the information control unit 111 stores the personal information linked to the reserved seats S in the seat information storage unit 131. The information control unit 111 may also output the limited express ticket issuance request to the ticket issuance control unit 114.

[0106] The ticketing control unit 114 of server 1 generates express train ticket information (step ST304). The ticketing control unit 114 performs payment based on the credit card information, etc., included in the express train ticket issuance request. The ticketing control unit 114 then generates express train ticket information based on the express train ticket issuance request. The express train ticket information may include, for example, ticket information and payment information.

[0107] The ticketing control unit 114 transmits the limited express ticket information to the user terminal 3 (step ST305). The ticketing control unit 114 transmits the generated limited express ticket information to the user terminal 3 via the communication interface 14. For example, the ticketing control unit 114 may transmit the limited express ticket information to the email address included in the limited express ticket issuance request.

[0108] The express ticket information control unit 314 stores the express ticket information in the ticket information storage unit 332 (step ST306). The express ticket information control unit 314 receives the express ticket information through the communication interface 34. The express ticket information control unit 314 then stores the received express ticket information in the ticket information storage unit 332. As mentioned above, the express ticket information can be received via email, so there is no need to install any special applications on the user terminal 3.

[0109] (Seating confirmation action) Figure 15 is a sequence diagram showing an example of the seating confirmation procedure in the seating system shown in Figure 11. This sequence of operations is realized when the control unit 11 of server 1 and the control unit 31 of user terminal 3 read and execute the programs stored in the program storage unit 12 and program storage unit 32, respectively.

[0110] First, this sequence begins when the user boards the reserved express train and arrives at their reserved seat S.

[0111] The code information acquisition unit 311 acquires 2D code information (step ST401). The user sits in the reserved seat S and uses the reader unit 353 of the user terminal 3 to read the 2D code information from the 2D code installed on seat S. The code information acquisition unit 311 receives the read 2D code information from the reader unit 353. The code information acquisition unit 311 may store the 2D code information in the code information storage unit 331. Furthermore, the code information acquisition unit 311 extracts the URL contained in the 2D code information and outputs the URL to the output unit 352. The output unit 352 will then display on the screen that the web page specified by the URL is accessible.

[0112] The operation control unit 312 accesses the specified web page (step ST402). The operation control unit 312 receives a signal from the input unit 351 indicating that the user wishes to access the specified web page. Based on this signal, the operation control unit 312 accesses the specified web page.

[0113] The operation control unit 312 transmits seat information to the server 1 (step ST403). The URL is the unique URL of seat S. Therefore, when the user accesses the web page, the output unit 352 displays information about seat S. Furthermore, the output unit 352 displays a field for entering personal information. The user then enters one of the following personal information: email address, phone number, or user terminal ID. This personal information is the same as the personal information used when purchasing the express ticket TC. After entering the personal information, a button is displayed to confirm that the user is seated in seat S. The user confirms that they are seated in the correct seat S and then touches the button. The operation control unit 312 receives the personal information and seat information indicating that the user touched the displayed button from the input unit 351. The operation control unit 312 transmits the personal information and seating information to the server 1 via the communication interface 34 and the web server that manages the web page.

[0114] The verification unit 115 verifies whether the correct user is seated in seat S based on personal information and seat information (step ST404). The verification unit 115 receives personal information and seating information through the communication interface 14. The verification unit 115 uses the personal information to retrieve the seat information stored in the seat information storage unit 131. That is, the verification unit 115 retrieves the seat information linked to the personal information. Then, it verifies whether the seat number included in the received seating information is the same as the seat number included in the retrieved seat information.

[0115] The confirmation unit 115 transmits confirmation information (step ST405). If it determines that the seat numbers are the same, the confirmation unit 115 transmits the confirmation information to the user terminal 3. The confirmation information may be information indicating that the user is seated in the correct seat S. The user can confirm that they are seated in the correct seat S by the confirmation information displayed on the output unit 352 of the user terminal 3.

[0116] If it is determined that the seat number indicated in the seat information is not the same as the seat number included in the acquired seat information, the confirmation information may send mismatch information to the user terminal 3. The mismatch information may indicate that the user is sitting in the wrong seat S. The mismatch information may also include the correct seat number. The user can recognize that they are sitting in the wrong seat S by the mismatch information displayed on the output unit 352 of the user terminal 3 and move to the correct seat S.

[0117] Since the ticket inspection procedure is the same as in the first embodiment, we will omit the explanation here.

[0118] (Effects of the second embodiment) According to the second embodiment described above, a user who has purchased an online ticket scans a 2D code placed on seat S with a user terminal 3, accesses the web page specified by the 2D code, and sends predetermined information (personal information and seating information) to server 1. This allows the conductor to confirm that the user is indeed seated in the reserved seat S without having to perform a ticket check. This reduces the number of users that the conductor needs to check on an express train.

[0119] [Other embodiments] This invention is not limited to the embodiments described above. For example, when a user purchases an express ticket TC online, Server 1 may send a URL to access a specified web page along with the express ticket information. The user may access the web page specified by the URL and enter seat information and personal information.

[0120] In short, this invention is not limited to the embodiments described above, and can be modified in various ways during implementation without departing from its essence. Furthermore, each embodiment may be combined as appropriately as possible, and in that case, the combined effects can be obtained. Moreover, the embodiments described above include inventions at various stages, and various inventions can be extracted by appropriate combinations of the multiple constituent elements disclosed. [Explanation of symbols]

[0121] 1…Server 11…Control Unit 111... Information Control Unit 112...URL generation section 113... Passenger Information Control Unit 114... Ticketing Control Unit 115...Verification section 12…Program memory 13…Data storage unit 131...Seat information storage unit 14…Communication Interface 15… Input / Output Interface 151...Input section 152…Output section 2…Ticket machine 21... Control Unit 211...Request generation section 212...2D code generation unit 213... Ticketing Control Unit 22...Program memory unit 23...Data storage unit 231...Acquired information storage unit 24…Communication Interface 25… Input / Output Interface 251...Input section 252…Output section 253... Ticketing Department 3…User terminal 31…Control Unit 311... Code information acquisition unit 312... Operation Control Unit 313...Request generation section 314... Express Ticket Information Control Unit 32…Program memory unit 33...Data storage unit 331... Code information storage unit 332…Ticket information storage unit 34…Communication Interface 35… Input / Output Interface 351...Input section 352…Output section 353...Reading section 4… Passenger confirmation terminal

Claims

1. A seat confirmation system comprising a server, wherein the server is From a user terminal that accessed a second web page specified by a URL contained in the second two-dimensional code information obtained from a second two-dimensional code printed on the limited express ticket, boarding completion information is received indicating that the train displayed on the second web page matches the train on the limited express ticket. The user terminal accesses a first web page specified by a URL contained in first two-dimensional code information obtained from a two-dimensional code installed on a seat in a vehicle, and in response to the confirmation input of sitting in the seat, the system receives seating information including the seat number of the seat. The receiving unit and A storage unit that stores seat information indicating whether the aforementioned seat is reserved, Based on the boarding completion information, the seat information is updated. If the seat number included in the seating information is reserved, the passenger information control unit updates the seating information to include information indicating that the user has taken a seat, only if the seating information has been updated based on the boarding completion information, and stores the updated seating information in the storage unit. A seating confirmation system equipped with this feature.

2. The server controls the second web page to not display or enable a button for confirming that the train matches the train on the express ticket, based on the timetable, until the time the train arrives at the station where the user is boarding. The seating confirmation system according to claim 1.

3. The seat confirmation system according to claim 1, wherein the passenger information control unit periodically or upon request transmits the seat information to the passenger confirmation terminal.

4. The passenger information control unit transmits the seat information to a passenger confirmation terminal based on the timetable or in accordance with the conductor's instructions, and the passenger confirmation terminal displays whether each seat in the vehicle is reserved, occupied, or not reserved based on the seat information. The seating confirmation system according to claim 1.

5. The server further comprises an information control unit that receives a limited express ticket issuance request, and a URL generation unit that generates URL information for accessing the second web page based on the limited express ticket issuance request, wherein the information control unit updates the seat information to reserve the seat specified in the limited express ticket issuance request, and transmits a limited express ticket issuance response that includes the URL information and information indicating that it is OK to issue the limited express ticket. The seating confirmation system according to any one of claims 1 to 4.

6. The aforementioned seat confirmation system further includes a ticket issuing machine, The ticketing machine includes a request generation unit that generates the request for issuance of the express ticket, A two-dimensional code generation unit generates a two-dimensional code based on the URL information included in the express ticket issuance response, A ticketing control unit that issues the express ticket based on the express ticket issuance request and the two-dimensional code, The seating confirmation system according to claim 5, comprising:

7. The receiving unit receives personal information related to the user along with the seating information, and the seating information is linked to the personal information. The seating confirmation system according to claim 1, further comprising a confirmation unit that determines whether the seat number included in the seating information is the same as the seat number indicated by the seating information linked to the personal information, and if it determines that the seat numbers are the same, transmits confirmation information to the user terminal.

8. Receiving boarding completion information from a user terminal that has accessed a second web page specified by a URL contained in the second two-dimensional code information obtained from a second two-dimensional code printed on a limited express ticket, indicating that it has been confirmed that the train displayed on the second web page matches the train on the limited express ticket, The system receives seating information, including the seat number of the seat, from the user terminal that accessed the first web page specified by the URL contained in the first two-dimensional code information obtained from the two-dimensional code installed on the seat of the vehicle, in response to the confirmation input of sitting in the seat. The system stores seat information indicating whether the aforementioned seat is reserved, The seat information is updated based on the boarding completion information, If the seat number included in the seating information is already reserved, the seating information will be updated to include information indicating that the user has taken up a seat, only if the seating information has been updated based on the boarding completion information. The updated seat information is stored, A seating confirmation program comprising instructions for execution by a processor in a seating confirmation system.

Images