JPS63123194A - Transactors managing apparatus - Google Patents

Abstract

(57) [Summary] This bulletin contains application data before electronic filing, so abstract data is not recorded.

Description

DETAILED DESCRIPTION OF THE INVENTION (AL Industrial Field of Application) This invention relates to a transaction system that is connected between a plurality of transaction devices (PO3O3 terminals and a door controller center, aggregates the sales data of the transaction devices, and sends the data to the center). The present invention relates to a device group management device.

(b1 Summary of the Invention The transaction device group management device according to the present invention is provided with a sales data aggregation memory, and when the sales data aggregated from each transaction device cannot be transmitted to the center, the data is aggregated in the open until the center or line is restored. Sales data is now stored in memory.

This allows each transaction device to continue processing transactions even when the center is down.

(C1 Conventional Technology) A transaction processing system that aggregates sales online generally consists of a transaction device operated by store staff, a store controller (center) that aggregates and manages sales, and a system connected between the transaction device and the store controller. It consists of a cluster controller (transaction device group management device) that aggregates the sales data of transaction devices and sends it to the store controller.The cluster controller collects the sales data accumulated and stored in each transaction device at a predetermined aggregation time. The sales data is received and sent all at once to the store controller.After each transaction device sends the sales data to the cluster controller, it clears its memory to enable continued transaction processing.

(d) Problems to be solved by the invention In such a transaction system, if the store controller or the line connecting the store controller and the cluster controller goes down, the cluster controller must send aggregated sales data to the store controller. become unable to do so. In such a case, the conventional cluster controller would interrupt the collection of sales data from each transaction device. By the way, a typical transaction device has only one memory for storing sales data, so if the sales data is not downloaded at the aggregation time, the memory cannot be cleared and transactions cannot continue to be processed. Ta. For this reason, conventional transaction systems have had the problem that if the store controller or line goes down, the transaction device also goes down.

This invention was made with a focus on these problems, and by having the cluster controller accumulate and store aggregated data, even when the store controller or the line between the store controller and the cluster controller goes down, the transaction device can still be operated. It is an object of the present invention to provide a transaction device group management device that can avoid downtime.

TE1 Means for Solving Problems This invention provides a system for connecting a plurality of transaction devices that process transactions with customers and store sales data, and a center that aggregates and processes transaction data. In the transaction device group management device that receives sales data of the plurality of transaction devices and transmits them all at once to the center, a sales data aggregation memory that collectively stores the sales data of the plurality of transaction devices, and a communication device between the center or the center and the transaction device group management device. a storage device that stores sales data of the plurality of transaction devices in a sales data aggregation memory when the line goes down until the downtime is resolved;
(f1 action) The transaction device group management device of the present invention receives sales data from each transaction device and transmits this sales data all at once to the center. Alternatively, when an error occurs due to a line going down, this sales data is stored in the sales data totaling memory, and when the center is restored, this sales data is sent to the center.

Even in this case, since each transaction device can send sales data to the transaction device group management device, transactions can continue to be processed in the same way as when the center is operating normally.

(Phantom Embodiment FIG. 2 is a block diagram of a cluster controller that is an embodiment of the present invention. The CPU, which is a control device, includes a memory 2, a clock 3 that measures the current time, and a host controller for communicating with the store controller 10. A plurality of lower side transmission units 5 are connected to each other for communicating with the side transmission unit 4 and the transaction device ECR 6. Communication between each ECR 6 and the store controller 10 is based on the timing of the clock 3 (at a specific time). It will be held on.

FIG. 3 is a block diagram showing the main parts of the memory 2. As shown in FIG. (A) of the same figure shows the opening flag and the total time table. The opening flag is a flag that is set when an opening instruction message is sent from the store controller 10, and is reset when a closing instruction message is sent or a sales data transmission error occurs. The aggregation time table stores the aggregation time sent together with the opening command message, and the sales data of each ECR 6 is collected based on this time.

FIG. 3B is a diagram showing a total data accumulation file (sales data total memory). Sales data for each ECR consists of its ECR number, total sales amount, number of sales, and sales amount and number of sales for each product category.Sales data for each ECR is aggregated once at each aggregation time. Configure aggregated data. The sales data accumulation file consists of a plurality of total data storage areas and an area for storing the number of total data. If the store controller 10 is down when the sales data is totaled, the total data is temporarily stored in the total data storage area, and later sent to the store controller 10 when the center is restored. The total data storage area is cleared.

FIG. 4 is a diagram showing a communication procedure between the cluster controller and the store controller 10. First, when the store controller starts operating, a message is sent to the cluster controller to instruct the cluster controller to open the station. When a predetermined aggregation time comes, the cluster controller notifies the store controller that it is the aggregation time, and sequentially transmits the aggregation data of the plurality of ECRs to the store controller. When the reception of all aggregated data is completed, the store controller sends a reception completion message to the cluster controller. When the station closing time comes, the store controller transmits a station closing command message to the cluster controller, and when the station closing is completed, the cluster controller transmits a station closing report message to the store controller.

FIG. 1 is a flowchart showing the operation of the control section of the cluster controller. When the operation starts, the opening flag is first reset in step nl (hereinafter step ni will be referred to as ni). In steps n2 to n6 (standby routine), it is determined whether there is data that prompts the trajectory of each motion.

At n2, it is determined whether or not an opening command has been received from the center 10, and if so, the operations from n7 onwards are performed. That is, in n7, the above-mentioned opening flag is set, and the center 10
A reply of the opening report is sent to (n8). Furthermore, if the opening instruction message contains data for newly setting the total time, that data is stored in the total time table (n9), and the process returns to the standby routine.

At n3, it is determined whether the total time has come with reference to the total time table and clock 3. When the aggregation time comes, the following operations are performed. That is, each ECR
The sales are collected from 6 and totaled (n1o), and it is determined whether the opening flag is set (nil). If the opening flag is set, total data is transmitted to center 0 (.n12). If the opening flag has been reset, the total data is stored in the total data storage area (n13) and the process returns to the standby routine.

In steps n4 to n5, it is determined whether or not the opening flag is set and there is data stored in the total data storage file. In this case, the stored data is sent to the center and the process returns to n14) standby routine.

Further, at n6, it is determined whether a station closing command has been input from the center 0, and if a station closing command has been input, the station open flag is reset at n15, and the process returns to the standby routine.

FIG. 2B is a diagram showing the total data transmission subroutine that operates in steps n12 to n14. One EC with n20
The total data regarding H is transmitted, and it is determined in n21 whether a transmission error has occurred.

If a transmission error occurs, it is determined in n26 whether or not there have been 5 consecutive errors, and if it has not been 5 consecutive errors, n
Go back to 20 and try sending again. If there are 5 consecutive errors, reset the opening flag at n27 and return. In other words, it is determined that the store controller is down. If no transmission error has occurred, it is determined at n22 whether or not all the data regarding the ECR has been transmitted, and if all the data has not been transmitted, the process returns to n20. When all the data has been sent, a reception completion message from the center is accepted at n23, and whether or not this message has been received within a predetermined time is checked at n23.
Judging by 24. If the reception completion message is not received within the predetermined time, the process proceeds to n27, and if the reception completion message is received, the transmitted data is deleted in n25 and the process returns.

nil to n13 correspond to the storage means of this invention.

(h) Effects of the Invention According to the present invention, even if the line between the center or the center and the transaction group management device goes down, the sales data aggregation memory set in the transaction group management device is stored in each transaction device. The transaction group management device can receive the sales data of each transaction device in the same way as usual. Since the sales data is retrieved normally even if the transaction is in progress, the memory will not become unavailable and a down state can be avoided.This allows for smooth transaction processing.

[Brief explanation of the drawing]

FIGS. 1(A) and 1(B) are flowcharts showing the operation of the control unit of a cluster controller according to an embodiment of the present invention, in which FIG. 1(A) is a main routine and FIG. 1(B) is a total data transmission subroutine. shows. FIG. 2 is a block diagram of the control section of the cluster controller, FIG. 3 is a block diagram of a main part of the memory of the cluster controller, and FIG. 4 is a communication time chart between the cluster controller and the store controller. 2-memory, 10-store controller.

Claims (1)

[Claims] (1) Connected between a plurality of transaction devices that process transactions with customers and store sales data, and a center that aggregates and processes the transaction data, and receives sales data of the plurality of transaction devices and collects the sales data at once. In the transaction device group management device that sends data to the center, when the line between the sales data aggregation memory that collectively stores the sales data of the plurality of transaction devices and the center or the center/transaction device group management device goes down, this down occurs. A transaction device group management device comprising: a storage device for storing sales data of the plurality of transaction devices in a sales data totaling memory until the transaction is resolved.