Information processing systems, printers, programs

Abstract

To reliably back up data generated on a printer.SOLUTION: An information processing system includes a server, a computer device, and a printer. The printer includes: a storage 32 for storing layout data and reference data to be referred for printing; a data editing unit which edits the reference data on the basis of operation input of a user, and records on a storage unit, or updates edited data obtained by editing the reference data; an automatic backup processing unit which periodically backs up the edited data stored in the storage to the computer device; and a manual backup processing unit which backs up the edited data stored in the storage unit to an external storage apparatus in response to user operation. The server includes a data recording unit which records, on the storage unit, edited data to be backed up, when there is a difference between edited data obtained through the latest editing on the printer and edited data obtained through the previous editing.SELECTED DRAWING: Figure 9

Description

Technical Field

[0001] The present invention relates to an information processing system, a printer, and a program.

Background Art

[0002] Conventionally, in order to prevent discrepancies in the content printed on labels or the like attached to products in a plurality of chain stores, the content printed by a plurality of printers has been centrally managed by a server. The printing data thus centrally managed is updated regularly or irregularly. For example, in Patent Document 1, a management server acquires registered image data stored in a connected representative printer from the representative printer, and based on the acquired registered image data, updates the registered image data stored in printers other than the representative printer, thereby maintaining the identity between the registered image data stored in the representative printer and the registered image data stored in other printers.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] By the way, even when the printing content of a plurality of chain stores is centrally managed by a server, some stores may have their own unique products, and in some cases, data for printing labels to be attached to such unique products is created by the store staff and saved in the printer. However, if the printer that stores the data created independently by the store fails, the data created for the unique products will be lost.

[0005] Therefore, the present invention aims to enable reliable backup of data created in a printer. [Means for solving the problem]

[0006] One aspect of the present invention is an information processing system including an information processing device and a printer capable of communicating with the information processing device. The aforementioned printer is A storage unit that stores layout data indicating the layout when printing, and reference data associated with the layout data and referenced when printing, A data editing unit that edits the reference data based on user input, records the edited data (which is the reference data after editing) in the storage unit, or updates the edited data in the storage unit as needed. A first backup processing unit that periodically backs up the edited data in the storage unit to the information processing device, The system includes a second backup processing unit that backs up the edited data in the aforementioned storage unit to an external storage device in response to user operations. The aforementioned information processing device is The system includes a data recording unit that records the edited data to be backed up in the storage unit if there is a difference between the edited data from the most recent edit on the printer and the edited data from the previous edit. [Effects of the Invention]

[0007] According to one aspect of the present invention, it is possible to reliably back up data created in a printer. [Brief explanation of the drawing]

[0008] [Figure 1] This is a system configuration diagram of the information processing system according to the embodiment. [Figure 2] This figure shows an example of the project file creation screen for the information processing device according to the embodiment. [Figure 3]This figure shows the procedure for displaying a call table definition in an information processing device according to an embodiment. [Figure 4] This figure shows the procedure for displaying a call table in the information processing device according to the embodiment. [Figure 5] This diagram shows the procedure for displaying a Kanji table and a store name table in an information processing device according to the embodiment. [Figure 6] This diagram shows the procedure for uploading a project file to a server in the information processing device according to the embodiment. [Figure 7] This diagram shows the operating procedure of the printer according to the embodiment. [Figure 8] This figure shows the hardware configuration of the information processing system according to the embodiment. [Figure 9] This is a functional block diagram of the information processing system according to the embodiment. [Figure 10] This is an example of a sequence chart for when a printer issues a label in an information processing system according to an embodiment. [Figure 11] This diagram shows the procedure for editing the call table in the printer according to the embodiment. [Figure 12] This figure shows an example of the storage directory configuration in a printer according to the embodiment. [Figure 13] This figure shows an example of how the object property setting section is displayed when each table is selected on the project file creation screen of the information processing device according to the embodiment. [Figure 14] This flowchart shows the process when a printer according to the embodiment references a table. [Figure 15] This diagram shows the procedure for configuring automatic backup in the printer according to this embodiment. [Figure 16] This figure shows an example of the storage directory configuration in a server according to the embodiment. [Figure 17]This is a sequence chart when performing an automatic backup process of an edited table in the information processing system according to the embodiment. [Figure 18] This is a diagram showing the procedure for setting manual backup in the printer according to the embodiment. [Figure 19] This is a diagram showing the procedure for restoring data in the printer according to the embodiment. [Figure 20] This is a diagram showing another configuration example of the storage directory in the server according to the embodiment. [Figure 21] This is a sequence chart when performing an automatic backup process of differential data of an edited table in the information processing system according to the embodiment.

Mode for Carrying Out the Invention

[0009] The "storage device" in the present disclosure may be a memory or storage built into the printer, or a device external to the printer (for example, an external storage device such as a HDD (Hard Disk Drive) or a USB (Universal Serial Bus) storage, or a database server). The "reference data" in the present disclosure may be any data as long as it is data referred to when printing. For example, layout data and data referring to text referred to when printing, data referred to when calling character data to be printed, and data indicating the distribution destination of layout data used when printing can be cited. Also, setting information and the like referred to when printing can also be reference data.

[0010] (1) System Overview Hereinafter, an information processing system 1 which is an embodiment of the information processing system of the present invention will be described with reference to FIG. 1. FIG. 1 is a system configuration diagram of the information processing system 1 according to the present embodiment.

[0011] As shown in Figure 1, in the information processing system 1 of this embodiment, a computer device 2 and multiple printers 3-A, 3-B, 3-C, 3-D, 3-E, ... are connected to a server 5 via a network NW such as the Internet or a LAN (Local Area Network). In this embodiment, the information processing system 1 is operated by a retailer that manages multiple stores and is a system for issuing labels to products sold at each store. In this embodiment, the example of a store is used to describe the location where the labels are issued, but in reality, labels may also be issued at factories or other locations.

[0012] Computer device 2 is located at the headquarters of the distributor. Computer device 2 (hereinafter referred to as "PC2" as appropriate) is a computer device such as a personal computer or a tablet terminal. At least one printer is located in each store. For example, printers 3-A, 3-B, 3-C, 3-D, and 3-E are located in stores A, B, C, D, and E, respectively. In the following explanation, when referring to matters common to multiple printers, it will be written as "printer 3". At headquarters, PC2 is used to design the basic layout of the labels. Each store then issues the labels to be affixed to the products based on the layout design provided by headquarters.

[0013] PC2 has a label creation application program (hereinafter referred to as the "label creation application") installed that creates a project file containing data on the label layout design, data on each item included in the label, various settings, store information, etc. The project file created by running the label creation application is distributed as a format file from PC2 to printer 3 via server 5. In other words, the project file is uploaded as a format file from computer device 2 to server 5 in response to a predetermined operation by the user, and downloaded from server 5 to printer 3 at a predetermined time.

