Settlement device and program

Abstract

To provide a settlement device and a program, capable of simply examining a frequency or a content of communication failure.SOLUTION: A settlement device of the present embodiment includes: a communication control unit that performs communication relating to settlement processing between itself and a server device; a detection unit that detects that communication failure has occurred during communication with the server device; a first generation unit that, when the detection unit detects that the communication failure has occurred, generates information including an occurrence date of the communication failure, information indicating the server device as a communication destination, and a content of the communication failure; a storage unit that individually stores the information generated by the first generation unit as a communication failure history; and an output control unit that outputs the communication failure history stored in the storage unit.SELECTED DRAWING: Figure 9

Description

Technical Field

[0001] Embodiments of the present invention relate to a settlement device and a program.

Background Art

[0002] Conventionally, in stores such as supermarkets, in order to handle settlements other than cash, settlement terminals for performing settlement processing by credit card or electronic money are installed. The settlement terminal performs settlement processing by communicating with a center server such as a credit company or a financial institution.

[0003] By the way, in the above-described settlement terminal, communication with the center server may fail for various reasons (hereinafter, in this specification, failure of communication with other devices is referred to as a communication failure). When the business of the store is hindered due to a communication failure, the maintenance staff of the settlement terminal will take measures. And, in order for the maintenance staff to handle the communication failure, it is generally necessary to investigate the content of the communication failure.

[0004] However, in a conventional settlement terminal, in order to investigate the content of a communication failure, it is necessary to extract and analyze the recorded content related to the communication failure from the logs recorded in the settlement terminal. This log extraction and analysis work is a heavy burden on the maintenance staff, and a technology that can easily investigate the content of the communication failure is eagerly desired.

Summary of the Invention

Problems to be Solved by the Invention

[0005] The problem to be solved by the present invention is to provide a settlement device and a program capable of easily confirming the content of a communication failure.

Means for Solving the Problems

[0006] The settlement device according to the embodiment includes a communication control unit that performs communication related to settlement processing with a server device, a detection unit that detects that a communication failure has occurred during communication with the server device, and when the detection unit detects that the communication failure has occurred, a first generation unit that generates information including the date and time of occurrence of the communication failure, information indicating the server device as the communication destination, and the content of the communication failure, and an output control unit that outputs the information generated by the first generation unit as a communication failure history. The first generation unit includes, as the content of the communication failure, , Notification information representing a process in which a failure has occurred on the communication protocol Report to generate the information.

Brief Description of the Drawings

[0007]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

DETAILED DESCRIPTION OF THE INVENTION

[0008] Hereinafter, embodiments of a settlement device and a program will be described in detail with reference to the accompanying drawings. Note that the embodiments described below are merely one embodiment of the settlement device and the program, and do not limit the configuration, specifications, and the like thereof. This embodiment is an application example to a settlement terminal that performs transaction settlements introduced in a store such as a supermarket.

[0009] FIG. 1 is a diagram showing the configuration of a settlement system 1 according to this embodiment. As shown in the figure, the settlement system 1 includes a POS terminal 2, a settlement terminal 3, an electronic money terminal 4, a center server 5, and a maintenance server 6. The settlement terminal 3 is an example of a "settlement device", and the center server 5 and the maintenance server 6 are examples of "server devices".

[0010] The settlement terminal 3 and the electronic money terminal 4 are communicably connected by wire or wirelessly. Also, the settlement terminal 3 and the POS terminal 2 are communicably connected by wire or wirelessly.

[0011] In addition, the settlement terminal 3, the center server 5, and the maintenance server 6 are communicably connected via a network N. The network N is, for example, a dedicated line with high security, a VPN (Virtual Private Network), or a public network such as the Internet.

[0012] As the network N, for example, a fixed telephone line such as an analog line, an ADSL line, a digital line (ISDN line), an optical fiber utilization line, or a mobile telephone line such as a mobile phone line or a PHS line is used.

[0013] Note that in Fig. 1, the settlement system 1 includes one POS terminal 2, one settlement terminal 3, one electronic money terminal 4, one center server 5, and one maintenance server 6 each. However, the number of each device connected to the settlement system 1 is not particularly limited.

[0014] The settlement terminal 3 is a device having a settlement function that reads card information from an IC card, a magnetic card, etc. and performs card settlement processing by communicating with servers such as credit card companies, financial institutions, and electronic money centers.

[0015] The electronic money terminal 4 is a terminal that accesses a non-contact card storing electronic money information using short-range wireless communication technology such as NFC (Near Field Communication), and executes settlement processing using the settlement-enabled amount information (hereinafter referred to as "card amount information") stored in the card. The electronic money terminal 4 reads the card amount information from the card and transmits it to the settlement terminal 3.

