Common infrastructure system and common infrastructure program

Abstract

To provide a common infrastructure system and a common infrastructure program for easily providing various services.SOLUTION: A common platform 10 as a common infrastructure system includes: a device interface 20 which communicates with a traffic service device to be used for a service of means of transportation; a network communication unit 26 which communicates with a service provider that is different from a business operator of the means of transportation; a service processing unit 21 which transmits, when receiving identification information read by the traffic service device from a medium through the device interface, information indicating whether to permit using the means of transportation based on ticket information held by a user identified with the identification information received from the traffic service device, to the traffic service device; and an authentication unit 241 which transmits, when receiving identification information read from the medium by a processing terminal that is operated by the service provider using the network communication unit, information on a ticket for using a service provided by the service provider, the ticket being held by the user identified by the identification information received from the processing terminal, to the processing terminal.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] Embodiments of the present invention relate to a common infrastructure system and a common infrastructure program.

Background Art

[0002] In transportation such as railways, a station operation system is in operation that executes station operations such as ticket gate operations using a boarding ticket or an IC card issued to each user. A conventional station operation system is a local system composed of station operation devices including ticket gates installed by each railway company. For this reason, in a conventional station operation system, the capital investment by each railway company for updating existing station operation devices and systems or installing new station operation devices increases.

[0003] On the other hand, service providers such as restaurants, sightseeing facilities, or amusement facilities around the station have a desire to actively provide services to transportation users. However, since a conventional station operation system is a local system operated by each railway company, it is not easy to provide services in cooperation with business operators in different industries to users. For example, in a conventional station operation system, in order to provide a new service using a joint ticket or the like in which a transportation company and a service provider cooperate, the transportation company and the service provider need to negotiate in advance to determine the implementation of the new service, and further, there is a problem that it is necessary to incorporate a mechanism for implementing the new service into the existing station operation system.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] In order to solve the above-described problems, an object of the present invention is to provide a common base system and a common base program that can easily provide various services.

Means for Solving the Problems

[0006] According to an embodiment, the common base system includes a device interface, a network communication unit, a business processing unit, an authentication unit, and A memory unit and a ticket management unit The device interface communicates with traffic business devices used in the business of transportation agencies. The network communication unit communicates with service providers different from the operators of transportation agencies. The business processing unit, when receiving the identification information read by the traffic business device from the medium through the device interface, notifies the traffic business device of information indicating whether the use of the transportation agency is permitted based on the ticket information held by the user specified by the identification information received from the traffic business device. The authentication unit, when receiving the identification information read by the processing terminal operated by the service provider from the medium through the network communication unit, notifies the processing terminal of information indicating the service ticket provided by the service provider held by the user specified by the identification information received from the processing terminal. The memory unit stores information regarding a planned ticket including a boarding ticket available for use on the transportation vehicle and a service use ticket provided by the service provider. The ticket management unit receives an application for a planned ticket in which a boarding ticket for the transportation vehicle and a service use ticket provided by the service provider are set from the service provider communicating via the network communication unit. The memory unit stores information indicating the boarding ticket and the service use ticket included in the planned ticket received by the ticket management unit, and further stores a user database that stores user information including the identification information of the user. The ticket management unit stores information indicating the planned ticket in association with the identification information of the user who purchased the planned ticket in the user database. When the business processing unit receives the identification information read by the transportation business device from the medium via the device interface, the business processing unit notifies the transportation business device of information indicating whether it is possible to use the transportation vehicle based on the information regarding the boarding ticket included in the planned ticket purchased by the user whose identification information matches the identification information received from the transportation business device in the user database. When the authentication unit receives the identification information read by the processing terminal operated by the service provider from the medium via the network communication unit, the authentication unit notifies the processing terminal of information indicating the content of the service use ticket included in the planned ticket purchased by the user whose identification information matches the identification information received from the processing terminal in the user database.

Brief Description of the Drawings

[0007]

Figure 1

Figure 2

Figure 3

Figure 4

Best Mode for Carrying Out the Invention

[0008] Hereinafter, embodiments will be described with reference to the drawings. FIG. 1 is a conceptual diagram showing a configuration example of a common platform 10 as a common base system according to an embodiment. The common platform 10 is a system that executes data processing of information related to operations in transportation such as railways or buses, and also executes processing to assist service providers other than transportation to provide services. That is, the common platform 10 is a system not only for operations in transportation such as railways or buses, but also for providing services by service providers other than transportation.

