JP4588492B2 - Data collection and distribution system - Google Patents

Description

  The present invention relates to a data collection / distribution system in which a plurality of payment terminal devices and a data collection / delivery server for transferring collection / delivery data between the payment terminal devices are connected via a network, and in particular, a plurality of payment terminals. The present invention relates to a data collection / distribution system capable of efficiently exchanging collection / distribution data without degrading the quality of a service to be originally performed when the collection / delivery data is transferred between the apparatus and the data collection / delivery server.

  Recently, IC cards are being used in various fields such as electronic money, focusing on the safety and convenience of IC cards. This IC card is a card in which an IC chip is embedded in a plastic card. A particularly convenient non-contact IC card is an IC card terminal (reader / writer) using an antenna coil provided in the plastic card. ) To exchange data without contact.

  Specifically, when a non-contact IC card is held over a portion called a holding part of an IC card terminal (payment terminal device), the non-contact IC card receives electromagnetic waves from the holding part to generate electric power, and the IC card A command transmitted from a terminal (hereinafter simply referred to as “terminal”) is received, analyzed, processed, and the result is transmitted. For example, Patent Document 1 discloses an invention relating to the holding portion of the terminal.

  Focusing on the effectiveness of such an IC card, recently, as shown in FIG. 9, terminals are often provided at chain stores or the like. In the figure, four terminals are arranged in each of the A area, B area and C area of a large-scale store, and six terminals are arranged in the D area, and a center server connected to each terminal via a LAN or the like is displayed in the center area. The case where it is provided is shown. The reason why each terminal is connected to the center server is to enable collecting data such as transaction logs of each terminal to be transmitted to the center server, and distribution data such as firmware to be transmitted from the center server to each terminal. is there.

JP 2004-355580 A

  However, when the system shown in FIG. 9 is constructed, direct access from each terminal is concentrated on the data collection / delivery server (hereinafter referred to as “center server”), and the center server becomes a bottleneck and functions of the entire system. There is a problem that will decrease.

  Specifically, even if the center server can process multiple terminals at the same time in a time-sharing manner, the number of terminals that the center server can handle at the same time is limited, and processing is performed in parallel with too many terminals. Will cause a processing delay. Originally, since collection and distribution data such as transaction logs transmitted from the terminal to the center server has a large amount of data, the function of the center server and the communication with the center server become the bottleneck of the system.

  In addition, since each terminal cannot perform settlement processing with the IC card during normal collection / delivery data processing, if it takes time to transfer such collection / delivery data, the settlement service to be originally provided is This delays the service, resulting in a decline in service quality. The reason why payment processing with the IC card cannot be performed during the collection and distribution data processing is that the transaction is stopped for the transaction counting (tightening processing) at the terminal, and the counting (log) information is confirmed and transmitted. Because it is necessary to do. In addition, since the log capacity is limited and cannot be stored indefinitely, it is necessary to periodically transmit a transaction log or the like as transaction confirmation information at the individual terminal to the center server.

  For this reason, when collecting and delivering data between multiple terminals and the center, it is extremely important how to efficiently send and receive the collected and delivered data without degrading the quality of the service that should be performed. It has become.

  This invention is made in view of the said subject (problem), and when performing collection delivery data delivery between a some payment terminal device and a data collection delivery server, the quality deterioration of the service which should be performed originally An object of the present invention is to provide a data collection / delivery system capable of efficiently exchanging collection / distribution data without incurring an error.

In order to solve the above-described problems, the present invention provides a network formed in multiple layers by connecting a LAN to which one or a plurality of settlement terminal devices and a predetermined relay server are connected to another LAN. A data collection / delivery system for delivering data from a data collection / delivery server to a settlement terminal device connected to each LAN, wherein the relay server is the data collection / delivery server or a higher-order relay close to the data collection / delivery server Distribution data storage means for storing common data that does not depend on each payment terminal apparatus received from the server as distribution data, and one or a plurality of payment terminals connected to the common data stored in the distribution data storage means on the same LAN Conversion means for converting into individual data suitable for the device, and one or a plurality of terminal devices connected on the same LAN. Delivering the converted individual data by, for lower relay server connected with the LAN, characterized in that a delivery control means for controlling so as to deliver it to the common data.

  Further, the present invention is the above invention, wherein the relay server further comprises management means for managing one or a plurality of terminal devices connected on the same LAN and a lower-level relay server connected to the LAN. Features.

  Further, the present invention is characterized in that, in the above invention, the data collection and distribution server manages route information from each settlement terminal device to the data collection and distribution server.

  Further, the present invention provides the management information managed by the management means of the relay server connected to the predetermined LAN when the predetermined settlement terminal device is newly connected to the predetermined LAN. The route information related to the settlement terminal device is added to the route information managed on the data collection and distribution server.

  Further, the present invention provides the data collection and distribution server according to the above invention, wherein when the route information related to the same payment terminal device as the payment terminal device to which route information is newly added has been registered, the payment terminal device It is considered that the route information that has been relocated is deleted, and the registered route information is deleted, and the relay server connected to the LAN before relocation is instructed to be excluded from the management target. To do.

