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

Abstract

To provide an information management apparatus which can improve convenience of a digital ticket for both of a user and a business entrepreneur.SOLUTION: The present invention is directed to an information management apparatus including: a ticket issuing unit for issuing a digital ticket for a sales target article in response to ticket issuance request information transmitted from a service server providing a digital ticketing service to transmit ticket issuing information including ticket issuance contents of the issued digital ticket to the service server; and a user right management unit for transmitting use right information including an identification code for use of the digital ticket through the service server to a user portable terminal in response to a use start request transmitted from the service server, and managing the user right of the digital ticket by using the identification code read out from the portable terminal.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] The present disclosure relates to an information management device, an information management system, an information management method, and a program.

Background Art

[0002] In transportation such as trains and buses, the introduction of digital tickets is progressing. In admission management using digital tickets, authentication is performed using identification codes such as barcodes and QR codes (registered trademarks) displayed on the screen of a mobile terminal carried by a user. In admission management using such identification codes, there are cases where a mechanism different from the existing ticket gate system has to be adopted.

[0003] Patent Document 1 discloses an admission management system that performs admission management for a specific area where only authorized persons can enter. In the method of Patent Document 1, the identification information of a transportation IC (Integrated Circuit) card is associated with the identification information of a digital ticket. In the method of Patent Document 1, digitalized admission management is realized using a transportation IC card.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] In the method of Patent Document 1, entry management for a specific area is performed using a transportation IC card. Therefore, according to the method of Patent Document 1, a digital ticket can be realized without displaying an identification code such as a barcode or a QR code (registered trademark) on the screen of the mobile terminal. However, in the method of Patent Document 1, it was difficult for the user to determine whether a digital ticket was being used or the amount deposited in the transportation IC card was being used. Therefore, in the method of Patent Document 1, although intending to use a digital ticket, there was a possibility that the amount deposited in the transportation IC card was used. Also, in the method of Patent Document 1, it was difficult for the operator to determine which of the digital ticket and the transportation IC card the user was using. Therefore, a ticket management method that can improve the convenience of digital tickets is required for both the user and the operator.

[0006] An object of the present disclosure is to provide an information management device, an information management system, an information management method, and a program that can improve the convenience of digital tickets for both the user and the operator.

Means for Solving the Problems

[0007] An information management device according to an aspect of the present disclosure includes an issuance unit that issues a digital ticket for a product to be sold in response to ticket issuance request information transmitted from a service server that provides a digital ticketing service, and transmits issuance information including the issuance details of the issued digital ticket to the service server; and a usage right management unit that, in response to a usage start request transmitted from the service server, transmits usage right information including an identification code for using the digital ticket to the user's mobile terminal via the service server, and manages the usage right of the digital ticket using the identification code read from the mobile terminal.

[0008] In the information management method according to one aspect of the present disclosure, a digital ticket for a product to be sold is issued in response to ticket issuance request information transmitted from a service server that provides a digital ticketing service, and ticket issuance information including the details of the issued digital ticket is transmitted to the service server. In response to a usage start request transmitted from the service server, usage right information including an identification code for using the digital ticket is transmitted to the user's mobile terminal via the service server, and the usage right of the digital ticket is managed using the identification code read from the mobile terminal.

[0009] A program according to one aspect of the present disclosure causes a computer to execute a process of issuing a digital ticket for a product to be sold in response to ticket issuance request information transmitted from a service server that provides a digital ticketing service, a process of transmitting ticket issuance information including the details of the issued digital ticket to the service server, a process of transmitting, in response to a usage start request transmitted from the service server, usage right information including an identification code for using the digital ticket to the user's mobile terminal via the service server, and a process of managing the usage right of the digital ticket using the identification code read from the mobile terminal.

Effect of the Invention

[0010] According to the present disclosure, it becomes possible to provide an information management device, an information management system, an information management method, and a program that can improve the convenience of digital tickets for both users and businesses.

Brief Description of the Drawings

[0011]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

Figure 19

Figure 20

Figure 21

Figure 22

Figure 23

Figure 24

Figure 25

Figure 26

Figure 27

Figure 28

Figure 29

Figure 30

Figure 31

Figure 32

Figure 33

Figure 34

Figure 35

Figure 36

Figure 37

Mode for Carrying Out the Invention

[0012] Hereinafter, embodiments for carrying out the present disclosure will be described with reference to the drawings. In the present disclosure, the drawings used in the description of each embodiment are associated with one or more embodiments. Also, the elements included in each drawing may apply to one or more embodiments. The embodiments described below have technically preferable limitations for carrying out the present disclosure, but do not limit the scope of the disclosure below. In all the drawings used in the description of the following embodiments, the same reference numerals are given to the same parts unless otherwise specified. In the following embodiments, repeated explanations may be omitted for the same configurations and operations.

[0013] (First Embodiment) First, the information management system according to the first embodiment will be described with reference to the drawings. The information management system of this embodiment is composed of a service server and a management server. The service server is a server used to provide a digital ticketing service (hereinafter referred to as the ticketing service). The management server is a server used to issue digital tickets in response to requests from the ticketing service. The digital tickets (hereinafter referred to as tickets) managed by the management server are entrusted for sale to the ticketing service.

[0014] In this embodiment, an example in which tickets are issued by the Account Based Ticketing (ABT) method will be given. The ABT method is a ticketing method in which user information associated with a unique identification number is managed on the cloud server side. In the ABT method, high-speed calculation processing is not required in the reading device of the transportation facility. Therefore, compared with the general digital ticketing method, the digital ticketing method of the ABT method can reduce the introduction cost of the reading device and the like.

[0015] (Configuration) FIG. 1 is a conceptual diagram for explaining the outline of ticket issuance by the information management system according to the present disclosure. In FIG. 1, a base station 14, a service server 15, a management server 16, and a mobile terminal 17 are illustrated as components related to ticket issuance. The information management system is composed of a service server 15 and a management server 16. The management server 16 includes an information management device 10 that manages ticket information.

[0016] The service server 15 and the management server 16 are connected to each other via a network NW such as the Internet. The service server 15 is a server for providing a digital ticketing service. The management server 16 is a server for issuing tickets in response to requests from the ticketing service. The service server 15 and the management server 16 are general server devices. For example, the service server 15 and the management server 16 are constructed in the cloud. The service server 15 and the management server 16 may be realized by stationary terminal devices.

[0017] The merchants using the service server 15 and the management server 16 may be the same or different. For example, the service server 15 is used by a merchant providing a digital ticketing service. For example, the management server 16 is used by a merchant managing ticket products. The number of each of the service server 15 and the management server 16 is not limited to one. For example, the service server 15 may be connected to a plurality of management servers 16. If configured in this way, services provided by a plurality of management servers 16 can be utilized via a single service server 15. For example, the management server 16 may be connected to a plurality of service servers 15. If configured in this way, access can be made to services provided by a single management server 16 from a plurality of service servers 15.

[0018] The base station 14 is a relay device that mediates wireless communication. The base station 14 relays the connection between the mobile terminal 17 and the network NW. For example, the base station 14 is realized by a mobile phone base station, a Wi-Fi (registered trademark) access point, or the like. There are no particular limitations on the base station 14 as long as it can wirelessly connect the mobile terminal 17 and the network NW. Also, as will be described later, the base station 14 relays the connection between a reader (not shown) mounted on a transportation vehicle such as a bus and the network NW. For example, the base station 14 and the reader 18 may be preferentially connected.

[0019] The mobile terminal 17 is a portable communication terminal used by a user. The mobile terminal 17 is connected to the service server 15 via the network NW. Also, the mobile terminal 17 is connected to the management server 16 via the network. For example, the mobile terminal 17 is realized by a communication terminal having a screen capable of displaying an identification code, such as a smartphone or a tablet. The mobile terminal 17 is not particularly limited as long as it is a portable communication terminal having a screen capable of displaying an identification code.

[0020] The mobile terminal 17 transmits an access request to the ticketing service server 15 for providing a ticketing service to the service server 15 in response to an operation by the user. The service server 15 transmits site information for accessing a user interface for using the ticketing service to the mobile terminal 17 which is the source of the access request, in response to the access request transmitted from the mobile terminal 17.

[0021] The mobile terminal 17 acquires the site information transmitted from the service server 15 in response to the access request. The mobile terminal 17 causes a user interface for using the ticketing service included in the site information to be displayed on the screen. The user interface includes an input screen for purchasing tickets provided by the ticketing service. The input screen includes an input portion for items used for ticket issuance. For example, the ticket issuance request information includes a ticket service ID (Identifier), an account ID, a merchant system product code, a start date, an expiration date, an attribute, and the number of people. The mobile terminal 17 accepts an input of items used for ticket issuance via the input screen displayed on the screen. The mobile terminal 17 transmits ticket issuance request information including information regarding items used for ticket issuance to the service server 15.

[0022] The service server 15 acquires ticket issuance request information from the mobile terminal 17. The service server 15 transmits a ticket issuance request included in the ticket issuance request information to the management server 16. The management server 16 acquires the ticket issuance request from the service server 15. The management server 16 generates ticket issuance information corresponding to the issuance request by using the information management device 10. The management server 16 transmits the generated issuance information to the service server 15. The service server 15 transmits the issuance information transmitted from the management server 16 to the mobile terminal 17.