[0009] For example, the common platform 10 manages information related to operations such as ticket gate operations in transportation. The transportation using the common platform 10 may be a plurality of transportation operators. Examples of transportation operators using the common platform 10 include railway operators who carry out station operations using station equipment and bus operators who process boarding and alighting of passes using ticket processing machines. In the following embodiments, it is assumed that the transportation is mainly a railway operator for explanation.

[0010] Also, the number of service providers other than transportation using the common platform 10 may be plural and is not limited to a specific provider. Examples of service providers using the common platform 10 include providers who provide services in cooperation with transportation. For example, service providers using the common platform 10 may include providers who operate restaurants, accommodation facilities, tourist facilities, museums, art galleries, or amusement facilities. Also, service providers using the common platform 10 may be providers who operate taxis, rental bicycles, or rental cars used by users of stations or passes.

[0011] The common platform 10 is composed of a computer, a storage device, an interface device, etc. The common platform 10 may be realized by a server device including a processor, various memories, and various interfaces, or may be realized by combining a plurality of server devices, a plurality of interface devices, and a plurality of storage devices.

[0012] In the configuration example shown in FIG. 1, the common platform 10 has processing functions such as a business processing unit 21, a settlement processing unit 22, a revenue processing unit 23, and an information processing unit 24. These processing functions are realized by a processor executing a program stored in a memory by one or more server devices constituting the common platform 10.

[0013] In the configuration example shown in FIG. 1, the common platform 10 communicates with each business (station operation) device 111 of each transportation agency, each transportation operator's system 11 (11A, 11B, 11C), a settlement operator system 12, a user terminal 13, a service provider system 14, etc. The common platform 10 has communication interfaces such as a device interface (I / F) 20 and a network communication unit 26.

[0014] The device interface 20 is an interface for communicating with each device (station operation device) 111 (111A, 111B,..., 111a) used in each transportation agency. The network communication unit 26 has an interface (communication unit) for communicating with external devices such as a service provider system 14 and a user terminal 13 via a network. Also, the settlement processing unit 22 is assumed to include a communication interface for communicating with the settlement operator system 12.

[0015] The business processing unit 21 executes business processing (station operation processing) as a business (station operation) corresponding to the information acquired from the device. The business processing unit 21 executes data processing related to station operation based on the information acquired from the station operation device via the device interface 20, and transmits the processing result to the station operation device.

[0016] In the configuration example shown in FIG. 1, the business processing unit 21 has a passage determination unit 211 that performs passage determination as an example of station operation processing. The passage determination unit 211 determines whether passage is permitted or not based on the identification information read by the ticket gates 111A, 111B,... or the ticket processing machines 111a via the device interface 20. The ticket gates 111A, 111B,... are station operation devices installed at ticket gates of a station or the like, and perform ticket inspection operations for controlling the entry of users into the station premises or the exit of users from the station premises.

[0017] For example, the ticket gates 111A, 111B,... control the passage of users according to the determination result of the passage determination unit 211 based on the identification information read from the medium presented by the user. That is, the ticket gate 111A (111B,...) reads information including the identification information for identifying the user from the medium presented by the user.

[0018] The medium presented by the user may be any medium from which the ticket gates 111A,..., the ticket processing machines 111a, and the processing terminal 15 of the service provider described later can read the user's identification information. For example, the medium presented by the user may be a mobile terminal such as a smartphone, an IC card such as a credit card, or a ticket with information including the identification information printed on the ticket surface.

[0019] For example, when the medium presented by the user is a mobile terminal having a display unit, the mobile terminal displays code information including the identification information on the display unit. The ticket gates 111A, 111B,..., the ticket processing machines 111a, and the processing terminal 15 are provided with readers for optically reading the code information including the identification information displayed by the mobile terminal presented by the user. For example, when the medium presented by the user is a contactless IC card such as a credit card or a mobile terminal having the same function as a contactless IC card, the ticket gates 111A, 111B,..., the ticket processing machines 111a, and the processing terminal 15 are configured to be provided with readers for reading data including the user's identification information from the contactless IC card presented by the user by non-contact communication.

[0020] The passage determination unit 211 acquires the identification information read by the ticket gate machine 111A and identifies the user based on the identification information read by the ticket gate machine 111A. The passage determination unit 211 determines whether the user can pass through the ticket gate where the ticket gate machine 111A is installed based on the information regarding the ticket owned by the identified user (hereinafter also referred to as ticket information) and the user's entry and exit history, etc. The passage determination unit 211 notifies the ticket gate machine 111A of the passage determination result to cause the ticket gate machine 111A to execute the passage control of the user.