According to the present invention, the relay server stores, as distribution data, common data that does not depend on each settlement terminal device received from the data collection / delivery server or a higher-order relay server close to the data collection / delivery server. The data is converted into individual data suitable for one or a plurality of payment terminal devices connected on the same LAN, and the converted individual data is distributed to one or a plurality of terminal devices connected on the same LAN. Since the common data is distributed and controlled as it is for the lower-level relay server connected to the LAN, the load and network of the data collection / distribution server can be changed even when the device configuration of each settlement terminal device is different. It is possible to efficiently provide individual data suitable for each settlement terminal device while reducing the burden on the customer.

  In addition, according to the present invention, the relay server is configured to manage one or a plurality of terminal devices connected to the same LAN and the lower-level relay server connected to the LAN. Can be reduced.

  Further, according to the present invention, the data collection / delivery server is configured to manage route information from each settlement terminal device to the data collection / distribution server, respectively. The route to the terminal device can be centrally managed.

  Further, according to the present invention, when a predetermined settlement terminal device is newly connected to a predetermined LAN, the management information of the relay server connected to the predetermined LAN is updated and the data collection / delivery server Since the route information related to the payment terminal device is added to the route information managed by the mobile phone, it is possible to respond flexibly and smoothly even when a new payment terminal device is provided at any location. it can.

  Further, according to the present invention, when the route information related to the same payment terminal device as the payment terminal device to which the route information is newly added has been registered, the data collection / delivery server is relocated to the payment terminal device. The registered route information is deleted, and the relay server connected to the LAN before relocation is instructed to exclude the payment terminal device from the management target. Even when the terminal device is replaced and replaced with another part, it is possible to respond flexibly and smoothly.

  Exemplary embodiments of a data collection / delivery system according to the present invention will be described below in detail with reference to the accompanying drawings. Example 1 below shows a case where the collected data in the payment terminal device (terminal) is uploaded to the data collection / delivery server (center server), and Example 2 shows a case where the distribution data of the center server is downloaded to each device. In the third embodiment, it is assumed that the terminals are rearranged. In the following description, the case where data is distributed from the center server to each terminal is called download, and the case where data is downloaded from each terminal to the center server is called upload.

  First, the system configuration of the data collection and distribution system according to the first embodiment and the concept when uploading the collected data will be described. FIG. 1 is a diagram illustrating a system configuration of the data collection and distribution system according to the first embodiment. Here, for convenience of explanation, it is assumed that only two relay servers are provided.

  As shown in the figure, in this data collection and distribution system, a center server S is connected to a relay server A via a router RA, and the relay server A and terminals A1 to A3 are connected to a LAN (Local Area Network) AA. The LANAA is connected to the relay server B via the router RB, and the relay server B and the terminals B1 to B3 are connected to the LANBB.

  Here, such a data collection and distribution system does not connect each terminal directly to the center server as in the prior art shown in FIG. 9, but intervenes relay servers A and B between the center server S and each terminal. The characteristic is in the point made to do.

  Conventionally, since collected data such as transaction log data generated as a result of the payment process is stored in the terminals A1 to A3 and B1 to B3 that perform the payment process with the IC card, the collected data is stored in the center server S. Must be uploaded regularly. However, as shown in FIG. 9, if the center server S is directly connected to each of the terminals A1 to A3 and B1 to B3, the center server S becomes a bottleneck and becomes an obstruction factor when uploading the collected data. . In addition, each of the terminals A1 to A3 and B1 to B3 cannot perform the settlement process, which is the original business, during the normal collection data upload process, which causes service degradation. Therefore, in the first embodiment, each terminal A1 to A3 quickly transfers the collected data to the relay server A, and each terminal B1 to B3 quickly transfers the collected data to the relay server B, so that each terminal A1 to A3. And B1 to B3 are configured so as to be able to sufficiently perform the settlement processing, which is originally a business.

  The terminals A1 to A3 and B1 to B3 are terminal devices that perform electronic money settlement processing with the IC card 30, and store transaction log data in the device every time transaction processing is performed. Here, each of the terminals A1 to A3 and B1 to B3 does not perform time-sharing processing, but performs processing for uploading collected data such as transaction log data and processing for downloading distribution data such as firmware. Shall not be able to process the original transaction. Although the payment process using electronic money has been described here, the payment type is not a characteristic part of the present embodiment and may be any type.

  The center server S is a data collection / delivery server that exchanges collection / delivery data with the terminals A1 to A3 and B1 to B3. That is, the center server S acquires and holds collected data such as transaction log data stored in the terminals A1 to A3 and B1 to B3, and distributes distribution data such as firmware to the terminals A1 to A3 and Download processing to B1 to B3.

  The center server S uses the route table 20 to manage routes to the terminals A1 to A3 and B1 to B3. Specifically, since it is via the relay server A to reach the terminal A1, “A” is stored as the route information of this terminal A1, and since it is via the relay servers A and B to reach the terminal B1, this “A → B” is stored as route information of the terminal B1. Thereby, the center server S can grasp | ascertain what relay server is passed through to each terminal A1-A3 and B1-B3.

  The relay servers A and B are devices that interpose between the terminals A1 to A3 and B1 to B3 and the center server S and relay collected and distributed data. The relay server A has a management table 12a for managing the terminal under management and the relay server as shown in the figure. Specifically, the management table 12a includes a terminal connected on the LANAA. A1 to A3 and relay server B are registered. Similarly, terminals B1 to B3 connected on the LANBB are registered in the management table 12b of the relay server B. The reason why the management tables 12a and 12b are provided is to clarify the delivery destination when the collection / delivery data is delivered.

  Next, the processing concept of uploading transaction data (collection data) stored in the terminal to the center server S will be described with reference to FIG. Here, for convenience of explanation, a case where transaction log data 11a stored in the terminals A1 and B1 is uploaded to the center server S will be described as an example.

  As shown in FIG. 1, the transaction log data LB1 of the terminal B1 is first transmitted to the relay server B via the LANBB. After the transmission of the transaction log data LB1, the terminal B1 immediately settles the transaction between the IC card 30 and the electronic money. Is possible. Thereafter, the relay server B transfers the transaction log data LB1 received from the terminal B1 to the relay server A located on the upper side (side closer to the center server S).

  Similarly, the transaction log data LA1 of the terminal A1 is transmitted to the relay server A via the LANAA, and the relay server A receives the transaction log data LB1 of the terminal B1 received via the relay server B and the terminal A1. The transaction log data LA1 is collected and transmitted to the center server S.

  Although the case where the transaction log data of the terminal A1 and the terminal B1 is collected is shown here, each relay server A and B actually stores in the managed terminal while referring to the management tables 12a and 12b, respectively. Each transaction log data obtained is acquired and finally transmitted to the center server S.

  Next, a specific configuration of the relay server A illustrated in FIG. 1 will be described. FIG. 2 is a functional block diagram showing the configuration of the relay server A shown in FIG. For convenience of explanation, the configuration of the relay server A is shown here, but the configuration of the relay server B shown in FIG. 1 is the same. As shown in the figure, the relay server A includes an interface unit 10, a storage unit 11, a management table 12a, a transaction log processing unit 13, an application processing unit 14, a connection request processing unit 15, and a control unit. 16.

  The interface unit 10 is an interface unit that plays the role of an interface connected to the LANAA and the role of an interface connected to the router RA. Specifically, the interface unit 10 performs communication processing according to the TCP / IP protocol.

  The storage unit 11 is formed by a storage medium such as a hard disk device, and stores transaction log data LOG, common application data APL, and the like therein. As described above, the transaction log data LOG includes the transaction log data LA1 generated when the terminals A1 to A3 perform transaction processing using the IC card 30 and electronic money settlement, and the terminals B1 to B3 received via the relay server B. Log data formed from the transaction log data LB1. The common application data APL is a program distributed by the center server S to each terminal, although the detailed description thereof will be omitted in the second embodiment to be described in the second embodiment.

  The management table 12a is a table for managing the terminals A1 to A3 connected to the LANAA and the relay server B on the lower side (the side farther from the center server S) connected to the LANAA. It also manages the specified MAC address and the like.

  The transaction log processing unit 13 is a processing unit that performs processing related to transaction log data that is collected data. Specifically, the transaction log processing unit 13 collects transaction log data LA1 from the terminals A1 to A3 managed on the management table 12a. A process for receiving transaction log data LB1 transferred from the relay server B managed on the management table 12a, a process for transferring the transaction log data LA1 and LB1 to the center server S as transaction log data LOG, and the like are performed. The transaction log processing unit 13 can also handle collected data other than transaction log data such as event data.

  The application processing unit 14 is a processing unit that performs processing related to an application delivered from the center server S to each of the terminals A1 to A3 and B1 to B3. Specifically, when a generalized program called common application data APL is received from the center server S, the common application data APL is transferred to the lower relay server B and the common application data APL is transferred to each A process of converting into individual application data suitable for each of the terminals A1 to A3 and transmitting it to each of the terminals A1 to A3 is performed. The detailed description of the application processing unit 14 will be described in a second embodiment described later.

  The connection request processing unit 15 is a processing unit that performs processing related to a connection request that is performed when a terminal is newly connected to LANAA or LANBB. Specifically, the connection request processing unit 15 receives a connection request from a terminal that is newly connected to LANAA. Is received, the new terminal is registered in the management table 12a, and the fact is notified to the center server S. This is to change the route table 20 on the center server S. For example, when the terminal A1 on the LANAA is reconnected to the LANBB, a deletion instruction comes from the center server S. At that time, a process of deleting the terminal A1 from the management table 12a is performed. Detailed processing of the connection request processing unit 15 will be described in a third embodiment to be described later.

  The control unit 16 is a control unit that performs overall control of the relay server A. Specifically, the update process of the management table 12a, the data read / write process to the storage unit 11, the transaction log data processing unit 13, the application processing unit 14 and activation control of the connection request processing unit 15, and data transmission / reception control via the router RA and LANAA.

  Next, a processing procedure in the case of uploading transaction log data LA1 from the terminal A1 shown in FIG. 1 to the center server S will be described. FIG. 3 is a sequence diagram showing a processing procedure when transaction log data LA1 is uploaded from the terminal A1 shown in FIG. 1 to the center server S.

  As shown in the figure, the terminal A1 is initially in a standby state for an electronic money transaction by the IC card 30 (step S101), and if the transaction log transmission operation is not performed (No in step S102), the standby state is continued. The transaction log transmission operation can be performed on the relay server A or the center server S in addition to being performed on the terminal A1. When such a transaction log transmission operation is performed on these devices, a transaction log transmission command is sent to the terminal A1, and processing similar to the transaction log transmission operation shown in step S102 is started.

  If a transaction log transmission operation is performed in this standby state (Yes at Step S102), the terminal A1 adds header information to the transaction log data LA1 and transmits it to the relay server A (Step S103). Such header information includes at least information for identifying the transaction log data LA1 of the terminal A1, and the transaction log data LA1 is transmitted together with this header information.

  Then, if the transaction log data LA1 is received while the relay server A is in a reception standby state (step S105), the transaction log processing unit 13 stores the transaction log data LA1 in the storage unit 11 (step S106). Thereafter, it is determined whether or not the transaction log should be transferred (step S107), and the header information indicating that the transaction log data has passed through the relay server A is added and transmitted to the center server S (step S108). (Step S109). That is, the header information includes “A1” indicating the transmission source terminal A1 and “A” indicating the intervention of the relay server A. When the transfer is completed (Yes at Step S109), the process returns to the reception standby state shown at Step S105. Note that if the reception of the transaction log data LA1 cannot be completed or is not received, the process proceeds to step S107 as it is without storing the log in step S106.

  If the transaction log data A1 is received while the center server S is in the reception standby state (step S110), the received transaction log data A1 is stored (step S111), and based on the header information as necessary. Then, the contents of the route table are updated (step S112). By looking at the header information, you can see which terminal's transaction log has reached via which relay server, so use this information to check the system configuration regularly and match the actual connection form. Because. If reception of the transaction log data LA1 cannot be completed or has not been received, the process proceeds to step S110 and the reception standby state is maintained.

  By performing the above-described series of processing, the transaction log data LA1 of the terminal A1 can be quickly transferred to the relay server A, and the transaction processing with the IC card 30 that should be performed can be efficiently performed while leaving the transfer to the relay server A. . In addition, although the case where the transaction log data A1 of the terminal A1 is uploaded to the center server S is shown here, the same processing is performed when the transaction log data of other terminals is uploaded.

  As described above, in the first embodiment, the center server S is connected to the relay server A via the router RA, the relay server A and the terminals A1 to A3 are connected to the LANAA, and the LANAA is connected via the router RB. By connecting the relay server B and the relay server B and the terminals B1 to B3 to the LANBB, the relay servers A and B are interposed between the terminals A1 to A3 and B1 to B3 and the center server S. Since the relay servers A and B are configured to take over the transmission of transaction log data from the terminals A1 to A3 and B1 to B3 to the center server S, the devices A1 to A3 and B1 to B3 should be originally performed. It is possible to spend a lot of time for the settlement process, and thus it is possible to efficiently prevent deterioration in the quality of services.

  In addition, although the case where transaction log data was made into the transfer object was shown in the present Example 1, this invention is not limited to this, The event toward the center server S from terminal A1-A3 and B1-B3 The same applies to various collected data such as logs.

  By the way, in the said Example 1, although the case where the transaction log data of each terminal A1-A3 and B1-B3 was transmitted to the center server S as concentration data was shown, conversely, each terminal A1-A3 and Distribution data can also be distributed to B1 to B3. In the second embodiment, a case where application data is distributed from the center server S to each terminal A1 to A3 and B1 to B3 will be described. Since the configuration of the relay server A is the same as that shown in FIG. 2 described in the first embodiment, the description thereof is omitted here.

  A concept for downloading distribution data on the data collection and distribution system according to the second embodiment will be described. FIG. 4 is a conceptual diagram when the distribution data is downloaded on the data collection and distribution system according to the second embodiment. As shown in the figure, the system connection in this case is the same as that of FIG.

  Here, the center server S holds common application data APL that is a source of applications distributed to the terminals A1 to A3 and B1 to B3, and transmits the common application data APL to the relay server A first. The relay server A that has received the common application data APL transfers the common application data APL to the relay server B and converts the common application data APL into individual application data PROA1 to PROA3 suitable for the terminals A1 to A3. Then, the converted individual application data PROA1 to PROA3 are distributed to the terminals A1 to A3. Similarly, the relay server B that has received the common application data APL converts the common application data APL into individual application data PROB1 to PROB3 suitable for the terminals B1 to B3, and converts the converted individual application data PROB1 to PROB3 to the terminals. Delivered to B1 to B3.

  That is, in this data collection and distribution system, the relay servers A and B are transferred in the form of the original common application data APL, and then distributed to the terminals A1 to A3 and B1 to B3 according to the terminals. Change to a program of the form. The reason why such a configuration is adopted is based on the assumption that the terminals A1 to A3 and B1 to B3 are not the same but have different restrictions on the operating programs. Therefore, for example, when the terminals A1 to A3 are different from each other, the relay server A needs to generate individual application data PROA1 to PROA3 corresponding to the terminals A1 to A3. For example, the common application data APL is a program source file, and the individual application data can be an execution file according to the individual circumstances of each terminal.

  Therefore, as described above, when the application processing unit 14 shown in FIG. 2 receives a generalized program called common application data APL from the center server S, the common processing data APL is relayed to the lower side. In addition to transferring to the server B, the common application data APL is converted into individual application data PROA1 to PROA3 suitable for the terminals A1 to A3 and transmitted to the terminals A1 to A3.

  Next, a processing procedure of the application processing unit 14 of the relay servers A and B according to the second embodiment will be described. FIG. 5 is a flowchart illustrating the processing procedure of the application processing unit of the relay servers A and B according to the second embodiment.

  As shown in the figure, when the relay server A receives the common application data APL (step S201), it is confirmed whether or not there is a lower relay server under the subordinate server (step S202). If a lower relay server exists (Yes at step S202), the common application data APL is transferred to the lower relay server (step S203).

  That is, in the case of the relay server A, since the relay server B which is a lower side relay server exists, the common application data APL is transferred to the relay server B according to such processing. Since there is no server, the common application data APL is not transferred.

  Thereafter, the application processing unit 14 refers to the management table 12a to check whether there is a subordinate terminal (step S204). If there are subordinate terminals (Yes in step S204), the application processing unit 14 determines whether each subordinate terminal exists. The adapted individual application data is generated (step S205), and the generated individual application data is transmitted to the corresponding terminal (step S206).

  In this example, since the relay server A has terminals A1 to A3 under its control and the relay server B has terminals B1 to B3 under its control, the individual application data PROA1 to PROA3 suitable for the respective terminals in both relay servers. And PROB1 to PROB3 are generated.

  In the case of an encryption application, the relay server A decrypts the common encryption application received from the center server S and transmits it to each lower terminal, and transmits the common encryption application to the lower relay server B as it is. Will do.

  As described above, in the second embodiment, the relay servers A and B are transferred in the form of the original common application data APL, and then distributed to the terminals A1 to A3 and B1 to B3, respectively. Therefore, the individual application data PROA1 to PROA3 and PROB1 to PROB3 according to the circumstances of each terminal can be efficiently distributed.

  In the second embodiment, the program is distributed while being converted from the common application data APL to the individual application data. However, other data can be distributed in the same procedure. Further, since the center server S has the route table 20, the individual application data can be distributed only to the corresponding terminal using the route table 20.

  In the first and second embodiments, the description has been made on the assumption that the system configuration is fixed. However, in actuality, it is assumed that the position of the terminal is moved or a new terminal is newly arranged in accordance with the rearrangement. Is done. Therefore, in the third embodiment, terminal movement in which a predetermined terminal connected to a certain LAN is connected to another LAN will be described.

  A concept when a terminal is moved on the data collection and distribution system according to the third embodiment will be described. FIG. 6 is a conceptual diagram when the terminal is moved on the data collection and distribution system according to the third embodiment. This figure shows a case where the terminal A3 on the LANAA is removed and the terminal is attached as a terminal B4 on the LANBB along with the layout change.

  In such a case, when the terminal B4 is mounted on the LANBB and the power is turned on, the terminal B4 makes a connection request including the MAC address of the terminal B4 to the relay server B, and the relay server B receiving the connection request Based on the connection request, the terminal B4 is registered in the management table 12b, and the fact is notified to the center server S via the relay server A. Upon receiving this notification, the center server S registers the terminal B4 in the route table 20, deletes the terminal having the same MAC address from the route table 20, and sends it from the management table 12a to the relay server A that manages the corresponding terminal A3. The terminal A3 is instructed to be deleted. In response to this instruction, the relay server A deletes the terminal A3 from the management table 12a. As a result, the management table of each relay server and the route table 20 of the center server S can be updated to conform to the latest connection form.

  Therefore, when receiving a connection request from a terminal newly connected to the LAN, the connection request processing unit 15 shown in FIG. 2 registers the new terminal in the management table 12a and informs the center server S of that fact. When the notification is received and a deletion instruction is received from the center server S, processing for deleting the terminal from the management table 12a is performed.

  Next, the processing procedure of each device when the terminal B4 is connected to the LANBB will be described. FIG. 7 is a sequence diagram showing a processing procedure of each device when the terminal B4 is connected to the LANBB. As shown in the figure, if the terminal B4 is connected to the LANBB (step S301), the terminal B4 makes a connection request to the relay server B (step S302). This connection request includes the MAC address of the own device.

  Thereafter, the relay server B adds the terminal B4 to the management table 12b (step S303), adds header information to the effect that the relay server B passes through the relay server B, and forwards the header information to the upper relay server A (step S304). Similarly, the relay server A adds header information to the effect that it passes through its own device A, and transmits the header information to the upper center server S (step S305).

  The center server S that has received such data adds the terminal B4 to the route table 20 (step S306) and confirms whether a terminal having the same MAC address is registered in the route table 20 (step S307). . As a result, if there are those having the same MAC address (Yes at Step S307), it is assumed that the terminal has been moved, and the corresponding one is deleted from the route table 20 (Step S308) and becomes a deletion target. A deletion instruction is given to the relay server A that manages the terminal (step S309).

  Receiving this deletion instruction, the relay server A deletes the corresponding terminal from the management table 12a (step S310), then sends a deletion completion notification to the center server S (step S311), and receives the deletion completion notification. S sends a completion notification to terminal B4 via relay server A and relay server B (steps S312 to S314).

  As described above, in the third embodiment, the relay server management table and the center server S route table 20 are updated and adapted to the latest state when the terminal moves, so that the layout can be changed. It is possible to respond smoothly and flexibly to the accompanying terminal movement.

  In the third embodiment, the case of moving a terminal has been described. However, the present invention is not limited to this, and the same processing can be performed when a new terminal is added. However, when only the terminal is removed, the removal operation by the administrator is required, and the management table and the route table are changed in response to the removal operation.

  In the first to third embodiments, the case where the system configuration is simple is shown to simplify the description. However, as shown in FIG. 8, the A area, B area, C area, D area, E area, Even when the relay servers A to I are provided in the F area and the G area, the first to third embodiments can be similarly applied.

  In addition, time series management and collection and distribution (multiple data management of relay server) of multiple distribution data will be explained. Multiple distribution data for the same terminal is managed in time series by the relay server and distributed in time series when connected. (Pooling in the case of lower path failure), when multiple collected data from the same terminal are collected before being sent to the upper relay server, these are managed in time series and It is transmitted at the time of connection (pooling in the case of upper path failure). That is, when the upper route and the lower route are restored, the accumulated data is transmitted in time series.

  The data collection and distribution system according to the present invention efficiently collects and distributes data without causing deterioration in the quality of the service that should be originally performed when the collection and distribution data is transferred between a plurality of payment terminal devices and the data collection and distribution server. It is useful when giving and receiving.