[0016] The POS terminal 2 is a device that processes product sales data of products purchased by customers and performs settlement processing for one transaction. Also, when performing card settlement such as credit cards, debit cards, and electronic money, the POS terminal 2 performs settlement processing (card settlement processing) for one transaction in conjunction with the settlement terminal 3.

[0017] As shown in Fig. 1, on the upper part of the main body 21 of the POS terminal 2, there are provided a display unit 22 for store clerks and a display unit 23 for customers. Each of the display units 22 and 23 is composed of an LCD (Liquid Crystal Display) or an LCD with a touch panel disposed on the surface, and displays product names, product prices, the total amount of one transaction, etc.

[0018] On the upper surface of the main body 21, a keyboard 24 is provided, and cash payment keys, credit payment keys, etc. for selecting payment methods such as cash payment or credit payment are provided. Further, a printer 25 for printing receipts or the like is provided inside the main body 21. The receipt paper printed by the printer 25 is issued from a receipt issuing port 26 provided at the upper part of the main body 21.

[0019] In response to an authentication request for payment processing from the payment terminal 3, the center server 5 performs checks such as a negative check of the card, and then transmits a command for executing authentication to the payment terminal 3. The center server 5 is, for example, a server of a credit company, a financial institution, an electronic money center, or the like. Also, the center server 5 may be a server for connecting the payment terminal 3 and servers of a credit company, a financial institution, an electronic money center, or the like.

[0020] The maintenance server 6 manages various data (programs, etc.) introduced into the payment terminal 3. The maintenance server 6, for example, receives version information of a program from the payment terminal 3 and transmits a necessary update program to the payment terminal 3. Also, the maintenance server 6 may, for example, acquire logs, setting data, etc. from the payment terminal 3 and perform processes such as grasping the state of the payment terminal 3.

[0021] Next, the payment terminal 3 will be described in detail. FIG. 2 is a diagram showing the appearance of the payment terminal 3, and FIG. 3 is a block diagram showing the hardware configuration of the payment terminal 3.

[0022] In FIG. 2, a power switch 36 is provided on the side of the main body 31 of the payment terminal 3. Also, on the upper part of the main body 31, an upper surface panel 37 that can be opened and closed with respect to the main body 31 is provided.

[0023] By opening the upper surface panel 37, a roll-shaped receipt paper can be set inside the main body 31. Also, on the surface of this upper surface panel 37, a display unit 32 with a touch panel serving as an operation unit 33 disposed on the surface is provided.

[0024] On the upper part of the side surface of the main body 31, a card reader 34 for reading information stored in a settlement card from the card is provided. As the settlement card, for example, a credit card, a debit card, or the like can be used.

[0025] Inside the main body 31, a printing unit 57 (see FIG. 3) for printing information related to settlement, a sales report, etc. on the above-mentioned receipt paper is provided. The printed receipt paper is issued from a receipt issuing port 35 provided between the main body 31 and the upper surface panel 37.

[0026] Next, in FIG. 3, the settlement terminal 3 includes a control unit 100 for controlling each part. As shown in FIG. 3, the control unit 100 is configured by connecting a ROM (Read Only Memory) 52 and a RAM (Random Access Memory) 53 to a CPU (Central Processing Unit) 51 that centrally controls each part via bus lines 55 such as an address bus and a data bus.

[0027] In addition, a memory unit 54 and a controller 56 are connected to the control unit 100 via a bus line 55. The control unit 100 executes control processing described later by the CPU 51 operating according to a control program 541 stored in the memory unit 54 and expanded in the RAM 53.

[0028] The memory unit 54 (an example of a “storage unit”) is a non-volatile memory such as a flash memory that retains stored information even when the power is turned off, and stores programs including the control program 541.

[0029] In addition, the memory unit 54 stores a communication failure history 542 described later. The memory unit 54 also stores the identification number of the settlement terminal 3, information for identifying the store where the settlement terminal 3 is installed, etc. The RAM 53 temporarily stores information read from the memory unit 54.

[0030] In addition, the controller 56 connects the display unit 32 and the operation unit 33. The controller 56 executes various controls based on commands from the control unit 100. The display unit 32 displays various information including the images of keys. The operation unit 33 is a touch panel provided on the display unit 32, and by touching the touch panel at a position corresponding to the key displayed on the display unit 32, various key operations are executed.

[0031] In addition, the controller 56 connects the printing unit 57 and the card reading unit 34. The printing unit 57 pulls out the leading edge of the receipt paper stored inside the main body 31, and prints settlement information and the like on the receipt paper using, for example, a thermal head. The card reading unit 34 reads card information stored magnetically or electrically on the settlement card.