[0021] The settlement processing unit 22 executes settlement processing by communicating with the settlement operator system 12. For example, the settlement processing unit 22 executes settlement processing such as the settlement of the fare based on the processing result of the business processing unit 21 by communicating with the settlement operator system 12. Also, the settlement processing unit 22 executes the settlement processing generated by the processing of the information processing unit 24 described later by communicating with the settlement operator system 12.

[0022] The revenue processing unit 23 executes revenue processing for managing the revenue for each transportation operator. The revenue processing unit 23 manages the fare paid by the user to each transportation operator, etc. The revenue processing unit 23 has an interface corresponding to the system 11 of each transportation operator. The revenue processing unit 23 notifies each transportation facility of information such as the revenue for each transportation operator via the interface for each transportation facility.

[0023] The information processing unit 24 executes various information processing. For example, the information processing unit 24 executes information processing for providing the service provided by the service provider to the user. In the configuration example shown in FIG. 1, the information processing unit 24 includes an authentication unit 241 and a ticket management unit 242.

[0024] The authentication unit 241 functions as a ticket authentication unit that authenticates the ticket held by the user. The authentication unit 241 acquires the information read by the processing terminal 15 of the service provider from the medium presented by the user. The authentication unit 241 identifies the user based on the identification information included in the information read from the medium and identifies the ticket held by the identified user.

[0025] The ticket management unit 242 manages information related to tickets planned by service providers. For example, the ticket management unit 242 manages a planned ticket that combines a ticket for using a transportation facility operated by a transportation provider and a ticket for using a service provided by a service provider. The service provider plans a ticket for using the service as a planned ticket combined with the transportation ticket of the transportation provider. The ticket management unit 242 manages the planned ticket planned by the service provider in response to a request from the service provider.

[0026] The storage unit 25 stores various types of information. The storage unit 25 is composed of one or more storage devices. The storage unit 25 stores data used for various processes by the information processing unit 24. In the configuration example shown in FIG. 1, the storage unit 25 has a user database 251 and a ticket database 252.

[0027] The user database 251 stores information related to users. The user database 251 stores various types of information in association with identification information for each individual user. For example, the authentication unit 241 identifies the user of the identification information read by the processing terminal 15 from the medium based on the identification information of the user registered in the user database 251.

[0028] The ticket database 252 stores information related to various tickets. The ticket database 252 stores information related to tickets managed by the ticket management unit 242. In the present embodiment, the ticket database 252 stores information related to tickets provided by the service provider managed by the ticket management unit 242.

[0029] For example, the ticket management unit 242 registers the planned tickets planned by the service provider in the ticket database 252. Each time a user purchases a planned ticket, the ticket management unit 242 registers it in the ticket database 252 in association with the information indicating the planned ticket and the identification information of the user who purchased the planned ticket. The authentication unit 241 identifies the planned tickets held by the user specified by the identification information read by the processing terminal 15 from the medium.

[0030] Also, the storage unit 25 may store data used for the processing by the business processing unit 21 and the like. For example, the storage unit 25 may store fare data indicating the fares of transportation agencies used by the passage determination unit 211 for passage determination in transportation agencies.

[0031] The network communication unit 26 is an interface for communicating with external devices via a network. In the configuration example shown in FIG. 1, the common platform 10 communicates with a system (service provider system) 14 and a processing terminal 15 operated by the service provider through the network communication unit 26. Also, the common platform 10 communicates with a user terminal 13 such as a mobile terminal possessed by the user through the network communication unit 26.

[0032] Next, an example of the information stored in the user database 251 of the storage unit 25 in the common platform 10 will be described in detail. The user database 251 stores information such as personal information, payment information, possessed ticket information, entry / exit information, etc. for each user (registrant). Personal information includes information such as the identification information of the registrant (user), authentication information (password, biometric information), the contact information of the user (e-mail address, etc.), name, gender, age, date of birth, address, and telephone number.

[0033] Personal information is information that users who utilize the common platform 10 register in advance. For example, personal information is registered (stored) in the user database 251 when the user himself / herself operates the user terminal 13 according to a predetermined procedure. The user terminal 13 may be any terminal device that can communicate with the common platform 10 via a network. For example, it may be a personal computer or a mobile terminal (smartphone, mobile phone, tablet PC), etc. Also, the personal information of the user may be registered in the user database 251 using, for example, station devices (ticket vending machines, registration devices, etc.) installed at stations. Also, the personal information may be registered in the user database 251 using a device operated by a station staff member or the like.

