JP2014149602A - Electronic apparatus, accounting system and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To improve reliability of a POS system using network computing.SOLUTION: An electronic apparatus includes first communication means, second communication means, relaying means and accounting processing means. The first communication means communicates with a server which performs accounting processing for accounting a commercial transaction. The second communication means communicates with a peripheral device used for the accounting processing. The relaying means relays control of the peripheral device when communication with the server by the first communication means is established. The accounting processing means performs the accounting processing by directly controlling the peripheral device, independently from the server, when communication with the server by the first communication means is cut.

Description

  Embodiments described herein relate generally to an electronic device, an accounting system, and a program.

  In recent years, for example, an environment in which a POS (Point Of Sales) system can be constructed quickly and inexpensively by using network computing such as cloud computing is being prepared.

JP-A-7-93667

  In a POS system using network computing, if a server goes down or a communication failure occurs between the server and the client, the POS system cannot be used. If the operation of the POS system stops, the store business will be greatly affected.

  The problem to be solved by the present invention is to improve the reliability of a POS system using network computing.

  An electronic device according to an embodiment includes a first communication unit, a second communication unit, a relay unit, and an accounting processing unit. The first communication means communicates with a server that executes an accounting process for accounting for a commercial transaction. The second communication means communicates with a peripheral device used for the accounting process. The relay unit relays control of the peripheral device by the server when communication with the server by the first communication unit is established. When the communication with the server by the first communication unit is disconnected, the accounting processing unit directly controls the peripheral device without executing the server and executes the accounting process.

The schematic diagram which shows the structure of the POS system in one Embodiment. The block diagram which shows the principal part structure of the POS input / output device in the embodiment. The schematic diagram which shows an example of the data structure of the 2nd registration buffer in the embodiment. The flowchart of the monitoring process in the embodiment. The software hierarchy figure of cloud POS and local POS in the same execution form. The flowchart of the accounting process by the cloud POS in the same embodiment. The flowchart of the accounting process by local POS in the embodiment. The flowchart of the upload process in the embodiment.

An embodiment will be described with reference to the drawings.
In the following embodiment, a POS system (accounting system) that accounts for the price of merchandise sold at a retail store will be exemplified.

