JP7148703B2 - Transaction processing system, control device and information processing program - Google Patents

Description

An embodiment of the present invention relates to a transaction processing system, a control device, and an information processing program.

A transaction processing system has been considered in which purchased products are registered in accordance with operations by customers on terminal devices such as a cart terminal attached to a shopping cart or a portable information communication terminal owned by the customer.
In such a transaction processing system, the number of terminal devices used simultaneously varies according to the number of customers shopping in the store. In addition, in such a transaction processing system, the number of terminal devices that can be used simultaneously is limited due to resource limitations on the store side. Therefore, when it is congested, a situation may arise in which it is not possible to start using a new terminal device.
It is desirable to reduce the possibility of such situations occurring.

JP 2019-153089 A

The problem to be solved by the present invention is to provide a transaction processing system that can reduce the possibility of a situation in which the use of a new terminal device cannot be started.

The transaction processing system of the embodiment comprises operation means, determination means, detection means, and control means. The operation means is provided in the terminal device, repeatedly confirms the occurrence of an operation by the operator, and receives the corresponding operation when the operation occurs . The determination means is provided in one of the information processing devices, and performs processing for determining the content of the transaction according to the operation received by the operation means. The detection means is provided in one of the terminal device and the information processing device, and detects as a non-operation state that the number of repetitions of confirmation by the operation means exceeds a predetermined number without being operated by the operation means. . The control means is provided in one of the terminal device or the information processing device, and during the period from when the determination means starts processing for determining the content of one transaction until the determination of the content of the one transaction is completed, In response to the detection of the no-operation state by the detection means, the determination means is controlled so as to end the processing relating to the one transaction.

1 is a block diagram showing a schematic configuration of a transaction processing system according to one embodiment; FIG. FIG. 2 is a block diagram showing the main circuit configuration of the store server in FIG. 1; FIG. 2 is a block diagram showing the main circuit configuration of the virtual POS server in FIG. 1; FIG. 2 is a block diagram showing the main circuit configuration of the mobile controller in FIG. 1; 5 is a schematic diagram showing the main data structure of data records included in the transaction management database shown in FIG. 4; FIG. FIG. 5 is a schematic diagram showing the main data structure of data records included in the registration database shown in FIG. 4; FIG. 2 is a block diagram showing the main circuit configuration of the user terminal in FIG. 1; FIG. 2 is a block diagram showing the main circuit configuration of the cart terminal in FIG. 1; 4 is a flowchart of smartphone UI processing. 4 is a flowchart of smartphone UI processing. 4 is a flowchart of smartphone UI processing. 4 is a flowchart of smartphone UI processing. A flowchart of cart UI processing. Management action flow chart. Flowchart of mediation processing. Flowchart of mediation processing. Flowchart of mediation processing. Flowchart of transaction processing. Flowchart of transaction processing. The figure which shows an example of a list screen. The figure which shows an example of a registration screen. The figure which shows an example of a list screen. The figure which shows an example of an accounting screen.

An embodiment of a transaction processing system will be described below with reference to the drawings.
The transaction processing system in this embodiment processes merchandise transactions at a store that sells merchandise displayed in the store to customers who visit the store.

FIG. 1 is a block diagram showing a schematic configuration of a transaction processing system according to this embodiment.
The transaction processing system includes a plurality of store systems 100, a relay server 200, a user terminal 300, a cart terminal 400, a settlement server 500, an electronic receipt server 600 and a communication network 700. A plurality of store systems 100 , relay servers 200 , user terminals 300 , settlement servers 500 and electronic receipt servers 600 can communicate via communication network 700 .

FIG. 1 shows two store systems 100 . These store systems 100 are provided in different stores A and B that use the transaction processing system. There may be three or more shops using the transaction processing system, and the shop system 100 is provided for each shop. In the following, when it is necessary to distinguish between the store systems 100 installed in each store, the store system 100 installed in store A will be referred to as store system 100A, and the store system 100 installed in store B will be referred to as store system 100A. Represented as system 100B.
The business operator that operates the store A may be the same as the business operator that operates the store B, or may be different. Even when the transaction processing system is used at other stores, the business operator that operates the store may be the same as the business operator that operates the store A or the store B, or may be different.

Relay server 200 relays data communication between user terminal 300 and store system 100 . The relay server 200 provides a data communication relay function as a cloud service via the communication network 700, for example.

The user terminal 300 is a terminal device that functions as a user interface for customers who shop at stores using the transaction processing system. The user terminal 300 has a function of wirelessly communicating with the store system 100 and a function of wirelessly communicating with the communication network 700 . As the user terminal 300, a communication terminal having a data communication function such as a smart phone or a tablet terminal can be used. User terminal 300 is owned by a customer. That is, the user terminal 300 is an example of a terminal device brought into a store by a customer.

The cart terminal 400 is a terminal device that functions as a user interface for customers who shop at stores using the transaction processing system. The cart terminal 400 has a function of wirelessly communicating with the store system 100 . The cart terminal 400 is attached to the shopping cart C1 and installed in the store. The cart terminal 400 is used by customers at the store. That is, the cart terminal 400 is an example of a terminal device lent to a customer by a store.

The settlement server 500 performs settlement processing for online settlement in response to a settlement request via the communication network 700 . The settlement server 500 may be compatible with only one of a plurality of settlement methods such as credit card settlement and electronic money settlement, or may be compatible with multiple settlement methods. . As the payment server 500, for example, an existing payment server operated by a payment agency that supports multiple payment services including multiple payment methods can be applied.

The electronic receipt server 600 provides receipts representing transaction results as images or web pages. As the electronic receipt server 600, for example, an existing electronic receipt server that provides an electronic receipt service can be applied.

As the communication network 700, for example, the Internet, a VPN (virtual private network), a LAN (local area network), a public communication network, a mobile communication network, etc. can be used singly or in combination as appropriate. As communication network 700, a mobile communication network and the Internet or VPN are typically used.

The general configuration of each store system 100 is common. That is, the store system 100 is configured such that the store server 1 , virtual POS server 2 , mobile controller 3 , communication server 4 , checkout machine 5 and access point 6 can communicate with each other via the in-store communication network 7 . However, the store server 1, the virtual POS server 2, the mobile controller 3, the communication server 4, the checkout machine 5, the access point 6, and the in-store communication network 7 only need to have common functions for realizing the operations described later. need not be identical to . Some store systems 100 may also include devices not shown in FIG.

The store server 1 is an information processing device for comprehensively managing a plurality of transactions processed by the transaction processing system. The store server 1 has, for example, functions similar to those of existing POS servers.
The virtual POS server 2 is an information processing device that performs information processing (hereinafter referred to as transaction processing) for registration of purchased products for each transaction and payment for the purchased products in response to requests from the outside. The virtual POS server 2 virtually implements the functions of existing POS terminals. Information processing performed by the virtual POS server 2 is customized so as to adapt to differences in management policies of each store. That is, for example, the transaction processing performed by the store server 1 provided in the store system 100A and the transaction processing performed by the store server 1 provided in the store system 100B may be partially different.

The mobile controller 3 is an information processing device that executes management processing and mediation processing. Management processing is information processing for managing the above transaction processing executed by the virtual POS server 2 . The intermediation process is performed by connecting the virtual POS server 2 and the user terminal 300 or the cart terminal 400 in order to perform the above transaction process executed by the virtual POS server 2 while using the user terminal 300 or the cart terminal 400 as a user interface device. It is information processing for mediation.
The communication server 4 performs communication processing for the store server 1, the virtual POS server 2, the mobile controller 3, and the accounting machine 5 to exchange data with the relay server 200 and the like via the communication network 700. FIG.

The accounting machine 5 obtains the price of the purchased product for each transaction managed by the virtual POS server 2, and performs processing for making the customer settle the price. Payment methods that can be used by the accounting machine 5 for the above payment include cash payment, credit card payment, electronic money payment, point payment, code payment (also called mobile payment, smartphone payment, etc.), and the like. It may be all or any part of the payment method. The checkout machine 5 may be operated by either a store clerk or a customer. As the checkout machine 5, for example, a self-service checkout machine used in an existing semi-self-checkout POS system can be used. The accounting machine 5 may have a function of performing information processing for registering products as purchased products. In this case, as the checkout machine 5, for example, a face-to-face POS terminal used in an existing POS system or a self-service POS terminal used in an existing self-service POS system can be used.

The access point 6 performs communication processing for enabling the user terminal 300 and the cart terminal 400 to access the in-store communication network 7 by wireless communication. As the access point 6, for example, a well-known communication device that performs wireless communication according to the IEEE802.11 standard can be used. The access point 6 is installed in the store so that the user terminal 300 and the cart terminal 400 can wirelessly communicate from anywhere in the sales floor of the store. A plurality of access points 6 may be arranged in one store system 100 depending on the size of the store.
As the in-store communication network 7, the Internet, VPN, LAN, public communication network, mobile communication network, etc. can be used singly or in combination as appropriate. However, typically, the in-store communication network 7 is a LAN.

In a store provided with the store system 100, a two-dimensional code TC1 for check-in is displayed near the entrance, and a two-dimensional code TC2 for check-out is displayed near the exit. A two-dimensional code TC1 represents check-in data for check-in. A two-dimensional code TC2 represents checkout data for checkout. Check-in data and check-out data differ from store to store. Therefore, when it is necessary to distinguish between the two-dimensional codes TC1 and TC2 for store A and the two-dimensional codes TC1 and TC2 for store B, the two-dimensional codes for store A are represented as TC1A and TC2A, and the two-dimensional codes for store B are represented as TC1A and TC2A. are represented as two-dimensional codes TC1B and TC2B.

The check-in data represents, for example, the following information.
(1) Operation version of store system 100 . For example, the check-in data represented by the two-dimensional code TC1A represents the operating version of the store system 100A. The check-in data represented by the two-dimensional code TC1B represents the operating version of the store system 100B.
(2) A company code for identifying a company that manages the store where the store system 100 is installed. For example, the check-in data represented by the two-dimensional code TC1A represents the company code assigned to the company that manages the store A. The check-in data represented by the two-dimensional code TC1B represents the company code assigned to the company that manages the store B.
(3) A shop code for identifying the shop where the shop system 100 is installed. For example, the check-in data represented by the two-dimensional code TC1A represents the store code assigned to store A. The check-in data represented by the two-dimensional code TC1B represents the store code assigned to the store B. The store code may be able to identify each of all stores that use the transaction processing system, or may be able to identify each of multiple stores operated by the same business operator. .

(4) The name of the business operator that operates the store where the store system 100 is installed. For example, the check-in data represented by the two-dimensional code TC1A represents the name of the company that manages the store A. The check-in data represented by the two-dimensional code TC1B represents the name of the company that manages the store B.
(5) The name of the store where the store system 100 is installed. For example, the check-in data represented by the two-dimensional code TC1A represents the name of the store A. The check-in data represented by the two-dimensional code TC1B represents the store B name.
(6) A flag for distinguishing between the two-dimensional code TC1 and the two-dimensional code TC2. The flag in check-in data is in a state indicating that it is check-in data. The state is, for example, "1". The flag is common to all two-dimensional codes TC1.

(7) IP address of communication server 4; For example, the check-in data represented by the two-dimensional code TC1A represents the IP address of the communication server 4 included in the store system 100A. The check-in data represented by the two-dimensional code TC1B represents the IP address of the communication server 4 included in the store system 100B.
(8) Domain name of relay server 200 . The domain name is common to all two-dimensional codes TC1. However, a plurality of relay servers 200 with different domain names may be used separately for each store. In this case, the check-in data represented by the two-dimensional code TC1 represents the domain name of the relay server 200 used at the corresponding store.
(9) the address of the electronic receipt server 600; The address may be common to all two-dimensional codes TC1, or one of a plurality of addresses may be represented for each two-dimensional code TC1.

(10) A flag indicating whether the user terminal 300 should use wireless communication with the access point 6 or wireless communication with the communication network 700 for exchanging data with the store system 100 . For example, in the store A, if wireless communication with the access point 6 is used for exchanging data between the store system 100A and the user terminal 300, the flag is set to "1", for example. For example, in store B, if wireless communication with communication network 700 is used for exchanging data between store system 100B and user terminal 300, the flag is set to "0", for example.
(11) SSID (service set identifier) for identifying the access point 6; For example, the check-in data represented by the two-dimensional code TC1A represents the SSID that identifies the access point 6 included in the store system 100A. The check-in data represented by the two-dimensional code TC1B represents the SSID of the access point 6 included in the store system 100B.
(12) a password for accessing the access point 6; For example, the check-in data represented by the two-dimensional code TC1A represents the password set for the access point 6 included in the store system 100A. The check-in data represented by the two-dimensional code TC1B represents the password set for the access point 6 included in the store system 100B.

(13) Identification number of the security method used by the access point 6; For example, "1" is assigned to the WPA2-PSK system, "2" is assigned to the WPA-PSK system, and "3" is assigned to the WEP system. For example, if the access point 6 included in the store system 100A uses the WPA2-PSK system as the security system, the check-in data represented by the two-dimensional code TC1A represents "1" as the identification number. Also, for example, if the access point 6 included in the store system 100B uses the WPA-PSK system as the security system, the check-in data represented by the two-dimensional code TC1B represents "2" as the identification number.
(14) A flag for identifying whether to treat an error when the user terminal 300 fails to connect to the relay server 200 or to continue operation without indicating an error. For example, in store A, if an error is set when user terminal 300 fails to connect to relay server 200, the check-in data represented by two-dimensional code TC1A represents, for example, "1" as the flag. . For example, if store B is configured to continue operation even if user terminal 300 fails to connect to relay server 200, the check-in data represented by two-dimensional code TC1B is set to "0" as the flag. show.

