Information management system, information management apparatus, information management method, and program

Abstract

An information management device (100) comprises: an issuing unit (102) that issues at least one token for each mobile body; an allocation unit (104) that allocates a token for a mobile body to a passenger when detecting that the passenger has boarded the mobile body; a cancellation unit (106) that cancels the allocation of the token to that passenger when detecting that the passenger has alighted from the mobile body; and a specification unit (108) that uses token history information indicating the token allocation and cancellation history and specifies the mobile body boarding history of the passenger.

Description

Technical Field

[0001] The present invention relates to an information management system, an information management device, an information management method, and a program, and particularly relates to an information management system, an information management device, an information management method, and a program for managing tokens issued for each moving body.

Background Art

[0002] In recent years, the use of digital ticket services has become widespread in various scenarios. Patent Document 1 describes a system that packages digital tickets related to services provided by different providers and offers them to users.

[0003] Patent Document 2 describes a system that issues transaction information for using transportation facilities or facilities as tokens, writes the information to a blockchain, and displays the transaction information on the user's mobile terminal.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Patent Document 2

Summary of the Invention

Problems to be Solved by the Invention

[0005] In the technologies described in the above patent documents, tickets for using transportation public facilities etc. are digitized to issue tokens, which are registered on the user's mobile terminal for use. However, all of the documents simply issue tickets for train tickets, reserved seats, or facility use. None of the documents have the idea of assigning tokens to the physical space of a moving body as an asset and issuing them to users.

[0006] In recent years, as a measure against infectious diseases and the like, alleviating overcrowding in public transportation during commuting hours and the like has become an urgent issue. In order to solve this problem, it is desired to be able to grasp and manage the boarding and alighting situations of current passengers of moving bodies.

[0007] The present invention has been made in view of the above circumstances, and an object thereof is to provide a technique for efficiently managing the boarding and alighting situations of passengers of a moving body.

Means for Solving the Problem

[0008] In each aspect of the present invention, in order to solve the above-described problems, the following configurations are respectively adopted.

[0009] The first aspect relates to an information management device. The information management device according to the first aspect has issuing means for issuing at least one token for each moving body, assignment means for assigning the token of the moving body to the passenger when it is detected that the passenger has boarded the moving body, release means for releasing the assignment of the token to the passenger when it is detected that the passenger has alighted from the moving body, and specifying means for specifying the boarding history of the passenger on the moving body using token history information indicating the history of assignment and release of the token.

[0010] The second aspect relates to an information management method executed by at least one computer. The information management method according to the second aspect is such that the information management device issues at least one token for each moving body, assigns the token of the moving body to the passenger when it is detected that the passenger has boarded the moving body, releases the assignment of the token to the passenger when it is detected that the passenger has alighted from the moving body, Identifying the boarding history of the passenger on the moving body by using token history information indicating the history of allocation and release of the tokens, including this.

[0011] In addition, as another aspect of the present invention, it may be a program for causing at least one computer to execute the method of the second aspect, or it may be a computer-readable recording medium recording such a program. This recording medium includes a non-temporary tangible medium. This computer program includes computer program code for causing a computer to implement the information management method when executed by the computer.

[0012] Note that any combination of the above components, and those obtained by converting the expression of the present invention among a method, an apparatus, a system, a recording medium, a computer program, etc. are also effective as aspects of the present invention.

[0013] In addition, the various components of the present invention do not necessarily have to exist independently of each other. It is also possible that a plurality of components are formed as one member, one component is formed of a plurality of members, a certain component is a part of another component, and a part of a certain component overlaps with a part of another component, etc.

[0014] In addition, although a plurality of procedures are described in order in the method and computer program of the present invention, the order of description does not limit the order of execution of the plurality of procedures. Therefore, when implementing the method and computer program of the present invention, the order of the plurality of procedures can be changed within a range that does not cause any problem in content.

[0015] Furthermore, the plurality of procedures of the method and computer program of the present invention are not limited to being executed at different timings individually. Therefore, it is also possible that another procedure occurs during the execution of a certain procedure, and a part or all of the execution timing of a certain procedure overlaps with the execution timing of another procedure, etc.

Advantages of the Invention

[0016] According to each of the above side surfaces, it is possible to provide a technique for efficiently managing the boarding and alighting status of passengers on a moving body.

Brief Description of the Drawings

[0017]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Modes for Carrying Out the Invention

[0018] Hereinafter, embodiments of the present invention will be described with reference to the drawings. In all the drawings, the same components are denoted by the same reference numerals, and the description will be omitted as appropriate. Also, in each of the following figures, the configuration of parts not related to the essence of the present invention is omitted and not shown.

[0019] In the embodiment, "acquisition" includes at least one of the following: the active acquisition in which the own device goes to obtain data or information stored in another device or storage medium, and the passive acquisition in which the own device receives data or information output from another device. Examples of active acquisition include sending a request or inquiry to another device and receiving a reply, and accessing and reading from another device or storage medium. Examples of passive acquisition include receiving information distributed (or transmitted, push-notified, etc.). Further, "acquisition" may be to select and acquire from the received data or information, or to select and receive the distributed data or information.

[0020] (First Embodiment) <System Overview> FIG. 1 is a diagram for explaining an information management system 1 according to an embodiment of the present invention. The information management system 1 manages the boarding and alighting information of passengers on a moving body using a token 80. In the example of FIG. 1, the boarding history of passengers on a railway is managed. The information management system 1 includes a plurality of nodes 20 (20A and 20B in FIG. 1) on a blockchain network 10 and an information management device 100 that manages the plurality of nodes 20.

[0021] At least one token 80 is issued for a moving body. In the example of a railway, a plurality of tokens 80 are issued for each vehicle of a train. For example, when the capacity is determined for each vehicle, the number of issued tokens 80 may be limited to a number corresponding to this capacity. When a passenger boards a train, one token 80 is assigned to the passenger. The token 80 does not refer to a so-called electronic ticket, but assigns a space in the vehicle to the passenger. When the token 80 is assigned to a passenger, the space in the vehicle corresponding to the token 80 is assigned to the passenger.