[0032] In addition, the bus line 55 connects the communication I / F (Interface) 59, 60, 61. The communication I / F 59 is connected to the POS terminal 2. The communication I / F 60 is connected to the electronic money terminal 4. The communication I / F 61 is connected to the center server 5 and the maintenance server 6. The settlement terminal 3 transmits and receives information to and from the POS terminal 2, the electronic money terminal 4, the center server 5, and the maintenance server 6 via each communication I / F 59, 60, 61.

[0033] Next, the control of the settlement terminal 3 of the embodiment will be described. FIG. 4 is a functional block diagram showing the functional configuration of the settlement terminal 3. The settlement terminal 3 realizes the communication control unit 101, the display control unit 102, the detection unit 103, the second generation unit 105, and the printing control unit 106 by operating according to programs such as the control program 541 stored in the memory unit 54 by the control unit 100.

[0034] The communication control unit 101 communicates with the center server 5 or the maintenance server 6. Specifically, the communication control unit 101 communicates with the center server 5 or the maintenance server 6 via the communication I / F 61.

[0035] The display control unit 102 controls the display unit 32 to perform control for displaying various screens. Specifically, the display control unit 102 performs control to display a GUI (Graphical User Interface) for assisting various operations related to card payment. That is, the display control unit 102 performs control to display a software keyboard (operation keys) for inputting the payment amount, selecting a payment method (such as lump-sum payment or installment payment), etc.

[0036] Here, various screens displayed by the display control unit 102 will be described. FIG. 5 is an explanatory diagram showing an example of a service selection menu screen 500.

[0037] The service selection menu screen 500 is composed of tabs (services 501, aggregation 502, settings 503, practice 504, and reprint 505), selection buttons (credit 511, debit 512, UnionPay (registered trademark) 513, electronic money 514, and points 515), a paper feed button 521, a help button 522, and a scroll button 523.

[0038] Service 501 is a tab for an operator to declare that a settlement process is to be performed on the settlement terminal 3. Aggregation 502 is a tab for an operator to declare that past transaction histories are to be aggregated on the settlement terminal 3. Settings 503 is a tab for an operator to declare that setting processes, etc. of the settlement terminal 3 are to be performed on the settlement terminal 3.

[0039] Practice 504 is a tab for an operator to declare that the operation of the settlement process is to be practiced on the settlement terminal 3. Reprint 505 is a tab for an operator to declare that a receipt is to be reprinted on the settlement terminal 3.

[0040] Credit 511, Debit 512, UnionPay (registered trademark) 513, Electronic Money 514, and Points 515 are selection buttons that are displayed when the operator selects Service 501. Note that on the initial screen, Credit 511, Debit 512, UnionPay (registered trademark) 513, Electronic Money 514, and Points 515 are displayed as selection buttons. However, when the operator selects a different tab, buttons different from the above are displayed as selection buttons.

[0041] The paper feed button 521 is a button for supplying the paper for printing the receipt to the printing unit 57 and performing the process of discharging it after printing. The help button 522 is a button for displaying a help menu that shows how to use the payment terminal 3 and the like.

[0042] The scroll button 523 is a button for switching the selection buttons displayed on the display unit 32 when the number of selection buttons is large and cannot be fully displayed on one screen. "1 / 1" in the figure indicates that the selection buttons on the first page out of one page are being displayed.

[0043] This makes it possible to know which page of the selection buttons is currently being displayed. For example, when "2 / 4" is displayed, it can be understood that the selection buttons on the second page out of four pages are being displayed.

[0044] Next, the screen transition when processing is performed on the payment terminal 3 will be described. FIG. 6 is an explanatory diagram showing an example of the screen transition when payment processing is performed on the payment terminal. Each screen in FIG. 6 transitions as indicated by the arrows in the figure.

[0045] When the power switch 36 of the payment terminal 3 is turned on and the OS is started, the initial screen (see FIG. 5) appears. When any one of the tabs Service 501, Aggregation 502, Settings 503, Practice 504, and Reprint 505 is selected by the operator on the initial screen, the process assigned to the selected tab is executed.

[0046] On the initial screen, the display control unit 102 displays the selection menu screen for service 501. The selection menu screen for service 501 includes buttons for credit 511, debit 512, UnionPay (registered trademark) 513, electronic money 514, and points 515.

[0047] These buttons represent the methods used for payment. The operator presses the button corresponding to the type of card to be used among these to make a selection. A screen that requests input from the operator such as pressing a button is collectively called an input screen.