[0023] The mobile terminal 17 acquires ticket information regarding the ticket issued in response to the ticket issuance request information from the service server 15. The mobile terminal 17 stores the acquired ticket information. The ticket information may be stored in a server or database accessible by the mobile terminal 17. As described later, the ticket specified by the ticket information stored in the mobile terminal 17 is activated in response to a ticket use start request.

[0024] FIG. 2 is a conceptual diagram for explaining an outline of the use of a ticket issued by the information management system according to the present disclosure. FIG. 2 illustrates a base station 14, a mobile terminal 17, and a reader 18 as components related to the issuance of a ticket.

[0025] The mobile terminal 17 transmits a ticket use start request in response to an operation of a user who wishes to start using the ticket. The ticket use start request transmitted from the mobile terminal 17 is transmitted to the service server 15. The service server 15 acquires the ticket use start request. The service server 15 transmits the acquired use start request to the management server 16.

[0026] The management server 16 uses the information management device 10 to confirm the validity of the ticket for which a usage start request has been made. The management server 16 transmits the usage right information of the ticket confirmed to be valid to the service server 15. The usage right information includes identification information that is converted into an identification code used for ticket usage. For example, the identification code is a one-dimensional code such as a barcode or a two-dimensional code such as a QR code (registered trademark). The service server 15 acquires the usage right information from the management server 16. The service server 15 transmits the identification code included in the usage right information to the mobile terminal 17.

[0027] The mobile terminal 17 acquires the identification code from the service server 15. The mobile terminal 17 causes the acquired identification code to be displayed on the screen. For example, the mobile terminal 17 causes the identification code to be displayed on the screen in response to an operation by the user. The user holds the screen of the mobile terminal 17 on which the identification code is displayed in front of the camera of the reader 18.

[0028] The reader 18 is a device equipped with a camera capable of reading the identification code. The reader 18 has a wireless communication function. The reader 18 is connected to the management server 16 via the network NW. For example, the function of the reader 18 is realized by an automatic ticket gate used for entrance and exit management to the platform of a station or an in-vehicle device installed in a transportation vehicle such as a bus. The reader 18 transmits the read identification code to the management server 16.

[0029] The management server 16 uses the information management device 10 to determine the validity of the ticket associated with the identification code transmitted from the reader 18. When the time at which the identification code was transmitted is included in the expiration date of the ticket associated with the identification code, the information management device 10 determines that the ticket is valid. On the other hand, when the time at which the identification code was transmitted is not included in the expiration date of the ticket associated with the identification code, the information management device 10 determines that the ticket is invalid. The management server 16 transmits the validity determination result to the reader 18. In addition, the management server 16 transmits a notification indicating that the ticket has been started to be used to the service server 15. For example, the management server 16 executes a ticket expiration determination process, a fare calculation process, a settlement process according to the remaining charge amount, etc. in association with the user's identification information.

[0030] The reader 18 obtains from the management server 16 the determination result regarding the validity of the ticket associated with the read identification code. The reader 18 executes a notification process according to the determination result of the validity of the ticket associated with the identification code. For example, when the ticket is valid, the reader 18 emits a sound indicating that the ticket is valid. For example, when the ticket is invalid, the reader 18 emits a sound indicating that the ticket is invalid. The crew member of the transportation facility can confirm the validity of the ticket used by the user who presented the identification code according to the sound emitted from the reader 18. The reader 18 may notify the validity / invalidity of the ticket by means other than sound. For example, the determination result of the reader 18 may be notified via a display provided together with the reader 18. For example, when the ticket is valid, the reader 18 causes the display to display information indicating that the ticket is valid. For example, when the ticket is invalid, the reader 18 causes the display to display information indicating that the ticket is invalid. The crew member of the transportation facility can confirm the validity of the ticket used by the user who presented the identification code by looking at the information displayed on the display. For example, the reader 18 may notify the validity / invalidity of the ticket by vibration or light. The reader 18 may be configured to notify the validity / invalidity of the ticket by combining sound, vibration, and light.

[0031] For example, the reader 18 may notify the validity of the ticket by controlling the opening and closing of the gate provided at the entrance of the transportation facility. For example, when the ticket is valid, the reader 18 keeps the gate provided at the entrance of the transportation facility open. On the other hand, when the ticket is invalid, the reader 18 keeps the gate provided at the entrance of the transportation facility closed. There is no particular limitation on the opening and closing method and type of the gate. For example, the reader 18 may be realized by the automatic ticket gate provided at the ticket barrier of the station.

[0032] The information management device 10 does not necessarily have to be implemented inside the management server 16. FIG. 3 shows an example in which the information management device 10 is implemented inside the service server 15. In the case of the example in FIG. 3, in ticket issuance, access is made from the service server 15 to the product information registered in the management server 16. Also, in the case of the example in FIG. 3, in ticket use, access is made from the service server 15 to the issuance information registered in the management server 16. The issuance information may be registered in the service server 15. According to the configuration of FIG. 3, on the side of the service server 15, the management of ticket issuance and use can be completed.

[0033] FIG. 4 shows an example in which the information management device 10 is implemented outside the service server 15 and the management server 16. In the case of the example in FIG. 4, in ticket issuance, access is made from the information management device 10 to the product information registered in the management server 16. Also, in the case of the example in FIG. 4, in ticket use, access is made from the information management device 10 to the issuance information registered in the management server 16. The issuance information may be registered in the information management device 10. According to the configuration of FIG. 4, the information management device 10 can manage ticket issuance and use independently of the service server 15 and the management server 16.

[0034] Next, the service server 15 and the management server 16 that constitute the information management system according to the present embodiment will be described with reference to the drawings. The configurations described below are examples of the service server 15 and the management server 16. The configurations of the service server 15 and the management server 16 are not limited to the following configurations.

[0035] 〔Service Server〕 FIG. 5 is a block diagram showing an example of the configuration of a service server according to the present disclosure. The service server 15 includes a reception unit 151, a site information acquisition unit 152, a storage unit 153, a request unit 155, an information acquisition unit 156, a ticket information generation unit 157, a settlement unit 158, and a transmission unit 159. FIG. 5 shows the main information, data, etc. exchanged between the management server 16 and the mobile terminal 17 and the service server 15.

[0036] The reception unit 151 receives an access request transmitted from the mobile terminal 17. The reception unit 151 outputs the received access request to the site information acquisition unit 152. The reception unit 151 also receives ticket issuance request information transmitted from the mobile terminal 17. For example, the ticket issuance request information includes a ticket service ID (Identifier), an account ID, a merchant system product code, a start date, an expiration date, an attribute, and the number of people. The reception unit 151 outputs the received ticket issuance request information to the request unit 155. The reception unit 151 also receives a use start request transmitted from the mobile terminal 17. The reception unit 151 outputs the received use start request to the request unit 155.

[0037] The site information acquisition unit 152 acquires an access request from the reception unit 151. The site information acquisition unit 152 acquires site information for accessing a user interface used in the ticketing service from the storage unit 153 according to the acquired access request. For example, the user interface includes an input screen for purchasing tickets provided by the ticketing service. The input screen includes an input portion for items used for ticket issuance. The site information acquisition unit 152 outputs the acquired site information to the transmission unit 159.

[0038] The storage unit 153 stores site information for accessing a user interface used in the ticketing service. Also, the storage unit 153 stores ticket information regarding tickets to be issued. Also, the storage unit 153 stores issuance information issued by the management server 16. The information stored in the storage unit 153 is not limited to what is listed here.

[0039] FIG. 6 is a table showing an example of ticket information (ticket master 131) stored in the storage unit 153. The ticket master 131 is a table for listing tickets to be sold and storing information regarding those tickets in a database. The ticket master 131 is used to manage basic ticket information repeatedly used in the ticketing system. The ticket master 131 is created by the product design of a vendor providing the ticketing service.

[0040] In the example of FIG. 6, the ticket master 131 includes a ticket code, a product name, a price, and a vendor system product code. The ticket code is an identifier for identifying a ticket. The product name is the name of the service provided by the ticket. The price is the price of the ticket. The vendor system product code is an identifier for collectively managing at least one service included in the ticket. The vendor system product code is an identifier formed by combining a sales vendor code and a product code managed by the management server 16. The ticket master 131 in FIG. 6 is an example and does not limit the ticket information of the present embodiment. The ticket information may include information other than the ticket code, product name, price, and vendor system product code.

[0041] In the example of FIG. 6, the product name of the service identified by the ticket code "AAAAAAAA" is "One-day Pass for ○○ Area + Theme Park Set". The price of the service identified by the ticket code "AAAAAAAA" is "2000 yen". Also, the business operator system product code "XXXXXXXXYYYYYYY2" is associated with the service identified by the ticket code "AAAAAAAA".

[0042] FIG. 7 is a table showing an example of the ticket issuance information (ticket transaction 135) stored in the storage unit 153. The ticket transaction 135 is a table (ticket management table) for storing information regarding tickets issued in the ticketing system in a database. In the example of FIG. 7, the ticket transaction 135 includes a user ID, a ticket code, a business operator system code, and an identification code. The user ID is an identifier indicating the user who purchased the ticket. The ticket code is an identifier indicating the issued ticket. The business operator system product code is an identifier for collectively managing at least one service included in the issued ticket. By using the business operator system product code, the service that can be received by the issued ticket can be uniquely specified. The identification code is a code used as a ticket. For example, the identification code is a one-dimensional code such as a barcode or a two-dimensional code such as a QR code (registered trademark).