(15) a transmission mode identification number for the status of the user terminal 300; The transmission modes include, for example, a first mode, a second mode and a third mode. For the identification number of the transmission mode, for example, "1" is assigned to the first mode, "2" to the second mode, and "3" to the third mode. In the first mode, the status of user terminal 300 is transmitted to relay server 200 . In the second mode, the status of user terminal 300 is transmitted to store system 100 . In the second mode, the status of user terminal 300 is not transmitted. For example, in store A, if the first mode is applied as the transmission mode, the check-in data represented by the two-dimensional code TC1A represents "1" as the identification number. Also, for example, in store B, if the second mode is applied as the transmission mode, the check-in data represented by the two-dimensional code TC1B represents "2" as the identification number.

(16) A transmission mode identification number for a log file storing log data of the user terminal 300 . The transmission modes include, for example, a first mode, a second mode, a third mode and a fourth mode. For the identification numbers of the transmission modes, for example, "1" is assigned to the first mode, "2" to the second mode, "3" to the third mode, and "4" to the fourth mode. . In the first mode, log files are sent only to relay server 200 . In the second mode, the log file is sent only to the store system 100. FIG. In the third mode, log files are sent to both store system 100 and relay server 200 . In the fourth mode, log files are not sent. For example, in store A, if the first mode is applied as the transmission mode, the check-in data represented by the two-dimensional code TC1A represents "1" as the identification number. Also, for example, in store B, if the second mode is applied as the transmission mode, the check-in data represented by the two-dimensional code TC1B represents "2" as the identification number.

(17) A host name or IP address used when sending the log file to the relay server 200 via the communication network 700 by FTP (file transfer protocol).
(18) A user name used when sending a log file to relay server 200 via communication network 700 by FTP.
(19) A password used when sending a log file to relay server 200 via communication network 700 by FTP.
(20) A path name of a log file to be sent to relay server 200 via communication network 700 by FTP.

(21) A flag for identifying whether or not to delete the check digit of UPC (universal product cord), which is a type of product code. For example, in store A, if the check digit is not deleted, the check-in data indicated by the two-dimensional code TC1A indicates "1" as the flag. Further, for example, in store B, if the operation is to delete the check digit, the check-in data represented by the two-dimensional code TC1B represents, for example, "0" as the flag.
(22) The time until the user terminal 300 automatically transitions the camera screen. The check-in data represented by the two-dimensional code TC1A represents the time preset for the store A as the time. The check-in data represented by the two-dimensional code TC1B represents the time preset for the store B as the time.
(23) A timeout period when the user terminal 300 communicates with the store system 100 via the access point 6; The check-in data represented by the two-dimensional code TC1A represents the time preset for the store A as the time. The check-in data represented by the two-dimensional code TC1B represents the time preset for the store B as the time.

(24) The number of allowed retries when communication between the user terminal 300 and the store system 100 via the access point 6 times out. The check-in data represented by the two-dimensional code TC1A represents the number of times preset for the store A as the number of times. The check-in data represented by the two-dimensional code TC1B represents the number of times preset for the store B as the relevant time.
(25) A time-out period when the user terminal 300 communicates with the store system 100 via the relay server 200; The check-in data represented by the two-dimensional code TC1A represents the time preset for the store A as the time. The check-in data represented by the two-dimensional code TC1B represents the time preset for the store B as the time.
(26) The number of allowed retries when communication between the user terminal 300 and the store system 100 via the relay server 200 times out. The check-in data represented by the two-dimensional code TC1A represents the number of times preset for the store A as the number of times. The check-in data represented by the two-dimensional code TC1B represents the number of times preset for the store B as the relevant time.

(27) Authentication data used in authentication processing for authenticating a declaration of completion of confirmation regarding transactions for products that require confirmation by a store clerk. The check-in data represented by the two-dimensional code TC1A represents authentication data preset for the store A. The check-in data represented by the two-dimensional code TC1B represents authentication data preset for the store B. The authentication data is preferably determined differently for each store, but the same authentication data may be set for different stores.
(28) data for identifying the operation mode of the store system 100; For example, if the store system 100A is set to the normal mode in which the transaction processing system is normally operated, the check-in data represented by the two-dimensional code TC1A represents, for example, "1". Also, for example, if the store system 100B is set to a demo mode for demonstrating the transaction processing system, the check-in data represented by the two-dimensional code TC1B represents, for example, "2".
(29) data for identifying the mode of data transfer to accounting machine 5; For example, if the store system 100A is set to a mode that requests data transfer from the checkout machine 5 to the mobile controller 3, the check-in data represented by the two-dimensional code TC1A represents, for example, "1". Also, for example, if the store system 100B is set to a mode in which data is transferred from the mobile controller 3 to the checkout machine 5 without a request from the checkout machine 5, the check-in data represented by the two-dimensional code TC1B is For example, it represents "2".

(30) A flag indicating whether or not payment by the code payment method by operating the user terminal 300 is permitted. For example, if store A permits the code payment, the check-in data represented by the two-dimensional code TC1A will indicate "1" as the flag. Also, for example, if the code payment is not permitted at the store B, the check-in data represented by the two-dimensional code TC1B represents, for example, "0" as the flag.
(31) A flag for identifying whether or not the user terminal 300 permits registration of an age-restricted product for which the purchaser's age limit is set. For example, if the store A permits the registration of age-restricted products on the user terminal 300, the check-in data represented by the two-dimensional code TC1A represents, for example, "1" as the flag. Also, for example, if the code payment is not permitted at the store B, the check-in data represented by the two-dimensional code TC1B represents, for example, "0" as the flag.
(32) Data for identifying the member code input mode of the point member. For example, if the store system 100A is set to the manual input mode of the membership code, the check-in data represented by the two-dimensional code TC1A represents, for example, "1" as the data. Also, for example, if the store system 100B is set to a mode in which a member code is entered by reading a barcode, the check-in data represented by the two-dimensional code TC1B represents, for example, "2".

(33) A flag for identifying whether confirmation by a store clerk is required when entering a member code when a mode for manually entering a member code of a point member is set. For example, if the store A requires the confirmation, the check-in data indicated by the two-dimensional code TC1A indicates, for example, "1" as the flag. Further, for example, if the confirmation is not required at the store B, the check-in data represented by the two-dimensional code TC1B represents, for example, "0" as the flag.
(34) A threshold for checking the remaining battery level of the user terminal 300 at check-in. The threshold is set for each store or each business. For example, if the operator of store A sets the threshold as "20%", the check-in data represented by the two-dimensional code TC1A represents, for example, "20" as the threshold. Further, for example, if the store B defines the threshold as "25%", the check-in data represented by the two-dimensional code TC1B represents, for example, "25" as the threshold.
The above is an example of information represented by check-in data. However, the check-in data may not include some of the various types of information shown above. Also, the check-in data may represent information different from the various types of information shown above.

FIG. 2 is a block diagram showing the essential circuit configuration of the store server 1. As shown in FIG.
Store server 1 includes processor 11 , main memory 12 , auxiliary storage unit 13 , communication interface 14 and transmission line 15 . The processor 11 , main memory 12 , auxiliary storage unit 13 and communication interface 14 can communicate with each other via a transmission path 15 . A computer for controlling the store server 1 is configured by connecting the processor 11, the main memory 12, and the auxiliary storage unit 13 via a transmission line 15. FIG.

The processor 11 corresponds to the central portion of the computer. The processor 11 executes information processing for realizing various functions of the store server 1 according to information processing programs such as an operating system and application programs. The processor 11 is, for example, a CPU (central processing unit).

The main memory 12 corresponds to the main memory portion of the computer. Main memory 12 includes a non-volatile memory area and a volatile memory area. The main memory 12 stores the above information processing program in a nonvolatile memory area. The main memory 12 may store data necessary for the processor 11 to execute information processing in a non-volatile or volatile memory area. The main memory 12 uses a volatile memory area as a work area in which data is appropriately rewritten by the processor 11 . The non-volatile memory area is, for example, ROM (read only memory). A volatile memory area is, for example, a RAM (random access memory).

The auxiliary storage unit 13 corresponds to the auxiliary storage portion of the computer. As the auxiliary storage unit 13, a storage unit using a well-known storage device such as EEPROM (electric erasable programmable read-only memory), HDD (hard disc drive), or SSD (solid state drive) can be used. The auxiliary storage unit 13 stores data used by the processor 11 in performing various types of processing, data created by processing in the processor 11, and the like. The auxiliary storage unit 13 may store the above information processing program.

The communication interface 14 performs data communication with each unit connected to the in-store communication network 7 according to a predetermined communication protocol. As the communication interface 14, for example, a known communication device for LAN can be applied.
The transmission line 15 includes an address bus, a data bus, a control signal line, etc., and transmits data and control signals exchanged between the connected units.

The auxiliary storage unit 13 stores a store management application AP11, which is one of information processing programs. The store management application AP11 is an application program, and describes information processing for realizing the functions of the store server 1 . The store management application AP11 may be a separate application that is created in accordance with the store management policy of each store or each company that manages the store. For example, if the sales data management method differs between store A and store B, the store management application AP11 used in the store system 100A provides a sales data management method suitable for the sales data management method at store A. Information processing is described, and the store management application AP11 used in the store system 100B describes information processing for managing sales data adapted to the sales data management method at the store B. FIG.

A part of the storage area of the auxiliary storage unit 13 is used as the database group DB11. The database group DB11 includes multiple databases for managing various types of information. One of the databases included in the database group DB11 is a product database for managing products sold at stores. A product database is a collection of data records associated with managed products. A data record in the product database contains data about the associated product, such as product code, price, and product name. The merchandise code is an identification code determined for identifying merchandise for each SKU (stock keeping unit), and for example, a JAN (Japanese article number) code is used. The product name is a name that is determined so that the product can be easily distinguished by humans. The price is the amount of money that is the consideration for the sale of the product.

One of the databases included in the database group DB11 is a user database for managing store users. A customer database is a collection of data records associated with customers registered as customers of a store. A data record in the user database contains data about the associated customer, such as a user code and attribute information for identifying the user. The user code is a unique identification code determined for each user of the store to individually identify the user of the store. Attribute information may include name, gender, age, address, phone number, and the like. Data records in the user database may also include payment information reported by store users. The payment information is a credit number, code payment ID (identifier), or the like. If a plurality of payment methods can be selected, the payment information may include a payment method code for identifying the payment method. In addition, in the case of a store that provides point services, the data record of the user database may include an identifier (hereinafter referred to as a point ID) for identifying the user of the point service and the number of points held. . A data record of the user database may also include a user identifier (hereinafter referred to as an electronic receipt ID) for identifying the user of the electronic receipt service. The various data contained in the data records of the user database need not contain substantive data for all users. For example, the user database may include only point IDs or electronic receipt IDs for which the user has applied for registration in advance.

In addition, the database group DB11 may include various databases managed by a POS server in an existing POS system. It should be noted that what kind of databases the database group DB11 includes, or what kind of data these databases contain in what kind of structure may be determined for each store.

FIG. 3 is a block diagram showing the essential circuit configuration of the virtual POS server 2. As shown in FIG.
The virtual POS server 2 includes a processor 21 , main memory 22 , auxiliary storage unit 23 , communication interface 24 and transmission line 25 . The processor 21 , main memory 22 , auxiliary storage unit 23 and communication interface 24 can communicate with each other via a transmission path 25 . A computer for controlling the virtual POS server 2 is configured by connecting the processor 21 , the main memory 22 and the auxiliary storage unit 23 via a transmission path 25 . The functions of the processor 21, the main memory 22, the auxiliary storage unit 23, the communication interface 24, and the transmission line 25 are roughly equivalent to those of the processor 11, the main memory 12, the auxiliary storage unit 13, the communication interface 14, and the transmission line 15. Therefore, its description is omitted.

However, the auxiliary storage unit 23 stores the virtual POS application AP21 instead of the store management application AP11. The virtual POS application AP21 is an application program and describes transaction processing. The virtual POS application AP21 may be a separate application that is created in accordance with the store management policy of each store or each company that manages the store. For example, if store A provides a discount service that is not available at store B, virtual POS application AP21 used in store system 100A describes information processing for realizing the discount service, and store system 100B The virtual POS application AP21 used in , does not describe information processing for realizing the discount service.

Part of the storage area of the auxiliary storage unit 23 is used as a transaction database DB21 instead of the database group DB11. The transaction database DB21 is a collection of data records associated with transactions with customers who are shopping around the store. Data records in the transaction database DB21 include transaction codes and product data related to products registered as purchased products. A transaction code is a unique identification code set for each transaction to identify each transaction. The product data represents product code, product name, price, quantity, and the like. The structure of the transaction database DB21 may be individually determined in accordance with the store operation policy of each store or each business operator that operates the store.

FIG. 4 is a block diagram showing the main circuit configuration of the mobile controller 3. As shown in FIG.
The mobile controller 3 includes a processor 31 , main memory 32 , auxiliary storage unit 33 , communication interface 34 and transmission path 35 . The processor 31 , main memory 32 , auxiliary storage unit 33 and communication interface 34 can communicate via a transmission line 35 . A computer for controlling the mobile controller 3 is configured by connecting the processor 31 , the main memory 32 and the auxiliary storage unit 33 via a transmission line 35 . The functions of the processor 31, the main memory 32, the auxiliary storage unit 33, the communication interface 34, and the transmission line 35 are roughly equivalent to those of the processor 11, the main memory 12, the auxiliary storage unit 13, the communication interface 14, and the transmission line 15. Therefore, its description is omitted.