[0022] The information management system 1 Multiply information regarding the boarding and alighting of passengers on a moving body The token 80 recorded with to the nodes 20 Store it for management.

[0023] User U, who is a passenger, installs in advance on the user terminal 30, for example, an application (hereinafter also referred to as "wallet 40") in which the electronic payment means used for paying the railway fare is registered, and registers the electronic payment means in advance so that it can be used.

[0024] Then, when using the railway, user U selects in advance on wallet 40 of the user terminal 30 the electronic payment means to be used for paying the fare, and then holds the user terminal 30 up to the automatic ticket gate 60 to enter. When the entry of user U is detected, a token 80 is assigned to user U, and for example, the token 80 is registered in wallet 40.

[0025] The token 80 is, for example, an NFT (Non-Fungible Token). The entry record of user U is transmitted to the information management device 100 and recorded, for example, in the token 80 stored in the node 20 on the blockchain network 10. The blockchain network 10 includes a plurality of nodes 20.

[0026] The boarding of the passenger on the moving body can be detected, for example, by the entry record at the automatic ticket gate 60. Also, the alighting of the passenger from the moving body can be detected, for example, by the exit record at the automatic ticket gate 60. In this way, the information management device 100 can obtain information indicating the boarding and alighting of the passenger from the automatic ticket gate 60. Further, as another method, the information management device 100 may obtain it from the usage information of the electronic payment means used for paying the fare on the wallet 40. Alternatively, a sensor may be installed in the vehicle 50 to detect the boarding and alighting of the passenger on the vehicle 50. Details will be described in the second embodiment described later.

[0027] As shown in FIG. 1, for example, a plurality of issued tokens 80 are stored in the waiting token pool 20A before being assigned to passengers. When the boarding of user U is detected, for example, the token 80 is registered in the wallet 40 of the user terminal 30 of user U (shown as "token purchase" in the figure), and the token 80 assigned to user U moves to the boarding token pool 20B. When the alighting of user U is detected, the token 80 assigned to user U is returned from the boarding token pool 20B to the waiting token pool 20A, and the token 80 registered in the wallet 40 of the user terminal 30 of user U is deleted (shown as "token return" in the figure).

[0028] However, FIG. 1 schematically shows the allocation and cancellation of token 80 by replacing it with the concept of the movement of token 80, and token 80 does not actually move between the waiting token pool 20A and the boarding token pool 20B. In reality, the usage information (information indicating boarding and alighting) of each token 80 is recorded in the node 20 of the blockchain network 10 each time. For each token 80, information indicating the user U to whom the token 80 is assigned and information on the date and time when the token 80 is assigned to user U are recorded.

[0029] <Hardware Configuration Example> The plurality of nodes 20 and the information management device 100 that constitute the information management system 1 are each realized by at least one computer. Also, the user terminal 30 of user U is a smartphone, a tablet terminal, a wearable terminal, etc., and these are also realized by a computer.

[0030] FIG. 2 is a block diagram illustrating the hardware configuration of each computer 1000 that constitutes the information management system 1 shown in FIG. 1.

[0031] Computer 1000 has a bus 1010, a processor 1020, a memory 1030, a storage device 1040, an input / output interface 1050, and a network interface 1060.

[0032] Bus 1010 is a data transmission path for the processor 1020, the memory 1030, the storage device 1040, the input / output interface 1050, and the network interface 1060 to transmit and receive data to and from each other. However, the method of connecting the processor 1020 and the like to each other is not limited to bus connection.

[0033] Processor 1020 is a processor implemented by a CPU (Central Processing Unit), a GPU (Graphics Processing Unit), or the like.

[0034] Memory 1030 is a main storage device implemented by a RAM (Random Access Memory) or the like.

[0035] Storage device 1040 is an auxiliary storage device implemented by an HDD (Hard Disk Drive), an SSD (Solid State Drive), a memory card, or a ROM (Read Only Memory). Storage device 1040 stores program modules that implement each function of information management device 100 of information management system 1 (for example, issue unit 102, allocation unit 104, release unit 106, and identification unit 108 shown in FIG. 3 described later, and settlement processing unit 120 shown in FIG. 9). When processor 1020 reads and executes these program modules onto memory 1030, each function corresponding to the program module is realized. Also, storage device 1040 functions as storage means (not shown) for storing various information used by information management device 100. Also, the storage means of node 20 may also be realized by storage device 1040.

[0036] The program module may be recorded on a recording medium. The recording medium for recording the program module includes a non-transitory tangible medium that can be used by the computer 1000, and program code readable by the computer 1000 (processor 1020) may be embedded in the medium.

[0037] The input / output interface 1050 is an interface for connecting the computer 1000 and various input / output devices.

[0038] The network interface 1060 is an interface for connecting the computer 1000 to a communication network. This communication network is, for example, a LAN (Local Area Network) or a WAN (Wide Area Network). The method by which the network interface 1060 connects to the communication network may be a wireless connection or a wired connection. However, the network interface 1060 may not be used.

[0039] And the computer 1000 is connected to necessary devices (for example, the automatic ticket gate 60, various sensors (not shown) mounted on the moving body, etc.) via the input / output interface 1050 or the network interface 1060.

[0040] The information management system 1 may be realized by a plurality of computers 1000 constituting the information management device 100 and the node 20.

[0041] Each component of the information management device 100 of the present embodiment shown in FIG. 3 to be described later is realized by an arbitrary combination of the hardware and software of the computer 1000 in FIG. 2. And it is understood by those skilled in the art that there are various modifications to the realization method and the device. The functional block diagram showing the information management device 100 of each embodiment shows blocks of logical function units, not the configuration in terms of hardware units.

[0042] <Functional configuration example> FIG. 3 is a functional block diagram logically showing the configuration of the information management apparatus 100 of the present embodiment. The information management apparatus 100 includes an issuance unit 102, an allocation unit 104, a release unit 106, and an identification unit 108. The issuance unit 102 issues at least one token 80 for each moving body. When the allocation unit 104 detects that a passenger has boarded a moving body, it allocates the token 80 of the moving body to the passenger. When the release unit 106 detects that a passenger has alighted from a moving body, it releases the allocation of the token 80 to the passenger. The identification unit 108 identifies the boarding history of a passenger on a moving body using token history information indicating the history of allocation and release of the token 80.