[0043] In the example of FIG. 7, the ticket with the ticket code "AAAAAAAA" was purchased by the user with the user ID "ABCDE". The ticket with the ticket code "AAAAAAAA" can be uniquely specified by the business operator system product code "XXXXXXXXYYYYYYY2". Since the ticket transaction 135 in FIG. 7 has not yet started being used, the identification code is blank. The ticket transaction 135 in FIG. 7 is an example and does not limit the ticket issuance information of the present embodiment. The ticket issuance information may include information other than the user ID, the ticket code, the business operator system code, and the identification code.

[0044] FIG. 8 is a table showing an example of activated ticket information (ticket transaction 137) stored in the storage unit 153. The ticket transaction 137 is related to an activated ticket in response to a usage start request by the user. In the example of FIG. 8, the ticket with the ticket code "AAAAAAAA" has been started to be used by the user with the user ID "ABCDE". The ticket with the ticket code "AAAAAAAA" can be uniquely identified by the operator system product code "XXXXXXXXYYYYYYY2". Since the usage of the ticket transaction 137 in FIG. 8 has been started, an identification code is stored. In the ticket transaction 137 of FIG. 8, a two-dimensional code is illustrated as the identification code. Actually, identification information corresponding to the identification code is stored in the ticket transaction 137. The identification code (identification information) is transmitted to the mobile terminal 17 used by the user with the user ID "ABCDE". The ticket transaction 137 in FIG. 8 is an example and does not limit the ticket information of the present embodiment. The activated ticket information may include information other than the user ID, ticket code, operator system code, and identification code.

[0045] The request unit 155 acquires the ticket issuance request information from the reception unit 151. The request unit 155 transmits the ticket issuance request included in the ticket issuance request information to the management server 16. Also, the request unit 155 acquires the usage start request from the reception unit 151. The request unit 155 transmits the acquired usage start request to the management server 16.

[0046] The information acquisition unit 156 receives the ticket information transmitted from the management server 16. The information acquisition unit 156 outputs the received ticket information to the ticket information generation unit 157. Also, the information acquisition unit 156 receives the usage right information transmitted from the management server 16. The information acquisition unit 156 outputs the received usage right information to the ticket information generation unit 157.

[0047] The ticket information generation unit 157 acquires the ticket issuance information from the information acquisition unit 156. The ticket issuance information includes the ticket issuance result, the amount, and the ticket expiration date. The ticket information generation unit 157 generates ticket information according to the acquired ticket issuance information. The ticket information generation unit 157 stores the generated ticket information in the storage unit 153. Also, the ticket information generation unit 157 outputs the ticket issuance information to the transmission unit 159. Furthermore, the ticket information generation unit 157 associates the claim amount included in the ticket issuance information with the account ID and outputs it to the settlement unit 158.

[0048] The ticket information generation unit 157 acquires the usage right information from the information acquisition unit 156. The ticket information generation unit 157 stores the acquired usage right information in the storage unit 153. The ticket information generation unit 157 extracts the identification code included in the usage right information. The ticket information generation unit 157 outputs the identification code extracted from the usage right information to the transmission unit 159.

[0049] The settlement unit 158 transmits the claim amount associated with the account ID from the ticket information generation unit 157 to the settlement agency company associated with the account ID. Details of the ticket settlement are omitted from the description.

[0050] The transmission unit 159 acquires the site information from the site information acquisition unit 152. The transmission unit 159 transmits the acquired site information to the mobile terminal 17 which is the source of the access request. Also, the transmission unit 159 acquires the ticket issuance information from the ticket information generation unit 157. The transmission unit 159 transmits the acquired ticket issuance information to the mobile terminal 17 used by the user of the account ID which is the source of the ticket issuance information. Furthermore, the transmission unit 159 acquires the identification code from the site information acquisition unit 152. The transmission unit 159 transmits the acquired identification code to the mobile terminal 17 used by the user of the account ID associated with the identification code.

[0051] 〔Management Server〕 FIG. 9 is a block diagram showing an example of the configuration of the management server according to the present disclosure. The management server 16 includes an issuance unit 11, a usage right management unit 12, a product information storage unit 160, and an issuance information storage unit 165. The issuance unit 11 and the usage right management unit 12 constitute the information management device 10. FIG. 9 shows the main information, data, etc. exchanged between the management server 16 and the service server 15.

[0052] The issuance unit 11 acquires an issuance request from the service server 15. The issuance unit 11 acquires ticket information corresponding to the acquired issuance request from the product information storage unit 160. The issuance unit 11 generates issuance information corresponding to the issuance request using the acquired ticket information. The issuance unit 11 stores the generated issuance information in the issuance information storage unit 165. The issuance unit 11 transmits the generated issuance information to the service server 15.

[0053] The usage right management unit 12 acquires a usage start request from the service server 15. The usage right management unit 12 acquires issuance information corresponding to the acquired usage start request from the issuance information storage unit 165. The usage right management unit 12 determines the validity of the acquired issuance information.

[0054] If the date and time when the usage start request is issued is earlier than the expiration date and time of the issuance information, the usage right management unit 12 determines that the issuance information is valid. If the issuance information is valid, the usage right management unit 12 sets the identification code expiration date included in the issuance information for which the usage start request is issued. The identification code expiration date is set to the date and time at a point in time after a predetermined period from the point in time when the usage start request is issued. For example, if 24 hours after the usage start request is issued is the predetermined period, the identification code expiration date is set to the date and time 24 hours later. The usage right management unit 12 transmits usage right information including the identification code to the service server 15.

[0055] On the other hand, if the date and time when the usage start request is issued is after the expiration date and time of the issuance information, the usage right management unit 12 determines that the issuance information is invalid. The usage right management unit 12 transmits the determination result that the issuance information is invalid to the service server 15.

[0056] In addition, the usage right management unit 12 acquires an identification code from a reader 18 installed in a transportation facility that the user intends to use. The usage right management unit 12 determines the validity of the ticket issuance information associated with the acquired identification code.

[0057] If the date and time when the identification code was sent is earlier than the date and time of the identification code expiration date of the ticket issuance information, the usage right management unit 12 determines that the identification code is valid. In that case, the usage right management unit 12 transmits a determination result indicating that the identification code is valid to the reader 18 that is the transmission source of the identification code. On the other hand, if the date and time when the identification code was sent is after the date and time of the identification code expiration date of the ticket issuance information, the usage right management unit 12 determines that the identification code is invalid. In that case, the usage right management unit 12 transmits a determination result indicating that the identification code is invalid to the reader 18 that is the transmission source of the identification code.

[0058] The product information storage unit 160 stores a product master. The product master is a list of products to be sold. The product master is a table (product management table) for storing information related to tickets sold in the ticketing system in a database. The product master is created according to the product design by the operator selling the tickets. The product master includes a plurality of products to be sold. For example, the product master includes products to be sold by operators providing transportation facilities such as railways and buses. For example, the operator providing the transportation facility may be an airline or a taxi company. For example, the operator providing the transportation facility may include an operator providing a rental business such as a rental car, a rental bicycle, or a car sharing. For example, the product master includes products to be sold that can use a plurality of transportation facilities. For example, the product master includes products to be sold that can use services provided by a plurality of operators in combination. For example, the product master includes products to be sold that can use transportation facilities in a plurality of target areas.

[0059] For example, the product master is a list that summarizes the sales business operator code, product code, product category, and product name for each product to be sold. The sales business operator code is an identifier for uniquely identifying the sales business operator. The product code is an identifier for uniquely identifying the product. The product category is information indicating the category of the product. The product name is the name of the product identified by the product code. The product master may include information other than the sales business operator code, product code, product category, and product name. The products to be sold included in the product master are associated with the tickets stored in the ticket master stored in the service server 15.

[0060] For example, the product master includes products to be sold that can be used for transportation during a predetermined period. For example, the predetermined period is specified by a time period such as 24 hours or a period such as several days. For example, the product master may include products to be sold in a form that allows the use of transportation for a fixed amount. The fare corresponding to the use of transportation may be settled via a credit card or account linked to the user's account. In this embodiment, an example is shown in which the management server 16 is configured to manage the user account and settlement. The management of the user account and settlement may be configured to be performed by the service server 15.

[0061] FIG. 10 is a table showing an example of a product master (product master 161). The product master 161 is a table that summarizes a list of a sales business operator code, a product code, a product category, and a product name for each product to be sold. For example, the product with the product code "YYYYYYYY1" sold by the operator with the sales business operator code "XXXXXXXX" has the product name "△△ Bus Monthly Pass". The product category of the product with the product code "YYYYYYYY1" is "Monthly". The product category "Monthly" indicates a monthly pass for a predetermined transportation means used for commuting or going to school. Also, the product with the product code "YYYYYYYY2" sold by the operator with the sales business operator code "XXXXXXXX" has the product name "One-Day Bus Ticket". The product category of the product with the product code "YYYYYYYY2" is "D-Day Ticket" (D is a natural number). The product category "D-Day Ticket" indicates a ticket that allows free boarding and alighting on a predetermined transportation means for D days. The product master 161 in FIG. 10 is an example and does not limit the product master of the present embodiment.