However, the auxiliary storage unit 33 stores a transaction management application AP31 instead of the store management application AP11. The transaction management application AP31 is an application program and describes management processing and mediation processing. The transaction management application AP31 is common to each store system 100 . However, various settings for information processing based on the transaction management application AP31 may be customized for each store system 100 .

Part of the storage area of the auxiliary storage unit 23 is used as a transaction management database DB31 and a registration database DB32 instead of the database group DB11. The structures of these transaction management database DB31 and registration database DB32 are common to each store system 100. FIG.

FIG. 5 is a schematic diagram showing the main data structure of the data record DR1 included in the transaction management database DB31.
The transaction management database DB31 is a collection of data records DR1 associated with the user terminals 300 or cart terminals 400 used by customers in the store. Therefore, when there is only one customer in the store, the transaction management database DB31 contains one data record DR1. Also, when there is no customer in the store, the transaction management database DB31 does not contain the data record DR1. Data record DR1 then includes fields F11, F12, F13, and F14.

A terminal code for identifying the associated user terminal 300 or cart terminal 400 is set in the field F11. As the terminal code, for example, a unique identification code set for each communication terminal in order to identify each communication terminal used as the user terminal 300 or the cart terminal 400 can be used. Alternatively, as the terminal code, for example, an identification code that is set for the smartphone POS application or the cart terminal application when installing the smartphone POS application or the cart terminal application described later in the user terminal 300 or the cart terminal 400 can be used. . A member code for distinguishing a customer using the associated user terminal 300 or cart terminal 400 from other customers is set in the field F12. The field F13 is set with the transaction code of the transaction performed using the associated user terminal 300 or cart terminal 400 . An electronic receipt ID is set in the field F14 as required. Note that the data record DR1 may include another field in which data different from the fields F11 to F14 is set.

FIG. 6 is a schematic diagram showing the main data structure of the data record DR2 included in the registration database DB32.
The registration database DB32 is a collection of data records DR2 associated with transactions with customers who are shopping around the store. Data record DR2 then includes fields F21 and F22. Data record DR1 may also include fields F23, F24, .

Field F21 is set with the transaction code of the associated transaction. This transaction code is identical to the transaction code set in field F12 of data record DR1 associated with user terminal 300 used in the associated transaction. Field F22 is set with registration data regarding the attempted product registration for the associated transaction. Registration data will be described later.

Data record DR2 includes fields after field F23 if registration of more than one purchase item is being attempted for the associated transaction. The same registration data as the field F12 is set in the fields after the field F23.

FIG. 7 is a block diagram showing the main circuit configuration of the user terminal 300. As shown in FIG.
A user terminal 300 includes a processor 301, a main memory 302, an auxiliary storage unit 303, a touch panel 304, a camera 305, a wireless communication unit 306, a mobile communication unit 307, a transmission line 308, and the like. Processor 301 , main memory 302 , auxiliary storage unit 303 , touch panel 304 , camera 305 and mobile communication unit 307 can communicate with each other via transmission line 308 . A computer for controlling the user terminal 300 is configured by connecting the processor 301 , the main memory 302 and the auxiliary storage unit 303 via a transmission line 308 . The functions of the processor 301, the main memory 302, the auxiliary storage unit 303, and the transmission line 308 are roughly the same as those of the processor 11, the main memory 12, the auxiliary storage unit 13, and the transmission line 15, so the description thereof will be omitted.

The touch panel 304 functions as an input device and display device for the user terminal 300 .
The camera 305 includes an optical system and an image sensor, and uses the image sensor to generate image data representing an image within a field of view formed by the optical system.

The wireless communication unit 306 exchanges data with the access point 6 by wireless communication according to a wireless communication protocol. As the wireless communication unit 306, for example, a well-known communication device conforming to the IEEE802.11 standard can be used.
Mobile communication unit 307 is an interface for data communication over communication network 700 . As the mobile communication unit 307, for example, a well-known communication device for performing data communication via a mobile communication network can be used.

The auxiliary storage unit 303 stores a smartphone POS application AP301, which is one of information processing programs. The smartphone POS application AP301 is an application program, and describes information processing (hereinafter referred to as smartphone UI processing) for causing the user terminal 300 to function as a user interface of the store system 100, which will be described later. A smartphone POS application AP 301 is commonly used by a plurality of user terminals 300 .

FIG. 8 is a block diagram showing the essential circuitry of the cart terminal 400. As shown in FIG.
The cart terminal 400 has a tablet computer 401 , a scanner 402 , a reader 403 and a camera 404 .

The tablet computer 401 includes a processor 401a, a main memory 401b, an auxiliary storage unit 401c, a wireless communication unit 401d, a touch panel 401e, a sound unit 401f, an interface unit 401g and a transmission line 401h. The processor 401a, main memory 401b, auxiliary storage unit 401c, wireless communication unit 401d, touch panel 401e, sound unit 401f, and interface unit 401g can communicate via a transmission path 401h. A computer for controlling the cart terminal 400 is configured by connecting the processor 401a, the main memory 401b, and the auxiliary storage unit 401c via a transmission line 401h. The functions of the processor 401a, the main memory 401b, the auxiliary storage unit 401c, the touch panel 401e, the wireless communication unit 401d, and the transmission path 401h are summarized as follows: , and the transmission line 15, the description thereof will be omitted.

However, the auxiliary storage unit 401c stores the cart terminal application AP401 instead of the store management application AP11. The cart terminal application AP401 is an application program, and describes information processing (hereinafter referred to as cart UI processing) for causing the cart terminal 400 to function as a user interface of the store system 100, which will be described later.
A cart terminal application AP 401 is commonly used by a plurality of cart terminals 400 .

The sound unit 401f outputs various sounds such as voice and melody.
A scanner 402, a reader 403 and a camera 404 are connected to the interface unit 401g. The interface unit 401g interfaces the exchange of data between the scanner 402, the reader 403 and the camera 404 and the processor 401a. An existing USB (universal serial bus) controller or the like can be used as the interface unit 401g.

Scanner 402 reads code symbols such as bar codes or two-dimensional data codes. The scanner 402 is mainly used to read a code symbol indicated on a product and representing a product code or the like of the product. Scanner 402 may be used to read code symbols shown on a membership card or displayed on a mobile device and representing a membership code or the like. The scanner 402 outputs data represented by the read code symbols. The scanner 402 may be of a type that reads code symbols by scanning laser light, or may be of a type that reads code symbols from an image captured by an imaging device.

A reader 403 reads and outputs data recorded on a recording medium. The reader 403 is a magnetic card reader when the recording medium is a magnetic card, and is an IC card reader when the recording medium is a contact IC card. An RFID reader is used as the reader 403 in the case of a recording medium using RFID (radio frequency identification) such as a contactless IC card or a smart phone.
The camera 404 captures a bird's-eye view of the inside of the shopping basket placed on the shopping cart C1.
The camera 404 then outputs image data representing the captured image.

As hardware for the store server 1, the virtual POS server 2, or the mobile controller 3, for example, a general-purpose server device can be used. When transferring the store server 1, the virtual POS server 2 or the mobile controller 3, the store management application AP11, the virtual POS application AP21 or the transaction management application AP31 is generally stored in the auxiliary storage unit 13, 23 or 33, and the database group DB11, This is done in a state where the transaction database DB21, or the transaction management database DB31 and the registration database DB32 are not stored. However, the store management application AP11, the virtual POS application AP21, or the transaction management application AP31 is not stored in the auxiliary storage units 13, 23, or 33, or another version of the same type of application program is stored in the auxiliary storage units 13, 23, or 33. The hardware in the state of being stored and the store management application AP11, the virtual POS application AP21, or the transaction management application AP31 may be individually transferred. By writing the store management application AP11, the virtual POS application AP21, or the transaction management application AP31 to the auxiliary storage unit 13, 23, or 33 according to the operation of an arbitrary worker, the store server 1, the virtual POS server 2, or the A mobile controller 3 may be configured. Transfer of the store management application AP11, virtual POS application AP21, or transaction management application AP31 is performed by recording on a removable recording medium such as a magnetic disk, magneto-optical disk, optical disk, or semiconductor memory, or by communication via a network. be able to. The transaction database DB21, or the transaction management database DB31 and the registration database DB32 are stored in the auxiliary storage unit 13 by the processor 11, 21 or 31 executing information processing based on the store management application AP11, the virtual POS application AP21, or the transaction management application AP31. , 23 or 33. At least part of the databases included in the store management application AP11 and the database group DB11 may be stored in the main memory 12 . At least part of the virtual POS application AP21 and transaction database DB21 may be stored in the main memory 22 . At least part of the transaction management application AP31, the transaction management database DB31, and the registration database DB32 may be stored in the main memory 32.

Next, the operation of the transaction processing system configured as above will be described. It should be noted that the contents of the various processes described below are only examples, and it is possible to change the order of some of the processes, omit some of the processes, or add other processes as appropriate. For example, in the following description, description of some processes is omitted in order to facilitate understanding of the characteristic operation of the present embodiment. For example, when some kind of error occurs, processing may be performed to deal with the error, but a part of such processing is omitted.

A service provided to a customer using the user terminal 300 through the operation of the transaction processing system is called a smartphone POS service. A service provided by the operation of the transaction processing system to the customer using the cart terminal 400 is called a cart POS service.
The user terminal 300 exchanges data with the store system 100 in order to use the smartphone POS service. It is determined by the state of the flag included in the check-in data. However, for the sake of simplification of explanation, the case of using wireless communication with the access point 6 will be explained below. In addition, there is a mode in which data transfer from the virtual POS server 2 to the accounting machine 5 is requested to the accounting machine 5 in order to make accounting by the accounting machine 5, and a mode in which data transfer from the accounting machine 5 to the mobile controller 3 is requested. Which of the modes for transferring data from the mobile controller 3 to the checkout machine 5 is used depends on the state of the flag included in the check-in data. However, for the sake of simplification, the following description assumes that the mode of requesting data transfer from the accounting machine 5 to the mobile controller 3 is fixedly used.

In order to use the smartphone POS service, the customer installs the smartphone POS application AP301 on his or her own smartphone or the like so that it can be used as the user terminal 300 . Alternatively, the customer rents a user terminal 300 configured by installing a smartphone POS application AP301 on a tablet terminal or the like at the store. Then, the customer enters one of the stores provided with the store system 100 with the user terminal 300 in a state in which information processing based on the smartphone POS application AP301 is activated.

If the customer wants to confirm the result of the transaction using the smartphone POS service by using the electronic receipt service, the customer registers for use of the electronic receipt service. An electronic receipt ID is assigned to the customer by this usage registration. Then, the customer stores the electronic receipt ID assigned to the customer in the user terminal 300 owned by the customer. Also, in a member database managed by the store to manage customers, the electronic receipt ID may be stored in association with the point ID. In this case, the customer may store the point ID assigned to the customer in the user terminal 300 owned by the customer.

The processor 301 in the user terminal 300 acquires an electronic receipt ID or point ID through setting processing based on the smartphone POS application AP301, and stores it in the auxiliary storage unit 303 as registration data related to the smartphone POS application AP301. For example, when the operator requests registration of an electronic receipt ID, the processor 301 causes the operator to specify a login ID and a login password for authenticating the user in the electronic receipt server 600 . The processor 301 then logs into the electronic receipt server 600 using the specified login ID and login password, acquires the electronic receipt ID of the user identified by the login ID, and stores it in the auxiliary storage unit 303 . . For example, the processor 301 may cause the operator to specify an electronic receipt ID and store the specified electronic receipt ID in the auxiliary storage unit 303 . For example, when the operator requests registration of the point ID, the processor 301 causes the operator to specify the point ID and stores the specified point ID in the auxiliary storage unit 303 . As the point ID, a point card number or the like assigned to the point card distributed to the customer is used. When registration of the electronic receipt ID and the point ID are requested in sequence, the processor 301 executes the above processes individually and stores both the electronic receipt ID and the point ID in the auxiliary storage unit 303. . However, the processor 301 may store only one predetermined one.

9, 10, 11 and 12 are flowcharts of smartphone UI processing executed by the processor 301 according to the smartphone POS application AP301.
First, as ACT 101 shown in FIG. 9, the processor 301 causes the touch panel 304 to display the main menu screen. The main menu screen is a screen for receiving designation of any one of several processes to be performed according to the smartphone POS application AP301. A plurality of GUI elements including a GUI (graphical user interface) element for designating the start of shopping are arranged on the main menu screen. Note that the GUI elements are, for example, soft keys.

As ACT 102, the processor 301 confirms whether or not the start of shopping has been specified. If the processor 301 cannot confirm the corresponding designation, it determines NO and proceeds to ACT103.
As ACT 103, the processor 301 confirms whether or not a designation other than the start of shopping has been made. If the processor 301 cannot confirm the designation, the processor 301 determines NO and returns to ACT102.
Thus, processor 301 as ACT 102 and ACT 103 waits for some designation on the main menu screen. Then, if the processor 301 has made a designation other than the start of shopping, it determines YES in ACT 103 and proceeds to the designated processing. A description of the processing of the processor 301 in this case is omitted. The processing of the processor 301 for registering the electronic receipt ID or point ID described above may be one of the processing here.