[0014] Printer 3 has a label printing application program (hereinafter referred to as "label printing application") installed that issues labels based on a format file. By running the label printing application, it is possible to select printing data that specifies the layout design of the label, the data of each item included in the label, etc., or to edit the selected printing data as needed, and then print labels based on the printing data. Store employees attach the labels printed by Printer 3 to products in the store. Project files and publishing data will be discussed later.

[0015] (2) The process until label issuance Next, referring to Figures 2 to 7, we will explain the entire process from when the project file is created by PC2 to when the label is printed by printer 3. Figure 2 shows an example of the project file creation screen on PC2. Figure 3 shows the procedure for displaying the call table definition on PC2. Figure 4 shows the procedure for displaying the call table on PC2. Figure 5 shows the procedure for displaying the Kanji table and the store name table on PC2. Figure 6 shows the procedure for uploading the format file to the server on PC2. Figure 7 shows the operation procedure when printing a label on printer 3.

[0016] (2-1) Creating a project file Figure 2 shows an example of PC screen G1 (project file creation screen) displayed on PC2 when the label creation application is launched. On the project file creation screen, the user can design the labels to be printed by printer 3 by setting the objects to be placed within the printable area of ​​the labels.

[0017] In the label creation application, data is managed by project files. A project file is a file that represents the management unit of data created by the label creation application, and it is distributed to each printer 3 via the server 5 as a format file.

[0018] As shown in Figure 2, the PC screen G1 includes a group of instruction buttons 101, a group of object buttons 102, a design window 103, a project settings unit 104, and an object property settings unit 105. The project settings section 104 displays the data contained in the project file in a hierarchical structure. As shown in this hierarchical structure, the project file includes a call table, layout data, a Kanji table, and a store name table. Although not shown in the diagram, the project file further includes individual table information files. The table information files are files that contain information about various settings for each table.

[0019] The call table is data used in the label printing application of printer 3 to print labels. The call table is an example of reference data used to reference layout data and text when printing by printer 3. The layout data is design data for printing labels on printer 3 in combination with the call table, and is displayed, for example, in the design window 103 on PC screen G1 during editing. The Kanji table is a table used to convert entered numerical values ​​into registered character data. Character data can be registered in the Kanji table in association with a registration number. For example, by setting the system to reference the Kanji table when entering characters into a string object (described later), it is possible to specify a registration number instead of entering character data. The Kanji table is an example of reference data used to retrieve text when printing based on layout data. The store name table contains information corresponding to the printer ID (printer identification information) of the printer located at the store to which the format file is distributed. The store name table is an example of reference data that includes the printer ID of printer 3, which prints based on the layout data.

[0020] Note that Figure 2 shows the case where one Kanji table and one store name table are set up, but this is not always the case. Multiple Kanji tables and store name tables can be set up. For example, it is possible to set them up as Kanji Table 1, Kanji Table 2, Kanji Table 3, ..., Store Name Table 1, Store Name Table 2, Store Name Table 3, ...

[0021] The design window 103 corresponds to the label creation and editing area, and the label is designed by placing and moving objects within this creation and editing area. In other words, the design window 103 is the window for designing the layout of the label. In this embodiment, an example is shown of a label being designed that includes four objects: object OBJ1 corresponding to the "product name" field, object OBJ2 corresponding to the "name" field, object OBJ3 corresponding to the "contents" field, and object OBJ4, which is a date and time object corresponding to the "expiration date" field. When button b2 ("Input Screen") is pressed, a window (not shown) for entering the strings or codes contained in each object is displayed instead of the design window 103. When button b1 ("Layout") is pressed while this window is displayed, the user returns to the design window 103.

[0022] The object button group 102 is where you select and move objects on the design window 103, or set up new objects. The object button group 102 allows you to select various objects, such as text objects, price objects, barcode objects, date and time objects, and graphic objects. Various object settings can be configured in the object property setting section 105. In the example shown in Figure 2, various settings for the selected object OBJ1 can be made in the object property setting unit 105. For example, the item name in the object property setting unit 105 (in this example, "Product Name") sets the items used in the layout design within the design window 103. The input method can be selected as "Fixed" or "On Issue". If "Fixed" is selected as the input method, it indicates that the value set in the "Data" field (in this example, "Chicken Cutlet Sandwich") will be printed. If "On Issue" is selected as the input method, it indicates that the initial value set in the "Data" field can be changed in the label printing application of printer 3.

[0023] By operating the buttons within the instruction button group 101, it is possible to read project files from storage, save project files to storage, or upload project files to server 5 as format files.

[0024] Next, we will explain the call table, the kanji table, and the store name table, referring to Figures 3 to 5. To register data for printing on labels in the retrieval table, the data must be defined beforehand. To perform this data definition, as shown in Figure 3, the retrieval table definition window W1 is displayed by manipulating the "retrieval table" in the project settings unit 104 (for example, by right-clicking and selecting "Define"). The retrieval table definition data TL1 in window W1 shows an example where four item names are defined: "Product Name," "Name," "Net Quantity," and "Expiration Date." In the records corresponding to each item name in the retrieval table definition data TL1, values ​​for each field such as "Number of Digits," "Number of Digits Check," and "Character Type Check" are entered.

[0025] The values ​​in fields such as "Number of Digits," "Number of Digits Check," and "Character Type Check" are provided to check the strings corresponding to each item name entered by the user, from the perspective of label layout and consistency of the displayed content on the label, but they are not mandatory. The value in the "Number of Digits" field indicates the maximum number of digits for the string corresponding to each item name. The value in the "Number of Digits Check" field indicates whether a check is performed to see if a string corresponding to the item name is entered in the retrieval table, or whether a check is performed to see if the number of digits in the string corresponding to the item name is less than or equal to the value in the "Number of Digits" field. The value in the "Character Type Check" field indicates whether a check is performed to see if the character type (numbers or non-numeric characters) of the string corresponding to the item name is checked, and if so, the character type is specified. When the user enters information in window W1 and creates the call table definition data TL1, the item names for printing on the label are registered in the call table (i.e., the items are defined).

[0026] After creating the call table definition data TL1, the user registers the print data in the call table. As shown in Figure 4, the call table TL2 is displayed by operating the "Call Table" in the project settings unit 104 (for example, by double-clicking or by right-clicking and selecting "Open" (see Figure 3)). The call table TL2 includes the four item name fields defined in the call table definition data TL1 (see Figure 3): "Product Name," "Name," "Contents," and "Expiration Date," as well as the fields "Call No." and "Layout Specification."