[0048] For example, when the operator presses the credit 511 button on the selection menu screen for service 501, the display control unit 102 displays the "message screen for the customer (Fig. 6(a))". The message screen for the customer is a screen for prompting the customer to insert the selected card into the card reader 34. In Fig. 6(a), a message is displayed prompting the customer to insert the credit card into the card reader 34.

[0049] When the customer inserts a credit card into the card reader 34 and the payment terminal 3 detects the reading of the card information while the message screen is being displayed, the display control unit 102 displays the "security code input screen (Fig. 6(b))". The security code input screen is a screen for instructing the customer to input the security code of the credit card.

[0050] When the customer inputs the security code and presses the "SET" button, the display control unit 102 displays the "product code input screen (Fig. 6(c))". The product code input screen is a screen for inputting the product code of the product subject to the transaction. When the operator inputs the product code and presses the "SET" button, the display control unit 102 displays the "amount input screen (Fig. 6(d))".

[0051] The amount input screen is a screen for inputting the amount of a product. Note that the product code and the amount of the product can also be automatically acquired from the POS terminal 2. When the operator inputs the amount and presses the "Set" button, the display control unit 102 displays the "Payment Method Selection Menu Screen (Fig. 6(e))".

[0052] The payment method selection menu screen is a screen for selecting a payment method. In Fig. 6(e), selection buttons for "Full Payment", "Bonus", "Installment Payment", and "Revolving" are arranged. For example, when the operator selects the "Full Payment" selection button on the payment method selection menu screen, the display control unit 102 displays the "PIN Input Screen (Fig. 6(f))". The PIN input screen is a message screen that prompts the customer to input a PIN.

[0053] When the customer inputs the PIN from the keypad, the display control unit 102 displays the "Payment Details Confirmation Screen (Fig. 6(g))". The payment details confirmation screen is a screen for having the customer confirm the payment details. In Fig. 6(g), on the payment details confirmation screen, in addition to the payment details, an execution button is displayed.

[0054] In a state where the PIN input screen is being displayed, when the customer confirms the payment details and presses the execution button, the payment terminal 3 establishes a communication connection with the center server 5. When the execution button is pressed by the customer, the display control unit 102 displays the "Message Screen Indicating Communication Status (Fig. 6(h))". When the payment process is completed, the payment terminal 3 disconnects the communication with the center server 5. When the payment process is completed, the display control unit 102 displays a completion message (Fig. 6(i)).

[0055] By the way, in the above, when the transaction is completed and the communication with the center server 5 is disconnected, a completion message (Fig. 6(i)) is displayed. However, a communication failure may occur during the communication with the center server 5. In this case, the display control unit 102 performs control to display an error message screen. Fig. 7 is an explanatory diagram showing an example of the error message screen displayed when a communication failure occurs.

[0056] When a communication failure occurs while a message screen (Fig. 6(h)) indicating the communication state is being displayed, the display control unit 102 performs control to display the error message screen 570. The error message screen 570 includes a message field 571, a reconnection button 572, and a cancellation button 573.

[0057] The message field 571 is a display field that displays that a communication failure has occurred. In the example of Fig. 7, a simple content of the communication failure that the connection to the center is impossible and a message asking whether to reconnect are displayed. Note that in addition to these, the message field 571 may display an error code, a name of a specific communication destination, a name of a function related to the process in which the communication failure has occurred, and the like.

[0058] The reconnection button 572 is a button for attempting reconnection. The cancellation button 573 is a button for instructing cancellation of the transaction.

[0059] Returning to Fig. 4 and continuing the explanation. The detection unit 103 detects that a communication failure has occurred during communication between the communication control unit 101 and the center server 5 or the maintenance server 6. Specifically, for example, the detection unit 103 detects a communication failure when the communication control unit 101 fails to establish communication with the center server 5 or the maintenance server 6 or when data transmission / reception between the communication control unit 101 and the center server 5 or the maintenance server 6 fails.

[0060] When the detection unit 103 detects that a communication failure has occurred, the first generation unit 104 generates information including the date and time of occurrence of the communication failure, information indicating the server device of the communication destination, and the content of the communication failure. Specifically, the first generation unit 104 generates information composed of a failure number, a date and time of occurrence, a communication destination, a transaction content, a failure content, a failure occurrence location, and failure information. The information generated by the first generation unit 104 is individually stored in the memory unit 54 as a communication failure history 542.

[0061] Here, the communication failure history 542 will be described. The communication failure history 542 individually stores information including the date and time of occurrence of a communication failure, the communication destination at the time of the communication failure, and the details of the communication failure for communication failures that occurred in the past.