[0034] Settlement information is information indicating a settlement method for settling fees that occur with the entry and exit such as fares. For example, the settlement information may be credit card information, may be account information for direct debit of fees, or may be information indicating the remaining balance of the amount pre-deposited for fee settlement, etc.

[0035] Holder ticket information is information regarding tickets (boarding tickets, commuter tickets, special tickets, etc.) held by the user as the registrant. For example, when a user purchases a special ticket planned by a service provider, information regarding the purchased special ticket is stored in the user database 251 as the holder ticket information of the user. Also, as the boarding ticket to be registered as holder ticket information, it may be information indicating electronic money for transportation systems that settles fees based on the settlement information, or it may be a boarding ticket purchased each time.

[0036] Entry / exit information is information indicating the entry and exit of a station or boarding and alighting of a bus or train, etc. for each user in a transportation facility. The entry / exit information is registered with information such as the entry / exit station (boarding / alighting location), entry / exit date and time, entry / exit direction, and settlement status as information indicating the entry / exit (boarding / alighting) history. As the entry / exit information, as the usage history for one instance, the entry / exit station (boarding / alighting location), entry / exit date and time, entry / exit direction, and settlement status are registered in order.

[0037] The entry / exit station is information indicating the entry station or the exit station. The entry / exit date and time is information indicating the date and time of entry or exit. The entry / exit direction is information indicating whether the passage direction is the entry direction (entry into the station premises) or the exit direction (exit from the station premises). The settlement status is information indicating whether the fare settlement process for the entry / exit has been completed or not. For example, the settlement status is registered with the initial value of "not settled" for settlement, and is updated to "settled" after the settlement process.

[0038] Next, an example of the information stored in the ticket database 252 of the storage unit 25 in the common platform 10 will be described in detail. As described above, the ticket database 252 stores information regarding tickets managed by the ticket management unit 242. The service provider creates (plans) a set ticket (planned ticket) that combines a transportation ticket of a transportation agency and a service use ticket provided by the service provider. If the planned ticket created by the service provider is a sellable ticket, the ticket management unit 242 registers the information regarding the planned ticket in the ticket database 252.

[0039] The common platform 10 allows the sale of a planned ticket in which a service use ticket provided by the service provider is set for a transportation ticket of a transportation agency that has obtained prior approval from the transportation agency. The ticket management unit 242 communicates with the service provider system 14 via the network communication unit 26 and accepts an application to newly sell a planned ticket created by the service provider. The ticket management unit 242 examines the content of the applied planned ticket, and if it permits the sale of the planned ticket, registers the information regarding the planned ticket in the ticket database 252. After registering the planned ticket in the ticket database 252, the ticket management unit 242 manages the information regarding the user who purchased the planned ticket.

[0040] The common platform 10 may receive the planned tickets created by the service provider and sell the received planned tickets on a network such as the Web. In this case, the ticket management unit 252 registers the planned tickets in the ticket database 252 and sells the planned tickets registered in the ticket database 252 on the network. The ticket management unit 252 communicates with the user terminal 13 via the network communication unit 26 and sells the planned tickets by settling the price of the planned tickets to the user operating the user terminal 13 using the settlement processing unit 22. The ticket management unit 252 registers the information regarding the sold planned tickets in the user database 251 as the held ticket information of the user.

[0041] Also, the planned tickets created by the service provider may be in a form where the service provider sells them after being registered by the common platform 10. In this case, after registering the planned tickets in the ticket database 252, the ticket management unit 252 obtains information indicating the user who sold the planned tickets from the service provider and registers the information regarding the sold planned tickets in the user database 251 as the held ticket information of the user.

[0042] Next, the process of registering the planned tickets created by the service provider in the common platform 10 according to the embodiment will be described. FIG. 2 is a flowchart for explaining the flow of the process of registering the planned tickets created by the service provider in the common platform 10 according to the embodiment. First, the service provider creates (plans) a planned ticket (set ticket) that combines a transportation ticket and a service ticket provided by the service provider. Here, the service provider may set usage conditions (for example, available date and time) for the created planned ticket.