[0027] Each record in the TL2 call table represents the label layout for issuing a single label and the data (strings) for each defined field name. This data in each record will be referred to as "issue data" below. Users can associate the label layout with the corresponding strings for each field name by entering the strings corresponding to each field name into the TL2 call table. Note that the TL2 call table does not need to contain multiple records; it may contain only one record (i.e., one piece of issue data). In the call table TL2, the issued data is identified by the call number. In the label printing application of printer 3, the issued data is retrieved by the call number.

[0028] In the TL2 call table, the value of the "Layout Specification" field indicates one of the layout data created in the design window 103 (see Figure 2). In this example, the value of the "Layout Specification" field indicates which of the two layout data sets each issue data corresponds to, given that two layout data sets have been created: [1] Content Label and [2] Expiry Label.

[0029] For example, in the label design within the design window 103 shown on PC screen G1 in Figure 2, the issued data corresponding to the record for call No.:1 (call name: "Chicken Cutlet Sandwich") in the call table TL2 is displayed. In this example, the label design in design window 103 corresponds to the value of the "Layout Specification" field ([1] Content Display Label) in the record corresponding to call No.:1. The string in object OBJ1 corresponding to the product name corresponds to the value of the "Product Name" field in the record for call No.:1 in call table TL2. The string in object OBJ2 corresponding to the name corresponds to the value of the "Name" field in the record for call No.:1 in call table TL2. The string in object OBJ3 corresponding to the quantity corresponds to the value of the "Quantity" field in the record for call No.:1 in call table TL2.

[0030] The value of the "Expiration Date" field in the record corresponding to Call No.:1 indicates the maximum number of digits for the date in object OBJ4, which is the datetime object corresponding to the expiration date. In the label design in design window 103, the date in object OBJ4 corresponding to the expiration date is displayed as, for example, the base date of PC2 or the current date.

[0031] As described above, PC2 users can design labels with different layouts or labels with the same layout but different printed content for each item by registering data in the call table TL2. For example, in the example shown in Figure 4, the issued data corresponding to call numbers 1 to 3 corresponds to labels with the same layout ([1] content display label) but different printed content for each item. The issued data corresponding to call number 100 corresponds to a label with a different layout ([2] expiration label) than call numbers 1 to 3.

[0032] As shown in Figure 5, the Kanji Table TL3 can be displayed by manipulating the "Kanji Table" in the project settings unit 104 (for example, by double-clicking it). In the illustrated example, each record in the Kanji table TL3 contains values ​​for the "Registration Number" and "Character Data" fields. The value of the "Registration Number" field is the number specified, for example, when entering characters into a string object. The value of the "Character Data" field is the character data entered when the corresponding registration number is specified.

[0033] As shown in Figure 5, the store name table TL4 can be displayed by manipulating the "store name table" in the project settings unit 104 (for example, by double-clicking it). In the illustrated example, each record in the store name table TL4 contains values ​​for the fields "Registration Number," "Store Name," "Address," and "Telephone Number." The registration number is a value that identifies the printer 3 to which the format file will be distributed, and is associated with the printer ID (printer identification information). Since some stores may have multiple printers 3, the registration number and store name do not necessarily correspond one-to-one. In the example in Figure 5, it is shown that store F has two printers 3 with registration numbers 6 and 7. Although not shown in Figure 5, it is possible to add a new record with a new registration number to the store name table TL4 or delete an existing record from the store name table TL4 based on predetermined user operations. The store name table TL4 contains data to identify printer 3, which is the destination for the format file, and the "address" and "telephone number" fields for each store are not necessarily required.

[0034] As described above, the label creation application on PC2 creates layout data, a call table, a kanji table, and a store name table. Then, by operating the output button in the instruction button group 101, the layout data, call table, kanji table, store name table, and a project file containing each table information file are uploaded to server 5 as a format file. Specifically, operating the output button in the instruction button group 101 displays the data output window W2, as shown in Figure 6. In the output destination selection section 204 of window W2, you can select either storage on PC2 ("Devices and Drives") or server 5 ("Server") as the output destination. If you select "Server," window W3 will be displayed. In window W3, by entering the address (URL) corresponding to server 5, the login ID, and the project file name, and then operating the OK button, the format file corresponding to the project file will be uploaded (window W4). Note that for security reasons, password authentication may be required in window W3. In the example shown in Figure 6, a format file named "Sandwich" is uploaded to server 5.

[0035] (2-2) Issuance of labels The procedure for printing labels using printer 3 is as follows: First, the label printing application on printer 3 is launched, and the format file is downloaded from server 5. Next, as shown in printer screen g1 in Figure 7, the user selects "Sandwich" from the downloaded format files as the format file corresponding to the label they want to print. The next printer screen g2 that appears includes an input box bx1 for entering a call number in the selected format file. The call number entered here corresponds to the call number in the call table (see Figure 4) within the format file. For example, if call number:003 is entered in input box bx1, the issuance data for the record corresponding to call number:003 in the call table in Figure 4 is retrieved, and printer screen g3 is displayed.

[0036] On the printer screen g3, the initial values ​​for each item of the issued data corresponding to call number: 003 are displayed in the issued data display unit 206. In the issued data display unit 206, the value corresponding to the expiration date is the reference date of printer 3. If the confirm button is pressed on printer screen g3, printer screen g4 is displayed. Printer screen g4 includes a preview button b4, a confirm button b5, two input boxes bx2 for entering the number of copies to print, and a group of input boxes 207. The input box group 207 consists of input boxes corresponding to each item of the issued data. If the data input method in the label creation application is set to "at the time of issuance" (see object property setting section 105 in Figure 2), the user can edit the string by selecting an input box and, for example, operating the software keyboard SK. The label will be printed by pressing the confirmation button b5 on the printer screen g4. Note that you can display a preview image of the label by pressing the preview button b4 before printing.

[0037] As will be explained later, the user of printer 3 can individually edit the call table, Kanji table, and store name table included in the format file downloaded by printer 3. In the following, the call table, kanji table, and store name table included in the format file distributed by PC2 and immediately downloaded by printer 3 from server 5 will be referred to as "master call table," "master kanji table," and "master store name table," respectively, as appropriate. The master call table, master kanji table, and master store name table are sometimes collectively referred to as the "master file." Furthermore, the tables after the Master Call Table, Master Kanji Table, and Master Store Name Table have been edited by the user of Printer 3 will be referred to as "Edited Call Table," "Edited Kanji Table," and "Edited Store Name Table," respectively, as appropriate. The Edited Call Table, Edited Kanji Table, and Edited Store Name Table may be collectively referred to as the "Edited Table" or "Master Edit File."