[0062] Specifically, the communication failure history 542 stores, for example, information on the failure number, date and time of occurrence, communication destination, transaction details, details of the failure, location of the failure occurrence, and failure information for the most recent 20 communication failures among the communication failures that occurred in the past. In this example, the communication failure history 542 stores information on the most recent 20 communication failures, but the number of communication failures to be retained as the communication failure history 542 is not limited to 20.

[0063] The failure number is a number for distinguishing each communication failure on the communication failure history 542. For example, the communication failure that occurred most recently is given the failure number "0001", and failure numbers from "0001" to "0020" are assigned in the order of occurrence of the communication failures such that the 20th communication failure from the most recent is given the failure number "0020".

[0064] In this case, when a new communication failure occurs, the failure number of the newly occurred communication failure becomes "0001", and the failure number of the communication failure that was previously "0001" is shifted down to "0002".

[0065] Also, by sequentially shifting down the failure numbers after "0002", for example, the failure number of the communication failure that was "0019" becomes "0020". Then, the information on the communication failure that was previously "0020" is erased due to the above shift down.

[0066] The date and time of occurrence is information indicating the date and time when the communication failure occurred. The communication destination is information representing the communication destination of the settlement terminal 3 when the communication failure occurred. For example, the communication destination is the center server of a credit card company, the center server of electronic money, etc. The transaction details are information representing the transaction details when the communication failure occurred. The transaction details are information indicating the type of transaction such as credit sales, electronic money sales, etc.

[0067] The failure content is information indicating the content of the communication failure. As the failure content, for example, information representing a process in which a failure (error) has occurred on the communication protocol, such as TCP / IP connection establishment failure, TCP / IP data reception failure, etc., is stored. The failure occurrence location is information representing the name of the process where the communication failure has occurred. The failure occurrence location is, for example, the name of the function related to the process where the communication failure has occurred.

[0068] The failure information is detailed information regarding the communication failure. In the failure information, for example, the return value of a function, detailed error codes, the received signal strength of the wireless LAN (when using the wireless LAN), messages related to the communication failure, etc. are stored.

[0069] The second generation unit 105 generates output data of the communication failure history based on the communication failure history 542 stored in the memory unit 54. Specifically, the second generation unit 105 generates print data of the communication failure history.

[0070] More specifically, the second generation unit 105 adds information such as the identification number of the payment terminal 3, information on the store where the payment terminal 3 is installed, information on the type of line used for communication, the date and time when printing is instructed, etc. to the information included in the above-mentioned communication failure history 542, and generates print data of the communication failure history.

[0071] The print control unit 106 controls the print unit 57 and prints the print data of the communication failure history generated by the second generation unit 105. Note that printing is an example of "output", and the print control unit 106 is an example of an "output control unit".

[0072] Here, the print process of the communication failure history by the print control unit 106 will be described in detail. FIG. 8 is an explanatory diagram showing an example of screen transition when performing the communication failure history print process in the payment terminal 3. Each screen in FIG. 8 transitions from left to right as indicated by the arrow Z in the same figure.

[0073] For example, when the operator selects setting 503 on the initial screen (see FIG. 5) and presses the scroll button 523, the display control unit 102 displays a screen (FIG. 8(k)) including a selection button labeled "Print Communication Failure History".

[0074] Subsequently, when the operator presses "Print Communication Failure History", the display control unit 102 displays a screen (FIG. 8(l)) for instructing printing. This screen has a reset button for returning to the previous screen and an execution button for executing the printing.

[0075] When the operator presses the execution button, the display control unit 102 displays a screen (FIG. 8(m)) indicating the printing status. Also, in response to the pressing of the execution button, the second generation unit 105 generates print data for the communication failure history, and the print control unit 106 prints the print data as the communication failure history.

[0076] FIG. 9 is an explanatory diagram showing an example of the printed communication failure history 600. The printed communication failure history 600 includes a terminal number 601, a printing date and time 602, a franchise store name 603, a communication line 604, a failure number 605, an occurrence date and time 606, a communication destination 607, a transaction content 608, a failure content 609, a failure occurrence location 610, and failure information 611.

[0077] Also, for the failure number 605, the occurrence date and time 606, the communication destination 607, the transaction content 608, the failure content 609, the failure occurrence location 610, and the failure information 611, only the information is printed without a project name. Therefore, a format F representing the correspondence between the project names such as the failure number and the printing positions is printed so that the project names can be associated with the printed information.

[0078] The terminal number 601 is printed with the identification number of the settlement terminal 3 stored in the memory unit 54. The printing date and time 602 is printed with the date and time when the operator pressed the execution button on the screen (FIG. 8(l)) for instructing printing. The franchise store name 603 is printed with the name of the store specified from the information identifying the store where the settlement terminal 3 stored in the memory unit 54 is installed.