[0062] In addition, the product information storage unit 160 stores a sales price master. The sales price master is a list of the prices of the products to be sold. The sales price master is a table (sales price table) for storing information regarding the prices of the products to be sold in a database. The sales price master is created according to the product design by the business operator selling the ticket. The sales price master includes a list of a sales business operator code, a product code, and a price for each ticket product. The sales business operator code is an identifier for uniquely identifying the sales business operator. The product code is an identifier for uniquely identifying the product. The price indicates the price of the product identified by the product code. The sales price of the product to be sold included in the sales price master is linked to the product to be sold included in the product master by the product code.

[0063] FIG. 11 is a table showing an example of a sales price master (sales price master 162). The sales price master 162 is a table that summarizes a list of the sales business operator code, product code, and price for each product to be sold. For example, the price of the product with the product code "YYYYYYYY2" sold by the business operator with the sales business operator code "XXXXXXXX" is "1000 yen". That is, the price of the "one-day bus ticket" included in the product master 161 in FIG. 10 is "1000 yen". The sales price master 162 in FIG. 11 is an example and does not limit the sales price master of the present embodiment. The sales price master may include information other than the sales business operator code, product code, and price.

[0064] The ticket issuance information storage unit 165 stores the held product transaction. The held product transaction is a list of issued products (issued tickets). The held product transaction is a table (held product management table) for listing the issued tickets and storing information about those tickets in a database. The held product transaction is used to manage information about the tickets issued in the ticketing system.

[0065] For example, the held product transaction includes a ticket service ID, an account ID, a business operator code, a product code, an expiration date, and an identification code expiration date. The ticket service ID is an identifier for each issued ticket. The account ID is an identifier for each account of the user who purchased the ticket service. The business operator code is an identifier for the business operator that provides the ticket service. The product code is an identifier for uniquely identifying the product. The expiration date indicates the expiration date of the issued ticket service. The identification code expiration date indicates the expiration date of the ticket service for which use has started. The held product transaction may include information other than the ticket service ID, account ID, business operator code, product code, expiration date, and identification code expiration date.

[0066] Figure 12 is a table showing an example of the held product transaction (held product transaction 166). The held product transaction 166 is a table that summarizes the ticket service ID, account ID, operator code, product code, expiration date, and identification code expiration date for each ticket service. For example, the ticket service with the ticket service ID "99999999" was purchased by a user with the account ID "ABCDE". The ticket service with the ticket service ID "99999999" is a product with the product code "YYYYYYY2" sold by an operator with the operator code "XXXXXXXX". The expiration date of the ticket service with the ticket service ID "99999999" is "March 31, 2024, 24:00:00". The expiration date is not specified up to the time and may be specified by the expiration month or expiration date. In the example of Figure 12, the use of the ticket service has not started. Therefore, the identification code expiration date of the held product transaction 166 is blank. As will be described later, when the use of the ticket service starts, the expiration date of use is added to the identification code expiration date. The held product transaction 166 in Figure 12 is an example and does not limit the held product transaction of the present embodiment.

[0067] In addition, the ticket issuance information storage unit 165 stores the detailed data. The detailed data is a table for listing the detailed information of the purchased ticket services and storing the detailed information of those ticket services in a database. The detailed data is used to manage the detailed information of the ticket services purchased in the ticketing system. The detailed data includes the ticket service ID, operator code, product code, and selling price. The ticket service ID is an identifier for each issued ticket. The account ID is an identifier for each account of the user who purchased the ticket service. The operator code is an identifier for the operator who sold the ticket service. The product code is an identifier for uniquely identifying the sold product. The selling price is the price of the sold product. The detailed data may include information other than the ticket service ID, operator code, product code, and selling price.

[0068] FIG. 13 is a table showing an example of detailed data (detailed data 167). The detailed data 167 is a table in which a ticket service ID, a vendor code, a product code, and a selling price are summarized. For example, the ticket service with the ticket service ID "99999999" is a product with the product code "YYYYYYY2" sold by the vendor with the vendor code "XXXXXXXX". The selling price of the ticket service with the ticket service ID "99999999" is "1000" yen. The detailed data 167 in FIG. 13 is an example and does not limit the detailed data of the present embodiment. For example, as the detailed data, not only the ticket issuance information but also the evidence of boarding and alighting are stored as the usage trace of the system by the user. When the storage of the detailed data is unnecessary, the creation of the detailed data is not essential.

[0069] FIG. 14 is a table showing an example of the held product transaction (held product transaction 168). The held product transaction 168 is a table in which a ticket service ID, an account ID, a vendor code, a product code, an expiration date, and an identification code expiration date are summarized for each ticket service. For example, the ticket service with the ticket service ID "99999999" was purchased by the user with the account ID "ABCDE". The ticket service with the ticket service ID "99999999" is a product with the product code "YYYYYYY2" sold by the vendor with the vendor code "XXXXXXXX". The expiration date of the ticket service with the ticket service ID "99999999" is "March 31, 2024 24:00:00". In the example of FIG. 14, the use of the ticket service has started. Therefore, the expiration date of the identification code used for the use of the ticket service is entered in the identification code expiration date of the held product transaction 166. The expiration date of the identification code may be specified by the expiration month or expiration date without specifying the time. The held product transaction 168 in FIG. 14 is an example and does not limit the held product transaction of the present embodiment.

[0070] Next, the ticket issuing unit 11 and the usage right management unit 12 of the management server 16 will be described with reference to the drawings. The configurations described below are examples of the ticket issuing unit 11 and the usage right management unit 12. The configurations of the ticket issuing unit 11 and the usage right management unit 12 are not limited to the following configurations.

[0071] <Ticket Issuing Unit> FIG. 15 is a block diagram showing an example of the configuration of the ticket issuing unit of the management server according to the present disclosure. The ticket issuing unit 11 includes a ticket issuing request acquisition unit 111, a ticket issuing information generation unit 113, and a ticket issuing information transmission unit 115.

[0072] The ticket issuing request acquisition unit 111 acquires a ticket issuing request from the service server 15. The ticket issuing request acquisition unit 111 outputs the ticket issuing request to the ticket issuing information generation unit 113. For example, the ticket issuing request acquisition unit 111 is realized by an API (Application Programming Interface) that receives the ticket issuing request and transmits a digital ticket corresponding to the ticket issuing request.

[0073] The ticket issuing information generation unit 113 acquires the ticket issuing request from the ticket issuing request acquisition unit 111. The ticket issuing information generation unit 113 acquires ticket information corresponding to the acquired ticket issuing request from the product information storage unit 160. The ticket issuing information generation unit 113 generates ticket issuing information corresponding to the ticket issuing request using the acquired ticket information. The ticket issuing information generation unit 113 stores the generated ticket issuing information in the ticket issuing information storage unit 165. Also, the ticket issuing information generation unit 113 outputs the generated ticket issuing information to the ticket issuing information transmission unit 115.

[0074] The ticket issuing information transmission unit 115 acquires the ticket issuing information from the ticket issuing information generation unit 113. The ticket issuing information transmission unit 115 transmits the acquired ticket issuing information to the service server 15.

[0075] <Usage Right Management Unit> FIG. 16 is a block diagram showing an example of the configuration of the usage right management unit included in the management server according to the present disclosure. The usage right management unit 12 includes a usage right information acquisition unit 121, a validity determination unit 122, a usage right information generation unit 123, a usage right information transmission unit 124, an identification code acquisition unit 125, and a determination result transmission unit 126.

[0076] The usage right information acquisition unit 121 acquires a usage start request from the service server 15. The usage right information acquisition unit 121 outputs the acquired usage start request to the validity determination unit 122.

[0077] The validity determination unit 122 acquires the acquired usage start request from the ticket information storage unit 165. The validity determination unit 122 determines the validity of the ticket identified by the acquired usage start request. If the date and time when the usage start request was issued is earlier than the expiration date and time of the ticket, the validity determination unit 122 determines that the ticket is valid. In this case, the validity determination unit 122 outputs a determination result indicating that the ticket for which the usage start request was made is valid to the usage right information generation unit 123. On the other hand, if the expiration date of the ticket identified by the ticket information is before the time when the usage start request was issued, the validity determination unit 122 determines that the ticket is invalid. In this case, the validity determination unit 122 outputs a determination result indicating that the ticket for which the usage start request was made is invalid to the usage right information generation unit 123.

[0078] The usage right information generation unit 123 acquires the determination result from the validity determination unit 122. When the ticket for which the usage start request has been made is valid, the usage right management unit 12 sets the identification code expiration date of the ticket issuance information. The usage right management unit 12 sets the date and time at a point in time after a predetermined period from the point in time when the usage start request is issued as the identification code expiration date. For example, when the predetermined period is 24 hours, the usage right information generation unit 123 sets the identification code expiration date to the date and time 24 hours later. The usage right management unit 12 sets the identification code expiration date for the ticket stored in the ticket issuance information storage unit 165. Further, the usage right management unit 12 generates usage right information for the user who purchased the ticket for which the usage start request has been made. The usage right information includes an identification code used in the use of the transportation facility. On the other hand, when the ticket for which the usage start request has been made is invalid, the usage right management unit 12 generates usage right information indicating that the ticket is invalid. The usage right information generation unit 123 outputs the generated usage right information to the usage right information transmission unit 124.

[0079] The usage right information transmission unit 124 acquires the usage right information from the usage right information generation unit 123. The usage right management unit 12 transmits the acquired usage right information to the service server 15.

[0080] The identification code acquisition unit 125 acquires the identification code from the reader 18 mounted on the transportation facility that the user intends to use. The identification code acquisition unit 125 outputs the acquired identification code to the validity determination unit 122.

