Portable image forming apparatus and program

Abstract

To provide a portable type image formation apparatus and program which can restrict a function according to the loss and the like.SOLUTION: A printer 17 of a printing system 10 acquires a printing instruction including a management object ID 51 from a terminal device 15 via a first communication IF 61 or the like in such a state that a management object ID 72 is stored in a printer storage unit 69 (S51). The printer 17 determines whether or not to permit printing by a printing unit 64 on the basis of the acquired management object ID 51 and the management object ID 72 of the printer storage unit 69 (S69). The printer 17 prints the image data of the printing instruction by the printing unit 64 (S65) when the printing is permitted (S69:YES). The printer 17 does not execute the printing of the image data (S73, S75) when the printing is not permitted (S69:NO).SELECTED DRAWING: Figure 10

Description

[Technical field]

[0001] The present application relates to a portable image forming apparatus and a program. [Background technology]

[0002] Various techniques for managing portable image forming devices have been proposed in the past. For example, the following Patent Document 1 describes a technique for managing the deterioration level of a rechargeable battery included in a portable printer using a management terminal. The management terminal receives a user ID and deterioration level information from the printer, and calculates the battery voltage value required to use the printer by referring to data such as the user's usage time based on the user ID. The management terminal determines, from among the registered rechargeable batteries, a rechargeable battery with a voltage equal to or higher than the calculated battery voltage value, and notifies the user. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2020-135583 A Summary of the Invention [Problem to be solved by the invention]

[0004] However, there is a possibility that a portable printer such as the printer disclosed in Patent Document 1 may be lost when a user takes the printer away from the office on a business trip. In this case, it is desirable to restrict the functions of the lost printer from a security standpoint.

[0005] The present application discloses a technique for solving the above-mentioned problems, and discloses a portable image forming apparatus and a program capable of restricting functions in the event of loss or the like. [Means for solving the problem]

[0006] The portable image forming device disclosed in this specification comprises an image forming unit that forms an image, a memory unit capable of storing first identification information, a communication interface capable of communicating with an information processing device, and a control unit, and the control unit executes the following steps: an acquisition process for acquiring an image formation instruction including second identification information and image data to be formed from the information processing device via the communication interface while the first identification information is stored in the memory unit; a judgment process for determining whether to permit image formation by the image forming unit based on the second identification information acquired in the acquisition process and the first identification information stored in the memory unit; an image formation process for performing image formation by the image forming unit based on the image data if it is determined as a result of the judgment process that image formation is permitted; and a restriction process for restricting image formation based on the image data if it is determined as a result of the judgment process that image formation is not permitted.

[0007] Furthermore, the contents disclosed in this specification are not limited to implementation as a portable image forming apparatus, and may also be usefully implemented as, for example, a computer-readable program for an information processing apparatus. Effect of the Invention

[0008] According to the portable image forming apparatus and the program configured as above, the functions can be restricted in case of loss or the like. [Brief description of the drawings]

[0009] [Figure 1] 1 is a schematic configuration diagram of a printing system according to an embodiment. [Diagram 2] FIG. 2 is a block diagram of the printing system shown in FIG. [Diagram 3] FIG. 13 is a diagram showing data stored in a management DB. [Figure 4] 11 is a sequence diagram showing the processes of the printer and the server in the managed ID storage process. FIG. [Diagram 5] 11 is a flowchart showing an ID storage process executed by a printer. [Figure 6]13 is a flowchart showing an ID storage process executed by a printer according to another example. [Figure 7] 10 is a flowchart showing a start-up process performed by the terminal device by executing an application. [Figure 8] FIG. 4 is a sequence diagram showing the processing of the terminal device and the printer in the printing process. [Figure 9] 10 is a flowchart showing a printing process performed by the terminal device by executing an application. [Figure 10] 4 is a flowchart showing a printing process executed by the printer. [Figure 11] FIG. 11 is a diagram showing a state in which a plurality of printers are used by one terminal device. [Figure 12] 6 is a flowchart showing a startup process executed by the printer. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] Hereinafter, a printing system 10, which is an embodiment of a portable image forming apparatus and a program according to the present application, will be described with reference to the drawings. FIG. 1 is a schematic diagram of the printing system 10, and FIG. 2 is a block diagram of the printing system 10. As shown in FIGS. 1 and 2, the printing system 10 includes a server 11, a management PC 13, a plurality of terminal devices 15, and a plurality of printers 17. For example, a company that uses the printing system 10 lends the terminal device 15 and the printer 17 to a user (such as an employee in charge of sales). The user can execute printing using the printer 17 by operating the terminal device 15. The server 11 is, for example, a management server that manages the terminal device 15. The administrator of the terminal device 15 and the printer 17 (such as a company system administrator) can use the management function of the server 11 to restrict the function of the terminal device 15 by operating the management PC 13. The server 11 also manages the printer 17 using a managed ID 72, which will be described later. The printer 17 changes the operation of its own device according to the managed ID 51 of the terminal device 15 and the managed ID 72 of its own device.

[0011] More specifically, the server 11 is, for example, a Mobile Device Management (MDM) server, which is a server that centrally manages a plurality of terminal devices 15 that are to be managed. The server 11 includes a server control unit 21 and a communication IF (abbreviation of interface) 22. The server control unit 21 and the like are capable of communicating with each other via a communication bus 23. The communication IF 22 is, for example, a LAN interface, and is connected to a network 19. The network 19 includes, for example, a wide area network such as the Internet, a LAN, and mobile communication networks such as 4G and 5G.

[0012] The server control unit 21 performs overall control of the server 11. The server control unit 21 includes a server storage unit 24 and a server CPU 25. The server storage unit 24 is configured, for example, by combining a RAM, a ROM, and a HDD. The server storage unit 24 stores a server program 27 and a management DB (abbreviation of database) 28. The server program 27 is a program that causes the server 11 to execute various processes. For example, the server control unit 21 controls access to the server 11 by executing the server program 27 in the server CPU 25. In addition, the server control unit 21 executes the server program 27 in the server CPU 25 to restrict functions of the terminal device 15 that is a subject of management of the MDM, based on instructions obtained from the management PC 13.

[0013] In the following description, the server control unit 21 that executes the server program 27 on the server CPU 25 may be described simply as a device name or a program name. For example, the description "the server 11 acquires an instruction from the management PC 13 via the communication IF 22" means that "the server control unit 21 executes the server program 27 on the server CPU 25 to control the communication IF 22 and acquires an instruction from the management PC 13 via the communication IF 22." The same applies to the management PC 13 that executes the management program 38 described below, the terminal device 15 that executes the OS program 49 and the application 50, and the printer 17 that executes the printer program 71. In addition, in this application, "acquire" is used as a concept that does not necessarily require a request. In other words, the process in which the server 11 receives an instruction without making a request is also included in the concept of "the server 11 acquires an instruction."

[0014] The management DB 28 stores information related to the printer 17 managed by the server 11. The server 11 of this embodiment manages not only the terminal devices 15 but also the printer 17. The server 11 may not have an MDM function, that is, it may not have a function for managing the terminal devices 15 and may be a server that manages only the printer 17.