[0043] The service provider who creates the planning ticket connects to the common platform 10 through the service provider system 14. The common platform 10 communicates with the service provider system 14 through the network communication unit 26. The service provider system 14 that is communicatively connected to the common platform 10 sends an application to the common platform 10 stating that the created planning ticket is newly to be sold. In the common platform 10, the ticket management unit 242 accepts the application for the planning ticket from the service provider at any timing.

[0044] When the ticket management unit 242 accepts the application for the planning ticket from the service provider (ST11, YES), it examines whether the planning ticket applied for by the service provider is sellable (ST12).

[0045] For example, the common platform 10 stipulates the content and conditions of the ticket for riding that the service provider is permitted to sell as a planning ticket or the like according to the regulations previously agreed upon with each transportation operator. In this case, the ticket management unit 242 determines whether the content of the ticket for riding included in the planning ticket applied for by the service provider is sellable based on the regulations agreed upon with the transportation operator.

[0046] Also, the common platform 10 may set in advance the conditions for making the service usage ticket part included in the planning ticket sellable. In this case, the ticket management unit 242 may determine whether the planning ticket is sellable based on whether the service usage ticket included in the planning ticket applied for by the service provider meets the conditions for making it sellable.

[0047] When it is determined that the planning ticket applied for by the service provider is sellable (ST12), the ticket management unit 242 registers the information regarding the planning ticket for which the sale is permitted in the ticket database 252 (ST13). After the ticket management unit 242 registers the planning ticket in the ticket database 252, the planning ticket registered in the ticket database 252 is sold to the user.

[0048] As described above, the special tickets registered in the ticket database 252 may be sold on the network using the common platform 10, or may be sold by the service provider that created the special tickets.

[0049] When a user purchases a special ticket (ST14, YES), the ticket management unit 252 acquires the sales information of the special ticket including the identification information of the user who purchased the special ticket (ST15). When the sales information of the special ticket is acquired, the ticket management unit 252 registers the information regarding the sold special ticket in the user database 251 as the ticket information held by the user who is the purchaser (ST16).

[0050] For example, when selling a special ticket to a user who operates the user terminal 13 communicating via the network communication unit 26, the ticket management unit 252 registers the information regarding the sold special ticket in the user database 251 as the ticket information held by the user. When acquiring information indicating the user who sold the special ticket from the service provider, the ticket management unit 252 registers the information regarding the sold special ticket in the user database 251 as the ticket information held by the user.

[0051] Next, the processing when a user passes through the ticket gate as a traffic service device managed by the common platform 10 according to the embodiment will be described. FIG. 3 is a flowchart for explaining the flow of passage control processing when a user passes through the ticket gate managed by the common platform 10 according to the embodiment. The common platform 10 is connected to each station service device such as the ticket gate 111A,... and the ticket processing machine 111a through the device interface 20. The ticket gate 111A connected to the common platform 10 reads information including identification information from the medium presented by the user who intends to pass through the ticket gate. The ticket gate 111A transmits the information read from the medium presented by the user to the common platform 10.

[0052] In the common platform 10, when the business processing unit 21 receives the information read by the ticket gate 111A from the medium through the device interface 20 (ST21, YES), it extracts the identification information of the user included in the information read by the ticket gate 111A from the medium. When acquiring the identification information of the user, the business processing unit 21 determines whether the user corresponding to the identification information is the purchaser of the special event ticket (ST22). For example, the business processing unit 21 determines whether the user corresponding to the identification information is the purchaser of the special event ticket (the person who holds the special event ticket) based on whether a special event ticket associated with the identification information is registered in the user database 251.

[0053] When the user corresponding to the identification information is the purchaser of the special event ticket (ST22, YES), the business processing unit 21 determines whether there is a special event ticket available for use by the ticket gate 111A among the special event tickets held by the person (ST23). For example, the business processing unit 21 determines whether there is a special event ticket available for use based on whether there is a special event ticket including a valid train ticket among the special event tickets held by the person. Also, when usage conditions or the like are set for the special event tickets held by the person, the business processing unit 21 determines whether there is a special event ticket available for use including whether the usage conditions are met.

[0054] When the user corresponding to the identification information is not the purchaser of the special event ticket (ST22, NO), or when there is no available special event ticket (ST23, NO), the business processing unit 21 executes a passage determination other than with a special event ticket by the passage determination unit 211 (ST31). The passage determination unit 211 determines whether passage is permitted based on the train ticket information held by the user registered in the user database 251. For example, the passage determination unit 211 determines whether passage is permitted based on the settlement of tolls by transportation - based electronic money or commuter pass information, etc. The business processing unit 21 notifies the ticket gate 111A of the determination result of whether passage is permitted by the passage determination unit 211 (ST32), and stores the passage result of the ticket gate 111A as passage history information (ST33).