[0081] The validity determination unit 122 acquires the identification code from the identification code acquisition unit 125. The validity determination unit 122 determines the validity of the acquired identification code. If the date and time when the identification code was sent is before the date and time of the identification code expiration date, the validity determination unit 122 determines that the identification code is valid. In that case, the validity determination unit 122 outputs a determination result indicating that the identification code is valid to the determination result transmission unit 126. On the other hand, if the date and time when the identification code was sent is after the date and time of the identification code expiration date, the validity determination unit 122 determines that the identification code is invalid. In that case, the validity determination unit 122 outputs a determination result indicating that the identification code is invalid to the determination result transmission unit 126.

[0082] The determination result transmission unit 126 acquires the determination result from the validity determination unit 122. The determination result transmission unit 126 transmits the acquired determination result to the reader 18 which is the transmission source of the identification code. If the determination result is valid, the user who uses the mobile terminal 17 which is the transmission source of the identification code is permitted to use the transportation means that can be used with the ticket associated with the identification code. If the determination result is invalid, the user who uses the mobile terminal 17 which is the transmission source of the identification code is not permitted to use the transportation means that could be used with the ticket associated with the identification code.

[0083] (Operation) Next, the operations related to the information management system according to the present embodiment will be described with reference to the drawings. In the following, the ticket issuance and use in the information management system according to the present embodiment will be individually described.

[0084] [Ticket Issuance] FIG. 17 is a sequence diagram for explaining the ticket issuance according to the present disclosure. FIG. 17 shows the relationship between the mobile terminal 17 used by the user, the service server 15, and the management server 16. In the example of FIG. 17, it is assumed that the information management device 10 is implemented in the management server 16.

[0085] In FIG. 17, first, the mobile terminal 17 transmits a request to access the ticketing service that provides the ticketing service to the service server 15 according to an operation by the user. The service server 15 transmits site information for accessing the user interface for using the ticketing service to the mobile terminal 17 that is the source of the access request in response to the access request.

[0086] Also, the mobile terminal 17 transmits ticket issuance request information to the service server 15 via the user interface for using the ticketing service. The service server 15 transmits a ticket issuance request corresponding to the issuance request information to the management server 16. The management server 16 executes a ticket issuance information generation process for issuing a ticket corresponding to the ticket issuance request. The management server 16 transmits the ticket issuance information regarding the issued ticket to the service server 15. The service server 15 transmits the ticket issuance information regarding the issued ticket to the mobile terminal 17 that is the source of the ticket issuance request information.

[0087] <Service Server> FIG. 18 is a flowchart showing an example of the operation of the service server 15 in ticket issuance according to the present disclosure. In the description of the process along the flowchart of FIG. 18, the service server 15 is described as the operating entity. The operating entity of the process along the flowchart of FIG. 18 may be a component of the service server 15. In the description of the process along the flowchart of FIG. 18, the internal process of the service server 15 may be omitted.

[0088] In FIG. 18, first, the service server 15 acquires an access request to the ticket purchase site (step S111).

[0089] Next, the service server 15 transmits the site information of the ticket purchase site corresponding to the access request to the mobile terminal 17 that is the source of the access request (step S112).

[0090] When the ticket issuance request information is acquired (Yes in step S113), the service server 15 transmits a ticket issuance request corresponding to the acquired ticket issuance request information to the management server 16 (step S114). When the ticket issuance request information has not been acquired (No in step S113), the service server 15 waits until the ticket issuance request information is acquired.

[0091] Next to step S114, when the ticket issuance information is acquired (Yes in step S115), the service server 15 transmits the acquired ticket issuance information to the mobile terminal 17 that is the transmission source of the ticket issuance request (step S116). When the ticket issuance information has not been acquired (No in step S115), the service server 15 waits until the ticket issuance information is acquired. Note that the description regarding settlement is omitted in step S114. Usually, the service server 15 transmits the ticket issuance information to the mobile terminal 17 that is the transmission source of the ticket issuance request after the settlement is completed.

[0092] Next to step S116, the service server 15 executes a settlement process according to the ticket issuance information (step S117). The settlement process in step S117 is a process in which the service server 15 that is the transmission source of the ticket issuance request executes settlement with respect to the management server 16 that is the transmission destination of the ticket issuance request. The settlement process in step S117 corresponds to the settlement process of the ticket rights between the service provider and the management server 10. Generally, the settlement process is not executed for each sale of an individual digital ticket, but is executed periodically in a lump sum. For example, the settlement process is executed at a fixed date and time every month. The details of the claim process are omitted from the description.

[0093] <Management Server> FIG. 19 is a flowchart showing an example of the operation of the management server 16 in ticket issuance according to the present disclosure. In the description of the process along the flowchart of FIG. 19, the management server 16 is described as the operating entity. The operating entity of the process along the flowchart of FIG. 19 may be a component of the management server 16. In the description of the process along the flowchart of FIG. 19, the internal process of the management server 16 may be omitted.

[0094] In FIG. 19, first, the management server 16 acquires a ticket issuance request from the service server 15 (step S121).

[0095] Next, the management server 16 executes a ticket information generation process according to the ticket issuance request to generate ticket information (step S122).

[0096] Next, the management server 16 transmits the generated ticket information to the service server (step S123).

[0097] FIG. 20 is a conceptual diagram showing an example in which a user interface for using the ticketing service is displayed on the screen of the mobile terminal 17. In the example of FIG. 20, a plurality of buttons are displayed on the user interface on the screen. Button A1 is a button for purchasing a ticket. Button A2 is a button for purchasing an option ticket. Button A3 is a button for checking the purchased ticket. The user interface transitions according to the selection of any of the buttons displayed on the screen of the mobile terminal 17. FIG. 20 is an example and does not limit the buttons displayed on the user interface for using the ticketing service.

[0098] FIG. 21 is a conceptual diagram showing an example in which a user interface for selecting a ticket is displayed on the screen of the mobile terminal 17. FIG. 21 shows an example of a transition to a screen for selecting a ticket in response to the selection of button A1 in the user interface of FIG. 20. In the example of FIG. 21, a plurality of buttons are displayed on the user interface. Button B1 is a button for purchasing an e-ticket. The e-ticket is a ticket for using a train. Button B2 is a button for purchasing a B-ticket. The B-ticket is a ticket for using a bus. Button B3 is a button for purchasing an EB-ticket. The EB-ticket is a ticket for using a train and a bus. Button B4 is a button for purchasing an EBC-ticket. The EBC-ticket is a ticket for using a train, a bus, and a rental cycle. FIG. 21 is an example and does not limit the buttons displayed in the user interface for selecting a ticket.

[0099] FIG. 22 is a conceptual diagram showing an example in which information showing details of a ticket is displayed on the screen of the mobile terminal 17. FIG. 22 shows an example of a transition to a screen showing details of the EB-ticket in response to the selection of button B3 in the user interface of FIG. 21. In the example of FIG. 22, detailed information on the ticket information of the EB-ticket is displayed on the screen. In the example of FIG. 22, the EB-ticket is a "24-hour ticket for trains and buses in City H". The expiration date for using the EB-ticket is 60 days. The fare for the EB-ticket is 1,000 yen for both adults and children. The transportation means available with the EB-ticket are trains (all lines of H Electric Railway) and buses (H Electric Railway, H Bus, H Transportation). A button C (Next) for purchasing the EB-ticket is displayed on the user interface of FIG. 22. When button C is selected, the screen transitions to the purchase screen for the EB-ticket.

[0100] FIG. 23 is a conceptual diagram showing an example in which a ticket purchase screen is displayed on the screen of the mobile terminal 17. FIG. 23 shows an example in which, in response to the selection of button C in the user interface of FIG. 22, the screen has transitioned to a screen for purchasing an EB ticket. In the example of FIG. 23, information indicating the purchase details of the EB ticket by the user is displayed on the screen. In the example of FIG. 23, the user's email address (XXX@AAA.com) is displayed on the screen as the user information. The purchase details include the product name, the number of tickets purchased, the start date of use, and the total amount. The product name is the EB ticket. The number of tickets purchased is one for an adult. The start date of use is 60 days. The total amount is 1,000 yen. On the user interface of FIG. 23, a button D (payment) for finalizing the purchase of the EB ticket is displayed. When button D is selected, the purchase of the EB ticket is finalized. When the purchase of the EB ticket is finalized, payment corresponding to the purchase of the ticket is executed via a settlement agency such as a credit card company linked to the user's account. Explanation of the payment corresponding to the purchase of the ticket is omitted.

[0101] [Activation] FIG. 24 is a sequence diagram for explaining the activation for starting the use of the ticket according to the present disclosure. FIG. 24 shows the relationship between the mobile terminal 17 used by the user, the service server 15, and the management server 16. In the example of FIG. 24, it is assumed that the information management device 10 is implemented in the management server 16.

[0102] In FIG. 24, first, the mobile terminal 17 transmits a request to start using the purchased ticket to the service server 15 in response to an operation by the user. The service server 15 transfers the start - use request obtained from the mobile terminal 17 to the management server 16. The management server 16 executes the activation process of the ticket in response to the start - use request. The management server 16 transmits the use - right information including the identification code for using the ticket to the service server 15. The service server 15 transmits the identification code included in the use - right information to the mobile terminal 17, which is the source of the start - use request.

