JP2017228011A - Ticket information processing method and ticket information processing system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To execute processing of ticket information at high speed while defining massive station service devices, users and tickets as targets.SOLUTION: The present invention relates to a ticket information processing method to be executed by multiple information processors for processing ticket information that is information relating to a ticket held by a user of means of transportation and to be used when utilizing the means of transportation. The ticket information is stored for every user. Regarding individual information included in the ticket information of every user, in accordance with a predetermined discrimination reference that is determined in accordance with a processing load of each of the individual information, partial charge of whether to process the individual information by a first information processor or another information processor of the multiple information processors is determined. Processing time of the individual information by the first information processor is calculated and if it is discriminated that the calculated processing time exceeds a predetermined threshold, the other information processor is further caused to be in partial charge of processing of the individual information.SELECTED DRAWING: Figure 1

Description

  The present invention relates to a ticket information processing method and a ticket information processing system.

  In recent years, with the development of network technology and virtualization technology, cloud computing and thin client type business systems are spreading. Along with this, in public transportation such as railways, it is considered that the demand for realizing station equipment such as automatic ticket gates and ticket vending machines in a thin client type will increase. In this configuration, for example, only reading data from the IC card is performed by the station-side equipment on the client side, and all other processing is performed on the server side. In a thin client type automatic ticket gate system, it is important to realize high-speed processing in order to prevent congestion at the ticket gate even during commuting rush hours.

  As a technique for realizing a thin client type automatic ticket gate system, there is a method in which various processes performed by station equipment are performed at high speed on the server side (see, for example, Patent Document 1). According to Patent Document 1, high-speed processing can be realized by assigning a processor group optimized for each processing on the server side according to various processing requested from the ticket gate.

  On the other hand, in an IC card ticket, there has been proposed a method for reducing the processing load of the center server by performing an unauthorized use check at each station server (see, for example, Patent Document 2). According to Patent Document 2, a user predicts a station where the card will be used from information such as a station or area where the IC card has been recently used, and distributes the latest usage history to the predicted station. It is said that unauthorized use can be detected quickly and the load on the center side can be reduced.

JP 2012-94053 A JP 2014-44473 A

Patent Document 1 provides a mechanism for performing high-speed ticket gate processing on the server side, and Patent Document 2 provides a mechanism for reducing the load on the center side by performing an unauthorized use check at each station server.
However, the method of Patent Document 1 has a problem that the processing becomes slow when the number of ticket gates increases significantly.

  In addition, the method of Patent Document 2 does not consider ticket gate processing other than the unauthorized use check. In general, the fare calculation and media authentication included in the ticket gate processing are more complicated than the unauthorized use check, and if the method of Patent Document 2 is applied as it is, high-speed processing that does not get crowded at the ticket gate even during commuting rush hours is performed. There is a problem that it is difficult to realize.

  The present invention has been made to solve the above-described problems, and one object thereof is a ticket information processing method and a ticket that can perform high-speed processing for a large number of station equipment, users, and tickets. It is to provide an information processing system.

One aspect of the present invention for achieving the above object is a plurality of pieces of information for processing ticket information, which is information relating to a ticket used when using a transportation facility held by a transportation user. A ticket information processing method executed by a processing device, wherein each ticket information is stored for each user, and individual information included in the ticket information of each user is determined according to a processing load of each individual information. Determined by each of the first information processing device and the other information processing device among the plurality of information processing devices, and the first information of the individual information When the processing time by the information processing device is calculated and it is determined that the calculated processing time exceeds a predetermined threshold, the other individual information processing device To share the management.

  In addition, another aspect of the present invention is executed by a plurality of information processing devices for processing ticket information, which is information related to a ticket used when using the transportation held by a transportation user. A ticket information processing method for storing each piece of ticket information for each user, and for the individual information included in the ticket information of each user, a predetermined determination criterion determined according to the processing load of each individual information To determine which of the first information processing apparatus and the other information processing apparatus to process each of the plurality of information processing apparatuses, and according to the determined sharing, Ticket information is stored in the other information processing apparatus, and the user's ticket information stored in the other information processing apparatus is stored in the first information. Synchronize with the ticket information and a predetermined timing stored in the management device.

  According to the present invention, high-speed processing can be performed for a large number of station service devices, users, and tickets.

