JP2017010491A - Network system, server and control method for network system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To effectively utilize log data transmitted by a control device to a server for a system in which the log data is transmitted from the control device to the server and the server constituting the system.SOLUTION: A POS terminal 13 generates log data D11 including status information data indicating a status of a monitoring item of an object of which status is monitored, transmits the log data D11 generated as a request to a maintenance server 17. When receiving the log data D11, the maintenance server 17 transmits the request corresponding thereto, stores status information data included in the log data D11 received in a first status information database 513, determines classification of the status of the monitoring item on the basis of the status information data included in the log data D11 received, generates status processing information including information indicating the classification, and stores the status processing information in a second status information database 514.SELECTED DRAWING: Figure 2

Description

  The present invention relates to a network system, a server, and a network system control method.

  Conventionally, a network system (remote maintenance system) that transmits log data (monitoring log and abnormal data) to a server (monitoring server) from a control device (client monitoring client) that is a client is known (for example, , See Patent Document 1).

JP 2003-271238 A

In a system that transmits log data from a control device that is a client to a server, such as the network system described above, there is a need to improve the value of the system by effectively using the log data that the control device transmits to the server as much as possible. There is.
The present invention has been made in view of the above-described circumstances, and for a system that transmits log data from a control device to a server and a server that constitutes the system, the log data that the control device transmits to the server is effectively used. With the goal.

To achieve the above object, a network system of the present invention includes a control device that transmits a request, and a server that is connected to the control device via a network and transmits a response in response to reception of the request, The control device generates log data including status information indicating a status of a monitoring item to be monitored, transmits the generated log data to the server as a request, and the server receives the log data A corresponding request is transmitted, the status information included in the received log data is stored in a first database, and the status classification of the monitoring item is classified based on the status information included in the received log data. The status processing information including information indicating the classification and classification is generated and stored in the second database. Characterized in that it pay.
According to the configuration of the present invention, log data transmitted from the control device to the server can be effectively used for a system that transmits log data from the control device to the server.

In the network system of the present invention, the control device includes status identification information for identifying the monitoring item in the status information of the monitoring item, and the server generates the status processing information when generating the status processing information. The monitoring item is identified based on the status identification information included in the item, and the status classification of the monitoring item is determined by a method corresponding to the monitoring item.
According to the configuration of the present invention, the server can classify the state of the monitoring item by a method corresponding to the monitoring item after accurately identifying the monitoring item using the status identification information.

In the network system of the present invention, when the server generates the status processing information, the value of the status identification information included in the status information is information indicating that the status information is a numerical value indicating the state of the monitoring item. In the case of a value indicating the presence, the classification of the state of the monitoring item is determined based on a relationship between a numerical value representing the state of the monitoring item and a predetermined threshold value.
According to the configuration of the present invention, the server can accurately determine the classification of the status of the monitoring item.

Further, in the network system of the present invention, when the server generates the status processing information, the value of the status identification information included in the status information indicates that the status information indicates the state of the monitoring item by a character string. In the case of a value indicating that, the classification of the state of the monitoring item is determined based on the content of a character string representing the state of the monitoring item.
According to the configuration of the present invention, the server can accurately determine the classification of the status of the monitoring item.

In the network system of the present invention, when the status processing information is generated, the server determines the status classification of the monitoring item based on the status identification information value included in the status information. When the value indicates that it is not necessary, the status processing information not including information indicating the classification is stored in the second database.
According to the configuration of the present invention, it is possible to prevent the classification of the status of the monitoring item from being performed when it is not necessary.

In order to achieve the above object, the present invention generates log data including status information indicating the status of a monitoring item whose status is to be monitored, and transmits the generated log data as a request to a control device. When the log data is received, a corresponding request is transmitted, the status information included in the received log data is stored in the first database, and the received log data The status classification of the monitoring item is determined based on the status information included in the status information, status processing information including information indicating the classification is generated, and stored in the second database.
According to the configuration of the present invention, the log data transmitted from the control device to the server can be effectively used for the server constituting the system for transmitting the log data from the control device to the server.

In order to achieve the above object, the present invention provides a network system comprising: a control device that transmits a request; and a server that is connected to the control device via a network and transmits a response in response to reception of the request. In the control method, the control device generates log data including status information indicating a status of a monitoring item to be monitored, and transmits the generated log data to the server as a request. When the log data is received, a corresponding request is transmitted, the status information included in the received log data is stored in the first database, and the status information included in the received log data is Determines the status classification of the monitoring item and generates status processing information including information indicating the classification. And, characterized by storing in the second database.
According to the configuration of the present invention, log data transmitted from the control device to the server can be effectively used for a system that transmits log data from the control device to the server.

The figure which shows the structure of the network system which concerns on this embodiment. The block diagram which shows the functional structure of each apparatus with which a network system is provided. The block diagram of a POS terminal and a maintenance server. The flowchart which shows operation | movement of each apparatus with which a network system is provided. The flowchart which shows operation | movement of a POS terminal. The figure which shows the content of status information data. The figure which shows request data. The flowchart which shows operation | movement of a maintenance server. The flowchart which shows operation | movement of a POS terminal. The flowchart which shows operation | movement of a maintenance server. The figure which shows the record memorize | stored in a 1st status information database and a 2nd status information database. The flowchart which shows operation | movement of a maintenance server. The flowchart which shows operation | movement of a maintenance server. The figure which shows the record memorize | stored in a power supply state monitoring database. The flowchart which shows operation | movement of a maintenance server. The flowchart which shows operation | movement of a maintenance server. The flowchart which shows operation | movement of a POS terminal and a shop management server. The figure which shows the user interface for accounts. The flowchart which shows operation | movement of a POS terminal. The flowchart which shows operation | movement of a POS terminal and a shop management server. The flowchart which shows operation | movement of a POS terminal and a shop management server. The flowchart which shows operation | movement of a POS terminal and a shop management server.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings.

FIG. 1 is a diagram showing a configuration of a network system 1 according to the present embodiment.
As shown in FIG. 1, the network system 1 includes a plurality of store management systems 10 (in FIG. 1, two first store management systems 101 and a second store management system 102).

The store management system 10 is a system used by companies that operate stores such as supermarkets, convenience stores, department stores, and restaurants. In FIG. 1, a first store management system 101 is a system used by the company K1, and a second store management system 102 is a system used by the company K2. The company K1 and the company K2 are other companies that have no partnership relationship, and information is not transmitted and received between the first store management system 101 and the second store management system 102.
In the present embodiment, it is assumed that the store is a facility that sells products. However, the store is not limited to a facility that sells products, and may be a facility where accounting is performed, such as a food and drink or a facility that provides a predetermined service. In the present embodiment, it is assumed that the entity that uses the store management system 10 is a company. However, the entity that uses the store management system 10 is not limited to a company.

  The store management system 10 includes one or a plurality of store systems 11 and a store management server 12. Each store system 11 and the store management server 12 are connected via a global network GN including the Internet. Connected to communicate.

The store system 11 is a system provided for each store, and has a function of performing accounting as described later and a function of issuing a receipt in accordance with the accounting.
A store to which the store system 11 is applied is provided with a cashier counter L for a customer to pay for. Each checkout counter L is provided with a POS terminal 13 (control device) or a printing device 14 (external device) that can issue a receipt according to a transaction. Receipts issued by the POS terminal 13 and the printing device 14 are delivered to the customer by the cashier.
The configurations, functions, and processing based on the functions of the POS terminal 13 and the printing apparatus 14 will be described later.

The store system 11 includes a local network LN.
The POS terminal 13 and the printing apparatus 14 are connected to the local network LN according to a communication standard related to the LAN. Any communication standard may be used when the POS terminal 13 and the printing apparatus 14 are connected to the local network LN, and may be wired connection or wireless connection.
A communication device 15 is connected to the local network LN. The communication device 15 is an interface device that connects the local network LN and the global network GN. The communication device 15 has a function as a modem (or ONU (Optical Network Unit)), a router function, a NAT (Network Address Translation) function, a DHCP (Dynamic Host Configuration Protocol) server function, and the like. The communication device 15 transfers data transmitted / received between devices during communication performed between a device connected to the local network LN and a device connected to the global network GN. In FIG. 1, the communication device 15 is represented by one block, but the communication device 15 may have a plurality of devices corresponding to functions.

The POS terminal 13 and the printing apparatus 14 can communicate with each other via the local network LN.
The POS terminal 13 can access the global network GN via the communication device 15 of the local network LN, and can communicate with devices connected to the global network GN.
The printing apparatus 14 does not have a function of accessing the global network GN.

In the store system 11, a POS unit 16 is configured by one POS terminal 13 and zero or more (0, 1 or 2 or more) printing apparatuses 14. In the present embodiment, for convenience of explanation, it is assumed that the POS unit 16 includes one or a plurality of printing apparatuses 14.
As will be described later, in one POS unit 16, one POS terminal 13 of the one POS unit 16 controls one or a plurality of printing apparatuses 14 of the one POS unit 16.

The store management server 12 is a cloud server of a cloud system using the POS terminal 13 and other devices as clients.
The configuration, function, and processing based on the function of the store management server 12 will be described later.

As shown in FIG. 1, a maintenance server 17 (server) is connected to the global network GN. The maintenance server 17 is a cloud server of a cloud system using the POS terminal 13 and other devices as clients.
The configuration, function, and processing based on the function of the maintenance server 17 will be described later.

  In FIG. 1, the store management server 12 and the maintenance server 17 are each represented by one block. This is because the store management server 12 and the maintenance server 17 are each represented by a single server device. It does not mean that it is composed. For example, the store management server 12 or the maintenance server 17 may be configured to include a plurality of server devices.

  FIG. 2 is a block diagram showing functional configurations of the POS terminal 13, the printing device 14, the store management server 12, and the maintenance server 17 included in the network system 1.

The POS terminal 13 is a line thermal printer that accommodates roll paper (recording medium) and prints an image by forming dots on the roll paper with a line-type thermal head.
As shown in FIG. 2, the POS terminal 13 includes a control device control unit 20, a control device printing unit 21, a control device storage unit 22, a control device communication unit 23 (communication unit), and a control device device communication unit 24. And comprising.

  The control device control unit 20 includes a CPU, ROM, RAM, and other peripheral circuits (not shown), and controls the POS terminal 13.

The control device control unit 20 includes a process control unit 201, a client function unit 202, a log collection unit 203, a communication management unit 204, and an instruction execution unit 205.
The processing control unit 201 is a functional block that executes processing based on firmware installed in the POS terminal 13 and other accompanying programs.
The client function unit 202 is a functional block that executes processing based on a web browser installed in the POS terminal 13 and other accompanying programs.
The log collection unit 203, the communication management unit 204, and the command execution unit 205 are functional blocks that execute processing based on corresponding predetermined software installed in the POS terminal 13 and other accompanying programs.

  The control device printing unit 21 includes a print head 211 and a cutter 212 in addition to a transport mechanism (not shown) that transports roll paper accommodated in the casing of the POS terminal 13.

  The transport mechanism includes a platen roller provided at a position facing the print head 211. The roll paper is sandwiched between the print head 211 and the platen roller, the platen roller is rotated in a predetermined direction, and the roll paper is moved in the transport direction. Transport.

The print head 211 is a thermal head in which a plurality of heating elements corresponding to the resolution are arranged in a direction crossing the roll paper conveyance direction, and heat is generated from the heating elements to form dots on the roll paper, which is thermal paper. To do.
The controller printing unit 21 alternately repeats the formation of dots for one line (rows of heating elements extending in the direction intersecting the conveyance direction) by the print head 211 and the conveyance of roll paper for one line by the conveyance mechanism. Print the image.

The cutter 212 includes a fixed blade and a movable blade, and cuts the roll paper by moving the movable blade relative to the fixed blade to cross the fixed blade and the movable blade.
The control device printing unit 21 controls the control device control unit 20 to print an image related to the receipt on the roll paper by the print head 211 while the roll paper is being transported by the transport mechanism, and the roll paper at a predetermined position by the cutter 212. And issue a receipt.

The control device storage unit 22 includes a nonvolatile memory and stores various data.
The control device storage unit 22 includes an SSD (solid state drive), and can store various data in an SSD flash memory (hereinafter simply referred to as “SSD”).
The control device storage unit 22 stores a generation interval setting file 221, a transmission interval setting file 222, and a log file 223. These data will be described later.

The control device communication unit 23 accesses the local network LN and communicates with devices (including other POS terminals 13 and the printing device 14) connected to the local network LN under the control of the control device control unit 20. .
Also, the control device communication unit 23 accesses the global network GN via the communication device 15 of the local network LN and communicates with devices connected to the global network GN under the control of the control device control unit 20.

  The control device device communication unit 24 includes an interface board having a port conforming to the USB standard, a port conforming to a serial communication standard other than USB, and a port conforming to another communication standard. The control device device communication unit 24 communicates with a device connected to the port under the control of the control device control unit 20. The controller device communication unit 24 may have a wireless communication function and wirelessly communicate with the device.

  In the example of FIG. 2, a barcode scanner BS, a customer display CD, a cash drawer KS, and a touch panel TP are connected to the POS terminal 13 as devices.

The barcode scanner BS reads a barcode attached to a product or product packaging, and outputs data indicating the read result to the control device communication unit 24. The control device device communication unit 24 outputs the data input from the barcode scanner BS to the control device control unit 20.
The customer display CD is a display device such as a liquid crystal display, and displays an image under the control of the control device control unit 20. The information displayed on the customer display CD can be visually recognized by the customer who makes a payment at the cashier counter L.
The cash drawer KS includes a tray that stores cash, a mechanism that locks the tray, a mechanism that pulls out the tray, and the like, and is unlocked and pulled out under the control of the control device controller 20.
The touch panel TP includes a display panel such as a liquid crystal display panel or an organic EL panel, and a touch sensor that is provided over the display device and detects a touch operation of a user (including a cashier person). The touch panel TP is provided at a position where the cashier person can visually recognize the touch panel TP and can perform a touch operation. The touch panel TP displays an image on the display panel under the control of the control device control unit 20. The client function unit 202 of the control device control unit 20 can display a web page on the touch panel TP based on the HTML file acquired by a predetermined means. In addition, when the touch operation of the user is detected, the touch panel TP outputs a signal indicating a position where the touch operation is performed to the control device control unit 20. The control device control unit 20 executes processing corresponding to the user's touch operation based on the input from the touch panel TP.

The printing device 14 is a line thermal printer that stores roll paper and prints an image by forming dots on the roll paper with a line-type thermal head.
As illustrated in FIG. 2, the printing apparatus 14 includes a printing apparatus control unit 30, a printing apparatus printing unit 31, a printing apparatus storage unit 32, a printing apparatus communication unit 33, and a printing apparatus device communication unit 34. .

The printing apparatus control unit 30 includes a CPU, a ROM, a RAM, and other peripheral circuits (not shown), and controls the printing apparatus 14.
The printing apparatus printing unit 31 includes a print head and a cutter in addition to a conveyance mechanism (not shown) that conveys roll paper accommodated in the casing of the printing apparatus 14. The printing device storage unit 32 includes a nonvolatile memory such as an EPROM and stores various data.
The printing device communication unit 33 accesses the local network LN and communicates with devices (including the POS terminal 13 and other printing devices 14) connected to the local network LN under the control of the printing device control unit 30. .
The printing device device communication unit 34 includes an interface board having a port conforming to the USB standard, a port conforming to a serial communication standard other than USB, and a port conforming to another communication standard. The printing device device communication unit 34 communicates with a device connected to the port under the control of the printing device control unit 30. The printing apparatus device communication unit 34 may have a wireless communication function and wirelessly communicate with the device. In the example of FIG. 2, a barcode scanner BS, a customer display CD, a cash drawer KS, and a touch panel TP are connected to the printing apparatus 14 as devices.

  As illustrated in FIG. 2, the store management server 12 includes a store management server control unit 40, a store management server storage unit 41, and a store management server communication unit 42.

The store management server control unit 40 includes a CPU (not shown), ROM, RAM, and other peripheral circuits, and controls the store management server 12.
The store management server control unit 40 includes an accounting related process execution unit 401.
The accounting-related processing execution unit 401 is a functional block that executes processing based on a predetermined web application that operates with server software installed in the store management server 12 and other accompanying programs.

The store management server storage unit 41 includes a hard disk (not shown) and a nonvolatile memory such as an EEPROM, and stores various data.
The store management server storage unit 41 stores a product master 411. The merchandise master 411 stores the merchandise code of the merchandise, the unit price of the merchandise, and information related to other merchandise in association with each other for the merchandise sold at the store.
The store management server storage unit 41 stores a transaction information management database 412. The accounting information management database 412 will be described later.

  As shown in FIG. 2, the maintenance server 17 includes a maintenance server control unit 50 (server control unit), a maintenance server storage unit 51 (server storage unit), and a maintenance server communication unit 52.

  The maintenance server control unit 50 includes a CPU (not shown), ROM, RAM, and other peripheral circuits, and controls the maintenance server 17.

The maintenance server control unit 50 includes a log reception unit 501, a response response unit 502, a log information storage unit 503, a log information display unit 504, and a monitoring unit 505.
The log receiving unit 501, the response response unit 502, the log information storage unit 503, the log information display unit 504, and the monitoring unit 505 are each a predetermined web application that operates with server software installed in the maintenance server 17, and other associated items. This is a functional block that executes processing based on a program to be executed.

The maintenance server storage unit 51 includes a hard disk (not shown) and a nonvolatile memory such as an EEPROM, and stores various data.
The maintenance server storage unit 51 stores an instruction storage database 511, a contract management database 512, a first status information database 513, a second status information database 514, and a power supply state monitoring database 515. These data will be described later.

  The maintenance server communication unit 52 accesses the global network GN and communicates with devices (including the POS terminal 13) connected to the network under the control of the maintenance server control unit 50.

As described above, the network system 1 includes the maintenance server 17.
The maintenance server 17 manages the states of the POS terminal 13 and the printing apparatus 14 included in the store system 11 of the store management system 10 based on a prior contract with the company regardless of the company using the store management system 10. In the present embodiment, the company K1 and the company K2 have previously concluded a contract relating to the management of the state of the POS terminal 13 and the printing apparatus 14 by the maintenance server 17, and the maintenance server 17 includes the first store management system 101. For each of the store system 11 and the store system 11 of the second store management system 102, the state of the POS terminal 13 and the printing device 14 included in each store system 11 is comprehensively managed.
Furthermore, the maintenance server 17 is for maintenance of the POS terminal 13 and the printing apparatus 14 for a person in charge of maintenance of the POS terminal 13 and the printing apparatus 14 of the store system 11 (hereinafter referred to as “maintenance person”). To provide useful information.
Hereinafter, the operation of the maintenance server 17 when managing the states of the POS terminal 13 and the printing apparatus 14 will be described.