[0055] When there are available planning tickets for the user of the identification information (ST23, YES), the business processing unit 21 determines whether the user can pass through the ticket gate 111A using the train tickets included in the available planning tickets by the passage determination unit 211 (ST24).

[0056] When it is determined that the ticket gate 111A can be passed through with the train tickets included in the planning ticket (ST24, YES), the business processing unit 21 notifies the ticket gate 111A of the information indicating that passage is possible (ST27). Here, the business processing unit 21 may display on the display unit of the ticket gate 111A that passage has been permitted with the planning ticket held by the user. Also, the business processing unit 21 may notify the contact information of the user himself / herself, such as the email address registered as the personal information of the user, of the information that the ticket gate has been passed through with the planning ticket.

[0057] Also, when the business processing unit 21 notifies the ticket gate 111A that passage is possible, it records the information indicating that the ticket gate 111A has been passed through using the planning ticket (ST28). For example, the business processing unit 21 stores in the storage unit 25, in association with the identification information of the user, information such as the date and time and location when the train ticket included in the planning ticket was used as the usage history information of the planning ticket. Thereby, the common platform 10 can manage the usage history of the train tickets included in the planning ticket.

[0058] Also, when it is not determined that passage is possible only with the available planning tickets held by the user (ST24, NO), the business processing unit 21 may perform the settlement process for the train tickets included in the planning ticket (ST25). For example, the business processing unit 21 settles the insufficient train fare with the settlement method pre-set by the user using the train tickets included in the planning ticket.

[0059] For example, the payment method for the insufficient fare may be registered in the user database according to the settings made by the user. In this case, the business processing unit 21 settles the insufficient fare for the ride using the payment processing unit 22 in accordance with the payment method of the user registered in the user database. Also, when the medium presented by the user to the ticket gate 111A is a credit card that enables immediate payment, the insufficient fare for the ride is settled by the payment function of the credit card.

[0060] However, the ride ticket included in the special ticket may be set so as not to execute the settlement process when passing through the ticket gate as a usage condition of the special ticket. In such a setting, when it is determined that the user cannot pass only with the special ticket held by the user (ST24, NO), the business processing unit 21 may proceed to ST31 and execute the passage determination process other than with the special ticket.

[0061] When the settlement for the ride ticket included in the special ticket is completed (ST26, YES), the business processing unit 21 proceeds to ST27, notifies the ticket gate 111A of the information indicating passage is permitted, and records the information indicating that the user has passed through the ticket gate 111A using the special ticket.

[0062] Also, when the settlement for the ride ticket included in the special ticket is not possible (ST26, NO), the business processing unit 21 notifies the ticket gate 111A of the information indicating passage is not permitted (ST29), and records the information indicating that passage through the ticket gate 111A using the special ticket is not permitted (ST30).

[0063] Next, the process of providing the service ticket included in the special ticket purchased by the user by the common platform 10 according to the embodiment to the service provider will be described. FIG. 4 is a flowchart for explaining the flow of the process of providing the service ticket included in the special ticket purchased by the user by the common platform 10 according to the embodiment to the service provider. The common platform 10 is connected to the processing terminal 15 of the service provider by the network communication unit 26. The processing terminal 15 connected to the common platform 10 is used by a service provider that provides a service according to a service ticket included in the planning ticket. When a user who holds a planning ticket appears, the service provider reads information including identification information from the medium presented by the user by the processing terminal 15. The processing terminal 15 transmits an authentication request for requesting information regarding the service ticket that the service provider can provide, together with the information read from the medium presented by the user and the information indicating the service provider, to the common platform 10.

[0064] In the common platform 10, the authentication unit 241 of the information processing unit 24 acquires the authentication request received from the processing terminal 15 by the device interface 20 (ST41, YES). The authentication unit 241 extracts the identification information of the user in the information read from the user's medium acquired together with the authentication request from the processing terminal 15.

[0065] The authentication unit 241 determines whether the user of the identification information is a purchaser of a planning ticket including a service ticket for the service provided by the service provider (ST42). For example, the authentication unit 241 determines whether a planning ticket including a service ticket for the service provided by the service provider is registered in the user database 251 in association with the identification information. Thereby, the authentication unit 241 determines whether the user of the identification information is a purchaser (a person who holds a planning ticket) of a planning ticket including a service ticket of the service provider.