FIG. 1 is a schematic diagram showing a configuration of a POS system according to the present embodiment.
The POS system includes a POS input / output box (POS-IO-BOX) 1 arranged in a store and a server 2 included in a cloud of SaaS (Software as a Service) type, for example. The POS input / output box 1 functions as an electronic device according to the present embodiment.

  Further, the POS system includes an access point 3, a hub 4, a terminal device 5, a scanner 6, a fluorescent display tube 7, a printer 8, and a drawer 9 disposed in the store. The access point 3 and the hub 4 are connected so as to be able to communicate with each other via, for example, a communication cable. The hub 4 and the server 2 are connected to be able to communicate with each other via, for example, the Internet. The terminal device 5 and the access point 3 are connected so as to be able to communicate with each other via, for example, radio waves. The scanner 6, the fluorescent display tube 7, the printer 8, the drawer 9 and the POS input / output box 1 are connected to each other via a USB (Universal Serial Bus) cable so that they can communicate with each other.

  The server 2 includes a storage device that stores an AP (application) file 21, a PLU (Price Look Up) master 22, a first registration buffer 23, and a history DB (Data Base) 24. The AP file 21 realizes an application A related to an accounting process for accounting for a product sold at a store. The PLU master 22 is a master in which product data (product name, unit price, etc.) of a product is associated with each product code assigned to each product sold in a store. The first registration buffer 23 is a buffer for temporarily storing a product code and product data of a product purchased by a customer in one transaction. The history DB 24 is a database for storing history data of transactions for which accounting has been completed. The history data includes a transaction number assigned for each transaction, a date and time when the transaction was performed, a product code and product data of a product sold in the transaction.

  The access point 3 and the hub 4 relay communication between the POS input / output box 1 and the terminal device 5 and the server 2. The access point 3 may relay communication between the POS input / output box 1 and the terminal device 5.

  The terminal device 5 is a tablet PC including, for example, a display and a touch panel that detects an operation on the display surface of the display. The terminal device 5 displays a screen related to the accounting process (hereinafter referred to as an accounting screen).

  The scanner 6 optically scans a code symbol such as a barcode attached to a product, and decodes data obtained by the scanning into a product code represented by the code symbol.

  The fluorescent display tube 7 is a simple display that displays characters, numbers, symbols, and the like in one line.

  The printer 8 prints a receipt including transaction details (transaction number, transaction date and time, product data, etc.) on a sheet.

  The drawer 9 includes a storage unit for storing banknotes and coins, a housing for retractably storing the storage unit, and a lock mechanism for locking the opening and closing of the storage unit with respect to the housing.

  FIG. 2 is a block diagram showing a main configuration of the POS input / output device 1. The POS input / output device 1 includes a CPU (Central Processing Unit) 10, memories 11, 12, 13, 14, a communication device 15, a device connector 16, and the like.

  The memory 11 is, for example, a DRAM (Dynamic Random Access Memory), and generates a program execution area and the like.

  The memory 12 is, for example, a boot ROM (Read Only Memory), and stores a boot program 120 that implements a basic input output system (BIOS) for booting the POS input / output device 1.

  The memory 13 is, for example, a NAND flash memory, and stores an AP (application) file 130, a driver file 131, and the like. The AP file 130 includes an application program for realizing the application B related to the accounting process. The driver file 131 is obtained by a device driver A and an application B that control peripheral devices (such as the scanner 6, the fluorescent display tube 7, the printer 8, and the drawer 9) of the POS input / output box 1 according to data transmitted from the server 2. It includes a driver program for realizing a device driver B that controls the peripheral devices and a monitoring driver M that monitors the communication state between the server 2 and the terminal device 5.

  The memory 14 is, for example, an SRAM (Static Random Access Memory), and stores the second registration buffer 140, the PLU master 22, and the like. The PLU master 22 in the memory 14 is downloaded from the server 2 to the POS input / output box 1 at the start of a day of work. FIG. 3 is a schematic diagram illustrating an example of the data structure of the second registration buffer 140. Similar to the first registration buffer 23, the second registration buffer 140 is a buffer for temporarily storing a product code and product data of a product purchased by a customer in one transaction. Specifically, the second registration buffer 140 is configured by a record including a product code of a product purchased by a customer, product data of the product, and a flag. The flag is identification information indicating whether or not the product code and product data relating to the record are written in the first registration buffer 23, and is “0” when written, and when not written. “1”.

  The communication device 15 functions as a first communication unit according to the present embodiment, and communicates with the access point 3 wirelessly. The communication device 15 may communicate with the terminal device 5.

  The device connector 16 functions as a second communication unit according to the present embodiment, and communicates with the peripheral devices (such as the scanner 6, the fluorescent display tube 7, the printer 8, and the drawer 9) via a communication cable. .

  The CPU 10 executes various functions such as an application B, device drivers A and B, and a monitoring driver M by executing a startup program 120, an application program included in the AP file 130, a driver program included in the driver file 131, and the like. Realize.

  In the POS system having such a configuration, the POS input / output box 1, the server 2, and the terminal device 5 are configured such that the POS input / output box 1 and the server 2 are communicatively connected via the access point 3 and the hub 4, and The terminal device 5 operates so as to be connected for communication via the access point 3 and the hub 4.