FIG. 1 is a diagram showing a configuration example of a station service equipment management system 1 according to a first embodiment of the present invention. FIG. 2 is a diagram illustrating a configuration example of the station server 1040 according to the first embodiment. FIG. 3 is a diagram illustrating a configuration example of the center server 1060 according to the first embodiment. FIG. 4 is a flowchart showing an example of data processing by the processing estimation / share creation unit 3080 of the center server 1060. FIG. 5 is a flowchart illustrating an example of data processing by the entrance / exit processing unit 2070 of the station server 1040. FIG. 6 is a flowchart illustrating an example of data processing performed by the sharing adjustment unit 2080 of the station server 1040. FIG. 7 is a diagram illustrating a configuration example of the ticket information tables 2090 and 3090. FIG. 8 is a diagram illustrating a configuration example of the threshold tables 2110 and 3110. FIG. 9 is a diagram illustrating a configuration example of the sharing tables 2100 and 3100. FIG. 10 is a diagram illustrating a screen example of the threshold setting screen 10010. FIG. 11 is a diagram showing a screen example of the system operation status monitor screen 11010. FIG. 12 is a diagram illustrating a configuration example of the station server 1040 in the second embodiment. FIG. 13 is a diagram illustrating a configuration example of the center server 1060 in the second embodiment. FIG. 14 is a flowchart illustrating an example of data processing by the processing estimation / share creation unit 3080 of the center server 1060 according to the second embodiment of this invention. FIG. 15 is a flowchart illustrating an example of data processing by the entrance / exit processing unit 2070 of the station server 1040 in the second embodiment. FIG. 16 is a diagram illustrating a configuration example of the usage history table 3130. FIG. 17 is a diagram illustrating a configuration example of the address tables 2120 and 3120.

  DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, an embodiment of the present invention will be described in detail with reference to the drawings based on examples.

Example 1
First, the station equipment management system according to the first embodiment as one aspect of the ticket information processing system of the present invention will be described. FIG. 1 is a block diagram illustrating a system configuration example of a station service device management system 1 according to the present embodiment. The station service device management system 1 connects the station service device 1020 and the station server 1040 so that they can communicate with each other via a communication network 1030, and connects the station server 1040 and the center server 1060 so that they can communicate with each other via a communication network 1050. It is configured by The station service device 1020 includes a plurality of devices such as an automatic ticket gate, an automatic ticket vending machine, and a station staff operation terminal installed at each railway station. In the present embodiment, the station service device 1020 is described as an automatic ticket gate, but is not limited thereto.

  The station ticket device 1020, which is an automatic ticket gate, includes unique information for identifying individual users, such as transportation IC cards and credit cards possessed by the users, information on tickets held, monetary value information, etc. The medium 1010 storing the information can be identified, and the data that is the information can be read and written. That is, the automatic ticket checker includes a reading unit including a sensor for reading information recorded on the medium 1010, an operation for performing processing such as deduction of fare from monetary value information and expiration date checking based on the read information. And a normal unit such as a writing unit that writes processed data to the medium 1010 and a control unit that controls opening and closing of the flap door based on the processing result of the arithmetic unit. Note that the medium 1010 is not limited to a storage medium such as a card, but biometric information that can specify a user, such as a fingerprint, finger vein, eye retina, or iris, can also be used. When the user's biometric information is used, information such as monetary value information (corresponding to a so-called card balance) associated with the biometric information is recorded in the station server 1040 or the center server 1060.

  The center server 1060 is accumulated by operations such as ticket information issued to the user, user attribute information indicating attributes such as the user's name, gender, and age, and data recording on a traffic IC card or the like in advance. It has a function of managing stored fair (Stored Fair) balance information, which is information indicating the remainder of the monetary value, information necessary for authentication of the medium 1010, past usage history information, and the like for each user. Hereinafter, information recorded on a medium such as a transportation IC card may be collectively referred to as “ticket information”.

  Here, in this embodiment, it is assumed that one station server 1040 is arranged at each station in order to speed up the data processing by the automatic ticket gate when passing through the ticket gate. However, the configuration of the present embodiment is not limited to this, and a plurality of station servers 1040 may be arranged at one station in a large-scale station where a large number of station service devices 1020 are provided. In addition, for a small station with few station service devices 1020 installed, one server may be arranged for a plurality of stations. In addition, the availability can be improved by multiplexing the center server 1060 and the communication network 1050.