[0043] The moving body includes vehicles of public transportation such as railways, streetcars (tracks), buses, taxis, airplanes, and ships. The moving body further in may be a vehicle in an amusement park or the like. Further, the moving body may be a vehicle such as a rental car and a rental bike. That is, the moving body is not particularly limited as long as a passenger pays a price and temporarily occupies the space and carries the passenger to move. In the present embodiment, the moving body will be described by taking a railway as an example.

[0044] At least one token 80 is issued for each moving body. For example, for a taxi, a rental bike, etc., one token 80 may be issued for one moving body. For railways, streetcars, buses, airplanes, ships, etc., a plurality of tokens 80 are issued for one moving body.

[0045] The moving body may have a plurality of vehicles. For example, it is exemplified by a railway or the like. The issuing unit 102 may issue a plurality of tokens 80 for each vehicle. The number of tokens 80 issued may be limited to a number corresponding to the capacity. Even for the same train, the number of tokens 80 issued may vary depending on the vehicle. Alternatively, the number of tokens 80 issued may vary depending on the time period. The number of tokens issued may be set in advance or may not be set. The issuing unit 102 may issue tokens 80 in predetermined quantities. For example, the issuing unit 102 may issue an additional predetermined number of tokens when all the issued tokens 80 have been assigned.

[0046] The information management device 100 may have a reception unit (not shown) that receives the setting of the number of tokens 80 issued. The reception unit receives the specification of the unit of issuance (by train, by vehicle, by time period, etc.) and the number of tokens issued.

[0047] FIG. 4 is a diagram schematically showing a plurality of tokens 80 issued for one vehicle. For example, in the case of a railway, a plurality of tokens 80 are issued for each train and for each vehicle. For example, identification information (hereinafter also referred to as "token ID") may be assigned to the tokens 80. The issuing unit 102 manages the tokens 80 by associating the token IDs of the issued tokens 80 with each train or each vehicle and storing them in the storage device 1040 as issued token information 202. For example, the issued token information 202 stores the train ID, the vehicle ID, and the token ID in association with each other. That is, the specifying unit 108 can specify the train or vehicle to which the token 80 has been assigned from the token ID.

[0048] The number of tokens 80 issued to the moving body is preferably equal to or greater than the number of people expected to board the moving body. Also, when all the tokens 80 issued to the moving body have been assigned to passengers, the issuing unit 102 may further issue additional tokens 80 for the moving body.

[0049] The larger the number of tokens 80 assigned to passengers, the larger the number of passengers riding on the moving body. That is, the moving body is likely to be crowded. Conversely, the larger the number of tokens 80 not assigned to passengers, the smaller the number of passengers riding on the moving body. That is, the moving body is likely to be empty.

[0050] When using the railway, user U selects in advance, on the wallet 40 of the user terminal 30, the electronic payment means to be used for paying the fare, and then holds the user terminal 30 up to the automatic ticket gate 60 to enter. The automatic ticket gate 60 may acquire the identification information of user U who has entered from the user terminal 30.

[0051] The identification information of user U may be, for example, the user identification information for registering the use of wallet 40, or the user identification information for registering the use of the electronic payment means, and is not particularly limited. However, it is assumed that the acquisition of the identification information of user U has obtained the prior consent of user U.

[0052] At this time, the allocation unit 104 records the identification information of user U that the issuance unit 102 has acquired from the automatic ticket gate 60, or the user ID assigned separately from the acquired identification information of user U, on the token 80. The recording on the token 80 is stored in any node 20 on the blockchain network 10.

[0053] FIG. 5 is a diagram showing an example of the data structure of the token 80. The token 80 includes a token ID, information indicating the date and time when boarding was detected, identification information of user U who boarded, information indicating the date and time when alighting was detected, and identification information of user U who alighted. When the token 80 moves from the waiting token pool 20A for use in FIG. 1 to the boarding token pool 20B, the boarding date and time and the user ID are recorded on the token 80. When moving from the boarding token pool 20B to the waiting token pool 20A for use, the alighting date and time and the user ID are recorded on the token 80.

[0054] That is, when user U boards the moving body and the allocation unit 104 allocates token 80 to user U, the user ID of the user and the boarding date and time are recorded in token 80. Further, when user U gets off the vehicle, the getting-off date and time and the user ID are recorded in token 80 by the release unit 106, and the allocation of token 80 to user U is released.

[0055] In the case where only the user ID and the boarding date and time are recorded in token 80, it can be determined that user U is on the moving body and has not yet been detected as having gotten off.

[0056] After token 80 is returned, it can be allocated to another user U who uses the moving body. When the next user U boards the moving body and token 80 is allocated to the next user U by the allocation unit 104, the user ID of the user and the boarding date and time are recorded in token 80. Further, when user U gets off the vehicle, the getting-off date and time and the user ID are recorded in token 80 by the release unit 106.

[0057] In this way, the boarding and alighting records of multiple users U are accumulated in token 80.

[0058] That is, the specifying unit 108 can specify the boarding history of the passenger on the moving body by using the token history information associated with the past token 8 0's boarding history.

[0059] Figure 6 shows a state in which information on token 80 allocated to each user U is recorded in a plurality of nodes 20.

[0060] As described above, the token ID of the token 80 assigned to a passenger, the boarding date and time or the disembarking date and time, and the user ID are recorded and accumulated in each node 20 of the blockchain network 10. The boarding record and disembarking record of a passenger may be recorded separately in different nodes 20. The allocation and release records of the tokens 80 recorded in a distributed manner in multiple nodes 20, that is, the boarding and disembarking records of passengers, are managed in an integrated manner by the information management device 100. Therefore, the identification unit 108 can identify the usage history of each token 80 or the boarding and disembarking history of each passenger.