[Switching between cloud POS / local POS]
The POS system according to the present embodiment has a function of switching between a cloud POS whose accounting process is the server 2 and a local POS whose accounting process is the POS input / output box 1. The monitoring driver M mainly executes processing related to this switching.

  Switching between the cloud POS and the local POS will be described with reference to FIGS. FIG. 4 is a flowchart of the monitoring process executed by the CPU 10 under the control of the monitoring driver M. FIG. 5 is a schematic software hierarchy diagram of the cloud POS and the local POS.

  The monitoring driver M periodically executes the monitoring process shown in the flowchart of FIG. In this process, first, the monitoring driver M determines whether or not communication between the communication device 15 and the server 2 has been established (step S101). If it is determined that communication is established (Yes in step S101), the monitoring driver M activates the device driver A (step S102). If the device driver A has already been activated at the time of execution of step S102, the monitoring driver M does not need to perform any particular processing. If the device driver B and the application B are activated at the time of executing step S102, the monitoring driver M ends the device driver B and the application B.

  After step S102, the monitoring driver M executes an upload process (step S103). Details of the upload process will be described later.

  With step S103, the monitoring driver M ends the process shown in the flowchart.

  If it is determined in step S101 that communication between the communication device 15 and the server 2 has not been established (No in step S101), the monitoring driver M activates the device driver B (step S104). If the device driver B has already been activated at the time of execution of step S104, the monitoring driver M does not need to perform any particular processing. If the device driver A is activated during the execution of step S104, the monitoring driver M ends the device driver A.

  As a case where communication between the communication device 15 and the server 2 is not established, a case where the server 2 is down or a failure occurs in the access point 3 or the hub 4 is assumed.

  After step S104, the monitoring driver M activates the application B (step S105). After step S105, the monitoring driver M tries communication connection between the communication device 15 and the terminal device 5 (step S106). The terminal device 5 basically sets the communication connection destination as the server 2 and sets the communication connection destination as the POS input / output device 1 when communication with the server 2 cannot be established. That is, when communication with the server 2 cannot be executed due to the server 2 being down, the terminal device 5 tries communication connection with the POS input / output device 1. When both the POS input / output device 1 and the terminal device 5 attempt communication connection, communication between the POS input / output device 1 and the terminal device 5 is established if there is no factor that hinders communication.

  After step S106, the monitoring driver M determines whether communication between the communication device 15 and the terminal device 5 has been established (step S107). If it is determined that communication has been established (Yes in step S107), the device driver M notifies the application B that communication with the terminal device 5 is possible (step S108). On the other hand, if it is determined that communication has not been established (Yes in step S107), the device driver M notifies the application B that communication with the terminal device 5 is impossible (step S109).

  Through step S108 or step S109, the monitoring driver M ends the processing shown in the flowchart.

  The software hierarchy shown in FIG. 5 is configured by the operation of the monitoring driver M as described above. That is, when communication between the POS input / output device 1 and the server 2 is established (normal time), the POS system functions as a cloud POS with the application A realized by the CPU 20 of the server 2 as a main body. At this time, the CPU 10 of the POS input / output device 1 implements the device driver A in addition to the monitoring driver M.

  On the other hand, when the communication between the POS input / output device 1 and the server 2 is disconnected (when the server is down), the CPU 10 of the POS input / output device 1 realizes the device driver B and the application B in addition to the monitoring driver M, and the application The POS system with B as the main body functions as a local POS.