[0038] (3) Configuration of Information Processing System 1 Next, referring to Figure 8, the configuration of PC2, printer3, and server5 included in information processing system 1 will be described.

[0039] (3-1) PC2 As shown in Figure 8, PC2 includes a control unit 21, storage 22, operation input unit 23, display unit 24, LAN interface 25, and USB interface 26.

[0040] The control unit 21 is mainly composed of a microprocessor and controls the entire PC2. For example, the microprocessor included in the control unit 21 loads and executes a label creation application program recorded in the storage 22, and displays the execution result on the display unit 24. The storage 22 is a non-volatile memory, and may be an SSD (Solid State Drive) such as flash memory. The storage 22 stores the label creation application program, project files created by running the label creation application, the printer ID of the printer 3 placed in each store (the printer ID corresponding to the registration number in the store name table), and so on. The project file includes layout data, a call table, a kanji table, a store name table, and information files for each table. Here, the call table, kanji table, and store name table are examples of reference data.

[0041] The control unit 21 may also set whether or not the master file can be edited by running the label creation application. The setting of whether or not the master file can be edited will be described later.

[0042] The operation input unit 23 includes, for example, an input device such as a pointing device or a touch panel. If the display unit 24 is equipped with a display panel for touch panel input, the display unit 24 constitutes a part of the operation input unit 23. The display unit 24 includes, for example, a liquid crystal display panel and displays the execution results of the label creation application. The LAN interface 25 is a communication interface used for communication with the server 5. The USB interface 26 is the interface used for direct communication with the printer 3.

[0043] (3-2) Printer 3 As shown in Figure 8, the printer 3 includes a control unit 31, storage 32 (an example of a memory unit), operation input unit 33, display unit 34, transport unit 35, printing unit 36, LAN interface 37, and USB interface 38.

[0044] The control unit 31 is mainly composed of a microprocessor and controls the entire printer 3. The storage 32 is a non-volatile memory, such as an SSD with flash memory. For example, the microprocessor included in the control unit 31 loads and executes the firmware and label issuing application program recorded in the storage 32. The control unit 31 requests the server 5 to send a format file, receives the format file sent in response to the request via the LAN interface 37, and saves it to the storage 32. The timing at which the control unit 31 requests the server 5 to send a format file is not limited, but could be, for example, when the printer 3 is started up, at a predetermined time each day, or when a predetermined download operation is performed by the user.

[0045] Storage 32 stores the firmware and label printing application program, as well as the printer ID of printer 3. This printer ID corresponds to the registration number in the store name table recorded on PC2. Storage 32 stores one or more format files downloaded from server 5.

[0046] The control unit 31 executes firmware to convert the issued data into bitmap data (print data) for printing, and sequentially sends line data, which is line-by-line data for the print data, to the printing unit 36. The transport unit 35 and the printing unit 36 ​​perform printing based on the sequentially sent line data. The transport unit 35 includes a platen roller (not shown), a motor drive circuit, and a stepping motor, and transports continuous paper within the printer 3. For example, based on a transport request from the firmware, the motor drive circuit drives a stepping motor that controls the rotation of the platen roller, thereby transporting the continuous paper. The printing unit 36 ​​includes a thermal head and a head drive circuit (not shown). The head drive circuit selectively supplies current to each heating element of the thermal head based on line data, thereby printing on the label of continuous paper.

[0047] The operation input unit 33 includes a touch panel input and its input circuit provided on the display panel of the printer 3. The display unit 34 has a display panel, which displays the execution results of the label issuing application. The LAN interface 37 is a communication interface used for communication with the server 5. The USB interface 38 is an interface used for direct communication with the computer device 2.

[0048] (3-3) Server 5 Server 5 comprises a control unit 51, storage 52, and a communication unit 53. Storage 52 is a large-capacity storage device such as an HDD, and it stores the format file sent from PC2 in association with the login ID. The control unit 51 is mainly composed of a microprocessor and controls the entire server 5 by executing a server program. For example, the control unit 51 controls the communication unit 53 to send a format file in response to a request from the printer 3. The communication unit 53 is a communication interface that communicates with both the PC2 and the printer3.

[0049] Further explanation will be given with reference to Figure 9. Figure 9 is a functional block diagram of printer 3 and server 5 of information processing system 1. Referring to Figure 9, the control unit 31 of the printer 3 functions as a data update unit 311, a data editing unit 312, a print control unit 313, an automatic backup processing unit 314, a manual backup processing unit 315, a backup generation setting unit 316, and a restore processing unit 317 by executing a label printing application. The control unit 51 of server 5 functions as a data recording unit 511 and a data deletion unit 512 by executing the server program.

[0050] In printer 3, the layout data and master files (i.e., the master call table, master Kanji table, and master store name table) recorded in storage 32 based on the format file downloaded from server 5 are updated periodically or irregularly. At this time, the data update unit 311 updates the layout data and master files in the first storage area of ​​storage 32 using the layout data and master files received from computer device 2 via server 5 at the data update timing. The timing of data updates is not limited, but could be, for example, when printer 3 is started up, at a predetermined time each day, or when a predetermined download operation is performed by the user.

[0051] When a user edits a master file included in a downloaded format file, the storage 32 stores the edited master edit file (i.e., at least one of the edited call table, edited Kanji table, and edited store name table). At this time, the master edit file is recorded in a different storage area (second storage area) of the storage 32 than the storage area (first storage area) where the original master file is stored. In other words, the data editing unit 312 edits the master file in the first storage area of ​​the storage 32 based on the user's input and records the edited master edit file in the second storage area of ​​the storage 32.

[0052] In one embodiment, the permission to edit the master file can be set by the label creation application on PC2. The print control unit 313 prints based on the master edited file if editing the master file is set to be permitted, and prints based on the master file if editing the master file is set to be prohibited.

[0053] In one embodiment, in case of printer 3 failure, the master edit files created by the printer 3 user can be backed up to server 5 and external USB storage. The automatic backup processing unit 314 (an example of the first backup processing unit) periodically backs up the master edit files located in storage 32 to server 5. The manual backup processing unit 315 (an example of the second backup processing unit) backs up the master edit file located in storage 32 to external USB storage when a user makes an operation.

[0054] In one embodiment, the printer 3 can be restored based on the backed-up data (backup data). The restore processing unit 317 restores the printer 3 based on backup data stored on an external USB storage device or server 5.

[0055] As described later, in automatic data backup, server 5 does not record the data to be backed up in printer 3 as is, but rather records it only if there is a difference from the previous backup data. If the data to be backed up is a master edit file, data recording unit 511 records the master edit file with the latest edits in storage 52 if there is a difference between the master edit file with the latest edits in printer 3 and the master edit file with the previous edits.