[0061] In this embodiment, since the history of the token 80 can be recorded on the blockchain network 10, even if the information is for different means of transportation, such as railroads and airplanes, it is possible to collectively manage the information in the information management system 1 by introducing the mechanism of the information management system 1. For example, it is possible to manage the riding status of moving objects across different means of transportation. Therefore, in specifying fares according to the riding history described in the third embodiment described later, it is possible to plan a tie-up campaign between railroads and airplanes, and to apply discount fares to the use of a specified railroad and a specified airplane.

[0062] Note that information recorded in association with the token 80 may be other than the example shown in FIG. 5. For example, information indicating the train or car in which the passenger boarded may be linked to the token 80. Furthermore, information indicating the boarding station and the disembarking station obtained from the automated ticket gate 60 through which the passenger entered and exited may be linked to the token 80 and recorded.

[0063] <Example of operation> FIG. 7 is a flowchart showing an example of the operation of the information management system 1 of this embodiment. First, the issuing unit 102 issues at least one token 80 for each moving body (step S101). In the example of a railway, as shown in FIG. 4, a plurality of tokens 80 are issued for each train or each vehicle. The issuing unit 102 stores, in the storage device 1040, the plurality of tokens 80 issued for each train or each vehicle, as issued token information 202, after associating them.

[0064] Then, when the allocation unit 104 detects that a passenger has boarded a moving body (YES in step S103), it allocates the token 80 of the moving body to the passenger (step S105). Specifically, when it is detected that the user U has boarded when entering the automatic ticket gate 60, the allocation unit 104 registers the token 80 in the wallet 40 of the user terminal 30 of the user U. Further, the allocation unit 104 acquires the identification information (user ID) of the user U who has entered the automatic ticket gate 60, and records, in the node 20, the token ID of the token 80, the date and time information, and the user ID in association with each other.

[0065] Then, when the cancellation unit 106 detects that a passenger has alighted from a moving body (YES in step S107), it cancels the allocation of the token 80 to the passenger (step S109). Specifically, when it is detected that the user U has alighted when leaving the automatic ticket gate 60, the cancellation unit 106 cancels the token 80 registered in the wallet 40 of the user terminal 30 of the user U. Further, the cancellation unit 106 acquires the identification information (user ID) of the user U who has left the automatic ticket gate 60, and records, in the node 20, the token ID of the token 80, the date and time information, and the user ID in association with each other.

[0066] Then, the specifying unit 108 specifies the boarding history of a passenger on a moving body, using token history information indicating the history of allocation and cancellation of the token 80 (step S111). Specifically, the specifying unit 108 aggregates the records of each token 80 recorded in a distributed manner in a plurality of nodes 20, and can specify the boarding history of the user U on the moving body, for example, by extracting for each user U.

[0067] In addition, the specific unit 108 can also identify the situation of the number of passengers in the train or vehicle by extracting the token history information for each train or vehicle of the moving body.

[0068] Note that the flowchart of FIG. 7 includes four processes, namely, the issuance process of the token 80 (step S101), the process when a passenger boards the vehicle (steps S103 to S105), the process when a passenger alights from the vehicle (steps S107 to S109), and the boarding history identification process (step S111). Although FIG. 7 shows the four processes as being executed in order for explanatory purposes, each process can be executed individually and does not necessarily need to be executed in order as in the flowchart of FIG. 7.

[0069] As described above, in the present embodiment, the issuing unit 102 issues at least one token 80 to the moving body, and the allocating unit 104 allocates the token 80 of the moving body to the passenger when it detects that the passenger has boarded the moving body. Then, the releasing unit 106 releases the allocation of the token 80 to the passenger when it detects that the passenger has alighted from the moving body, and the specific unit 108 identifies the boarding history of the passenger on the moving body using the token history information indicating the history of allocation and release of the token 80.

[0070] In this way, according to the present embodiment, by allocating the token 80 to the passenger and recording it on the token 80, it becomes possible to efficiently collect and manage the boarding records of the passengers.

[0071] (Second Embodiment) In the present embodiment, it is the same as the above embodiment except that it has a configuration for identifying the vehicle on which the passenger has boarded. Since the information management device 100 has the same configuration as the above embodiment, it will be described using the functional block diagram of FIG. 3.

[0072] The specific unit 108 identifies the vehicle on which the passenger has boarded using the token history information of the token 80.

[0073] A method for identifying the vehicle in which a passenger has boarded can, for example, use a check-in detection technology for a general predetermined area. Examples are shown below, but are not limited thereto. (1) Detect communication with a wireless communication device installed in the vehicle using a short-range wireless communication function such as Bluetooth (registered trademark) of the passenger's user terminal 30. (2) Detect communication with an access point of a wireless LAN installed in the vehicle using a wireless communication function such as a wireless LAN (Local Area Network) of the passenger's user terminal 30. (3) Receive a predetermined sound wave output from a sound wave generator installed in the vehicle with a microphone of the passenger's user terminal 30.

[0074] An application for detecting check-in to a predetermined area by methods such as (1) to (3) is installed and launched on the user terminal 30. By notifying the server from the application of the detection of communication or the reception of sound waves, the server identifies the check-in area of the user terminal 30.

[0075] Furthermore, the following are also exemplified as other examples. (4) Register the biometric information (such as face information) of the passenger in advance, and when the passenger can be identified by comparing the biometric information of the passenger in the captured image using a camera installed inside the vehicle with the registered biometric information, detect which vehicle (identify the vehicle in which the camera that captured the image is installed) the passenger has boarded. Alternatively, the boarding position is identified by tracking the boarding position of the passenger using the captured image of a camera installed in the station building. (5) Use the location registration information with the base station of the mobile phone communication network of the user terminal 30. (6) Use the current position of the user terminal 30 identified by the GPS (Global Positioning System) reception function of the user terminal 30.

[0076] When the allocation unit 104 detects the boarding of user U and allocates the token 80, in addition to the boarding date and time and the user ID, the information indicating the train or vehicle on which user U has boarded is associated with the token ID of the token 80 and recorded in the node 20.