[Accounting at Cloud POS]
Next, the flow of accounting processing when the POS system functions as a cloud POS will be described.

  In the cloud POS, the application A repeatedly executes the operation shown in the flowchart of FIG.

  First, the application A transmits image data of the accounting screen in the initial state to the terminal device 5 (step S201). The terminal device 5 displays an accounting screen based on the received image data. This accounting screen has a display area for displaying the product data written in the first registration buffer 23 and the total price of the transaction, a subtotal button for inputting a subtotal instruction, and a numeric keypad for inputting a deposit amount from the customer. , Including a tightening button for inputting a tightening command.

  In a state where the accounting screen is displayed on the terminal device 5, the store clerk scans the barcode attached to the product purchased by the customer with the scanner 6, thereby inputting the product code of the product. The device driver A of the POS input / output box 1 captures the input product code from the scanner 6 and transmits it to the server 2.

  After step S201, the application A determines whether or not the product code input by the scanner 6 has been received (step S202). When it is determined that the product code is received from the POS input / output box 1 (Yes in step S202), the application A acquires product data corresponding to the product code from the PLU master 22 stored in the storage device of the server 2. (Step S203). Furthermore, the application A writes the acquired product data in the record of the first registration buffer 23 (step S204).

  After step S204, the application A transmits the product code received from the POS input / output box 1 and the product data acquired in step S203 to the terminal device 5 and the POS input / output box 1 (step S205). The terminal device 5 displays the received product code and product data on the accounting screen. The device driver A of the POS input / output box 1 displays the received product data on the fluorescent display tube 7. Further, the monitoring driver M of the POS input / output box 1 writes the received product code and product data in the record of the second registration buffer 140. The monitoring driver M sets the flag of this record to “0”.

  After step S205 or when it is determined in step S202 that the product code has not been received from the POS input / output box 1 (No in step S202), the application A determines whether or not a subtotal command has been received ( Step S206). The terminal device 5 transmits a subtotal command to the server 2 when, for example, a store clerk operates a subtotal button on the accounting screen.

  When it is determined that the subtotal command has not been received (No in step S206), the operation of the application A returns to step S202.

  On the other hand, when it is determined that the subtotal command has been received (Yes in step S206), the application A, based on the product data written in each record of the first registration buffer 23, the total price and the total product quantity of the transaction. Are generated and transmitted to the terminal device 5 and the POS input / output box 1 (step S207). The terminal device 5 displays the total price and the total product quantity represented by the received subtotal data on the accounting screen. The device driver A of the POS input / output box 1 causes the fluorescent display tube 7 to display the total price and the total product quantity represented by the received subtotal data. For example, the customer sees the total price displayed on the fluorescent display tube 7 and pays cash.

  After step S207, the application A determines whether or not the data indicating the deposit amount from the customer and the closing command have been received (step S208). The application A repeats this determination until it receives data representing the deposit amount and a closing command (No in step S208). For example, when the closing amount on the accounting screen is operated in a state in which the deposit amount is input by operating the numeric keypad on the accounting screen, the terminal device 5 stores the data indicating the entered deposit amount and the closing command on the server 2 Send.

  When it is determined that the data representing the deposit amount and the closing command have been received (Yes in step S208), the application A calculates the change amount based on the deposit amount and the total price represented by the data, and the calculated change amount Data to be represented is transmitted to the terminal device 5 and the POS input / output box 1 (step S209). The terminal device 5 displays the change amount represented by the received data on the accounting screen. The device driver A of the POS input / output box 1 displays the change amount represented by the received data on the fluorescent display tube 7.

  After step S209, the application A transmits an opening command for opening the drawer 9 to the POS input / output box 1 (step S210). The device driver A of the POS input / output box 1 releases the lock mechanism of the drawer 9 in response to receiving the release command.

  After step S210, the application A generates receipt print data including the product data written in the first registration buffer 23 and transmits it to the POS input / output box 1 (step S211). The device driver A of the POS input / output box 1 causes the printer 8 to print a receipt based on the received print data.

  For example, the clerk takes out coins or banknotes corresponding to the amount of change displayed on the accounting screen from the drawer 9 and gives them to the customer together with the receipt printed by the printer 8.

  After step S211, the application A stores history data including the product code, product data, transaction number, transaction date and time written in the first registration buffer 23 in the history DB 24 (step S212). Furthermore, the application A erases all the data written in the first registration buffer 23 (step S213). Note that the monitoring driver M of the POS input / output box 1 erases all the data in the second registration buffer 140 in response to receiving the print data transmitted in step S211.

  With step S213, the application A ends the process shown in the flowchart.