FIG. 3 shows the functional blocks provided in the control device control unit 20 of the POS terminal 13 together with the data stored in the control device storage unit 22, and the functional blocks provided in the maintenance server control unit 50 of the maintenance server 17 It is a figure represented with the data to memorize | store.
Hereinafter, first, a basic flow of data transmitted and received between functional blocks when the maintenance server 17 manages the states of the POS terminal 13 and the printing apparatus 14 will be described with reference to FIG. In the description using FIG. 3, the details of the processing of the functional blocks and the details of the contents of data transmitted / received between the functional blocks are omitted.

As illustrated in FIG. 3, the log collection unit 203 of the POS terminal 13 refers to the generation interval setting file 221 and generates request data D1 at an interval indicated by the generation interval setting file 221.
The request data D1 is data including log data D11 and processing result notification data D12.
The log collection unit 203 outputs the generated request data D1 to the communication management unit 204 (arrow Y1 in FIG. 3).

The communication management unit 204 refers to the transmission interval setting file 222 and transmits the request data D1 input from the log collection unit 203 to the maintenance server 17 at an interval indicated by the transmission interval setting file 222 (arrow Y2 in FIG. 3). .
The request data D1 that the communication management unit 204 transmits to the maintenance server 17 at intervals corresponds to a request transmitted from the POS terminal 13 that is a client to the maintenance server 17 that is a server. The maintenance server 17 can transmit data to the POS terminal 13 as a response in response to reception of the request data D1 that is a request.

  The log receiving unit 501 of the maintenance server 17 receives the request data D1 transmitted from the POS terminal 13. The log receiving unit 501 outputs the received request data D1 to the response response unit 502 (arrow Y3 in FIG. 3).

The response response unit 502 refers to the instruction storage database 511 based on the log data D11 input from the log reception unit 501, and generates response data D2 as a response corresponding to the request data D1 (request).
As will be described later, the response data D2 includes processing command control data D21 (control data) for causing the POS terminal 13 to execute predetermined processing, and a predetermined monitoring item (described later) in an error warning state (described later) or an error. Error warning / prediction notification data D22 indicating a predictive state (described later) is included.
The response response unit 502 transmits the generated response data D2 to the POS terminal 13 (arrow Y5 in FIG. 3).
Also, the response response unit 502 outputs the request data D1 to the log information storage unit 503 (arrow Y4 in FIG. 3).

  Further, the log information storage unit 503 stores a record in the first status information database 513 (described later) based on the request data D1 input from the response response unit 502, and records in the second status information database 514 (described later). Remember.

The communication management unit 204 of the POS terminal 13 receives the response data D2 transmitted from the maintenance server 17.
The communication management unit 204 outputs the error warning / prediction notification data D22 included in the received response data D2 to the log collection unit 203 (arrow Y6 in FIG. 3).
Further, the communication management unit 204 outputs the processing command control data D21 included in the received response data D2 to the command execution unit 205 (arrow Y7 in FIG. 3).

  The command execution unit 205 executes predetermined processing based on the processing command control data D21 input from the communication management unit 204. The instruction execution unit 205 generates processing result data D3 indicating the processing result of the executed predetermined processing. The instruction execution unit 205 outputs the generated processing result data D3 to the log collection unit 203 (arrow Y8 in FIG. 3).

The log collection unit 203 changes the contents of the generation interval setting file 221 as necessary based on the error warning / prediction notification data D22 input from the communication management unit 204 and the generated log data D11.
Further, the log collection unit 203 generates processing result notification data D12 based on the processing result data D3 input from the instruction execution unit 205.

  Thereafter, the log collection unit 203 refers to the generation interval setting file 221 to generate request data D1 at an interval indicated by the generation interval setting file 221 and outputs the request data D1 to the communication management unit 204.

  As described above, the POS terminal 13 transmits the request data D1 (log data D11) at an interval to the maintenance server 17, executes processing based on the request data D1 received by the maintenance server 17, and response data D2 as a response. Is transmitted and received, and data is transmitted and received between the POS terminal 13 and the maintenance server 17 in a cycle in which processing based on the response data D2 received by the POS terminal 13 is executed.

Next, the operation of the maintenance server 17 when managing the states of the POS terminal 13 and the printing apparatus 14 will be described in detail.
FIG. 4 is a flowchart showing the operations of the POS terminal 13 and the maintenance server 17.
4A shows the operation of the log collection unit 203 of the POS terminal 13, FIG. 4B shows the operation of the communication management unit 204 of the POS terminal 13, and FIG. 4C shows the operation of the instruction execution unit 205 of the POS terminal 13. (D) shows the operation of the log receiving unit 501 of the maintenance server 17, (E) shows the operation of the response response unit 502 of the maintenance server 17, and (F) shows the log information storage unit 503 of the maintenance server 17. Shows the operation.

As shown in FIG. 4A, the log collection unit 203 refers to the generation interval setting file 221 and monitors whether the timing for generating the request data D1 has arrived (step SA1).
The generation interval setting file 221 is a file in which information indicating an interval for generating the request data D1 is recorded. In step SA1, the log collection unit 203 refers to the generation interval setting file 221, and after generating the request data D1 last time, when the interval indicated by the generation interval setting file 221 has elapsed, the timing of generating the request data D1 is determined. It is determined that it has arrived.

  As will be described later, the interval indicated by the information recorded in the generation interval setting file 221 is shorter than the reference generation interval, with a predetermined interval (hereinafter referred to as “reference generation interval”) as the longest interval. There is.

When it is time to generate the request data D1 (step SA1: YES), the log collection unit 203 generates processing result notification data D12 based on the processing result data D3 stored in a predetermined storage area (step S1). SA2).
The processing result notification data D12 is text data (for example, data in XML (Extensible Markup Language) format) that can be described by hierarchizing information, and is data that can be transmitted to the maintenance server 17 as a request.
After generating the processing result notification data D12, the log collection unit 203 deletes the processing result data D3 used for generating the processing result notification data D12 from a predetermined storage area.
As will be apparent later, the log collection unit 203 generates the request data D1 before the processing that is input from the instruction execution unit 205 until it is determined in step SA1 that the timing for generating the request data D1 has arrived. The result data D3 is stored in a predetermined storage area.

  Next, the log collection unit 203 executes log data generation processing (step SA3). The log data generation process is a process for generating log data D11. Hereinafter, the log data generation process will be described in detail.

FIG. 5 is a flowchart showing in detail the operation of the log collection unit 203 when the log data generation process is executed.
As shown in FIG. 5, the log collection unit 203 refers to the log file 223 stored in the control device storage unit 22 (step SG1).
The log file 223 is a file in which logs of a plurality of monitoring items are recorded. The monitoring item is an item that is determined in advance as a target for monitoring a state and collecting a log. In this embodiment, monitoring items: monitoring item: communication error, monitoring item: printer error, monitoring item: RAM usage rate, monitoring item: CPU usage rate, monitoring item: CPU temperature, monitoring item: data transfer rate, monitoring item : SSD usage record value, monitoring item: print head formation line cumulative number, monitoring item: cumulative cutter usage number, monitoring item: operation process, and monitoring item: connected device. Note that the monitoring items described in the present embodiment are examples, and other monitoring items may exist in addition to the exemplified monitoring items or instead of at least a part of the exemplified monitoring items.

Monitoring item: As a communication error log, the log file 223 includes information indicating that a communication error has occurred and information indicating that the generated communication error has been resolved together with information indicating the date and time (date + time). , Recorded in time series. A communication error refers to a state in which normal communication cannot be performed, such as an overflow of a reception buffer that temporarily stores received data.
The processing control unit 201 monitors whether or not a communication error has occurred and whether or not the communication error has been resolved (monitoring item: monitoring the state of the communication error), and the monitoring item: communication error is recorded in the log file 223. Record the log.

Monitoring item: As a log of printer errors, the log file 223 records information indicating that a printer error has occurred and information indicating that the generated printer error has been resolved in chronological order together with information indicating the date and time. Is done. A printer error refers to a state where printing cannot be performed normally, such as running out of roll paper or jammed roll paper.
The processing control unit 201 monitors whether or not a printer error has occurred and whether or not the printer error has been resolved (monitoring item: monitoring the status of the printer error), and the monitoring item: printer error in the log file 223. Record the log.

As a log of the monitoring item: RAM usage rate, information indicating the RAM usage rate (hereinafter referred to as “RAM usage rate”) is recorded in the log file 223 in time series together with information indicating the date and time.
The processing control unit 201 acquires the RAM usage rate at a predetermined interval (monitoring item: monitoring the status of the RAM usage rate) by a predetermined means, and records a log of the monitoring item: RAM usage rate in the log file 223. .

As a monitoring item: CPU usage rate log, information indicating the CPU usage rate (hereinafter referred to as “CPU usage rate”) is recorded in the log file 223 along with information indicating the date and time.
The process control unit 201 acquires the CPU usage rate at a predetermined interval (monitors the status of the monitoring item: CPU usage rate), and records the log of the monitoring item: CPU usage rate in the log file 223.

As a monitoring item: CPU temperature log, information indicating the temperature of the CPU (hereinafter referred to as “CPU temperature”) is recorded in time series in the log file 223 together with information indicating the date and time.
The process control unit 201 acquires the CPU temperature at predetermined intervals by a predetermined means (monitoring item: monitoring the state of the CPU temperature), and records a log of the monitoring item: CPU temperature in the log file 223.

As a log of monitoring item: data transfer rate, information indicating the data transfer rate is recorded in the log file 223 in time series together with information indicating the date and time. The data transfer rate is the amount of data per unit time that can be transmitted via the global network GN.
The processing control unit 201 acquires the data transfer rate by a predetermined means at a predetermined interval (monitors the status of the monitoring item data transfer rate), and records a log of the monitoring item: data transfer rate in the log file 223.

Monitoring item: As a log of actual SSD usage values, the log file 223 includes the cumulative number of writes to the SSD, the average value of the amount of data written to the SSD per unit time, and the life of other SSDs. Information indicating a value necessary for calculation (hereinafter, a value necessary for calculating the life of the SSD is referred to as “SSD actual use value”) is recorded in time series together with information indicating the date and time.
The process control unit 201 acquires the SSD usage record value at a predetermined interval (monitoring item: monitoring the status of the use record value), and records the log of the monitoring item: SSD use record value in the log file 223.

Monitoring item: As a log of the total number of print head formation lines, information indicating the total number of print head formation lines is recorded in time series in the log file 223 together with information indicating the date and time.
The cumulative number of print head formation lines is the cumulative number of lines formed by the print head 211. As described above, the control device printing unit 21 of the POS terminal 13 according to this embodiment alternately repeats the formation of dots for one line by the print head 211 and the conveyance of roll paper for one line by the conveyance mechanism. Go to print the image. As described above, the formation of a line means that a dot for one line is formed by the print head 211.
The processing control unit 201 acquires the print head line cumulative number at a predetermined interval (monitoring item: monitors the print head forming line cumulative number), and records a log of the monitoring item: print head forming line cumulative number in the log file 223. To do.

Monitoring item: As a log of the cumulative number of cutters used, information indicating the cumulative number of cutters used is recorded in the log file 223 in time series together with information indicating the date and time.
The cumulative number of cutters used is the cumulative number of roll paper cuts performed by the cutter 212.
The processing control unit 201 acquires the cumulative number of cutters used at a predetermined interval (monitoring item: monitors the cumulative number of cutters used), and records a log of the monitoring item: cumulative number of cutters used in the log file 223.

Monitoring item: As a log of an operation process, in the log file 223, a character string indicating the name of a process in an operation state (= a state in which a CPU is assigned) is recorded in time series together with information indicating date and time. The
The process control unit 201 acquires a process in an operation state at a predetermined interval, and records a log of monitoring item: operation process in the log file 223.

As a monitoring item: connected device log, a character string indicating the type of device in the connected state is recorded in the log file 223 in time series together with information indicating the date and time.
The connected device is a device connected by wire or wirelessly and means a device that can communicate normally.
The process control unit 201 acquires the type of the connected device at a predetermined interval, and records the monitoring item: connected device log in the log file 223.

The log file 223 records at least the line formation time recording medium attribute information and the disconnection time recording medium attribute information in addition to the monitoring item log described above.
The recording medium attribute information at the time of line formation includes information indicating a combination of the quality, type, and thickness (hereinafter referred to as “recording medium attribute”) of the roll paper accommodated in the POS terminal 13 in the past, and the respective recordings. This is a value associated with information indicating the cumulative number of lines formed on roll paper having a medium attribute.
For example, in the past, a roll paper having a recording medium attribute z1 associated with a combination of paper quality kx1, type sx1, and thickness ax1, and a roll having a recording medium attribute z2 associated with a combination of paper quality kx2, type sx2, and thickness sx2. Assume that paper has been accommodated in the POS terminal 13. Further, the cumulative number of print head formation lines is “100”, the cumulative number of lines formed on the roll paper with the recording medium attribute z1 is “30”, and the cumulative number of lines formed on the roll paper with the recording medium attribute z2. Is “70”. In this case, the recording medium attribute information at the time of line formation is information in which information indicating the recording medium attribute z1 is associated with information indicating “30” that is the cumulative number of lines formed on the roll paper having the recording medium attribute z1. The information indicating the recording medium attribute z2 is associated with information indicating “70”, which is the cumulative number of lines formed on the roll paper having the recording medium attribute z2.

The recording medium attribute information at the time of cutting includes information indicating the recording medium attribute of the roll paper accommodated in the POS terminal 13 in the past, and the cumulative number of cuttings performed by the cutter 212 on the roll paper of each recording medium attribute. It is a value associated with information indicating the number.
For example, it is assumed that the roll paper having the recording medium attribute z1 and the roll paper having the recording medium attribute z2 have been accommodated in the POS terminal 13 in the past. Further, the cumulative number of cutters used is “100”, the cumulative number of cuts made by the cutter 212 with respect to the roll paper having the recording medium attribute z1 is “30”, and the cutter is used with respect to the roll paper having the recording medium attribute z2. Assume that the cumulative number of cuts made in 212 is “70”. In this case, the recording medium attribute information at the time of cutting is information in which information indicating the recording medium attribute z1 is associated with information indicating “30” that is the cumulative number of lines formed on the roll paper of the recording medium attribute z1; , Information indicating the recording medium attribute z2 and information indicating “70” that is the cumulative number of lines formed on the roll paper having the recording medium attribute z2.

  The processing control unit 201 manages the recording medium attribute of the roll paper stored in the POS terminal 13 based on an input from a predetermined sensor or a user input by a predetermined means, and based on the managed recording medium attribute The recording medium attribute information at the time of line formation and the recording medium attribute information at the time of cutting are recorded in the log file 223 as appropriate.

  As illustrated in FIG. 5, the log collection unit 203 acquires the log of each monitoring item, the line formation recording medium attribute information, and the cutting recording medium attribute information based on the log file 223 referred to in step SG1. (Step SG2).

  Next, the log collection unit 203 generates status information data (status information) for each monitoring item (step SG3). Hereinafter, the status information data of each monitoring item will be described in detail.

FIG. 6 is a diagram schematically showing the contents of status information data of each monitoring item.
As will be described later, the status information data includes status identification information that is identification information for identifying the status information data.

FIG. 6A shows the contents of monitoring item: communication error status information data (hereinafter referred to as “communication error status information data”).
As shown in FIG. 6A, the communication error status information data includes status identification information for identifying communication error status information data (hereinafter referred to as “communication error status identification information”).
The communication error status information data includes communication error status information. The communication error status information includes information indicating a communication error that has occurred at the present time (time corresponding to the timing for generating the request data D1) and information indicating the date and time when the communication error occurred.
In step SG3, the log collection unit 203 generates communication error status information based on the monitoring item: communication error log, and associates the communication error status identification information with the communication error status information to generate communication error status information data. Generate.
Note that the log collection unit 203 does not have a communication error at the present time (when a communication error that has occurred in the past has been resolved and no new communication error has occurred), a communication error status. Does not generate information data.

FIG. 6B is a diagram showing the contents of monitoring item: printer error status information data (hereinafter referred to as “printer error status information data”).
As shown in FIG. 6B, the printer error status information data includes status identification information for identifying printer error status information data (hereinafter referred to as “printer error status identification information”).
The printer error status information data includes printer error status information. The printer error status information includes information indicating a printer error that has occurred at the present time (time corresponding to the timing of generating the request data D1) and information indicating the date and time when the printer error occurred.
In step SG3, the log collection unit 203 generates printer error status information based on the monitoring item: printer error log, and associates the printer error status identification information with the printer error status information to obtain printer error status information data. Generate.
Note that the log collection unit 203 determines that the printer error status is not in a state where a printer error has occurred (when a printer error that has occurred in the past has been resolved and no new printer error has occurred). Does not generate information data.

FIG. 6C is a diagram showing the contents of monitoring item: RAM usage rate status information data (hereinafter referred to as “RAM usage rate status information data”).
As shown in FIG. 6C, the RAM usage rate status information data includes status identification information for identifying the RAM usage rate status information data (hereinafter referred to as “RAM usage rate status identification information”).
The RAM usage rate status information data includes RAM usage rate state information. The RAM usage rate state information includes information indicating the RAM usage rate at the present time (time corresponding to the timing of generating the request data D1) and information indicating the date and time when the RAM usage rate is measured.
In step SG3, the log collection unit 203 generates RAM usage status information based on the log of the monitoring item: RAM usage, and associates the RAM usage status identification information with the RAM usage status information to use the RAM. Generate rate status information data.

FIG. 6D is a diagram showing the contents of monitoring item: status information data of CPU usage rate (hereinafter referred to as “CPU usage rate status information data”).
As shown in FIG. 6D, the CPU usage rate status information data includes status identification information for identifying the CPU usage rate status information data (hereinafter referred to as “CPU usage rate status identification information”).
The CPU usage rate status information data includes CPU usage rate state information. The CPU usage rate state information includes information indicating the CPU usage rate at the present time (the time corresponding to the timing of generating the request data D1) and information indicating the date and time when the CPU usage rate is measured.
In step SG3, the log collection unit 203 generates CPU usage rate status information based on the log of the monitoring item: CPU usage rate, and associates the CPU usage rate status identification information with the CPU usage rate status information to use the CPU. Generate rate status information data.