[0077] FIG. 8 is a diagram showing an example of the data structure of the token 80 of the present embodiment. In addition to the information of the token 80 in FIG. 5, the information further includes the information indicating the train or vehicle recorded in association with the token 80. The information indicating the train or vehicle recorded in association with the token 80 may be the identification information (train ID) for identifying the train or the identification information (vehicle ID) for identifying the vehicle.

[0078] Also, when user U moves vehicles during boarding, the allocation unit 104 may detect the change in the position of user U and record the information indicating the vehicle at the destination each time together with the date and time information.

[0079] According to the present embodiment, the specifying unit 108 can specify the vehicle on which the passenger has boarded using the token history information of the token 80 assigned to the passenger. Depending on the position of the vehicle, even if it is the same train, the congestion situation may be different. For example, the vehicles at a specific position of the train may be more congested than other vehicles. By specifying which vehicle user U has boarded, it becomes possible to effectively take measures for congestion alleviation.

[0080] (Third Embodiment) FIG. 9 is a functional block diagram logically showing the configuration of the information management device 100 of the present embodiment. The information management device 100 of the present embodiment is the same as any of the above-described embodiments except that it has a configuration for performing a settlement process using the boarding history of the passengers specified by the specifying unit 108.

[0081] The information management device 100 in FIG. 9 further includes a settlement processing unit 120 in addition to the configuration of the information management device 100 in FIG. 3. The settlement processing unit 120 performs a settlement process of the fare of the passenger using the boarding history of the passenger specified by the specifying unit 108.

[0082] Since the token 80 is issued for each train and further assigned to the passengers who board the train, the passengers who board each train can be identified. That is, the boarding history indicating the train on which the passenger has boarded can be identified. And the boarding situation of the train, for example, the congestion situation can be identified by the number of tokens 80 assigned to the passengers.

[0083] The settlement processing unit 120 identifies the fare of the passenger according to the boarding conditions of the passenger and performs settlement processing using the identified fare.

[0084] For example, by setting the fare of the passengers boarding during the rush hour such as the commuting time zone higher than the fare of the passengers boarding during other time zones, it is expected to promote the alleviation of congestion during the commuting time zone. Therefore, the settlement processing unit 120 changes the fare of the passenger according to the boarding conditions of the passenger.

[0085] The boarding conditions are, for example, at least any one of the time zone, position, and boarding and alighting stations of the train or vehicle on which the passenger has boarded. The boarding conditions may also include the congestion situation of the train or vehicle, or the congestion situation of other trains or vehicles on which the passenger has not boarded.

[0086] The settlement processing unit 120 identifies the fare of the passenger including the discounted fare and the increased fare according to the congestion situation of the train or vehicle on which the passenger has boarded. Since the congestion situation can be identified using the token history information, the settlement processing unit 120 uses the token history information to identify the fare as follows, for example. (1) An increased fare is applied to a train or vehicle in which the number of tokens 80 assigned to the passenger is more than the standard. (2) A discounted fare is applied to a train or vehicle in which the number of tokens 80 not assigned to the passenger is more than the standard.

[0087] The standard is preferably, for example, the number of tokens 80 for achieving the target number of boarders for each train or vehicle.

[0088] In addition, the settlement processing unit 120 may specify the user U fare according to the congestion status of other trains or other vehicles while the user U is on a certain train or vehicle.

[0089] The boarding history includes, for example, the train or vehicle on which the passenger boarded and the boarding time. Further, the boarding conditions may include the boarding and alighting stations. The specifying unit 108 specifies the train or vehicle on which the passenger boarded and the boarding time. In addition, the specifying unit 108 may specify the boarding and alighting stations of the passenger. In this case, the allocating unit 104 and the releasing unit 106 associate and record information indicating the section of the train on which the passenger boarded, for example, the information of the boarding station and the alighting station, with the token 80 assigned to the passenger when boarding the moving body.

[0090] The specifying unit 108 can specify the train or vehicle on which the passenger boarded and the boarding time using the boarding history of the passenger specified from the token history information. Therefore, the specifying unit 108 can also specify the train or vehicle on which the passenger is not boarding and the time period thereof.

[0091] The settlement processing unit 120 may specify the fare as follows, for example, using the token history information indicating the congestion status of other trains or other vehicles while the user U is on board. (1) If there is a train or vehicle in which the number of tokens 80 not assigned to the passenger among the tokens 80 issued to other trains or other vehicles is more than the standard (that is, if other trains or other vehicles are empty), an additional fare is applied to the user U. (2) If there is a train or vehicle in which the number of tokens 80 assigned to the passenger among the tokens 80 issued to other trains or other vehicles is more than the standard (that is, if other trains or other vehicles are congested), a discounted fare is applied to the user U.

[0092] Here too, the standard is preferably, for example, the number of tokens 80 for achieving the target number of passengers set for each other train or other vehicle.

[0093] Also, as described above, since the information management device 100 can collectively manage information on different transportation means, for example, the settlement processing unit 120 can identify the use of a predetermined railway and a predetermined airplane by a passenger from the token history information, and can also perform settlement processing by applying a discounted fare.

[0094] Furthermore, the settlement processing unit 120 may identify the fare of a passenger using the boarding time of the passenger. For example, when congestion is expected during the commuting time zone or near the last train time zone, while it is expected to be empty during the daytime time zone, as shown in FIG. 10, a discount rate or surcharge rate for the fare may be set in advance for each time zone. The settlement processing unit 120 can determine which time zone the boarding time of the passenger is included in and identify the fare of the passenger.

[0095] <Operation Example> FIG. 11 is a flowchart showing an operation example of the settlement processing of the information management device 100 of the present embodiment. First, the settlement processing unit 120 identifies the fare of a passenger according to the boarding conditions of the passenger using the boarding history of the passenger identified from the token history information (step S121). For example, when it is identified from the token history information that the passenger has boarded a train during the commuting time zone, the settlement processing unit 120 identifies that a fare with a 10% surcharge rate is applied to the normal fare. Then, the settlement processing unit 120 performs settlement processing of the passenger's fare using the identified fare (step S123).