[0079] The communication line prints the type of communication line used when the settlement terminal 3 communicates with the center server 5 or the maintenance server 6. For example, information such as optical (line), ISDN (line), etc. is printed.

[0080] Since the contents of the failure number 605, the occurrence date and time 606, the communication destination 607, the transaction details 608, the failure details 609, the failure occurrence location 610, and the failure information 611 have been described above, the description is omitted. These pieces of information are printed in the order in which the communication failures occurred.

[0081] For example, in the example of FIG. 9, as the failure number "0001" which is the most recent communication failure, it is printed that at "YYYY / MM / DD HH:MM:SS", during communication with "AAA", in the "credit sales" process, "TCP / IP connection establishment failure" occurred.

[0082] Also, the function related to the process in which "TCP / IP connection establishment failure" occurred is "AAA_XXX", and "XXXXXXXX, -40dbm" is printed as information regarding the communication failure. "XXXXXXXX" represents a detailed error code, and "-40dbm" represents the received signal strength of the wireless LAN.

[0083] Also, as the failure number "0002", it is printed that at "YYYY / MM / DD HH:MM:SS", during communication with "BBB", in the "credit sales" process, "TCP / IP data transmission failure" occurred.

[0084] Also, the function related to the process in which "TCP / IP data transmission failure" occurred is "BBB_YYY", and "transmission timeout" is printed as a message regarding the communication failure.

[0085] Also, as the failure number "0003", it is printed that at "YYYY / MM / DD HH:MM:SS", during communication with "CCC", in the "credit sales" process, "TCP / IP data reception failure" occurred.

[0086] Also, the function related to the process in which "TCP / IP data reception failure" occurred is "CCC_ZZZ", and "reception timeout" is printed as a message regarding the communication failure.

[0087] As described above, the printing control unit 106 prints the print data generated by the second generation unit 105 as a communication failure history. The print result of the printing control unit 106 includes the occurrence date and time 606 for each of the one or more communication failures that occurred most recently.

[0088] Therefore, by checking the printed communication failure history, the operator can easily know at what time intervals the communication failures are occurring. That is, the operator can grasp the frequency of communication failures by checking the occurrence date and time for multiple communication failures.

[0089] Also, the print result of the printing control unit 106 includes the communication destination 607 for each of the one or more communication failures that occurred most recently. Therefore, the operator can grasp whether a communication failure is occurring at a specific communication destination or whether a communication failure is occurring regardless of the communication destination.

[0090] For example, in the example of FIG. 9, since the communication destinations are different from "AAA", "BBB", and "CCC", the operator can infer that a communication failure is not caused by a specific communication destination.

[0091] Also, the print result of the printing control unit 106 includes the transaction content 608 for each of the one or more communication failures that occurred most recently. Therefore, the operator can grasp whether a communication failure is occurring for a specific transaction content or whether a communication failure is occurring regardless of the transaction content.

[0092] For example, in the example of FIG. 9, since the transaction content is only "credit sales", the operator can make a certain prediction, such as the possibility that there is a problem with the processing related to "credit sales".

[0093] In addition, the printing result of the printing control unit 106 includes the failure details 609 for each of the one or more recently occurred communication failures. Therefore, the operator can grasp whether only communication failures of a specific content have occurred, whether communication failures of various contents have occurred, and the tendency of the content of the communication failures.

[0094] For example, in the example of FIG. 9, the failure details are "TCP / IP connection establishment failure", "TCP / IP data transmission failure", and "TCP / IP data reception failure", and the operator can infer that the communication failures do not occur biased towards a specific content.

[0095] In addition, the printing result of the printing control unit 106 includes the failure location 610 for each of the one or more recently occurred communication failures. Therefore, the operator can grasp the name of the function related to the process where the communication failure has occurred.

[0096] For example, even if the failure details are the same "TCP / IP connection establishment failure", it is possible that the functions related to the process where "TCP / IP connection establishment failure" occurs are different. If the functions related to the process where the communication failure occurs are different, the causes of the communication failure may also be different. That is, by checking the failure location 610, the operator can increase the judgment materials for identifying the cause of the communication failure.

[0097] In addition, the printing result of the printing control unit 106 includes the failure information 611 for each of the one or more recently occurred communication failures. Therefore, by checking the failure information 611, the operator can grasp more detailed information about the communication failure. Thereby, it becomes easier for the operator to grasp the tendency of the occurred communication failure.

[0098] For example, the operator may be able to infer the cause of the communication failure by checking the detailed error code. Also, for example, the operator can roughly estimate whether there is a problem with the wireless communication equipment and a communication failure has occurred (such as radio waves being blocked), or whether the communication failure has occurred due to other factors, by checking the received signal strength of the wireless LAN for the last few cases.