FIG. 6E is a diagram showing the contents of monitoring item: CPU temperature status information data (hereinafter referred to as “CPU temperature status information data”).
As shown in FIG. 6E, the CPU temperature status information data includes status identification information for identifying CPU temperature status information data (hereinafter referred to as “CPU temperature status identification information”).
The CPU temperature status information data includes CPU temperature state information. The CPU temperature state information includes information indicating the CPU temperature at the present time (the time corresponding to the timing for generating the request data D1) and information indicating the date and time when the CPU temperature is measured.
In step SG3, the log collection unit 203 generates CPU temperature status information based on the log of the monitoring item: CPU temperature, and associates the CPU temperature status identification information with the CPU temperature status information to obtain the CPU temperature status information data. Generate.

FIG. 6F is a diagram showing the contents of monitoring item: data transfer rate status information data (hereinafter referred to as “data transfer rate status information data”).
As shown in FIG. 6F, the data transfer rate status information data includes status identification information for identifying the data transfer rate status information data (hereinafter referred to as “data transfer rate status identification information”).
The data transfer rate status information data includes data transfer rate state information. The data transfer rate state information includes information indicating the data transfer rate at the present time (a time corresponding to the timing for generating the request data D1) and information indicating the date and time when the data transfer rate is measured.
In step SG3, the log collection unit 203 generates data transfer rate state information based on the log of the monitoring item: data transfer rate, associates the data transfer rate status identification information with the data transfer rate state information, and transfers the data. Generate speed status information data.

FIG. 6G is a diagram showing the contents of monitoring item: status information data of SSD usage record value (hereinafter referred to as “SSD use record value status information data”).
As shown in FIG. 6G, the SSD usage record value status information data includes status identification information for identifying the SSD use record value status information data (hereinafter referred to as “SSD use record value status identification information”).
The SSD usage record value status information data includes SSD use record value status information and SSD life information.
The SSD usage record value status information includes information indicating the SSD use record value (such as the cumulative number of times written to the SSD) at the present time (the time corresponding to the timing for generating the request data D1) and the date and time when the SSD use record value was acquired. Information.
In step SG3, the log collection unit 203 generates SSD use result value state information based on the log of the monitoring item: SSD use result value.
The SSD life information is information indicating the life of the SSD.
In step SG3, the log collection unit 203 calculates the SSD lifetime by a predetermined method based on the SSD usage record value, and generates SSD lifetime information.
In step SG3, the log collection unit 203 associates the SSD usage record value status identification information, the SSD use record value status information, and the SSD life information to generate SSD use record value status information data.

FIG. 6H is a diagram showing the contents of status information data (hereinafter referred to as “print head formation line cumulative number status information data”) of the monitoring item: print head formation line cumulative number.
As shown in FIG. 6H, the print head formation line cumulative number status information data includes status identification information for identifying the print head formation line cumulative number status information data (hereinafter, “print head formation line cumulative number status identification information”). Is provided.)
The print head formation line cumulative number status information data includes print head formation line cumulative number state information and print head remaining use days information.
The print head formation line cumulative number state information includes information indicating the print head formation line cumulative number at the present time (the time corresponding to the timing of generating the request data D1), and information indicating the date and time when the print head formation line cumulative number is acquired. including.
In step SG3, the log collection unit 203 generates print head formation line total number state information based on a log of monitoring item: print head formation line total number.

The remaining print head use days information is information indicating the remaining days that the print head 211 can be used (hereinafter referred to as “print head remaining use days”).
In step SG3, the log collection unit 203 calculates the remaining print head usage days using the following equation (1).

  IH = (IUseLimit−IUse (N)) ÷ [(IUse (N) −IUse (0)) ÷ N] (1).

  In Expression (1), “IH” represents the number of days that the print head remains used. “IUseLimit” represents an upper limit value of lines that can be formed by the print head 211 (upper limit value of the number of times the print head 211 is used). “IUse (N)” represents the total number of lines formed by the print head 211 from the first day to the Nth day, with the day when the POS terminal 13 is installed in the store as the first day. IUse (0) represents the cumulative number of lines formed by the print head 211 before the date when the POS terminal 13 was installed in the store. For reasons such as printing for testing, printing may be performed by the POS terminal 13 before being installed in the store.

In the formula (1), the part of “(IUseLimit−IUse (N))” on the right side represents the number of remaining lines that can be formed by the print head 211.
Further, in the formula (1), the part of “[(IUse (N) −IUse (0)) ÷ N]” on the right side is set up in one day by the print head 211 after being installed in the POS terminal 13 store. Represents the average number of lines.
Then, by dividing the number of remaining lines that can be formed by the print head 211 by the average value of the number of lines that the POS terminal 13 forms in one day, printing in a case where the POS terminal 13 is continuously used. The remaining head usage days can be calculated.

  Here, in calculating the remaining print head usage days using Expression (1), the log collection unit 203 calculates values of N, IUse (N), and IUse (0) based on the log file 223. . In the log file 223, the process control unit 201 records the values of these variables (may be values necessary for calculating these variables).

Further, the log collection unit 203 calculates the value of IUseLimit based on the line formation recording medium attribute information recorded in the log file 223 by the following method.
That is, the log collection unit 203 multiplies IUseLimit by multiplying a predetermined initial value of IUseLimit by a coefficient set for each recording medium attribute of the roll paper accommodated in the POS terminal 13 in the past. calculate. In calculating IUseLimit, the log collection unit 203 takes the coefficient of each recording medium attribute as a value reflecting a weight corresponding to the cumulative number of lines formed on the roll paper having the recording medium attribute.
Here, the recording medium attribute is information indicating a combination of the quality, type, and thickness of the roll paper. The progress of deterioration when a line is formed by the print head 211 differs depending on the combination of the paper quality, type, and thickness of the roll paper. Based on this, the coefficient set to one recording medium attribute increases as the progress of deterioration of the print head 211 when a line is formed on roll paper having the one recording medium attribute increases. The value is set based on the result of a prior test or simulation so that the value decreases as the progress of deterioration of the print head 211 decreases.

By using the IUseLimit calculated by the above method and calculating the remaining print head remaining days of the print head 211 by the method of Expression (1), the degree of progress of deterioration of the print head 211 forms a line. Based on the characteristic that it varies depending on the paper quality, type, or thickness of the roll paper, it is possible to appropriately calculate the remaining days of use of the print head by reflecting the characteristic.
In this embodiment, the remaining print head usage days are calculated by reflecting the paper quality, type, and thickness of the roll paper (recording medium) accommodated in the past, or the paper quality, type, and thickness are calculated. If the calculation is performed by reflecting at least one of them, the above-described effects can be obtained. The same applies to the remaining cutter use days described later.

In step SG3, the log collection unit 203 calculates print head remaining use days information by the above-described method based on the line formation recording medium attribute information, and indicates the calculated print head remaining use days. Generate information.
In step SG3, the log collection unit 203 associates the print head formation line cumulative number status identification information, the print head formation line cumulative number state information, and the print head remaining use day information with the print head formation line cumulative number status. Generate information data.

FIG. 6I is a diagram showing the contents of status information data (hereinafter referred to as “cutter use cumulative number status information data”) of monitoring item: cumulative cutter use number.
As shown in FIG. 6I, the cumulative cutter usage count status information data includes status identification information (hereinafter referred to as “cumulative cutter usage cumulative status identification information”) for identifying the cumulative cutter usage status information data.
The cumulative cutter usage number status information data includes cumulative cutter usage number status information and remaining cutter usage day information.
The cumulative cutter usage count state information includes information indicating the cumulative cutter usage count at the present time (the time corresponding to the timing of generating the request data D1) and information indicating the date and time when the cumulative cutter usage count is acquired.
In step SG3, the log collection unit 203 generates cutter usage cumulative number state information based on a log of monitoring item: cumulative cutter usage number.

The remaining cutter use days information is information indicating the remaining days that the cutter 212 can use (hereinafter referred to as “cutter remaining use days”).
In step SG3, the log collection unit 203 calculates the remaining cutter use days by the following equation (2).

  KH = (KUseLimit−KUse (N)) ÷ [(KUse (N) −KUse (0)) ÷ N] (2).

  In Equation (2), “KH” represents the remaining cutter usage days. “KUseLimit” represents an upper limit value of the number of times the cutter 212 is used. “KUse (N)” represents the cumulative number of times the cutter 212 is used from the first day to the Nth day, with the day when the POS terminal 13 is installed in the store as the first day. IUse (0) represents the cumulative number of times the cutter 212 has been used before the date when the POS terminal 13 is installed in the store.

In Expression (2), the part “(KUseLimit−KUse (N))” on the right side represents the remaining number of times that the cutter 212 can be used.
In Expression (2), the part “[(KUse (N) −KUse (0)) ÷ N]” on the right side is the number of times the cutter 212 is used per day after the POS terminal 13 is installed in the store. The average value of.
Then, by dividing the remaining number of times that the cutter 212 can be used by the average value of the daily usage count of the cutter 212, the remaining cutter usage days when the POS terminal 13 is continuously used in the store are calculated. can do.

  Here, in calculating the remaining cutter use days using Expression (2), the log collection unit 203 calculates the values of N, KUse (N), and KUse (0) based on the log file 223. In the log file 223, the process control unit 201 records the values of these variables (may be values necessary for calculating these variables).

In addition, the log collection unit 203 calculates the value of KUseLimit based on the recording medium attribute information at the time of cutting recorded in the log file 223 by the following method.
In other words, the log collection unit 203 multiplies a predetermined initial value of KUseLimit by a coefficient set for each of the recording medium attributes of the roll paper accommodated in the POS terminal 13 in the past, to thereby calculate KUseLimit. calculate. In calculating KUseLimit, the log collection unit 203 sets the coefficient of each recording medium attribute to a value reflecting a weight corresponding to the number of times the recording medium attribute roll paper has been cut.
Here, the recording medium attribute is information indicating a combination of the quality, type, and thickness of the roll paper. The progress of deterioration when the roll paper is cut by the cutter 212 differs depending on the combination of the paper quality, type, and thickness of the roll paper. Based on this, the coefficient set to one recording medium attribute increases as the progress of deterioration of the cutter 212 when the roll paper having the one recording medium attribute is cut, while the coefficient of the cutter 212 It is set based on the results of prior tests and simulations so that the value decreases as the degree of progress of deterioration decreases.

  By using KUseLimit calculated by the above method and calculating the remaining number of days of use of the cutter 212 by the method of formula (2), the degree of deterioration of the cutter 212 is determined by the paper quality of the roll paper to be cut, Based on the characteristic that it varies depending on the type or thickness, the remaining cutter use days can be calculated appropriately reflecting the characteristic.

In step SG3, the log collection unit 203 calculates the remaining cutter use days information by the method described above based on the recording medium attribute information at the time of cutting, and generates remaining cutter use days information indicating the calculated remaining cutter use days. .
In step SG3, the log collection unit 203 associates the cumulative cutter usage status identification information, the cumulative cutter usage status information, and the remaining cutter usage date information to generate cumulative cutter usage status information data.

FIG. 6J is a diagram showing the contents of monitoring item: status information data of operation process (hereinafter referred to as “operation process status information data”).
As shown in FIG. 6J, the operation process status information data includes status identification information for identifying the operation process status information data (hereinafter referred to as “operation process status identification information”).
The operation process status information data includes operation process state information. The operation process state information includes information (a character string representing a process) indicating a process in an operation state (= a state in which a CPU is assigned) at the present time (a time corresponding to the timing at which the request data D1 is generated), and an operation And information indicating the date and time when the process status information is acquired.
In step SG3, the log collection unit 203 generates operation process state information based on the monitoring item: operation process log, and associates the operation process status identification information with the operation process state information to generate operation process status information data. Generate.

FIG. 6K is a diagram showing the contents of monitoring item: status information data of connected devices (hereinafter referred to as “connected device status information data”).
As shown in FIG. 6K, the connected device status information data includes status identification information for identifying the connected device status information data (hereinafter referred to as “connected device status identification information”).
The connected device status information data includes connected device status information. The connected device status information acquires information indicating the type of the device connected at the present time (the time corresponding to the timing of generating the request data D1) (character string indicating the type of device) and the connected device status information. Information indicating the date and time of the date.
In step SG3, the log collection unit 203 generates connection device status information based on the log of the monitoring item: connection device, and associates the connection device status identification information with the connection device status information to obtain the connection device status information data. Generate.

After generating the status information data of each monitoring item in step SG3, the log collecting unit 203 generates log data D11 including the status information data of each monitoring item and the POS terminal identification information of the POS terminal 13 (step) SG4).
The POS terminal identification information is identification information for identifying the POS terminal 13 and is, for example, a serial number uniquely assigned to the POS terminal 13 at the manufacturing stage of the POS terminal 13.
The log data D11 is text data that can be described by layering information (for example, data in XML format), and each piece of information is described by a combination of layered keys and values.

  Next, the log collection unit 203 communicates with each of the printing apparatuses 14 belonging to the same POS unit 16, and generates log data D11 for each printing apparatus 14 (step SG5). Hereinafter, the log data D11 of the POS terminal 13 is expressed as main log data D11m, the log data D11 of the printing apparatus 14 is expressed as sub-log data D11s, and these data are appropriately distinguished.

The sub-log data D11s is data including status information data of each monitoring item of the printing device 14 and printing device identification information of the printing device 14 as with the main log data D11m.
The printing device identification information is identification information for identifying the printing device 14 and is, for example, a serial number uniquely assigned to the printing device 14 in the manufacturing stage of the printing device 14.
In step SG5, the log collection unit 203 communicates with each of the printing apparatuses 14 belonging to the same POS unit 16, and from each of the printing apparatuses 14, logs of each monitoring item of the printing apparatus 14 and other sub-log data D11s. Get the information needed to generate. Information necessary for communication with the printing apparatus 14 such as the IP address of the printing apparatus 14, the protocol used for communication with the printing apparatus 14, and the format of data transmitted to and received from the printing apparatus 14 is registered in advance.
Next, the log collection unit 203 generates status information data of each monitoring item based on the log of each monitoring item for each printing apparatus 14, and generates sub-log data D11s based on the generated status information data.

  After generating the main log data D11m and the sub log data D11s, the log collection unit 203 ends the log data generation process in step SA3.

As shown in FIG. 4A, after log data D11 (main log data D11m and sub-log data D11s) is generated in the log data generation process in step SA3, the log collection unit 203 generates request data D1. (Step SA4).
The request data D1 includes store identification information for identifying the store where the POS terminal 13 is installed, POS terminal identification information for the POS terminal 13, processing result notification data D12, main log data D11m, and sub-log data D11s (POS terminal 13). In the case where there are a plurality of printing apparatuses 14 belonging to the same POS unit 16, the text data includes a plurality of sublog data D11s) and each information is described in a hierarchical manner.

FIG. 7 is a diagram schematically illustrating an example of the request data D1 in a mode suitable for explanation.
In the request data D1 illustrated in FIG. 7, store identification information and POS terminal identification information are described in the area A1.
In the area A2, processing result notification data D12 is described.
In the area A3, main log data D11m is described. In the area A31 of the area A3, POS terminal identification information is described. Status information data is described in area A32 of area A3. Status identification information is described in area A321 of area A32.
In the area A4, sub log data D11s is described. In the area A41 of the area A4, printing device identification information is described. Status information data is described in area A42 of area A4. Status identification information is described in area A421 of area A42.

  As shown in FIG. 4A, after generating the request data D1 in step SA4, the log collection unit 203 outputs the generated request data D1 to the communication management unit 204 by inter-program communication (step SA5). .

As shown in FIG. 4B, the communication management unit 204 acquires the request data D1 input from the log collection unit 203 (step SB1).
Next, the communication management unit 204 stores the acquired request data D1 in a predetermined storage area (step SB2). In the predetermined storage area, request data D1 that has not been transmitted to the maintenance server 17 and request data D1 that has been transmitted to the maintenance server 17 and discarded for the reason described later are accumulated.

Next, the communication management unit 204 refers to the transmission interval setting file 222 and monitors whether or not the timing for transmitting the request data D1 to the maintenance server 17 has arrived (step SB3).
The transmission interval setting file 222 is a file in which information indicating the timing for transmitting the request data D1 is recorded.
In the present embodiment, there are the following two timings for transmitting the request data D1.
The first timing is the timing when the request data D1 is generated by the log collection unit 203. In this case, the timing at which the request data D1 is generated is synchronized with the timing at which the request data D1 is transmitted, and the generated request data D1 is transmitted to the maintenance server 17 in response to the generation of the request data D1. Hereinafter, the first timing is referred to as “normal transmission timing”.

The second timing is a timing at which a predetermined interval (hereinafter referred to as “interval outside the contract period”) has elapsed since the request data D1 was transmitted last time. The interval outside the contract period is an interval longer than the reference generation interval (the longest interval for generating the request data D1) described above. For example, when the reference generation interval is “5 minutes”, the predetermined interval for transmitting the request data D1 is “1 hour”. Hereinafter, the second timing is referred to as “transmission timing outside the contract period”.
As will be described later, when the contract with the company using the store system 11 including the POS terminal 13 is in a state of being expired, information indicating the transmission timing outside the contract period is recorded in the transmission interval setting file 222.

In step SB3, when the information recorded in the transmission interval setting file 222 indicates the normal transmission timing, the communication management unit 204 maintains the request data D1 when the input of the log data D11 from the log collection unit 203 is completed. It is determined that the transmission timing to the server 17 has arrived.
In step SB3, when the information indicated by the transmission interval setting file 222 is the transmission timing outside the contract period, the communication management unit 204 transmits the request data D1 the last time after the transmission period outside the contract period has elapsed. It is determined that the timing for transmitting the request data D1 has arrived.

  When it is time to transmit the request data D1 (step SB3: YES), the communication management unit 204 controls the control device communication unit 23 to use the request data D1 stored in a predetermined storage area as a request as a maintenance server. 17 (step SB4). For example, the communication management unit 204 transmits an HTTP (Hypertext Transfer Protocol) request in which the request data D1 is described in the request body to the maintenance server 17 according to HTTP. Information necessary for transmitting the request data D1 to the maintenance server 17 as a request, such as the URL of the maintenance server 17 that transmits the request data D1 and the protocol to be used, is registered in advance.

  When there are a plurality of request data D1 stored in the predetermined storage area, the communication management unit 204 transmits the request data D1 having the oldest timing stored in the predetermined storage area.

  After transmitting the request data in step SB4, the communication management unit 204 monitors whether or not a response (contract information response data or response data D2) is received from the maintenance server 17 (step SB5).