[0096] As described above, according to the present embodiment, the settlement processing unit 120 identifies the fare of a passenger according to the boarding conditions of the passenger using the boarding history of the passenger identified from the token history information, and performs settlement processing of the passenger with the identified fare. With this configuration, flexible fare setting becomes possible based on the passenger's riding situation. For example, by setting fares according to time bands, it is expected to promote the alleviation of congestion.

[0097] As described above, the embodiments of the present invention have been described with reference to the drawings, but these are examples of the present invention, and various configurations other than the above can also be adopted. <Treated as a monthly pass or a multiple-ride ticket retrospectively> For example, using the token history information of token 80, the specific part 108 can identify the riding situation of the user U on the train within a predetermined period. Therefore, for example, when it is identified that a specific section has been used for more than the reference number of days or times within three months, the settlement processing unit 120 may perform settlement processing such as calculating the difference between the fare applied when using a monthly pass or a multiple-ride ticket and the fare already paid by the user and refunding the difference. The difference may be Process handled in other ways than refunding, or the fare for subsequent trips may be discounted, or points that can be used for fares may be given to the user U, and it is not particularly limited.

[0098] According to this configuration, it is possible to retrospectively apply the fares of monthly passes or multiple-ride tickets, which is particularly beneficial for the user U. Furthermore, there is an advantage that it can also promote the use of the moving body for the company.

[0099] <Settlement processing during substitute transportation> In the case of an accident or the like causing the suspension of operation of the public transportation or a significant temporary delay, other public transportation may perform substitute transportation. Currently, for passengers who have a monthly pass or the like, a boarding ticket for substitute transportation is distributed, and it becomes possible to use other public transportation.

[0100] For example, by using the token history information of token 80, the specifying unit 108 can specify the user U's riding history, and thereby determine whether the user U has used other public transportation by this transfer transportation. As a result, the settlement processing unit 120 can perform settlement processing by exempting the payment of the fare for using other public transportation by the specified transfer transportation. That is, it becomes possible to automatically perform the fare settlement processing at the time of transfer transportation without going through procedures such as distribution of tickets for transfer transportation.

[0101] Furthermore, even for passengers who are not subject to transfer transportation, by using a detour route, the passengers can contribute to the alleviation of congestion. Therefore, the use of the detour route by the passengers may be detected, and a discounted fare may be applied to the passengers who have used the detour route. Thus, the specifying unit 108 may specify the use of a detour route due to an accident or the like by using the token history information.

[0102] For example, the specifying unit 108 acquires operation information indicating the occurrence of an accident or a significant delay. These operation information may be provided by public transportation at any time, or may be acquired from a web service that provides traffic information. The method of collecting the operation information is not particularly limited, and the specifying unit 108 may collect it regularly, or may receive the operation information provided in a push type from the provider.

[0103] Then, for example, the specifying unit 108 specifies a general route of the riding section of the user U. Then, the specifying unit 108 determines whether the acquired operation information includes information such as a delay related to the specified route. When the operation information includes information such as a delay related to the specified route, and the route actually ridden by the user U is different from the general not route, the specifying unit 108 specifies that the user U has used a detour route. Then, the settlement processing unit 120 may perform settlement processing by applying a discounted fare to the fare for the riding of the user U who has used the detour route.

[0104] According to this configuration, when the operation status is disrupted due to an accident or the like, the riding history of user U can be identified by using the token history information of token 80. Therefore, after determining whether user U has used the replacement transportation, appropriate settlement processing can be performed. Alternatively, since it is also possible to determine whether a detour route has been used, discounted fares can be applied as an incentive to user U who has used the detour route for settlement processing.

[0105] As described above, the present invention has been described with reference to the embodiments and examples. However, the present invention is not limited to the above embodiments and examples. Various changes that can be understood by those skilled in the art can be made to the configuration and details of the present invention within the scope of the present invention. In the present invention, when acquiring and using information regarding the user (user U), it shall be done legally.

[0106] Some or all of the above embodiments can also be described as follows in the appended claims, but are not limited thereto. 1. An information management device comprising: issuing means for issuing at least one token for each moving body; assigning means for assigning the token of the moving body to the passenger when it is detected that the passenger has boarded the moving body; releasing means for releasing the assignment of the token to the passenger when it is detected that the passenger has alighted from the moving body; identifying means for identifying the riding history of the passenger on the moving body by using token history information indicating the history of assignment and release of the token. 2. The information management device according to 1., wherein the moving body is a railway. 3. The information management device according to 1. or 2., wherein the moving body has a plurality of vehicles, and the issuing means issues a plurality of tokens for each vehicle. 4. The information management device according to 2. or 3., The specific means is an information management device that uses the token history information to identify the vehicle in which the passenger has boarded. 5. In the information management device according to any one of 1. to 4., The token is an NFT (Non-Fungible Token), the information management device. 6. In the information management device according to 5., The specific means is an information management device that uses the token history information associated with the boarding history of the past tokens to identify the boarding history of the passenger on the moving body. 7. In the information management device according to any one of 1. to 6., The information management device further includes a settlement processing means for performing a settlement process of the fare of the passenger using the boarding history of the passenger. 8. In the information management device according to 7., The settlement processing means identifies the fare of the passenger according to the boarding conditions of the passenger, and performs the settlement process using the identified fare, the information management device. 9. In the information management device according to 8., The settlement processing means identifies the fare of the passenger using the number of the unassigned tokens while the passenger is boarding, the information management device. 10. In the information management device according to 8. or 9., The moving body has a plurality of vehicles, The settlement processing means identifies the fare of the passenger using the number of the unassigned tokens of the other vehicles while the passenger is boarding, or the information management device. 11. In the information management device according to any one of 8. to 10., The settlement processing means identifies the fare of the passenger using the boarding time of the passenger, the information management device.

[0107] 12. The information management device according to any one of 1. to 11., and An information management system including a plurality of nodes for storing records of information regarding boarding and alighting of passengers on a moving body in a token issued by the information management device.