[0056] The backup generation setting unit 316 sets the maximum number of master edit files stored in the server 5's storage 52 based on the user's input for the printer 3. The data deletion unit 512 deletes master edit files previously recorded in the storage 52 based on the maximum value set by the backup generation setting unit 316. In other words, older backup data, which are master edit files, are sequentially deleted from the storage 52.

[0057] Referring to Figure 10, the label issuance process is as follows: In response to user input, the label creation application on PC2 sends a format file containing each table (master file) to server 5 (step S2). Server 5 saves the format file received from PC2 to storage 52 (step S4). Server 5 sends the format file to printer 3 in response to a request from printer 3 (for example, a request for a data update) (step S6), and printer 3 saves the received format file to storage 32 (step S8).

[0058] Subsequently, as shown in Figure 7, printer 3 reads the format file selected according to the user operation (step S10) and accepts the input of a call number (step S12). Next, printer 3 displays the issuance data called by the input call number as shown on printer screen g3 (Figure 7) (step S14), and the label becomes ready to be issued. Once the format file is obtained from server 5, the label issuance application of printer 3 can issue labels corresponding to each call number even in an offline environment.

[0059] (4) Managing edited tables Next, referring to Figures 11 to 14, we will explain how edited tables are managed in printer 3. As mentioned above, the format file downloaded by printer 3 includes a call table, a Kanji table, and a store name table (i.e., a master file). This master file contains data corresponding to labels used universally in all stores managed by headquarters. On the other hand, users of printer 3 in stores can edit the master file and save it as a master edit file in storage 32. This allows store users to create and save data for printing labels to be attached to store-specific products if they have store-specific products.

[0060] Figure 11 shows the procedure for a user of printer 3 in a store to edit a call table (master call table) as an example. Referring to Figure 11, if you select the "Master Editing" option on the printer settings screen g5, the printer screen will switch to g6, and a screen will appear where you can edit the master file for each format file (master editing). In master editing, you can edit the master call table, master Kanji table, and master store name table individually. For example, if you select the master call table as the editing target, the printer screen g7 for editing the master call table will be displayed. On the printer screen g7, selecting "New Registration," for example, adds issue data corresponding to a new call number to the master call table. In other words, it is possible to create an edited call table with the new issue data added to the master call table. In this case, as shown on the printer screens g8-g9, the user can create new issue data by entering the values ​​of each item included in the issue data.

[0061] Although not shown in the diagram, selecting "Copy and Register" on printer screen g7 allows you to create new issued data by copying the issued data contained in the master call table and changing the values ​​of some items. Selecting "Change" on printer screen g7 allows you to change some items of the issued data contained in the master call table. Selecting "Delete" on printer screen g7 allows you to delete at least one issued data contained in the master call table. In all cases, a new master editing file will be created by editing the master file. Figure 11 shows the procedure for editing the master call table, but the master Kanji table and master store name table can also be edited individually in the same way.

[0062] Figure 12 shows an example of the directory configuration in the storage 32 of the printer 3 according to this embodiment. As mentioned above, the master edit file created as shown in Figure 11 is recorded in a different storage area (second storage area) in storage 32 than the storage area (first storage area) where the original master file is stored.

[0063] As shown in Figure 12, storage 32 includes a FormatFiles folder, a Histories folder, a LocalTables folder, a Logs folder, and a Settings folder. The FormatFiles folder is a folder that stores layout data, a master call table, a master Kanji table, and a master store name table for each format file. The Histories folder contains publication history files for each format file. These publication history files include data such as the publication history of past labels (when, what kind of labels, and how many copies were issued). The LocalTables folder is a folder that stores the edited call table, edited Kanji table, and edited store name table for each format file. The Logs folder is where error information that occurred in the labeling application is recorded for later troubleshooting. The Settings folder is a folder that contains configuration information files.

[0064] As shown in Figure 12, in storage 32, the master files (master call table, master Kanji table, and master store name table) and the master edit files (edited call table, edited Kanji table, and edited store name table) are stored in different folders. In other words, the master files and master edit files are stored in different memory areas of storage 32. If you further edit the master editing file, the changes will be overwritten and saved to the master editing file already located in the LocalTables folder.

[0065] When updating data, the control unit 31 of printer 3 overwrites the master file contained in the corresponding format file in the FormatFiles folder of storage 32 with the master file contained in the format file downloaded from server 5. During this data update, the master editing file in the LocalTables folder of storage 32 is not updated. Therefore, in the information processing system 1 of this embodiment, when updating the data of printer 3 based on a format file received from PC 2 via server 5, it is possible to prevent the deletion of the master editing file, which contains data edited by printer 3.

[0066] In one embodiment, the headquarters may use a label creation application on PC2 to set whether or not master data editing is permitted on the store's printer 3. Figure 13 shows an example of the display of the object property setting unit 105 when each table is selected in the project file creation screen of PC2 according to the embodiment. In Figure 13, from left to right, the display state of the object property setting unit 105 is shown when the call table, Kanji table, and store name table are selected in the project setting unit 104, respectively. As shown in Figure 13, each table is provided with editing permission buttons 211 to 213, which are buttons for "Allow master editing in Print". By operating these buttons, it is possible to set whether or not to allow master editing by the label printing application of printer 3.

[0067] The settings made using the edit permission buttons 211-213 are reflected in the edit permission flags contained in each table information file. The label printing application on printer 3 refers to the edit permission flags in each table information file contained in the format file received via server 5 and individually determines whether editing is permitted for the call table, Kanji table, and store name table. In other words, the label printing application obtains each table information file from server 5, and if the edit permission flag contained in each obtained table information file indicates that editing is not permitted, it does not allow master editing. By allowing or denying editing, headquarters can decide on a table-by-table basis which tables are allowed to be edited by the store and which are not.

[0068] If multiple Kanji tables or multiple store name tables exist, you can set whether or not master editing is permitted for each individual table. For example, if Kanji Table 1, Kanji Table 2, Kanji Table 3, ... are set up, you can specify the corresponding table number (1, 2, 3, ...) and set whether or not master editing is permitted for each table individually. By setting whether or not master editing is permitted individually, you can flexibly set the degree of freedom for stores to issue their own labels.

[0069] Next, referring to Figure 14, this flowchart shows the process by which the printer 3 determines the table to be referenced when issuing a label based on the issuance data. The flowchart in Figure 14 is executed by the control unit 31 of the printer 3. As shown in Figure 12, when the master file is edited on printer 3 in the store, the master file and the master edit file will coexist. In that case, the priority of the tables to be referenced when reading the issuance data from the corresponding format file and issuing labels is defined by the flowchart in Figure 14.

