JP7757191B2 - Relay device, processing device, and transaction processing system - Google Patents

Description

Embodiments of the present invention relate to a relay device, a processing device, and a transaction processing system.

Conventionally, in transaction processing systems and the like, stand-alone processing devices have been widely used that are equipped with or connected to various devices and are configured to execute information processing for processing transactions while utilizing these devices.
However, a network-connected transaction processing system is also being considered in which the various devices that were previously mounted on or connected to stand-alone processing devices are treated as independent devices, and the required information processing is performed by these devices working together via a communication network.

However, in a network-connected transaction processing system, each device must have a communication function via a communication network, so if a store that previously used a stand-alone transaction processing system tried to install a network-connected transaction processing system, it was not possible to reuse the various devices used in the stand-alone transaction processing system in the new transaction processing system.
In view of these circumstances, it has been desired to be able to build a network-connected transaction processing system while utilizing various devices that do not have the ability to communicate via a communication network.

Special table 2014-508341 publication

The problem that this invention aims to solve is to provide a relay device, a processing device, and a transaction processing system that enable the construction of a transaction processing system using various devices that do not have the ability to communicate via a communication network.

In one embodiment, the relay device executes transaction processing using notification data from at least one of multiple devices of different types belonging to a single checkout lane, and together with a processing device, transmits data generated by the transaction processing to a communication network addressed to a communication identifier that identifies the device on the communication network, along with a type identifier that identifies the type of the device that is the notification recipient among the multiple devices belonging to the checkout lane. The relay device comprises an interface means, a first management means, a first communication means, a transmission processing means, and a reception processing means. The interface means is connected to multiple devices belonging to a single checkout lane and interfaces the exchange of data with each of the connected devices. The first management means manages the type identifiers that identify the types of each of the multiple devices connected to the interface means. The first communication means communicates data via the communication network. The transmission processing means controls the first communication means to send data acquired by the interface means from a device connected to the interface means to the processing device, along with a type identifier managed by the first management means for the device that output the data, to the communication network. The reception processing means controls the interface means to provide the data received by the first communication means to a device of a type identified by the type identifier attached to the data, among multiple devices connected to the interface means.

FIG. 1 is a block diagram illustrating a schematic configuration of a transaction processing system according to an embodiment. FIG. 2 is a block diagram showing a main circuit configuration of the processing device in FIG. 1 . FIG. 3 is a diagram schematically illustrating the structure of one of the data records included in the management table in FIG. 2 . FIG. 2 is a functional block diagram showing a main circuit configuration of the relay device in FIG. 1 . FIG. 5 is a diagram schematically illustrating the structure of one of the data records included in the management table in FIG. 4 . 5 is a flowchart of a relay process performed by the processor in FIG. 4; 3 is a flowchart of a transfer process performed by the processor in FIG. 2;

An example of an embodiment will be described below with reference to the drawings.
FIG. 1 is a block diagram showing a schematic configuration of a transaction processing system 100 according to this embodiment.
The transaction processing system 100 includes device groups 1 and 2, a processing device 3, and a relay device 4.

The device group 1 includes a display 11, a keyboard 12, a magnetic reader 13, a scanner 14, a printer 15, and a payment machine 16. The number of device groups 1 included in the transaction processing system 100 may be two or more. In many cases, the transaction processing system 100 will include multiple device groups 1, but for simplicity's sake, only one will be included here. An appropriate number of device groups 1 are provided depending on the size of the store in which the transaction processing system 100 is installed. Typically, one device group 1 is associated with one of the checkout lanes formed in the store. Each device group 1 is used to process transactions related to customers who enter the associated checkout lane. The display 11, keyboard 12, magnetic reader 13, scanner 14, printer 15, and payment machine 16 are all configured as independent devices and are installed, for example, near the checkout lane to which the device group 1 to which it belongs is associated. The display 11, keyboard 12, magnetic reader 13, scanner 14, printer 15, and payment machine 16 are each individually connected to the communication network 200. In the following, the display 11, keyboard 12, magnetic reader 13, scanner 14, printer 15, and payment machine 16 will sometimes be referred to as "devices included in device group 1" without distinction.

The display 11 displays a screen for presenting information to an operator such as a store clerk or a customer. The display 11 has a communication function via the communication network 200, and displays the screen in accordance with control data sent from the processing device 3 via the communication network 200.
The keyboard 12 has a plurality of keys operable by an operator. The operator inputs instructions by operating these keys on the keyboard 12. The keyboard 12 has a communication function via the communication network 200, and sends notification data for notifying the processing device 3 of the input contents over the communication network 200.
The magnetic reader 13 reads data magnetically recorded on a magnetic card. The magnetic card may be a membership card, a point card, etc. The magnetic reader 13 has a communication function via the communication network 200, and sends notification data for notifying the processing device 3 of the reading result over the communication network 200.
The scanner 14 reads the barcode or two-dimensional code displayed on the product. The scanner 14 has a communication function via the communication network 200, and sends notification data for notifying the processing device 3 of the reading result over the communication network 200.
The printer 15 prints an image of a receipt, invoice, sales slip, or other voucher onto receipt paper. The printer 15 then ejects the receipt paper with the image printed on it from the receipt ejection port. The printer 15 has a communication function via the communication network 200, and prints the image in accordance with control data sent from the processing device 3 via the communication network 200.
The payment machine 16 processes payments using a predetermined payment method among various payment methods, such as cash payment, credit card payment, electronic money payment, barcode payment, etc. The payment machine 16 has a communication function via the communication network 200, and processes payments in accordance with control data sent from the processing device 3 via the communication network 200.