[0015] FIG. 3 shows an example of data stored in the management DB 28. As shown in FIG. 3, for example, the printer ID, the managed ID 72, and the application ID of the printer 17 to be managed are stored in the management DB 28 in association with each other. The printer ID is information capable of identifying a plurality of printers 17, and is, for example, a serial number set by a vendor. The managed ID 72 is information stored in the printer 17, as described later, and is, for example, information generated by the printer 17 and registered in the server 11. The managed ID 72 is also stored in the terminal device 15, for example, by an input operation by the user of the terminal device 15. In the following description, the managed ID of the terminal device 15 is referred to as the managed ID 51 to distinguish it from the managed ID 72 of the printer 17. The managed IDs 51 and 72 are used to confirm whether the terminal device 15 that issued the print instruction is a legitimate user. The managed ID 72 is, for example, unique information given to each printer 17, and is information generated from the printer ID (such as a vendor's serial number). If the printing system 10 is a system in which printers 17 from multiple vendors coexist, the managed ID 72 may be information including the serial number of each vendor and the model name of the printer 17, or information generated from such information. The managed ID 72 may be the same information as the printer ID. The managed ID 72 may be the same information for multiple terminal devices 15 and printers 17, for example, the same information for each group that shares multiple printers 17.

[0016] The application ID is information capable of identifying an application program (hereinafter, referred to as an application) 50 of the terminal device 15 described later, and for example, a different value is set for each application 50. The server 11 has data (not shown) related to the terminal device 15 to be managed, and can individually transmit instructions to identify the terminal device 15 and restrict functions based on the data in response to loss of the terminal device 15, etc.

[0017] Next, the management PC 13 will be described. In the following description of the management PC 13, the terminal device 15, and the printer 17, the same contents as those of the server 11 described above will be omitted as appropriate. The management PC 13 is, for example, a notebook or desktop personal computer. The management PC 13 includes a CPU 31, a storage unit 32, a user IF 33, a display 34, and a communication IF 35. The CPU 31 and the like can communicate with each other via a communication bus 37. The management PC 13 executes various processes by executing a management program 38 stored in the storage unit 32 with the CPU 31. The management PC 13 changes the display contents of the display 34 in response to an operation input to the user IF 33 (such as a mouse or keyboard). The management PC 13 can also be connected to the network 19 via the communication IF 35.

[0018] Next, the terminal device 15 will be described. The terminal device 15 is an example of an information processing device of the present application, for example, a smartphone. The information processing device of the present application is not limited to a smartphone, and may be a tablet terminal or a notebook PC. The terminal device 15 includes a terminal control unit 41, a first communication IF 43, a second communication IF 44, and a touch panel 45. The terminal control unit 41 and the like are capable of communicating with each other via a communication bus 46.

[0019] The terminal control unit 41 controls the terminal device 15 in an overall manner, and includes a terminal storage unit 47 and a terminal CPU 48. The terminal storage unit 47 is configured by combining, for example, RAM, ROM, and the like. An OS program 49 and an application 50 are stored in the terminal storage unit 47. The OS program 49 is a program that controls the terminal device 15 in an overall manner, and provides basic functions and services to the application 50. The OS program 49 is, for example, Android (registered trademark) OS or iOS (registered trademark). In addition, when the terminal device 15 is, for example, a notebook PC, the OS program 49 is, for example, Windows (registered trademark) OS.

[0020] The application 50 is, for example, a program provided by the vendor of the printer 17, and is a program that uses the functions of the OS program 49, etc. to send print instructions to the printer 17, obtain setting information for the printer 17, send setting instructions to the printer 17, etc. The terminal control unit 41 executes the OS program 49 and the application 50 in the terminal CPU 48, and controls the operation of the terminal device 15.

[0021] Therefore, the server program 27 of the server 11 and the management program 38 of the management PC 13 include a program compatible with MDM capable of controlling the terminal device 15 that runs on the Android (registered trademark) OS or the like. For example, the administrator can operate the management PC 13 and use the MDM function of the server 11 to execute various controls on the terminal device 15. The various controls referred to here are, for example, restriction controls such as limiting functions such as communication functions in each of the terminal devices 15 to be managed, deleting data on the terminal device 15, initializing, screen locking, and loss locking. The screen lock referred to here is, for example, control that displays a screen on the touch panel 45 for inputting authentication information such as a password or a fingerprint, and prohibits operation of the terminal device 15 using the touch panel 45 or the like until authentication of the authentication information is established. The loss lock is, for example, control that stops all functions other than turning the power on and off in response to the loss of the terminal device 15. The server 11 may be a server capable of at least one of the above-mentioned restriction controls such as limiting functions, deleting data, initializing, screen locking, and loss locking.

[0022] Furthermore, the server 11 has a MAM (Mobile Application Management) function in addition to the MDM function. For example, the server 11 can control the installation of the application 50 on the terminal device 15 and the setting of parameters at the time of installation based on an instruction from the management PC 13. Furthermore, the terminal storage unit 47 stores a managed ID 51. There is no particular limitation on the method of storing the managed ID 51 in the terminal storage unit 47, but for example, as described later, a method of accepting an operational input from a user (see FIG. 7) can be adopted. Alternatively, a method of storing the managed ID 51 in the terminal storage unit 47 when the application 50 is installed by utilizing the above-mentioned MAM function may be adopted.

[0023] The first communication IF 43 is a communication interface capable of performing short-distance wireless communication such as Bluetooth (registered trademark) and NFC. The terminal device 15 can communicate with the printer 17 via the first communication IF 43 and can transmit a print instruction or the like to the printer 17. The second communication IF 44 is a communication interface capable of communication with a network of a mobile communication system such as 4G or 5G and wireless communication such as Wi-Fi (registered trademark). The terminal device 15 is connected to the network 19 via the second communication IF 44. The terminal device 15 can communicate with the printer 17 also via the second communication IF 44 and can transmit a print instruction or the like to the printer 17. The terminal device 15 may be connected to the network 19 by a wire. The above-mentioned communication method is an example and can be changed as appropriate. The first communication IF 43 may be configured to communicate with the printer 17 by the WFD (abbreviation of Wi-Fi Direct (registered trademark)) method established by the Wi-Fi Alliance.

[0024] Furthermore, the terminal device 15 accepts user operation input via the touch panel 45. Furthermore, the terminal device 15 displays various information on the touch panel 45. Note that the user IF provided in the terminal device 15 is not limited to the touch panel 45, and in addition to or instead of the touch panel 45, a button switch or a slide switch may be provided.

[0025] Next, the printer 17 will be described. The printer 17 is, for example, a portable printing device that can be carried around, and prints image data of a print job acquired via wired or wireless communication with the terminal device 15 onto a sheet (such as thermal paper). The printer 17 includes a first communication IF 61, a second communication IF 62, a power supply unit 63, a printing unit 64, a user IF 65, and a printer control unit 67. The first communication IF 61 and the like are capable of communicating with each other via a communication bus 68.

[0026] The first communication IF 61 is a communication interface capable of short-range wireless communication such as Bluetooth (registered trademark), and communicates with the first communication IF 43 of the terminal device 15. The second communication IF 62 is a communication interface capable of communication via, for example, a wireless LAN such as Wi-Fi (registered trademark) or a wired LAN. The printer 17 can be connected to the network 19 by, for example, connecting to an access point at a company or on the road via the second communication IF 62.

[0027] The power supply unit 63 includes, for example, a power supply circuit and a battery that generate power from the commercial power supply to be supplied to each device in the printer 17. Therefore, even when the printer 17 is not connected to the commercial power supply, the printer 17 can perform printing operations using the battery as a power source. The power supply unit 63 may be configured to include only one of a power supply circuit and a battery that can use a commercial power source. The portable image forming device of the present application is not limited to the battery-powered printer 17, but may also be other portable image forming devices such as a label printer, a receipt printer, or a battery-powered FAX device or scanner device. The printer 17 may also include multiple functions among the printing function, FAX function, scanner function, and copy function.

[0028] The printing unit 64 includes, for example, a thermal head and prints an image on a sheet by a direct thermal method. The printing unit 64 may be configured to print by an electrophotographic method or an inkjet method. The user IF 65 is, for example, a touch panel, a push button switch, etc., and receives operation input from the user and displays various information. The printer 17 may not include a touch panel and may include only switches such as push button switches and slide switches.

[0029] The printer control unit 67 controls the printer 17 in an integrated manner. The printer control unit 67 includes a printer storage unit 69 and a printer CPU 70. The printer storage unit 69 is configured by combining a RAM, a ROM, and the like. The printer storage unit 69 can store a printer program 71, a managed ID 72, contact information 73, template data 74, personal information 75, and a mode flag 76. The printer program 71 is, for example, firmware that controls each unit of the printer 17 in an integrated manner. The printer control unit 67 executes the printer program 71 with the printer CPU 70 to control the printing unit 64 and the like. The contact information 73 is, for example, information indicating the contact information (address, telephone number, email address, etc.) of the owner (manager or company) of the printer 17. For example, the manager operates the user IF 65 to store the contact information 73 in the printer storage unit 69 before lending the printer 17 to an employee.

[0030] The template data 74 is, for example, data of a template used when printing standard documents such as receipts and reports, or data typically used for documents such as a company logo. The personal information 75 is, for example, data to be inserted into a template, such as the name and department of the user of the printer 17, the customer name, and the customer address. The printer 17 executes printing using, for example, a template or personal information specified in a print job. Alternatively, the printer 17 executes printing using a preset template or personal information based on a predetermined operation on the user IF 65.

[0031] The mode flag 76 is a flag value indicating whether the printer 17 is in lost mode. When a value indicating ON is set in the mode flag 76, the printer 17 transitions to lost mode. When a value indicating OFF is set in the mode flag 76, the printer 17 transitions to a state in which the lost mode is OFF (hereinafter, referred to as normal mode). Here, the terminal device 15 and the printer 17 described above are portable devices. For example, a user who is an employee takes the terminal device 15 and the printer 17 out of the company and uses them at a business destination. Alternatively, the printer 17 can be used in various places, such as events and stores, not limited to using the printer 17 at the company. In this case, the terminal device 15 and the printer 17 may be lost at a business trip or the like. The printing system 10 of this embodiment can restrict the functions of the terminal device 15 based on an instruction from the management PC 13.

[0032] Furthermore, if the printer 17 is lost, there is a possibility that the printer 17 will be used illegally, consumables such as sheets will be consumed by a third party, parts such as the thermal head will deteriorate through use, or personal information 75 will be leaked through printing, etc. Therefore, as will be described later, the printer 17 will switch to lost mode in accordance with the determination result based on the managed IDs 51 and 72, and restrict the functions of the printer itself. Although details will be described later, when the printer 17 switches to lost mode, it restricts functions such as operations on the user IF 65. In normal mode, the printer 17 does not execute the function restrictions in lost mode, and is in a state where it can accept operations via the user IF 65.

[0033] (Managed ID storage process) Next, the managed ID storage process executed by the printing system 10 will be described with reference to Figs. 4 to 6. Fig. 4 shows the process of the printer 17 and the server 11 in the managed ID storage process. The printing system 10 executes the managed ID storage process to store the managed ID 72 in the printer 17 and register it in the server 11. Fig. 4 shows the sequence when S23 described later is executed. In Fig. 4, the operation by the user is indicated by an arrow pointing downward to the left. In addition, the sequence diagrams and flowcharts in this specification basically show the process of the CPU (server CPU 25, CPU 31, terminal CPU 48, printer CPU 70) according to the command written in each program. That is, the process of "inquiry", "determination", etc. in the following description represent the process of the CPU. The process by the CPU also includes hardware control via the program. In addition, "data" in this specification is represented by a bit string that can be read by a computer. And, data with the same substantial meaning and different formats are treated as the same data. The same applies to "information" in this specification.

[0034] As shown in step (hereinafter simply referred to as "S") 11 in Fig. 4, for example, an administrator or user of the printer 17 operates the user IF 65 to power on the printer 17. The administrator, for example, operates the user IF 65 to execute network settings for the first communication IF 61 and the second communication IF 62 of the printer 17, and sets the printer 17 in a state in which it can communicate with the terminal device 15 and the server 11. Fig. 5 shows an ID storage process executed by the printer 17. For example, when the printer 17 is powered on and the server CPU 25 executes the server program 27, the printer 17 starts the process shown in Fig. 5. The printer 17 may start the process of Fig. 5 from the point in time when the network settings are completed, or may start the process of Fig. 5 after the network settings are completed and the printer 17 is powered on again.

[0035] In S13 of Fig. 5, the printer 17 determines whether or not it is necessary to register the managed ID 72 with the server 11. The printer 17 executes a process of, for example, inquiring of the server 11 via the network 19 as to whether the managed ID 72 is registered (S15 of Fig. 4). The access destination (URL, etc.) of the server 11 to which the printer 17 makes an inquiry may be set in the printer 17 in advance by an administrator, or may be input using the user IF 65. The printer 17 transmits its own printer ID and data requesting confirmation of registration to the server 11 (S15).

[0036] When the server 11 receives the inquiry of S15, it searches the management DB 28 based on the obtained printer ID (S17) and returns the search result to the printer 17 (S19). For example, if the search result of S17 shows that the printer ID is stored in the management DB 28 in association with the managed ID 72, the server 11 returns a search result indicating that the printer ID has been registered (S19). Also, if the printer ID has not been registered, or if the printer ID has been registered but the managed ID 72 has not been registered, the server 11 returns a search result indicating that the printer ID has not been registered (S19).

[0037] The method of checking whether the managed ID 72 has been registered in the server 11 is not limited to the above-mentioned method of inquiring of the server 11. For example, the printer 17 may store a flag value indicating whether registration in the server 11 has been completed. For example, this flag value is set to a value indicating incomplete as an initial value. When the registration process in the server 11 (S25) described below is completed, the printer 17 changes this flag value to a value indicating completion. In this way, the printer 17 can determine whether registration has been completed by determining the flag value in S13, without inquiring of the server 11.

[0038] When the printer 17 obtains a search result indicating that the printer 17 has been registered from the server 11 in S19, the printer 17 makes a negative determination in S13 (S13: NO) and ends the process shown in FIG. 5. Also, when the printer 17 cannot communicate with the server 11, the printer 17 may make a negative determination in S13 (S13: NO). This allows the printer 17 to be started without executing the registration process of the managed ID 72 in the event of a failure in the network 19 or when the network is not yet configured. In this case, as will be described later, when the printer 17 receives a print instruction, the printer 17 executes printing without determining whether the managed IDs 51 and 72 match (see S63: NO in FIG. 10). Alternatively, for example, when the printer 17 is set not to execute print control using the managed ID 72, the printer 17 may determine that registration of the managed ID 72 is unnecessary (S13: NO). In this case as well, the printer 17 can execute printing without determining whether the managed IDs 51 and 72 match. Furthermore, the printer 17 may receive an instruction from the user via the user IF 65 as to whether or not the managed ID 72 needs to be registered in the server 11 .

[0039] On the other hand, when the printer 17 obtains from the server 11 a search result indicating that the printer is not registered (S13: YES), the printer 17 judges whether the managed ID 72 is stored in the printer storage unit 69, i.e., whether the printer 17 already has the managed ID 72 (S21). If the managed ID 72 is not stored in the printer storage unit 69 (S21: NO), the printer 17 generates the managed ID 72 and stores it in the printer storage unit 69 (S23). There is no particular limitation on the method of generating the managed ID 72, but the printer 17 may, for example, combine the printer ID (such as a serial number) of the printer itself with a predetermined character string or the like to generate a managed ID 72 that does not overlap with the managed IDs 72 of other printers 17, that is, a unique managed ID 72. In addition, if there is a possibility that serial numbers overlap between vendors, the printer 17 may add a different character string to the managed ID 72 for each vendor. The printer 17 may not generate the managed ID 72, but may instead accept it from the user.

[0040] When the printer 17 executes S23, it registers the generated managed ID 72 in the server 11 (S25). The printer 17 notifies the server 11 of its own printer ID and the managed ID 72 generated in S23 via the network 19 (S25). When the printer 17 executes S25, it ends the process shown in FIG. 5. As shown in FIG. 4, when the server 11 receives the notification of S25, it associates the obtained printer ID and managed ID 72 and registers them in the management DB 28 (S29). When the registration is complete, the server 11 responds with a completion notification to the printer 17 (S31). This completes the registration of the managed ID 72 in the server 11.

[0041] Furthermore, if the managed ID 72 is stored in the printer storage unit 69 in S21 (S21: YES), the printer 17 notifies the server 11 of the already stored managed ID 72 and the printer ID and registers them (S25). For example, if the server 11 to which the managed ID 72 is registered is changed to another server 11 by the administrator after the managed ID 72 is once registered in the server 11, the managed ID 72 is stored in the printer 17, but the managed ID 72 is not registered in the management DB 28 of the new server 11 after the change. In such a case, the printer 17 makes an affirmative determination in S21 (S21: YES) and registers the managed ID 72 that it already possesses (registered in the server 11 before the change) in the new server 11. This makes it possible to migrate the server 11 to which the managed ID 72 is registered.

[0042] (Alternative ID Memory Processing) The method of storing the managed ID 72 shown in Fig. 5 above is just one example. Fig. 6 shows another example of ID storage processing by the printer 17. In the processing of Fig. 5 above, the printer 17 generates the managed ID 72. In contrast, in the processing of Fig. 6, the server 11 notifies the printer 17 of the managed ID 72. In the following explanation, the same reference numerals are used for the contents similar to those in Fig. 5, and the explanation thereof will be omitted as appropriate.

[0043] If the managed ID is not registered in the server 11 (S13: YES), the printer 17 executes a registration process with the server 11 (S33). The printer 17 notifies the server 11, for example, that it wants the printer ID to be registered in the management DB 28. When the server 11 receives the notification from the printer 17, it sets a managed ID 72 for the printer 17 that sent the notification, and stores the set managed ID 72 in the management DB 28 in association with the printer ID. In this case, the server 11 may, for example, generate a managed ID 72 that is different from a managed ID 72 that has already been registered (in use) in the management DB 28, and set a unique managed ID 72. Alternatively, the administrator may operate the management PC 13 or the server 11 to set the managed ID 72 in the management DB 28.

[0044] The server 11 responds with the set managed ID 72 to the printer 17. After executing S33, the printer 17 acquires the managed ID 72 from the server 11, stores the acquired managed ID 72 in the printer storage unit 69 (S35), and ends the process shown in Fig. 6. This allows the managed ID 72 notified from the server 11 to be stored in the printer 17.

[0045] (Application 50 startup process) Next, the startup process performed by the terminal device 15 executing the application 50 will be described with reference to FIG. 7. For example, when the terminal device 15 receives an operation input to execute the application 50 via the touch panel 45, the terminal device 15 starts the process shown in FIG. 7. Note that in the following description of FIGS. 7 and 9, the application 50 will be described as the main subject. For example, the description "the application 50 determines whether the managed ID 51 has been stored" means that "the terminal device 15 executing the application 50 determines whether the managed ID 51 has been registered based on the control of the application 50."

[0046] First, in S37 of Fig. 7, the application 50 judges whether or not the managed ID 51 has been stored. If the managed ID 51 is stored in the terminal storage unit 47, the application 50 makes an affirmative judgment in S37 (S37: YES) and executes processing to start the application 50 (S39). The application 50 ends the processing shown in Fig. 7. After starting up, the application 50 executes processing to accept a print instruction based on an operation of the touch panel 45, processing to change settings for the printer 17, and the like. If the application 50 accepts a print instruction, it executes the print processing of Fig. 9, which will be described later, and uses the managed ID 51 stored in the terminal storage unit 47 at that time.

[0047] Furthermore, if the managed ID 51 is not stored in the terminal storage unit 47 (S37: NO), the application 50 displays an input screen for inputting the managed ID 51 on the touch panel 45 (S41). The application 50 displays, for example, a message such as "Please enter the managed ID to be used for the printer 17" and an input field for the managed ID 51 on the touch panel 45. The user operating the terminal device 15 operates the touch panel 45 to input the managed ID 51 on the input screen. The user operating the terminal device 15 may be the user of the terminal device 15 or the printer 17, or may be an administrator.

[0048] For example, the administrator sets the printer 17 and the terminal device 15 to be used for each employee of the company. The administrator turns on the printer 17 and performs the task of registering the managed ID 72 in the server 11. As described above, when the printer 17 is turned on, the managed ID 72 generated by the printer 17 is registered in the management DB 28 of the server 11 (S25 in FIG. 5). The administrator also operates the management PC 13 to select the printer 17 (printer ID) and managed ID 72 to be used by each employee, and registers the application ID of the application 50 to be installed in the terminal device 15 used by the employee in the management DB 28. This associates the printer ID, the managed ID 72, and the application ID. The administrator lends the printer 17 and the terminal device 15 to the employee, and tells the employee the managed ID 51 to be registered in the terminal device 15, i.e., the managed ID 72 associated in the management DB 28 with the printer ID of the printer 17 to be lent. When the employee operates the loaned terminal device 15 to execute the application 50, he or she inputs the managed ID 51, which has been given to the employee by the administrator, on the above-mentioned input screen (S41 in FIG. 7).

[0049] After executing S41, the application 50 determines whether or not a managed ID 51 has been entered on the input screen displayed in S41 (S43), and if entered (S43: YES), stores the entered managed ID 51 in the terminal storage unit 47 (S45). As a result, after being started in S39, the application 50 can use the managed ID 51 stored in S45 to send a print instruction to the loaned printer 17, i.e., the printer 17 having a managed ID 72 that matches the managed ID 51.

[0050] Furthermore, in S43, if the managed ID 51 is not input (S43: NO), the application 50 stops the start-up process (S47) and ends the process shown in Fig. 7. For example, if the input screen is displayed and the managed ID 51 is not input for a certain period of time, or if an input cancel operation is performed, the application 50 makes a negative determination in S43 (S43: NO). In this case, the application 50 is not started.

[0051] The method of storing the managed ID 51 in the terminal storage unit 47 is not limited to the above-mentioned method of input by the user. For example, the managed ID 51 may be stored when the server 11 uses the MAM function of the server 11 to instruct the terminal device 15 to install the application 50. When the administrator operates the management PC 13 and uses the MAM function of the server 11 to install the application 50 in the terminal device 15, the administrator may store the managed ID 72 of the printer 17 used by the user of the terminal device 15 as the managed ID 51 in the terminal storage unit 47. In this way, the administrator can store the application 50 and the managed ID 72 of the printer 17 used by the employee in advance in the terminal device 15 used by each employee in association with each other.

[0052] In the above example, the case where there is one printer 17 has been described, but the application 50 can be implemented in the same way when there are multiple printers 17. For example, when multiple printers 17 are registered and a print instruction is received, the application 50 may receive the selection of the printer 17 to send the print instruction. In this case, when no managed ID 51 is stored, the application 50 may make a negative determination in S37 (S37: NO) and receive the selection of the printer 17 or the input of the managed ID 51 (S41). Also, when at least one managed ID 51 is stored, the application 50 may make a positive determination in S37 (S37: YES) and start up (S39). After the start up, when a printer 17 with no registered managed ID 51 is selected, the application 50 may receive the managed ID 51 to be used. Alternatively, the administrator may use the MAM function to control the terminal device 15 to store the managed ID 51 of each printer 17 used by the terminal device 15.

[0053] (Printing process) Next, the printing process executed by the above-mentioned printing system 10 will be described with reference to Fig. 8 to Fig. 10. Fig. 8 shows the processing of the terminal device 15 and the printer 17 in the printing process. By executing the printing process, the printing system 10 executes printing by the printer 17 based on a print instruction sent from the terminal device 15 to the printer 17.

[0054] Fig. 9 shows the print processing executed by the terminal device 15. The terminal device 15 executes, for example, S39 in Fig. 7 to start the application 50, and then accepts a print instruction in the application 50. The application 50 displays, on the touch panel 45, a reception screen for accepting print settings and a print execution instruction, for example, based on a predetermined operational input to the touch panel 45. After displaying the reception screen, the application 50 executes S51 in Fig. 9 to determine whether or not a print instruction has been accepted.

[0055] For example, when the application 50 receives an operation to execute printing on the reception screen, it makes a positive determination in S51 (S51: YES) and executes S53. On the other hand, when the application 50 receives an operation to cancel printing on the reception screen (S51: NO), it ends the process shown in Fig. 9. In this case, a print instruction is not sent. When the application 50 displays the print reception screen again, it starts the process shown in Fig. 9.

[0056] In S53, the application 50 generates a print job. The application 50 generates a print job based on the print settings (paper size, number of copies, monochrome or color settings, etc.) accepted on the acceptance screen. After executing S53, the application 50 assigns a managed ID 51 to the generated print job (S55). The print job includes image data described in a page description language, for example. The application 50 sets information on the managed ID 51 at a specific byte position in the image data included in the print job, for example, at a header position of the image data that is predefined. The application 50 may set the managed ID 51 at a position other than the header (such as the end of the image data), or may set the managed ID 51 in the image data so that the managed ID 51 can be detected by executing a predetermined calculation or image processing on the image data.

[0057] After the application 50 assigns the managed ID 51 to the print job in S55, it transmits a print instruction to the printer 17 to execute printing of the print job (S57), and ends the process of FIG. 9. As a result, the print instruction with the managed ID 51 assigned thereto can be transmitted to the printer 17, and the printer 17 can print. Note that the method of transmitting the managed ID 51 in a print instruction from the terminal device 15 to the printer 17 (one example of a screen formation instruction of the present application) is not limited to the method of setting the managed ID 51 in the image data described above. For example, the application 50 may set the managed ID 51 as one of the print parameters to be set in the print job. The application 50 may also transmit the managed ID 51 as data separate from the print job. In a communication session between the terminal device 15 that transmits the print instruction and the printer 17, the application 50 may transmit the managed ID 51 to the printer 17 in data (separate packet, etc.) separate from the print job. That is, the managed ID 51 may be included in a separate packet in one communication session that transmits the print instruction and transmitted. Therefore, in the present application, transmitting an image formation instruction including the second identification information is a concept that includes a process of transmitting the managed ID 51 in a separate packet during a communication session of the print instruction.

[0058] Next, the print processing executed by the printer 17 will be described with reference to FIG. 10. The printer 17 starts the processing shown in FIG. 10 after, for example, executing the ID storage processing shown in FIG. 5. First, the printer 17 judges whether or not a print instruction has been acquired from the terminal device 15 (S61). If the printer 17 has not acquired a print instruction (S61: NO), the printer 17 ends the processing shown in FIG. 10. After terminating the processing, the printer 17 executes the processing from S61 again. Thus, the printer 17 repeatedly executes the processing shown in FIG. 10 during startup and judges whether or not a print instruction has been acquired.

[0059] When the printer 17 receives a print instruction from the terminal device 15 (S61: YES), it judges whether the managed ID 72 is stored in the printer storage unit 69, that is, whether the printer 17 has the managed ID 72 (S63). When the managed ID 72 is not stored in the printer storage unit 69 (S63: NO), the printer 17 executes printing of the image data included in the acquired print job (S65). In this case, the printer 17 prints the image data of the acquired print job without executing the print availability judgment using the managed ID 72 in S67 and thereafter described later. For example, when the managed ID 51 is set in the header of the image data, the printer 17 deletes the information of the managed ID 51 and then prints the image data. When the printer 17 completes printing, it notifies the terminal device 15, which is the sender of the print instruction, of a print completion notification (S66 in FIG. 8). After completing the process shown in FIG. 10, the printer 17 executes the process from S61 again.

[0060] For example, as described above, when the process of Fig. 5 is executed, if the printer 17 cannot communicate with the server 11 due to a network failure or the network settings of the second communication IF 62 not being set, and the process of registering the managed ID 72 to the server 11 cannot be executed (S13: NO in Fig. 5), or if the printer 17 is set not to execute a print availability determination using the managed ID 72 (S13: NO), the printer 17 starts up without storing the managed ID 72 in the printer storage unit 69. After that, when the printer 17 acquires a print instruction in S61 in Fig. 10 (S61: YES), it makes a negative determination in S63 (S63: NO) and executes printing (S65). As a result, even if a network failure occurs or the network settings of the second communication IF 62 are not set, the printer 17 can be made to execute printing by sending a print instruction from the terminal device 15. If the printer 17 judges negative in S63 (S63: NO), it may notify the terminal device 15 of an error or the like without executing printing. The printer 17 may notify the terminal device 15 that printing is not possible because the managed ID 72 is not registered, or may notify the terminal device 15 through the user IF 65 of the printer 17.

[0061] If the managed ID 72 is stored in the printer storage unit 69 in S63 (S63: YES), the printer 17 compares the managed ID 51 acquired in the print instruction with the managed ID 72 possessed by the printer itself stored in the printer storage unit 69 (S67). The printer 17 acquires the managed ID 51 from the header of the image data, and determines whether the two managed IDs 51, 72 match (S69). If the two managed IDs 51, 72 match, for example, if the values ​​indicated by the two managed IDs 51, 72 completely match (S69: YES), the printer 17 executes S71, and if they do not match (S69: NO), the printer 17 executes S73.

[0062] In S73, the printer 17 sets the mode flag 76 to a value indicating ON. This causes the printer 17 to transition to lost mode. After transitioning to lost mode, the printer 17 also performs processing to lock the user IF 65. In the locked state, the printer 17 prohibits operations of the user IF 65 other than turning the power on and off until, for example, preset authentication information (such as a PIN number) is entered. Furthermore, the printer 17 does not execute printing based on the acquired print job, and therefore notifies the terminal device 15 that is the sender of the print instruction of an error (S73). Note that the printer 17 does not have to notify the sender of the error.

[0063] Here, if the printer 17 is lost while on a business trip or the like, the printer 17 may be used by a finder. The finder may send a print instruction to the printer 17, for example, by operating the terminal device 15 on which the application 50 is installed. In such a case, if the printer 17 has the managed ID 72, the printer 17 will not execute printing if the managed ID 51 of the print instruction does not match the managed ID 72 of the printer 17 (S69: NO). This makes it possible to prevent unauthorized use of the printer 17.

[0064] Furthermore, if the lost printer 17 is left in normal mode, it may be used by a finder or the like. Therefore, when the printer 17 acquires a print instruction for a managed ID 51 that does not match the managed ID 72, the printer 17 switches to lost mode to restrict functions. Therefore, the lost mode is, for example, a mode that restricts functions to prevent unauthorized use of the printer 17 by a finder or the like. When the printer 17 switches to lost mode, for example, it switches to a state in which input of operations via the user IF 65 is restricted. In the lost mode, the printer 17 permits operations of the user IF 65 for turning the power on / off and operations of the user IF 65 for enabling or disabling the communication functions of the first communication IF 61 and the second communication IF 62, but restricts other operations of the user IF 65. The operations of the other user IF 65 here include, for example, a test printing operation, a printing operation of the template data 74, an operation for changing the IP address of the first communication IF 61, an operation for changing the access destination (URL, etc.) of the registered server 11, and the like.

[0065] By permitting the operation to enable or disable the communication function, for example, when the user loses the printer 17 and then returns it, the user can unlock the user IF 65 of the printer 17 in lost mode and enable the communication functions such as short-range wireless communication of the second communication IF 62. As will be described later, when the printer 17 acquires a print instruction with a matching managed ID 51, 72, the printer 17 cancels the lost mode. Therefore, if the user can perform the operation to enable the communication functions such as the second communication IF 62 in lost mode, the user can cancel the lost mode by sending a print instruction from the terminal device 15 to the printer 17 via short-range wireless communication or Wi-Fi Direct (registered trademark) wireless communication.

[0066] Furthermore, if the operation of the user IF 65 that changes the IP address of the first communication IF 61 is prohibited, it is possible to prevent the IP address from being changed between the time of loss and the time of return to the user. As a result, when the printer 17 is returned to the user, the user can connect the printer 17 to the network 19, etc., and send a print instruction from the terminal device 15 to the printer 17. Furthermore, if the change of the access destination of the registered server 11 is prohibited, for example, when the printer 17 is turned on and the server 11 is accessed, the server 11 side can detect that the printer 17 has been turned on. Therefore, in the lost mode, the printer 17 allows communication between the printer 17 and the server 11 while restricting the operation of the user IF 65, and restricts the change of the server 11 to be accessed. Note that the method of restricting the change of the server 11 to be accessed is not limited to the method of restricting the operation of the user IF 65. For example, in the lost mode, the printer 17 may allow the operation of the user IF 65 while prohibiting the change of the communication setting of the printer 17 (setting of IP address) and the setting of the server 11 to be accessed (URL, IP address, etc.).

[0067] In addition, in the lost mode, the printer 17 restricts the operation of the user IF 65 for printing the template data 74 and the personal information 75. This makes it possible to prevent the personal information 75 and the like stored in the printer 17 from being viewed by a third party. In addition, the printer 17 executes control so that the template data 74 and the personal information 75 cannot be viewed by the user even by a method other than printing. For example, in the lost mode, when the printer 17 receives a print instruction from the terminal device 15 to form a preview image of the template data 74 and the personal information 75, the printer 17 does not execute the process of forming the preview image or responding to the terminal device 15 with the formed preview image. In the lost mode, when the printer 17 receives an operation to display the information of the template data 74 and the personal information 75 on the user IF 65, the printer 17 does not display the information. The preview image here is, for example, an image that allows the user to check in advance the print state when printed on a sheet. In the lost mode, the printer 17 may execute the image formation and display of a part of the preview image (such as only the template data 74). Printer 17 may also perform preview image generation and response in lost mode.

[0068] The above-described control contents in the lost mode are merely examples. For example, the printer 17 may prohibit the first communication IF 61 from performing short-distance wireless communication in the lost mode. Alternatively, the printer 17 may turn off the display of the user IF 65 in the lost mode.

[0069] When the printer 17 shifts to the lost mode in S73 of FIG. 10, it prints the contact information 73 in the printer storage unit 69 (S75). The printer 17 executes printing of the contact information 73 previously set in the printer 17 (S75), and ends the process shown in FIG. 10. This allows the contact information (address, telephone number, etc.) of the owner of the printer 17 to be printed and provided to the person who finds the printer 17 at the location where the printer 17 was lost. This can encourage the finder to contact the owner, and can increase the probability that the lost printer 17 will be returned. Note that the method of notifying the contact information 73 is not limited to printing. The printer 17 may display the contact information 73 on the user IF 65. Alternatively, the printer 17 may notify the contact information 73 to the terminal device 15 whose managed IDs 51 and 72 do not match.

[0070] On the other hand, if the managed IDs 51, 72 match (S69: YES), the printer 17 sets the mode flag 76 to a value indicating OFF (S71). As a result, if the lost mode was OFF and the printer 17 was in normal mode before S71 was executed, the printer 17 maintains the normal mode, and if the printer was in lost mode before S71 was executed, the printer 17 transitions to normal mode. In other words, if the printer 17 receives a print instruction with a matching managed ID 51, 72 (S69: YES), the printer 17 cancels lost mode.

[0071] Furthermore, in S71, if the user IF 65 is in a locked state, the printer 17 unlocks it. This allows the user IF 65 to be used without requiring authentication or the like. Note that the printer 17 does not need to lock the user IF 65 in S73. In this case, the printer 17 does not need to execute the process of unlocking the user IF 65 in S71.

[0072] After executing S71, the printer 17 executes printing of the image data included in the print job acquired from the terminal device 15 (S65). The printer 17 prints the image data by deleting the managed ID 51 included in the image data. This allows only the terminal device 15 having the managed ID 51 that matches the managed ID 72, i.e., the authorized user, to cause the printer 17 to execute printing. When printing is completed, the printer 17 notifies the terminal device 15 that is the sender of the print instruction of a print completion notification (S66 in FIG. 8). As described above, the printer 17 determines whether or not to execute printing based on the print instruction based on the determination result of S69. For this reason, it can be said that the printer 17 determines whether or not to permit printing based on the print instruction by determining whether or not the managed IDs 51 and 72 match in S69.

[0073] In S67 and S69, the printer 17 judges whether the managed IDs 51 and 72 are completely identical. However, the method of judging whether to switch to lost mode or execute printing based on the managed IDs 51 and 72 is not limited to the method of judging whether the managed IDs 51 and 72 are identical. For example, the printer 17 may make a positive judgment in S69 if the managed IDs 51 and 72 are not completely identical, but the value of the managed ID 72 is set as part of the management ID 51. Alternatively, the printer 17 may calculate a hash value of the identification information sent from the terminal device 15, and make a positive judgment in S69 if the calculated hash value matches the hash value stored in the printer 17. The identification information sent from the terminal device 15 to the printer 17 may be encrypted information. The printer 17 may make a positive judgment in S69 if it successfully decrypts the identification information acquired from the terminal device 15 with a decryption key stored in the printer 17.

[0074] In addition, in the above-mentioned print instruction, when the terminal device 15 can send a print instruction to a plurality of printers 17, the terminal device 15 may store the printer ID of each printer 17 in association with the managed ID 51 that matches the managed ID 72 stored in the printer 17, and may use different managed IDs 51 when sending a print instruction. FIG. 11 shows a state in which a single terminal device 15 uses a plurality of printers 17. For example, the terminal storage unit 47 of the terminal device 15 stores the printer IDs of the plurality of printers 17 in association with the managed ID 51 that matches the managed ID 72 stored in the printer 17. This associated data may be data stored in association with the managed ID 51 input by the user of the terminal device 15 and the printer 17 selected at that time, as shown in FIG. 7. For example, every time the user sets up a new printer 17 (communication settings, etc.), the user may input the managed ID 72 of the printer 17 on the input screen and store the managed ID 51 in association with the printer ID. Alternatively, the server 11 may use the MAM function to store data associating multiple printer IDs with the managed IDs 51 in the terminal storage unit 47 when the application 50 is installed, for example.

[0075] The terminal device 15 may accept the selection of the printer 17 to which the print instruction is to be sent on the reception screen for accepting the print settings described in S51 of FIG. 9, for example. Then, when the terminal device 15 accepts the print instruction from the user (S51: YES), the terminal device 15 assigns the managed ID 51 associated with the printer ID of the selected printer 17 to the print job (S55) and sends it to the printer 17 (S57). The example of FIG. 11 shows a state in which the printer 17 with the printer ID 3 is selected, and the terminal device 15 sends the managed ID 3 associated with the printer ID 3 in the print instruction. As a result, even if there are multiple printers 17, the managed ID 51 corresponding to each printer 17, that is, the managed ID 72 stored in the printer 17, can be sent to execute printing.

[0076] (Printer 17 startup process) Next, the startup process executed by the printer 17 will be described with reference to Fig. 12. The printer 17 determines whether or not the power has been turned on, for example, in S81 of Fig. 12. For example, when the power button of the user IF 65 is not operated and the printer 17 is not turned on (S81: NO), the printer 17 executes the process of S81 and enters a state of waiting for the power to be turned on. When the power button of the user IF 65 is operated and the printer 17 is turned on (S81: YES), the printer 17 executes the printer program 71 in the printer CPU 70 and starts up the system of the printer 17 (S83).

[0077] When the printer 17 starts up the system, it determines whether the mode flag 76 is a value indicating ON (S85). If the mode flag 76 is a value indicating OFF (S85: NO), that is, if the printer 17 is in the normal mode, it ends the process of Fig. 12. In this case, the printer 17 starts up in the normal mode in which functions are not restricted.

[0078] On the other hand, if the mode flag 76 is a value indicating ON (S85: YES), the printer 17 locks the user IF 65 (S86) in the same manner as S73 in FIG. 10. As a result, the printer 17 is in a state in which an authentication number or the like must be input in order to operate the user IF 65 after startup. The printer 17 executes printing of the contact information 73 (S87) and ends the process shown in FIG. 12. In this case, the printer 17 starts up in a lost mode that limits functions. As a result, while the printer 17 is in the lost mode, the printer 17 executes printing of the contact information 73 every time the printer is turned on. This makes it possible to more reliably notify the finder or the like of the contact and return the printer 17 early. Note that if the printer 17 is in the lost mode when the printer is turned on, the printer 17 does not need to execute locking of the user IF 65 in S86. Also, the printer 17 does not need to execute printing of the contact information 73 in S87. Furthermore, if the printer 17 is in lost mode when the printer 17 is turned on, the printer 17 may display the contact information 73 on the user IF 65, or may turn on a lamp or sound a buzzer.

[0079] Incidentally, the server 11 is an example of a management server. The terminal device 15 is an example of an information processing device. The printer 17 is an example of a portable image forming device. The terminal storage unit 47 is an example of a storage unit. The terminal CPU 48 is an example of a computer. The application 50 is an example of a program. The managed ID 51 is an example of second identification information. The first communication IF 43, the second communication IF 44, the first communication IF 61, and the second communication IF 62 are examples of communication interfaces. The printing unit 64 is an example of an image forming unit. The printer control unit 67 is an example of a control unit. The printer storage unit 69 is an example of a storage unit. The managed ID 72 is an example of first identification information. The personal information 75 is an example of user information. S51 is an example of an acquisition process. S69 is an example of a judgment process. S65 is an example of an image forming process. S73 and S75 are examples of a restriction process. S57 is an example of a transmission process. Step S37 is an example of a determination process, and step S41 is an example of a reception process.

[0080] (Effects) According to the above-described embodiment, the following effects are obtained. (1) In this embodiment, the printer 17, with the managed ID 72 stored in the printer storage unit 69, acquires a print instruction (an example of an image formation instruction) including the managed ID 51 from the terminal device 15 via the first communication IF 61 and the second communication IF 62 (S51). The printer 17 determines whether or not to permit printing (an example of image formation) by the printing unit 64 based on the acquired managed ID 51 and the managed ID 72 in the printer storage unit 69 (S69). If the printer 17 permits printing (S69: YES), the printer 17 prints the image data of the print job by the printing unit 64 (S65). If the printer 17 does not permit printing (S69: NO), the printer 17 does not execute printing of the image data (S73, S75).

[0081] According to this, the printer 17 determines whether or not to permit printing based on the managed ID 72 stored in advance in the printer storage unit 69 before receiving a print instruction and the managed ID 51 received from the terminal device 15. Therefore, only those who know the managed ID 72 stored in the printer 17, i.e., only authorized users, can cause the printer 17 to normally execute printing. Furthermore, even if a print instruction is received from an unauthorized user due to loss or the like, execution of printing can be restricted. This can prevent the use of consumables of the printer 17, deterioration of parts, and leakage of template data 74 and personal information 75 stored in the printer 17.

[0082] (2) In S69, the printer 17 permits printing in S65 if the values ​​indicated by the two managed IDs 51, 72 are completely identical (S69: YES). This allows printing to be permitted only when the managed IDs 51, 72 match, and makes it possible to prevent use by unauthorized users (such as finders) whose managed IDs 51, 72 do not match.

[0083] (3) Each time a new print instruction is acquired (S61: YES), the printer 17 executes the judgment process of S69 based on the managed ID 51 acquired in the new print instruction. According to this, each time a print instruction is acquired, judgment is executed based on the managed ID 51 of the newly acquired print instruction. For example, if the managed IDs 51 and 72 match and the acquired print instruction is printed without checking the managed IDs 51 and 72 for a certain period of time, there is a possibility that the printer 17 may also print a print instruction from a terminal device 15 that does not have the managed ID 51. If the printer 17 judges whether the managed IDs 51 and 72 match each time a new print instruction is acquired, as in this embodiment, the occurrence of unauthorized use of the printer 17 can be more reliably suppressed.

[0084] (4) Printer storage unit 69 stores template data 74 and personal information 75 that can be added to template data 74. Printer 17 is able to execute printing using template data 74 and personal information 75 when printing based on image data. This makes it possible to prevent personal information 75 and the like from leaking by restricting printing based on the determination results of managed IDs 51, 72. Therefore, in printer 17 which stores such template data 74 and personal information 75, it is extremely effective to restrict printing based on managed IDs 51, 72.

[0085] (5) If the printer 17 determines that printing is not permitted (S69: NO), it transitions to lost mode (an example of a functional restriction mode) in which the functions of the printer 17 are restricted. With this, for example, after the printer 17 is lost, if the printer receives a print instruction from a terminal device 15 whose managed IDs 51, 72 do not match, the printer can transition to lost mode in which not only the print instruction is not executed but also functions are restricted. In lost mode, the printer 17 prohibits operations on the user IF 65 other than, for example, turning the power on and off. This makes it possible to suppress changes to the IP address of the printer 17 and changes to information on the access destination of the registered server 11.

[0086] (6) In the lost mode, the printer 17 prints the contact information 73 (S75, S87). This allows the finder or the like to confirm the contact information by printing the contact information 73, thereby increasing the probability that the printer 17 will be returned. In the lost mode, the printer 17 also permits the operation of the user IF 65 that activates communication (communication functions such as Bluetooth (registered trademark) and Wi-Fi Direct (registered trademark)) of the first communication IF 61 or the like. This allows the user to activate communication functions such as Bluetooth (registered trademark) by operating the user IF 65 when the lost printer 17 is returned to the user. The user can cancel the lost mode by sending a print instruction from the terminal device 15, and use the printer in normal mode. In the lost mode, the printer 17 also permits the operation of the user IF 65 that turns on the power. This allows the user to turn on the power and perform operations such as canceling the lost mode using the user IF 65, even if the returned printer 17 is in the lost mode. In the lost mode, the printer 17 also restricts operations of the user IF 65 other than the above operations. According to this, by restricting the operation of the user IF 65, it is possible to prohibit printing of template data 74 and personal information 75, display of preview images, changing of setting information of the printer 17, and the like.

[0087] (7) After the printer 17 goes into lost mode, it is powered off, and then maintains the lost mode even after it is turned on (FIG. 12). As a result, even if a finder turns the printer 17 on and off, the lost mode is maintained, preventing information leakage and consumption of expendables (parts).

[0088] (8) After switching to lost mode, when the printer 17 receives a new print instruction, if the managed IDs 51, 72 match and printing is permitted (S69: YES), the printer 17 cancels lost mode (S71). In this way, when the printer 17 in lost mode is returned, a regular user such as an employee can cancel lost mode of the printer 17 by sending a print instruction from the terminal device 15, and use the printer 17 in normal mode. No special operation is required to cancel lost mode.

[0089] (9) The server 11 manages the managed ID 72 of each of the multiple printers 17 in the management DB 28 (FIG. 3). In lost mode, the printer 17 allows communication between itself and the server 11, but restricts operation of the user IF 65, thereby restricting changes to the access destination for accessing the server 11. Since the access destination of the registered server 11 is not changed, for example, when the printer 17 is turned on and the server 11 is accessed, the server 11 can detect that the printer 17 has been turned on.

[0090] (10) Furthermore, when printer 17 is in lost mode and receives a print instruction from terminal device 15 to form a preview image using template data 74 and personal information 75, printer 17 does not form the preview image. This not only restricts printing, but also restricts the formation of a preview image using template data 74 and personal information 75. This makes it possible to prevent personal information 75 and the like stored in printer 17 from being viewed by a third party, such as a finder.

[0091] (11) In the embodiment shown in FIG. 5, the printer 17 generates a managed ID 72 and registers it in the server 11 (S23, S25). This allows the printer 17 to generate and register the managed ID 72 at the printer's own timing (such as when a certain condition is met). Also, the server 11 does not need to generate the managed ID 72, and the processing load of the server 11 can be reduced. Also, in another embodiment shown in FIG. 6, the printer 17 stores the managed ID 72 acquired from the server 11 in the printer storage unit 69 of the printer's own device (S35). This allows the printer 17 to store and use the managed ID 72 acquired from the server 11. This allows the printer 17 to generate the managed ID 72, and the processing load of the printer 17 can be reduced. Also, the server 11 can manage the managed ID 72 in use.

[0092] (12) The server 11 is a server with an MDM function, and is capable of restricting functions and erasing data in each of the managed terminal devices 15. As a result, the server 11, which restricts functions and erases data of the terminal device 15 in response to loss, etc., can manage the managed ID 72 of the printer 17 used together with the terminal device 15.

[0093] (13) The application 50 transmits a print instruction including the managed ID 51 and image data to the printer 17 via the first communication IF 43 or the second communication IF 44 (S57). By transmitting the print instruction, the application 50 causes the printer 17 to determine whether or not to permit printing based on the transmitted managed ID 51 and the managed ID 72 stored in the printer 17 (FIG. 10). This allows the printer 17 to determine whether or not to permit printing based on the managed ID 72 previously stored in the printer storage unit 69 before receiving the print instruction and the managed ID 51 acquired from the terminal device 15. Only those who know the managed ID 72 stored in the printer 17, i.e., only authorized users, can cause the printer 17 to normally execute printing.

[0094] (14) The application 50 determines whether or not the managed ID 51 is stored in the terminal storage unit 47 (S37), and if the managed ID 51 is not stored in the terminal storage unit 47 (S37: NO), the application 50 accepts the managed ID 51 from the user of the terminal device 15 (S41). This allows the user to store and set in the terminal device 15 the managed ID 51 that matches the managed ID 72 of the printer 17 to be used. The user can set the managed ID 51 according to the actual use.

[0095] (15) The server 11 manages the printer ID (an example of image forming device identification information) for identifying the printer 17 and the managed ID 72 of the printer 17 indicated by the printer ID in the management DB 28 in association with each other. For example, the server 11 controls the terminal device 15 to install the application 50 in the terminal device 15 by using the MAM function, and stores the managed ID 72 stored in the printer 17 that transmits the print instruction as the managed ID 51 in the terminal storage unit 47 when installing the application 50. According to this, when the administrator installs the application 50 in the terminal device 15 used by each user such as an employee, the administrator can set the managed ID 72 of the printer 17 used by the user as the managed ID 51 in the terminal device 15. The user of the terminal device 15 does not need to set the managed ID 51. Also, input errors of the managed ID 51 by the user can be eliminated. Also, the administrator can install the managed IDs 51 of the printers 17 used in each terminal device 15 in a batch in a plurality of terminal devices 15 by operating the management PC 13.

[0096] (16) In the example shown in Fig. 11, multiple managed IDs 51 are stored in the terminal storage unit 47 in association with a printer ID (an example of image forming device identification information). When sending a print instruction, the application 50 sends the managed ID 51 associated with the printer ID indicating the destination printer 17. This makes it possible to send the managed ID 51 corresponding to each of the multiple printers 17 to execute printing. The managed IDs 51 can be switched to use different printers 17.

[0097] (17) In the process of transmitting a print instruction, the application 50 sets the managed ID 51 in a specific byte position (an example of a data position) of the image data included in the print instruction. This allows the managed ID 51 to be included in the image data of the print job and transmitted.

[0098] (Modification) Although the specific examples of the present application have been described in detail above, these are merely examples and do not limit the scope of the claims. The technology described in the claims includes various modifications and variations of the specific examples exemplified above. Modifications of the above embodiment are listed below. For example, the configuration of the printing system 10 described above is one example. For example, the printing system 10 does not need to include the server 11 (MDM server) that manages the terminal device 15. Also, for example, the printer 17 may be configured to include either the first communication IF 61 or the second communication IF 62. Also, the terminal device 15 may be configured to include either the first communication IF 43 or the second communication IF 44. A configuration in which multiple terminal devices 15 can communicate with one printer 17 may be used, or a configuration in which only one terminal device 15 can communicate with one printer 17 may be used. Furthermore, the restriction process for restricting image formation in the present application is not limited to prohibiting printing, and may be, for example, the execution of partial printing based on a print instruction (such as printing only the top page). Additionally, the printer 17 does not need to print the personal information 75 . Furthermore, the user information of the present application is not limited to personal information 75 (such as the user's name), but may include various information related to the user, such as the company name, employee ID, and store name. The printer 17 does not need to be provided with the template data 74 or the personal information 75 . Printer 17 does not need to have a lost mode.

[0099] In the above embodiment, printer 17 cancels lost mode (S71) when it receives a print command with a matching managed ID 51, 72 (S69: YES), but it does not have to be cancelled. Printer 17 may be configured to cancel lost mode when a specific command is sent from terminal device 15 or management PC 13, for example. Furthermore, the storage unit that stores each program (server program 27, management program 38, OS program 49, application 50, printer program 71) is not particularly limited and may be a ROM or flash memory of each storage unit. Furthermore, the storage unit that stores each program may be a computer-readable storage medium. In addition to the above examples, recording media such as CD-ROM and DVD-ROM may be used as the computer-readable storage medium.

[0100] Although the terminal device 15 is a smartphone, the present invention is not limited to this, and other terminals such as desktop PCs, notebook PCs, and tablet PCs can be used as the information processing device. Although the printer 17 is used as the portable image forming device of the present application, a label printer, a FAX machine, etc. may also be used. In the case of a FAX machine, a reading unit (scanning unit) that reads an image is an example of an image forming unit of the present application. Also, an instruction to the FAX machine to scan a document is an example of an image forming instruction of the present application. [Explanation of symbols]

[0101] 11 server (management server), 15 terminal device (information processing device), 17 printer (image forming device), 43 first communication IF (communication interface), 44 second communication IF (communication interface), 47 terminal memory unit (memory unit), 48 terminal CPU (computer), 50 application program (program), 51 managed ID (second identification information), 61 first communication IF (communication interface), 62 second communication IF (communication interface), 64 printing unit (image forming unit), 65 user IF, 67 printer control unit (control unit), 69 printer memory unit (memory unit), 72 managed ID (first identification information), 77 personal information (user information).

Claims

1. an image forming unit that forms an image; A storage unit capable of storing first identification information; A communication interface capable of communicating with an information processing device; A user interface; A control unit; An image forming apparatus comprising: The control unit is an acquisition process of acquiring, in a state in which the first identification information is stored in the storage unit, second identification information and an image formation instruction including image data to be formed from the information processing device via the communication interface; a determination process for determining whether or not to permit image formation by the image forming unit based on the second identification information acquired in the acquisition process and the first identification information stored in the storage unit; an image forming process in which, when it is determined that image formation is permitted as a result of the determination process, image formation is performed by the image forming unit based on the image data; a restriction process for restricting image formation based on the image data and shifting the image forming apparatus to a function restriction mode in which functions of the image forming apparatus are restricted when it is determined that image formation is not permitted as a result of the determination process; Run The limited functionality mode is A portable image forming device in a mode that notifies contact information stored in the image forming device, permits operation of the user interface to enable communication through the communication interface, and permits operation of the user interface to turn on the power, while restricting operation of other user interfaces.

2. An image forming unit that forms an image; A storage unit capable of storing first identification information; A communication interface capable of communicating with an information processing device; A user interface; A control unit; An image forming apparatus comprising: The control unit is an acquisition process of acquiring, from the information processing device via the communication interface, second identification information and an image formation instruction including image data to be formed, while the first identification information is stored in the storage unit; a determination process for determining whether or not to permit image formation by the image forming unit based on the second identification information acquired in the acquisition process and the first identification information stored in the storage unit; an image forming process in which, when it is determined that image formation is permitted as a result of the determination process, image formation is performed by the image forming unit based on the image data; a restriction process for restricting image formation based on the image data and shifting the image forming apparatus to a function restriction mode in which functions of the image forming apparatus are restricted when it is determined that image formation is not permitted as a result of the determination process; Run The limited functionality mode is A portable image forming apparatus in a mode in which operations of the user interfaces for enabling communication of the communication interface and for turning on the power are permitted, while operations of the other user interfaces are restricted.

3. An image forming unit that forms an image; A storage unit capable of storing first identification information; A communication interface capable of communicating with an information processing device; A control unit; An image forming apparatus comprising: The control unit is an acquisition process of acquiring, from the information processing device via the communication interface, second identification information and an image formation instruction including image data to be formed, while the first identification information is stored in the storage unit; a determination process for determining whether or not to permit image formation by the image forming unit based on the second identification information acquired in the acquisition process and the first identification information stored in the storage unit; an image forming process in which, when it is determined that image formation is permitted as a result of the determination process, image formation is performed by the image forming unit based on the image data; a restriction process for restricting image formation based on the image data and shifting the image forming apparatus to a function restriction mode in which functions of the image forming apparatus are restricted when it is determined that image formation is not permitted as a result of the determination process; Run The limited functionality mode is A portable image forming apparatus in a mode for notifying contact information stored in the image forming apparatus.

4. The control unit is 4. The portable image forming apparatus according to claim 1, wherein the determination process determines that image formation is permitted when a value indicated by the first identification information and a value indicated by the second identification information match.

5. The control unit is 5. The portable image forming device according to claim 1, further comprising: a first identification information acquisition unit that acquires, when acquiring a new image forming instruction, an image forming instruction acquisition unit that acquires the image forming instruction and an image forming instruction acquisition unit that acquires the image forming instruction.

6. The storage unit is A template and user information that can be added to the template are stored; The control unit is The portable image forming apparatus according to claim 1 , wherein image formation using the template and the user information is executable in the image formation based on the image data in the image forming process.

7. The control unit is 7. The portable image forming device according to claim 1, wherein the image forming device is powered off after the function restriction mode is entered, and the function restriction mode is maintained even after the image forming device is powered on.

8. The control unit is 8. The portable image forming device according to claim 1, wherein, after transitioning to the function restriction mode, when a new image formation instruction is acquired in the acquisition process, the function restriction mode is released based on a determination in the judgment process that image formation by the image forming unit is permitted.

9. The information processing device includes: Can communicate with the management server, The management server includes: managing the first identification information possessed by each of the plurality of image forming apparatuses; The control unit is 9. The portable image forming apparatus according to claim 1, wherein in the function restriction mode, communication between the portable image forming apparatus and the management server is permitted, but a change of an access destination for accessing the management server is restricted.

10. The storage unit is A template and user information that can be added to the template are stored; The control unit is 10. The portable image forming device according to claim 1, wherein in the function limited mode, when the image forming instruction for forming a preview image using the template and the user information is obtained from the information processing device, formation of the preview image is restricted.

11. The image forming apparatus includes: Can communicate with the management server, The management server includes: managing the first identification information held by each of the plurality of image forming apparatuses; The control unit is A portable image forming device according to claim 1 , further comprising: a process for generating the first identification information and registering it in the management server; or a process for storing the first identification information obtained from the management server in the memory unit of the portable image forming device.

12. The management server includes:

12. The portable image forming apparatus according to claim 11, wherein the portable image forming apparatus is a server capable of communicating with the plurality of information processing devices and capable of at least one of restricting the functions of each of the plurality of information processing devices and erasing data of each of the plurality of information processing devices.

Images