[0070] In Figure 14, if, for example, one of the format files is selected by the printer screen g1 in Figure 7 (step S20: YES), the control unit 31 first reads the editing permission flag from each table information file contained in the selected format file (step S22). As mentioned above, the editing permission flag is a flag that indicates whether master editing is permitted for each table, and is set for the call table, the Kanji table, and the store name table, respectively.

[0071] The editing permission flag is referenced, and each process in steps S24 to S30 is performed sequentially for each table (step S32). Specifically, if the editing permission flag corresponding to the table to be processed indicates "permission", the LocalTables folder in storage 32 is referenced preferentially. In other words, if there is an edited table in the LocalTables folder (step S26: YES), the control unit 31 references the edited table in the LocalTables folder (step S28). If, in step S24, the editing permission flag corresponding to the table to be processed indicates "not permitted", or if there are no edited tables in the LocalTables folder (step S26: NO), the control unit 31 refers to a table in the FormatFiles folder (i.e., the master call table, the master Kanji table, or the master store name table) (step S30).

[0072] As shown in the flowchart in Figure 14, when printer 3 issues labels based on the issuance data, if an edited table exists in the LocalTables folder, that edited table is referenced preferentially. Therefore, users of printer 3 in stores can sequentially update the data for labels used universally across all stores managed by headquarters, while also issuing labels different from the universally used labels (labels to be affixed to store-specific products).

[0073] As explained with reference to Figure 13, allowing the headquarters to configure whether or not to permit master data editing by printer 3 at the store level has the following advantages. For example, some retail stores may change their operations so that all tables are centrally managed by headquarters from a certain point in time. In that case, even if headquarters wants all stores to issue labels based on the master file, if the store's printer 3 has a master editing file, the master editing file will be referenced preferentially, as shown in the flowchart in Figure 14, and the master file will not be referenced. Therefore, by allowing headquarters to set whether or not to allow master editing by printer 3 on a table-by-table basis, it is possible to control the system so that the master file (data in the FormatFiles folder) is referenced preferentially, even if a master editing file exists.

[0074] In one embodiment, the control unit 31 deletes the master editing file corresponding to the format file deleted from the printer 3 at the data update timing from the storage 32. During data update timing, format files that are no longer needed may be deleted from all stores managed by headquarters. In such cases, printer 3 deletes one of the format files stored in storage 32 based on instructions from PC 2 via server 5. At this time, since the deleted format file and the master editing file created based on that format file are stored in different folders, it is possible to keep the format file in storage 32 even after it has been deleted. However, since the master editing file cannot be used if it remains on its own and puts a strain on the capacity of storage 32, it is preferable to delete it.

[0075] As described above, according to the information processing system 1 of one embodiment, the printer 3 records the master file that is subject to data updates with the server 5 and the master edit file created by editing the master file by the user of the printer 3 in different storage areas of the storage 32. Therefore, for stores, it is possible to maintain the function of updating the master file with headquarters while preventing the master edit file used for store-specific products from being deleted from the printer 3 when data is updated.

[0076] (5) Backing up and restoring master editing files Next, the backup and restore of data in printer 3 will be explained with reference to Figures 15 to 19. If printer 3 malfunctions, for example, master editing files created by store users (edited call table, edited Kanji table, and edited store name table) will be lost. Therefore, the system is configured to ensure that master editing files can be backed up. Both automatic and manual backup methods are available. As will be described later, the data to be backed up is not limited to master editing files. In the following explanation, the data recorded on the backup destination server 5 or USB storage by the backup process performed by printer 3 may be referred to as "backup data".

[0077] Automatic backup involves backing up data by sending and recording it to the server 5 periodically (for example, at a predetermined time each day) or when the printer 3 is started up. Since automatic backup is performed without the user's awareness, it avoids situations where the user forgets to manually back up their data, which could hinder the recovery of the printer 3.

[0078] Manual backup is a method of backing up data by having the user manually record the data from printer 3 onto a USB storage device. Manual backups are provided for the following reasons: Firstly, it is more convenient for users of printer 3 to be able to manually back up their data when they use printer 3 without connecting to server 5. Secondly, when service technicians from the manufacturer or distributor of printer 3 come to the store to investigate the cause of a malfunction or other issue with printer 3, they can back up the data from printer 3 to USB storage and take it with them, thereby enabling a quicker resolution. Furthermore, manual backups offer the advantage of making it easier to perform the kitting work for multiple printers using USB storage. For example, by repeatedly backing up data from the first printer to USB storage and then restoring the data from the second printer to the USB storage, the burden of kitting multiple printers is reduced.

[0079] As will be explained later, manual backups back up all data to be backed up, while automatic backups back up data only if there are differences between the data to be backed up and the previous backup data.

[0080] Furthermore, the data backup destination is not limited to USB storage or server 5; it may also be the internal storage 32 of printer 3. By using storage 32 as the data backup destination, it becomes easy to restore the system if the user makes a mistake in changing settings or modifies the master file.

[0081] (5-1) Automatic backup Next, automatic backups will be explained further with reference to Figures 15 to 17. Figure 15 shows the procedure for setting up automatic backup on printer 3. Referring to Figure 15, if you select the "External Storage Linkage Management" item on the printer settings screen g10, the screen switches to printer screen g11. Next, if you select the "Data to be Linked" item, printer screen g12 is displayed, where you can configure the details of data download and upload between server 5 and printer 3. Note that printer screen g12 can only be displayed if "External Storage Linkage" is enabled in "External Storage Linkage Management" on printer screen g11. On the printer screen g12, the "Upload" section includes "[Backup] Master Edit File" and "[Backup] Configuration Information File" options, with buttons to enable or disable automatic backup of the master edit file and configuration information file, respectively. By moving these buttons to the enabled position, automatic backup of the master edit file and configuration information file can be performed individually. Although not shown in the diagram, the timing of automatic backups (for example, a predetermined time each day) can be set by the user.

[0082] The data subject to automatic backup includes, for example, format files, master editing files (edited call tables, edited Kanji tables, edited store name tables), and configuration information files.

[0083] Figure 16 shows an example of the directory configuration in the storage 52 of the server 5 according to this embodiment. As shown in Figure 16, storage 52 includes a FormatFiles folder, a Logs folder, a BackupFiles folder, and a Settings folder. The FormatFiles folder contains the format files uploaded from PC2. The Logs folder contains the print history files uploaded from printer 3. The BackupFiles folder contains backup data for each printer ID (e.g., "0001-SX-5555") of printer 3 that can connect to server 5. The Settings folder is a folder that contains configuration information files.