As shown in FIG. 4D, the log receiving unit 501 of the maintenance server 17 controls the maintenance server communication unit 52 to receive and acquire the request data D1 transmitted by the communication management unit 204 (step SD1). .
Next, the log receiving unit 501 outputs the acquired request data D1 to the response response unit 502 (step SD2).

As shown in FIG. 4E, the response response unit 502 acquires the request data D1 input from the log reception unit 501 (step SE1).
Next, the response response unit 502 refers to the contract management database 512 (contract period information) and determines whether or not the current time is within the contract period of the corresponding company (step SE2).
The contract management database 512 is a database that stores a record in which store identification information is associated with information indicating a contract period of a company that uses the store system 11 of the store for each store that can be managed by the maintenance server 17. is there. The contract period of the company is a period during which the company can manage the store system 11 using the maintenance server 17. The contract period of the store is negotiated by a prior contract between the company operating the maintenance server 17 and the company. The company that operates the maintenance server 17 manages the state of the POS terminal 13 and the printing device 14 of the store system 11 of the company contracted by the maintenance server 17 during the contract period, and obtains revenue as the price.
The content of the contract management database 512 is appropriately rewritten by a predetermined means according to the contract status for each company, and the content corresponds to the actual contract status.

  In step SE2, the response response unit 502 acquires the store identification information of the store where the POS terminal 13 that is the transmission source of the request data D1 is installed. As described above, the store identification information is described in the request data D1. Next, the response response unit 502 specifies a record having the acquired store identification information among the records in the contract management database 512. Next, the response response unit 502 acquires information indicating the contract period of the identified record, and determines whether the current time is within the contract period.

  Next, the response response unit 502 determines whether or not the current time is within the contract period of the company (step SE3).

If not within the contract period (step SE3: NO), the response response unit 502 generates contract information response data, controls the maintenance server communication unit 52, and transmits the generated contract information response data as a response (step SE4). ).
More specifically, the response response unit 502 generates contract information response data including information indicating that it is not within the contract period, and transmits it as a response.

  Next, the response response unit 502 discards the request data D1 (step SE5) and ends the process. In this case, storage of records (storage of information based on the log data D11) is not performed in the first status information database 513 and the second status information database 514 based on the request data D1. This is because these processes should be performed for companies within the contract period, that is, companies that pay the consideration.

  If the current time is within the contract period of the company (step SE3: YES), the response response unit 502 outputs the request data D1 acquired in step SE1 to the log information storage unit 503 (step SE6). The processing of the log information storage unit 503 will be described later.

Next, the response response unit 502 executes response data generation processing (step SE7).
The response data generation process is a process for generating response data D2. Hereinafter, the response data generation process will be described in detail.

FIG. 8A is a flowchart showing in detail the operation of the response response unit 502 when executing the response data generation process.
As shown in FIG. 8A, in the response data generation process, the response response unit 502 executes a process command control data generation process (step SH1) and generates process command control data D21.

FIG. 8B is a flowchart showing in detail the operation of the response response unit 502 when executing the processing instruction control data generation process.
As shown in FIG. 8B, in the process command control data generation process, the response response unit 502 refers to the command storage database 511 (step SI1).
The instruction storage database 511 is a database that stores a record in which POS terminal identification information of the POS terminal 13 and information related to processing to be executed by the POS terminal 13 (hereinafter referred to as “execution processing information”) are associated with each other.
The execution process information includes information for identifying a process to be executed by the POS terminal 13, data necessary for executing the process, information necessary for generating other process command control data D21, and the like.

The response response unit 502 generates POS terminal identification information of a specific POS terminal 13 and execution processing information related to processing to be executed by the specific POS terminal 13 for a person in charge of the company or a person in charge of maintenance. Therefore, a user interface for inputting necessary information is provided, and a record is stored in the instruction storage database 511 based on an input to the user interface. The process executed by the POS terminal 13 is, for example, firmware upgrade. When the process to be executed is firmware upgrade, information necessary for generating execution process information is, for example, a firmware program. Data, etc.
More specifically, a person in charge of a company who desires a specific POS terminal 13 to execute a predetermined process starts up a web browser of a terminal in which the web browser is installed, Access URL. The response response unit 502 is a user who can input necessary information to generate POS terminal identification information and execution processing information after performing necessary authentication when there is an access to the predetermined URL. An interface (web page) is displayed on the terminal. The person in charge of the company, for example, information necessary for generating the POS terminal identification information of the specific POS terminal 13 and the process execution related information related to the process to be executed by the specific POS terminal 13 in the user interface. Enter. The response response unit 502 acquires information necessary for generating the process execution related information input to the user interface, and generates execution process information based on the acquired information. The response response unit 502 accesses the command storage database 511 and stores a record in which the POS terminal identification information input to the user interface is associated with the generated execution process information.

After referring to the instruction storage database 511 in step SI1, the response response unit 502 acquires the POS terminal identification information of the POS terminal 13 that is the transmission source of the request data D1 (step SI2). As described above, the POS terminal identification information is described in the request data D1.
Next, the response response unit 502 determines whether or not a record having the POS terminal identification information acquired in step SI2 exists in the instruction storage database 511 (step SI3).
When there is no record having the POS terminal identification information acquired in step SI2 in the command storage database 511 (step SI3: NO), the response response unit 502 shifts the processing procedure to step SI5.

  When the record having the POS terminal identification information acquired in step SI2 exists in the instruction storage database 511 (step SI3: YES), the response response unit 502 records the record having the POS terminal identification information acquired in step SI2 (the record is If there are a plurality of records, the execution process information of each of the plurality of records) is acquired (step SI4). For the purpose of causing the POS terminal 13 that is the transmission source of the request data D1 to execute predetermined processing by the user including the person in charge of the company between the time when the response data D2 is transmitted and the current time. When the record corresponding to the command storage database 511 is stored by the means, the record having the POS terminal identification information acquired in step SI2 is in the command storage database 511.

  In the subsequent step SI5, the response response unit 502 acquires the processing result notification data D12 included in the request data D1 (step SI5).

Next, the response response unit 502 generates processing command control data D21 based on the execution processing information acquired in step SI4 and the processing result notification data D12 acquired in step SI5 (step SI6).
More specifically, the response response unit 502 generates control data (hereinafter referred to as “first control data”) that causes the POS terminal 13 to execute a process corresponding to the execution process information based on the acquired execution process information. . If there are a plurality of acquired execution process information, the response response unit 502 generates control data for executing each of the processes corresponding to the plurality of execution process information. Note that the response response unit 502 has a function of generating processing instruction control data D21 for executing corresponding one or more processes based on one or more execution process information.
Further, the response response unit 502 executes the process when there is a process to be executed by the POS terminal 13 based on the process result notification data D12 and according to the process result of the process executed by the instruction execution unit 205. Control data (hereinafter referred to as “second control data”) to be generated.
Next, the response response unit 502 generates processing command control data D21 including the first control data and the second control data. The processing command control data D21 is data that can be transmitted to the POS terminal 13 as a response in JSON (JavaScript (registered trademark) Object Notation) format, XML format, or the like.

  After generating the processing command control data D21, the response response unit 502 deletes each of the records having the POS terminal identification information acquired in step SI2 from the command storage database 511 (step SI7). As a result of the processing in step SI7, the instruction storage database 511 is in a state where there is no record from which the process instruction control data D21 is generated.

After deleting the record, the response response unit 502 ends the processing command control data generation process.
Note that “there is no record corresponding to the instruction storage database 511” and “the request data D1 does not have the processing result notification data D12, or the processing result notification data D12 included in the request data D1 indicates to the POS terminal 13 If there is no process to be executed, the process command control data D21 is not generated. However, in the following, for the convenience of description, the response response unit 502 and other main processes will be described on the assumption that the processing command control data D21 has been generated.

  As shown in FIG. 8A, after the processing instruction control data generation process is executed in step SH1 to generate the processing instruction control data D21, the response response unit 502 executes the error warning / predictive notification data generation process. Thus, error warning / predictive notification data D22 is generated (step SH2).

FIG. 8C is a flowchart showing in detail the operation of the response response unit 502 when the error warning / predictive notification data generation process is executed.
As shown in FIG. 8C, in the error warning / predictive notification data generation process, the response response unit 502 acquires log data D11 (main log data D11m and sub log data D11s) included in the request data D1. (Step SJ1).

Next, based on the log data D11 acquired in step SJ1, the response response unit 502 determines whether the predetermined monitoring item of the POS terminal 13 is in the error warning state or the error predictor state, and the predetermined response of the printing device 14. It is determined whether or not the monitoring item is in an error warning state or an error predictor state (step SJ2).
Here, the monitoring items that are targets for determining whether or not the error warning state or the error predictor state are monitoring item: RAM usage rate, monitoring item: CPU usage rate, monitoring item: CPU temperature, and monitoring item: Data transfer rate.
The response response unit 502 determines whether the POS terminal 13 monitoring item: RAM usage rate is in an error warning state or an error predictor state by the following method. That is, with regard to the monitoring item: RAM usage rate, there is a high probability that a failure will occur if a corresponding action is not taken, although an error state (a failure has occurred in the RAM), an error warning state (a failure has not occurred in the RAM) Conditions) and an error sign state (a state in which a failure has not occurred in the RAM but a failure may occur due to continuous use) are determined in advance. The condition is a condition that is satisfied when the RAM usage rate (numerical value) and a predetermined threshold value have a predetermined relationship. The condition for determining an error state is, for example, that the RAM usage rate exceeds a predetermined threshold. The condition for determining the error warning state is, for example, that the RAM usage rate exceeds a predetermined threshold value that is smaller than the threshold value for determining the error state. The condition for determining the error sign state is, for example, that the increase or decrease in the RAM usage rate exceeds a predetermined threshold. Here, exceeding the threshold includes, for example, the case where the RAM usage rate exceeds the threshold instantaneously and the state where the RAM usage rate exceeds the threshold continues for a predetermined period.
Monitoring item: In determining whether the RAM usage rate is in the error warning state or the error predictor state, the response response unit 502 uses the RAM usage rate status information data included in the main log data D11m of the request data D1. Get rate status information. As described above, the RAM usage rate state information includes information indicating the transition of the RAM usage rate in a predetermined period in time series. Next, the response response unit 502 determines whether or not a condition relating to the error warning state or the error predictor state is satisfied based on the acquired RAM usage rate state information, so that an error about the monitoring item: RAM usage rate is obtained. It is determined whether the state is a warning state or an error predictor state.

  The conditions for discriminating between the error warning state and the error predictor state can be changed by a predetermined means by a maintenance person, a person in charge of the company, or the like.

In a similar manner, the response response unit 502 determines whether the monitoring item: CPU usage rate, the monitoring item: CPU temperature, and the monitoring item: data transfer rate are in an error warning state or an error predictor state.
Further, the response response unit 502 determines whether the predetermined monitoring item of the printing apparatus 14 is in an error warning state or an error predictor state based on the sublog data D11s in the same manner.

  Note that the response response unit 502 takes into account the temporal relationship between the date and time when the monitoring item has reached a predetermined state and the current date and time when determining whether the monitoring item is in an error warning state or an error predictor state. To do.

  The error warning state and the error predictor state correspond to “a state where an error is highly likely to occur”.

In subsequent step SJ3, the response response unit 502 generates error warning / predictive notification data D22 based on the determination result in step SJ2.
In other words, the response response unit 502 is configured when the predetermined monitoring item of the POS terminal 13 is in the error warning state or the error predictor state, or when the predetermined monitoring item of the printing apparatus 14 is in the error warning state or the error predictor state. For each monitoring item that is in the error warning state or the error predictor state, error warning / prediction notification data D22 including information indicating the monitoring item and information indicating either the error warning state or the error predictor state is generated.
The response response unit 502 also includes error warning / prediction notification data including information indicating that there is no error warning state or error predictor state monitoring item when there is no error warning state or error predictor state monitoring item. D22 is generated.
The error warning / predictive notification data D22 is text data (for example, data in XML format) that can be described by layering information, and is data that can be transmitted to the POS terminal 13 as a response.

As shown in FIG. 8A, after executing the error warning / predictive notification data generation process, the response response unit 502 includes information indicating that the current time based on the determination result in step SE2 is within the contract period of the company. Response data D2 is generated based on the processing instruction control data D21 generated in step SH1 and the error warning / prediction notification data D22 generated in step SH2 (step SH3), and the response data generation process is terminated.
The response data D2 is data including information indicating that the current time is within the contract period of the company, processing command control data D21, and error warning / prediction notification data D22.

As shown in FIG. 4 (E), after executing the response data generation process of step SE7, the response response unit 502 controls the maintenance server communication unit 52 and sends the generated response data D2 to the POS terminal 13 as a response. Transmit (step SE8). For example, the response response unit 502 transmits an HTTP response in which the response data D2 is described in the response body to the POS terminal 13 according to HTTP.
After transmitting the response data D2, the response response unit 502 ends the process.

  Thus, in this embodiment, the POS terminal 13 generates the log data D11 with a predetermined interval, and transmits the request data D1 including the log data D11 to the maintenance server 17. The maintenance server 17 transmits response data D2 in response to the request data D1. Due to such a configuration, the POS terminal 13 can notify the maintenance server 17 of the status of the monitoring items of the POS terminal 13 and the printing apparatus 14 at a predetermined interval. In addition, the maintenance server 17 uses the configuration in which the POS terminal 13 transmits the request data D1 including the log data D11 at intervals, and transmits the response data D2 as a response to perform processing necessary for the POS terminal 13. Can be executed.

As shown in FIG. 4B, the communication management unit 204 waiting for reception of a response (contract information response data or response data D2) in step SB5 receives a response (step SB5: YES). A transmission interval setting process is executed (step SB6).
Specifically, the communication management unit 204 determines whether the current time is within the contract period based on the contract information response data or the response data D2. When the current time is within the contract period, the communication management unit 204 records information indicating the normal transmission timing in the transmission interval setting file 222. On the other hand, when the current time is not within the contract period, the communication management unit 204 writes information indicating the transmission timing outside the contract period in the transmission interval setting file 222. The non-contract period timing is the timing at which the non-contract period interval has elapsed since the request data D1 was transmitted last time. The non-contract period interval is an interval longer than the reference generation interval (the longest interval for generating the request data D1). For example, when the reference generation interval is “5 minutes”, the non-contract period is “1 hour”.

  If the current time is within the contract period by the processing of step SB5, the request data D1 is transmitted at an interval synchronized with the generated interval. If the current time is not within the contract period, the request data D1 is Sent at intervals outside the contract period.

Thus, in the present embodiment, when the current time is not within the contract period of the company, the interval for transmitting the request data D1 (log data D11) is longer than that when the current time is within the contract period of the company. It is said. Thereby, the following effects are produced.
That is, when the POS terminal 13 transmits the request data D1, the communication bandwidth is consumed correspondingly, and the maintenance server 17 that has received the request data D1 uses the necessary storage area to obtain the necessary data. Is stored, and necessary arithmetic processing is executed. That is, transmission of the request data D1 by the POS terminal 13 involves consumption of resources related to communication, software in the maintenance server 17, and resources related to hardware. Then, by making the interval at which the POS terminal 13 related to the company not within the contract period transmits the request data D1 longer than the interval at which the POS terminal 13 related to the company within the contract period transmits the request data D1, the contract period It is possible to suppress the consumption of resources due to the transmission of the request data D1 by the POS terminal 13 related to a company that is not within, and to differentiate the response between the contracted company and the company that is not, and to improve the fairness Can be secured.
Here, for companies that are not within the contract period, it is possible to completely stop the transmission of the request data D1 from the POS terminal 13 related to the company. However, it is assumed that there may be a situation where the current time is not within the contract period due to a mistake in the procedure even though the company is willing to contract. Then, as in this embodiment, for companies that are not within the contract period, the transmission of the request data D1 from the POS terminal 13 related to the company is not completely stopped, but only temporarily during the contract period. By increasing the transmission interval of the request data D1, it is possible to suppress the occurrence of unexpected disadvantages due to the fact that the function of the maintenance server 17 cannot be used at all for a company that intends to make a contract. In addition, every time the maintenance server 17 receives the request data D1, the maintenance server 17 continuously transmits the request data D1 by the POS terminal 13 in order to determine whether it is within the contract period. Whether or not it is within the contract period accompanying reception of the request data D1 is continuously performed. For this reason, when a new contract is made, the timing for transmitting the request data D1 can be set as the normal transmission timing.
As will be described later, the request data D1 generated while not within the contract period does not disappear, but is transmitted to the maintenance server 17 and appropriately processed by the server when it is within the contract period.

After executing the transmission interval setting process in step SB6, the communication management unit 204 determines whether or not the current time is within the contract period (step SB7).
If it is not within the contract period (step SB7: NO), the communication management unit 204 ends the process. In this case, the request data D1 stored in the predetermined storage area is not deleted, and the stored state is maintained. The request data D1 stored in the predetermined storage area is the data to be transmitted (in the state where a plurality of request data D1 is stored in the predetermined storage area) when the next transmission timing of the request data D1 arrives. In this case, it is one of the data to be transmitted).

  If it is within the contract period (step SB7: YES), the communication management unit 204 acquires the error warning / predictive notification data D22 included in the response data D2 and outputs it to the log collection unit 203 (step SB8).

  As shown in FIG. 4A, the log collection unit 203 is based on the error warning / prediction notification data D22 input and acquired from the communication management unit 204, and the log data D11 generated by the log data generation processing in step SA3. Then, the generation interval setting process is executed (step SA6).

FIG. 9 is a flowchart showing details of the process of the log collection unit 203 when the generation interval setting process is executed.
As illustrated in FIG. 9, the log collection unit 203 acquires log data D11 (main log data D11m and sub-log data D11s) (step SK1).
Next, the log collection unit 203 determines whether the predetermined monitoring item of the POS terminal 13 is in the error warning state or the error predictor state based on the log data D11 acquired in step SK1, and the predetermined amount of the printing apparatus 14. It is determined whether or not the monitoring item is in an error warning state or an error sign state (step SK2).