As an example, the system of this embodiment shown in FIG. 1 uses, for example, an IC card as the medium 1010, the station service device 1020 is a general automatic ticket gate, the station server 1040 and the center server 1060 are personal computers, workstations, and the like. Etc., and each of the communication networks 1030 and 1050 is an LA using an appropriate communication protocol.
It can be realized by configuring with N or the like.

  Next, the station server 1040 (sometimes referred to as another information processing apparatus with respect to a first information processing apparatus that is a center server 1060 described later) will be described. FIG. 2 is a diagram illustrating a configuration example of the station server 1040. As described above, the station server 1040 is, for example, a general computer, and includes a main control unit 2010, an input unit 2020, an output unit 2030, a communication processing unit 2040, and a storage management unit 2050. The main control unit 2010 is a processor such as a CPU that performs hardware control and program execution processing. The input unit 2020 is an input device for receiving an instruction input such as a program execution start instruction or a stop instruction from the system administrator, and can be configured by a keyboard, a mouse, a touch panel, or the like, for example. The output unit 2030 is an output device that outputs a program execution state and the like, and can be configured by a monitor / display or the like. The communication processing unit 2040 has a function of managing communication processing performed by the main control unit 2010 with the communication network 1030 in order to exchange data with other computers, and is a network interface card, for example. The storage management unit 2050 is a storage management unit that reads and records programs and data, and includes a memory device such as a RAM or a ROM. The above units are connected to each other by a data bus 2060 for exchanging data with each other. In the storage management unit 2050, an entrance / exit processing unit 2070 and a sharing adjustment unit 2080, which are programs for realizing the main functions of the station server 1040, a ticket information table 2090 storing data used by those programs, A sharing table 2100 and a threshold table 2110 are stored. The storage management unit 2050 may be provided with an auxiliary storage device such as an HDD or an SSD.

  Next, the center server 1060 (first information processing apparatus) will be described. FIG. 3 is a diagram illustrating a configuration example of the center server 1060. The center server 1060 is also a general computer, for example, and includes a main control unit 3010, an input unit 3020, an output unit 3030, a communication processing unit 3040, and a storage management unit 3050. The main control unit 3010 is a processor such as a CPU that performs hardware control and program execution processing. The input unit 3020 is an input device for receiving an instruction input such as a program execution start instruction or a stop instruction from the system administrator, and can be configured by a keyboard, a mouse, a touch panel, or the like, for example. The output unit 3030 is an output device that outputs a program execution state and the like, and can be configured by a monitor / display or the like. The communication processing unit 3040 has a function of managing communication processing performed by the main control unit 3010 with the communication network 3030 in order to exchange data with other computers, and is a network interface card, for example. The storage management unit 3050 reads and records programs and data, and includes a memory device such as a RAM or a ROM. The above units are connected to each other by a data bus 3060 for exchanging data with each other. The storage management unit 3050 includes a registration processing / monitoring unit 3070 that is a program for realizing the main functions of the center server 1060, a processing estimation / sharing creation unit 3080 (sharing processing unit), and data used by these programs. Are stored in a ticket information table 3090 (ticket information storage unit), a sharing table 3100, and a threshold table 3110. The storage management unit 3050 may be provided with an auxiliary storage device such as an HDD or an SSD.

  Next, the function of the station service equipment management system 1 having the above configuration will be described. First, with respect to the center server 1060, a processing example of the processing estimation / share creation unit 3080 will be described with reference to the flowchart of FIG. The processing estimate / share creation unit 3080 calculates the next day's data processing amount required by the station service device management system 1, and calculates the type and amount of data processing to be shared by the station server 1040 based on the estimation. For example, the data processing can be set to be executed every day at night from the last train operation to the first train.

  When the process estimation / share creation unit 3080 of the center server 1060 starts the process in S4000 (the symbol S means “step”), first, the ticket information table 3090 is referred to, and for each ticket type, the center It is determined which of the server 1060 and the station server 1040 is to be processed (S4010). Here, the ticket information table 3090 (ticket information storage unit) is master data that manages information (ticket information) related to an electronic ticket that has been issued at the time of execution of this data processing and is valid on the next business day. FIG. 7 shows a configuration example of the ticket information table 3090. The ticket information table 3090 of this embodiment illustrated in FIG. 7 has a plurality of records including items of a user ID 7010, SF balance 7020, commuter pass information 7030, and individual ticket information 7040. The user ID 7010 is a unique identification code assigned to each user managed by the station service device management system 1. The SF balance 7020 indicates a balance (SF balance) of monetary value that is recorded on the user's medium specified by the corresponding user ID 7010 and that can be applied to a fare or the like. In the commuter pass information 7030, the type of commuter pass (commuting to school, commuting), the boarding section of the commuter pass, and the validity period of the commuter pass are registered. The individual ticket information 7040 includes planned tickets, coupon tickets, limited express tickets, round-trip tickets, various types of tickets other than commuter passes that can be used for a fixed period within a free section, sections, validity period, and charges. Information such as reserved seat tickets can be registered. The commuter pass information and individual ticket information may store a plurality of pieces of information for one user ID 7010. In step S4010, the process estimation / share creation unit 3080 refers to the individual ticket information 7040, for example, and can enter and exit using the issued valid number A of the ticket type (two in the example of FIG. 7) and the ticket. If the value Z calculated by Equation 1 using the number of stations B (the number of stations between Tokyo and Totsuka in the example of FIG. 7) and the status update frequency C of the ticket is equal to or greater than a predetermined threshold, the station server 1040 side If the process is less than the threshold, the center server 1060 determines that the process is being performed.