[0084] As shown in Figure 16, a folder (YYYYMMDD-hhmmss folder) is automatically created within the BackupFiles folder for each specific printer 3, indicating the time when an automatic backup was performed. For example, if an automatic backup was performed on April 25, 2022 at 21:08:38, the automatically created folder will be named "20220425-210838". The YYYYMMDD-hhmmss folder contains the LocalTables folder and the Settings folder. The LocalTables folder contains data where the master editing files have been backed up for each format file. The Settings folder contains backed-up configuration information files.

[0085] Automatic backups are performed periodically, for example. During this time, printer 3 uploads the master edit file stored in the LocalTables folder to server 5. If there is a difference between the previously uploaded master edit file and the currently uploaded master edit file, server 5 creates a folder indicating the time of the current upload (YYYYMMDD-hhmmss folder) and records the currently uploaded master edit file in the YYYYMMDD-hhmmss folder (see Figure 16).

[0086] Next, with reference to Figure 17, the automatic backup process in Information Processing System 1 will be explained. Figure 17 is a sequence chart for when the information processing system 1 performs automatic backup processing of edited tables.

[0087] The sequence chart in Figure 17 also includes the data update process performed by printer 3. Specifically, at the time of data update, printer 3 sends a data update request to server 5 (step S38). Server 5 responds to the data update request by sending update data for the format file (including, for example, an update master file) to printer 3 (step S40), and printer 3 performs data update processing based on the update data (step S42). In the data update process, for example, the master file stored in storage 32 is overwritten and updated by the master file included in the update data.

[0088] When the pre-set automatic backup time arrives, printer 3 sends the master editing file and / or configuration information file stored in storage 32 to server 5 (step S44). The files sent will follow the settings on printer screen g12 in Figure 15. Server 5 determines whether there is any difference between the data (master editing file or configuration information file) at the time of the previous automatic backup (for example, the previous day) and the data (master editing file or configuration information file) received in step S44 (step S46). If there is a difference in both files or either file, Server 5 generates a YYYYMMDD-hhmmss folder (see Figure 16) based on the time the files were received in step S44, and records the data received in step S44 (master editing file and configuration information file) as new backup data in the generated YYYYMMDD-hhmmss folder (step S48). The configuration information file received in step S44 is recorded as is in the YYYYMMDD-hhmmss folder. In one embodiment, the server 5 deletes old backup data (step S50). That is, since storing old backup data indefinitely would put a strain on the capacity of the storage 52, it is preferable to delete old backup data sequentially.

[0089] (5-2) Manual backup Next, manual backups will be explained further with reference to Figure 18. Figure 18 shows the procedure for setting up manual backup on printer 3. Note that the procedure shown in Figure 18 assumes that the USB storage device to be used as the backup destination is connected to printer 3. Referring to Figure 18, if the "System Management" item is selected on the printer settings screen g13, the screen switches to printer screen g14. Next, if the "Backup / Restore" item is selected, printer screen g15 is displayed. If the "Backup" item is selected here, the backup screen is displayed as shown on printer screen g16. Printer screen g16 includes an input area 301 for the user to enter comments.

[0090] Entering comments in input area 301 is useful when restoring printer 3. When multiple manual backups are performed, comments (text) are associated with the data backed up each time. That is, when printer 3's control unit 31 backs up the master editing file, it accepts text input from the user and associates the entered text with the master editing file to be backed up. This allows the user to select the data to use during restoration from among multiple backup data sets, according to the content of the comments. For example, by entering "Data after setting XX" as a comment, it becomes easier to select the data during restoration.

[0091] In the case of manual backups, just like with automatic backups, a folder named YYYYMMDD-hhmmss is created on the USB storage device at the backup destination, and the backup data is recorded within this folder. At that time, the created YYYYMMDD-hhmmss folder is associated with the text entered in input area 301. Manual backups are not limited to master editing files and configuration information files; all folders are included.

[0092] (5-3) Restore Next, the procedure for restoring (recovering) Printer 3 based on data backed up by automatic or manual backup will be explained with reference to Figure 19. Figure 19 shows the procedure for restoring data on Printer 3. Note that if the backup data is stored on a USB storage device, it is assumed that the USB storage device is connected to Printer 3.

[0093] Referring to Figure 19, when the "Restore" option is selected on the printer settings screen g15, the screen switches to printer screen g17. Printer screen g17 is configured to allow the user to operate a selection button 302 for selecting the printer 3 to be restored and a selection button 303 for selecting the backup data. To ensure the security of manual backups, it is preferable that printer screen g15 (settings screen) be displayed only after successful authentication using the user's ID and password.

[0094] The selection button 303 allows you to choose either the name of the YYYYMMDD-hhmmss folder on server 5, which is the automatic backup destination, or the name of the YYYYMMDD-hhmmss folder on the USB storage device, which is the manual backup destination, along with a comment. After selecting the printer 3 to restore and the backup data, pressing the OK button displays the printer screen g18 as a restore confirmation screen. The select button 303 displays the name of the selected YYYYMMDD-hhmmss folder along with its associated text (e.g., "Backup"), making it easier for the user to select the desired backup data when multiple backup data sets exist. The printer screen g18 has a group of checkboxes 304. These checkboxes allow the user to select which folders from the YYYYMMDD-hhmmss folder to use during the restore process (at least one of the FormatFiles, LocalTables, and Settings folders). Pressing the OK button on the printer screen g18 executes the restore process.

[0095] In Figure 19, the printer screen g15, which is related to settings, has an item called "Backup Generation Setting." By selecting this item, the number of backup data generations to be stored on server 5 can be set. For example, one of the values ​​from 1 to 9 can be selected for the generation setting. In other words, the control unit 31 of printer 3 sets the maximum number of backup data stored in the storage 52 of server 5 based on the user's input. This maximum value is notified to server 5, for example, when an automatic backup is performed. For example, if "3" is selected as the generation setting, it means that three sets of backup data will be saved. In step S50 of Figure 17, the server 5 determines which backup data to delete based on the backup generation setting value obtained from the printer 3. That is, the control unit 51 of the server 5 functions as a data deletion unit that deletes backup data previously recorded in the storage 52 based on the above maximum value set by the printer 3. Backup generation settings can be applied to both automatic and manual backups. By configuring backup generation settings, you prevent older backup data that is not needed during restoration from being stored in the backup destination, thus avoiding putting a strain on the capacity of your storage 52 or USB storage.

[0096] As described above, in one embodiment of the information processing system 1, the printer 3 automatically backs up data to the server 5 periodically, and also manually backs up data to USB storage at the user's request, ensuring reliable backup of data created on the printer, such as master editing files. In this case, with automatic backup, data is saved to the server 5 only when it has been modified by editing on the printer 3, thus avoiding putting a strain on the server 5's capacity. Manual backup allows users of the printer 3 who cannot access the server 5 to back up data by directly connecting USB storage to the printer 3, and is also convenient when a service technician needs to retrieve data from the printer 3 when diagnosing a malfunction.