[0099] Next, the processing of the settlement terminal 3 according to the present embodiment will be described. FIG. 10 is a flowchart showing an example of the communication failure history printing process of the settlement terminal 3 according to the present embodiment.

[0100] First, the communication control unit 101 starts communication with the center server 5 or the maintenance server 6 (step S101). When a communication failure occurs, the detection unit 103 detects the communication failure (step S102). The first generation unit 104 generates information regarding the communication failure, and the memory unit 54 stores the information generated by the first generation unit 104 individually as the communication failure history 542 (step S103).

[0101] The second generation unit 105 checks whether there is an instruction to print the communication failure history (step S104). If there is no print instruction (step S104: No), the process returns to step S101. If there is a print instruction (step S104: Yes), the second generation unit 105 generates print data for the communication failure history based on the communication failure history 542 in the memory unit 54 (step S105).

[0102] Then, the print control unit 106 prints the print data generated by the second generation unit 105 and ends this process (step S106).

[0103] Next, the effects of the payment terminal 3 according to the present embodiment will be described. The payment terminal 3 according to the present embodiment includes a communication control unit 101 that communicates with a center server 5 and a maintenance server 6, a detection unit 103 that detects the occurrence of a communication failure during communication with the center server 5 or the maintenance server 6 by the communication control unit 101, and a first generation unit 104 that generates information including the occurrence date and time of the communication failure, information indicating the communication destination, and the content of the communication failure when the detection unit 103 detects the occurrence of the communication failure, a memory unit 54 that individually stores the information generated by the first generation unit 104 as a communication failure history 542, and a printing control unit 106 that prints the communication failure history 542 stored in the memory unit 54.

[0104] As a result, the payment terminal 3 according to the present embodiment can print the occurrence date and time of the communication failure, information indicating the communication destination, and the content of the communication failure in a form that is easy for the operator to grasp with respect to the communication failures that have occurred in the past. That is, according to the payment terminal 3 according to the present embodiment, the content of the communication failure can be easily confirmed.

[0105] In addition, the payment terminal 3 according to the present embodiment includes a second generation unit 105 that generates output data in which the communication failure histories 542 stored in the memory unit 54 are arranged in chronological order based on the occurrence date and time of the communication failures included in the communication failure history 542. As a result, it becomes easier for the operator to grasp the tendency of communication failures such as what kind of communication failures occur and with what frequency.

[0106] Note that the above-described embodiment can be appropriately modified and implemented by changing a part of the configuration or function of each of the above-described devices. Therefore, below, some modification examples according to the above-described embodiment will be described as other embodiments.

[0107] Note that below, the points different from the above-described embodiment will be mainly described, and detailed descriptions of the points common to the already described content will be omitted. In addition, the modification examples described below may be implemented individually or in appropriate combinations.

[0108] (Modification Example 1) In the above-described embodiment, the settlement terminal 3 is configured to be separate from the POS terminal 2. In contrast, for the settlement terminal 3 according to this modification example, the housings of both are integrated. Note that the settlement terminal 3 and the electronic money terminal 4 may be integrated.

[0109] (Modification Example 2) In the above-described embodiment, the memory unit 54 is configured to store 20 communication failure histories 542. In contrast, the settlement terminal 3 according to this modification example further includes a setting change unit (not shown) that sets the number of communication failure histories 542 to be stored in accordance with an operation of specifying the number of items, and the memory unit 54 stores the communication failure histories 542 for the number of items set by the setting change unit.

[0110] Specifically, the setting change unit changes the setting information of the number of communication failures to be left as the communication failure history 542 stored in the memory unit 54. As a method of changing the setting information, for example, a selection button for "setting the number of communication failure histories" is provided in the setting 503 of the service selection menu screen 500, and when the operator presses the selection button for "setting the number of communication failure histories", the display control unit 102 displays a number setting screen.

[0111] The setting change unit receives an operation (input of a numerical value) for specifying the number of items from the operator via the number setting screen, and changes the setting information of the number of communication failures to be left as the communication failure history 542 to the number of items received from the operator. The memory unit 54 stores information regarding communication failures for the number of communication failures set in the setting information as the communication failure history 542.

[0112] This makes it possible to change the number of communication failures to be left as the communication failure history 542 in the memory unit 54 according to situations such as when it is sufficient to grasp the tendency of short-term communication failures or when it is necessary to grasp the tendency of long-term communication failures.