Device group 1 may include any devices other than display 11, keyboard 12, magnetic reader 13, scanner 14, printer 15, and payment machine 16, or device group 1 may not include some of display 11, keyboard 12, magnetic reader 13, scanner 14, printer 15, and payment machine 16. Furthermore, if transaction processing system 100 includes multiple device groups 1, these device groups 1 may include different devices. Devices that may be included in device group 1 include, for example, touch panels, wireless tag readers, weighing scales, or contactless card readers. For some devices, such as displays, multiple devices of the same type may be included in device group 2. However, all devices included in device group 1 have the ability to communicate via communication network 200 and are connected to communication network 200.

The device group 2 includes a display 21, a keyboard 22, a magnetic reader 23, a scanner 24, a printer 25, and a payment machine 26. The number of device groups 2 included in the transaction processing system 100 may be two or more. In many cases, the transaction processing system 100 will include multiple device groups 2, but for simplicity's sake, only one will be included here. An appropriate number of device groups 2 are provided depending on the size of the store in which the transaction processing system 100 is installed. Typically, one device group 2 is associated with one of the checkout lanes formed in the store. Each device group 2 is used to process transactions related to customers who enter the associated checkout lane. The display 21, keyboard 22, magnetic reader 23, scanner 24, printer 25, and payment machine 26 are all configured as independent devices and are installed, for example, near the checkout lane to which the device group 2 belongs. The display 21, keyboard 22, magnetic reader 23, scanner 24, printer 25, and payment machine 26 are each connected individually to the relay device 4. In the following, the display 21, keyboard 22, magnetic reader 23, scanner 24, printer 25, and payment machine 26 will sometimes be referred to as "devices included in device group 2" without distinction between them.

The display 21 displays a screen for presenting information to an operator such as a store clerk or a customer. The display 21 displays the screen in accordance with control data sent from the relay device 4.
The keyboard 22 has a plurality of keys operable by an operator. The operator inputs instructions by operating these keys on the keyboard 22. The keyboard 22 outputs data representing the input contents to the relay device 4.
The magnetic reader 23 reads data magnetically recorded on a magnetic card. The magnetic card may be a membership card, a point card, etc. The magnetic reader 23 outputs the read data to the relay device 4.
The scanner 24 reads the barcode or two-dimensional code displayed on the product and outputs the read data to the relay device 4.
The printer 25 prints an image of a receipt, invoice, sales slip, or other voucher onto receipt paper. The printer 25 then ejects the receipt paper with the image printed on it from the receipt ejection port to the outside. The printer 25 prints the image in accordance with the control data sent from the relay device 4.
The payment machine 26 performs processing for payment using a predetermined payment method among various payment methods, such as cash payment, credit card payment, electronic money payment, barcode payment, etc. The payment machine 26 performs processing for payment in accordance with control data sent from the relay device 4.

Device group 2 may include any devices other than display 21, keyboard 22, magnetic reader 23, scanner 24, printer 25, and payment machine 26, or device group 2 may not include some of display 21, keyboard 22, magnetic reader 23, scanner 24, printer 25, and payment machine 26. Furthermore, if transaction processing system 100 includes multiple device groups 2, the devices included in these device groups 2 may differ. Examples of devices that may be included in device group 2 include a touch panel, a wireless tag reader, a weighing scale, or a contactless card reader. However, all devices included in device group 2 are connected to relay device 4.

Processing device 3 is capable of communicating with each device included in device group 1 and relay device 4 via communication network 200. Processing device 3 performs information processing to process transactions related to the checkout lane associated with device group 1, using each of the devices included in device group 1. Processing device 3 performs information processing to process transactions related to the checkout lane associated with device group 2, using each of the devices included in device group 2. Processing device 3 is realized, for example, as a cloud server.

Relay device 4 is connected to communication network 200. Relay device 4 imports data output from devices included in device group 2, and after performing the conversion process described below, sends the notification data to processing device 3 over communication network 200. When relay device 4 receives control data sent from processing device 3 and transmitted over communication network 200, it outputs the data to the devices included in device group 2 that are to be controlled by the control data.

The communication network 200 may be the Internet, a virtual private network (VPN), a local area network (LAN), a public communication network, a mobile communication network, or the like, either alone or in appropriate combination. Typically, the communication network 200 is the Internet or a LAN.