[0103] <Service Server> FIG. 25 is a flowchart showing an example of the operation of the service server 15 in ticket activation according to the present disclosure. In the description of the process along the flowchart of FIG. 25, the service server 15 will be described as the main operating entity. The main operating entity of the process along the flowchart of FIG. 25 may be a component of the service server 15. In the description of the process along the flowchart of FIG. 25, the internal processing of the service server 15 may be omitted.

[0104] In FIG. 25, first, the service server 15 acquires a usage start request for a ticket purchased at the request of the user (step S131).

[0105] Next, the service server 15 transfers the acquired usage start request to the management server 16 (step S132).

[0106] When the usage right information is acquired (Yes in step S133), the service server 15 transmits the identification code included in the acquired usage right information to the mobile terminal 17 that is the source of the usage start request (step S134). When the usage right information has not been acquired (No in step S133), the service server 15 waits until the usage right information is acquired.

[0107] After step S134, the service server 15 records the acquired usage right information (step S135). Step S135 may be executed before step S134.

[0108] <Management Server> FIG. 26 is a flowchart showing an example of the operation of the management server 16 in ticket issuance according to the present disclosure. In the description of the process along the flowchart of FIG. 26, the management server 16 will be described as the main operating entity. The main operating entity of the process along the flowchart of FIG. 26 may be a component of the management server 16. In the description of the process along the flowchart of FIG. 26, the internal processing of the management server 16 may be omitted.

[0109] In FIG. 26, first, the management server 16 acquires a start request from the service server 15 (step S141).

[0110] Next, the management server 16 executes an activation process in response to the start-of-use request and generates use right information including an identification code (step S142).

[0111] Next, the management server 16 transmits the generated use right information to the service server (step S143).

[0112] FIG. 27 is a conceptual diagram showing an example in which a user interface for accepting the start of use of the ticketing service is displayed on the screen of the mobile terminal 17. In the example of FIG. 27, the ticket name, user, and start-of-use deadline are displayed on the screen of the mobile terminal 17. The ticket name is "EB Ticket_H City Tram Bus 24-Hour Pass". The user is "Adult". The start-of-use deadline is "60 days" from the purchase date. A button E (OK) for transmitting a start-of-use request for the displayed ticket is displayed on the user interface of FIG. 27. Character information "Do you want to start using?" is displayed in the information of button E. When button E is selected by the user, a start-of-use request is transmitted to the service server 15. FIG. 27 is an example and does not limit the information displayed on the user interface for accepting the start of use of the ticketing service.

[0113] FIG. 28 is a conceptual diagram showing an example in which usage right information regarding a ticket used by a user is displayed on the screen of the mobile terminal 17. FIG. 28 shows the usage right information of the ticket activated in response to a usage start request transmitted by selecting button E included in the user interface of FIG. 27. In the example of FIG. 28, the ticket name, user, and identification code expiration date are displayed on the screen of the mobile terminal 17. The ticket name is "EB Ticket_H City Tram Bus 24-Hour Pass". The user is "Adult". The identification code expiration date is "December 1, 2023, 24:00:00". In the example of FIG. 28, an identification code for using the ticket is displayed on the screen of the mobile terminal 17. The validity of the ticket is determined by having the identification code displayed on the screen of the mobile terminal 17 read by the reader 18 mounted on the transportation facility. FIG. 28 is an example and does not limit the screen on which the usage right information regarding the ticket used by the user is displayed.

[0114] 〔Boarding and alighting process〕 FIGS. 29 and 30 are sequence diagrams for explaining the boarding and alighting process using the ticket according to the present disclosure. In the examples of FIGS. 29 and 30, it is assumed that the information management device 10 is implemented in the management server 16. In the following, a case where both the boarding process and the alighting process are performed will be described. For example, there is also a case where only one of the boarding process or the alighting process is performed. In such a case, in either the boarding process or the alighting process, it is sufficient to perform the content confirmation or settlement process of the digital ticket.

[0115] Figure 29 is a sequence diagram related to the boarding process. Figure 29 shows the relationship among the mobile terminal 17 used by the user, the reader 18 installed in the transportation vehicle, and the management server 16. In Figure 29, first, according to the user's operation, the screen of the mobile terminal 17 is held in front of the camera of the reader 18 with the identification code displayed. The reader 18 executes a reading process to read the identification code displayed on the screen of the mobile terminal 17. The reader 18 transmits the read identification code to the management server 16. The management server 16 executes a determination process to determine whether the received identification code is valid. The management server 16 transmits a determination result indicating whether the identification code is valid or not to the reader 18. The reader 18 executes a boarding process according to the determination result. When the determination result is valid, the reader 18 permits the boarding of the user carrying the mobile terminal 17 on which the identification code is displayed. When the determination result is invalid, the reader 18 does not permit the boarding of the user carrying the mobile terminal 17 on which the identification code is displayed. For example, the reader 18 notifies the crew whether the user can use the transportation vehicle by outputting voice information and display information indicating permission and non-permission of boarding. In the case of a railway ticket gate, etc., there are cases where the user can confirm by himself / herself without the crew or station staff checking on the spot. In such cases, the reader 18 notifies not only the crew but also the user of voice information and display information indicating permission and non-permission of boarding.

[0116] FIG. 30 is a sequence diagram related to the alighting process. FIG. 30 shows the relationship among the mobile terminal 17 used by the user, the reader 18 installed in the transportation vehicle, the management server 16, and the service server 15. In FIG. 30, first, according to the operation of the user, the screen of the mobile terminal 17 is held in front of the camera of the reader 18 with the identification code displayed. The reader 18 executes a reading process to read the identification code displayed on the screen of the mobile terminal 17. The reader 18 transmits the read identification code to the management server 16. The management server 16 executes a determination process to determine whether the received identification code is valid. The management server 16 transmits a determination result indicating whether the identification code is valid to the reader 18. The reader 18 executes an alighting process according to the determination result. When the determination result is valid, the reader 18 permits the user carrying the mobile terminal 17 on which the identification code is displayed to alight. For example, the reader 18 outputs voice information or display information indicating permission to alight to notify the crew that the user is permitted to alight from the transportation vehicle. When the determination result is invalid, the reader 18 issues a notice requesting settlement to the user carrying the mobile terminal 17 on which the identification code is displayed. For example, the reader 18 outputs voice information or display information to notify the crew that the user needs to settle. In the example of FIG. 30, the management server 16 executes a settlement process. The management server 16 executes a settlement process for the user according to a preset settlement standard. The management server 16 transmits the settlement information of the user to the service server 15. With such a configuration, settlement for the user can be executed via the service server 15. For example, it may be configured so that the user can settle on the spot according to the instructions of the crew.

[0117] <Management Server> FIG. 31 is a flowchart showing an example of the operation of the management server 16 in the boarding and alighting process using the ticket according to the present disclosure. In the description of the process along the flowchart of FIG. 31, the management server 16 will be described as the main operating entity. In the description of the process along the flowchart of FIG. 31, the main operating entity of the process may be a component of the management server 16. In the description of the process along the flowchart of FIG. 31, the internal processing of the management server 16 may be omitted.

[0118] In FIG. 31, first, the management server 16 acquires an identification code from the reader 18 mounted on the transportation means that the user is about to use (step S151).

[0119] Next, the management server 16 determines the validity of the ticket associated with the acquired identification code (step S152).

[0120] Next, the management server 16 transmits the determination result to the reader 18 that is the transmission source of the identification information (step S153).

[0121] If settlement processing is required (Yes in step S154), the management server 16 executes settlement processing (step S155). On the other hand, if settlement processing is not required (No in step S154), the process along the flowchart of FIG. 31 ends.

[0122] Next to step S155, the management server 16 transmits the settlement information to the service server 15 (step S156). By step S156, the process along the flowchart of FIG. 31 ends.

[0123] 〔Refresh processing〕 FIG. 32 is a sequence diagram for explaining the refresh process of the identification code in the boarding and alighting process using the ticket according to the present disclosure. FIG. 32 shows the relationship among the mobile terminal 17 used by the user, the service server 15, and the management server 16. In the example of FIG. 32, it is assumed that the information management device 10 is implemented in the management server 16. For example, the refresh process is executed in accordance with the timing when the expiration date of the displayed identification code expires. For example, the refresh process may be executed at the timing manually requested by the user's operation. The timing at which the refresh process is performed can be arbitrarily set.

[0124] In FIG. 32, first, the service server 15 transmits a refresh request for requesting an update of the identification code of the ticket for which use has started to the management server 16. In response to the refresh request from the service server 15, the management server 16 executes a refresh process to update the identification code of the ticket. The management server 16 transmits the updated identification code to the service server 15. The service server 15 updates the identification code of the ticket targeted by the refresh request with the acquired identification code. The service server 15 transfers the updated identification code to the mobile terminal 17 carried by the user who uses the ticket.

[0125] FIG. 33 is a table showing an example (ticket transaction 139) in which the ticket issuance information stored in the storage unit 153 of the service server 15 is updated. The ticket transaction 139 in FIG. 33 is an example in which the identification code of the ticket transaction 137 in FIG. 8 is updated. In the example of FIG. 33, the ticket with the ticket code "AAAAAAAA" has been started to be used by the user with the user ID "ABCDE". The ticket with the ticket code "AAAAAAAA" can be uniquely identified by the operator system product code "XXXXXXXXYYYYYYY2". The identification code of the ticket transaction 139 in FIG. 33 has been updated in response to the refresh request.