[0113] (Modification Example 3) In the above embodiment, the second generation unit 105 is configured to generate print data of a communication failure history in which the generated communication failures are arranged in chronological order. In contrast, the second generation unit 105 of the payment terminal 3 according to this modification example generates print data of a communication failure history in which the generated communication failures are arranged for each communication destination.

[0114] As a result, the operator can grasp the frequency and content of communication failures for each communication destination. That is, it becomes easier for the operator to grasp trends such as whether communication failures occur only for the same communication destination or whether communication failures occur regardless of the communication destination.

[0115] (Modification Example 4) In the above embodiment, the second generation unit 105 is configured to generate print data of a communication failure history in which the communication failures are arranged in chronological order. In contrast, the second generation unit 105 of the payment terminal 3 according to this modification example generates print data of a communication failure history including statistical information on communication failures.

[0116] Specifically, the second generation unit 105 generates print data of a communication failure history including statistical information such as the number of communication failures per unit time (for example, how many per week, per day, per hour, etc.), the number of occurrences of communication failures by content, and the number of communication failures by communication destination.

[0117] As a result, it becomes easier for the operator to grasp the frequency of occurrence of communication failures and the trends of the occurring communication failures.

[0118] (Modification Example 5) In the above embodiment, the print control unit 106 prints the print data of the communication failure history generated by the second generation unit 105. In contrast, the payment terminal 3 according to this modification example includes a writing control unit (not shown) as an "output control unit". The writing control unit writes the output data of the communication failure history generated by the second generation unit 105 to a storage medium such as a USB flash memory or an SD card.

[0119] (Modification Example 6) In the above-described embodiment, the printing control unit 106 prints the print data of the communication failure history generated by the second generation unit 105. In contrast, the settlement terminal 3 according to this modification includes a transmission control unit (not shown) as an "output control unit". The transmission control unit transmits the output data of the communication failure history generated by the second generation unit 105 to a server device such as the maintenance server 6.

[0120] The program executed by the settlement terminal 3 of the above embodiment is provided by being recorded on a computer-readable recording medium such as a CD-ROM, a flexible disk (FD), a CD-R, or a DVD (Digital Versatile Disk) in an installable format or an executable format file.

[0121] Alternatively, the program executed by the settlement terminal 3 of the above embodiment may be configured to be stored on a computer connected to a network such as the Internet and downloaded via the network. Further, the program executed by the settlement terminal 3 may be configured to be provided or distributed via a network such as the Internet.

[0122] Alternatively, the program executed by the settlement terminal 3 of the embodiment may be configured to be provided by being pre-embedded in a ROM or the like.

[0123] Note that the above embodiment is presented as an example and is not intended to limit the scope of the invention. This novel embodiment can be implemented in various other forms, and various omissions, replacements, and changes can be made without departing from the gist of the invention. This embodiment and its modifications are included in the scope and gist of the invention and are included in the invention described in the claims and its equivalent scope.

Explanation of Signs

[0124] 1 Settlement system 2 POS terminal 3 Settlement terminal 4 Electronic money terminal 5 Center Server 6 Maintenance Server 21 Main Body 22 Display Unit for Store Employees 23 Display Unit for Customers 24 Keyboard 25 Printer 26 Receipt Issuing Slot 31 Main Body 32 Display Unit 33 Operation Unit 34 Card Reading Unit 35 Receipt Issuing Slot 36 Power Switch 37 Top Panel 54 Memory Unit 55 Bus Line 56 Controller 57 Printing Unit 100 Control Unit 101 Communication Control Unit 102 Display Control Unit 103 Detection Unit 104 First Generation Unit 105 Second Generation Unit 106 Printing Control Unit 541 Control Program 542 Communication Failure History N Network

Prior Art Documents

Patent Documents

[0125]

Patent Document 1

Claims

1. A communication control unit that performs communication related to a payment process with the server device; A detection unit that detects that a communication failure has occurred during communication with the server device; a first generating unit configured to generate information including a date and time when the communication failure is detected by the detecting unit, information indicating the server device of the communication destination, and a content of the communication failure; an output control unit that outputs the information generated by the first generation unit as a communication failure history; Equipped with the first generation unit generates information including information indicating a process in which a failure has occurred on a communication protocol as the content of the communication failure. Payment device.

2. The computer of the payment device, A communication control unit that performs communication related to a payment process with the server device; A detection unit that detects that a communication failure has occurred during communication with the server device; a first generating unit configured to generate information including a date and time when the communication failure is detected by the detecting unit, information indicating the server device of the communication destination, and a content of the communication failure; an output control unit that outputs the information generated by the first generation unit as a communication failure history; A program that functions as the first generation unit generates information including information indicating a process in which a failure has occurred on a communication protocol as the content of the communication failure. program.

Images