[0108] 13. The information management device issues at least one token for each moving body, assigns the token of the moving body to the passenger when it is detected that the passenger has boarded the moving body, releases the assignment of the token to the passenger when it is detected that the passenger has alighted from the moving body, An information management method for identifying the boarding history of the passenger on the moving body using token history information indicating the history of assignment and release of the token. 14. In the information management method according to 13., wherein the moving body is a railway, the information management method. 15. In the information management method according to 13. or 14., wherein the moving body has a plurality of vehicles, the information management device issues a plurality of tokens for each vehicle, the information management method. 16. In the information management method according to 14. or 15., the information management device identifies the vehicle on which the passenger has boarded using the token history information, the information management method. 17. In the information management method according to any one of 13. to 16., wherein the token is an NFT (Non-Fungible Token), the information management method. 18. In the information management method according to 17., the information management device identifies the boarding history of the passenger on the moving body using the token history information associated with the past boarding history of the token, the information management method. 19. In the information management method according to any one of 13. to 18., the information management device further An information management method for performing fare settlement processing for a passenger using the passenger's boarding history. 20. In the information management method according to 19., wherein the information management device identifies the fare of the passenger according to the boarding conditions of the passenger, and performs the settlement processing using the identified fare, an information management method. 21. In the information management method according to 20., wherein the information management device identifies the fare of the passenger using the number of unassigned tokens while the passenger is on board, an information management method. 22. In the information management method according to 20. or 21., wherein the moving body has a plurality of vehicles, wherein the information management device identifies the fare of the passenger using the number of unassigned tokens of the other vehicle while the passenger is on board, an information management method. or 23. In the information management method according to any one of 20. to 22., wherein the information management device identifies the fare of the passenger using the boarding time of the passenger, an information management method.

[0109] 24. A program for causing a computer to execute a procedure for issuing at least one token for each moving body, a procedure for assigning the token of the moving body to the passenger when it is detected that the passenger has boarded the moving body, a procedure for canceling the assignment of the token to the passenger when it is detected that the passenger has alighted from the moving body, a procedure for identifying the boarding history of the passenger on the moving body using token history information indicating the history of assignment and cancellation of the token. 25. In the program according to 24., wherein the moving body is a railway, a program. 26. In the program according to 24. or 25., The moving body has a plurality of vehicles, A program for causing a computer to execute a procedure for issuing a plurality of tokens for each vehicle. 27. In the program according to 25. or 26., A program for causing a computer to execute a procedure for identifying the vehicle on which the passenger has boarded using the token history information. 28. In the program according to any one of 24. to 27., The program, wherein the token is an NFT (Non-Fungible Token). 29. In the program according to 28., A program for causing a computer to execute a procedure for identifying the boarding history of the passenger on the moving body using the token history information associated with the past boarding history of the token. 30. In the program according to any one of 24. to 29., A program for further causing a computer to execute a procedure for performing fare settlement processing for the passenger using the boarding history of the passenger. 31. In the program according to 30., A program for causing a computer to execute a procedure for identifying the fare of the passenger according to the boarding conditions of the passenger and performing the settlement processing using the identified fare. 32. In the program according to 31., A program for causing a computer to execute a procedure for identifying the fare of the passenger using the number of unassigned tokens while the passenger is on board. 33. In the program according to 31. or 32., The moving body has a plurality of vehicles, The fare of the passenger is identified using the number of unassigned tokens of the other vehicle while the passenger is on board. or A program for causing a computer to execute a procedure for identifying the fare of the passenger using the number of unassigned tokens of the other vehicle while the passenger is on board. 34. In the program according to any one of 24. to 33., A program for causing a computer to execute a procedure for specifying the fare of a passenger using the boarding time of the passenger.

Explanation of Signs

[0110] 1 Information management system 10 Blockchain network 20 Node 20A Token pool for waiting to use 20B Boarding token pool 30 User terminal 40 Wallet 50 Vehicle 60 Automatic ticket gate 80 Token 100 Information management device 102 Issuing section 104 Allocating section 106 Canceling section 108 Specifying section 120 Settlement processing section 202 Issued token information 1000 Computer 1010 Bus 1020 Processor 1030 Memory 1040 Storage device 1050 Input / output interface 1060 Network interface

Claims

1. Issuing means for issuing a plurality of tokens for each moving body; When it is detected that a passenger has boarded the moving body, the identification information of the passenger is acquired, one token from the plurality of tokens of the moving body is assigned to the passenger, and the passenger's identification information and the boarding date and time of the moving body are associated and recorded in the token; When it is detected that the passenger has alighted from the moving body, the identification information of the passenger is acquired, the assignment of the token to the passenger is cancelled, and the passenger's identification information and the alighting date and time from the moving body are associated and recorded in the token that was assigned to the passenger; Using token history information indicating the boarding and alighting date and time history of the plurality of moving bodies of the passenger recorded in the plurality of tokens associated with the identification information of the passenger, specifying means for specifying a boarding history including information regarding a plurality of boardings and alightings of the passenger associated with the identification information of the passenger to the moving body; Settlement processing means for performing settlement processing of fares for each of the plurality of passengers using the boarding histories of the plurality of passengers; An information management device comprising the above.

2. Issuing means for issuing a plurality of tokens for each moving body; When it is detected that a passenger has boarded the moving body, the identification information of the passenger is acquired, one token from the plurality of tokens of the moving body is assigned to the passenger, and the passenger's identification information and the boarding date and time of the moving body are associated and recorded in the token; When it is detected that the passenger has alighted from the moving body, the identification information of the passenger is acquired, the assignment of the token to the passenger is cancelled, and the passenger's identification information and the alighting date and time from the moving body are associated and recorded in the token that was assigned to the passenger; Using token history information indicating the boarding and alighting date and time history of the plurality of moving bodies of the passenger recorded in the plurality of tokens associated with the identification information of the passenger, specifying means for specifying a boarding history including information regarding a plurality of boardings and alightings of the passenger associated with the identification information of the passenger to the moving body; Settlement processing means for performing settlement processing of fares for each of the plurality of passengers using the boarding histories of the plurality of passengers, comprising: The settlement processing means uses the boarding history and the token history information, If the number of tokens issued to the moving body while the passenger is on board the moving body and not assigned to any passenger exceeds a reference, the fare of the passenger is increased. If the number of tokens assigned to any passenger among the plurality of tokens issued to the moving body while the passenger is on board the moving body exceeds the reference, the fare of the passenger is discounted. An information management device comprising the above.