When the customer enters the store and starts shopping, the customer performs a predetermined operation for designating the start of shopping on the main menu screen. For example, when the operation is detected on the touch panel 304 , the processor 301 determines YES in ACT 102 and proceeds to ACT 104 .
As ACT 104, the processor 301 causes the touch panel 304 to display a scan screen for check-in. The scan screen for check-in is a screen prompting the customer to read the two-dimensional code TC1 for check-in. The processor 301, for example, activates the camera 305, and displays a text message prompting the customer to read the two-dimensional code TC1 and an indication of the position where the two-dimensional code TC should be held in the image obtained by the camera 305. Lines are superimposed to generate a scan screen.

When the scan screen is displayed on the touch panel 304, the customer points the camera 305 at the two-dimensional code TC1 posted near the entrance of the store so that the two-dimensional code TC1 is reflected in the scan screen.

As ACT 105, the processor 301 waits for the two-dimensional code to be read. At this time, the processor 301 repeatedly analyzes the image obtained by the camera 305 and attempts to read the two-dimensional code. This reading of the two-dimensional code may be performed as processing based on the smartphone POS application AP301, or may be performed as processing based on another application program for reading the two-dimensional code. If the two-dimensional code can be read, the processor 301 determines YES and proceeds to ACT106.

As ACT 106, the processor 301 confirms whether or not the data represented by the read two-dimensional code is check-in data. If it is not check-in data, the processor 301 determines NO and returns to ACT105. At this time, the processor 301 may cause the touch panel 304 to display a screen notifying the customer that an incorrect two-dimensional code has been read.

If the processor 301 can confirm that the data represented by the read two-dimensional code is check-in data, it determines YES in ACT 106 and proceeds to ACT 107 .
As ACT 107 , the processor 301 stores the read check-in data in the main memory 302 or the auxiliary storage unit 303 .

As ACT 108, the processor 301 requests the mobile controller 3 to check-in. Specifically, processor 301 establishes wireless communication between wireless communication unit 306 and access point 6 based on the data represented by the check-in data. For example, if the customer points the camera 305 at the two-dimensional code TC1A at the store A, the processor 301 communicates wirelessly with the access point 6 provided in the store system 100A based on the check-in data represented by the two-dimensional code TC1A. Establish communication. The processor 301 then transmits request data for requesting check-in to the mobile controller 3 via wireless communication with the access point 6 . When wireless communication with the access point 6 provided in the store system 100A is established as described above, the request data is sent via the access point 6 provided in the store system 100A and the in-store communication network 7. and transmitted to the mobile controller 3 provided in the store system 100A. Note that the processor 301 includes identification data for identifying a check-in request and a terminal code in the request data for requesting check-in. If the customer is a registered user of the smartphone POS service and has a member code, the processor 301 also includes the member code in the request data. The membership code is stored in the auxiliary storage unit 303 of the user terminal 300, for example. If the point ID is stored in the auxiliary storage unit 303, the processor 301 also includes the point ID in the request data. Processor 301 may include other data in the request data, such as data for authenticating the guest, for example.

Various requests from the user terminal 300 to the mobile controller 3, which will be described later, send request data including identification data for identifying the reason for the request to the access point 6 and the in-store communication network 7 in the same manner as described above. It is realized by sending from the user terminal 300 to the mobile controller 3 via.

When the cart terminal 400 is activated, the processor 401a executes cart UI processing described below in accordance with the cart terminal application AP401.
FIG. 13 is a flowchart of cart UI processing executed by the processor 401a.

As ACT 161, the processor 401a notifies the mobile controller 3 of the activation. The processor 401a transmits notification data for activation notification to the mobile controller 3 via wireless communication between the wireless communication unit 401d and the access point 6. FIG. The relevant notification data is transmitted to the mobile controller 3 via the access point 6 and the in-store communication network 7 .
As ACT 162, the processor 401a waits for the usage start operation.
At this time, the processor 401a is in a state of waiting for the start of shopping using the attached shopping cart C1. For example, in this standby state, the processor 401a causes the touch panel 401e to display a screen showing a start button. When using the cart POS service, the customer takes out one of the shopping carts C1 placed in the cart storage area, and pre-registers the cart terminal 400 attached to the shopping cart C1 for starting use. Perform the prescribed operation. If the customer is a member, the member code recorded on the member card is read by the scanner 402 or reader 403 . If the customer is not a member, the customer operates the above start button. Then, if these operations have been performed, the processor 401a determines YES as an operation for starting use has been performed, and proceeds to ACT163.

As ACT 163, the processor 401a requests the mobile controller 3 to check-in. Specifically, the processor 401 a transmits request data for requesting check-in to the mobile controller 3 via wireless communication between the wireless communication unit 401 d and the access point 6 . The requested data is transmitted to the mobile controller 3 via the access point 6 and the in-store communication network 7 . The request data for requesting check-in includes identification data for identifying the check-in request and a terminal code for identifying the cart terminal 400 on which the processor 401a is mounted. , including the aforementioned membership code. When the start button is touched, the processor 401a notifies the virtual POS server 2 of a membership code predetermined for non-members. Membership codes for non-members may be common to a plurality of customers, or may be different. The relevant notification data is transmitted to the mobile controller 3 via the access point 6 and the in-store communication network 7 .

Various requests from the cart terminal 400 to the mobile controller 3, which will be described later, send request data including identification data for identifying the reason for the request to the access point 6 and the in-store communication network 7 in the same manner as described above. It is realized by sending from the user terminal 300 to the mobile controller 3 via.

The processor 31 in the mobile controller 3 executes management processing according to the transaction management application AP31.
FIG. 14 is a flow chart of management processing by the processor 31 .

In ACT 181, the processor 31 confirms whether or not a start notification has been received. If the notification cannot be confirmed, the processor 31 determines NO and proceeds to ACT182.
As ACT 182, the processor 31 confirms whether or not a check-in request has been made. If the request cannot be confirmed, the processor 31 determines NO and proceeds to ACT183.
As ACT 183, the processor 31 confirms whether or not the mediation process has ended. If the processor 31 cannot confirm the end of the mediation process, it determines NO and returns to ACT181.
Thus, in ACT181-ACT183, the processor 31 waits for an activation notification, a check-in request, or the end of mediation processing.

The processor 31 determines YES in ACT 181 and proceeds to ACT 184 when the communication interface 34 receives the notification data for the activation notification transmitted from the cart terminal 400 as described above.
As ACT 184 processor 31 updates the cart list. The cart list is data representing a list of terminal codes of cart terminals 400 in operation. The cart list is stored in main memory 32 or auxiliary storage unit 33 . Processor 31, for example, updates the cart list to include the terminal code included in the notification data above. The processor 31 may acquire various data related to the cart terminal 400 such as the SSID of the cart terminal 400 from the cart terminal 400 and describe the data in the cart list in association with the terminal code. The processor 31 then returns to the standby state of ACT181-ACT183.
Although a detailed description is omitted, the processor 31 updates the cart list so as to delete the terminal code of the cart terminal 400 when detecting that the cart terminal 400 has stopped operating.

If the request data for the check-in request transmitted from the user terminal 300 or the cart terminal 400 is received by the communication interface 34 as described above, the processor 31 determines YES in ACT 182 and proceeds to ACT 185. .
In ACT 185, the processor 31 confirms whether or not the virtual POS server 2 can start new transaction processing. As will be described later, the virtual POS server 2 executes multiple transaction processes in parallel. However, due to resource limitations such as the processing power of the processor 21, the number of transactions that can be executed in parallel (hereinafter referred to as the maximum number) is limited. For example, if the total number of transaction processes being executed by the processor 21 at that time is less than the maximum number, the processor 31 determines YES as startable, and proceeds to ACT 186 .

In ACT 186, the processor 31 confirms whether or not it is the cart terminal 400 that is requesting check-in. For example, the processor 31 checks whether the terminal code included in the request data is included in the cart list. If the corresponding terminal code is not included in the cart list, the processor 31 judges that it is the user terminal 300 that is requesting check-in, and proceeds to ACT187.
The processor 31 may confirm which of the user terminal 300 and the cart terminal 400 is requesting check-in based on the type data included in the request data. However, in this case, at least one of the processor 301 of the user terminal 300 and the processor 401a of the cart terminal 400 includes the type data for distinguishing between the user terminal 300 and the cart terminal 400 in the request data for requesting check-in. to
In ACT 187, the processor 31 confirms whether or not the user terminal 300 is in a state permitting the start of transaction processing. For example, if the number of transactions executed by the virtual POS server 2 for the user terminal 300 is the predetermined allowable number, the processor 31 determines NO, and proceeds to ACT188. For this determination, for example, the processor 31 compares the number of executions stored in the main memory 32 or the auxiliary storage unit 33 with respect to the mediation process for the user terminal 300 as described later with the allowable number.

As an example, for each store, the manager of the store system 100 or the like determines the limit of the number of cart terminals 400 to be operated simultaneously within the store. The processor 31 inputs the limit number according to the operation of the administrator or the like, and stores the limit number in the main memory 32 or the auxiliary storage unit 33 . If the number limit has already been stored in the main memory 32 or the auxiliary storage unit 33, the processor 31 overwrites it with the newly input number limit. Then, the processor 31 takes the number obtained by subtracting the limit number from the maximum number as the allowable number. Specifically, if the maximum number is 24 and the limit number is 15, the allowable number is 9. In this example, it is always guaranteed that transaction processing can be executed in parallel using each of the limited number of cart terminals 400 as target terminals.

However, the limit number may be determined by the creator of the transaction management application AP31, for example, and may be fixedly applied to each store. Also, the allowable number may be determined by the creator of the transaction management application AP31, for example, and may be fixedly applied in common to each store. The allowable number may be the number obtained by subtracting the number of terminal codes described in the cart list, that is, the number of cart terminals 400 in operation, from the maximum number. Also, the allowable number is obtained by multiplying the limit number or the number of cart terminals 400 in operation by a coefficient of less than 1, or by subtracting a constant number from the number obtained by appropriately rounding the number obtained by subtracting the integer value from the maximum number. It can be a number. Also, in place of the limited number of units, the guaranteed number of connections determined as a number less than the maximum number regardless of the limited number is stored in the main memory 32 or the auxiliary storage unit 33, and the guaranteed number of connections is subtracted from the maximum number. number may be acceptable.

The processor 31 advances to ACT188 not only when ACT187 determines NO, but also when ACT185 determines NO. If the total number of transaction processes being executed by the processor 21 matches the maximum number, the processor 31 judges NO in ACT 185 as not being startable. The processor 31 obtains the above total number, for example, as the sum of two execution numbers stored in the main memory 32 or the auxiliary storage unit 33 as described later.
In ACT 188, the processor 31 notifies the user terminal 300 or cart terminal 400, which is the check-in request source, of an error that the check-in is not possible. The processor 31 then returns to the standby state of ACT181-ACT183. In other words, the processor 31 determines that the number of check-in requests made from the user terminal 300 or the cart terminal 400 or the number of executions of transaction processing related to the user terminal 300 reaches the allowable number while the virtual POS server 2 cannot start new transaction processing. A check-in request from the user terminal 300 is rejected while the user terminal 300 is on.

If the virtual POS server 2 can start a new transaction process and the check-in request is from the cart terminal 400 , the processor 31 determines YES in ACT 186 and proceeds to ACT 189 . For example, when the terminal code included in the request data is included in the cart list, the processor 31 determines YES in ACT 186 assuming that the check-in request is from the cart terminal 400 . If the virtual POS server 2 can start a new transaction process and the check-in request is from the user terminal 300, but the number of transaction processes executed for the user terminal 300 is less than the allowable number, the processor 31 , ACT 187 determines YES and advances to ACT 189 .
In ACT 189, the processor 31 starts mediation processing for the user terminal 300 or cart terminal 400 that requested check-in. Note that the mediation process is executed by the processor 31 in parallel with the management process, for example, as a process in a different thread from the management process. If the processor 31 is already executing mediation processing for another user terminal 300 or cart terminal 400, the processor 31 starts a new mediation processing in parallel with the mediation processing. That is, the processor 31 may execute multiple mediation processes in parallel.

As ACT 190, processor 31 increases the number of executions of mediation processing. The processor 31 manages, for example, the number of executions of mediation processing for the user terminal 300 and the number of executions of mediation processing for the cart terminal 400 by storing them in the main memory 12 or the auxiliary storage unit 13, for example. . After starting the mediation process for the user terminal 300 in ACT 189 , the processor 31 increments the number of executions of the mediation process for the user terminal 300 by one. Also, after starting the mediation process for the cart terminal 400 in ACT 189 , the processor 31 increments the number of executions of the mediation process for the cart terminal 400 by one. The processor 31 then returns to the standby state of ACT181-ACT183.

Processor 31 determines YES in ACT 183 and proceeds to ACT 191 when the mediation process started as described above is completed.
As ACT 191 processor 31 reduces the number of executions. For example, if the user terminal 300 is the target of the mediation process that has ended, the processor 31 decrements the number of executions of the mediation process targeting the user terminal 300 by one. In addition, if the mediation process that has ended targets the cart terminal 400, the processor 31 decrements the number of mediation processes that target the cart terminal 400 by one. The processor 31 then returns to the standby state of ACT181-ACT183.

15 and 16 are flow charts of mediation processing by the processor 31. FIG.
As described above, the processor 31 may execute a plurality of mediation processes in parallel targeting a plurality of user terminals 300 or cart terminals 400 respectively. In the following description of the intermediation process, simply referring to the user terminal 300 or cart terminal 400 indicates the user terminal 300 or cart terminal 400 that is the target of the intermediation process. If the user terminal 300 or the cart terminal 400 that is the target of the intermediary processing need not be distinguished, it will be referred to as a target terminal.