[0097] In automatic backups, the master edit file may be backed up as differential data. That is, automatic backups are performed periodically, for example, and at this time, printer 3 uploads the master edit file stored in the LocalTables folder to server 5. Server 5 records data (differential data) that shows the difference between the master edit file uploaded last time and the master edit file uploaded this time. At that time, server 5 creates a folder (YYYYMMDD-hhmmss folder) that shows the time of the current upload and records the differential data in the YYYYMMDD-hhmmss folder. Figure 20 shows an example of the directory configuration in the storage 52 of server 5 according to one embodiment. The difference from Figure 16 is that differential data is stored in storage 52 as backup data. In Figure 20, the difference between the current edited call table and the previous edited call table is called the "differential call table," the difference between the current edited Kanji table and the previous edited Kanji table is called the "differential Kanji table," and the difference between the current edited store name table and the previous edited store name table is called the "differential store name table." Since the master file is known on server 5, the latest master edited file can be reproduced during the restore process described later, based on the master file and one or more differential data sets that are automatically backed up each time.

[0098] Figure 21 is a sequence chart showing the automatic backup process when backing up differential data. In Figure 21, steps S38 to S44 are the same as in the sequence chart in Figure 17, so a redundant explanation is omitted. When Server 5 receives the master edit file from Printer 3, it extracts the difference data between the latest file already backed up in Storage 52 and the master edit file received in step S44 (step S52). Based on the time the file was received in step S44, Server 5 creates a YYYYMMDD-hhmmss folder (see Figure 20) and records the difference data in the created YYYYMMDD-hhmmss folder (step S54). The configuration information file received in step S44 is recorded directly in the YYYYMMDD-hhmmss folder. In one embodiment, the server 5 deletes old differential data (step S56). That is, since storing old differential data indefinitely would strain the capacity of the storage 52, it is preferable to delete the old differential data sequentially.

[0099] Although one embodiment of the information processing system, printer, and program of the present invention has been described in detail above, the present invention is not limited to the above embodiment. Furthermore, the above embodiment can be improved or modified in various ways without departing from the spirit of the present invention. [Explanation of Symbols]

[0100] 1… Information processing system 2… Computer device 21... Control Unit 22…Storage 23... Operation Input Section 24…Display section 25…LAN interface 26…USB Interface 3…Printer 31…Control Unit 311...Data update unit 312...Data Editorial Department 313...Printing Control Unit 314...Automatic backup processing unit 315...Manual Backup Processing Unit 316... Backup generation setting section 317…Restore Processing Unit 32...Storage 33... Operation input section 34…Display section 35…Conveyor Unit 36…Printing section 37…LAN interface 38…USB interface 5…Server 51... Control Unit 511...Data recording unit 512...Data Deletion Section 52...Storage 53... Communications Department 101... Instruction button group 102... Layout setting button group 103... Design Window 104...Project Setup Department 105...Object property setting section 204... Output destination selection section 206...Issuance data display section 207... Input box group 211-213... Edit permission / deny button 301...Input area 302, 303… Select button 304... Checkboxes OBJ1~OBJ4...Objects SK…Software keyboard TL1…Call table definition data TL2... Call Table TL3... Kanji Table TL4...Store Name Table

Claims

1. An information processing system including an information processing device and a printer capable of communicating with the information processing device, The aforementioned printer is A storage unit having a first storage area for storing reference data that is referenced when printing, and a second storage area which is a storage area different from the first storage area, A data update unit, which receives new reference data from the information processing device, updates the reference data stored in the first storage area with the new reference data. A data editing unit that edits the reference data based on user input, records the edited data (the reference data after editing) in the second storage area, or updates the edited data in the second storage area as needed. A first backup processing unit that periodically backs up the edited data in the second storage area to the information processing device, or when the printer is started, The system includes a second backup processing unit that backs up the edited data in the second storage area to an external storage device in response to user operations, The aforementioned information processing device is The printer is equipped with a data recording unit that records the edited data to be backed up in a storage unit if there is a difference between the edited data from the most recent edit and the edited data from the previous edit. Information processing system.

2. The printer has editing permission information for each print target, indicating whether or not editing by the data editing unit is permitted, When printing, if the editing permission information indicates editing permission and edited data corresponding to the reference data to be printed in the first storage area exists in the second storage area, the edited data is referenced. If the editing permission information indicates that editing is not permitted, or if edited data corresponding to the reference data to be printed in the first storage area does not exist in the second storage area, the reference data to be printed in the first storage area is referenced. The information processing system described in claim 1.

3. The printer is capable of communicating with the information processing device via a network, The external storage device is directly connected to the printer. The information processing system described in claim 1.

4. The printer includes a setting unit that sets the maximum number of edited data to be backed up by the information processing device based on user input. The information processing device includes a data deletion unit that deletes previously recorded edited data in the storage unit of the information processing device based on the maximum value set by the setting unit. The information processing system described in claim 1.

5. The second backup processing unit accepts text input from the user when backing up the edited data, and associates the input text with the edited data to be backed up. An information processing system according to any one of claims 1 to 4.

6. The printer includes a restore processing unit that performs a restore based on the edited data backed up in the storage device, The restore processing unit, when performing a restore, displays the edited data backed up in the storage device along with the associated text. The information processing system described in claim 5.

7. A printer capable of communicating with an information processing device, A storage unit having a first storage area for storing reference data that is referenced when printing, and a second storage area which is a storage area different from the first storage area, A data update unit, which receives new reference data from the information processing device, updates the reference data stored in the first storage area with the new reference data. A data editing unit that edits the reference data based on user input, records the edited data (the reference data after editing) in the second storage area, or updates the edited data in the second storage area as needed. A first backup processing unit that periodically backs up the edited data in the second storage area to the information processing device, or when the printer is started, A second backup processing unit backs up the edited data in the second storage area to an external storage device in response to user operation, A printer equipped with [a specific feature / ability].

8. A program executed in a printer capable of communicating with an information processing device, The aforementioned printer is The storage unit includes a first storage area for storing reference data that is referenced when printing, and a second storage area which is a different storage area from the first storage area. The aforementioned program, the computer, When new reference data is received from the information processing device, a data update unit updates the reference data stored in the first storage area using the new reference data. A data editing unit that edits the reference data based on user input, records the edited data (the reference data after editing) in the second storage area, or updates the edited data in the second storage area as needed. A first backup processing unit that periodically backs up the edited data in the second storage area to the information processing device, or when the printer is started, and A second backup processing unit backs up the edited data in the second memory area to an external storage device in response to user operation. A program designed to function as such.

Images