FIG. 2 is a block diagram showing the main circuit configuration of the processing device 3.
The processing device 3 includes a processor 31, a main memory 32, an auxiliary storage unit 33, a communication unit 34, and a transmission path 35. As the hardware of the processing device 3, for example, a general-purpose server device can be used.

The processor 31, main memory 32, and auxiliary storage unit 33 are connected by a transmission line 35 to form a computer that executes information processing for processing transactions.
The processor 31 corresponds to the central part of the computer. The processor 31 executes information processing for transaction processing by executing information processing programs such as an operating system, middleware, and application programs stored in the main memory 32 and the auxiliary storage unit 33.

Main memory 32 corresponds to the main storage portion of the computer. Main memory 32 includes a non-volatile memory area and a volatile memory area. Main memory 32 stores the information processing programs in the non-volatile memory area. Main memory 32 may also store data required by processor 31 to execute various information processes in either the non-volatile or volatile memory area. Main memory 32 uses the volatile memory area as a work area where data can be rewritten by processor 31 as needed.

The auxiliary memory unit 33 corresponds to the auxiliary memory portion of the computer. The auxiliary memory unit 33 includes well-known storage devices, such as an EEPROM (electric erasable programmable read-only memory), a HDD (hard disk drive), or an SSD (solid state drive). The auxiliary memory unit 33 stores data used by the processor 31 in performing various information processing operations, as well as data generated by the processor 31's processing. The auxiliary memory unit 33 may also store the information processing programs. In this embodiment, the auxiliary memory unit 33 stores the transfer program PRA and the transaction program PRB, which are each information processing programs. The transfer program PRA is an application program that describes the procedures for information processing (hereinafter referred to as transfer processing) for data transfer between the devices included in the device group 1 and the relay device 4. The transaction program PRB is an application program that describes the procedures for information processing (hereinafter referred to as transaction processing) for transaction processing. A portion of the storage area of the auxiliary memory unit 33 is used as the management table TAA. Management table TAA is a data table for managing each device included in device group 1 and each device included in device group 2.

The communication unit 34 performs processing for data communication via the communication network 200. The communication unit 34 is an example of a second communication means.
The transmission path 35 includes an address bus, a data bus, a control signal line, etc. The transmission path 35 transmits data and signals exchanged between the components connected thereto.

FIG. 3 is a diagram showing a schematic structure of one of the data records REA contained in the management table TAA.
The data record REA is associated with either one of the devices included in device group 1 or one of the devices included in device group 2. The management table TAA is a collection of data records REA associated with each of a plurality of devices.

Data record REA includes fields FAA, FAB, FAC, and FAD. Field FAA contains an IP address as a communication identifier for identifying the associated device on communication network 200. Field FAB contains a vendor ID (identifier) set for the associated device. Field FAC contains a product ID set for the associated device. Field FAD contains a lane ID as an identifier for the checkout lane associated with device group 1 or device group 2 to which the associated device belongs.

FIG. 4 is a functional block diagram showing the main circuit configuration of the relay device 4.
The relay device 4 includes a processor 41, a main memory 42, an auxiliary storage unit 43, an interface unit 44, a communication unit 45, and a transmission path 46. As the hardware of the relay device 4, for example, a general-purpose computer device can be used.

The processor 41, main memory 42, and auxiliary storage unit 43 are connected by a transmission line 46 to form a computer that performs processing to realize the functions of the relay device 4.
The processor 41 corresponds to the central part of the computer. The processor 41 executes information processing for the above-mentioned processing by executing information processing programs such as an operating system, middleware, and application programs stored in the main memory 42 and the auxiliary storage unit 43.

Main memory 42 corresponds to the main storage portion of the computer. Main memory 42 includes a non-volatile memory area and a volatile memory area. Main memory 42 stores the information processing programs in the non-volatile memory area. Main memory 42 may also store data required by processor 41 to execute various information processes in either the non-volatile or volatile memory area. Main memory 42 uses the volatile memory area as a work area where data can be rewritten by processor 41 as needed.

The auxiliary memory unit 43 corresponds to the auxiliary memory portion of the computer. The auxiliary memory unit 43 includes well-known storage devices such as an EEPROM, HDD, or SSD. The auxiliary memory unit 43 stores data used by the processor 41 when performing various types of information processing, as well as data generated by the processing performed by the processor 41. The auxiliary memory unit 43 may also store the information processing programs described above. In this embodiment, the auxiliary memory unit 43 stores a relay program PRC, which is one of the information processing programs. The relay program PRC is an application program that describes the procedures for information processing (hereinafter referred to as relay processing) for relaying data communication between each device included in the same device group 2 and the processing device 3. A portion of the storage area of the auxiliary memory unit 43 is used as a management table TAB.