As ACT 201 in FIG. 15, the processor 31 performs check-in processing. For example, the processor 31 requests the virtual POS server 2 to start a transaction and receives notification of the transaction code. Processor 31 then adds a new data record DR1 to transaction management database DB31. Processor 31 sets the terminal code contained in the request data in field F11 of new data record DR1. Processor 31 sets the membership code in field F12 of new data record DR1 if the request data contains a membership code. Processor 31 sets the notified transaction code in field F13 of new data record DR1. If a point ID is included in the request data, the processor 31 attempts to acquire an electronic receipt ID associated with this point ID. That is, the processor 31, for example, accesses the shop server 1, checks the user database included in the database group DB11, and acquires the electronic receipt ID if the point ID is associated with the electronic receipt ID. Then, when the processor 31 can acquire the electronic receipt ID in this way, it sets the electronic receipt ID in the field F14 of the new data record DR1. As a result, management of transactions performed using the target terminal is started.

In the virtual POS server 2, the processor 21 starts transaction processing according to the virtual POS application AP21 when the mobile controller 3 requests the start of transaction.
FIG. 18 is a flow chart of transaction processing by the processor 21 .

The processor 21 initiates the transaction process each time a transaction initiation is requested. If another transaction process is already in progress, a new transaction process is started in parallel. That is, when the mobile controller 3 is executing a plurality of intermediary processes in parallel, the processor 21 executes in parallel a plurality of transaction processes corresponding to each of the plurality of intermediary processes.

In other words, the processor 31 starts intermediation processing in response to a request from the user terminal 300 or the cart terminal 400 as a terminal device, thereby performing transaction processing in response to an instruction from the requesting terminal device. Start at 21. However, the processor 31 assumes that the request source terminal device is the user terminal 300 as a terminal device belonging to the first type, and the processor 21 has already executed a predetermined allowable number of transaction processes with the user terminal 300 as the target terminal. If so, do not initiate transaction processing in response to the above request.

As ACT 301, the processor 21 executes transaction start processing. In this transaction initiation process, the processor 21 determines a transaction code according to a predetermined rule, and updates the transaction database DB21 so as to include new data records for managing purchased products in the transaction identified by the transaction code. Update. The processor 21 then notifies the mobile controller 3 of the determined transaction code.

As ACT 302, the processor 21 confirms whether or not a change of purchased product has been requested. If the processor 21 cannot confirm the corresponding request, it determines NO and proceeds to ACT303.
As ACT 303, the processor 21 confirms whether or not cancellation of the transaction has been requested. If the processor 21 cannot confirm the request, it determines NO and proceeds to ACT304.
As ACT 304, the processor 21 confirms whether payment has been requested. If the processor 21 cannot confirm the request, it determines NO and proceeds to ACT305.
In ACT 305, the processor 21 confirms whether transfer of payment data has been requested. If the processor 21 cannot confirm the corresponding request, it determines NO and proceeds to ACT306.
As ACT 306, the processor 21 confirms whether or not an end has been instructed. If the processor 21 cannot confirm the corresponding instruction, it determines NO and returns to ACT302.
Thus, the processor 21, in ACTs 302-306, waits for either a request for change, cancellation, settlement or transfer, or an instruction to terminate.

After completing the check-in process, the processor 31 of the mobile controller 3 proceeds to ACT 202 in FIG.
As ACT 202, the processor 31 confirms whether or not the check-in process has been completed normally. If the check-in process could not be completed normally due to some abnormality, the processor 31 determines NO and proceeds to ACT203.
As ACT 203, the processor 31 notifies the target terminal of the error. The processor 31 , for example, transmits notification data for error notification to the target terminal via the in-store communication network 7 and the access point 6 . The processor 31 includes identification data in the notification data to identify the error notification. Processor 31 may include an error code representing the cause of the error in the notification data. The processor 31 then terminates the mediation process.

Various notifications from the mobile controller 3 to the target terminal, which will be explained later, are similar to those described above. is transmitted from the mobile controller 3 to the target terminal.

On the other hand, if the check-in process can be completed normally, the processor 31 determines YES in ACT202 and proceeds to ACT204.
In ACT 204, the processor 31 notifies the target terminal of check-in completion.

After requesting check-in in ACT108 in FIG. 9, the processor 301 in the user terminal 300 proceeds to ACT109.
In ACT 109, the processor 301 confirms whether or not the completion of check-in has been notified. If the notification cannot be confirmed, the processor 301 determines NO and proceeds to ACT110.
As ACT 110, the processor 301 confirms whether or not a check-in error has been notified. If the notification cannot be confirmed, the processor 301 determines NO and returns to ACT109.
Thus, processor 301 as ACT 109 and ACT 110 waits to be notified of check-in completion or an error. Processor 301 determines YES in ACT110 if notification data for error notification in ACT188 in FIG. 14 or ACT203 in FIG.

As ACT 111, the processor 301 causes the touch panel 304 to display an error screen. The error screen is a screen that is defined to inform the customer that check-in is not possible. Note that the processor 301, for example, in response to the error notification in ACT 188 in FIG. 14, notifies that check-in is not possible due to the store being crowded, and also displays an error screen prompting the user to try to check-in after a while. display. It should be noted that the processor 301 returns to ACT 101 when an instruction to cancel the display of the error screen is given, for example, by operating a GUI element displayed in the error screen.

On the other hand, processor 301 determines YES in ACT 109 if the wireless communication unit 306 has received the notification data for notifying completion of check-in, and proceeds to ACT 112 in FIG.
As ACT 112, the processor 301 causes the touch panel 304 to display a list screen. The list screen is a screen showing a list of registered purchased products.

FIG. 20 is a diagram showing an example of the list screen SC1.
The list screen SC1 includes display areas AR11, AR12 and buttons BU11, BU12, BU13. The display area AR11 displays the total number of purchased products and the total price of the purchased products. The display area AR12 represents a list of purchased products. The button BU11 is a soft key for the customer to declare that he or she wants to cancel all purchased products and stop shopping. The button BU12 is a soft key for the customer to declare to start scanning products to be registered as purchased products. The button BU13 is a soft key for the customer to declare the start of checkout.
It should be noted that FIG. 20 shows the list screen SC1 in a state in which the purchased products have not yet been registered. Therefore, both the total number and the total amount are displayed in the display area AR11, and nothing is displayed in the display area AR12.

As ACT 113 in FIG. 10, the processor 301 confirms whether or not the start of product scanning has been specified. If the processor 301 cannot confirm the designation, the processor 301 determines NO and proceeds to ACT114.
As ACT 114, the processor 301 confirms whether or not a quantity change has been designated. If the processor 301 cannot confirm the corresponding designation, the processor 301 determines NO and proceeds to ACT115.
In ACT 115, the processor 301 confirms whether or not shopping stop is designated. If the processor 301 cannot confirm the corresponding designation, the processor 301 determines NO and proceeds to ACT 116 .
As ACT 116, the processor 301 confirms whether or not the start of accounting has been designated. If the processor 301 cannot confirm the corresponding designation, the processor 301 determines NO and returns to ACT113.
Thus, the processor 301 waits for any one of scan start, quantity, stop, and accounting start as ACT113 to ACT116.

If the customer registers the product as a purchased product, the customer designates the start of scanning by a predetermined operation such as touching the button BU12 on the list screen SC1. In response, the processor 301 determines YES in ACT113 and proceeds to ACT117.
As ACT 117, the processor 301 causes the touch panel 304 to display a registration screen. The registration screen is a screen prompting the customer to read the bar code representing the product code of the product to be registered as the purchased product.

FIG. 21 is a diagram showing an example of the registration screen SC2.
The registration screen SC2 includes a display area AR21, a message ME21 and a button BU21. A display area AR21 displays an image obtained by the camera 305. FIG. The message ME21 is a character message prompting the customer to read the bar code of the product. The button BU21 is a soft key for the customer to declare to stop scanning the product code.
The processor 301, for example, activates the camera 305, and superimposes a line representing the range of the display area AR21 and an image representing the message ME21 and the button BU21 on the image obtained by the camera 305 to generate the registration screen SC2. do.

As ACT 118 in FIG. 10, the processor 301 confirms whether or not the barcode has been read. At this time, the processor 301 analyzes the image obtained by the camera 305 and attempts to read the barcode. This barcode reading may be performed as processing based on the smartphone POS application AP301, or may be performed as processing based on another application program for reading barcodes. If the barcode cannot be read, the processor 301 determines NO and proceeds to ACT119.
In ACT 119, the processor 301 confirms whether or not scanning stop has been specified. If the processor 301 cannot confirm the designation, the processor 301 determines NO and returns to ACT118.
Thus, processor 301 waits in ACT 118 and ACT 119 for the bar code to be read or for an instruction to stop scanning.

If the customer wishes to return to the list screen without performing the scan this time, the customer designates to stop scanning by a predetermined operation such as touching the button BU21. In response, the processor 301 determines YES in ACT119 and returns to ACT112.

When the registration screen is displayed on the touch panel 304, the customer points the camera 305 at the product so that the bar code displayed on the product to be registered as the purchased product is reflected in the display area AR21. If the barcode can be read in response, the processor 301 determines YES in ACT 118 and proceeds to ACT 120 .
As ACT 120, the processor 301 requests the mobile controller 3 to register. The request data transmitted by the processor 301 includes data represented by the read barcode (hereinafter referred to as barcode data).
As ACT 121, the processor 301 waits for an instruction to display the list screen.

When the customer touches the area indicating the number on the list screen SC1 in the standby state of ACT113 to ACT116, the processor 301 displays a list box for specifying the number overlaid on the list screen SC1. Then, when this list box is operated, the processor 301 receives this as the specification of quantity. In this case, the processor 301 determines YES in ACT 114 in FIG. 10 and proceeds to ACT 122 in FIG.

As ACT 122, the processor 301 confirms whether or not the designated number is zero. If the specified number is not 0, the processor 301 determines NO and proceeds to ACT123.
As ACT 123, the processor 301 requests the mobile controller 3 to change the quantity. The request data transmitted by the processor 301 here includes specific data for specifying the product for which the quantity is specified and the specified quantity. The specific data may be a product code, or data that allows the mobile controller 3 to specify the purchased product, such as a number for identifying each purchased product in a list of purchased products. Note that if a product code is used as the specific code, the processor 31 includes the product code for each purchased product in the instruction data for instructing display of the list screen.

Now, if the specified number is 0, the processor 301 determines YES in ACT122 and proceeds to ACT124.
As ACT 124, the processor 301 causes the touch panel 304 to display a delete screen. The deletion screen is a screen for notifying the customer that the product for which the quantity is designated as 0 will be deleted from the purchased products. The delete screen includes a delete button for specifying deletion, and a return button for specifying to return to the state before specifying the change of the number without changing the number.

As ACT 125, the processor 301 checks whether or not deletion has been specified. If the processor 301 cannot confirm the corresponding designation, the processor 301 determines NO and proceeds to ACT126.
In ACT 126, processor 301 checks whether a return was specified. If the processor 301 cannot confirm the designation, the processor 301 determines NO and returns to ACT125.
Thus, processor 301 waits for ACT 125 and ACT 126 to specify delete or return.

If the customer wants to cancel the deletion and return to the state before specifying the quantity change, the customer specifies return by a predetermined operation such as touching a return button on the delete screen.
In response, processor 301 determines YES in ACT 126 and returns to ACT 112 in FIG. In this case, since the registration status of the purchased product is not changed, the processor 301 causes the touch panel 304 to display again the list screen SC1 in the same status that was displayed before the deletion screen was displayed.

If the customer is sure of deletion, the customer designates deletion by a predetermined operation such as touching a delete button on the delete screen. In response, the processor 301 determines YES in ACT125 and proceeds to ACT127.
As ACT 127, the processor 301 requests the mobile controller 3 to delete. The request data transmitted by the processor 301 includes specific data for identifying the product designated to be deleted.

After processor 301 has requested a quantity change in ACT 123 or a deletion in ACT 127, processor 301 proceeds to ACT 128. FIG.
In ACT 128, the processor 301 waits for an instruction to display the list screen.

Now, after the processor 31 in the mobile controller 3 notifies the completion of check-in in ACT204 in FIG. 15, it proceeds to ACT205.
As ACT 205, the processor 31 confirms whether or not a change of purchased product is requested. If the request cannot be confirmed, the processor 31 determines NO and proceeds to ACT206.
As ACT 206, the processor 31 checks whether or not cancellation of the purchased product has been requested. If the request cannot be confirmed, the processor 31 determines NO and proceeds to ACT207.
In ACT 207, processor 31 checks whether accounting has been requested. If the request cannot be confirmed, the processor 31 determines NO and proceeds to ACT208.
As ACT 208, the processor 31 confirms whether or not the time limit has passed. If not, the processor 31 determines NO and returns to ACT205.
Thus, processor 31, for ACTs 205-208, waits for any of changes, cancellations and accounts to be requested or for a time limit to expire. Processor 31 determines YES in ACT 205 if any of registration, quantity change, and deletion is requested from user terminal 300, which is the target terminal, as described above, and proceeds to ACT 209 in FIG. move on.

As ACT 209, the processor 31 transfers the request from the user terminal 300 to the virtual POS server 2 along with notification of the transaction code of the transaction to be processed. At this time, the processor 31 may transfer the request data sent from the user terminal 300 to the virtual POS server 2 as it is, or may send the request data converted by some process to the virtual POS server 2 . However, the processor 31 notifies the virtual POS server 2 of the barcode data or specific data included in the request data sent from the user terminal 300 .