[Accounting at local POS]
Next, the flow of accounting processing when the POS system functions as a local POS will be described.

  In the local POS, the application B repeatedly executes the operation shown in the flowchart of FIG.

  First, the application B determines whether or not communication with the terminal device 5 is established (step S301). In a recent monitoring process executed by the monitoring driver M, when it is notified that communication with the terminal device 5 is possible (step S108), the application B determines that communication with the terminal device 5 has been established. To do. On the other hand, in a recent monitoring process executed by the monitoring driver M, when it is notified that communication with the terminal device 5 is impossible (step S109), the application B has established communication with the terminal device 5. Judge that there is no.

  If it is determined that communication with the terminal device 5 is established (Yes in step S301), the application B transmits image data of the accounting screen in the initial state to the terminal device 5 (step S302). The terminal device 5 displays an accounting screen based on the received image data. This accounting screen may have a data size smaller than the accounting screen in the case of the cloud POS in order to reduce the processing load of the POS input / output box 1.

  After step S302 or when it is determined in step S301 that communication with the terminal device 5 has not been established (No in step S301), the application B determines whether or not a product code has been input (step S303). ).

  When the device driver B takes in the product code input by the scanner 6, the application B determines that the product code is input (Yes in step S303). At this time, the application B acquires product data corresponding to the product code from the PLU master 22 in the memory 14 (step S304). Furthermore, the application B writes the product code taken in by the device driver B and the product data acquired in step S304 in the record of the second registration buffer 140 (step S305). Application B sets the flag of the record to “1”.

  After step S305, the application B determines whether communication with the terminal device 5 has been established (step S306). The determination method is the same as in step S301. When it is determined that communication with the terminal device 5 has been established (Yes in step S306), the application B transmits the product data acquired in step S304 to the terminal device 5, and the device driver B uses the fluorescent display tube. 7 is displayed to display the product name and unit price included in the product data (step S307).

  Even when it is determined that communication with the terminal device 5 has not been established (No in step S306), the application B controls the fluorescent display tube 7 with the device driver B, and the product name and unit price included in the product data. Is displayed (step S308). However, in this case, the application B does not transmit the product data to the terminal device 5.

  After step S307 or step S308, the application B determines whether or not a subtotal command has been input (step S309). The terminal device 5 transmits a subtotal command to the POS input / output box 1 when, for example, a store clerk operates a subtotal button on the accounting screen displayed on the terminal device 5. The subtotal command can be input by operating an operation button provided in a peripheral device connected to the device connector 16, for example. A subtotal command may be input by scanning a dedicated barcode with the scanner 6.

  When it is determined that the subtotal command has not been input (No in step S309), the operation of the application B returns to step S303.

  On the other hand, if it is determined that a subtotal command has been input (Yes in step S309), the application B determines whether communication with the terminal device 5 has been established (step S310). The determination method is the same as in step S301. If it is determined that communication with the terminal device 5 has been established (Yes in step S310), the application B determines the total price and total of the transaction based on the product data written in each record of the second registration buffer 140. Subtotal data including the product quantity and the like is generated, the generated subtotal data is transmitted to the terminal device 5, and the device driver B controls the fluorescent display tube 7 to display the total amount and the like (step S311). The terminal device 5 displays the total price and the total product quantity represented by the received subtotal data on the accounting screen.

  Even when it is determined that communication with the terminal device 5 has not been established (No in step S310), the application B controls the fluorescent display tube 7 with the device driver B to display the total price or the like (step S312). . However, in this case, the application B does not transmit the subtotal data to the terminal device 5.

  After step S311 or step S312, the application B determines whether or not data indicating a deposit amount from the customer and a closing command are input (step S313). The application B repeats this determination until data representing a deposit amount and a closing command are input (No in step S313). For example, when the closing amount on the accounting screen is operated in a state where the deposit amount is input by operating the numeric keypad on the accounting screen displayed on the terminal device 5, the terminal device 5 performs the input to the POS input / output box 1. The data indicating the amount deposited and the closing command are transmitted. The deposit amount and the closing command can be input by operating an operation button provided in a peripheral device connected to the device connector 16, for example. The tightening command may be input by scanning a dedicated barcode with the scanner 6.

  When it is determined that the data representing the deposit amount and the closing command are received (Yes in step S313), the application B determines whether communication with the terminal device 5 is established (step S314). The determination method is the same as in step S301. If it is determined that communication with the terminal device 5 is established (Yes in step S314), the application B calculates a change amount based on the deposit amount and the total price represented by the received data, and the calculated change amount is calculated. The data to be represented is transmitted to the terminal device 5, and the device driver B controls the fluorescent display tube 7 to display the change amount (step S315). The terminal device 5 displays the change amount represented by the received data on the accounting screen.

  Even when it is determined that communication with the terminal device 5 has not been established (No in step S314), the application B controls the fluorescent display tube 7 with the device driver B to display the change amount (step S316). However, in this case, the application B does not transmit data representing the change amount to the terminal device 5.

  After step S315 or step S316, the application B releases the lock mechanism of the drawer 9 by the device driver B (step S317).

  After step S317, the application B generates receipt print data including the product data written in the second registration buffer 140, and controls the printer 8 by the device driver B to print a receipt based on the print data. . (Step S318).

  After step S318, the application B generates history data including the product data, transaction number, transaction date and time written in the second registration buffer 140, and stores the history data in the memory 14 (step S319). Furthermore, the application B erases the data written in the second registration buffer 140 (step S320).

  With step S320, the application B ends the process shown in the flowchart.

  By the operation of the application B as described above, the product data of the product for which the product code is input when the server is down is written in the second registration buffer 140 together with the flag set to “1”. If there is a product for which the product code is input before the server is down, the product data of the product is written in the second registration buffer 140 together with the flag set to “0” by the accounting process in the cloud POS described above. Therefore, it is possible to distinguish the product data already written in the first registration buffer 23 of the server 2 from the unwritten product data. Further, transaction data of transactions for which accounting has been completed by the application B is stored in the memory 14.