[0126] FIG. 34 is a conceptual diagram showing an example in which an identification code updated in response to a refresh request is displayed on the screen of the mobile terminal 17. FIG. 34 is an example in which the identification code in FIG. 28 is updated. The identification code has been updated in the management server 16. Therefore, the user who uses the identification code can use the transportation facility without being aware that the identification information has been updated. If the identification code is refreshed, unauthorized use due to theft of the user's identification code can be prevented.

[0127] As described above, the information management system of the present embodiment includes a service server and a management server. The service server provides a ticketing service. The management server manages digital tickets issued by the ticketing service. The management server has an information management device. The information management device includes an issuing unit and a usage right management unit. The issuing unit issues a digital ticket for a product for sale in response to issuing request information transmitted from a service server that provides a digital ticketing service. The issuing unit transmits issuing information including the issuing details of the issued digital ticket to the service server. The usage right management unit transmits usage right information including an identification code for using the digital ticket to the user's mobile terminal via the service server in response to a usage start request transmitted from the service server. The usage right management unit manages the usage right of the digital ticket using the identification code read from the mobile terminal.

[0128] According to the present embodiment, the user can purchase a digital ticket via the service server without being aware that the digital ticket is being managed by the information management device. In addition, an operator who provides a transportation service can sell a digital ticket managed by the information management device without being aware that it is a digital ticket purchased by the service server. Further, according to the present embodiment, the digital ticket can be used using the identification code read from the user's mobile terminal. That is, according to the present embodiment, the convenience of the digital ticket can be improved for both the user and the operator.

[0129] The ABT (Account - Based Ticketing) method is a ticketing method that manages user information associated with a unique identification number on the cloud server side. Until now, in the cooperation between the general ABT method and digital tickets, paper tickets have been the mainstream. When paper tickets are used, it is necessary for the crew to check them, so delays are likely to occur when users board and alight. According to the method of this embodiment, since tickets can be transferred using the identification code, the trouble of the crew checking the tickets can be saved. Therefore, the delay caused by the crew's check can be reduced.

[0130] In one aspect of this embodiment, the ticket - issuing department issues a digital ticket for a sales - target product according to the ticket - issuing request information from a product master (product management table), which is a list summarizing the sales - business operator code, product code, product category, and product name for each sales - target product. The ticket - issuing department registers the ticket - issuing information including the ticket - issuing content of the issued digital ticket in the held - product tran (held - product management table), which is a list of issued products. According to this aspect, a digital ticket for a product corresponding to the ticket - issuing request information can be issued from among the sales - target products summarized in the product master. According to this aspect, the ticket - issuing information including the ticket - issuing content of the issued digital ticket can be managed in the held - product tran.

[0131] In one aspect of this embodiment, the digital ticket is managed in the service server using the business - operator system product code, which is a combination of the sales - business operator code and the product code. The sales - business operator code is an identifier for identifying the business operator that sells the sales - target product. The product code is an identifier for identifying the sales - target product. The sales - target product identified by the business - operator system product code is uniquely associated with the sales - target product included in the product master by the sales - business operator code and the product code that constitute the business - operator system product code. According to this aspect, the sales - target product can be uniquely identified using the business - operator system product code.

[0132] In one aspect of this embodiment, the usage right management unit sets the expiration date of the identification code of the digital ticket registered in the owned product management table in response to a usage start request. The usage right management unit transmits usage right information including the identification code with the set expiration date of the identification code to the service server. The identification code transmitted to the service server is provided to the user. According to this aspect, in response to a usage start request, the identification code with the set expiration date of the identification code can be provided to the user via the service server.

[0133] In one aspect of this embodiment, sales target products that can use a plurality of transportation agencies are registered in the product management table. According to this aspect, a plurality of transportation agencies can be used with a single digital ticket.

[0134] In one aspect of this embodiment, the usage right management unit receives the identification code read by the reader mounted on the transportation agency. When the reading time of the identification code is before the expiration date, the usage right management unit determines that the digital ticket associated with the identification code is valid. When the reading time of the identification code is after the expiration date, the usage right management unit determines that the digital ticket associated with the identification code is invalid. The usage right management unit transmits a determination result indicating the validity or invalidity of the digital ticket to the reader. According to this aspect, it is possible to determine whether the user associated with the identification code can use the transportation agency by using the identification code read by the reader mounted on the transportation agency.

[0135] In one aspect of this embodiment, the usage right management unit updates the identification code in response to a refresh request for the identification code. The usage right management unit transmits the updated identification code to the mobile terminal via the service server. According to this aspect, the security in the use of the digital ticket can be improved by updating the identification code transmitted to the mobile terminal used for the digital ticket.

[0136] (Second Embodiment) Next, the information management device 20 according to the second embodiment will be described with reference to the drawings. The information management device 20 of this embodiment has a simplified configuration compared to the information management device 10 of the first embodiment.

[0137] (Configuration) FIG. 35 is a block diagram showing an example of the configuration of the information management device in the present disclosure. The information management device 20 includes a ticket issuing unit 21 and a usage right management unit 22.

[0138] The ticket issuing unit 21 issues a digital ticket for a product to be sold in response to the ticket issuing request information transmitted from the service server that provides the digital ticketing service. The ticket issuing unit 21 transmits the ticket issuing information including the details of the issued digital ticket to the service server.

[0139] The usage right management unit 22 transmits the usage right information including the identification code for using the digital ticket to the user's mobile terminal via the service server in response to the usage start request transmitted from the service server. The usage right management unit 22 manages the usage right of the digital ticket using the identification code read from the mobile terminal.

[0140] (Operation) FIG. 36 is a flowchart for explaining an example of the operation of the information management device in the present disclosure. In the description of the process along the flowchart of FIG. 36, the components of the information management device 20 will be described as the operating entities. The operating entity of the process along the flowchart of FIG. 36 may be the information management device 20.

[0141] In FIG. 36, first, the ticket issuing unit 21 issues a digital ticket for the product to be sold in response to the ticket issuing request information transmitted from the service server that provides the digital ticketing service (step S21).

[0142] Next, the ticket issuing unit 21 transmits the ticket issuing information including the details of the issued digital ticket to the service server (step S22).

[0143] Next, in response to the usage start request transmitted from the service server, the usage right management unit 22 transmits, via the service server, usage right information including an identification code for using the digital ticket to the user's mobile terminal (step S23).

[0144] Next, the usage right management unit 22 manages the usage right of the digital ticket using the identification code read from the mobile terminal (step S24).

[0145] According to the present embodiment, the user can purchase a digital ticket via the service server without being aware that the digital ticket is being managed by the information management device. Also, an operator providing transportation services can sell a digital ticket managed by the information management device without being aware that it is a digital ticket purchased by the service server. Further, according to the present embodiment, the digital ticket can be used using the identification code read from the user's mobile terminal. That is, according to the present embodiment, the convenience of the digital ticket can be improved for both the user and the operator.

[0146] (Hardware) Next, the hardware configuration for executing the control and processing in the present disclosure will be described with reference to the drawings. Here, as an example of such a hardware configuration, the information processing apparatus 90 (computer) in FIG. 37 is given. The information processing apparatus 90 in FIG. 37 is an example of a configuration for executing the control and processing in the present disclosure and does not limit the scope of the present disclosure.

[0147] As shown in FIG. 37, the information processing apparatus 90 includes a processor 91, a memory 92, an auxiliary storage device 93, an input / output interface 95, and a communication interface 96. In FIG. 37, the interface is abbreviated as I / F (Interface). The processor 91, the memory 92, the auxiliary storage device 93, the input / output interface 95, and the communication interface 96 are connected to each other via a bus 98 so as to be capable of data communication. Further, the processor 91, the memory 92, the auxiliary storage device 93, and the input / output interface 95 are connected to a network such as the Internet or an intranet via the communication interface 96.

[0148] The processor 91 expands a program (instruction) stored in the auxiliary storage device 93 or the like into the memory 92. For example, the program is a software program for executing the control and processing in the present disclosure. The processor 91 executes the program expanded in the memory 92. The processor 91 executes the control and processing in the present disclosure by executing the program.

[0149] The memory 92 is a storage device having an area where a program is expanded. In the memory 92, a program stored in the auxiliary storage device 93 or the like is expanded by the processor 91. The memory 92 is realized by a volatile memory such as a DRAM (Dynamic Random Access Memory), for example. Further, a non-volatile memory such as an MRAM (Magnetoresistive Random Access Memory) may be applied as the memory 92.

[0150] The auxiliary storage device 93 stores various data such as programs. For example, the auxiliary storage device 93 is realized by a local disk such as a hard disk or a flash memory. Note that it is also possible to omit the auxiliary storage device 93 and configure to store various data in the memory 92.

[0151] The input / output interface 95 is an interface for connecting the information processing apparatus 90 and peripheral devices based on standards and specifications. The communication interface 96 is an interface for connecting to external systems and devices through networks such as the Internet and intranet based on standards and specifications. As interfaces for connecting to external devices, the input / output interface 95 and the communication interface 96 may be shared.

[0152] Input devices such as a keyboard, a mouse, and a touch panel may be connected to the information processing apparatus 90 as necessary. Those input devices are used for inputting information and settings. When a touch panel is used as the input device, a screen having the function of the touch panel becomes the interface. The processor 91 and the input devices are connected via the input / output interface 95.