The interface unit 44 has multiple ports for connecting devices included in the same device group 2. The display 21, keyboard 22, magnetic reader 23, scanner 24, printer 25, and payment machine 26 are connected to these ports. However, multiple devices included in multiple device groups 2 may be connected to the interface unit 44 ports via a hub. Therefore, the interface unit 44 may be configured with only one port. The interface unit 44 imports data output from the connected devices. The interface unit 44 also outputs data supplied via the transmission path 46 to the device specified as the output destination under the processing of the processor 41. A commercially available device for a general-purpose device interface can be used as the interface unit 44. In this embodiment, the interface unit 44 complies with the USB (universal serial bus) standard. Therefore, in this embodiment, each device included in device group 2 is a device that is connected to another device using a USB interface. For example, each device included in device group 2 may be a device that is externally connected to a commercially available POS terminal device using a USB interface. Thus, this interface unit functions as an interface means.

The communication unit 45 performs processing for data communication via the communication network 200. The communication unit 45 is an example of a first communication means.
The transmission path 46 includes an address bus, a data bus, control signal lines, etc. The transmission path 46 transmits data and signals exchanged between the components connected thereto.

FIG. 5 is a diagram showing a schematic structure of one of the data records REB contained in the management table TAB.
A data record REB is associated with each of all devices included in the device group 2. In other words, the management table TAB is a collection of multiple data records REB. The data record REB includes fields FBA, FBB, and FBC. A device address for distinguishing the associated device from other devices connected to the interface unit 44 is set in field FBA. The vendor ID of the associated device is set in field FBB. The product ID of the associated device is set in field FBC.

The transfer program PRA, transaction program PRB, and relay program PRC may be stored in the auxiliary storage units 33, 43 when the processing device 3 and relay device 4 are transferred, or the programs transferred separately from the hardware of the processing device 3 and relay device 4 may be written to the auxiliary storage units 33, 43 by the processors 31, 41 in response to the operation of any operator. When transferring the programs separately from the hardware, they may be transferred by recording them on removable recording media such as a magnetic disk, magneto-optical disk, optical disk, or semiconductor memory, or they may be transferred via communication via a network.

Next, a description will be given of the operation of the transaction processing system 100 configured as described above. Note that the content of the processing described below is an example, and it is possible to change the order of some of the processing, omit some of the processing, or add other processing as appropriate.
When the relay device 4 is in a normal operating state, the processor 41 executes relay processing based on the relay program PRC.
FIG. 6 is a flowchart of the relay process by the processor 41.

In ACT11, the processor 41 checks whether a new device has been connected to the interface unit 44. If the processor 41 cannot check the relevant event, it determines NO and proceeds to ACT12.
In ACT 12, the processor 41 checks whether or not a device has been removed from the interface unit 44. If the processor 41 cannot check the relevant event, it determines "NO" and proceeds to ACT 13.
In ACT 13, the processor 41 checks whether data has been input from any of the devices included in the device group 2. If the processor 41 cannot check the relevant event, it determines NO and proceeds to ACT 14.
In ACT 14, the processor 41 checks whether data to be given to any of the devices included in the device group 2 has been received. If the processor 41 cannot check the relevant event, it determines NO and returns to ACT 11.
Thus, in ACT11 to ACT14, the processor 41 waits for a new connection or removal of a device, or for input or reception of data.

It is anticipated that transaction processing system 100 will be introduced into stores as a replacement for conventional transaction processing systems in which checkout lanes are equipped with POS terminals configured with various devices such as scanners attached to the POS terminal itself. Some checkout lanes will be equipped with device group 1, which includes various new devices that are different from those used in the existing transaction processing system, and some checkout lanes will be equipped with device group 2, which includes various devices that were used in the existing transaction processing system. It is also possible to install device group 2 in all checkout lanes.

For checkout lanes where device group 2 is located, the various devices included in device group 2 are connected to a newly installed relay device 4. If multiple device groups 2 are located in multiple checkout lanes, one relay device 4 will be installed in each of the multiple checkout lanes.

A worker involved in the construction of the transaction processing system 100 accesses the processing device 3 using, for example, an information terminal and inputs various information for various settings of the processing device 3. For example, for a checkout lane where device group 1 is located, the worker inputs the lane ID of that checkout lane and the IP address, vendor ID, and product ID for each device included in device group 1 located in that checkout lane. In response, processor 31 in the processing device 3 adds a data record REA, in which the IP address, vendor ID, product ID, and lane ID are respectively set in fields FAA, FAB, FAC, and FAD, to management table TAA. The IP address, vendor ID, and product ID may be transmitted from the device to the communication network 200 and addressed to the processing device 3. Alternatively, the lane ID entered by the worker into the device may be transmitted by the device to the communication network 200 and addressed to the processing device 3.

For the checkout lane in which device group 2 is located, the worker also enters the lane ID of that checkout lane, the vendor ID and product ID for each device in device group 2 located in that checkout lane, and the IP address of the relay device 4 installed in that checkout lane. The processor 31 then adds to management table TAA a data record REA in which the IP address, vendor ID, product ID, and lane ID are set in fields FAA, FAB, FAC, and FAD, respectively.