[Upload process]
The upload process in step S103 will be described.
FIG. 8 is a flowchart showing the operation of the monitoring driver M in the upload process.

  First, the monitoring driver M determines whether or not product data is written in the second registration buffer 140 (step S401). If it is determined that the product data is written (Yes in step S401), the monitoring driver M accesses the first registration buffer 23 of the server 2 and determines whether or not the product data is written in the first registration buffer 23. Is determined (step S402). When it is determined that the product data is written in the first registration buffer 23 (Yes in step S402), the monitoring driver M performs a transaction related to the product data written in the first registration buffer 23 and the second registration buffer 140. It is determined whether or not they are the same transaction (step S403).

  An example of the determination method in step S403 will be described. A first counter for managing the transaction number is provided in the storage device of the server 2, and a second counter for managing the transaction buffer is provided in the memory 14 of the POS entry / exit box 1. In the accounting process in the cloud POS, when the application A writes the first product data in the first registration buffer 23 in a state where the product data is not written (at the start of one transaction), the value of the first counter Is incremented by one. Furthermore, the monitoring driver M increments the value of the second counter by 1 when writing the first product data in the second registration buffer 140 in a state where the product data is not written (at the start of one transaction). . That is, while the POS system functions as a cloud POS, the first and second counters indicate the same transaction number. In the accounting process at the local POS, when the application B writes the first product data in the second registration buffer 140 in a state where product data is not written (at the start of one transaction), the value of the second counter Is incremented by one. That is, when one transaction is completed while the POS system is functioning as a local POS, the transaction numbers of the first and second counters have different values. When the POS system functions as a cloud POS again, the transaction number consistency can be maintained by updating the transaction number of the first counter with the transaction number of the second counter.

  The monitoring driver M performs the determination in step S403 using such first and second counters. That is, the monitoring driver M determines that the transactions are the same when the transaction numbers indicated by the first and second counters are the same. On the other hand, the monitoring driver M determines that the transactions are not the same when the transaction numbers indicated by the first and second counters are different.

  When it determines with it not being the same transaction (No of step S403), the monitoring driver M deletes all the data written in the 1st registration buffer 23 (step S404). Further, the monitoring driver M uploads (transfers) the product code and the product data written in the record whose flag is “1” among the records of the second registration buffer 140 to the first registration buffer 23 (step S405). . When it is determined in step S403 that the transactions are not the same, the flags in all records in the second registration buffer 140 are “1”. After step S405, the monitoring driver M sets the flag of each record in the second registration buffer 140 to “0” (step S406).

  On the other hand, when it determines with it being the same transaction (Yes of step S403), the monitoring driver M performs step S405, S406, without passing through step S404. In this case, the first registration buffer 23 stores the product data of the product for which the product code is input when the POS system is functioning as the cloud POS, and the product code when the POS system is functioning as the local POS. The product data of the input product is mixed. That is, when switching to the local POS during the accounting process by the cloud POS and then recovering to the cloud POS, the store clerk can continue accounting without re-entering the product code.

  Even when it is determined in step S402 that product data is not written in the first registration buffer 23 (No in step S402), the monitoring driver M executes steps S405 and S406 without passing through step S404.

  If it is determined in step S401 that the product data has not been written in the second registration buffer 140 (No in step S401), the monitoring driver M stores all the data if data has been written in the first registration buffer 23. It deletes (step S407).

  After step S406 or step S407, the monitoring driver M determines whether or not history data is stored in the memory 14 (step S408). If it is determined that the history data is stored (Yes in step S408), the monitoring driver M uploads the history data to the history DB 24 (step S409). When a plurality of history data is stored in the memory 14, the monitoring driver M uploads them all. After step S409, the monitoring driver M deletes all history data from the memory 14 (step S410).

  After step S410, or when it is determined that the history data is not stored in the memory 14 (No in step S408), the monitoring driver M ends the upload process. By such an upload process, the product data input when the POS system functions as a local POS can be replenished to the registration buffer 23. Further, history data of transactions processed when the POS system functions as a local POS can be supplemented to the history DB 24.

  As is clear from the above description, the POS input / output box 1 is a relay means for relaying control of peripheral devices by the server 2 when communication with the server 2 by the communication device 15 is established. When the communication with the server 2 is disconnected, the accounting processing means for directly controlling the peripheral device without executing the server 2 and executing the accounting process, and the communication after the communication with the server 2 by the communication device 15 is disconnected. When the data is restored, it functions as a transfer means for transferring information such as product data stored in the memory 14 to the server 2. These functions as each means are mainly realized by the monitoring driver M, the device drivers A and B, and the application B.

  The server 2 transmits control data for controlling peripheral devices to the POS input / output box 1 and performs accounting processing based on input data from the peripheral devices transmitted from the POS input / output box 1. Functions as a means. The function as this means is mainly realized by the application A.

  According to the POS system according to the present embodiment, even when the communication between the POS input / output box 1 and the server 2 is disconnected due to the server 2 being down or the like, the local area mainly composed of the POS input / output box 1 is used. Accounting can be continued as a POS. Therefore, the reliability of the POS system is improved.

  In addition, the POS system according to the present embodiment writes the product data related to the product code input in the accounting process using the cloud POS in both the first registration buffer 23 and the second registration buffer 140. Therefore, even when the cloud POS is switched to the local POS during the accounting process, the accounting process can be continued using the product data written in the second registration buffer 140 without requiring the product code input again.

  Further, the POS system according to the present embodiment transfers the product data written in the second registration buffer 140 in the accounting process by the local POS to the server 2 after the communication between the POS input / output box 1 and the server 2 is restored. . Therefore, even when the local POS is switched to the cloud POS during the accounting process, the accounting process can be continued using the product data written in the first registration buffer 23 without the need to input the product code again.