[0153] The information processing apparatus 90 may be provided with a display device for displaying information. When the display device is provided, the information processing apparatus 90 is provided with a display control device (not shown) for controlling the display of the display device. The information processing apparatus 90 and the display device are connected via the input / output interface 95.

[0154] The information processing apparatus 90 may be provided with a drive device. The drive device mediates the reading of data and programs stored in the recording medium and the writing of the processing results of the information processing apparatus 90 to the recording medium between the processor 91 and the recording medium (program recording medium). The information processing apparatus 90 and the drive device are connected via the input / output interface 95.

[0155] The above is an example of the hardware configuration for enabling the control and processing in the present disclosure. The hardware configuration in FIG. 37 is an example of the hardware configuration for executing the control and processing in the present disclosure and does not limit the scope of the present disclosure. A program for causing a computer to execute the control and processing in the present disclosure is also included in the scope of the present disclosure.

[0156] A program recording medium that records a program for executing the processing in the present embodiment is also included in the scope of the present invention. For example, the program recording medium is a non-transitory computer-readable recording medium. The recording medium can be realized by, for example, an optical recording medium such as a CD (Compact Disc) or a DVD (Digital Versatile Disc). The recording medium may be realized by a semiconductor recording medium such as a USB (Universal Serial Bus) memory or an SD (Secure Digital) card. Further, the recording medium may be realized by a magnetic recording medium such as a flexible disk or other recording media.

[0157] The components in the present disclosure may be arbitrarily combined. The components in the present disclosure may be realized by software. The components in the present disclosure may be realized by a circuit.

[0158] The present disclosure has been described with reference to the embodiments above, but the present disclosure is not limited to the above-described embodiments. Various changes that can be understood by those skilled in the art can be made to the configuration and details of the present disclosure within the scope of the present disclosure. And each embodiment can be combined with other embodiments as appropriate.

[0159] Some or all of the above embodiments can also be described as follows in the appended claims, but are not limited thereto. (Appended Claim 1) A ticket issuing unit that issues a digital ticket for a product to be sold in response to ticket issuing request information transmitted from a service server that provides a digital ticketing service, and transmits ticket issuing information including the content of the issued digital ticket to the service server; A usage right management unit that transmits usage right information including an identification code for using the digital ticket to a user's mobile terminal via the service server in response to a usage start request transmitted from the service server, and manages the usage right of the digital ticket using the identification code read from the mobile terminal. An information management device comprising: (Appended Claim 2) The ticket issuing unit issues the digital ticket for the target sales product according to the ticket issuing request information from a product management table which is a list summarizing the sales business operator code, product code, product classification, and product name for each of the target sales products, and is an information management device described in Appendix 1 that registers the ticket issuing information including the content of the issued digital ticket in a held product management table which is a list of products for which tickets have been issued. (Appendix 3) In the service server, the digital ticket is managed using a business operator system product code in which a sales business operator code for identifying the business operator selling the target sales product and a product code for identifying the target sales product are combined, and the target sales product identified by the business operator system product code is uniquely associated with the target sales product included in the product management table by the sales business operator code and the product code constituting the business operator system product code. It is an information management device described in Appendix 2. (Appendix 4) The usage right management unit sets the identification code expiration date of the digital ticket registered in the held product management table according to the usage start request, and is an information management device described in Appendix 2 that transmits the usage right information including the identification code with the set identification code expiration date to the service server. (Appendix 5) In the product management table, the target sales products that can be used for multiple transportation agencies are registered. It is an information management device described in Appendix 2. (Appendix 6) The usage right management unit receives the identification code read by a reader installed on a transportation agency, and when the reading time of the identification code is earlier than the identification code expiration date, determines that the digital ticket associated with the identification code is valid, When the reading time of the identification code is after the expiration date of the identification code, it is determined that the digital ticket associated with the identification code is invalid. An information management device according to Appendix 1 that transmits a determination result indicating whether the digital ticket is valid or invalid to the reader. (Appendix 7) The usage right management unit updates the identification code in response to a refresh request for the identification code, An information management device according to Appendix 1 that transmits the updated identification code to the mobile terminal via the service server. (Appendix 8) An information management device according to any one of Appendices 1 to 7, a service server that provides a ticketing service, An information management system comprising a management server that manages digital tickets issued by the ticketing service. (Appendix 9) A computer issues a digital ticket for a product for sale in response to ticket issuance request information transmitted from a service server that provides a digital ticketing service, transmits ticket issuance information including the ticket issuance details of the issued digital ticket to the service server, in response to a usage start request transmitted from the service server, transmits usage right information including an identification code for using the digital ticket to the user's mobile terminal via the service server, An information management method for managing the usage right of a digital ticket using the identification code read from the mobile terminal. (Appendix 10) A process of issuing a digital ticket for a product for sale in response to ticket issuance request information transmitted from a service server that provides a digital ticketing service, A process of transmitting ticket issuance information including the ticket issuance details of the issued digital ticket to the service server, In response to a service start request transmitted from the service server, a process of transmitting, via the service server, usage right information including an identification code for using the digital ticket to the user's mobile terminal; A program that causes a computer to execute a process of managing the usage right of the digital ticket using the identification code read from the mobile terminal.

[0160] In addition, part or all of the configurations described in Appendices 2 to 8 that are subordinate to Appendix 1 described above may be subordinate to Appendices 9 and 10 in the same subordinate relationship as Appendices 2 to 8. Furthermore, not limited to Appendices 1, 9, and 10, part or all of the configurations described as appendices can be similarly made subordinate to various hardware, software, various recording means for recording software, or systems, within the scope not departing from the above-described embodiments.

Explanation of Signs

[0161] 10, 20 Information management device 11, 21 Ticket issuing section 12, 22 Usage right management section 14 Base station 15 Service server 16 Management server 17 Mobile terminal 18 Reader 111 Ticket issuing request acquisition section 113 Ticket issuing information generation section 115 Ticket issuing information transmission section 121 Usage right information acquisition section 122 Validity determination section 123 Usage right information generation section 124 Usage right information transmission section 125 Identification code acquisition section 126 Determination result transmission section 151 Receiver 152 Site information acquisition section 153 Memory section 155 Request section 156 Information acquisition section 157 Ticket information generation section 158 Settlement section 159 Transmission section 160 Product information storage section 165 Ticket issuance information storage section

Claims

1. A ticket issuing unit that issues a digital ticket for a product to be sold in response to ticket issuing request information sent from a service server that provides a digital ticketing service, and transmits ticket issuing information including the content of the issued digital ticket to the service server; A usage right management unit that, in response to a usage start request sent from the service server, transmits usage right information including an identification code for using the digital ticket to a user's mobile terminal via the service server, and manages the usage right of the digital ticket using the identification code read from the mobile terminal. An information management apparatus comprising:

2. The ticket issuing unit: Issues the digital ticket for the product to be sold according to the ticket issuing request information from a product management table which is a list summarizing the sales merchant code, product code, product category, and product name for each product to be sold; The information management apparatus according to claim 1, wherein the ticket issuing information including the content of the issued digital ticket is registered in a held product management table which is a list of products for which tickets have been issued.

3. In the service server, the digital ticket is managed using a merchant system product code in which a sales merchant code for identifying a merchant selling the product to be sold and a product code for identifying the product to be sold are combined; The product to be sold identified by the merchant system product code is uniquely associated with the product to be sold included in the product management table by the sales merchant code and the product code constituting the merchant system product code. The information management apparatus according to claim 2.

4. The usage right management unit: Sets an identification code expiration date of the digital ticket registered in the held product management table in response to the usage start request; The information management apparatus according to claim 2, wherein the usage right information including the identification code with the set identification code expiration date is transmitted to the service server.

5. In the product management table: The information management apparatus according to claim 2, wherein the product to be sold that can be used by a plurality of transportation agencies is registered.

6. The usage right management unit: Receives the identification code read by a reader mounted on a transportation agency; When the reading time of the identification code is earlier than the identification code expiration date, determines that the digital ticket associated with the identification code is valid. When the reading time of the identification code is after the expiration date of the identification code, it is determined that the digital ticket associated with the identification code is invalid. The information management device according to claim 1, which transmits a determination result indicating whether the digital ticket is valid or invalid to the reader. **Claim 7** The usage right management unit updates the identification code in response to a refresh request for the identification code, and transmits the updated identification code to the mobile terminal via the service server. The information management device according to claim 1. **Claim 8** An information management system comprising the information management device according to any one of claims 1 to 7, a service server that provides a ticketing service, and a management server that manages digital tickets issued by the ticketing service. **Claim 9** A computer issues a digital ticket for a sales target product in response to ticket issuance request information transmitted from a service server that provides a digital ticketing service, transmits ticket issuance information including the ticket issuance details of the issued digital ticket to the service server, in response to a usage start request transmitted from the service server, transmits usage right information including an identification code for using the digital ticket to the user's mobile terminal via the service server, An information management method for managing the usage right of the digital ticket using the identification code read from the mobile terminal. **Claim 10** A process of issuing a digital ticket for a sales target product in response to ticket issuance request information transmitted from a service server that provides a digital ticketing service, a process of transmitting ticket issuance information including the ticket issuance details of the issued digital ticket to the service server, a process of transmitting usage right information including an identification code for using the digital ticket to the user's mobile terminal via the service server in response to a usage start request transmitted from the service server, A program that causes a computer to execute a process of managing the usage right of the digital ticket using the identification code read from the mobile terminal.

Images