The worker does not need to enter a vendor ID or product ID for the checkout lane where device group 2 is located. In this case, processor 31 leaves fields FAB and FAC blank, or sets predetermined invalid values to fields FAB and FAC. In this case, the worker does not connect devices for which a vendor ID and product ID are not entered to relay device 4.

Since various devices are connected to the relay device 4 via USB, a new device can be connected to the relay device 4 or a device already connected to the relay device 4 can be removed at will.
The interface unit 44 periodically checks the connection status of devices, and if a device with an unassigned device address is connected, it detects the device as a newly connected device and notifies the processor 41. Upon receiving this notification, the processor 41 determines YES in ACT 11 and proceeds to ACT 15.

In ACT 15, the processor 41 acquires the vendor ID and product ID of the connected device. For example, the processor 41 reads the vendor ID and product ID from the newly connected device via the interface unit 44.

In ACT 16, the processor 41 updates the management table TAB to start managing the newly connected device. For example, the processor 41 determines a device address for the newly connected device so that it can be distinguished from devices already under management, and updates the management table TAB to include a new data record REB in which the device address and the vendor ID and product ID acquired in ACT 15 are set in fields FBA, FBB, and FBC, respectively. Note that the device address may be determined by the interface unit 44.

In ACT 17, the processor 41 notifies the processing device 3 of the configuration change. The processor 41, for example, causes the communication unit 45 to send notification data, which includes predetermined identification data to identify that the notification is for adding a device and has the IP address of the processing device 3 as the destination address, to the communication network 200. The processor 41 includes in the notification data the vendor ID and product ID acquired in ACT 15 and the lane ID of the checkout lane in which the relay device 4 is installed. Note that the lane ID of the checkout lane in which the relay device 4 is installed and the IP address of the processing device 3 are stored in advance, for example, in the auxiliary storage unit 43. The processor 41 then returns to the standby state of ACTs 11 to 14.

Here, the vendor ID is an identifier used to identify the supplier of the device, such as the manufacturer. The product ID is an identifier assigned by the supplier to ensure that each device model is unique. Therefore, the combination of the vendor ID and product ID makes it possible to identify the type of device. In other words, the combination of the vendor ID and product ID corresponds to a type identifier that identifies the type of device. In other words, the processor 41 uses the management table TAB to manage the type identifiers that identify the types of each of the multiple devices connected to the interface unit 44, which serves as interface means. Thus, by having the processor 41 execute information processing based on the relay program PRC, the computer with the processor 41 as its central part functions as a first management means.

On the other hand, if the processor 41 cannot confirm the connection of the device with the device address set in field FBA of the data record in the management table TAB, for example, it determines that the device has been removed and judges YES in ACT 12, and proceeds to ACT 18.
In ACT 18, the processor 41 identifies the removed device. For example, the processor 41 identifies a device that is identified by the device address set in field FBA of data record REB in the management table TAB but whose connection cannot be confirmed as the removed device.

In ACT 19, the processor 41 updates the management table TAB to stop managing the removed device. For example, the processor 41 updates the management table TAB to delete the data record REB in which the device address of the device identified in ACT 18 is set in the field FBA.
In ACT 20, the processor 41 notifies the processing device 3 of the configuration change. For example, the processor 41 causes the communication unit 45 to send notification data, which includes predetermined identification data to identify that the notification is for device removal and has the IP address of the processing device 3 as the destination address, to the communication network 200. The processor 41 includes in the notification data the vendor ID and product ID set in fields FBB and FBC of the data record REB in which the device address of the device identified in ACT 18 is set in field FBA. Then, the processor 41 then returns to the standby state of ACTs 11 to 14.

When the processing device 3 is in a normal operating state, the processor 31 executes the transfer process based on the transfer program PRA.
FIG. 7 is a flowchart of the transfer process performed by the processor 31.

In ACT 31, the processor 31 checks whether or not a notification has been made regarding a change in the configuration of the device group 2. If the processor 31 cannot confirm the event, it determines NO and proceeds to ACT 32.
In ACT 32, the processor 31 checks whether or not a data notification has been sent from the store. If the processor 31 cannot confirm the event, it determines "NO" and proceeds to ACT 33.
In ACT 33, the processor 31 checks whether or not a data transmission request has been made by the transaction process. If the processor 31 cannot check the relevant event, it determines "NO" and returns to ACT 31.
Thus, the processor 31 waits for any one of a change notification, a data notification, or a transmission request in ACT 31 to ACT 33. Then, as described above, notification data sent from the relay device 4 for connection notification or removal notification is transmitted to the processing device 3 via the communication network 200, and when this notification data is received by the communication unit 34, the processor 31 determines YES in ACT 31 and proceeds to ACT 34.