Further, when the POS system according to the present embodiment functions as a local POS, even if communication between the POS input / output box 1 and the terminal device 5 is impossible, the fluorescent display tube 7 and the printer 8 are used. Accounting can be continued using peripheral devices such as
In addition, various suitable effects can be obtained from the configuration disclosed in the present embodiment.

  Several modifications regarding this embodiment are shown.

  In the present embodiment, as an example of the accounting system, a POS system that accounts for the price of goods sold at a retail store is disclosed. However, a configuration similar to this POS system can be applied to an accounting system that accounts for the cost of services at a store (for example, a restaurant) that provides services.

  The accounting system also includes devices such as a card reader that reads cards such as credit cards and point cards, and an electronic money reader that reads information about electronic money from an electronic money medium as peripheral devices connected to the POS input / output box 1. May be included.

  In the present embodiment, a POS system using a cloud is illustrated. However, the accounting system may be constructed by other forms of network computing such as a client server system using a server installed in a store or headquarters.

  In the present embodiment, the memory 13 of the POS input / output box 1 stores the AP file 130 and the driver file 131 in advance. However, the AP file 130 and the driver file 131 are not necessarily stored in advance in an electronic device such as the POS input / output box 1. The AP file 130 and the driver file 131 may be downloaded from the network to the electronic device, or those recorded on the recording medium may be installed in the electronic device. The recording medium may be in any form as long as it can store data such as a CD-ROM or a memory card and can be read by the apparatus. The function obtained by installing or downloading the AP file 130 or the driver file 131 may be realized in cooperation with an OS (operating system) of an electronic device.

  Although several embodiments of the present invention have been described, these embodiments are 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 changes 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 invention described in the claims and the equivalents thereof.

  DESCRIPTION OF SYMBOLS 1 ... POS entry / exit box, 2 ... Server, 3 ... Access point, 4 ... Hub, 5 ... Terminal device, 6 ... Scanner, 7 ... Fluorescent display tube, 8 ... Printer, 9 ... Drawer, 10, 20 ... CPU, 15 ... Communication device, 16 ... Device connector, 21, 130 ... AP file, 22 ... PLU master, 23 ... First registration buffer, 24 ... History DB, 131 ... Driver file, 140 ... Second registration buffer.