3. Issuing means for issuing a plurality of tokens for each moving body. When it is detected that a passenger has boarded the moving body, the identification information of the passenger is acquired, one token is assigned to the passenger from among the plurality of tokens of the moving body, and the identification information of the passenger and the boarding date and time on the moving body are associated and recorded on the token. When it is detected that the passenger has alighted from the moving body, the identification information of the passenger is acquired, the assignment of the token to the passenger is cancelled, and the identification information of the passenger and the alighting date and time from the moving body are associated and recorded on the token assigned to the passenger. Using token history information indicating the boarding and alighting date and time history of the plurality of moving bodies of the passenger recorded on the plurality of tokens associated with the identification information of the passenger, specifying means for specifying a boarding history including information on a plurality of boardings and alightings of the passenger to the moving body associated with the identification information of the passenger. Settlement processing means for performing settlement processing of fares for each of the plurality of passengers using the boarding histories of the plurality of passengers. The moving body has a plurality of vehicles. The issuing means issues a plurality of tokens to each of the plurality of vehicles, and further associates and records information indicating the vehicle of the moving body on which the passenger has boarded on the token of the passenger in the token history information. The specifying means specifies the vehicle on which the passenger has boarded using the token history information, and includes the specified vehicle in the boarding history in association with the identification information of the passenger. The settlement processing means uses the boarding history and the token history information. If the number of tokens issued to vehicles other than the vehicle on which the passenger is boarding among the plurality of tokens issued to the moving body while the passenger is on board the moving body and not assigned to any passenger exceeds a reference, the fare of the passenger is increased. An information management device that discounts the fare of a passenger if the number of tokens issued to a vehicle other than the vehicle on which the passenger is riding during the period when the passenger is riding on the moving body is greater than a reference for any of the tokens assigned to the passenger.

4. Issuing means for issuing a plurality of tokens for each moving body; Assignment means that, when it is detected that a passenger has boarded the moving body, acquires the identification information of the passenger, assigns one of the plurality of tokens of the moving body to the passenger, and records the identification information of the passenger and the boarding date and time on the moving body in association with the token; Release means that, when it is detected that the passenger has alighted from the moving body, acquires the identification information of the passenger, releases the assignment of the token to the passenger, and records the identification information of the passenger and the alighting date and time from the moving body in association with the token that had been assigned to the passenger; Specification means for specifying a boarding history including information regarding a plurality of boardings and alightings of the passenger on the moving body associated with the identification information of the passenger, using token history information indicating the history of the boarding date and time and alighting date and time of the plurality of moving bodies of the passenger recorded in the plurality of tokens associated with the identification information of the passenger; Settlement processing means for performing settlement processing for each of the plurality of passengers using the boarding history of the plurality of passengers, comprising: The settlement processing means specifies boarding information regarding the boarding time of the passenger, the boarding position on the moving body, and the station where the passenger boarded and alighted from the moving body using the boarding history, specifies the fare of the passenger according to the boarding information, and performs the settlement processing using the specified fare. An information management device.

5. In the information management device according to any one of Claims 1 to 4, The moving body is a railway. An information management device.

6. In the information management device according to any one of Claims 1 to 5, The specification means specifies the boarding history of the passenger using the token history information, and specifies whether the passenger has used another public transportation means by transfer transportation. The settlement processing means performs settlement processing for the passenger by exempting payment of the fare for using another public transportation means by transfer transportation that has been specified. An information management device.

7. In the information management device according to any one of Claims 1 to 6, The information management device, wherein the token is an NFT (Non-Fungible Token). **Claim 8** The information management device according to any one of claims 1 to 7, and a plurality of nodes that store records of information related to boarding and alighting of a plurality of passengers on a moving body in the token issued by the information management device. An information management system. **Claim 9** The information management device issues a plurality of tokens for each moving body, when it detects that a passenger has boarded the moving body, obtains the identification information of the passenger, assigns one of the plurality of tokens of the moving body to the passenger, and records the identification information of the passenger and the boarding date and time on the moving body in association with the token, when it detects that the passenger has alighted from the moving body, obtains the identification information of the passenger, releases the assignment of the token to the passenger, and records the identification information of the passenger and the alighting date and time from the moving body in association with the token assigned to the passenger, uses token history information indicating the history of the boarding date and time and alighting date and time of the plurality of moving bodies of the passenger recorded in the plurality of tokens associated with the identification information of the passenger to identify a boarding history including information related to a plurality of boardings and alightings of the passenger on the moving body associated with the identification information of the passenger, An information management method for performing fare settlement processing for each of the plurality of passengers using the boarding history of the plurality of passengers. **Claim 10** On a computer, a procedure for issuing a plurality of tokens for each moving body, when it detects that a passenger has boarded the moving body, obtains the identification information of the passenger, assigns one of the plurality of tokens of the moving body to the passenger, and records the identification information of the passenger and the boarding date and time on the moving body in association with the token, when it detects that the passenger has alighted from the moving body, obtains the identification information of the passenger, releases the assignment of the token to the passenger, and records the identification information of the passenger and the alighting date and time from the moving body in association with the token assigned to the passenger, a procedure for identifying a boarding history including information related to a plurality of boardings and alightings of the passenger on the moving body associated with the identification information of the passenger using token history information indicating the history of the boarding date and time and alighting date and time of the plurality of moving bodies of the passenger recorded in the plurality of tokens associated with the identification information of the passenger. A program for executing a procedure of performing fare settlement processing for each of the plurality of passengers using the boarding history regarding the plurality of passengers.

Images