Z = αA × βB × γC (Formula 1)
Here, α, β, and γ are positive coefficients. That is, for example, if the number of issued ticket types corresponding to individual tickets issued to the user is large, it is determined that processing is performed on the station server 1040 side because the load is high when processing is performed on the center server 1060 side. If the number of stations that can be entered and exited by the ticket recorded in the individual ticket information 7040 is large, it is predicted that access to the center server 1060 will occur from automatic ticket gates installed in a wide range of stations, and the communication network 1030 , 1050 traffic is congested and may not be in time for the processing time required by the automatic ticket checker, it is determined that the processing is performed on the station server 1040 side. Ticket status update frequency (for example, if it is a 6-month commuter pass, the renewal is for 2/6 months at the start of use and at the end of the period, 3/3 days for unlimited travel, 2/3 days, if it is a coupon ticket) If the usage is high, it is determined that the processing is performed on the station server 1040 side because the load is high when the processing is performed on the center server 1060 side.

  Next, the processing estimation / share creation unit 3080 estimates the total processing time of the ticket gate processing at the time of entrance and exit from the combination of tickets held for each user and the authentication method (S4020). The processing time calculation method, for example, checks the combination of owned tickets, and the fare calculation at entry is complicated when the boarding section partially crosses the commuter pass section or when connection discounts are applied Try to estimate the processing time longer. The time required for the authentication process can be calculated by applying a known value such as the average processing time required for the existing card medium authentication and the average processing time required for finger vein authentication.