Whether the monitoring item is in an error warning state or an error predictor state is determined by the same method as described in the error warning / predictor notification data generation process described above. In other words, the log collection unit 203 determines that the corresponding condition relating to the error warning state is satisfied for the monitoring item: RAM usage rate, the monitoring item: CPU usage rate, the monitoring item: CPU temperature, and the monitoring item: data transfer rate. Is determined to be in an error warning state. In addition, the log collection unit 203 determines that these monitoring items are in the error predictor state when the corresponding condition relating to the error predictor state is satisfied.
In the process of step SK2, conditions used for determining whether or not an error warning state or an error predictor state is registered in advance by a predetermined person by a predetermined means.

Here, the conditions used in the error warning / predictive notification data generation process performed by the maintenance server 17 (hereinafter referred to as “server-side conditions”) and the conditions used in the process of step SK2 performed by the POS terminal 13 (hereinafter referred to as “ "POS terminal side condition") does not have to be the same.
For example, the POS terminal-side condition is such that a person who can grasp the actual usage mode of the POS terminal 13 such as the environment where the POS terminal 13 is installed is a condition reflecting the actual usage mode of the POS terminal 13. The content of the condition can be set from a viewpoint different from the side condition.

  When there is at least one monitoring item in the error warning state or the error predictor state (step SK2: YES), the log collection unit 203 updates the generation interval setting file 221 to the generation interval setting file 221 based on the reference generation interval. Also, information indicating a short interval (hereinafter referred to as “shortened generation interval”) is recorded (step SK3). Thereafter, the log collection unit 203 proceeds to step SK4. As described above, the reference generation interval is the longest interval that can be set as an interval for generating the request data D1 (log data D11). The value of the shortened generation interval is determined by a predetermined method according to the state of the monitoring item that is in the error warning state or the error predictor state.

  When there is no monitoring item of the error warning state or the error predictor state based on the log data D11 (step SK2: NO), the log collection unit 203 moves the processing procedure to step SK4.

  In step SK4, the log collection unit 203 acquires error warning / predictive notification data D22.

Next, the log collection unit 203 determines whether or not the predetermined monitoring item of the POS terminal 13 is in the error warning state or the error prediction state based on the error warning / prediction notification data D22 acquired in step SK4, and the printing apparatus. It is determined whether or not the 14 predetermined monitoring items are in an error warning state or an error predictor state (step SK5).
When there is at least one monitoring item in the error warning state or the error predictor state (step SK5: YES), the log collection unit 203 updates the generation interval setting file 221 and sets a shortened generation interval in the generation interval setting file 221. The information shown is recorded (step SK6). Thereafter, the log collection unit 203 shifts the processing procedure to step SK7. The value of the shortened generation interval includes the status of the monitoring item determined as the error warning state or the error predictor state in step SK2, and the monitor item indicated as the error warning state or the error predictor state in the error warning / predictor notification data D22. It is a value according to the state of.

  When there is no monitoring item of the error warning state or the error prediction state based on the error warning / prediction notification data D22 (step SK7: YES), the log collection unit 203 shifts the processing procedure to step SK8.

In step SK7, the log collection unit 203 determines whether there is no monitoring item in the error warning state or the error predictor state in any of the processes in steps SK2 and SK5.
When it is determined that there is no monitoring item in the error warning state or the error predictor state in any of the processes of step SK2 and step SK5 (step SK7: YES), the log collection unit 203 generates the generation interval setting file 221. And information indicating the reference generation interval is recorded in the generation interval setting file 221 (step SK8). Thereafter, the log collection unit 203 ends the generation interval setting process.
If there is a monitoring item that has been determined as an error warning state or an error warning state in any of the processes of step SK2 and step SK5 (step SK7: NO), the log collection unit 203 ends the generation interval setting process.

As described above, in the present embodiment, when the predetermined monitoring item is in the error warning state or the error predictor state (when there is a high possibility of being in the error state), the request data D1 (log) The interval for generating the data D11) is shortened. This produces the following effects. When the request data D1 is generated at the shortened generation interval, basically, the request data D1 is transmitted at the normal transmission timing, and therefore the request data D1 is transmitted at a shorter interval.
In other words, when one monitoring item is in an error warning state or an error predictor state, the one monitoring item is in a state where there is a high possibility of being in an error state (a state in which a failure has occurred). In this case, the person in charge of maintenance needs to monitor the state of the one monitoring item at intervals as short as possible, and perform corresponding processing as necessary. As will be described later, the log information storage unit 503 of the maintenance server 17 stores a record based on the request data D1 in the second status information database 514 in response to the reception of the request data D1. Further, the log information display unit 504 of the maintenance server 17 notifies the states of the POS terminal 13 and the printing device 14 based on the second status information database 514 in response to a request from the maintenance staff. Therefore, by shortening the interval for generating and transmitting the request data D1 when the monitoring item is in an error warning state or an error predictive state, the maintenance staff can change the state of the monitoring item in such a state. Can be monitored at intervals as short as possible, and corresponding processing can be performed as necessary.
It should be noted that the interval at which the request data D1 is generated and transmitted can always be a shortened generation interval. However, as described above, transmission of the request data D1 involves consumption of various resources. Therefore, while the monitoring item is in the error warning state or the error predicting state, the generation and transmission intervals of the request data D1 are shortened, thereby suppressing unnecessary resource consumption and efficient when necessary. The maintenance staff can be notified of the status of the monitoring items.

As shown in FIG. 4B, after outputting the error warning / prediction notification data D22 to the log collection unit 203 in step SB9, the communication management unit 204 acquires the processing command control data D21 included in the response data D2. Is output to the instruction execution unit 205 (step SB9).
Next, the communication management unit 204 deletes the request data D1 transmitted in step SB4 from a predetermined storage area (step SB10). By the process of step SB11, the request data D1 transmitted to the maintenance server 17 and processed by the maintenance server 17 (information based on the request data D1 is stored) is prevented from being transmitted redundantly.
Next, the communication management unit 204 determines whether or not the request data D1 is stored in a predetermined storage area (step SB11). The request data D1 stored in the predetermined storage area at the time of step SB12 is data that is not processed by the maintenance server 17 (information that is based on the request data D1 is not stored).
When the request data D1 is stored in the predetermined storage area (step SB11: YES), the communication management unit 204 moves the processing procedure to step SB4.
If the request data D1 is not stored in the predetermined storage area (step SB11: NO), the communication management unit 204 ends the process.

As shown in FIG. 4C, the command execution unit 205 acquires the processing command control data D21 input from the communication management unit 204 (step SC1).
Next, the instruction execution unit 205 executes a corresponding process based on the acquired process instruction control data D21 (step SC2). As described above, the processing instruction control data D21 includes control data for instructing execution of each process to be executed by the instruction execution unit 205. The instruction execution unit 205 executes processing by changing the command system of the control data as necessary. For example, when the processing instruction control data D21 includes control data for instructing firmware update, the instruction execution unit 205 executes firmware update based on the control data.

Next, the instruction execution unit 205 generates process result data D3 indicating the process result of the process executed based on the process instruction control data D21 (step SC3).
Next, the instruction execution unit 205 outputs the generated processing result data D3 to the log collection unit 203 (step SC4).

  As shown in FIG. 4A, the log collection unit 203 acquires the processing result data D3 input from the instruction execution unit 205, stores it in a predetermined storage area (step SA7), and returns the processing to step SA1. .

  As described above, in step SE6 of FIG. 4E, the response response unit 502 outputs the request data D1 to the log information storage unit 503.

As illustrated in FIG. 4F, the log information storage unit 503 receives and acquires the request data D1 input from the log reception unit 501 (step SF1).
Next, the log information storage unit 503 executes database registration processing (step SF2).

FIG. 10 is a flowchart showing details of the process of the log information storage unit 503 when the database registration process is executed.
As illustrated in FIG. 10, the log information storage unit 503 acquires log data D11 (main log data D11m and sub-log data D11s) included in the request data D1 (step SL1).

Next, the log information storage unit 503 executes a first database registration process based on the acquired log data D11 (step SL2). Hereinafter, the first database registration process will be described in detail.
The first database registration process is a process for generating a record based on the status information data included in the log data D11 and storing it in the first status information database 513.
When generating a record based on the status information database of one monitoring item, the log information storage unit 503 executes the following processing. That is, the log information storage unit 503 stores the store identification information of the corresponding store and the identification information (POS terminal identification information or printing device identification information) of the device (POS terminal 13 or printing device 14) corresponding to the one monitoring item. And a record that associates the status information data of the one monitoring item with each other. Note that the log information storage unit 503 performs a formal change on the status information data included in the record so as to correspond to the data structure of the record in the first status information database 513.

FIG. 11A is a diagram schematically showing a record generated based on the monitoring item of the POS terminal 13: RAM usage rate status information data (status information data) of the RAM usage rate.
For example, when generating a record based on the monitoring item: RAM usage rate of the POS terminal 13, the log information storage unit 503 executes the following processing. That is, the log information storage unit 503 has a formal format for the purpose of supporting the store identification information described in the request data D1, the POS terminal identification information of the POS terminal 13, and the data structure of the first status information database 513. A record in which the changed RAM usage status information data is associated is generated. As a result, a record shown in FIG. 11A is generated as a record based on the monitoring item: RAM usage rate and stored in the first status information database 513.

  In the first database registration process of step SL2, the POS terminal 13 uses the above-described method, based on the log data D11 (main log data D11m and sub log data D11s), status information data of each monitoring item of the POS terminal 13, A record based on the status information of each monitoring item of the printing apparatus 14 is generated and stored in the first status information database 513.

After execution of the first database registration process, the log information storage unit 503 executes the second database registration process (step SL3). Hereinafter, the second database registration process will be described in detail.
The second database registration process is a process for generating a record based on the status information data included in the log data D11 and storing it in the second status information database 514. In particular, in the second database registration process, the log information storage unit 503 generates a record including state classification information described later in a predetermined case.

FIG. 12 is a flowchart showing details of the process of the log information storage unit 503 when one record is generated based on the status information data of one monitoring item in the second database registration process.
As shown in FIG. 12, the log information storage unit 503 acquires status information data from the log data D11 (step SM1).
Next, the log information storage unit 503 determines whether or not status identification information is included in the acquired status information data (step SM2).

  If the status information data is not in a state where the status identification information is included (step SM2: NO), the log information storage unit 503 ends the second database registration process. In this case, the generation of the record based on the status information data acquired in step SM1 and the storage in the second status information database 514 are not performed. Note that the status information does not include the status identification information when the status information data is not data indicating the status of the monitoring item or when the status identification information is not allocated.

When the status information includes the status identification information (step SM2: YES), the log information storage unit 503 determines that the status information data is in the error status based on the status identification information value. It is determined whether or not the data is present (step SM3).
More specifically, in the present embodiment, in the status information data, monitoring item: communication error status information data (status information data) for communication error and monitoring item: printer error status information data (status information data) for printer error Is “data indicating that the monitoring item is in an error state”. As described above, these status information data are data generated when the status of the monitoring item becomes an error state. The monitoring items corresponding to these status information data are determined to be in an error state, and there is no need to classify the state by the log information storage unit 503 described later.

  In step SM3, the log information storage unit 503 identifies the monitoring item based on the value of the status identification information. If the monitoring item is a monitoring item: communication error or a monitoring item: printer error, the status information data indicates the monitoring item. It is determined that the data indicates that the state is an error state.

When the status information data is data indicating that the state of the monitoring item is an error state (step SM3: YES), the log information storage unit 503 generates the following record and stores it in the second status information database 514. Store (step SM4) and end the second database registration process. That is, the log information storage unit 503 stores the store identification information of the corresponding store and the identification information (POS terminal identification information or printing device identification information) of the device (POS terminal 13 or printing device 14) corresponding to the one monitoring item. And a record in which status information data of the one monitoring item is associated with classification information indicating an error state. Note that the log information storage unit 503 performs a formal change on the status information data included in the record so as to correspond to the data structure of the record in the second status information database 514.
The classification information is information indicating the classification of the status of the monitoring item. In this embodiment, the status of the monitoring item is an error state (a state in which a failure has occurred), an error warning state (a state in which no failure has occurred, but there is a high probability that a failure will occur if no corresponding action is taken), It is classified into four states: an error predicting state (a state in which no failure has occurred but a failure may occur due to continuous use) and a normal state. The classification information is information indicating any one of the four states described above.

FIG. 11B is a diagram schematically showing a record generated based on the monitoring item of the POS terminal 13: communication error status information data (status information data) of a communication error.
For example, when the record based on the monitoring item: communication error of the POS terminal 13 is generated, the log information storage unit 503 executes the following processing. That is, the log information storage unit 503 has a formal format for the purpose of supporting the store identification information described in the request data D1, the POS terminal identification information of the POS terminal 13, and the data structure of the second status information database 514. A record is generated in which the communication error status information data that has been changed is associated with the classification information that indicates an error state. As a result, a record shown in FIG. 11B is generated as a record based on the monitoring item: communication error, and stored in the second status information database 514.

In step SM3, when it is determined that the status information data is not data indicating that the status of the monitoring item is an error state (step SM3: NO), the log information storage unit 503 displays the status information data of the monitoring item. It is determined whether the data represents the state by a numerical value or the data that represents the state of the monitoring item by a character string (step SM5).
In this embodiment, monitoring item: RAM usage rate, monitoring item: CPU usage rate, monitoring item: CPU temperature, monitoring item: data transfer rate, monitoring item: SSD usage record, monitoring item: print head formation line cumulative number, And the monitoring item: the status information data of the cumulative number of cutters used is data representing the state of the monitoring item by a numerical value.
In particular, regarding the status information data of the monitoring item: SSD usage record value, the SSD life indicated by the SSD life information corresponds to the state of the monitoring item represented by a numerical value. In addition, regarding the status information data of the monitoring item: cumulative number of print head formation lines, the remaining print head use days indicated by the print head remaining use days information corresponds to the state of the monitor item represented by a numerical value. In addition, regarding the status information data of the monitoring item: cumulative number of cutters used, the remaining cutter usage days indicated by the remaining cutter usage days information corresponds to the state of the monitoring item represented by a numerical value.
In this embodiment, the status information data of the monitoring item: operation process and the monitoring item: connected device is data representing the status of the monitoring item by a character string.

In step SM5, the log information storage unit 503 identifies the monitoring item based on the value of the status identification information, and the monitoring item is monitoring item: RAM usage rate, monitoring item: CPU usage rate, monitoring item: CPU temperature, monitoring. In the case of item: data transfer speed, monitoring item: SSD usage record value, monitoring item: print head formation line cumulative number, or monitoring item: cutter usage cumulative number, the status information data represents the status of the monitoring item as a numerical value. It is determined that
In step SM5, the log information storage unit 503 identifies the monitoring item based on the value of the status information. If the monitoring item is monitoring item: operation process or monitoring item: connected device, the status information data is stored. , It is determined that the data represents the status of the monitoring item by a character string.

When the status information data is data representing the state of the monitoring item by a numerical value (step SM5: “numerical value”), the log information storage unit 503 monitors based on the relationship between the numerical value representing the state of the monitoring item and a predetermined threshold value. The classification of the item state is determined (step SM6).
Specifically, for each monitoring item, a condition for determining that each of the error state, the error warning state, the error predictor state, and the normal state is classified into each state is determined in advance. The condition is a condition that is established when a numerical value indicating the state of the monitoring item and a predetermined threshold value have a predetermined relationship.

For example, regarding the condition for determining an error state, in the case of monitoring item: RAM usage rate, monitoring item: CPU usage rate, monitoring item: CPU temperature, and monitoring item: data transfer rate, a predetermined value set in advance for each monitoring item It is a condition that the threshold value is exceeded. Further, for example, regarding the condition for determining an error state, in the case of the monitoring item: SSD usage record value, the condition is that the life of the SSD is shorter than a predetermined threshold. Further, for example, regarding the condition for determining an error state, in the case of monitoring item: cumulative number of print head formation lines or monitoring item: cumulative number of cutters used, the remaining number of days that the print head 211 or the cutter 212 can be used is a predetermined number. The condition is that it is shorter than the threshold value.
Note that the condition for a predetermined monitoring item may be the same as the condition used in the error warning / predictive notification data generation process described above.

  The conditions can be changed by a predetermined means by a maintenance person, a person in charge of the company, or the like.

  Next, the log information storage unit 503 stores the store identification information of the corresponding store and the identification information (POS terminal identification information) of the device (POS terminal 13 or printing device 14) corresponding to the monitoring item of the status information data acquired in step SM1. Alternatively, a record in which the status information data acquired in step SM1 and the classification information indicating the classification determined in step SM6 are associated with each other is generated and stored in the second status information database 514 (step SM7). ). Thereafter, the log information storage unit 503 ends the second database registration process. Note that the log information storage unit 503 performs a formal change on the status information data included in the record so as to correspond to the data structure of the record in the second status information database 514.

FIG. 11C is a diagram schematically showing a record generated in step SM6 based on the monitoring item of the POS terminal 13: RAM usage status information data (status information data) of the RAM usage rate.
For example, when generating a record based on the monitoring item: RAM usage rate of the POS terminal 13, the log information storage unit 503 executes the following processing. That is, the log information storage unit 503 has a formal format for the purpose of supporting the store identification information described in the request data D1, the POS terminal identification information of the POS terminal 13, and the data structure of the second status information database 514. A record is generated in which the changed RAM usage status information data is associated with the classification information indicating the classification determined in step SM6. As a result, a record shown in FIG. 11C is generated as a record based on the monitoring item: RAM usage rate and stored in the second status information database 514.
As is clear from the comparison between the record shown in FIG. 11A and the record shown in FIG. 11C, the classification information is not added to the record stored in the first status information database 513, but the second status information Classification information is added to the record stored in the database 514.

On the other hand, when the status information data is data representing the state of the monitoring item by a character string (step SM5: “character string”), the log information storage unit 503 monitors based on the content of the character string representing the state of the monitoring item. The classification of the item state is discriminated (step SM8).
The processing in step SM8 when the monitoring item of the status information data is the monitoring item: an operation process will be described in detail. For each POS terminal 13, a process that needs to be in an operation state (hereinafter referred to as “necessary process”). A process that should not be in an operating state (hereinafter referred to as “unnecessary process”) is determined in advance and registered in association with the POS terminal identification information of the POS terminal 13 or the printing apparatus identification information of the printing apparatus 14. In step SM8, the log information storage unit 503 determines whether or not the status of the monitoring item represented by the character string is an operating state for each of the necessary process and the unnecessary process using a technique such as character string search. Is determined. The log information storage unit 503 determines that the state of the monitoring item is the normal state when the necessary process is in the operating state and the unnecessary process is not in the operating state. On the other hand, the log information storage unit 503 determines that the state of the monitoring item is an error state when there is a necessary process that is not in an operating state or there is an unnecessary process that is in an operating state.
Necessary processes and unnecessary processes can be changed by predetermined means by a maintenance person, a person in charge of a company, or the like.