If the processor 21 in the virtual POS server 2 is in the waiting state of ACT302 to ACT305 in FIG. Then, proceed to ACT307.
As ACT 307, the processor 21 updates the transaction database DB21 according to the request in the transferred request data. For example, when a request for registration is made, the processor 21 assumes that the barcode data included in the request data has been read by a barcode scanner provided in an existing POS terminal. Attempts to register the purchased product by the same processing as the POS terminal. However, for some reason, the product code represented by the bar code data may not be registered in the product database. In addition, there are cases where a bar code other than the product code is displayed on the product. Then, in these cases, the processor 21 cannot register the purchased product, resulting in an error. In this way, the processor 21 registers purchased products based on regular bar code reading. For example, when a change in quantity is requested, the processor 21 changes the quantity already indicated in the transaction database DB21 for the product whose quantity is to be changed. For example, when deletion is requested, the processor 21 updates the transaction database DB21 so as to exclude the target product from the purchased products.

As ACT 308 , the processor 21 transmits result data representing the result of the above processing to the mobile controller 3 . The processor 21 includes, in the result data, the identification data for identifying the notification of the official registration and the product code, product name and price of the registered product when the registration of the purchased product is correctly performed. When the quantity is changed, the processor 21 includes the product code of the changed product and the changed quantity in the result data. When the purchased product is deleted, the processor 21 includes the product code of the product excluded from the purchased products in the result data. If an error is detected, the processor 21 includes, in the result data, identification data for identifying an error notification and the bar code data sent with the registration request. After the processor 21 has finished transmitting the result data, it returns to the standby state of ACT302 to ACT305.

After forwarding the request in ACT 209 , the processor 31 in the mobile controller 3 proceeds to ACT 210 .
As ACT 210, the processor 31 acquires result data transmitted from the virtual POS server as described above. The processor 31 saves the acquired result data in the main memory 32 or the auxiliary storage unit 33 .

As ACT 211, the processor 31 updates the registration database DB32 based on the above result data. This registration database DB32 is updated, for example, as follows.
First case: A notification of regular registration, and the registration data including the notified product code is not included in the data record DR2 associated with the transaction to be processed.
In this case, the processor 31 adds a new field next to the last field already existing in the data record DR2 associated with the transaction being processed, and adds the new registration data to that field. The processor 31 stores the notified product code, the error flag set to "0" indicating that there is no error, the notified product name and price, the number set to "1", and the number set to "1". and a revocation flag set to "0" to indicate that it has not been revoked. Thus, the registration data added in this case has a structure as shown in the upper right side of FIG.

Second case: Although the data record DR2, which is a notice of formal registration and is associated with the transaction to be processed, contains registration data including the notified product code, the registration data is canceled. If the flag is "1" indicating that it has been canceled.
In this case, processor 31 processes in the same manner as in the first case above.

Third case: The data record DR2, which is a notification of regular registration and is associated with the transaction to be processed, contains registration data including the notified product code, and the cancellation flag of the registration data is "0".
In this case, the processor 31 rewrites the value of the quantity contained in the registration data that includes the notified product code and the cancellation flag is "0" to a value that is one larger.

Fourth case: when it is notification of quantity change.
In this case, the processor 31 finds registration data containing the notified product code from the data record DR2 associated with the transaction to be processed. The processor 31 then rewrites the number included in the corresponding registration data to the number included in the result data.

Fifth case: if it is a notice of deletion.
In this case, the processor 31 finds registration data containing the notified product code from the data record DR2 associated with the transaction to be processed. Processor 31 then changes the cancellation flag included in the corresponding registration data to "1".

Sixth case: when it is an error notification.
In this case, the processor 31 adds a new field next to the last field already existing in the data record DR2 associated with the transaction being processed, and adds the new registration data to that field. The processor 31 includes the notified barcode data and an error flag set to "1" representing an error in the new registration data. Thus, the registration data added in this case has a structure as shown in the lower right side of FIG.

By being updated by the processor 31 in this way, the registration database DB32 represents a list of purchased products that have been registered in the virtual POS server 2, and additionally records barcode readings resulting in errors.
Note that the processor 31 stores the barcode data sent with the registration request in the main memory 32 or the auxiliary storage unit 33, and in the sixth case, stores the stored barcode data as the registration data. may be included in In this case, the processor 21 in the virtual POS server 2 does not have to include barcode data in the result data. Also, the processor 31 may extract a product code from the stored bar code data, and process the first to fifth cases based on this product code. Also, the product name and price may be obtained from the store server 1 or the like by the processor 31 based on the product code.

As ACT 212, the processor 31 instructs the user terminal 300 to display the list screen. For example, the processor 31 transmits instruction data including identification data for identifying the list screen display instruction to the user terminal 300 via the in-store communication network 7 and the access point 6 . The processor 31 includes, in the instruction data, the product code, product name, price, and quantity included in the data record DR2 associated with the transaction to be processed in the registration database DB32. Also, if the registration this time is an error, the processor 31 includes error data representing that fact in the instruction data. The processor 31 then returns to the standby state of ACT205 to ACT208 in FIG.

Various instructions from the mobile controller 3 to the user terminal 300, which will be described later, are similar to those described above. It is realized by sending from the mobile controller 3 to the user terminal 300 via.

When the result data in any of the first to third and sixth cases described above is received by the wireless communication unit 306 at the user terminal 300, the processor 301 determines YES in ACT121 in FIG. do. Also, when the result data in the above-described fourth case or fifth case is received by wireless communication unit 306, processor 301 determines YES in ACT 128 in FIG. In both cases, the processor 301 returns to ACT 112 in FIG. 10 and causes the touch panel 304 to display the list screen SC1 again. At this time, the processor 301 uses the list screen SC1 as a screen showing the product name, price, and quantity of the purchased product included in the instruction data. Further, if the instruction data contains error data, the processor 301 adds to the list screen SC1 to indicate that the registration was not performed correctly.

FIG. 22 is a diagram showing an example of the list screen SC1 in a state where purchased products have already been registered.
The list screen SC1 shown in FIG. 22 includes one product whose product name is "AAA" and costs 120 yen, two products whose product name is "BBB" and costs 98 yen, and This is an example in which one product whose product name is "CCC" and whose price is 1,024 yen has already been registered as a purchased product. In the list screen SC1 shown in FIG. 22, the display area AR12 displays the product name, price and quantity of these registered products. The display area AR11 displays "4" as the total number and "1,340" as the total amount. The area enclosed by the dashed line to the left of the product name represents an area for displaying icons.
The dashed line representing the area is not actually displayed on the list screen SC1.

If the customer wishes to cancel all of the purchased products that have already been registered and stop shopping, the customer designates cancellation by a predetermined operation such as touching the button BU11 on the list screen SC1. In response, processor 301 determines YES in ACT 115 in FIG. 10, and proceeds to ACT 129 in FIG.
As ACT 129, the processor 301 causes the touch panel 304 to display a cancel screen. The cancellation screen is a screen for notifying the customer that all of the purchased products that have already been registered will be cancelled. The cancel screen includes an execute button for specifying cancel execution, and a return button for specifying to return to the state before specifying the change of the number without changing the number.

As ACT 130, the processor 301 confirms whether or not execution of cancellation is designated. If the processor 301 cannot confirm the corresponding designation, the processor 301 determines NO and proceeds to ACT131.
As ACT 131, the processor 301 checks whether a return is specified. If the processor 301 cannot confirm the corresponding designation, the processor 301 determines NO and returns to ACT130.
Thus, processor 301, for ACT 130 and ACT 131, waits for an undo execution or return to be specified.

If the customer wants to continue shopping, the customer designates a return by a predetermined operation such as touching a return button on the cancel screen. In response, the processor 301 determines YES in ACT 131, returns to ACT 112 in FIG. 10, and causes the touch panel 304 to display the list screen SC1 again. In this case, since the registration status of the purchased product is not changed, the processor 301 causes the touch panel 304 to display again the list screen SC1 in the same status that was displayed before the cancellation screen was displayed.

If the customer wants to cancel the purchase, the customer designates cancellation execution by a predetermined operation such as touching an execution button on the cancellation screen. In response, processor 301 determines YES in ACT 130 and proceeds to ACT 132 .
As ACT 132, the processor 301 requests the mobile controller 3 to cancel.

If the user terminal 300 requests cancellation as described above, the processor 31 of the mobile controller 3 determines YES in ACT 206 in FIG. 15, and proceeds to ACT 213 in FIG.
As ACT 213, the processor 31 forwards the request for cancellation to the virtual POS server 2 along with notification of the transaction code of the transaction being processed. At this time, the processor 31 may transfer the request data sent from the user terminal 300 to the virtual POS server 2 as it is, or may send the request data converted by some process to the virtual POS server 2 .

If the processor 21 in the virtual POS server 2 is in the waiting state of ACT302 to ACT305 in FIG. and proceed.
As ACT 309, the processor 21 updates the transaction database DB21 according to the request in the transferred request data. For example, the processor 21 regards the request by the request data sent from the mobile controller 3 as a cancellation instruction input by the input device provided in the existing POS terminal, and performs the same processing as the existing POS terminal. updates the transaction database DB21 so as to exclude all the products registered in association with the notified transaction code from the purchased products.

As ACT 310 , the processor 21 transmits result data representing the result of the above processing to the mobile controller 3 . The processor 21 includes the product codes of all the products excluded from the purchased products in the result data. After the processor 21 has finished transmitting the result data, it returns to the standby state of ACT302 to ACT305.

As described above, the processor 21 determines the details of the transaction according to the operation received at the target terminal. As a result of the processor 21 executing information processing based on the virtual POS application AP21, the computer having the processor 21 as its central part functions as decision means.

After transferring the request in ACT213, the processor 31 in the mobile controller 3 proceeds to ACT214.
As ACT 214, the processor 31 acquires result data transmitted from the virtual POS server as described above. The processor 31 saves the acquired result data in the main memory 32 or the auxiliary storage unit 33 .

As ACT 215, the processor 31 updates the registration database DB32 based on the above result data. That is, the processor 31 changes the cancellation flag from "0" to "1" for all registration data included in the data record DR2 associated with the transaction to be processed.
As ACT 216, the processor 31 notifies the user terminal 300 of the cancellation. The processor 31 then returns to the standby state of ACT205 to ACT208 in FIG.

Now, the processor 301 in the user terminal 300 proceeds to ACT133 after requesting cancellation in ACT132 in FIG.
As ACT 133 , the processor 301 waits for notification of cancellation from the mobile controller 3 . Then, the processor 301 determines YES when the cancellation is notified as described above, and returns to ACT101 in FIG.

When the customer has finished registering all of the products he or she wishes to purchase as purchased products, the customer proceeds to settlement. At this time, the customer designates the start of accounting by a predetermined operation such as touching the button BU13 on the list screen SC1. In response, processor 301 determines YES in ACT 116 in FIG. 10 and proceeds to ACT 134 .
As ACT 134, the processor 301 requests the mobile controller 3 for accounting. The request data transmitted by the processor 301 includes the terminal code. Also, if the electronic receipt ID is stored in the auxiliary storage unit 303, the processor 301 includes the electronic receipt ID in the request data.
In ACT 135, the processor 301 waits for an instruction to display the checkout screen.

If the user terminal 300 requests payment as described above, the processor 31 of the mobile controller 3 determines YES in ACT 207 in FIG. 15, and proceeds to ACT 217 in FIG.
In ACT 217, the processor 31 confirms whether or not the user terminal 300 has notified the user terminal 300 of the electronic receipt ID. Then, if the request data includes the electronic receipt ID, the processor 31 determines YES, and proceeds to ACT218.

As ACT 218 , the processor 31 updates the transaction management database DB 31 to record the electronic receipt ID notified from the user terminal 300 . For example, the processor 31 searches the transaction management database DB31 for the data record DR1 in which the terminal code included in the request data is set in the field F11. The processor 31 then sets the electronic receipt ID included in the request data in the field F14 of the relevant data record DR1. If the electronic receipt ID is already set in the field F14 of the data record DR1, the processor 31 overwrites it with the electronic receipt ID included in the request data.

When processor 31 finishes updating transaction management database DB31, processor 31 proceeds to ACT219. If the request data does not include an electronic receipt ID, the processor 31 determines NO in ACT 217 , skips ACT 218 , and proceeds to ACT 219 .
In ACT 219, the processor 31 instructs the user terminal 300 to display a checkout screen.

The processor 301 of the user terminal 300 determines YES in ACT 135 in FIG. 10 when the display of the accounting screen is instructed as described above, and proceeds to ACT 136 in FIG.
As ACT 136, the processor 301 causes the touch panel 304 to display a checkout screen. The checkout screen is a screen for the customer to select which of the user terminal 300 and the checkout machine 5 is to be used for the payment operation.

FIG. 23 is a diagram showing an example of the checkout screen SC3.
Accounting screen SC3 includes display area AR31, message ME31, and buttons BU31 and BU32. The display area AR31 displays the total number of purchased products and the total price of the purchased products. The message ME31 is a character message prompting the customer to specify which of the user terminal 300 and the accounting machine 5 is to be used for the payment operation. The button BU31 is a soft key for the customer to designate the user terminal 300 . The button BU32 is a soft key for the customer to specify the checkout machine 5 .