1 is a diagram illustrating a system configuration of a data collection and distribution system according to a first embodiment. It is a functional block diagram which shows the structure of the relay server A shown in FIG. It is a sequence diagram which shows the process sequence in the case of uploading transaction log data LA1 from the terminal A1 shown in FIG. 1 to the center server S. It is a conceptual diagram in the case of downloading distribution data on the data collection and distribution system according to the second embodiment. It is a flowchart which shows the process sequence of the application process part of the relay servers A and B which concern on the present Example 2. It is a conceptual diagram when a terminal is moved on the data collection and distribution system according to the third embodiment. It is a sequence diagram which shows the process sequence of each apparatus at the time of connecting the terminal B4 to LANBB. It is a figure which shows an example of the actual system configuration | structure of a data collection and delivery system. It is a figure which shows the system configuration | structure of the conventional data collection delivery system.

Explanation of symbols

S Center server A, B Relay server AA, BB LAN
A1 to A3, B1 to B3 terminals (payment terminal devices)
LA1, LB1, LOG Transaction log data RA, RB router APL Common application data 10 Interface unit 11 Storage unit 12a, 12b Management table 13 Transaction log processing unit 14 Application processing unit 15 Connection request processing unit 20 Route table 30 IC card

Claims (5)

Payment connected to each LAN from the data collection / distribution server via a network formed in multiple layers by connecting a LAN connected with one or a plurality of payment terminal devices and a predetermined relay server to another LAN. A data collection and distribution system for distributing data to a terminal device,
The relay server is
Distribution data storage means for storing, as distribution data, common data that does not depend on each settlement terminal device received from the data collection / delivery server or a higher-order relay server close to the data collection / delivery server;
Conversion means for converting the common data stored in the distribution data storage means into individual data suitable for one or more payment terminal devices connected on the same LAN;
Distribute the individual data converted by the conversion means to one or a plurality of terminal devices connected on the same LAN, and distribute the common data as it is to the lower-level relay server connected to the LAN. Distribution control means for controlling
Data collection and delivery system, characterized in that with. 2. The data according to claim 1 , wherein the relay server further includes a management unit that manages one or a plurality of terminal devices connected to the same LAN and a lower-level relay server connected to the LAN. Collection and delivery system. The data collection / delivery system according to claim 1 or 2 , wherein the data collection / delivery server manages route information from each settlement terminal device to the data collection / delivery server. When a predetermined settlement terminal device is newly connected to a predetermined LAN, the management information managed by the management unit of the relay server connected to the predetermined LAN is updated and the data collection / delivery server 4. The data collection and distribution system according to claim 3 , wherein the route information related to the settlement terminal device is added to the route information managed in step (b). The data collection / delivery server is registered by assuming that the payment terminal device has been rearranged when the route information related to the same payment terminal device as the payment terminal device to which the route information is newly added has already been registered. 5. The data collection and distribution according to claim 4 , wherein the routing information is deleted and the relay server connected to the LAN before the rearrangement is instructed to exclude the payment terminal device from the management target. system.

Images