Next, the process estimation / share creation unit 3080 reads the data recorded in the threshold value table 3110 and checks whether there is a process in which the time required for the ticket gate process for each ticket exceeds a predetermined threshold (S4030). . FIG. 8 shows a configuration example of the threshold table 3110. The threshold table 3110 stores items such as a response speed of the ticket gate (time from the card touching the reading unit until the gate is opened and closed) 8010, an allowable upper limit value 8020 of the communication network load, and an allowable upper limit value 8030 of the server load. doing. The process estimation / share creation unit 3080 checks whether or not there is a process exceeding the threshold 8020 for a ticket gate response speed in the processing time calculated above. If there is, the station server 1040 creates a share plan for the ticket gate process. A cooperation request message is transmitted to the station server 1040 to wait for reception of a response message from the station server 1040 (S4040).

  As a method for creating a ticket sharing process sharing plan, for example, a process (for example, biometric authentication or fare calculation) having a long processing time according to the length of the processing time among processes that can be shared is performed by the station server 1040. Alternatively, the station server 1040 may be requested to perform a process with a short calculated processing time (for example, a ticket expiration check). Alternatively, depending on the amount of data required for the sharing process, a process with a small amount of data (for example, a fare calculation is a process with a large amount of data because fare table data is required in the station server 1040). The server 1040 may be requested. In S4030, the load amount of the center server 1060 and the communication networks 1030 and 1050 may be estimated from the number of tickets processed on the center server 1060 side, the number of stations, and the status update frequency, and it may be checked whether or not the threshold value is exceeded.

  In S4050, the process estimation / assignment creation unit 3080 checks whether the response message from the station server 1040 that requested the assignment process is cooperation approval, and determines that the response message is cooperation approval (S4050, Yes). The ticket information table 3090 and the sharing table 3100 necessary for the sharing process in the station server 1040 are created and transmitted (S4060), and the process ends (S4070). A configuration example of the sharing table 3100 is shown in FIG. The sharing table 3100 (the sharing table 2100 in the station server 1040) records the result of processing sharing requested from the center server 1060 to the station server 1040 for each user. For example, in the example of FIG. 9, for user ID 9010, a record in which a server 9020 responsible for authentication processing, a server 9030 responsible for entry / exit check processing, a server 9040 responsible for fare calculation processing, and a server 9050 responsible for fraudulent use check processing are associated with each other. Is recorded. Each server can be identified by an address assigned on the communication network, for example. In addition, you may add the other process included in a ticket gate process as an item recorded on a record.

  On the other hand, if it is determined in S4030 that there is no processing exceeding the predetermined threshold (S4030, No), the process estimation / share creation unit 3080 determines the ticket information table 3090 related to the ticket determined to be processed in the station server 1040 in S4010 (station server). In 1040, a ticket information table 2090) is created and transmitted (S4060), and the process is terminated (S4070). If the response from the station server 1040 is refusal of cooperation in S4050, the center server 1060 creates another sharing plan by returning, for example, an item with a large processing amount to the center server 1060 among the processing requested to be shared to the station server 1040. (S4040), and the cooperation request to the station server 1040 is repeated until cooperation approval is obtained from all the request destination station servers 1040. According to the processing of the processing estimation / share creation unit 3080 described above, an excessive load is not applied to the center server 1060 and the communication networks 1030 and 1050 within the range of processing speed required for the automatic ticket gates installed in the station. As described above, the station server 1040 can share data processing. As a result, the data processing efficiency of the station service device management system 1 as a whole is improved.

  Next, a processing example of the entrance / exit processing unit 2070 will be described with reference to the flowchart of FIG. It is assumed that the entrance / exit processing unit 2070 is executed when the station server 1040 receives a ticket gate processing request message including a user ID, a device ID, and a type (entrance or participation) from the station service device 1020. Note that a message including not the user ID but the ID of the IC card possessed by the user may be received, and the IC card ID received by the station server 1040 may be converted into a user ID for processing.

  When the entry / exit processing unit 2070 starts processing in S5000, first, the ticket information table 2090 stored in the station server 1040 of the station is referred to, and the user included in the received message is stored in the table 2090. It is checked whether there is data corresponding to the ID (S5010). If it is determined that there is data corresponding to the user ID (S5010, Yes), a ticket gate process is performed in the station server 1040 (S5020). When it is determined that there is no data corresponding to the user ID (No in S5010), the entrance / exit processing unit 2070 refers to the sharing table 2100 and checks whether there is data corresponding to the user ID in the table 2100. (S5030). When it is determined that there is data corresponding to the user ID (S5030, Yes), in accordance with the contents of the table 2100, the other station server specified in the table 2100 is executed in parallel with the sharing process of the own station server 1040. Request processing sharing to 1040 (S5040). When it is determined in S5030 that the user ID does not exist in the sharing table (S5030, No), the entrance / exit processing unit 2070 requests the center server 1060 to perform a ticket gate process (S5050). After S5040 or S5050, the entrance / exit processing unit 2070 waits for reception of a response message from the server (S5060). When all the responses from the server are received or the processing of S5020 is completed, a gate opening / closing instruction of the ticket gate is transmitted to the automatic ticket gate as a processing result (S5070), and the processing is terminated (S5080). For example, in the example of FIG. 9, when executing the entry / exit processing of the user specified by the user ID 31578, the station server 14 executes the authentication processing and the entrance / exit check, the center server executes the fare calculation, and the unauthorized use check The processing is shared such that the station server 15 executes. According to the entrance / exit processing unit 2070 described above, it is possible to reduce the processing load of the center server 1060 by accepting the sharing request from the center server 1060, and when there is a possibility that the load of the center server 1060 may increase. Since the station server 1040 can share the processing, it is possible to improve the processing efficiency of the station service device management system 1 while preventing an overload as the station server 1040.

  Next, the sharing adjustment unit 2080 provided in the station server 1040 will be described. A processing example of the sharing adjustment unit 2080 is shown in the flowchart of FIG. Assume that the sharing adjustment unit 2080 executes data processing when a cooperation request message is received from the process estimation / share creation unit 3080 of the center server 1060. When the sharing adjustment unit 2080 starts processing in S6000, first, the processing time when the requested processing content is performed in the station server 1040 is estimated (S6010). Here, as the processing time calculation method, as described with respect to the processing estimation / share creation unit 3080 of the center server 1060, for example, a known value can be applied for each process content exemplified in the share table 2100. Next, the sharing adjustment unit 2080 reads the threshold with reference to the threshold table 2110, and checks whether or not the calculated or acquired processing time is expected to exceed the threshold (S6020). If it is determined that the threshold is not exceeded (No in S6020), the sharing adjustment unit 2080 adds the process to the sharing table 2100 (S6030), and then transmits a cooperation permission response message to the center server 1060 (S6040). ), The process ends (S6050). If it is determined that the threshold is exceeded (S6020, Yes), the sharing adjustment unit 2080 transmits a cooperation rejection response message to the center server 1060 (S6040), and ends the process (S6050).