In ACT 34, processor 31 updates management table TAA to reflect the notified changes. For example, if processor 31 has received notification data for a connection notification, it updates management table TAA to include a new data record REA in which the IP address of the sender of the notification data and the vendor ID, product ID, and lane ID included in the notification data are set in fields FAA, FAB, FAC, and FAD, respectively. Also, if processor 31 has received notification data for a removal notification, it updates management table TAA to delete the data record REA in which the IP address of the sender of the notification data and the vendor ID and product ID included in the notification data are set in fields FAA, FAB, and FAC, respectively. Then, processor 31 returns to the standby state of ACTs 31 to 33.

In other words, processor 31 uses management table TAA to associate and manage lane IDs (lane identifiers for identifying checkout lanes), vendor IDs and product IDs (type identifiers for identifying each of multiple devices belonging to the checkout lane identified by the lane identifier), and IP addresses (communication identifiers for identifying the relay device 4 to which the device is connected) on communication network 200. When processor 31 updates management table TAA in ACT 34, it adds a managed device based on a notification from relay device 4. Thus, by processor 31 executing information processing based on transfer program PRA, the computer with processor 31 as its central component functions as a second management unit and adding unit. Furthermore, processor 41 of relay device 4 determines the vendor ID and product ID (type identifiers) of the newly connected device in ACT 15 of FIG. 6. The notification data for the connection notification corresponds to request data requesting the addition of a managed device, and processor 41 controls communication unit 45 (first communication unit) to transmit the notification data as request data. Thus, by having the processor 41 execute information processing based on the relay program PRC, the computer with the processor 41 as its central part functions as a determination means and a request means.

When a device included in device group 1 acquires any data to be used in transaction processing by processing device 3, it sends notification data to communication network 200 that includes the data, predetermined identification data to identify that the notification is for data to be used in transaction processing, its own vendor ID and product ID, and has the IP address of processing device 3 as the destination address. For example, when scanner 14 reads a barcode, it sends notification data to communication network 200 that includes the barcode data represented by the barcode, predetermined identification data to identify that the notification is for data to be used in transaction processing, the vendor ID and product ID of scanner 14, and has the IP address of processing device 3 as the destination address.

When a device included in the device group 2 acquires any data to be used for transaction processing in the processing device 3, it outputs the data to the relay device 4. In the relay device 4, the interface unit 44 takes in the data. Then, the processor 41 determines YES in ACT 13 in FIG. 6 and proceeds to ACT 21.
In ACT 21, the processor 41 determines the vendor ID and product ID of the device that output the data. For example, the processor 41 searches the management table TAB for a data record REB in which the device address of the device that output the data is set in field FBA, and obtains the vendor ID and product ID set in fields FBB and FBC of the corresponding data record REB.

In ACT 22, the processor 41 generates notification data to notify the processing device 3 of the data captured by the interface unit 44. For example, the processor 41 generates notification data that includes predetermined identification data to identify that the notification is for data used in transaction processing, and has the IP address of the processing device 3 as the destination address. The processor 41 includes in this notification data the data captured by the interface unit 44 and the vendor ID and product ID obtained in ACT 21. For example, when the scanner 24 reads a barcode, it outputs the barcode data represented by the barcode to the interface unit 44. In this case, the processor 41 includes in the notification data the barcode data and the vendor ID and product ID of the scanner 24 obtained from the management table TAB.

In ACT 23, the processor 41 transmits the generated notification data. That is, the processor 41 causes the communication unit 45 to send the data to the communication network 200. Then, the processor 41 then returns to the standby state of ACT 11 to ACT 14.
Thus, the processor 41 executes information processing based on the relay program PRC, and the computer having the processor 41 as its central part functions as a transmission processing means.

As described above, both the data obtained from the devices included in device group 1 and the data obtained from the devices included in device group 2 are notified to the processing device 3 along with the vendor ID and product ID of the device that obtained the data.
Notification data for notifying the data to be used in transaction processing is transmitted to the processing device 3 via the communication network 200, and when this notification data is received by the communication unit 34, the processor 31 judges YES in ACT 32 in Figure 7 and proceeds to ACT 35.
In ACT 35, the processor 31 determines the transaction process that should process the data notified by the corresponding notification data as the target process.

Here, processor 31 executes transaction processing based on transaction program PRB as needed, separate from the transfer processing. Transaction processing is well-known processing for processing transactions, such as creating a list of items to be traded, calculating the payment amount, and settling the payment amount. Processor 31 may also execute transaction processing in parallel for each of multiple checkout lanes. In this way, processor 31 executes information processing based on transaction program PRB, and the computer with processor 31 as its central part functions as a processing means.

Therefore, in ACT 35, for example, processor 31 searches management table TAA for a data record REA in which the IP address of the sender of the notification data is set in field FAA, and determines that the transaction process for the checkout lane identified by the lane ID set in field FAD of the corresponding data record REA is the target process. If a transaction process for the corresponding checkout lane is not currently being executed, processor 31 starts the corresponding transaction process and sets the transaction process as the target process.
In ACT 36, the processor 31 passes the data included in the notification data to the target process as data to be processed. Then, the processor 31 returns to the standby state in ACT 31 to ACT 33.