[0066] When the user of the identification information is not a purchaser of a planning ticket including a service ticket of the service provider (ST42, NO), the authentication unit 241 notifies the processing terminal 15 that is the source of the authentication request that the user who presented the medium does not hold a service ticket for the service provided by the service provider (ST43), and ends the series of processes.

[0067] When the user of the identification information is a purchaser of a planning ticket including a service ticket of the service provider (ST42, YES), the authentication unit 241 determines whether the service ticket included in the planning ticket held by the user is in a valid state (ST44). For example, when usage conditions or the like are set for the service ticket included in the planning ticket held by the user, the authentication unit 241 determines whether the service ticket included in the planning ticket exists based on whether the usage conditions are met.

[0068] When it is determined that the service ticket included in the planning ticket held by the user of the identification information is not in a valid state (ST44, NO), the authentication unit 241 notifies the processing terminal 15 of the authentication requester that the service ticket included in the planning ticket held by the user who presented the medium is invalid (ST45). Here, the authentication unit 241 may notify the processing terminal 15 of the reason why the service ticket included in the planning ticket such as expired has become invalid. Thereby, the processing terminal 15 can notify the user who presented the medium of the reason why the planning ticket is invalid.

[0069] When it is determined that the service ticket included in the planning ticket held by the user of the identification information is valid (ST44, YES), the authentication unit 241 transmits information indicating the content of the service ticket included in the planning ticket held by the user to the processing terminal 15 of the authentication requester as an authentication result (ST46).

[0070] Thereby, the processing terminal 15 acquires information indicating the content of the service that can be provided to the user who presented the medium from the common platform 10 in response to the authentication request. When the processing terminal 15 provides a service based on the service ticket included in the planning ticket, that is, when the user uses the service ticket included in the planning ticket, the processing terminal 15 notifies the common platform 10 of information indicating the usage record.

[0071] The ticket management unit 242 manages that the service use tickets included in the planned ticket are used based on the information from the processing terminal 15. That is, after the authentication unit 241 transmits the information indicating the content of the service available as the authentication result, the ticket management unit 242 receives a notification indicating that the service use tickets included in the planned ticket have been used (ST47).

[0072] When the ticket management unit 242 receives information indicating that the service use tickets included in the planned ticket have been used from the processing terminal 15 of the service provider (ST47, YES), the ticket management unit 242 records the service use record included in the planned ticket (ST48). For example, the ticket management unit 242 records in the user database 251 that the service use tickets included in the planned ticket held by the user have been used.

[0073] According to the above processing, the common platform manages a set (planned) ticket in which a service use ticket provided by a service provider different from the transportation provider and a transportation ticket planned by the transportation provider are set. When the user presents a medium indicating his / her identification information to the ticket gate machine, the common platform identifies the planned ticket held by the user of the identification information read by the ticket gate machine and executes the ticket gate processing using the transportation ticket included in the planned ticket. Also, when the user presents a medium indicating his / her identification information to the processing terminal of the service provider, the common platform identifies the planned ticket held by the user of the identification information read by the processing terminal and notifies the service provider of the content of the service to be provided based on the service use tickets included in the planned ticket.

[0074] Thereby, a service provider who is not a transportation provider can plan and sell a planned ticket in which a service use ticket and a transportation ticket of a transportation provider are set, and can promote the use of the service and the use of transportation facilities. Also, since the service provider can sell a planned ticket in which a transportation ticket of a transportation provider is set at an arbitrary timing without prior consultation with the transportation provider, it is possible to promote the use (sale) of the service according to the service use situation and the like.

[0075] For example, a restaurant, which is an example of a service provider, can plan and sell to users a package ticket that combines a train ticket and a coupon ticket that can be used at the restaurant at any timing. Also, as another example of a service provider, various facilities such as an amusement park and an art museum can plan and sell to users a package ticket that combines a train ticket and an admission ticket to the facility or a ticket for using an attraction at any timing. For example, when a decrease in the number of service users is expected due to rain or the like, by selling, as a package ticket, a service ticket that provides the service at a discount and a train ticket, it is possible to promote the use of the service.