According to the above-described sharing adjustment unit 2080, processing sharing in a possible range is accepted in response to the processing sharing request from the center server 1060. Therefore, the station service device 1020 such as an automatic ticket gate managed by the station server 1040 Is prevented from being delayed.

Next, an interface with the system administrator in this embodiment will be described. FIG. 10 shows an example of a threshold setting screen regarding the threshold table 3110, and FIG. 11 shows an example of a system operation status monitor screen. The threshold setting screen 10010 in FIG. 10 can be configured to be displayed by executing / operating the registration processing / monitoring unit 3070 of the center server 1060, for example. The system administrator can set thresholds such as a ticket gate response speed, a network load allowable upper limit value, and a server load allowable upper limit value using the screen 10010, but the thresholds that can be set are not limited to these. Absent. For example, it is possible to set an upper limit value when data such as user ticket information is multiplexed and stored, and an upper limit value when processing at the station server 1040 is distributed and multiplexed. Further, the system administrator uses the system operation status display screen 11010 in FIG. 11 to load the center server 1060, each station server 1040, and the communication networks 1030 and 1050 (CPU / memory usage rate of the server, usage rate of the communication network). Can be visualized and confirmed.

  As described above, in this embodiment, the processing example in the case where the sharing request is created on the side of the center server 1060 and then the cooperation is requested to the station server 1040 has been described. However, the present invention is not limited to this, and the sharing process may be determined only on the center server 1060 side. Also, the creation of the sharing process plan is not limited to nighttime, and may be executed in a timely manner, such as at regular intervals during the day. Further, when the load on the station server 1060 side exceeds a predetermined threshold, the process estimation / share creation unit 3080 may readjust the share process plan.

Example 2
Next, a second embodiment of the present invention will be described. In the present embodiment, a method for performing a high-speed ticket gate process when the boarding fare is paid by SF will be described. In this embodiment, as shown in FIG. 12, the sharing adjustment unit 2080, the sharing table 2100, and the threshold table 2110 are deleted from the configuration example of the station server 1040 shown in FIG. It has been added. FIG. 17 shows a configuration example of the address table 2120. The address table 2120 illustrated in FIG. 17 stores a user ID 15010 and a data storage destination 15020 related to the user in association with each other. The user ID 15010 is a unique identification code assigned to each user as in the first embodiment. The data storage destination 15020 stores the network address of the station server 1040. When the SF data is copied and arranged in a plurality of station servers 1040 and the processing is multiplexed between the station servers 1040, the data storage destination 15020 includes a plurality of station servers 1040 as illustrated in FIG. Address can be stored.

  For the center server 1060, the sharing table 3100 and the threshold value table 3110 are deleted from the configuration example shown in FIG. 3 in the first embodiment, and the address table 3120 and the usage history table 3130 are added. FIG. 16 shows a configuration example of the usage history table 3130. In the usage history table 3130 illustrated in FIG. 16, the user ID 14010, the SF usage date 14020, the SF usage location 14030, the SF processing type (entrance or participation) 14040, and the SF balance 14050 are recorded in association with each other. ing. The usage history table 3130 accumulates IC card usage histories related to a plurality of users during a certain period.