If the transaction process requires a device included in device group 1 to perform some operation, processor 31 requests the transfer process to send control data for controlling that operation. In the transaction process, processor 31 passes to the transfer process, for example, a command indicating the content of the control, as well as control data including the vendor ID and product ID of the device to be controlled. In response to this request, processor 31 determines YES in ACT 33 and proceeds to ACT 37.

In ACT 37, processor 31 determines the destination of the control data. For example, processor 31 determines which checkout lane the transaction request is for. For example, processor 31 searches management table TAA for a data record REA in which the vendor ID and product ID included in the control data and the lane ID of the determined checkout lane are set in fields FAB, FAC, and FAD, respectively. Then, processor 31 determines, for example, the IP address set in field FAA of the corresponding data record REA as the IP address of the destination of the control data. If the device to be controlled is a device included in device group 1, processor 31 determines the IP address of that device as the destination IP address. Furthermore, if the device to be controlled is a device included in device group 2, processor 31 determines the IP address of relay device 4 to which that device is connected as the destination IP address.

In ACT 38, the processor 31 transmits the control data to the destination determined in ACT 37. For example, the processor 31 sends the control data handed over from the transaction process from the communication unit 34 to the communication network 200, with the IP address determined in ACT 37 as the destination address. The processor 31 then returns to the standby state of ACTs 31 to 33.

When control data sent from the processing device 3 to the device's IP address is transmitted over the communication network 200, a device included in device group 1 receives the control data and performs an operation according to the included command. For example, when the display 11 receives control data containing a command to change the display screen, it changes the displayed screen according to the command.

On the other hand, when the control data transmitted from the processing device 3 to the IP address of the relay device 4 is transmitted over the communication network 200, the control data is received by the communication unit 45 of the relay device 4. Then, in response to the control data being received by the communication unit 45, the processor 41 determines YES in ACT 14 in FIG. 6 and proceeds to ACT 24.
In ACT 24, the processor 41 determines the device that is to be controlled by the received control data. For example, the processor 41 searches the management table TAB for a data record REB in which the vendor ID and product ID included in the control data are set in fields FBB and FBC, respectively. The processor 41 then determines the target device as the device identified by the device address set in field FBA of the corresponding data record REB.

In ACT 25, the processor 41 outputs the control data to the determined device. For example, the processor 41 outputs the control data from the interface unit 44 to the device address determined in ACT 24. Then, the processor 41 returns to the standby state of ACT 11 to ACT 14.
Thus, the processor 41 executes information processing based on the relay program PRC, and the computer with the processor 41 as its central part functions as a receiving processing means.

When a device included in device group 2 receives control data output from interface unit 44, it operates in accordance with the command included in the control data. For example, when display 21 receives control data including a command to change the display screen, it changes the displayed screen in accordance with the command.

As described above, the relay device 4 mediates the exchange of data between the devices included in the device group 2 and the processing device 3. The processing device 3 and relay device 4 manage each device by associating its vendor ID and product ID with the IP address of the relay device 4 to which the device is connected, and determine the source and destination of the data to be exchanged based on the vendor ID and product ID. This makes it possible to realize a network-connected transaction processing system using devices that do not have the ability to communicate with the processing device 3 via the communication network 200. As a result, when a network-connected transaction processing system is introduced in a store that previously used a standalone transaction processing system, the various devices used in the standalone transaction processing system can be reused in the new transaction processing system, reducing waste when updating such systems.

Furthermore, for devices included in device group 1, processing device 3 manages each device's vendor ID and product ID in association with the device's IP address and the lane ID of the checkout lane associated with that device, making it possible to determine which device group each device belongs to. Furthermore, for devices included in device group 2, processing device 3 also manages the lane ID of the checkout lane associated with that device in association with the vendor ID, product ID, and IP address of relay device 4. This allows processing device 3 to exchange data with devices included in device group 1 and devices included in device group 2 using similar processing, making it possible to configure transaction processing system 100 by mixing device group 1 and device group 2.

This embodiment can be modified in various ways as follows.
A transaction processing system can also be configured to include one or more device groups 2, but not device group 1. In this case, since the IP address of relay device 4 can be used to identify the checkout lane to which relay device 4 belongs, field FAD of management table TAA can be omitted, and the IP address can be used instead of the lane ID.

The management table TAA may be divided into a management table for device group 1 and a management table for device group 2. For example, the management table for device group 1 may have the configuration shown in FIG. 3, and the management table for device group 2 may have a configuration in which field FAD of the management table TAA is omitted. In this case, for device group 2, the IP address is used instead of the lane ID.

The communication identifier may be any identifier, such as various communication addresses other than IP addresses.

The functions realized by processors 31 and 41 through information processing can also be realized in part or in whole by hardware that performs information processing not based on a program, such as a logic circuit. Each of the above functions can also be realized by combining software control with hardware such as the logic circuit.