The processing in step SM8 when the monitoring item of the status information data is the monitoring item: connected device will be described in detail. For each POS terminal 13, a process that needs to be connected (hereinafter referred to as “necessary device”), connection, and the like. Devices that should not be performed (hereinafter referred to as “unnecessary devices”) are determined in advance and registered in association with the POS terminal identification information of the POS terminal 13 or the printing device identification information of the printing device 14. In step SM8, the log information storage unit 503 determines whether the status of the monitoring item represented by the character string is connected to each of the necessary device and the unnecessary device using a technique such as character string search. Determine whether or not. The log information storage unit 503 determines that the state of the monitoring item is the normal state when the necessary device is connected and the unnecessary device is not connected. On the other hand, the log information storage unit 503 determines that the state of the monitoring item is an error state when there is something that is not connected to a necessary device or there is something that is connected to an unnecessary device. To do.
Necessary devices and unnecessary devices can be changed by predetermined means by a maintenance person, a person in charge of a company, or the like.

  Next, the log information storage unit 503 stores the store identification information of the corresponding store and the identification information (POS terminal identification information) of the device (POS terminal 13 or printing device 14) corresponding to the monitoring item of the status information data acquired in step SM1. Alternatively, a record in which the status information data acquired in step SM1 and the classification information indicating the classification determined in step SM8 are associated with each other is generated and stored in the second status information database 514 (step SM9). ). Thereafter, the log information storage unit 503 ends the second database registration process. Note that the log information storage unit 503 performs formal processing on the status information data included in the record so as to correspond to the data structure of the record in the second status information database 514.

FIG. 11D is a diagram schematically showing a record generated in step SM9 based on the monitoring item of the POS terminal 13: operation process status information data (status information data) of the operation process.
For example, when generating a record based on the monitoring item: operation process of the POS terminal 13, the log information storage unit 503 executes the following processing. That is, the log information storage unit 503 has a formal format for the purpose of supporting the store identification information described in the request data D1, the POS terminal identification information of the POS terminal 13, and the data structure of the second status information database 514. A record is generated in which the operation process status information data subjected to the processing and the classification information indicating the classification determined in step SM8 are associated with each other. As a result, a record shown in FIG. 11D is generated as a record based on the monitoring item: operation process, and stored in the second status information database 514.

  In the second database registration process, the log information storage unit 503 executes the process of the flowchart of FIG. 12 for each of the status information data recorded in the request data D1 to generate a record and store it in the second status information database 514. Execute memory.

As described above, in the present embodiment, the log information storage unit 503 uses the classification information when storing records in the first status information database 513 based on the status information data in the database registration process in step SF2 of FIG. Is not added. On the other hand, when the log information storage unit 503 stores the record in the second status information database 514 based on the status information data, the log information storage unit 503 determines the classification of the status of the monitoring item of the status information data in a predetermined case, and classifies the classification. The classification information shown is added.
By performing such processing, the following effects are obtained.
That is, each record in the first status information database 513 includes data having the same content as the content of the status information data that is the generation source. Therefore, based on the records in the first status information database 513, the status classification of the monitoring items using conditions different from the conditions used for generating the records in the second status information database 514, and the statuses of other monitoring items Analysis becomes possible.
In addition, classification information indicating classification determined by a predetermined method is added to a predetermined record in the second status information database 514. Therefore, based on a predetermined record in the second status information database 514, it is possible to immediately execute processing according to the status category of the corresponding monitoring item, notification of the status classification of the monitoring item, and the like.

  The information added with the classification information and stored in the second status information database 514 corresponds to “status processing information”.

  The operation of each device when the status of the POS terminal 13 and the printing device 14 is managed by the maintenance server 17 has been described above. As described above, the POS terminal 13 generates the log data D11 at intervals, and transmits the request data D1 including the log data D11 as a request. The maintenance server 17 generates records in the first status information database 513 and the second status information database 514 based on the received request data D1, and manages the status of the monitoring items (the status of the POS terminal 13 and the printing device 14). . Furthermore, the maintenance server 17 transmits the response data D2 as a response to the POS terminal 13, and causes the POS terminal 13 to execute necessary processing. Since each apparatus performs such processing, the maintenance server 17 can continuously and efficiently monitor the states of the POS terminal 13 and the printing apparatus 14.

In addition, the processing of the log collection unit 203, the communication management unit 204, and the instruction execution unit 205 has been described.
These functional blocks are configured such that functions can be added by adding plug-ins to programs corresponding to the functional blocks (programs that realize the functions of the functional blocks). With such a configuration, functions can be added as necessary to each of the log collection unit 203, the communication management unit 204, and the instruction execution unit 205 with a flexible and simple means.

Next, the log information display unit 504 provided in the maintenance server 17 will be described.
The log information display unit 504 monitors the designated device (POS terminal 13 or printing device 14) based on the second status information database 514 with respect to a maintenance person (may be another person having authority). Information on the state of the item is notified.
A maintenance person who wants to acquire information on the status of the monitoring item related to the specific POS terminal 13 or the specific printing apparatus 14 starts up the web browser of the terminal in which the web browser is installed, and the maintenance server 17 The predetermined URL is accessed. For example, when the person in charge of maintenance receives a notification from the person in charge of the store that the state of the specific POS terminal 13 or the specific printing device 14 is not a normal state by telephone or e-mail, the above work is performed. I do.
When there is an access to the predetermined URL, the log information display unit 504 transmits a predetermined HTTP file to the terminal after performing necessary authentication, and inputs the POS terminal identification information or the printing apparatus identification information. A possible user interface (web page) is displayed on the terminal. The maintenance staff inputs the POS terminal identification information of the specific POS terminal 13 or the printing apparatus identification information of the specific printing apparatus 14 into the user interface. The log information display unit 504 acquires the POS terminal identification information or the printing apparatus identification information input to the user interface.

Next, the log information display unit 504 refers to the second status information database 514 and based on the acquired POS terminal identification information or printing apparatus identification information, status information of each monitoring item of the corresponding POS terminal 13 or printing apparatus 14 Get the necessary records (including at least the most recently stored records) based on the data.
Next, the log information display unit 504 transmits a predetermined HTTP file to the terminal and causes the terminal to display a user interface (web page, screen) on which the following information regarding the monitoring item is displayed. The log information display unit 504 displays information indicating a monitoring item: communication error and a monitoring item: printer error when a communication error or a printer error has occurred on the user interface. . The maintenance staff can recognize that a communication error or printer error has occurred by referring to the user interface.
In addition, the log information display unit 504 includes a monitoring item: RAM usage rate, a monitoring item: CPU usage rate, a monitoring item: CPU temperature, a monitoring item: data transfer speed, a monitoring item: SSD usage record value, a monitoring item: print head formation. Information indicating the status classification (error status, error warning status, error predictive status, or normal status) of each monitoring item is displayed on the user interface for the cumulative number of lines and monitoring items: cumulative number of cutters used. Further, the log information display unit 504 displays information indicating the status classification (error status or normal status) of each monitoring item on the user interface for the monitoring item: operation process and monitoring item: connected device. To do.
The log information display unit 504 displays information indicating the status classification of these monitoring items based on the corresponding record classification information.
The maintenance staff can recognize the status classification of these monitoring items by referring to the user interface, and can execute corresponding processing based on the recognition.

  As described above, the maintenance staff can recognize the status of the monitoring items of any POS terminal 13 and printing device 14 at any timing by the function of the log information display unit 504.

Next, the monitoring unit 505 provided in the maintenance server 17 will be described.
The monitoring unit 505 is a functional block that monitors whether or not the transmission of the request data D1 (request) is normally performed for the POS terminal 13 provided in the store system 11.

Here, it has a function of transmitting data including predetermined information having at least POS terminal identification information of the POS terminal 13 (hereinafter referred to as “on notification data”) to the maintenance server 17 when the power is turned on. The data corresponds to data indicating that the power is turned on.
In addition, when the POS terminal 13 is turned off, the POS terminal 13 includes the POS terminal identification information of the POS terminal 13 and indicates that the power is turned off (hereinafter referred to as “the power supply is turned off”) before executing the shutdown process corresponding to the power off. , “Off notification data”)) to the maintenance server 17.
In the present embodiment, the monitoring unit 505 efficiently monitors whether or not the transmission of the request data D1 by the POS terminal 13 is normally performed by using the above processing of the POS terminal 13.
In the following description, monitoring whether or not the request data D1 is normally transmitted by the POS terminal 13 by the monitoring unit 505 is referred to as “log communication monitoring”.

FIG. 13A is a flowchart showing the processing of the monitoring unit 505.
As shown in FIG. 13A, the monitoring unit 505 monitors whether or not the ON notification data is received from any POS terminal 13 among the POS terminals 13 to be managed (step SN1).
When the ON notification data is received (step SN1: YES), the monitoring unit 505 accesses the power supply state monitoring database 515, and sets the value of the power supply state information of the record corresponding to the POS terminal 13 that is the transmission source of the ON notification data. A value indicating that the power is on is set (step SN2).

FIG. 14 is a diagram schematically showing the data structure of one record in the power supply state monitoring database 515.
The power supply state monitoring database 515 has a record for each POS terminal 13, and one record includes the store identification information of the store where the POS terminal 13 is provided and the POS terminal of the POS terminal 13 as shown in FIG. 14. The identification information and the power status information are stored in association with each other.
The power state information is information indicating whether or not the POS terminal 13 is in a power-on state, and includes a value indicating that the power is on and a state in which the power is not on. Takes one of the following values.
In step SN2, the monitoring unit 505 identifies a record having the POS terminal identification information included in the ON notification data received in step SN1 among the records in the power supply state monitoring database 515. Next, the monitoring unit 505 sets the value of the power state information of the identified record as a value indicating that the power is on.

FIG. 13B is a flowchart showing processing of the monitoring unit 505.
As shown in FIG. 13B, the monitoring unit 505 monitors whether or not the off notification data is received from any POS terminal 13 among the POS terminals 13 to be managed (step SO1).
When the OFF notification data is received (step SO1: YES), the monitoring unit 505 accesses the power supply state monitoring database 515, and sets the value of the power supply state information of the record corresponding to the POS terminal 13 that is the transmission source of the ON notification data. A value indicating that the power is not turned on is set (step SO2).
In step SO2, the monitoring unit 505 identifies a record having the POS terminal identification information included in the off notification data received in step SO1 among the records in the power supply state monitoring database 515. Next, the monitoring unit 505 sets the value of the power state information of the identified record as a value indicating that the power is not turned on.

  As described above, when the power of one POS terminal 13 is turned on, the value of the power status information of the corresponding record in the power status monitoring database 515 is a value indicating that the power is on. . On the other hand, when the power of the one POS terminal 13 is turned off, the value of the power status information in the corresponding record in the power status monitoring database 515 is a value indicating that the power is not turned on. Therefore, the monitoring unit 505 can monitor whether or not the POS terminal 13 is in a power-on state based on the value of the power state information.

Here, the monitoring unit 505 performs the following processing for each store system 11 (local network LN included in the store system 11), and the POS terminal 13 included in the store system 11 (POS terminal connected to the local network LN). 13) is determined as a target for log communication monitoring.
In the following description, regarding the store system 11, the POS terminal 13 included in the store system 11 is simply subject to log communication monitoring as “the store system 11 is subject to log communication monitoring”.

FIG. 15 is a flowchart illustrating the operation of the monitoring unit 505 when determining whether or not a certain store system 11 is a target for log communication monitoring.
The monitoring unit 505 performs the process shown in the flowchart of FIG. 15 on each store system 11 at a predetermined timing, and determines whether or not the store system 11 is a target for log communication monitoring.
In the description using the flowchart of FIG. 15, the store system 11 to be processed is expressed as a “process target store system”.

As shown in FIG. 15, the monitoring unit 505 determines whether or not the store provided with the processing target store system is a business day (step SP1). The monitoring unit 505 manages business days for each store.
When today is not a business day of the store where the processing target store system is provided (step SP1: NO), the monitoring unit 505 does not set the processing target store system as a target for log communication monitoring (step SP2). Thereafter, the monitoring unit 505 ends the process.

When today is the business day of the store where the processing target store system is provided (step SP1: YES), the monitoring unit 505 is the preparatory period before the business operation time of the store where the processing target store system is provided Or whether it belongs to a time zone reflecting a predetermined margin based on the remaining processing time after business or the like (hereinafter referred to as “business time zone”) (step SP3).
When the current time does not belong to the business hours (step SP3: NO), the monitoring unit 505 does not set the processing target store system as a target for log communication monitoring (step SP2). Thereafter, the monitoring unit 505 ends the process.

  Here, if the store is not a business day, and it is not a business time zone even on a business day, it is assumed that the POS terminal 13 of the store system 11 is not in a power-on state, and therefore the POS terminal 13 is logged. There is no need to monitor communications. In the present embodiment, the monitoring unit 505 determines that the processing target store system is subject to log communication monitoring if the current date and time is not the business day of the corresponding store or the business hours. And not. Thereby, it is possible to prevent the log communication monitoring from being performed on the POS terminal 13 unnecessarily.

When the current time belongs to the business hours (step SP3: YES), the monitoring unit 505 determines that the number of the POS terminals 13 that are turned on among the POS terminals 13 provided in the processing target store system is predetermined. It is determined whether or not the threshold value is below (step SP4).
The monitoring unit 505 acquires the number of POS terminals 13 in a state where power is turned on in the processing target store system based on the power state monitoring database 515.
Here, the predetermined threshold is the minimum number of POS terminals 13 that need to be in a power-on state when a normal business is performed in a store. The predetermined threshold is predetermined and registered for each store system 11.

  When the number of POS terminals 13 in a state where the power is turned on is below a predetermined threshold (step SP4: YES), the monitoring unit 505 does not set the processing target store system as a target for log communication monitoring (step SP5). This is due to the following reason. In other words, the fact that the POS terminal 13 in a state where the power is turned on falls below a predetermined threshold means that the number of POS terminals 13 required for normal business operation is not in a state where the power is turned on, and is normal. This means that business is not possible. In this case, since it is assumed that some kind of trouble has occurred in the store system 11, first, it is necessary to eliminate the trouble that has occurred. Further, even if the store system 11 is targeted for log communication monitoring in a state where a failure has occurred in the store system 11, the accuracy of log communication monitoring is not guaranteed due to the failure that has occurred. Based on the above, when the number of POS terminals 13 that are turned on is below a predetermined threshold, the monitoring unit 505 does not target the store system 11 for log communication monitoring.

  When the processing target store system is not the target of log communication monitoring, the monitoring unit 505 executes a corresponding process (step SP6). Thereafter, the monitoring unit 505 ends the process. In step SP6, for example, the monitoring unit 505 notifies the maintenance staff and other related parties to that effect. For the notification, for example, the monitoring unit 505 displays the store identification information of the store where the processing target store system is provided on a predetermined display device that can be visually recognized by a maintenance person and the POS in a state where power is turned on in the store. Information indicating that the number of terminals 13 is small and a failure may occur is displayed. At the time of notification, for example, the monitoring unit 505 may have a failure due to a small number of store identification information of the store where the processing target store system is provided and the number of POS terminals 13 in a state where power is turned on in the store. An e-mail in which information indicating the presence of the e-mail is described is transmitted to a predetermined destination registered in advance.

  On the other hand, when the number of POS terminals 13 in the power-on state does not fall below a predetermined threshold (step SP4: NO), the monitoring unit 505 sets the processing target store system as a target for log communication monitoring (step SP7). ).

  Next, the monitoring unit 505 for monitoring whether or not the request data D1 is normally transmitted to the POS terminal 13 of the store system 11 subjected to log communication monitoring (log communication monitoring). Will be described.

FIG. 16 is a flowchart showing the operation of the monitoring unit 505 when executing processing related to monitoring of a certain POS terminal 13.
The monitoring unit 505 executes the process shown in the flowchart of FIG. 16 for each of the POS terminals 13 of the store system 11 that are the targets of log communication monitoring, and the transmission of the request data D1 by the POS terminal 13 is normally performed. Monitor whether it is broken.
Note that at the start of the flowchart of FIG. 16, the corresponding POS terminal 13 is not turned on.
In the description using the flowchart of FIG. 16, the processing target POS terminal 13 is expressed as a “processing target POS terminal”.

  In addition, the monitoring unit 505 executes the process illustrated in the flowchart of FIG. 16 for the POS terminal 13 related to the company within the contract period. Thereby, the service provided by the maintenance server 17 can be differentiated between a company within the contract period and a company that is not.

  As shown in FIG. 16, the monitoring unit 505 monitors whether or not the processing target POS terminal is powered on (step SQ1). In step SQ1, the monitoring unit 505 is powered on from the value indicating that the power status information included in the record corresponding to the processing target POS terminal in the power status monitoring database 515 is not in a power-on state. When the value changes to a value indicating the state, it is determined that the processing target POS terminal is powered on.

When the power of the processing target POS terminal is turned on (step SQ1: YES), the monitoring unit 505 sets the processing target POS terminal as a target for monitoring whether or not the transmission of the request data D1 is normally performed. (Step SQ2).
The monitoring unit 505 monitors whether or not the processing target POS terminal to be monitored is in a state where the transmission of the request data D1 is normally performed (step SQ3).
That is, the monitoring unit 505 performs processing for a period longer than a period in which a predetermined margin is reflected in the reference generation interval (the longest interval when the POS terminal 13 related to the company within the contract period generates and transmits the request data D1). When the request data D1 is not transmitted by the target POS terminal (when the request data D1 is not received from the processing target POS terminal), the request data D1 is normally transmitted by the processing target POS terminal. It is determined that there is not. As described above, the POS terminal 13 associated with the company within the contract period transmits the request data D1 at an interval that makes the reference generation interval the longest, so that the reference generation interval exceeds a period reflecting a predetermined margin. This is because if the request data D1 is not transmitted, it is assumed that an error has occurred.

  If the monitoring unit 505 determines that the transmission of the request data D1 by the processing target POS terminal is not in a normal state, the monitoring unit 505 notifies the maintenance staff and other related parties to that effect. For example, the monitoring unit 505 displays information indicating that the transmission of the POS terminal identification information of the processing target POS terminal and the request data D1 is not normally performed on a predetermined display device that can be visually recognized by a maintenance person or the like. indicate. Further, for example, the monitoring unit 505 transmits the POS terminal identification information and an e-mail in which information indicating that the request data D1 is not normally transmitted is described to a predetermined destination registered in advance.

  The monitoring unit 505 monitors whether or not the processing target POS terminal is turned off while monitoring whether or not the transmission of the request data D1 by the processing target POS terminal is normally performed in step SQ3 (step SQ3). SQ4). In step SQ4, the monitoring unit 505 turns on the power from the value indicating that the power supply state information included in the record corresponding to the processing target POS terminal in the power supply state monitoring database 515 indicates that the power supply is turned on. When the value is changed to a value indicating that it is not in the state, it is determined that the processing target POS terminal is turned off.

  When the power is turned off (step SQ4: YES), the monitoring unit 505 removes the processing target POS terminal from the target for monitoring whether or not the transmission of the request data D1 is normally performed (step SQ5). The processing procedure is returned to step SQ1.

As described above, in the present embodiment, the monitoring unit 505 manages whether the POS terminal 13 is powered on by using the POS terminal 13 transmitting the ON notification data and the OFF notification data. To do. When the power is turned on, the monitoring unit 505 monitors whether the request data D1 is normally transmitted. When the power is not turned on, the monitoring unit 505 transmits the request data D1. Does not monitor whether the status is normal.
Thereby, the following effects are produced.
That is, in a store, it is not always possible to make an account at all the cashier counters L, but depending on the time of day and the customer's busyness, the cashier can be made to be in a cashier state or not. It is common. When the cashier counter L cannot be checked, the POS terminal 13 may be turned off. The POS terminal 13 whose power is turned off does not transmit the request data D1, but this is because the request data D1 is not transmitted as a result of the power being intentionally turned off because the POS terminal 13 is not used. Yes, the request data D1 is not transmitted unintentionally due to an error or the like occurring in the POS terminal 13. Based on the above, the POS terminal 13 in the power-on state is monitored as to whether or not the transmission of the request data D1 has been normally performed, thereby determining that the POS terminal 13 is not in a normal state unnecessarily. Thus, the corresponding processing can be prevented from being executed, and the POS terminal 13 that needs to be monitored is monitored, so that the processing efficiency is high.

Next, the operation of the POS terminal 13 when the power of the POS terminal 13 installed in the store is turned on will be described.
FIG. 17 is a flowchart showing the operations of the POS terminal 13 and the store management server 12 when the power is turned on. FIG. 17A shows the operation of the POS terminal 13, and FIG. 17B shows the operation of the store management server 12.

  The cashier person turns on the power of the POS terminal 13 (step S1). In this example, the POS terminal 13 is installed in the cashier counter L, and the cashier person turns on the POS terminal 13 when the store is opened, for example. In the present embodiment, the browser is automatically activated in response to turning on the power of the POS terminal 13.

  As shown in FIG. 17A, the client function unit 202 of the POS terminal 13 accesses a predetermined URL of the store management server 12 in response to the activation of the browser (step SR1). The URL of the store management server 12, the format of data transmitted / received by communication with the store management server 12, and other information necessary for communication with the store management server 12 are registered in the POS terminal 13 in advance. .

  As shown in FIG. 17B, in response to access to a predetermined URL from the POS terminal 13, the accounting related process execution unit 401 of the store management server 12 controls the store management server communication unit 42 to perform a predetermined process. Are transmitted to the POS terminal 13 (step SS1). The predetermined HTML file is an HTML file having a function of displaying at least an accounting user interface 60 described later.

As shown in FIG. 17A, the client function unit 202 of the POS terminal 13 controls the control device communication unit 23 to receive and acquire a predetermined HTML file (step SR2).
Next, the client function unit 202 executes the acquired predetermined HTML file and displays the accounting user interface 60 (FIG. 18) on the touch panel TP (step SR3).

FIG. 18 is a diagram illustrating an example of the accounting user interface 60 displayed on the touch panel TP.
In the accounting user interface 60 of FIG. 18, a list display area 61 is provided in the upper left part, in which a list of product names, product unit prices, and product quantities of products purchased by the customer is displayed. To the right of the list display area 61, there is provided an amount display area 62 for displaying the total amount of products purchased by the customer, the amount of money deposited from the customer at the time of accounting, and the amount of change given to the customer.
Below the list display area 61, there is provided a barcode information display area 63 for displaying barcode information read by the barcode scanner BS (hereinafter referred to as "barcode information"). Bar code information is basically a product code assigned to a product.
A software numeric keypad 64 is provided on the right side of the bar code information display area 63. The software numeric keypad 64 has a confirmation key 641 for confirming the accounting and a subtotal key 642 for instructing a subtotal (calculation of the total amount of products purchased by the customer).

Thereafter, the cashier in charge at the cashier counter L performs accounting using the accounting user interface 60.
As described above, the accounting user interface 60 used for accounting (business) performed by the cashier counter L is automatically displayed on the touch panel TP of the POS terminal 13 in accordance with the power-on of the POS terminal 13. Therefore, the cashier person does not need to perform operations such as inputting the URL of the store management server 12 when the POS terminal 13 is turned on, and the cashier person's work efficiency is high and convenience is high.

  Next, the accounting process performed by the POS terminal 13 in accordance with the accounting at the checkout counter L will be described in detail.

FIG. 19 is a flowchart showing the operation of the POS terminal 13 when executing the accounting process.
As shown in FIG. 19, in the accounting process, the client function unit 202 of the control device control unit 20 of the POS terminal 13 executes a product information acquisition process (step ST1).
In the product information acquisition process, the client function unit 202 communicates with the store management server 12 for each product purchased by the customer, and the product name of the product and the unit price of the product (hereinafter referred to as “product related information”). And executes processing based on the acquired product related information. Hereinafter, the product information acquisition process will be described in detail.

  FIG. 20 is a flowchart showing the operation of the POS terminal 13 and the operation of the store management server 12 when executing the product information acquisition process. FIG. 20A shows the operation of the POS terminal 13, and FIG. 20B shows the operation of the store management server 12.

In the accounting at the cashier counter L, the cashier in charge reads the bar code attached to the product purchased by the customer, the packaging of the product, etc. by the bar code scanner BS (step S2). In response to the reading of the barcode, the barcode scanner BS controls the data from the reading result (hereinafter referred to as “reading result data”) of the POS terminal 13 via the port to which the barcode scanner BS is connected. The data is output to the device / device communication unit 24. The control device device communication unit 24 outputs the read result data to the control device control unit 20.
The read result data is data including information indicating the product code of the product.

As shown in FIG. 20A, the client function unit 202 of the control device control unit 20 of the POS terminal 13 acquires the read result data based on the input from the control device device communication unit 24 (step SU1).
Next, the client function unit 202 acquires a product code based on the read result data (step SU2).
Next, the client function unit 202 displays the product code acquired in step SU2 in the bar code information display area 63 of the accounting user interface 60 (step SU3).
Next, the client function unit 202 controls the control device communication unit 23 to inquire the product name of the product with the product code acquired in step SU2 and the unit price of the product (hereinafter referred to as “product information request data”). ) Is transmitted to the store management server 12 (step SU4).

As shown in FIG. 20B, the transaction related process execution unit 401 of the store management server control unit 40 of the store management server 12 controls the store management server communication unit 42 to receive the product information request data (step). SV1).
Next, the accounting related process execution unit 401 acquires a product code based on the received product information request data, refers to the product master 411 stored in the store management server storage unit 41, and stores the product of the product with the acquired product code. The name and the unit price of the product are acquired (step SV2).
The process of step SV2 corresponds to a process corresponding to a request from the store management server 12 (server).

Next, the accounting-related process execution unit 401 controls the store management server communication unit 42 to transmit the product information response data indicating the product name and the unit price of the product acquired in step SV2 to the POS terminal 13 ( Step SV3).
The merchandise information response data corresponds to the response, and the process of step SV3 corresponds to a process of transmitting a response indicating the processing result of the process corresponding to the request.

As shown in FIG. 20A, the client function unit 202 of the control device control unit 20 of the POS terminal 13 controls the control device communication unit 23 to receive the product information response data (step SU5).
Next, the client function unit 202 acquires the product name of the product and the unit price of the product based on the received product information response data, and stores the product name in the corresponding area of the list display area 61 of the accounting user interface 60. A combination of a product name, a product unit price, and a product quantity is displayed (step SU6).

In the merchandise information acquisition process, the bar code scanner BS reads the barcode for each product purchased by the customer, and the POS terminal 13 and the store management server 12 are read according to the barcode reading. Thus, the processing shown in the flowchart of FIG. 20 is executed.
When the reading of the barcodes of all the products and the processing of each device corresponding to the reading are completed, the product information acquisition processing in step ST1 of FIG. 19 is completed.
When the barcodes of all products are read and the processing of each device according to the reading is completed, the list display area 61 displays a list of combinations of product names, unit prices, and quantities of products purchased by the customer. It becomes a state.

  As shown in FIG. 19, after executing the product information acquisition process of step ST1, the client function unit 202 executes the accounting amount acquisition process (step ST2). In the accounting amount acquisition process of step ST2, the client function unit 202 acquires the total amount of the products purchased by the customer, and acquires the amount of change to be given to the customer according to the customer's payment. The accounting amount acquisition process will be described in detail below.

  FIG. 21 is a flowchart showing the operation of the POS terminal 13 and the corresponding operation of the store management server 12 when executing the transaction amount acquisition process. FIG. 21A shows the operation of the POS terminal 13, and FIG. 21B shows the operation of the store management server 12.

When the reading of the barcodes of all products is completed, the cashier person operates the subtotal key 642 of the software numeric keypad 64 (step S3).
As shown in FIG. 21A, when it is detected that the subtotal key 642 is operated, the client function unit 202 of the control device control unit 20 of the POS terminal 13 generates subtotal calculation request data for requesting subtotal calculation. Then, the control device communication unit 23 is controlled and transmitted to the store management server 12 (step SW1). In response to the transmission of the subtotal calculation request data, the client function unit 202 starts measuring elapsed time.

As shown in FIG. 21B, the transaction related process execution unit 401 of the store management server 12 controls the store management server communication unit 42 to receive subtotal calculation request data (step SX1).
Next, the accounting related process execution unit 401 calculates a subtotal based on the received subtotal calculation request data (step SX2). The accounting related processing execution unit 401 manages the product code of the product purchased by the customer based on the product information response request data received from the POS terminal 13 and other accompanying data. In step SX2, the accounting-related process execution unit 401 refers to the product master 411 as appropriate based on the managed product code, and calculates a subtotal (total amount of products purchased by the customer). The method for calculating the subtotal is not limited to the method described above, and any method may be used.

  Next, the accounting related process execution unit 401 transmits subtotal response data indicating the calculated subtotal to the POS terminal 13 (step SX3).

As shown in FIG. 21A, the client function unit 202 of the control device control unit 20 of the POS terminal 13 controls the control device communication unit 23 to receive subtotal response data (step SW2).
Next, based on the received subtotal response data, the client function unit 202 displays a subtotal (total price of products purchased by the customer) in a corresponding area of the price display area 62 (step SW3).

When the subtotal is displayed in the amount display area 62, the customer hands over money to the cashier. The cashier person receives money from the customer, inputs the amount of money received in the software numeric keypad 64, and operates the confirmation key 641 (step S4). When it is detected that the confirmation key 641 is operated, the client function unit 202 displays the amount of money received from the customer in a corresponding area of the amount display area 62.
Further, when detecting that the confirmation key 641 has been operated, the client function unit 202 transmits change calculation request data for requesting calculation of the change amount to the store management server 12 (step SW4). In response to transmission of the change calculation request data, the client function unit 202 starts measuring elapsed time.

As shown in FIG. 21B, the transaction related process execution unit 401 of the store management server 12 controls the store management server communication unit 42 to receive change calculation request data (step SX4).
Next, the accounting related process execution unit 401 calculates the amount of change (step SX5).
Next, the accounting related process execution unit 401 transmits change response data indicating the calculated change amount to the POS terminal 13 (step SX6).

As shown in FIG. 21A, the client function unit 202 of the POS terminal 13 controls the control device communication unit 23 to receive change response data (step SW5).
Next, the client function unit 202 displays the amount of change in the corresponding area of the amount display area 62 based on the received change response data (step SW6).
The cashier person delivers the change to the customer based on the change amount displayed in the amount display area 62.

  As described above, in the accounting amount acquisition process of step ST2, the client function unit 202 acquires the total amount of the products purchased by the customer, and acquires the amount of change to be delivered to the customer according to the customer's payment.

  As shown in FIG. 19, after executing the transaction amount acquisition process, the client function unit 202 executes a receipt issue process (step ST3). In the receipt issuing process of step ST3, the client function unit 202 communicates with the store management server 12 and issues a receipt on which information related to the product purchased by the customer, information indicating the total price of the product purchased by the customer, and the like are printed. To do. Hereinafter, the receipt issuing process will be described in detail.

  FIG. 22 is a flowchart showing the operation of the POS terminal 13 and the operation of the store management server 12 when executing the receipt issuing process. 22A shows the operation of the POS terminal 13, and FIG. 22B shows the operation of the store management server 12.

As shown in FIG. 22 (A), when the accounting amount acquisition process is completed, the client function unit 202 of the control device control unit 20 of the POS terminal 13 acquires accounting information (step SY1).
The accounting information includes identification information uniquely assigned for each accounting (hereinafter referred to as “accounting identification information”) and information indicating a combination of each product code, product name, unit price, and quantity of the product purchased by the customer ( Hereinafter referred to as “purchased product information”), total purchase amount (subtotal), amount of money received from the customer, and information indicating the amount of change delivered to the customer (hereinafter referred to as “accounting amount information”). And information indicating the time when the transaction was made (hereinafter referred to as “accounting time information”) and store identification information which is the identification information of the store where the transaction was performed.
During the accounting, the client function unit 202 stores the information included in the purchased product information and the information included in the accounting amount information in a predetermined storage area. In step SY1, the client function unit 202 acquires purchased product information and accounting amount information based on the information stored in the predetermined storage area.
Further, the time when the transaction indicated by the transaction time information is performed is the time when the enter key 641 is operated. The time at which the accounting indicated by the accounting time information is performed is not limited to the time at which the confirmation key 641 is operated, but may be any time derived from accounting, such as the time when the barcode of the first product is read during accounting. Good.
Further, the client function unit 202 has a function of generating transaction identification information according to the transaction, and generates the transaction identification information based on the function. The value of the transaction identification information is a unique value for each transaction performed at each store.

  After acquiring the transaction information, the client function unit 202 controls the control device communication unit 23 to transmit the transaction information data indicating the acquired transaction information to the store management server 12 (step SY2).

As shown in FIG. 22B, the transaction related process execution unit 401 of the store management server control unit 40 of the store management server 12 controls the store management server communication unit 42 to receive the transaction information data (step SZ1). ).
Next, the accounting-related process execution unit 401 generates recording data instructing to issue a receipt having a predetermined layout based on the accounting information indicated by the received accounting information data (step SZ2).
The recorded data is in accordance with a predetermined layout, so-called top logo, bottom logo, accounting identification information, time when accounting was performed, product name, unit price, quantity, total purchase price of the product purchased by the customer, and the amount of money received from the customer. This is control data that instructs the issuance of a receipt in which the amount of money, the amount of change delivered to the customer, and the like are recorded. The recording data is an XML document in which information is described according to the XML format.

  Next, the accounting related process execution unit 401 controls the store management server communication unit 42 to transmit the generated recording data to the POS terminal 13 (step SZ3).

Further, after receiving the transaction information data in step SZ1, the transaction related process execution unit 401 accesses the transaction information management database 412 stored in the store management server storage unit 41 (step SZ4).
One record in the transaction information management database 412 stores transaction identification information, purchased product information, transaction amount information, transaction time information, and store identification information in association with each other.
Next, based on the transaction information data received in step SZ1, one item in which transaction identification information, purchased product information, transaction amount information, transaction time information, and store identification information are associated with the transaction information management database 412. Is generated (step SZ5).
As described above, the store management server 12 cumulatively stores the transaction information corresponding to the transaction. Thereby, sales for each store and sales for each product in the store can be managed.

As shown in FIG. 22A, the client function unit 202 of the control device control unit 20 of the POS terminal 13 controls the control device communication unit 23 to receive recording data (step SY3).
Next, the client function unit 202 generates a command command recording command corresponding to the processing control unit 201 based on the XML document recording data (step SY4). The client function unit 202 outputs the generated recording command to the process control unit 201.
Next, the processing control unit 201 controls the control device printing unit 21 based on the generated recording command and issues a receipt (step SY5).
The receipt issued in step SY5 is delivered to the customer by the cashier.

  As described above, in the present embodiment, the POS terminal 13 issues a receipt by performing the accounting process using the function of the store management server 12 according to the accounting. Moreover, the store management server 12 memorize | stores the accounting information based on accounting processing cumulatively.

As described above, the POS terminal 13 according to the present embodiment changes the upper limit value of the number of times of use of the mechanism related to the issuance of a receipt (paper piece) according to the use state of the mechanism, and based on the changed upper limit value. The control device control unit 20 calculates the remaining period during which the mechanism can be used.
According to this configuration, the remaining period of use of the mechanism relating to the issuance of receipts can be accurately determined, reflecting the characteristic that the degree of deterioration of the mechanism relating to the issuance of receipts changes according to the usage status of the mechanism. Can be calculated.

In the present embodiment, the control device control unit 20 calculates the remaining period in which the print head 211 can be used based on the upper limit value of the number of times the print head 211 is used, which is changed according to the use state of the print head 211. .
According to this configuration, it is possible to accurately calculate the remaining usable period of the print head 211 by reflecting the characteristics of the print head 211.

In the present embodiment, the control device control unit 20 calculates the remaining period in which the print head 211 can be used in at least one of the paper quality, type, and thickness of the accommodated roll paper (recording medium). Based on this, the upper limit value of the number of times the print head 211 is used is changed.
According to this configuration, it is possible to accurately calculate the remaining usable period of the print head 211 by reflecting the characteristics of the print head 211.

Moreover, in this embodiment, the control apparatus control part 20 calculates the remaining period which can use the cutter 212 based on the upper limit of the frequency | count of use of the cutter 212 changed according to the usage condition of the cutter 212. FIG.
According to this configuration, the remaining period in which the cutter 212 can be used can be accurately calculated by reflecting the characteristics of the cutter 212.

Further, in the present embodiment, the control device control unit 20 calculates the remaining period in which the cutter 212 can be used, based on at least one of the paper quality, type, or thickness of the accommodated roll paper. Change the maximum number of times you can use
According to this configuration, the remaining period in which the cutter 212 can be used can be accurately calculated by reflecting the characteristics of the cutter 212.

Further, in the present embodiment, the control device control unit 20 transmits information indicating the remaining period in which the calculated mechanism for issuing a receipt can be used to the maintenance server 17 (server).
According to this configuration, the maintenance server 17 can execute processing corresponding to the remaining usable period.

In the present embodiment, the control device control unit 20 calculates the remaining number of days for which the mechanism for issuing a receipt can be used as the remaining period in which the mechanism for issuing a receipt can be used.
According to this configuration, it is possible to provide information that can be easily grasped by humans as “the number of days” as the remaining period during which the mechanism relating to the receipt issuance can be used.

Further, as described above, the POS terminal 13 (control device) according to the present embodiment generates a log data D11 including status information data (status information) indicating the status of a monitoring item whose status is to be monitored. A communication management unit 204 that transmits the log data D11 generated by the collection unit 203 and the log collection unit 203 as a request to the maintenance server 17 (server) and receives the processing command control data D21 (control data) as a response from the maintenance server 17; And the control apparatus control part 20 which has the command execution part 205 which performs a process based on the process command control data D21 which the communication management part 204 received is provided.
According to this configuration, using the configuration in which the log data D11 is transmitted from the POS terminal 13 to the maintenance server 17, the maintenance server 17 sends the processing command control data D21 to the POS terminal 13 as a response to the log data D11. Can be executed.
In other words, for a system that transmits the log data D11 from the POS terminal 13 to the maintenance server 17, processing corresponding to the configuration in which the POS terminal 13 transmits the log data D11 to the maintenance server 17 can be executed.

In the present embodiment, the functions of the log collection unit 203, the communication management unit 204, and the instruction execution unit 205 can be added by adding plug-ins.
According to this configuration, functions can be added as necessary to each of the log collection unit 203, the communication management unit 204, and the instruction execution unit 205 with flexible and simple means.

In the present embodiment, the log collection unit 203 acquires the processing result of the instruction execution unit 205, and generates processing result notification data D12 including information indicating the acquired processing result. The communication management unit 204 transmits the processing result notification data D12 and the log data D11 to the maintenance server 17 as requests.
According to this configuration, the POS terminal 13 can quickly notify the maintenance server 17 of the processing result of the process executed based on the data received from the maintenance server 17.

In the present embodiment, the log collection unit 203 generates log data D11 (sub-log data D11s) related to the printing device 14 (external device) that can communicate with the control device communication unit 23 (communication unit). The communication management unit 204 transmits log data D11 (sub-log data D11s) relating to the printing apparatus 14 generated by the log collection unit 203 to the maintenance server 17.
According to this configuration, the POS terminal 13 can notify the maintenance server 17 of the status of the monitoring items of the printing device 14 connected to the POS terminal 13.

In addition, as described above, the maintenance server 17 (server) according to the present embodiment performs predetermined processing on the POS terminal 13 in response to the log reception unit 501 that receives the log data D11 and the reception of the log data D11. A maintenance server control unit 50 (server control unit) having a response response unit 502 that transmits processing command control data D21 (control data) for executing the response as a response.
According to this configuration, the maintenance server 17 can transmit the processing command control data D21 to the POS terminal 13 as a response in response to the reception of the log data D11, and cause the POS terminal 13 to execute predetermined processing. That is, according to the above configuration, the processing using the configuration in which the POS terminal 13 transmits the log data D11 can be executed on the maintenance server 17 that configures the system that transmits the log data D11 from the POS terminal 13 to the maintenance server 17.

In the present embodiment, the response response unit 502 acquires the execution process information stored in association with the POS terminal identification information (device identification information) included in the received log data D11, and adds the acquired execution process information to the acquired execution process information. Processing instruction control data D21 (control data) for executing the corresponding processing (processing indicated by the execution processing information) is transmitted as a response.
According to this configuration, when a specific process is to be executed by a specific POS terminal 13, the POS terminal identification information of the specific POS terminal 13 is associated with the execution process information corresponding to the predetermined process in advance. If registered in the maintenance server 17, it is possible to cause the POS terminal 13 to execute a predetermined process at a timing when the maintenance server 17 transmits a response.

In addition, the maintenance server 17 according to the present embodiment includes a maintenance server storage unit 51 (server storage unit) that stores information based on the log data D11 received by the log reception unit 501.
According to this configuration, the maintenance server 17 can perform processing based on information based on the stored log data D11.

Further, in the present embodiment, the maintenance server control unit 50 displays a screen on which information based on the log data D11 stored in the maintenance server storage unit 51 is displayed when a request is received from an external device via the global network GN (user A log information display unit 504 for displaying an interface and a web page on an external device.
According to this configuration, the maintenance server 17 can provide useful information regarding the status of the monitoring items of the POS terminal 13 by display.

Further, as described above, the maintenance server 17 (server) according to the present embodiment normally transmits the request data D1 with the POS terminal 13 (control device) in a power-on state being monitored. A maintenance server control unit 50 having a monitoring unit 505 for monitoring whether or not it is in a broken state is provided.
According to this configuration, the POS terminal 13 in a state where the power is turned on is a target for monitoring whether or not the transmission of the request data D1 is normally performed, so that it is necessary to be a target for monitoring. Since the terminal 13 is a monitoring target, the processing efficiency is good and the processing load on the maintenance server 17 can be reduced.

In this embodiment, the monitoring unit 505 receives the data indicating that the power is turned on from the POS terminal 13 and then receives the data indicating that the power is turned off until the POS terminal 13 is received. Target for monitoring.
According to this configuration, the maintenance server 17 uses the data received from the POS terminal 13 to accurately determine the POS terminal 13 in a power-on state, and makes the POS terminal 13 a monitoring target. Can do.

In the present embodiment, the monitoring unit 505 notifies the fact that the transmission of the request data D1 by the monitored POS terminal 13 is not normally performed.
According to this configuration, the person in charge can recognize that the transmission of the request data D1 is not normally performed.

In the present embodiment, the monitoring unit 505 acquires the number of POS terminals 13 that are turned on among the plurality of POS terminals 13 connected to the local network LN, and the acquired number is a predetermined threshold value. If the value is less than, the plurality of POS terminals 13 connected to the local network LN are not monitored.
According to this configuration, when the number of POS terminals 13 that are turned on among the POS terminals 13 connected to the local network LN falls below a predetermined threshold, the POS terminals 13 are set as monitoring targets. Can not.

In the present embodiment, the monitoring unit 505 does not monitor a plurality of POS terminals 13 connected to the local network LN during a predetermined time period.
According to this configuration, it is possible to prevent the POS terminal 13 from being monitored in a predetermined time period according to the actual use of the POS terminal 13.

Further, as described above, in the network system 1 according to the present embodiment, the POS terminal 13 (control device) includes log data including status information data (status information) indicating the status of the monitoring item to be monitored. D11 is generated, and the log data D11 generated at a predetermined interval is transmitted as a request to the maintenance server 17 (server). The maintenance server 17 stores a contract management database 512 (contract period information) indicating a period during which the function of the maintenance server 17 can be used by the POS terminal 13 by contract, and when the log data D11 is received, the contract management of the POS terminal 13 Based on the database 512, it is determined whether or not it is within the contract period. If it is not within the contract period, a response including information indicating that it is not within the contract period is transmitted to the POS terminal 13 and is within the contract period. In this case, a response including information indicating that it is within the contract period is transmitted to the POS terminal 13. When the POS terminal 13 receives a response including information indicating that it is not within the contract period, the interval for transmitting the log data D11 is set longer than a predetermined interval.
According to this configuration, the interval at which the POS terminal 13 related to the company not within the contract period transmits the request data D1 is made longer than the interval at which the POS terminal 13 related to the company within the contract period transmits the request data D1. Thus, it is possible to suppress the consumption of resources due to the transmission of the request data D1 by the POS terminal 13 related to a company that is not within the contract period, and it is possible to differentiate the response between the contracted company and the other company , Can ensure fairness. That is, according to the above configuration, the POS terminal 13 uses the function of the maintenance server 17 in a period other than the period based on the contract for a system in which the period during which the POS terminal 13 can use the function of the maintenance server 17 is determined by the contract. The process corresponding to the case where it is going to be performed can be performed.

In the present embodiment, the POS terminal 13 makes the interval for transmitting the log data D11 longer than a predetermined interval in response to receiving a response including information indicating that it is not within the period indicated by the contract period information. When a response including information indicating that it is within the contract period is received, the interval for transmitting the log data D11 is set as a predetermined interval.
According to this configuration, it is possible to prevent the interval at which the log data D11 is transmitted for the POS terminal 13 related to the company within the contract period from becoming longer than the predetermined interval.

In the present embodiment, when the POS terminal 13 generates the log data D11, the POS terminal 13 stores the generated log data D11 and transmits the stored log data D11. After the log data D11 is transmitted, the POS terminal 13 stores the log data stored when the response received from the maintenance server 17 according to the transmission of the log data D11 includes information indicating that it is within the contract period. When D11 is deleted and information indicating that the response is not within the contract period is included, the stored log data D11 is not deleted, but is a target to be transmitted when the next request is transmitted. When the maintenance server 17 receives the log data D11, the maintenance server 17 determines whether it is within the contract period based on the contract management database 512. If it is within the contract period, the maintenance server 17 acquires the log data D11 and acquires the acquired log data. Information based on D11 is stored, and if it is not within the contract period, information based on log data D11 is not stored.
According to this configuration, the maintenance server 17 is prevented from storing information based on the log data D11 related to the company not within the contract period, and is caused by the transmission of the request data D1 by the POS terminal 13 related to the company not within the contract period. It is possible to reduce the consumption of resources to be used, and to differentiate between the contracted company and the non-contracted company.

Further, as described above, in the present embodiment, the POS terminal 13 (control device) stores the log data D11 including the status information data (status information) indicating the status of the monitoring item whose status is to be monitored at a predetermined interval. The generated log data D11 is transmitted as a request to the maintenance server 17 (server). The POS terminal 13 sets the interval for generating the log data D11 to be shorter than the predetermined interval when there is a high possibility that the state of the predetermined monitoring item becomes an error state.
According to this configuration, the POS terminal 13 can notify the maintenance server 17 of the monitoring item status at a short interval with respect to the monitoring item that is likely to be in an error state. Can be monitored at intervals as short as possible, and corresponding processing can be performed as necessary. That is, according to the above configuration, for the system that transmits the log data D11 from the POS terminal 13 that is the client to the maintenance server 17, the processing corresponding to the configuration in which the log data D11 is transmitted from the POS terminal 13 to the maintenance server 17 is executed. it can.

In the present embodiment, the POS terminal 13 determines that the state of the monitoring item is in a state where the relationship between the numerical value related to the status information data of the monitoring item included in the generated log data D11 and the predetermined threshold value is a predetermined relationship. It is determined that there is a high possibility of an error state, and the interval for generating the log data D11 is made shorter than a predetermined interval.
According to this configuration, the POS terminal 13 can accurately determine whether or not the state of the monitoring item is likely to be an error state.

In the present embodiment, the maintenance server 17 receives the log data D11, and the relationship between the numerical value related to the status information data of the monitoring item included in the received log data D11 and the predetermined threshold value is a predetermined relationship. In this case, a response including information indicating that the monitoring item is likely to be in an error state is transmitted to the POS terminal 13. When the POS terminal 13 receives a response including information indicating that there is a high possibility of being in an error state, the POS terminal 13 determines that there is a high possibility of being in an error state, and sets an interval for generating log data D11 to be greater than a predetermined interval. shorten.
According to this configuration, the maintenance server 17 can accurately determine whether or not the monitoring item is likely to be in an error state, and the POS terminal 13 uses the determination result of the maintenance server 17. Thus, it is possible to determine whether or not the state of the monitoring item is likely to be an error state.

Further, in the present embodiment, the POS terminal 13 sets the interval for generating the log data D11 when the possibility that an error state is not high after the interval for generating the log data D11 is made shorter than the predetermined interval. The interval of
According to this configuration, it is possible to prevent the POS terminal 13 from transmitting the log data D11 at an unnecessarily short interval.

Further, as described above, in the present embodiment, the POS terminal 13 (control device) generates log data D11 including status information data (status information) indicating the status of the monitoring item to be monitored, The generated log data D11 is transmitted to the maintenance server 17 as a request. When the maintenance server 17 receives the log data D11, the maintenance server 17 transmits a corresponding request, stores the status information data included in the received log data D11 in the first status information database 513 (first database), and receives the received log Based on the status information data included in the data D11, the classification of the state of the monitoring item is determined, status processing information including information indicating the classification is generated, and stored in the second status information database 514 (second database).
According to this configuration, based on each record in the first status information database 513, the classification of the state of the monitoring item using a condition different from the condition used for generating the record in the second status information database 514, and other monitoring The status of items can be analyzed. Furthermore, classification information indicating classification determined by a predetermined method is added to a predetermined record in the second status information database 514. Therefore, based on a predetermined record in the second status information database 514, it is possible to immediately execute processing according to the status category of the corresponding monitoring item, notification of the status classification of the monitoring item, and the like.

In the present embodiment, the maintenance server 17 identifies the monitoring item based on the status identification information included in the status information when generating the status processing information, and classifies the status of the monitoring item by a method corresponding to the monitoring item. Determine.
According to this configuration, the maintenance server 17 can classify the state of the monitoring item by a method corresponding to the monitoring item after accurately identifying the monitoring item using the status identification information.

Further, in the present embodiment, when the status processing information is generated, the maintenance server 17 indicates that the value of the status identification information included in the status information data is information in which the status information data represents the state of the monitoring item by a numerical value. If it is a value, the classification of the state of the monitoring item is determined based on the relationship between the numerical value representing the state of the monitoring item and a predetermined threshold.
According to this configuration, the maintenance server 17 can accurately determine the classification of the status of the monitoring item.

In the present embodiment, when the status processing information is generated, the maintenance server 17 indicates that the value of the status identification information included in the status information data is information in which the status information data represents the state of the monitoring item by a character string. In the case of the indicated value, the state classification of the monitoring item is determined based on the content of the character string representing the state of the monitoring item.
According to this configuration, the maintenance server 17 can accurately determine the classification of the status of the monitoring item.

  Further, in the present embodiment, when the status processing information is generated, the maintenance server 17 does not require the status identification information value included in the status information data to determine the status classification of the monitoring item based on the status information data. In the case of the value indicating status information, status processing information not including classification information is stored in the second status information database 514 (second database).

The above-described embodiment is merely an aspect of the present invention, and can be arbitrarily modified and applied within the scope of the present invention.
Further, for example, in the above-described embodiment, the invention has been described by exemplifying the case where the store system 11 is applied to a store, but the facility to which the store system 11 is applied is not limited to a store.
Further, for example, any method may be used as a communication method for each device constituting the network system 1.
In the above-described embodiment, the recording method of the POS terminal 13 is the thermal method, but any recording method may be used.
Further, for example, each functional block described with reference to the drawings can be arbitrarily realized by hardware and software, and does not suggest a specific hardware configuration.
Moreover, the functional block shown in the functional block diagram shows the functional configuration of each device, and does not limit a specific mounting form. In other words, it is not necessary to implement hardware corresponding to the functional blocks in the figure, and it is of course possible to adopt a configuration in which the functions of a plurality of functional units are realized by one processor executing a program. In addition, in the above embodiment, a part of the function realized by software may be realized by hardware, or a part of the function realized by hardware may be realized by software.

  DESCRIPTION OF SYMBOLS 1 ... Network system, 13 ... POS terminal (control apparatus, printing apparatus), 14 ... Printing apparatus, 17 ... Maintenance server (server).

Claims (7)

A control device that transmits a request; and a server that is connected to the control device via a network and that transmits a response in response to reception of the request;
The controller is
Generating log data including status information indicating the status of the monitoring item to be monitored, and transmitting the generated log data to the server as a request;
The server
When receiving the log data, send the corresponding request,
Storing the status information included in the received log data in a first database;
A network that determines a status classification of the monitoring item based on the status information included in the received log data, generates status processing information including information indicating the classification, and stores the status processing information in a second database system. The controller is
The status information of the monitoring item includes status identification information for identifying the monitoring item,
The server
When generating the status processing information, the monitoring item is identified based on the status identification information included in the status information, and the state classification of the monitoring item is determined by a method corresponding to the monitoring item. The network system according to claim 1. The server
When generating the status processing information, when the value of the status identification information included in the status information is a value indicating that the status information is information representing the state of the monitoring item by a numerical value,
The network system according to claim 2, wherein a classification of the state of the monitoring item is determined based on a relationship between a numerical value representing the state of the monitoring item and a predetermined threshold value. The server
When generating the status processing information, when the value of the status identification information included in the status information is a value indicating that the status information is information indicating the state of the monitoring item by a character string,
The network system according to claim 2 or 3, wherein a classification of the state of the monitoring item is determined based on a content of a character string representing the state of the monitoring item. The server
When generating the status processing information, when the value of the status identification information included in the status information is a value indicating that it is not necessary to determine the status classification of the monitoring item based on the status information,
The network system according to any one of claims 2 to 4, wherein the status processing information not including information indicating classification is stored in the second database. A server that generates log data including status information indicating a status of a monitoring item to be monitored, and that can be connected via a network to a control device that transmits the generated log data as a request;
When receiving the log data, send the corresponding request,
Storing the status information included in the received log data in a first database;
A server that determines a status classification of the monitoring item based on the status information included in the received log data, generates status processing information including information indicating the classification, and stores the status processing information in a second database . A control method of a network system comprising: a control device that transmits a request; and a server that is connected to the control device via a network and transmits a response in response to reception of the request,
The controller is
Generating log data including status information indicating the status of the monitoring item to be monitored, and transmitting the generated log data to the server as a request;
The server
When receiving the log data, send the corresponding request,
Storing the status information included in the received log data in a first database;
A network that determines a status classification of the monitoring item based on the status information included in the received log data, generates status processing information including information indicating the classification, and stores the status processing information in a second database How to control the system.

Images