Next, a processing example of the processing estimation / share creation unit 3080 in the present embodiment will be described with reference to the flowchart of FIG. The processing estimation / share creation unit 3080 of the center server 1060 executes the processing of this embodiment for the next business day every day, for example, at night from the last train operation to the first train, as in the first embodiment. And When the process estimation / share creation unit 3080 starts the process in S12000, it first calculates the use frequency for each user ID by referring to the ticket information table 3090 and the use history table 3130, and the distributed arrangement plan according to the use frequency. Is created (S12010). Here, the usage frequency can be calculated by, for example, counting the number of usages during a certain period such as the last 6 months for each user ID. In the distributed arrangement plan, for example, if the number of uses during a certain period is less than a predetermined number, it can be determined that the IC card is not used so much, so that the load is small even if processing is performed on the center server 1060 side. It can be judged. On the other hand, for example, if the number of uses during a certain period is equal to or greater than a predetermined number, it is determined that the IC card is used relatively well.
It can be determined that the distributed processing on the 040 side is more efficient.

  Next, the processing estimate / share creation unit 3080 checks the normality of movement from the movement history for the user ID determined to be processed on the station server 1040 side in S12010, and creates a distributed arrangement plan according to the normality of the movement (S12020). Here, the normality of movement refers to data indicating a tendency such as a place (station) and time zone that each user uses relatively frequently. In this embodiment, for example, the SF history data during a certain period such as the last 6 months is counted by the number of times of use for each combination of weekday / holiday time zone, place, and processing, and the obtained frequency is a predetermined threshold ( It is determined that the normality is higher than the usage count or the ratio of the total usage count). As a distributed arrangement plan, for example, SF data of a user ID with high normality of a place is arranged on a station server 1040 close to a station determined to have high normality in order to improve the processing speed of the ticket gate processing. It can be configured to process. In addition, the SF data of a plurality of user IDs having high normality in time zones are processed in a distributed manner on a plurality of station servers 1040 so that the load is not concentrated on a specific station server 1040 in the obtained time zone. Can be configured.

  Next, the processing estimate / share creation unit 3080 creates a ticket information table 2090 and an address table 2120 for each station server 1040 based on the distributed processing plan created in S12020, and distributes each table to each station server 1040 ( In step S12030, the process ends (S12040).

  Next, a processing example of the entrance / exit processing unit 2070 in the station server 1040 according to the present embodiment will be described with reference to the flowchart of FIG. The entrance / exit processing unit 2070 is executed when a ticket gate processing request message including a user ID, a device ID, and a type (entrance or participation) is received from the station equipment 1020 (automatic ticket gate in this embodiment). .

  When the entry / exit processing unit 2070 starts processing in S13000, first, the address storage 2120 of the station server 1040 to which the entry / exit processing unit 2070 belongs is referred to, and the data storage destination corresponding to the user ID in the ticket processing request message received from the automatic ticket gate 15020 is searched, and it is checked whether the searched data storage destination server is the own station server 1040 or another station server 1040 other than the own station server 1040 (S13010). If it is determined that the station server 1040 is another station (S13010, No), the entrance / exit processing unit 2070 transfers the ticket processing request message to be processed to the address of the other station server 1040, and ends the process. (S13060).

  When it is determined that the retrieved data storage destination server is the own station server 1040 (S13010, Yes), the entrance / exit processing unit 2070 uses the ticket information table 2090 in the own station server 1040 to use the own station server. The ticket gate process is executed in 1040 (S13030), and the gate opening / closing instruction of the automatic ticket gate as the message transmission source is transmitted to the automatic ticket gate machine as a result of the ticket gate process (S13040). Next, the entry processing unit 2070 refers to the address table 2120, searches for the data storage destination 15020 corresponding to the user ID in the ticket gate processing request message, and if there is a data storage destination 15020 other than the own station server 1040, The ticket information related to the user ID is transmitted to the address of the station server 1040 which is a data storage destination other than the own station server 1040, the data is synchronized (S13050), and the process is terminated (S13060).

Here, the data synchronization processing of S13050 may be performed not at the end of the processing of S13040 but at another timing. In general, data synchronization regarding a specific user may be executed until the next time the IC card possessed by the user is used in another automatic ticket checker. Therefore, for example, the station server 1040 within the minimum required time from the station that performed the admission process to the nearest station.
The data synchronization processing may be performed at a timing when the load on the train is not high (for example, not when there are many ticket gate participants immediately after arrival of the train). According to the second embodiment of the present invention described above, ticket information is multiplexed and stored in a plurality of station servers 1040 using a parameter called normality indicating a tendency related to the use history of a station used by a user. Thus, the ticket gate process for each user can be performed more efficiently.

  In addition, Example 2 demonstrated above can also be comprised so that it may adapt to events, such as a driving postponement resulting from the transportation obstacle of a transportation system. For example, it is considered that the user often moves in a pattern different from the normal user movement pattern at the time of railway transportation failure. In this case, for example, the center server 1060 may acquire transportation fault information from a separate operation management system, and from the operation stoppage section included in the information, the user may change to another company's line at a peripheral station in the section. Therefore, it is possible to prevent load concentration on a specific station server 1040 by distributing the ticket information to the station servers 1040 of the surrounding stations.

DESCRIPTION OF SYMBOLS 1 ... Station service equipment management system 1010 ... IC card, 1020 ... Station service equipment 1030, 1050 ... Communication network, 1040 ... Station server 1060 ... Center server, 2010, 3010 ... Main control part 2020, 3020 ... Input part 2030, 3030 ... Output unit 2040, 3040 ... Communication processing unit 2050, 3050 ... Storage management unit 2070 ... Entrance / exit processing unit 2080 ... Sharing adjustment unit 2090, 3090 ... Ticket information table 2100, 3100 ... Sharing table 2110, 3110 ... Threshold table 3070 ... Registration processing Monitor unit 3080 ... Processing estimation / share creation unit 2120, 3120 ... Address table 3130 ... Usage history table

Claims (10)

A ticket information processing method executed by a plurality of information processing devices for processing ticket information, which is information relating to a ticket used when using a transportation facility held by a transportation user,
Storing each ticket information for each user;
With respect to the individual information included in the ticket information of each user, the first information processing apparatus and the other of the plurality of information processing apparatuses, respectively, according to predetermined determination criteria determined according to the processing load of each individual information Determine which of the information processing devices to process,
When processing time of the individual information by the first information processing device is calculated and it is determined that the calculated processing time exceeds a predetermined threshold, processing of the individual information is further processed in another information processing device. Share,
Ticket information processing method. The ticket information processing method according to claim 1,
The other information processing apparatus determines whether or not the ticket information of the user to be processed is held, and when determining that the other information processing apparatus holds the ticket information, the other information processing apparatus determines that it does not hold the ticket information by itself. If the process related to the user is further allocated to itself, and if it is determined that it is allocated to itself, the allocated process is executed, and if it is determined that the process is not allocated, the first information A ticket information processing method that transmits a processing request for ticket information to a processing device. The ticket information processing method according to claim 1,
From the ticket information of each user, according to the effective quantity for each type of ticket included in the ticket information, the number of stations that can be entered or exited with the ticket, and the update frequency of the state of the ticket A ticket information processing method for determining whether the processing of the individual information is performed by the first information processing apparatus or the other information processing apparatus. The ticket information processing method according to claim 1,
When it is determined that the processing time of the ticket information in the other information processing apparatus exceeds a predetermined threshold, the other information processing apparatus executes a process assigned to the first information processing apparatus A ticket information processing method that responds that it cannot be performed. The ticket information processing method according to claim 1,
As a criterion for determining whether the processing sharing for the other information processing apparatus is possible, the response speed of the automatic ticket gate installed at the station, and the connection between the first information processing apparatus and the other information processing apparatus A ticket information processing method configured to be able to set an allowable load limit of a communication network. A ticket information processing method executed by a plurality of information processing devices for processing ticket information, which is information relating to a ticket used when using a transportation facility held by a transportation user,
Storing each ticket information for each user;
With respect to the individual information included in the ticket information of each user, the first information processing apparatus and the other of the plurality of information processing apparatuses, respectively, according to predetermined determination criteria determined according to the processing load of each individual information Determine which of the information processing devices to process,
According to the determined sharing, the user's ticket information to which processing is shared is stored in the corresponding other information processing device,
Synchronizing the ticket information of the user stored in the other information processing apparatus with the ticket information stored in the first information processing apparatus at a predetermined timing;
Ticket information processing method. The ticket information processing method according to claim 6,
A ticket information processing method for determining the other information processing apparatus for storing the ticket information according to a use frequency for each ticket information recording medium held by each user. The ticket information processing method according to claim 6,
According to the usage pattern which is the frequency of processing contents of either entry or exit, and the usage location, usage time zone of the recording medium recorded for each ticket information recording medium held by each user A ticket gate processing method for determining the other information processing apparatus for storing ticket information. The ticket information processing method according to claim 6,
When a transportation failure occurs in the transportation, a section where operation is stopped due to the transportation failure and a station that is considered to increase the processing amount of ticket information are determined, and the ticket information is determined according to the result. A ticket information processing method for determining the other information processing device to be stored. A ticket information processing system including a plurality of information processing devices for processing ticket information, which is information related to a ticket used when a user of a transportation facility uses the transportation facility,
A ticket information storage unit that stores the ticket information for each user;
With respect to the individual information included in the ticket information of each user, the first information processing apparatus and the other of the plurality of information processing apparatuses, respectively, according to predetermined determination criteria determined according to the processing load of each individual information Determine which of the information processing devices to process,
When processing time of the individual information by the first information processing device is calculated and it is determined that the calculated processing time exceeds a predetermined threshold, processing of the individual information is further processed in another information processing device. A shared processing unit to share,
Ticket information processing system.