While several embodiments of the present invention have been described, these embodiments are presented as examples and are not intended to limit the scope of the invention. These novel embodiments may be embodied in a variety of other forms, and various omissions, substitutions, and modifications may be made without departing from the spirit of the invention. These embodiments and their variations are within the scope and spirit of the invention, and are also included in the scope of the invention and its equivalents as set forth in the claims.

1, 2...device group, 3...processing device, 4...relay device, 11, 21...display, 12, 22...keyboard, 13, 23...magnetic reader, 14, 24...scanner, 15, 25...printer, 16, 26...payment machine, 31, 41...processor, 32, 42...main memory, 33, 43...auxiliary storage unit, 34, 45...communication unit, 44...interface unit, 100...transaction processing system, 200...communication network.

Claims (5)

a relay device that constitutes a transaction processing system together with a processing device that executes transaction processing using notification data from at least one of a plurality of different types of devices belonging to one checkout lane, and transmits data generated by the transaction processing to a communication network, the communication network including a type identifier that identifies the type of the device that is the notification destination among the plurality of devices belonging to the checkout lane, addressed to a communication identifier that identifies the device on the communication network;
an interface means to which a plurality of devices belonging to one checkout lane are connected and which interfaces data transmission and reception between the plurality of connected devices;
a first management means for managing type identifiers that identify the types of the respective devices connected to the interface means;
a first communication means for performing data communication via the communication network;
a transmission processing means for controlling the first communication means so that data acquired by the interface means from a device connected to the interface means is sent to the processing device via the communication network, with a type identifier managed by the first management means for the device that is the output source of the data attached thereto;
a receiving processing means for controlling the interface means to provide the data received by the first communication means to a device of a type identified by a type identifier attached to the data among a plurality of devices connected to the interface means;
A relay device comprising: a second management means for managing, in association with each other, a type identifier for identifying each type of a plurality of different types of devices belonging to one checkout lane and a communication identifier for identifying the relay device to which each of the plurality of devices is connected on a communication network;
a second communication means for performing data communication via the communication network;
a processing means for controlling the second communication means to execute a transaction process for a checkout lane to which the relay device belongs, using data sent from the relay device via the communication network with a type identifier associated with the data as data output from a device of the type identified by the type identifier, and to transmit data generated as output to a device belonging to the same checkout lane to the relay device belonging to the checkout lane that is the target of the transaction process, with the type identifier of the device as the output destination attached;
A processing device comprising: a second management means for managing, in association with each other, type identifiers that identify the types of a plurality of different types of devices belonging to one checkout lane and communication identifiers that identify, on a communication network, relay devices to which the plurality of devices are connected;
a second communication means for performing data communication via the communication network;
a processing means for controlling the second communication means to execute a transaction process for a checkout lane to which the relay device belongs, using data sent from the relay device via the communication network with a type identifier associated with the data as data output from a device of the type identified by the type identifier, and to transmit data generated as output to a device belonging to the same checkout lane to the relay device belonging to the checkout lane that is the target of the transaction process, with the type identifier of the device as the output destination attached;
a processing device comprising:
an interface means for interfacing data transmission and reception between each of the plurality of connected devices;
a first management means for managing type identifiers of each of a plurality of devices connected to said interface means;
a first communication means for performing data communication via the communication network;
a transmission processing means for controlling the first communication means so that data acquired by the interface means from a device connected to the interface means is sent to the processing device via the communication network, with a type identifier managed by the first management means for the device that is the output source of the data attached thereto;
a receiving processing means for controlling the interface means to provide the data received by the first communication means to a device of a type identified by a type identifier attached to the data among a plurality of devices connected to the interface means;
a relay device comprising:
A transaction processing system including: The second management means further manages a type identifier of a device that has a communication function via the communication network and is not connected to the relay device, in association with a communication identifier of the device and a lane identifier that identifies a checkout lane to which the device belongs;
The second management means further manages, with respect to a device connected to the relay device, an association between a type identifier of the device connected to the relay device and a communication identifier of the relay device, and further associates the type identifier with a lane identifier of a checkout lane to which the device belongs;
The processing means further controls the second communication means to execute a transaction process for a checkout lane identified by a lane identifier associated with the communication identifier of the device, using data sent from the device via the communication network with a type identifier associated with the device as an output source, and to transmit data generated as output to the device identified by a communication identifier associated with the lane identifier of the checkout lane targeted for the transaction process, to the device;
The processing means further executes a transaction process for the data transmitted from the relay device via the communication network, the transaction process being targeted at a checkout lane identified by a lane identifier associated with the communication identifier of the relay device.
The transaction processing system of claim 3 . The relay device
a determination means for determining a type identifier of a device newly connected to said interface means;
a requesting means for controlling the first communicating means so as to send request data for requesting registration of the type identifier determined by the determining means to the processing device over the communication network;
Further comprising:
The processing device includes:
an adding means for, when the request data transmitted by the first communication means is received by the second communication means, adding an association between a communication identifier of the relay device that is a sender of the request data and a type identifier whose registration is requested by the request data to be managed by the second management means;
The transaction processing system according to claim 3 or claim 4, further comprising: