WO2017022602A1 - Information processing device, program, printer, and information processing system - Google Patents

Abstract

This information processing device is connected to printers and is capable of accessing a storage device that stores address information associated with event identification information, which identifies an event that has occurred in a printer. The information processing device comprises: an acquisition means that acquires event identification information from a printer; and a transmission means that transmits a notification in response to an event identified by event identification information to an address indicated by address information among the address information stored in the storage device, said address information being associated with the event identification information acquired by the acquisition means.

Description

Information processing apparatus, program, printer, information processing system

The present invention relates to an information processing apparatus, a program, a printer, and an information processing system.

In general, many printers are used in company factories and offices. In such printers used by companies, the individual operating rate of each printer affects the business efficiency of the company. Therefore, it is important to suppress the decrease in the operating rate.
As a factor that lowers the operating rate, there is a printer stop due to an abnormality. Therefore, in order to suppress a decrease in the operating rate of the printer, it is important to shorten the printer stop time due to an abnormality.

On the other hand, conventionally, a system including a printer and a server connected to the printer is known. For example, Japanese Patent Laid-Open No. 2000-047841 discloses a technique in which a server causes another label printer to continue issuing a label when the label issuance by the label printer is interrupted.

However, the technique disclosed in Japanese Patent Laid-Open No. 2000-047841 does not execute a process for eliminating the abnormality of the label printer that interrupts the label issuance, so the stop time of the label printer cannot be shortened.
Further, in the technique disclosed in Japanese Patent Application Laid-Open No. 2000-047841, the error is not resolved until a person in charge having knowledge necessary for eliminating the abnormality notices the occurrence of the abnormality.
Therefore, even if other label printers continue to issue labels, the operation rate of the label printer that interrupts label issuance decreases. As described above, the conventional technology cannot suppress a decrease in the operating rate of the printer.

An object of the present invention is to suppress a decrease in the operation rate of the printer.

One aspect of the present invention is an information processing apparatus that is connected to a printer and that can access a storage device that stores destination information associated with event identification information that identifies an event that has occurred in the printer.
Obtaining means for obtaining the event identification information from the printer;
Transmission means for transmitting a notification corresponding to the event identified by the event identification information to the destination indicated by the destination information corresponding to the event identification information acquired by the acquisition means among the destination information stored in the storage device When,
Is an information processing apparatus.

According to the present invention, it is possible to suppress a decrease in the operating rate of the printer.

The figure which shows the structure of the information processing system of this embodiment. FIG. 2 is a diagram illustrating a configuration of a management server 10, a label printer 30, and a client terminal 50 in FIG. The figure which shows the structure of the data table memorize | stored in the memory | storage device 12 of FIG. The figure which shows the structure of the data table memorize | stored in the memory | storage device 12 of FIG. FIG. 10 is a sequence diagram of destination information registration processing according to the embodiment. The figure which shows an example of the display screen displayed in the process of FIG. The sequence diagram of the process of the notification of this embodiment. The figure which shows an example of the display screen displayed in the process of FIG.

(1) Configuration of information processing system (Figs. 1 and 2)
The information processing system of this embodiment will be described.
FIG. 1 is a diagram illustrating a configuration of an information processing system according to the present embodiment. FIG. 2 is a diagram illustrating the configuration of the management server 10, the label printer 30, and the client terminal 50 of FIG.

As shown in FIG. 1, the information processing system 1 includes a management server 10 and a plurality of label printers 30-1 to 30-n (hereinafter referred to as each label printer 30-1 to 30-n in common). "Label printer 30"), a plurality of client terminals 50-1 to 50-n (hereinafter referred to as "client terminal 50" when referring to each of the client terminals 50-1 to 50-n in common), Is provided.
The management server 10, the label printer 30, and the client terminal 50 can communicate with each other via a network NW (for example, the Internet).

The management server 10 has a function of transmitting a notification corresponding to an event that has occurred in the label printer 30 to the client terminal 50.
The label printer 30 has a function of printing information on a label and a function of transmitting log data of the label printer 30 to the management server 10. The information printed on the label is, for example, text, a barcode, an image, or a combination thereof.
The client terminal 50 has a function of accepting user instructions and a function of presenting various information to the user. The client terminal 50 is, for example, a computer, a tablet terminal, a smartphone, or the like.

(1-1) Configuration of Management Server As shown in FIG. 2, the management server 10 includes a CPU (Central Processing Unit) 11, a storage device 12, and a communication interface 13.

The storage device 12 includes, for example, a ROM (Read Only Memory), a RAM (Random Access Memory), and a storage. The storage device 12 is referred to by an operating system (hereinafter referred to as “OS”) program of the management server 10, an application program (hereinafter referred to as “server application”) for realizing the function of the management server 10, and the CPU 11. And data generated by the CPU 11 are stored.

The CPU 11 realizes the server application function by executing the server application program stored in the storage device 12.

The communication interface 13 controls communication between the management server 10 and the label printer 30 and the client terminal 50. The communication interface 13 is a wired interface, a wireless interface, or a combination thereof.

(1-2) Configuration of Label Printer As shown in FIG. 2, the label printer 30 includes a CPU 31, a storage device 32, an input device 33, a display device 34, a printing unit 35, and a communication interface 36. Prepare.

The storage device 32 includes, for example, a ROM, a RAM, and an EEPROM (Electrically Erasable Programmable Read-Only Memory). The storage device 32 stores a program of an application (hereinafter referred to as “firmware”) for controlling the operation (for example, printing operation) of the label printer 30, data referred to by the CPU 31, and data generated by the CPU 31 (for example, , Which will be described later).

The CPU 31 implements a firmware function by executing a firmware program stored in the storage device 32.

The input device 33 is, for example, a hard key, a touch panel, or a combination thereof.

The display device 34 is, for example, a liquid crystal display.

The printing unit 35 is a mechanism for printing information on a label. The print unit 35 includes, for example, a paper storage unit, a platen roller, and a print head.
The paper storage unit stores roll-shaped continuous paper. The continuous paper is, for example, a plurality of labels temporarily attached to a mount. The label has an adhesive surface and a printing surface.
The platen roller has a function of conveying continuous paper. The platen roller rotates according to firmware control. When the platen roller rotates, the continuous paper is fed out from the paper storage unit. The continuous paper fed out from the paper storage unit is conveyed by the rotation of the platen roller.
The print head has a function of printing information on a label. The print head may print information by applying heat to the label, or may print information using an ink ribbon.
The cutter has a function of separating a label on which information is printed from a plurality of labels constituting the continuous paper from the continuous paper. When information is printed on the label, the cutter comes into contact with the label and a label on which no information is printed. As a result, the label on which the information is printed is separated from the continuous paper.
A label, an ink ribbon, a platen roller, a print head, and a cutter are consumables (an example of parts) that are consumed with use. The remaining amount of the label, the remaining amount of the ink ribbon, the remaining amount of the platen roller, the remaining amount of the print head, and the remaining amount of the cutter are determined by various sensors (for example, optical sensors) or counters provided in the label printer 30. Detected.

The communication interface 36 controls communication between the label printer 30, the management server 10, and the client terminal 50. The communication interface 36 is a wired interface, a wireless interface, an NFC (Near Field Communication) interface, or a combination thereof.

The CPU 31 stores log data including information regarding the state of the label printer 30 in the storage device 32 at regular intervals. When an event occurs in the label printer 30, the CPU 31 consumes the time when the event occurs (hereinafter referred to as “event occurrence time”), an event code that identifies the event, and a consumable that is attached to the label printer 30. The product code and setting information are included in the log data. For example, the CPU 31 extracts a consumable code stored in an IC chip embedded in the consumable, and includes the extracted consumable code in the log data.
The CPU 31 transmits this log data to the management server 10.
“Setting information” includes, for example, the following information.
Operation mode: For example, information indicating whether the operation mode of the label printer 30 is a normal mode in which power consumption is not limited or a power save mode in which power consumption is limited.
Continuous operation time: Information indicating the elapsed time since the label printer 30 was turned on.
Firmware version: Firmware version information.
-Conveyance speed: Setting value related to the speed at which the platen roller conveys the print medium.
• Print density: A setting value related to the density of information printed on the label by the print head.
Sensor type: The type of sensor that specifies the position of the label (for example, a sensor that specifies the position of the label based on the eye mark provided on the continuous paper, or based on the mount portion exposed between a plurality of labels) Information indicating which of the sensors identifies the position of the label).
-Printing mode: Indicates whether the mode is a peeling mode in which the label is peeled off from the mount every time information is printed on one label, or a continuous mode in which information is printed on a predetermined number of labels without peeling off the label. information.
・ Total travel distance: Cumulative value of the rotation distance of the platen roller ・ Number of print head replacements: Cumulative value of the number of print head replacements ・ Cutter replacement number: Cumulative value of the number of cutter replacements ・ Number of platen roller replacements ... Cumulative value of the number of times the platen roller has been replaced

(1-3) Configuration of Client Terminal As shown in FIG. 2, the client terminal 50 includes a CPU 51, a storage device 52, an input device 53, a display device 54, and a communication interface 55.

The storage device 52 includes, for example, a ROM, a RAM, and a storage. The storage device 52 stores an OS program of the client terminal 50, an application (for example, browser) program, data referred to by the CPU 51, and data generated by the CPU 51.

The CPU 51 implements the function of the client terminal 50 by executing a program stored in the storage device 52.

The input device 53 is, for example, a keyboard, a touch panel, or a combination thereof.

The display device 54 is, for example, a liquid crystal display.

The communication interface 55 controls communication between the client terminal 50, the management server 10, and the label printer 30. The communication interface 55 is a wired interface, a wireless interface, or a combination thereof.

(2) Data table configuration (Figs. 3-4)
The configuration of the data table stored in the storage device 12 of this embodiment will be described.
3 and 4 are diagrams showing the configuration of the data table stored in the storage device 12 of FIG.

(2-1) Configuration of User Data Table As shown in FIG. 3, each record (hereinafter referred to as “user record”) of the user data table TBL1 stores information about the user (hereinafter referred to as “user information”). . The user data table TBL1 is updated by the management server 10 based on a user instruction.
The user data table TBL1 includes a “user ID” field, a “printer ID” field, a “model” field, a “printer name” field, and a “location” field.
A “user” is a user registered in the management server 10 as a user of the label printer 30. The user who actually uses the label printer 30 and the registered user may be the same or different. The user ID may be owned by one user or shared by a plurality of users.

In the “user ID” field, a user ID for identifying the user of the label printer 30 is stored. The user ID in the “user ID” field is a primary key that identifies a user record. The user ID may be information arbitrarily determined by the user (for example, an email address), or may be information randomly determined by the management server 10.

In the “printer ID” field, a printer ID for identifying the label printer 30 registered by the user is stored. The printer ID may be information determined randomly by the management server 10 or may be a serial code unique to the label printer 30.

In the “model” field, a model code indicating the model of the label printer 30 is stored. Information in the “model” field is predetermined information.

In the “printer name” field, the name of the label printer 30 registered by the user (hereinafter referred to as “printer name”) is stored. The printer name is information (for example, text information) arbitrarily determined by the user. The “printer name” field is associated with the “printer ID” field. That is, the user can register a printer name for each label printer 30.

In the “location” field, information indicating a location where the label printer 30 registered by the user is used (hereinafter referred to as “location information”) is stored. The location information is information (for example, text information) arbitrarily determined by the user. The “location” field is associated with the “printer ID” field. That is, the user can register location information for each label printer 30.

(2-2) Configuration of Address Data Table As shown in FIG. 3, each record of the address data table TBL 2 (hereinafter referred to as “address record”) is a candidate for a notification destination regarding an event that has occurred in the label printer 30. Information relating to the address (hereinafter referred to as “address information”) is stored. The address data table TBL2 is updated by the management server 10 based on a user instruction.
Address data table TBL2 includes an “address” field, a “destination name” field, and a “group” field.
The log data table TBL5 is associated with the user ID (that is, the address data table TBL2 is provided for each user).

In the “address” field, addresses that are candidates for the notification destination are stored. The address is, for example, a mail address indicating a destination of an e-mail, a mobile phone number indicating a destination of SMS (Short Message Service), a user ID indicating a destination of a message service other than e-mail and SMS, and the like. The address is information arbitrarily determined by the user.

The “Destination name” field stores the owner name of the address. The owner name is information (for example, text information) arbitrarily determined by the user.

In the “Group” field, the group name to which the address belongs is stored. The group name is information (for example, text information) arbitrarily determined by the user.

(2-3) Structure of Event Data Table As shown in FIG. 3, each record (hereinafter referred to as “event record”) of the event data table TBL3 stores information related to the event. The event record is stored in the storage device 12 in advance. The event record is stored in the storage device 12 in advance.
The event data table TBL3 includes an “event code” field, an “event name” field, an “event type” field, a “content” field, and a “measure” field.

The event code is stored in the “event code” field. The event code in the “event code” field is a primary key for identifying the event record.

The event name is stored in the “event name” field. The event name in the “event name” field is predetermined information (for example, text information).

In the “event type” field, a type code indicating the type of event is stored. The type code in the “event type” field is predetermined information.

The type code “A” means an alert. “Alert” means that although the operation of the label printer 30 is not stopped immediately, a factor that hinders the operation of the label printer 30 has occurred.
For example, the alert includes the following events.
Event name “cleaning” (event code “# 1001”): A predetermined time (for example, one week) has elapsed since the label printer 30 was cleaned.
Event name “Cutter replacement” (event code “# 1002”): The number of times the cutter has been used (for example, a value detected by a cutter counter provided in the label printer 30) has reached a predetermined number.
Event name “Replace platen roller” (event code “# 1003”): The rotation distance of the platen roller (for example, a value detected by a roller counter provided in the label printer 30) has reached a predetermined distance.
Event name “print head replacement” (event code “# 1004”): the cumulative distance of the continuous paper that has passed through the print head (for example, a value detected by a head counter provided in the label printer 30) is a predetermined distance. What has been reached.
The predetermined time, the predetermined number of times, and the predetermined distance may be fixed values or values arbitrarily determined by the user.

The type code “E” means an error. “Error” means that a factor that causes the operation of the label printer 30 to stop immediately (that is, a factor that is more severe than an alert for the operation of the label printer 30) has occurred.
For example, the error includes the following events.
Event name “label end” (event code “# 2001”): The remaining amount of continuous paper (for example, a value detected by a sensor provided in the label printer 30) has become zero.
Event name “ribbon end” (event code “# 2002”): the remaining amount of ink ribbon (for example, a value detected by a sensor provided in the label printer 30) has become zero.
• Event name “Print head error” (event code “# 2003”): An error occurred in the print head. The print head error is detected by, for example, a head check circuit provided in the label printer 30.
Event name “Cutter error” (event code “# 2004”): The cutter position (for example, a position detected by a sensor provided in the label printer 30) is not a predetermined position.
Event name “overheat” (event code “# 2005”): the temperature in the casing of the label printer 30 (for example, a value detected by a temperature sensor provided in the label printer 30) is equal to or higher than a predetermined temperature.
Event name “jam” (event code “# 2006”): The continuous paper is out of the predetermined transport path (that is, the continuous paper is jammed in the label printer 30). The jam is detected by, for example, a sensor provided in the label printer 30.
Event name “imitation” (event code “# 2007”). The consumables attached to the label printer 30 are predetermined consumables (for example, consumables manufactured by the manufacturer of the label printer 30 or the label printer 30). Consumables recommended by the manufacturer). The imitation is detected by the CPU 31 based on the consumable code stored in the IC chip provided in the consumable.
Event name “size error” (event code “# 2008”): The size of the continuous paper attached to the paper storage unit is not a size that the label printer 30 can handle. The size error is detected by, for example, a sensor provided in the label printer 30.
Event name “Non-lock error” (event code “# 2009”): The opening / closing cover attached to the casing of the label printer 30 is not locked. The non-lock error is detected by, for example, a sensor provided in the label printer 30.

The type code “W” means a warning. “Warning” means that the remaining amount of consumables in the label printer 30 has become a predetermined value or less (that is, the time to replace the consumables in the label printer 30 is approaching).
For example, the warning includes the following events.
Event name “Ribbon Near End” (event code “# 3001”): The remaining amount of ink ribbon (for example, a value detected by a sensor provided in the label printer 30) is equal to or less than a predetermined value.
Event name “paper near end” (event code “# 3002”): the remaining amount of continuous paper (for example, a value detected by a sensor provided in the label printer 30) is equal to or less than a predetermined value.
The predetermined value may be a fixed value or a value arbitrarily determined by the user.

In the “Content” field, information indicating the content of the event is stored. The information in the “content” field is predetermined information (for example, text information).

In the “Countermeasure” field, information indicating a countermeasure for solving the event is stored. The information in the “measure” field is predetermined information (for example, text information).

(2-4) Configuration of Destination Data Table As shown in FIG. 4, each record (hereinafter referred to as “destination record”) of the destination data table TBL4 stores information about the destination. The destination data table TBL4 is updated by the management server 10 based on a user instruction.
The destination data table TBL4 includes an “event code” field and a “destination” field.
The destination data table TBL4 is associated with the printer ID (that is, the destination data table TBL4 is provided for each label printer 30).

The event code is stored in the “event code” field. The event code in the “event code” field is a primary key for specifying the destination record.

• At least one address is stored in the “destination” field. The address in the “destination” field indicates a notification destination when an event identified by the event code in the “event code” field occurs.

(2-5) Structure of Log Data Table As shown in FIG. 4, the log data of the label printer 30 is stored in each record of the log data table TBL5 (hereinafter referred to as “log record”). The log data table TBL5 is updated by the management server 10 based on the log data transmitted by the label printer 30.
The log data table TBL5 includes a “time” field, an “event code” field, a “consumables code” field, and a “setting” field.
The log data table TBL5 is associated with the printer ID (that is, the log data table TBL5 is provided for each label printer 30).

In the “time” field, information indicating the event occurrence time is stored. The information in the “time” field is a primary key that identifies a log record. If no event has occurred (that is, “NONE” is stored in an “event code” field described later), the information in the “time” field is information indicating the time of the log data.

In the “event code” field, an event code for identifying an event that has occurred in the label printer 30 is stored. “NONE” means that no event has occurred.

In the “consumable code” field, a consumable code for identifying a consumable that is attached to the label printer 30 is stored. “H0001” is an identification code for identifying the print head. “R0001” is an identification code for identifying the platen roller. “L0001” is an identification code for identifying continuous paper. “C0001” is an identification code for identifying a cutter. “UNKNOWN” means that the consumable code taken out of the consumables attached to the label printer 30 is an unknown code, or that the consumable codes could not be taken out from the consumables.

In the “setting” field, setting information of the label printer 30 is stored.

(3) Information Processing Flow The information processing flow of this embodiment will be described.

(3-1) Address information registration processing (FIGS. 5 to 6)
A destination information registration process according to this embodiment will be described.
FIG. 5 is a sequence diagram of destination information registration processing according to this embodiment. FIG. 6 is a diagram illustrating an example of a display screen displayed in the process of FIG.
In FIG. 5, the processing of the management server 10 is executed by the function of the server application. The processing of the client terminal 50 is executed by the browser function.

As shown in FIG. 5, first, the client terminal 50 receives a request for registration of destination information (S500).
Specifically, the CPU 51 receives a user instruction via the input device 53.
Next, the CPU 51 generates a request REQ10 for registering destination information in the management server 10 based on the received user instruction. The request REQ10 includes a user ID that identifies the user who has given the instruction.
Next, the CPU 51 transmits the generated request REQ10 to the management server 10 via the communication interface 55.

The management server 10 transmits screen data based on the request REQ10 to the client terminal 50 (S100).
Specifically, the CPU 11 receives the request REQ10 transmitted in S500 via the communication interface 13.
Next, the CPU 11 refers to the user record specified by the user ID included in the received request REQ10 in the user data table TBL1.
Next, the CPU 11 refers to the information of the referred user record, and generates screen data of a screen that accepts designation of a printer (hereinafter referred to as “target printer”) that is a destination information registration process. The screen data is, for example, HTML (HyperText Markup Language) data. The screen data includes a printer name in the “printer name” field and a model code in the “model” field.
Next, the CPU 11 transmits the generated screen data to the client terminal 50 as a response RES10 to the request REQ10 via the communication interface 13.

When the client terminal 50 receives the response RES10 transmitted in S100, the client terminal 50 displays a screen for accepting designation of the target printer (S501).
Specifically, the CPU 51 receives the response RES10 via the communication interface 55.
Next, the CPU 51 displays the screen P10 of FIG. 6 on the display device 54 based on the response RES10.

As shown in FIG. 6, the screen P10 includes display areas A100 to A102 and a button B100.
In the display area A100, the user ID included in the response RES10 is displayed.
In the display area A101, combinations of printer names and model codes included in the response RES10 are displayed in a list format. The printer name displayed in the display area A101 is associated with the printer ID. The user can designate a printer ID for identifying the target printer by designating the printer name displayed in the display area A101.
In the display area A102, conditions for narrowing down the printer names displayed in the display area A101 are displayed in a pull-down format. This condition is, for example, location information stored in the “place” field of the user data table TBL1. When the user designates the location information displayed in the display area A102, the printer name corresponding to the designated location information is specified in the user data table TBL1. Only the specified printer name is displayed in the display area A101.
The button B100 is a button operated when the designation of the target printer is completed.

Next, the client terminal 50 accepts designation of the target printer (S502).
For example, when the user designates the printer name “PRT1” displayed in the display area A101 of the screen P10 via the input device 53 and presses the button B100, the CPU 51 designates the designated printer name “PRT1”. A request REQ11 including the printer ID “P0001” corresponding to the printer name “PRT1” is generated.
Next, the CPU 51 transmits the generated request REQ11 to the management server 10 via the communication interface 55.

Upon receiving the request REQ11 transmitted in S502, the management server 10 transmits screen data based on the request REQ11 to the client terminal 50 (S101).
Specifically, the CPU 11 receives the request REQ11 via the communication interface 13.
Next, the CPU 11 refers to the event name in the “event name” field of the event data table TBL3 and receives a designation of an event to be registered in the destination information (hereinafter referred to as “target event”). Generate data. The screen data includes the event name of the referred “event name” field.
Next, the CPU 11 transmits the generated screen data to the client terminal 50 as a response RES11 to the request REQ11 via the communication interface 13.

When the client terminal 50 receives the response RES11 transmitted in S101, the client terminal 50 displays a screen for accepting the designation of the target event (S503).
Specifically, the CPU 51 receives the response RES11 via the communication interface 55.
Next, the CPU 51 displays the screen P11 of FIG. 6 on the display device 54 based on the response RES11.

As shown in FIG. 6, the screen P11 includes display areas A100 and A110 to A111, and a button B1100.
In the display area A110, the event names included in the response RES11 are displayed in a list format. The event name displayed in the display area A110 is associated with the event code. The user can specify an event code for identifying the target event by specifying the event name displayed in the display area A110.
In the display area A111, conditions for narrowing down event names to be displayed in the display area A110 are displayed in a pull-down format. This condition is, for example, a type code “A”, “E”, or “W” indicating the type of event. When the user designates the type code displayed in the display area A111, the event name corresponding to the designated type code is specified in the event data table TBL3. Only the specified event name is displayed in the display area A101.
The button B110 is a button that is operated when the designation of the target event is completed.

Next, the client terminal 50 receives the designation of the target event (S504).
For example, when the user designates the event name “ribbon near end” displayed in the display area A110 of the screen P11 via the input device 53 and presses the button B110, the CPU 51 displays the designated event name “ribbon”. A request REQ12 including “near end” and an event code “# 3001” corresponding to the event name “ribbon near end” is generated.
The CPU 51 transmits the generated request REQ12 to the management server 10 via the communication interface 55.

Upon receiving the request REQ12 transmitted in S504, the management server 10 transmits screen data based on the request REQ12 to the client terminal 50 (S102).
Specifically, the CPU 11 receives the request REQ12 via the communication interface 13.
Next, the CPU 11 refers to the address in the “address” field of the address data table TBL2 corresponding to the user ID included in the request REQ10 and the owner name in the “destination name” field, and receives a designation of a notification destination. Generate screen data. The screen data includes the address of the referred “address” field and the owner name of the “destination name” field.
Next, the CPU 11 transmits the generated screen data to the client terminal 50 as a response RES12 through the communication interface 13.

When the client terminal 50 receives the response RES12 transmitted in S102, the client terminal 50 displays a screen for accepting designation of a destination (S505).
Specifically, the CPU 51 receives the response RES12 via the communication interface 55.
Next, the CPU 51 displays the screen P12 of FIG. 6 on the display device 54 based on the response RES12.

As shown in FIG. 6, the screen P12 includes display areas A100 and A120 and a button B120.
In the display area A120, combinations of addresses in the “address” field and owner names in the “destination name” field included in the response RES12 are displayed in a list format. The user can designate the notification destination by designating the address displayed in the display area A120.
The button B120 is a button operated when the designation of the destination is completed.

Next, the client terminal 50 accepts designation of a destination (S506).
For example, when the user designates the addresses “abc ...” and “xyz ...” displayed in the display area A120 of the screen P12 via the input device 53 and presses the button B120, the CPU 51 The request REQ13 including the designated addresses “abc ...” and “xyz ...” is generated.
Next, the CPU 51 transmits the generated request REQ13 to the management server 10 via the communication interface 55.

When receiving the request REQ13 transmitted in S506, the management server 10 registers the destination information (S103).
Specifically, the CPU 11 receives the request REQ 13 through the communication interface 13.
Next, the CPU 11 stores the event code “# 3001” included in the request REQ12 and the address “abc ...” included in the request REQ13 in the destination data table TBL4 corresponding to the printer ID “P0001” included in the request REQ11. And a destination record containing "xyz ...". As a result, the destination information is registered in the management server 10.

Next, the management server 10 transmits screen data based on the request REQ13 to the client terminal 50 (S104).
Specifically, the CPU 11 generates screen data indicating that the destination information registration processing has been completed. The screen data includes a printer name “PRT1” included in the request REQ11, an event name included in the request REQ12, and an address included in the request REQ13.
Next, the CPU 11 transmits the generated screen data to the client terminal 50 as a response RES13 via the communication interface 13.

When the client terminal 50 receives the response RES13 transmitted in S104, the client terminal 50 displays a screen indicating that the destination information registration processing is completed (S507).
Specifically, the CPU 51 receives the response RES13 via the communication interface 55.
Next, the CPU 51 displays the screen P13 of FIG. 6 on the display device 54 based on the response RES13.

As shown in FIG. 6, the screen P13 includes display areas A100 and A130.
In the display area A130, information included in the response RES13 (printer name “PRT1”, event content “ABC”, and destination “abc ...”) is displayed.

(3-2) Notification transmission processing (FIGS. 7 to 8)
The notification transmission process of this embodiment will be described.
FIG. 7 is a sequence diagram of notification transmission processing according to this embodiment. FIG. 8 is a diagram illustrating an example of a display screen displayed in the process of FIG.
In FIG. 7, the processing of the management server 10 is executed by the function of the server application. The process of the label printer 30 is executed by a firmware function. The processing of the client terminals 50-1 and 50-2 is executed by the browser function.

The label printer 30 transmits the log data D20 to the management server 10 (S320).
Specifically, the CPU 31 extracts the log data D20 that has not been transmitted to the management server 10 from the storage device 32. The log data D20 includes a printer ID, information indicating an event occurrence time, an event code, and a consumable code. There may be one or a plurality of combinations of information indicating event occurrence times, event codes, and consumable codes included in the log data D20.
Next, the CPU 31 transmits log data D <b> 20 to the management server 10 via the communication interface 36.
S320 is executed at a fixed time interval (as an example, every 10 minutes), when an event occurs, or when a request (request for log data transmission) by the management server 10 is received.

Upon receiving the log data D20 transmitted in S320, the management server 10 updates the log data table TBL5 (S120).
Specifically, the CPU 11 receives the log data D20 via the communication interface 13.
Next, the CPU 11 stores, in the log data table TBL5 corresponding to the printer ID included in the log data D20, a new log including information indicating the event occurrence time included in the log data D20, the event code, and the consumable item code. Add a record.

Next, the management server 10 specifies a destination (S121).
Specifically, in the destination data table TBL4, the CPU 11 specifies the address of the “destination” field corresponding to the event code included in the log data D20 as the notification destination.

Next, the management server 10 creates a notification (S122).
Specifically, the CPU 11 refers to the event record specified by the event code included in the log data D20 in the event data table TBL3.
Next, the CPU 11 refers to the information of the event record referred to (that is, the information of the “event code” field, the “event type” field, the “event name” field, the “content” field, and the “measure” field), and the log. A notification D21 is created using information indicating the event occurrence time included in the data D20. The notification is text data, still image data, moving image data, URL (Uniform Resource Locator), or a combination thereof.

Next, the management server 10 transmits a notification (S123).
Specifically, the CPU 11 transmits the notification D21 created in S122 to the destination specified in S121 via the communication interface 13.

Upon receiving the notification D21 transmitted in S123, the client terminals 50-1 and 50-2 display a screen including the notification D21 (S520).
Specifically, the CPU 51 receives the notification D21 via the communication interface 55.
Next, the CPU 51 displays the screen P20 of FIG. 8 on the display device 54 based on the notification D21.

As shown in FIG. 8, the screen P20 includes a display area A200.
In the display area A200, an event code, a type code, an event name, an event occurrence time, a text indicating the content of the event, and a text indicating a countermeasure for eliminating the event are displayed.

(4) Summary of this embodiment Hereinafter, this embodiment is summarized.

In the present embodiment, an address (an example of destination information) that is connected to the label printer 30 (an example of a printer) and is associated with an event code (an example of event identification information) that identifies an event that has occurred in the label printer 30. The management server 10 (an example of an information processing device) that can access the storage device 12 that stores the event code acquires the event code from the label printer 30 (for example, executes the processing of S120), and stores the event code in the storage device 12 A transmission unit that transmits a notification corresponding to the event identified by the event code (for example, executes the processing of S123) to a destination indicated by the address corresponding to the event code acquired by the acquisition unit among the received addresses; .

In the present embodiment, the label printer 30 that can be connected to the management server 10 transmits event identification information for identifying an event to the information processing apparatus at regular time intervals or when an event occurs (for example, S320). ).

In the present embodiment, the information processing system 1 includes a label printer 30, a management server 10 (an example of a server), and a client terminal 50, and the label printer 30 detects an event that has occurred in the label printer 30. An event code to be identified is transmitted to the management server 10 (for example, the process of S320 is executed). The management server 10 includes the above-described units, and the client terminal 50 receives the notification transmitted to the destination by the transmission unit. Display (for example, execute the process of S520).

Thereby, the information regarding the event that has occurred in the label printer 30 can be transmitted to an appropriate destination without any user operation. As a result, it is possible to prevent the operation of the label printer 30 from being stopped due to an event, or it is possible to reduce the time required for the recovery of the label printer 30 stopped due to the event. Accordingly, it is possible to suppress a reduction in the operating rate of the label printer 30.
For example, the user registers the address of the person in charge of the label printer 30 as the address of the notification regarding the alert, and registers the address of the person in charge having knowledge of repair of the label printer 30 as the address of the notification regarding the error. The address of the person in charge of the equipment can be registered in the notification destination. In this case, when an alert occurs, the person in charge of the label printer 30 is notified of the contents of the event, so that measures necessary to eliminate the alert can be taken promptly. When an error occurs, the person in charge who has knowledge of repairing the label printer 30 is notified of the contents of the event, so that the label printer 30 can be repaired promptly. When a warning occurs, the person in charge of the equipment is notified of the contents of the event, so that necessary consumables can be quickly prepared.

In the present embodiment, the event identified by the event code and the destination indicated by the address are presented to the user (for example, the processing of S100 to S102 is executed), and the event presented by the presentation means And an address indicating the destination designated by the user and an event code for identifying the event designated by the user (for example, executing the process of S103), and accepting by the accepting means The storage device 12 may further include storage means for storing the received destination information in association with the event code received by the reception means (for example, executing the processing of S103).
Thus, the user can register the notification destination by designating a desired destination from the presented events and destinations (for example, screens P11 to P12 in FIG. 6). As a result, it is possible to reduce the burden on the user related to registration of the notification destination.

In the present embodiment, the event type includes an error (an example of the first type) that is a cause of the cause of the operation of the label printer 30 being stopped, and an alert (the occurrence of a factor that impedes the operation of the label printer 30). An example of the second type) and a warning (an example of the third type) that the remaining amount of the consumables of the label printer 30 has become a predetermined value or less may be included.

(5) Modification A modification of the present embodiment will be described.

(5-1) Modification 1
In Modification 1, an example will be described in which the management server 10 changes at least one of the notification destination and the notification content when the predetermined condition is satisfied.
The “predetermined condition” means that an event has not been resolved when a predetermined time (for example, 1 hour) has elapsed since the event occurrence time, and the number of notification transmissions within a certain time (for example, 3 hours) (that is, S123 The number of executions of (3) has reached a predetermined number (for example, five times), the consumables attached to the label printer 30 are not predetermined consumables, or a combination thereof.

A first example of the first modification will be described. The first example of Modification 1 is an example in which the management server 10 changes the notification destination when a predetermined condition is satisfied.
In S123 of FIG. 7, the CPU 11 transmits a notification to an address corresponding to the group name “R1” among the addresses in the “destination” field of the destination data table TBL4.
When the predetermined condition is satisfied after S520, the CPU 11 transmits the same notification as the notification transmitted in S123 to the address corresponding to the group name “R2” among the addresses in the “destination” field of the destination data table TBL4. To do.

A second example of the first modification will be described. The second example of Modification 1 is an example in which the management server 10 changes the content of notification when a predetermined condition is satisfied.
When the predetermined condition is satisfied after S520 in FIG. 7, the CPU 11 creates a new notification having contents different from the notification transmitted in S123. For example, the CPU 11 creates a new notification by changing the text data of the notification transmitted in S123 to another text data.
Next, the CPU 11 transmits the created new notification to the same destination as the notification destination transmitted in S123.

A third example of the first modification will be described. The third example of Modification 1 is an example in which the management server 10 retransmits a notification when a predetermined condition is satisfied.
When the predetermined condition is satisfied after S520 in FIG. 7, the CPU 11 transmits the same notification as the notification transmitted in S123 to the same destination as the notification transmitted in S123.

According to the first example of the first modification, the storage device 12 has an address corresponding to the group name “R1” (an example of “first destination information”) and an address corresponding to the group name “R2” (“second” An example of “destination information” is stored in association with the event code, and the transmission unit transmits a notification to an address corresponding to the group name “R1” when the predetermined condition is not satisfied, and when the predetermined condition is satisfied, A notification is transmitted to the address corresponding to the group name “R2”.
According to the second example of the first modification, the notification includes at least one of text data and image data, and the transmission unit transmits at least one of the text data and the image data included in the notification when a predetermined condition is satisfied. change.
Accordingly, the user can switch at least one of the notification destination and the notification content depending on whether the predetermined condition is satisfied or not. As a result, the degree of freedom in management of the label printer 30 is improved.

According to the third example of the first modification, the transmission unit retransmits the notification when the predetermined condition is satisfied.
Thereby, the probability that the user who received the notification overlooks the notification can be reduced.

Further, according to the first modification, the acquisition unit further acquires information indicating the event occurrence time from the label printer 30, and the predetermined condition is that the event has not been resolved when a predetermined time has elapsed from the event occurrence time. It may be.
Further, according to the first modification, the predetermined condition may be that the number of notification transmissions within a predetermined time has reached a predetermined number.
Thereby, the event is not resolved (for example, any state in which the operation of the label printer 30 is hindered, the label printer 30 is stopped, or the remaining amount of consumables is low). A certain time can be shortened.

According to the first modification, the predetermined condition may be that the consumable item attached to the label printer 30 is not a predetermined consumable item.
Thus, the usage status of the consumables attached to the label printer 30 (for example, whether or not the consumables are manufactured by the manufacturer of the label printer 30) can be notified to an appropriate destination.

(5-2) Modification 2
In the second modification, an example will be described in which the destination candidates presented to the user are switched according to the event type.

For example, when the type code corresponding to the event code included in the request REQ12 is “A” in S102 of FIG. 5 (ie, the event is an alert), the CPU 11 performs group name “R1” in the address data table TBL2. A response RES12 including the address of the “address” field corresponding to is generated. In this case, only the address corresponding to the group name “R1” is displayed in the display area A110 of the screen P11 in FIG.
On the other hand, when the type code corresponding to the event code included in the request REQ12 is “E” (that is, the event is an error), the CPU 11 “address” corresponding to the group name “R2” in the address data table TBL2. A response RES12 including the address of the field is generated. In this case, only the address corresponding to the group name “R2” is displayed in the display area A110.

According to the second modification, the storage device 12 stores a plurality of addresses, and the presentation unit selects a destination to be presented from destinations indicated by the plurality of addresses according to the type of event.
Thereby, the notification can be transmitted to an appropriate destination according to the type of the event.

(5-3) Modification 3
In the third modification, an example in which a notification is transmitted to a destination other than the destination designated by the user will be described.
When the event code included in the request REQ12 is a specific event code (for example, event code “# 2007” indicating the event name “imitation”), the CPU 11 determines that the event code included in the log data D20 in S123 of FIG. In addition to the address of the “destination” field corresponding to “”, it is transmitted to an address owned by the manufacturer of the label printer 30.

According to the third modification, when a specific event occurs, the manufacturer of the label printer 30 can receive a notification regarding the specific event, so that the occurrence state of the specific event can be grasped. In particular, when the specific event is the event name “imitation”, information about the label printer 30 to which a consumable item other than the predetermined consumable item is attached (for example, the number of the label printer 30) can be grasped. The manufacturer of the label printer 30 can utilize such information when planning the development and sale of the label printer 30 and consumables.

(5-4) Modification 4
In Modification 4, an example in which the management server 10 receives registration of destination information for each event type will be described.
In S101, the CPU 11 refers to the type code in the “event type” field of the event data table TBL3, and generates screen data of a screen that accepts designation of an event type that is a target of destination information registration processing. The screen data includes the type code of the referred “event type” field.
In step S <b> 503, the CPU 51 displays on the display device 54 a screen that accepts designation of an event type based on the screen data generated by the CPU 11.

(5-5) Modification 5
In Modification 5, an example in which the management server 10 updates the event data table TBL3 based on a user instruction will be described.
For example, the event data table TBL3 is stored in association with the user ID.
When the user gives an instruction to change the data of the event data table TBL3 via the input device 53, the CPU 51 transmits a request including the instruction to the management server 10. The request includes a user ID for identifying a user who gives an instruction, an event code for identifying an event to be updated, and information indicating the contents of the update (for example, text indicating a measure for eliminating the event). Including.
When receiving the request transmitted by the CPU 51, the CPU 11 extracts an event record specified by the event code included in the request in the event data table TBL3 corresponding to the user ID included in the request.
Next, the CPU 11 rewrites the “Countermeasure” field information of the extracted event record using the information indicating the content of the update included in the request. As a result, the event data table TBL3 is updated.

(5-6) Modification 6
In Modification 6, an example in which the management server 10 displays log data based on a user instruction will be described.
For example, when the user gives an instruction to display log data via the input device 53, the CPU 51 transmits a request including the instruction to the management server 10. The request includes a printer ID for identifying the label printer 30 that has transmitted the log data to be displayed, and a condition for designating a range of log data to be displayed. This condition is, for example, a period or an event code.
Next, when the CPU 11 receives the request transmitted by the CPU 51, the CPU 11 extracts a log record corresponding to the condition included in the request in the log data table TBL5 corresponding to the printer ID included in the request.
Next, the CPU 11 transmits the extracted log record to the client terminal 50 via the communication interface 13.
Next, when the CPU 51 receives the log record transmitted by the CPU 11, the display device 54 displays a screen presenting information indicating an event occurrence time, an event code, and a consumable code included in the received log record. indicate.

(5-7) Other Modifications In the above embodiment, an example in which the printer is the label printer 30 has been described. However, the printer of this embodiment is not limited to this. The printer of this embodiment also includes an apparatus (for example, an ink jet printer, a laser printer, a multifunction peripheral, etc.) that prints information on a print medium other than a label.

In the above embodiment, as an example of the continuous paper stored in the paper storage unit of the label printer 30, a plurality of labels temporarily attached to the mount is illustrated, but the continuous paper of the present embodiment is not limited to this. The continuous paper of the present embodiment may be a continuous label that is not temporarily attached to the mount, may be a label in which RFID (Radio Frequency IDentifier) is embedded, or may not have an adhesive surface. It may be a medium (for example, tag, wristband, etc.).

In the above-described embodiment, an example has been described in which the CPU 31 includes the consumable code stored in the IC chip embedded in the consumable in the log data. However, the method for obtaining information for identifying the consumable is not limited thereto. . For example, the CPU 31 may measure the current obtained when a predetermined voltage is applied to the consumable, calculate the electrical resistance of the consumable based on the measured current, and include the calculated electrical resistance in the log data. Good. In this case, the electric resistance calculated by the CPU 31 is stored in the “consumable code” field of the log data table TBL5 instead of the consumable code.

In the above embodiment, an example in which the storage device 12 is provided in the management server 10 has been described, but the storage device 12 may be provided outside the management server 10. In this case, the storage device 12 is connected to the management server 10 via the network NW. The CPU 11 accesses the storage device 12 via the communication interface 13.

As mentioned above, although embodiment of this invention was described in detail, the scope of the present invention is not limited to said embodiment. The above-described embodiment can be variously improved and changed without departing from the gist of the present invention. Moreover, said embodiment and modification can be combined.

1: Information processing system 10: Management server 11: CPU
12: Storage device 13: Communication interface 30: Label printer 31: CPU
32: Storage device 33: Input device 34: Display device 35: Printing unit 36: Communication interface 50: Client terminal 51: CPU
52: Storage device 53: Input device 54: Display device 55: Communication interface

Claims (13)

1. An information processing apparatus connected to a printer and capable of accessing a storage device that stores destination information associated with event identification information for identifying an event that has occurred in the printer,
   Obtaining means for obtaining the event identification information from the printer;
   Transmission means for transmitting a notification corresponding to the event identified by the event identification information to the destination indicated by the destination information corresponding to the event identification information acquired by the acquisition means among the destination information stored in the storage device When,
   An information processing apparatus comprising:
2. The storage device stores first destination information and second destination information in association with the event identification information,
   The transmission means transmits the notification to a destination indicated by the first destination information when the predetermined condition is not satisfied, and transmits the notification to a destination indicated by the second destination information when the predetermined condition is satisfied.
   The information processing apparatus according to claim 1.
3. The notification includes at least one of text data and image data;
   The transmission means changes at least one of text data and image data included in the notification when a predetermined condition is satisfied;
   The information processing apparatus according to claim 1 or 2.
4. The transmission means resends the notification when a predetermined condition is satisfied,
   The information processing apparatus according to any one of claims 1 to 3.
5. The acquisition unit further acquires information indicating the event occurrence time from the printer,
   The predetermined condition is that the event has not been resolved when a predetermined time has elapsed from the event occurrence time.
   The information processing apparatus according to any one of claims 2 to 4.
6. The predetermined condition is that the number of transmissions of the notification within a predetermined time has reached a predetermined number of times.
   The information processing apparatus according to any one of claims 2 to 5.
7. The predetermined condition is that a consumable item attached to the printer is not a predetermined consumable item.
   The information processing apparatus according to any one of claims 2 to 6.
8. Presenting means for presenting an event identified by the event identification information and a destination indicated by the destination information to a user;
   Accepting means for receiving destination information indicating a destination designated by the user from among the events and destinations presented by the presenting means, and event identification information for identifying the event designated by the user;
   Storage means for storing the destination information received by the receiving means in association with the event identification information received by the receiving means in the storage device;
   The information processing apparatus according to any one of claims 1 to 7.
9. The storage device stores a plurality of destination information,
   The presenting means selects a destination to be presented from destinations indicated by the plurality of destination information according to the type of the event;
   The information processing apparatus according to claim 8.
10. The event type includes a first type that is a cause of the stop of the operation of the printer, a second type that is a cause of an obstacle to the operation of the printer, and a remaining amount of parts of the printer. Including the third type, which is below the value,
    The information processing apparatus according to claim 9.
11. A program for causing a computer to realize each means of the information processing apparatus according to any one of claims 1 to 10.
12. A printer connectable to the information processing apparatus according to any one of claims 1 to 10,
    When the event occurs every fixed time or when a request by the information processing device is received, event identification information for identifying the event is transmitted to the information processing device.
    Printer.
13. An information processing system comprising a printer, a server, and a client terminal,
    The printer transmits event identification information for identifying an event occurring in the printer to the server;
    The server includes each unit of the information processing apparatus according to any one of claims 1 to 10,
    The client terminal displays a notification sent to the destination by the sending means;
    Information processing system.

Images