Claims (6)

A first communication means for communicating with a server that executes an accounting process for accounting for a commercial transaction;
Second communication means for communicating with peripheral devices used for the accounting process;
When communication with the server by the first communication means is established, relay means for relaying control of the peripheral device by the server;
When communication with the server by the first communication means is disconnected, accounting processing means for directly controlling the peripheral device and executing the accounting processing without using the server;
An electronic device comprising: The peripheral device includes an input device for inputting information on a purchased product or service,
The relay means transmits information input by the input device to the server when communication with the server by the first communication means is established,
A memory for storing information input by the input device when communication with the server by the first communication unit is disconnected;
Transfer means for transferring information stored in the memory to the server when the communication is restored after the communication with the server by the first communication means is disconnected;
The electronic apparatus according to claim 1, further comprising: An accounting system in which a server and peripheral devices used for accounting for accounting for commercial transactions are connected to an electronic device,
The server
First accounting processing means for transmitting control data for controlling the peripheral device to the electronic device, and executing the accounting processing based on input data from the peripheral device transmitted from the electronic device;
With
The electronic device is
When communication between the electronic device and the server is established, the peripheral device is controlled based on the control data received from the server, and the input data input from the peripheral device is transmitted to the server. Relay means to
When communication between the electronic device and the server is disconnected, second accounting processing means for directly controlling the peripheral device and executing the accounting processing without depending on the control data;
An accounting system comprising: The peripheral device includes an input device for inputting information on a purchased product or service,
When the communication with the server by the first communication unit is established, the relay unit transmits information input by the input device to the server as the input data,
The electronic device is
A memory for storing information input by the input device when communication with the server by the first communication unit is disconnected;
Transfer means for transferring information stored in the memory to the server when the communication is restored after the communication with the server by the first communication means is disconnected;
Further comprising
The first accounting processing means executes the accounting processing based on the information transmitted by the relay means and the information transferred by the transfer means.
The accounting system according to claim 3. The accounting system further includes a terminal device that displays a screen related to the accounting process based on screen data received from the outside,
The first accounting processing means transmits the screen data to the terminal device when communication between the electronic device and the server is established,
The second accounting processing means transmits the screen data to the terminal device when communication between the electronic device and the server is disconnected.
The accounting system according to claim 3 or 4, characterized in that. An electronic device comprising a first communication means for communicating with a server for performing an accounting process for accounting for a commercial transaction, and a second communication means for communicating with a peripheral device used for the accounting process;
When communication with the server by the first communication means is established, relay means for relaying control of the peripheral device by the server, and
Accounting processing means for executing the accounting processing by directly controlling the peripheral device without depending on the server when communication with the server by the first communication means is disconnected;
Program to function as.

Images