As ACT 137, the processor 301 confirms whether or not the user terminal 300 has been specified. If the processor 301 cannot confirm the corresponding designation, the processor 301 determines NO and proceeds to ACT138.
As ACT 138, the processor 301 confirms whether or not the accounting machine 5 has been specified. If the processor 301 cannot confirm the designation, the processor 301 determines NO and returns to ACT137.
Thus, processor 301 waits for ACT 137 and ACT 138 to specify user terminal 300 or accounting machine 5 .

When the customer wants to use the user terminal 300 to make a payment, the customer designates the user terminal 300 by a predetermined operation such as touching the button BU31. In response, the processor 301 determines YES in ACT137 and proceeds to ACT139.
As ACT 139, the processor 301 requests the mobile controller 3 to make a payment. Note that the processor 301 may include payment information such as a credit number or a user code for an online payment service required for payment in the request data for requesting payment.

The processor 31 of the mobile controller 3 instructs the display of the checkout screen in ACT219 in FIG. 16, and then proceeds to ACT220.
As ACT 220, the processor 31 confirms whether payment has been requested. If the request cannot be confirmed, the processor 31 determines NO and proceeds to ACT221.
In ACT 221, the processor 31 confirms whether or not payment completion has been notified. If the notification cannot be confirmed, the processor 31 determines NO and returns to ACT220.
Thus, the processor 31 waits for a payment request or a payment completion notice as ACT220 and ACT221. Then, the processor 31 determines YES in ACT220 if payment is requested from the user terminal 300 as described above, and proceeds to ACT222.

As ACT 222, the processor 31 transfers a payment request to the virtual POS server 2 along with notification of the transaction code of the transaction to be processed. At this time, the processor 31 may transfer the request data sent from the user terminal 300 to the virtual POS server 2 as it is, or may send the request data converted by some process to the virtual POS server 2 . However, if the processor 31 has already acquired an electronic receipt ID for the transaction to be processed, the processor 31 includes the electronic receipt ID in the request data. For example, the processor 31 searches the transaction management database DB31 for the data record DR1 in which the terminal code included in the request data is set in the field F11. Then, if the electronic receipt ID is set in the field F14 of the data record DR1, the processor 31 includes the electronic receipt ID in the request data. Also, if the request data sent from the user terminal 300 includes payment data, the processor 31 includes this payment data in the request data to be sent to the virtual POS server 2 as it is.

If the electronic receipt ID set in the field F14 of the data record DR1 has been sent from the user terminal 300, the processor 31 assigns the electronic receipt ID to the virtual POS server 2 as the second information processing device. to , using the communication interface 34 .
In ACT 223, the processor 31 waits for notification of settlement completion.

If the processor 21 in the virtual POS server 2 is in the waiting state of ACT302 to ACT305 in FIG. Go to ACT 311 in 19.
As ACT 311, the processor 21 executes settlement processing for settlement of the price according to the request in the transferred request data. For example, the processor 21 regards the request by the request data sent from the mobile controller 3 as the payment instruction input by the input device provided in the existing POS terminal, and performs the same processing as the existing POS terminal. calculates the price for the transaction identified by the notified transaction code. The processor 21 then requests the settlement server 500 to settle the calculated price. The processor 21, for example, refers to the user database included in the database group DB11 to determine the payment method to be applied to payment, and acquires payment information to be used for payment by that payment method. When multiple payment methods or multiple payment information are registered in the user database, one of them is selected according to an instruction from the operator of the user terminal 300 or according to a predetermined condition. . For example, if payment information is included in the request data, the processor 21 may determine a payment method to be used for payment based on the payment information, and use the payment information as payment information to be used for payment.

In ACT 312, the processor 21 confirms whether or not the electronic receipt ID has been notified. For example, if the request data requesting payment includes an electronic receipt ID, the processor 21 determines YES and proceeds to ACT 313 .
As ACT 313, the processor 21 registers the transaction data related to the transaction for which the payment has been completed as described above in the electronic receipt server 600 so that the user identified by the electronic receipt ID included in the request data can view it. process. Note that this process may be the same as the process performed by an existing electronic receipt service, for example. What kind of data the processor 21 includes in the transaction data is, for example, according to the regulation of the electronic receipt service.

When the customer wants to use the checkout machine 5 to make a payment, the customer designates the checkout machine 5 by a predetermined operation such as touching the button BU32 on the checkout screen SC3. In response to this, the processor 301 of the user terminal 300 determines YES in ACT138 in FIG. 12 and proceeds to ACT140.
As ACT 140, the processor 301 causes the touch panel 304 to display the accounting barcode screen. The accounting barcode screen is a screen showing accounting barcodes representing data necessary for the accounting machine 5 to acquire data on the content of transactions from the virtual POS server 2 . Although illustration of detailed processing is omitted, the processor 301 acquires the accounting barcode from the virtual POS server 2 via the mobile controller 3 and displays the accounting barcode on the accounting barcode screen.

The customer causes the scanner of the accounting machine 5 not used by other customers to read the accounting bar code. In response to this, the checkout machine 5 requests the virtual POS server 2 to transfer payment data according to the data indicated by the checkout bar code. For example, the checkout machine 5 transmits request data containing the transaction code included in the data represented by the checkout bar code to the virtual POS server 2 .

If the processor 21 in the virtual POS server 2 receives the request data for the transfer request including the transaction code of the transaction to be processed in the waiting state of ACT302 to ACT305 shown in FIG. ACT 305 determines YES, and proceeds to ACT 314 in FIG.
As ACT 314, the processor 21 represents the details of the transaction to be processed and transmits payment data necessary for payment at the accounting machine 5 to the accounting machine 5 that requested the transfer. The payment data may be data similar to the payment data transferred from the registration machine to the accounting machine in an existing semi-self-type transaction processing system, for example.
In ACT 315, the processor 21 waits for completion of payment at the accounting machine 5 that has sent the payment data as described above.

After receiving the settlement data transmitted from the virtual POS server 2, the accounting machine 5 settles the transaction fee while being operated by the operator. The accounting machine 5 also issues various printed materials such as receipts and coupons as necessary. When the payment is completed, the accounting machine 5 notifies the virtual POS server 2 to that effect. In response to this, the processor 21 of the virtual POS server 2 determines YES in ACT 315 and proceeds to ACT 316 .
Note that the processor 21 proceeds to ACT316 even after completing the electronic receipt registration in ACT313. If the request data requesting payment does not include an electronic receipt ID, the processor 21 determines NO in ACT 312 , skips ACT 313 , and proceeds to ACT 316 .
As ACT 316, the processor 21 updates the transaction database DB21 to finish managing the transaction to be processed. For example, the processor 21 deletes the data record containing the transaction code of the transaction to be processed from the transaction database DB21.
In ACT317, the processor 21 notifies the mobile controller 3 of the completion of payment. The processor 21 then terminates transaction processing.

When the processor 31 of the mobile controller 3 is notified of the settlement completion from the virtual POS server 2 as described above, it determines YES in ACT221 or ACT223 in FIG. 16, and proceeds to ACT224 in either case. Incidentally, when the processor 21 proceeds from ACT 312 or ACT 313 in FIG. 18 to ACT 317, the processor 31 determines YES in ACT 221 in FIG. In this case, YES is determined in ACT223 in FIG.
In ACT224, the processor 31 notifies the user terminal 300 of the settlement completion.

After the processor 301 of the user terminal 300 requests payment in ACT139 or after displaying the accounting bar code screen in ACT140, the process proceeds to ACT141.
In ACT 141, the processor 301 waits for notification of settlement completion. Then, the processor 301 determines YES when the settlement completion is notified from the mobile controller 3 as described above, and proceeds to ACT142.
As ACT 142, the processor 301 causes the touch panel 304 to display a completion screen. The completion screen is a screen for notifying the customer that the payment has been completed.

After confirming the completion screen, the customer declares that he/she has confirmed by a predetermined operation such as touching a button displayed on the completion screen. In response, processor 301 advances to ACT 143 . Note that the processor 301 may proceed to ACT 143 when the elapsed time with the completion screen displayed reaches a predetermined time.

As ACT 143, the processor 301 causes the touch panel 304 to display a scan screen for checkout. The scan screen for checkout is a screen for reading the two-dimensional code TC2 for checkout. The processor 301, for example, activates the camera 305, and displays a character message prompting the customer to read the two-dimensional code TC2 and an indication of the position where the two-dimensional code TC2 should be held in the image obtained by the camera 305. Lines are superimposed to generate a scan screen.

When the scan screen for checkout is displayed on the touch panel 304, the customer points the camera 305 at the two-dimensional code TC2 posted near the exit of the store so that the two-dimensional code TC2 is reflected in the scan screen.
As ACT 144, the processor 301 waits for the two-dimensional code to be read. At this time, the processor 301 repeatedly analyzes the image obtained by the camera 305 and attempts to read the two-dimensional code. This reading of the two-dimensional code may be performed as processing based on the smartphone POS application AP301, or may be performed as processing based on another application program for reading the two-dimensional code. Then, if the two-dimensional code can be read, the processor 301 determines YES, and proceeds to ACT145.

As ACT 145, the processor 301 confirms whether or not the data represented by the read two-dimensional code is checkout data. If it is not checkout data, the processor 301 determines NO and returns to ACT144. At this time, the processor 301 may cause the touch panel 304 to display a screen notifying the customer that an incorrect two-dimensional code has been read.

If the processor 301 can confirm that the data represented by the read two-dimensional code is checkout data, it determines YES in ACT 145 and proceeds to ACT 146 .
As ACT 146, the processor 301 requests the mobile controller 3 to check out.

The processor 31 in the mobile controller 3 proceeds to ACT225 after notifying the settlement completion in ACT224 in FIG.
In ACT 225 processor 31 waits for a checkout to be requested.
If the user terminal 300 requests checkout as described above, the processor 31 determines YES and proceeds to ACT226.

As ACT 226, the processor 31 executes checkout processing. The checkout process is a process such as clearing data stored in the main memory 32 and the auxiliary storage unit 33 for management of transactions that have been processed. Note that the virtual POS server 2 may terminate the transaction-related processing upon completion of payment, or may terminate the transaction-related processing upon instruction from the mobile controller 3 . In the latter case, the processor 31 gives the above instruction to the virtual POS server 2 in the checkout process. In addition, a history database representing a history of user operations, including erroneous barcode scans, may be managed by the store server 1, the virtual POS server 2, the mobile controller 3, or another server (not shown). In this case, the processor 31 performs processing for updating the history database so as to reflect the history of operations related to the current transaction in the checkout processing.
In ACT 227, the processor 31 notifies the user terminal 300 of completion of checkout. The processor 31 then terminates the mediation process.

The processor 301 of the user terminal 300 proceeds to ACT147 after requesting checkout in ACT146 in FIG.
In ACT 147, the processor 301 waits for a checkout completion notification. Then, the processor 301 determines YES when the checkout completion is notified from the mobile controller 3 as described above, and proceeds to ACT148.
As ACT 148, the processor 301 clears various data temporarily used for the current shopping, such as the check-in data saved in ACT 107 in FIG. Processor 301 then returns to ACT 101 in FIG.

By the way, the processor 401a in the cart terminal 400 advances to ACT164 after requesting check-in in ACT163 in FIG.
In ACT 164, the processor 401a confirms whether or not the completion of check-in has been notified. If the processor 401a cannot confirm the corresponding notification, it determines NO and proceeds to ACT165.
As ACT 165, the processor 401a confirms whether or not a check-in error has been notified. If the notification cannot be confirmed, the processor 401a determines NO and returns to ACT164.
Thus, processor 401a, in ACT 164 and ACT 165, waits to be notified of check-in completion or an error. The processor 401a determines YES in ACT165 if notification data for error notification in ACT188 in FIG. 14 or ACT203 in FIG.

As ACT 166, the processor 401a causes the touch panel 401e to display an error screen. The error screen is a screen that is defined to inform the customer that check-in is not possible. Note that the processor 401a, for example, in response to the error notification in ACT 188 in FIG. 14, notifies that check-in is not possible due to the store being crowded, and also displays an error screen prompting the user to try to check-in after a while. display. The processor 401a returns to the standby state of ACT 162 when an instruction to cancel the display of the error screen is given, for example, by operating a GUI element displayed in the error screen.

On the other hand, the processor 401a executes ACT 164 when the wireless communication unit 401d receives the aforementioned notification data for the check-in completion notification transmitted from the mobile controller 3 by the processor 31 executing ACT 204 in FIG. is determined to be YES. Although not shown in FIG. 15, after this, the processor 401a requests the mobile controller 3 to register, change the quantity, cancel, or make a payment according to the operation of the customer, in the same way as the processor 301 described above, or A barcode screen is displayed on the touch panel 401e. However, the customer's operation received by processor 401 a may be different from that of processor 301 . For example, the scanner 402 reads a bar code displayed on a product to be registered as a purchased product.
In the mobile controller 3 and the virtual POS server 2, even in the intermediary processing and transaction processing with the cart terminal 400 as the target terminal, the request or accounting machine 5 Execute processing according to the transfer request from

As described above, the processor 21 executes transaction processing as information processing for processing transactions in accordance with instructions from different target terminals.

The processor 401a at the cart terminal 400 requests payment as in ACT139 in FIG. 12, or after displaying the accounting bar code screen as in ACT140, proceeds to ACT171 in FIG.
In ACT 171, the processor 401a waits for notification of settlement completion. Then, the processor 401a makes a determination of YES when the aforementioned settlement completion notification is received from ACT 224 in FIG.
As ACT 172, the processor 401a causes the touch panel 401e to display an end screen. The end screen is, for example, a screen that informs the customer that the transaction has ended.
As ACT 173, the processor 401a clears various data temporarily used for the current shopping. The processor 401a then returns to the standby state of ACT161.