[0076] Note that each of the above-described processes can be executed by some software. Therefore, by installing and executing these programs in a remote control device through a computer-readable storage medium storing some programs for executing the procedures of the above processes, the above processes can be easily realized. For example, the remote control device may download the program via a network and install the program by storing the downloaded program. Also, the remote control device may read the above program from various information storage media and install the program by storing the read program.

[0077] Although some embodiments of the present invention have been described, these embodiments are presented by way of example and are not intended to limit the scope of the invention. These novel embodiments can be implemented in various other forms, and various omissions, replacements, and changes can be made without departing from the gist of the invention. These embodiments and their modifications are included in the scope and gist of the invention and are included in the invention described in the claims and the equivalent scope thereof.

Description of Reference Numerals

[0078] 10…Common platform, 12…Payment operator system, 13…User terminal, 14…Service provider system, 15…Processing terminal, 20…Device interface, 21…Business processing unit, 22…Payment processing unit, 23…Revenue processing unit, 24…Information processing unit, 25…Memory unit, 26…Network communication unit, 111A, 111B…Ticket barrier, 111a…Ticket processing machine, 211…Passage determination unit, 241…Authentication unit, 242…Ticket management unit, 251…User database, 252…Ticket database.

Claims

1. A device interface for communicating with a transportation service device used in the operations of a transportation agency, A network communication unit for communicating with a service provider different from the operator of the transportation agency, When receiving the identification information read by the transportation service device from a medium through the device interface, a service processing unit for notifying the transportation service device of information indicating the availability of using the transportation agency based on the ticket information held by the user identified by the identification information received from the transportation service device, When receiving the identification information read by a processing terminal operated by the service provider from a medium through the network communication unit, an authentication unit for notifying the processing terminal of information indicating the service ticket provided by the service provider held by the user identified by the identification information received from the processing terminal, A storage unit for storing information regarding a planned ticket including a boarding ticket available for use in the transportation agency and a service ticket provided by the service provider, A ticket management unit for receiving an application for a planned ticket in which a boarding ticket of the transportation agency and a service ticket provided by the service provider are set from the service provider communicating through the network communication unit, The storage unit stores information indicating the boarding ticket and the service ticket included in the planned ticket received by the ticket management unit, and further stores a user database storing user information including the identification information of the user, The ticket management unit stores information indicating the planned ticket in association with the identification information of the user who purchased the planned ticket in the user database, When receiving the identification information read by the transportation service device from a medium through the device interface, the service processing unit notifies the transportation service device of information indicating the availability of using the transportation agency based on the information regarding the boarding ticket included in the planned ticket purchased by the user whose identification information matches the identification information received from the transportation service device in the user database, When the authentication unit receives the identification information read from the medium by the processing terminal operated by the service provider through the network communication unit, the authentication unit notifies the processing terminal of information indicating the content of the service use ticket included in the planning ticket purchased by the user whose identification information matches the identification information received from the processing terminal in the user database. A common infrastructure system having

2. The storage unit stores a ticket database that stores information regarding the train ticket included in the planning ticket and information indicating the content of the service use ticket included in the planning ticket. The business processing unit specifies information regarding the train ticket included in the planning ticket specified by the identification information received from the transportation business device based on the information stored in the ticket database. The authentication unit specifies information indicating the content of the service use ticket included in the planning ticket specified by the identification information received from the processing terminal based on the information registered in the ticket database. The common infrastructure system according to claim 1.

3. In a computer having a device interface for communicating with a transportation business device used for the business of a transportation facility and a network communication unit for communicating with a service provider different from the operator of the transportation facility, Receive an application for a planning ticket that sets a train ticket for the transportation facility and a service use ticket provided by the service provider from the service provider communicating through the network communication unit. When the planning ticket applied for by the service provider is received, register information indicating the train ticket and the service use ticket included in the planning ticket in the storage unit. Store information indicating the planning ticket in association with the identification information of the user who purchased the planning ticket in the user database stored in the storage unit that stores user information including the identification information of the user. When receiving the identification information read by the traffic operation device from the medium through the machine interface, notify the traffic operation device of information indicating whether the user can use the transportation facility based on the information on the transportation ticket included in the planned ticket purchased by the user whose identification information matches the identification information received from the traffic operation device in the user database. When receiving the identification information read by the processing terminal operated by the service provider from the medium through the network communication unit, notify the processing terminal of information indicating the content of the service ticket included in the planned ticket purchased by the user whose identification information matches the identification information received from the processing terminal in the user database. A common base program for executing the above.

Images