Even though the customer has completed check-in, it is not possible for the customer to stop shopping and leave the store without completing the payment as described above and without specifying the cancellation. Prohibited items related to the use of POS services. However, there is a risk that the customer will act as such.
When the customer acts as described above, the processor 31 of the mobile controller 3 continues the standby state of ACT205 to ACT208. If the elapsed time from ACT204, ACT212 or ACT216 in FIG. 16 to the standby state of ACT205 to ACT208 reaches a predetermined time limit, the processor 31 determines YES in ACT208, Proceed to ACT228. At this time, the processor 31 detects a state in which no operation is received for a predetermined period of time as a non-operation state. As a result of the processor 31 executing information processing based on the transaction management application AP31, the computer having the processor 31 as a central part functions as detection means.
As an example, the time limit is determined for each store by an administrator of the store system 100 or the like. The processor 31 inputs the time limit according to the operation of the administrator or the like, and stores the time limit in the main memory 32 or the auxiliary storage unit 33 . If the time limit has already been stored in the main memory 32 or the auxiliary storage unit 33, the processor 31 overwrites it with the newly input time limit. However, the time limit may be determined by the creator of the transaction management application AP31, for example, and may be fixedly applied in common to each store.

As ACT 228, the processor 31 instructs the virtual POS server 2 to end transaction processing for the target terminal. The processor 31 , for example, sends instruction data for the end instruction to the virtual POS server 2 from the communication interface 34 to the in-store communication network 7 . The processor 31 includes identification data in the instruction data for identifying the instruction to end. The processor 31 finds the data record DR1 in which the terminal code of the target terminal is set in the field F11 from the transaction management database DB31, and includes the transaction code set in the field F13 of the corresponding data record DR1 in the instruction data.

When the instruction data is transmitted to the virtual POS server 2 via the in-store communication network 7 , it is received by the communication interface 24 . At this time, the processor 21 should be in the standby state of ACT302 to ACT306 in FIG. 18 in the transaction processing for the transaction identified by the transaction code included in the instruction data. Therefore, the processor 21 determines YES in ACT306 regarding the transaction processing, and proceeds to ACT318 in FIG.
As ACT 318, the processor 21 updates the transaction database DB21 to end management of the transaction to be processed. For example, the processor 21 deletes the data record containing the transaction code of the transaction to be processed from the transaction database DB21.
As ACT 319, the processor 21 notifies the mobile controller 3 of the end. The processor 21 includes the transaction code of the transaction to be processed in the notification data for this end notification. The processor 21 then completes transaction processing. In other words, the processor 21 forcibly terminates the corresponding transaction processing even though the settlement is not completed.
In this manner, the transaction processing is terminated in accordance with instructions from the processor 31 of the mobile controller 3. FIG. Thus, the processor 31 executes information processing based on the transaction management application AP31, so that the computer having the processor 31 as a central part functions as control means.

The processor 31 in the mobile controller 3 proceeds to ACT229 after instructing the end in ACT228 in FIG.
As ACT 229, the processor 31 waits for a termination notification. Then, the processor 31 determines YES when the end is notified from the virtual POS server 2 as described above, and proceeds to ACT230.

As ACT 230, processor 31 instructs a predetermined notification destination to execute the notification operation. The processor 31 then terminates the mediation process.
The notification operation is an operation for notifying a predetermined notification destination that the transaction processing has been forcibly terminated.
For example, when the transaction process is forcibly terminated as described above, it is assumed that the customer leaves the store while the cart terminal 400, which is the target terminal for the transaction process, is left in the store. In other words, the shopping cart C1 containing products is left in the store without being used by any customer. The cart terminal 400 attached to the shopping cart C1 enters a state in which a new transaction can be started due to the forcible termination of transaction processing. Can not. Therefore, the processor 31 notifies the store clerk of the forced termination by causing the store clerk's terminal to perform a notification operation. In response to this notification, the store clerk finds the notified shopping cart C1 in the store, removes the commodities from the shopping cart C1, and returns the shopping cart C1 to the storage area, thereby making the shopping cart C1 available for use. .

In addition, for example, the customer using the target terminal of the forcibly terminated transaction process may be forced to terminate the transaction process even though they are shopping due to circumstances such as taking a break in the rest space in the store. A case is also considered. Therefore, the processor 31 notifies the customer of the forcible termination by causing the target terminal of the forcibly terminated transaction processing to perform a notification operation. The customer can know from this report that the shopping needs to be restarted from the beginning. If there is concern that such a situation may occur, the processor 31 detects that the duration of the standby state of ACT205 to ACT208 in FIG. Accordingly, the target terminal may be instructed to perform an alarm operation to inform the customer that the operation will be forcibly terminated if no operation is performed. Then, in response to this instruction, the processor 301 or processor 401a in the target terminal may execute a predetermined warning operation as described above.
Note that the processor 31 may instruct each of a plurality of terminals to execute the notification operation.
Thus, the processor 31 instructs a predetermined terminal to execute the notification operation, thereby notifying a predetermined notification destination. As a result of the processor 31 executing information processing based on the transaction management application AP31, the computer having the processor 31 as its central part functions as reporting means.

As described above, the transaction processing system of the present embodiment forcibly terminates the transaction processing when the target terminal becomes inactive while the processor 21 in the virtual POS server 2 is processing the transaction. Therefore, it becomes possible to release the resources used for the transaction processing and use them for new transactions. This can reduce the possibility of a situation where the use of a new terminal device cannot be started.

This embodiment can be modified in various ways as follows.
Requests from the user terminal 300 and the cart terminal 400 may be directly received by the virtual POS server 2 without the mobile controller 3 . The management process may be executed by the processor 21 in the virtual POS server 2 . Also, in this case, the processor 21 executes a process corresponding to ACT208 in FIG. 15 instead of ACT306 in FIG. 18, for example. Also, the processor 21 executes a process corresponding to ACT230 in FIG. 15 instead of ACT319 in FIG. 19, for example.

The detection of the no-operation state may be executed by the processors 301 and 401a in the user terminal 300 and the cart terminal 400, respectively. For the processor 301, for example, it is sufficient to confirm whether or not the duration of the standby state of ACT113 to ACT116 in FIG. 10 has exceeded the time limit. Also, the processor 401a can check whether the duration of the standby state corresponding to ACT113 to ACT116 in FIG. 10 in the cart UI processing has exceeded the time limit. If the user terminal 300 and the cart terminal 400 detect the non-operating state, the processors 301 and 401a may also instruct the termination of transaction processing in response to the detection of the non-operating state. .

Detection of the no-operation state can be arbitrarily changed, for example, by counting the number of times the ACT 208 is repeatedly executed and determining the no-operation state when the number of times exceeds a predetermined limit.

A plurality of virtual POS servers 2 may be provided, and the plurality of virtual POS servers 2 may share and execute a plurality of transaction processes. Moreover, you may share and process one transaction processing by several information processing apparatuses. For example, the processing for registering purchased products and the processing for settlement may be performed by separate information processing devices.

Transactions to be processed by the transaction processing system are not limited to sales of products displayed in stores, and may be other forms of transactions such as cooking and providing food and drink.

The terminal device lent to the customer by the store may be carried by the user without being attached to the shopping cart C1, or such a terminal device and the cart terminal 400 may be mixed.

Either one of the user terminal 300 and the cart terminal 400 may be used.

Each function realized by the processors 11, 21, 31, 301, and 401a by information processing can be partially or entirely realized by hardware such as a logic circuit that executes information processing not based on a program. be. Further, each of the functions described above can be implemented by combining hardware such as the logic circuit described above with software control.

While several embodiments of the invention have been described, these embodiments have been presented by way of example and are not intended to limit the scope of the invention. These novel embodiments can be implemented in various other forms, and various omissions, replacements, and modifications can be made without departing from the scope of the invention. These embodiments and modifications thereof are included in the scope and gist of the invention, and are included in the scope of the invention described in the claims and equivalents thereof.
The following is a supplementary description of the inventions originally claimed in this application.
[Appendix 1] including a terminal device and at least one information processing device,
an operating means provided in the terminal device for receiving an operation by an operator;
a determining means that is provided in one of the information processing devices and performs processing for determining the content of a transaction according to an operation received by the operating means;
detection means provided in one of the terminal device and the information processing device for detecting a no-operation state in which the operation is not received by the operation means;
provided in one of the terminal device or the information processing device, and between the time the determination means starts the processing for determining the content of one transaction and the completion of the determination of the content of the one transaction, a control means for controlling the determination means to end the processing related to the one transaction in response to the detection of the no-operation state by the detection means;
A transaction processing system comprising:
[Supplementary Note 2] The detection means detects a state in which the operation is not received by the operation means for a predetermined time as the no-operation state.
The transaction processing system of Supplementary Note 1.
[Supplementary Note 3] Reporting means provided in one of the information processing devices for reporting to a predetermined reporting destination that the determining means has terminated without completing the processing;
3. The transaction processing system of Clause 1 or Clause 2, further comprising:
[Appendix 4] The terminal device is lent to a customer from the store, and the customer acts as the operator,
The reporting means has an employee of the store as the reporting destination,
The transaction processing system of Supplementary Note 3.
[Appendix 5] Transaction processing together with a terminal device comprising an operation means for receiving an operation by an operator and a registration processing device comprising a determination means for performing processing for determining the content of a transaction according to the operation received by the operation means configure the system,
a detection means for detecting a no-operation state in which the operation is not received by the operation means;
In response to the detection of the non-operating state by the detection means during the period from when the determination means starts the processing for determining the content of one transaction until the determination of the content of the one transaction is completed a control means for controlling the decision means to end the processing relating to the one transaction;
A control device comprising:
[Appendix 6] Transaction processing together with a terminal device comprising operation means for receiving an operation by an operator, and a registration processing device comprising a determination means for performing processing for determining the content of a transaction according to the operation received by the operation means The computer provided in the control device that constitutes the system,
a detection means for detecting a no-operation state in which the operation is not received by the operation means;
In response to the detection of the non-operating state by the detection means during the period from when the determination means starts the processing for determining the content of one transaction until the determination of the content of the one transaction is completed a control means for controlling the decision means to end the processing relating to the one transaction;
Information processing program to function as

REFERENCE SIGNS LIST 1 store server 2 virtual POS server 3 mobile controller 4 communication server 5 accounting machine 6 access point 7 in-store communication network 11, 21, 31, 301, 401a processor 12 , 22, 32, 302, 401b... main memory, 13, 23, 33, 303, 401c... auxiliary storage unit, 14, 24, 34... communication interface, 15, 25, 35, 308, 401h... transmission path, 304, 401e... touch panel, 305, 404... camera, 306, 401d... wireless communication unit, 307... mobile communication unit, 401f... sound unit, 401g... interface unit, 402... scanner, 403... reader, 100 (100A, 100B)... store System, 200 -- Relay server, 300 -- User terminal, 400 -- Cart terminal, 500 -- Settlement server, 600 -- Electronic receipt server, 700 -- Communication network.

Claims (5)

including a terminal device and at least one information processing device,
an operation means provided in the terminal device for repeatedly confirming occurrence of an operation by an operator and receiving the corresponding operation when the operation occurs ;
a determining means that is provided in one of the information processing devices and performs processing for determining the content of a transaction according to an operation received by the operating means;
A non-operating state provided in one of the terminal device and the information processing device, wherein the number of repetitions of confirmation by the operating means exceeds a predetermined number of times while no operation is received by the operating means. a detection means for detecting as
Provided in one of the terminal device or the information processing device, between the time the determination means starts the process for determining the content of one transaction and the completion of the determination of the content of the one transaction, Control means for controlling the decision means to end the processing related to the one transaction in response to the detection of the non-operating state by the detection means;
A transaction processing system comprising: Reporting means provided in one of the information processing devices for reporting to a predetermined reporting destination that the determining means has terminated without completing the processing ;
The transaction processing system of Claim 1 , further comprising: The terminal device is lent to a customer from the store and the customer acts as the operator,
The reporting means has an employee of the store as the reporting destination,
The transaction processing system according to claim 2 . Repeatedly confirming the occurrence of an operation by an operator, a terminal device having an operation means for receiving the corresponding operation when the operation occurs, and processing for determining the contents of the transaction according to the operation received by the operation means configuring a transaction processing system with a registration processor comprising a determining means;
detection means for detecting, as a non-operating state , that the number of repetitions of confirmation by the operating means has exceeded a predetermined number without being operated by the operating means;
In response to the detection of the non-operating state by the detection means during the period from when the determination means starts processing for determining the content of one transaction until the determination of the content of the one transaction is completed a control means for controlling the decision means to end the processing related to the one transaction;
A control device comprising: Repeatedly confirming the occurrence of an operation by an operator, a terminal device having an operation means for receiving the corresponding operation when the operation occurs, and processing for determining the contents of the transaction according to the operation received by the operation means a computer included in a control device that constitutes a transaction processing system together with a registration processing device that includes a determination means;
detection means for detecting, as a no-operation state , that the number of repetitions of confirmation by the operation means has exceeded a predetermined number without being operated by the operation means;
In response to the detection of the non-operating state by the detection means during the period from when the determination means starts processing for determining the content of one transaction until the determination of the content of the one transaction is completed a control means for controlling the decision means to end the processing related to the one transaction;
Information processing program to function as

Images