Method, and communication system

Abstract

To transfer information about a first printer to a second printer.SOLUTION: A first printer executes: an output step in which specific information about the first printer is output; an input step in which a second printer receives an input of the specific information; and an acquisition step in which the second printer acquires specific destination information showing the first printer within a local network to which the first printer is connected on the basis of the specific information; a setting step in which the second printer sets the specific destination information as destination information showing the second printer within the local area network; and an instruction transmission step in which either the second printer or a server communicable with the first printer transmits an instruction to execute stop processing for stopping communication using the specific destination information to the first printer.SELECTED DRAWING: Figure 3

Description

[Technical field]

[0001] The present specification relates to a method and a communication system for using a first printer and a second printer to be used in place of the first printer. [Background technology]

[0002] Patent Document 1 discloses a technique for transferring flat-rate service information from one printer to another printer in a communication system. For example, in response to a transfer code request from the one printer, a server transmits a transfer code to the one printer. A user inputs the transfer code displayed on the one printer into the other printer. When the other printer transmits the transfer code input by the user to the server, the server associates the flat-rate service information with the ID of the other printer. [Prior art documents] [Patent documents]

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

[0004] This specification discloses a new technique for transferring information about a first printer to a second printer. [Means for solving the problem]

[0005] The technology disclosed in this specification can be realized in the following application examples.

[0006] [Application Example 1] A method executed by using a first printer and a second printer to be used in place of the first printer, comprising: an output step in which the first printer outputs specific information regarding the first printer; an input step of the second printer receiving an input of the specific information; an acquisition step of the second printer acquiring specific destination information indicating the first printer within the local network to which the first printer is connected based on the specific information; a setting step of setting the specific destination information as destination information indicating the second printer within a local area network by the second printer; an instruction transmission step in which either the second printer or a server capable of communicating with the first printer transmits to the first printer an instruction to execute a stop process for stopping communication using the specific destination information; A method for performing.

[0007] According to the above configuration, the second printer acquires specific destination information indicating the first printer in the local network based on the specific information output from the first printer, and sets the specific destination information as destination information indicating the second printer in the local area network. As a result, the second printer can take over the specific destination information. Furthermore, the second printer transmits an instruction to the first printer to execute a stop process for stopping communication using the specific destination information. As a result, it is possible to avoid the inconvenience that the specific destination information becomes destination information indicating both the first printer and the second printer in the local area network, and it becomes possible to execute communication with the second printer in the local area network similar to the communication that was performed with the first printer.

[0008] According to the above configuration, the printer that performs printing based on a print job transmitted from the terminal device can be switched from the first printer to the second printer without making any settings on the terminal device.

[0009] The technology disclosed in this specification can be realized in various forms, such as a communication system, a server, a printer, a computer program for realizing these devices, systems, and methods, a recording medium on which the computer program is recorded, and the like. [Brief description of the drawings]

[0010] [Figure 1] FIG. 1 is a block diagram showing the configuration of a system 1000. [Diagram 2] FIG. 2 is an explanatory diagram of a management database DB and an information database IB. [Diagram 3] FIG. 11 is a first sequence diagram of a takeover-related process according to the embodiment. [Figure 4] FIG. 2 is a second sequence diagram of the takeover-related process according to the embodiment; [Diagram 5] FIG. 11 is a third sequence diagram of the takeover-related process in the embodiment. [Figure 6] FIG. 4 is a diagram showing an example of a notification image NI. [Figure 7] FIG. 11 is a sequence diagram of a takeover-related process according to a modified example. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0011] A. Working Example A1. System 1000 Configuration 1 is a block diagram showing the configuration of a system 1000. The system 1000 includes multifunction peripherals 100A and 100B, a terminal device 200, and a server 300.

[0012] The multifunction device 100A is a device that has a function of consuming ink as a printing material to perform printing, and a function of reading an original document to generate scan data. The multifunction device 100A has a CPU 110 as a controller of the multifunction device 100A, a volatile storage device 120 such as a DRAM, and a non-volatile storage device 130 such as a hard disk or a flash memory. The multifunction device 100A also has a display unit 140 such as a liquid crystal display that displays images, an operation unit 150 such as a button or a touch panel for acquiring operations by a user, a reading mechanism 160, a printing mechanism 170, and a communication interface (IF) 180.

[0013] The communication IF 180 is an interface for connecting to the Internet IT, for example, a wired interface conforming to Ethernet (registered trademark) or a wireless interface conforming to the Wi-Fi standard.

[0014] The CPU 110 is a calculation device (processor) that performs data processing. The volatile storage device 120 provides a buffer area for temporarily storing various intermediate data generated when the CPU 110 performs processing. The non-volatile storage device 130 stores a computer program PGp for controlling the multifunction peripheral 100A, and an information database IB in which various types of service information and setting information, which will be described later, are stored.

[0015] In this embodiment, the computer program PGp is ​​provided by being stored in advance in the non-volatile storage device 130 when the multifunction peripheral 100A is manufactured. Alternatively, the computer program PGp may be provided in a form in which it is downloaded from a server connected via the Internet IT, or in a form recorded on a CD-ROM or the like.

[0016] The CPU 110 executes various processes for controlling the multifunction device 100A by executing the computer program PGp. For example, the multifunction device 100A (CPU 110) controls the print mechanism 170 to print an image. Furthermore, the multifunction device 100A executes the computer program PGp to communicate with the multifunction device 100B and the server 300, and executes, for example, a handover-related process described below.

[0017] The reading mechanism 160, under the control of the CPU 110, optically reads an original using a one-dimensional image sensor, thereby generating scan data representing an image of the original.

[0018] The printing mechanism 170 executes printing under the control of the CPU 110. The printing mechanism 170 of this embodiment is an inkjet printing mechanism that prints an image on a recording medium using a plurality of types of ink, for example, four types of ink: cyan (C), magenta (M), yellow (Y), and black (K). Alternatively, the printing mechanism 170 may be an electrophotographic printing mechanism that prints an image on a recording medium using toner contained in a toner cartridge as a coloring material.

[0019] The multifunction device 100B is a printer to be used in place of the multifunction device 100A when, for example, a malfunction such as a breakdown occurs in the above-mentioned multifunction device 100A. The multifunction device 100B has components 110 to 180 (not shown) similar to those of the multifunction device 100A. A description of the components of the multifunction device 100B will be omitted. In the following, the multifunction device 100A will also be referred to as the "old multifunction device" and the multifunction device 100B will also be referred to as the "new multifunction device."

[0020] The multifunction peripheral 100A is connected to, for example, a local area network LN, and is connected to the Internet IT via the local area network LN. The multifunction peripheral 100B is also not connected to the local area network LN in Fig. 1, but when used in place of the multifunction peripheral 100A, it is connected to the local area network LN, and is connected to the Internet IT via the local area network LN.

[0021] The terminal device 200 is a computer of a user of the multifunction peripherals 100A and 100B, such as a personal computer or a smartphone. The terminal device 200 includes a CPU 210 as a controller of the terminal device 200, a volatile storage device 220 such as a RAM, and a non-volatile storage device 230 such as a hard disk drive or a flash memory. The terminal device 200 also includes a display unit 240 such as a liquid crystal display for displaying images, an operation unit 250 such as a mouse or keyboard for acquiring operations by the user, and a wired or wireless communication IF 280 for connecting to the Internet IT.

[0022] The CPU 210 is a computing device (processor) that performs data processing. The volatile storage device 220 provides a buffer area for temporarily storing various intermediate data generated when the CPU 210 performs processing. The non-volatile storage device 230 stores an application program AP.

[0023] The CPU 210 executes the application program AP to function as a print application for causing a printer (e.g., the multifunction device 100A) to execute printing. For example, the print application transmits a print job to a printer connected to the local area network LN in response to a user's instruction. A port name, which will be described later, is used as destination information indicating the destination of the print job.

[0024] The server 300 is, for example, a computer, such as a cloud server, operated by a business that manufactures and sells the multifunction peripherals 100A and 100B. The server 300 includes a CPU 310 as a controller of the server 300, a volatile storage device 320 such as a DRAM, a non-volatile storage device 330 such as a hard disk or a flash memory, and a wired or wireless communication IF 380 for connecting to the Internet IT. The server 300 is connected to the Internet IT. This allows the server 300 to communicate with each of the multifunction peripherals 100A and 100B via the Internet IT.

[0025] The CPU 310 is a computing device (processor) that performs data processing. The volatile storage device 320 provides a buffer area for temporarily storing various intermediate data generated when the CPU 310 performs processing. The non-volatile storage device 330 stores computer programs PGs and a management database DB.

[0026] The computer programs PGs are provided, for example, in a form of being uploaded by a business operator who operates the server 300. The server 300 (CPU 310) executes the computer programs PGs to cooperate with the multifunction peripherals 100A and 100B and execute a handover-related process, which will be described later.

[0027] The management database DB stores various data (described later) necessary for the takeover-related processing.

[0028] 1, only the multifunction devices 100A and 100B are shown, but the server 300 communicates with a number of printers (multifunction devices and standalone printers) to provide similar services. Below, the processes related to the multifunction devices 100A and 100B are described, but these processes are also executed independently between the multifunction devices and the other printers.

[0029] A2. Management database DB and information database IB The following describes the management database DB stored in the non-volatile storage device 330 of the server 300 and the information database IB stored in the non-volatile storage device 130 of the multifunction peripheral 100A. Fig. 2 is an explanatory diagram of the management database DB and the information database IB.

[0030] In the management database DB in Fig. 2(A), a device ID, a port name, and setting information other than the port name (hereinafter, also referred to as other setting information) are stored in association with a handover keyword. In the example of Fig. 2, the device ID "DID_a" of the multifunction device 100A, the port name "PN_a" of the multifunction device 100A, and other settings "OT_a" are stored in association with the handover keyword "KW_a" assigned to the multifunction device 100A.

[0031] The handover keyword is information generated and used in the handover-related process described later, and is, for example, a string of multiple randomly generated characters. The device ID is identification information for identifying a device (for example, a printer or a multifunction device). The device ID is, for example, a serial number or a MAC address.

[0032] The port name is address information that indicates a device (e.g., the multifunction device 100A) in a local area network. In other words, the port name is identification information different from the device ID, and is identification information that a terminal device (e.g., the terminal device 200) uses to identify a printer (e.g., the multifunction device 100A) in communication between the terminal device and the printer. For example, the terminal device 200 can transmit a print job to a printer having the port name "PN_a" by specifying the port name "PN_a" and transmitting the print job to the local area network LN. In order to correctly specify one communication partner, the port name is set so that it is not duplicated among devices connected to the local area network LN. In this embodiment, the port name "PN_a" of the multifunction device 100A is created based on the MAC address of the multifunction device 100A. For example, a character string obtained by adding a specific character string to the MAC address is used as the port name. The port name is used, for example, when the OS (operating system) of the terminal device is Windows (registered trademark), and is also called a "NetBIOS name".

[0033] The other setting information includes, for example, print setting information related to printing, read setting information related to scanning, and communication setting information related to communication via a network. The print setting information includes, for example, various setting information related to paper, print mode, etc. set by the user. The read setting information includes, for example, various setting information related to the read resolution, save format of scan data, etc. set by the user. The communication setting information includes, for example, various setting information such as the IP address of the device and the user's email address.

[0034] As shown in Fig. 2(B), information database IB of multifunction device 100A stores setting information of multifunction device 100A. As shown in Fig. 2(C), information database IB of multifunction device 100B stores setting information of multifunction device 100B. Hereinafter, information database IB of multifunction device 100A will also be referred to as information database IBa, and information database IB of multifunction device 100B will also be referred to as information database IBb.

[0035] For example, the information database IBa of the multifunction device 100A in Fig. 2(B) stores the device ID "DID_a" of the multifunction device 100A, the port name "PN_a" of the multifunction device 100A, and other settings "OT_a" of the multifunction device 100A. In addition, as described below, when the multifunction device 100A receives a handover keyword from the server 300, the handover keyword is stored in the information database IBa of the multifunction device 100A, but in the example of Fig. 2(B), the above-mentioned handover keyword is not stored in the information database IBa.

[0036] For example, the information database IBb of the multifunction device 100B in Fig. 2(C) stores the device ID "DID_b" of the multifunction device 100B and other setting information "OT_b". The multifunction device 100B is in an initial state at the start of the handover-related processing described below. In the initial state, as shown in Fig. 2(C), for example, the information database IBb stores other setting information "OT_b" indicating the initial settings, and the port name is not stored because it has not been set.

[0037] A3. Handover related process For example, suppose that a user purchases a new multifunction device 100B to replace the multifunction device 100A when the multifunction device 100A currently being used breaks down. In such a case, the user may wish to transfer the setting information of the multifunction device 100A to the multifunction device 100B. For example, when the user uses a print service (e.g., a printing material management service) using the multifunction device 100A, the user may wish to continue using the print service using the multifunction device 100B. In such a case, the setting information related to the print service needs to be transferred to the multifunction device 100B. The following describes a transfer-related process for transferring setting information from the multifunction device 100A to the multifunction device 100B. FIGS. 3 to 5 are sequence diagrams of the transfer-related process.

[0038] In this embodiment, the setting information of the multifunction device 100A is saved in the server 300 before the multifunction device 100A breaks down. For example, a user starts using the multifunction device 100A, configures the multifunction device 100A according to the user's needs, and then inputs a setting save instruction to the multifunction device 100A. The setting save instruction is an instruction to save the setting information of the multifunction device 100A in the server 300. The setting save instruction is input by the user performing a predetermined operation on the operation unit 150 of the multifunction device 100A. It is assumed that the information database IBa of the multifunction device 100A is in the state shown in FIG. 2(B) above when the setting save instruction is input to the multifunction device 100A.

[0039] When a setting save instruction is input, the multifunction peripheral 100A (CPU 110) transmits a setting save request to the server 300 in S10. The setting save request includes information to be saved, i.e., the setting information stored in the information database IBa. In this embodiment, the setting save instruction includes the device ID "DID_a", the port name "PN_a", and other settings "OT_a" (FIG. 2(B)).

[0040] The communication between the multifunction device 100A and the server 300 is executed using, for example, HTTP (Hypertext Transfer Protocol). That is, data sent from the multifunction device 100A to the server 300 is sent as an HTTP request, and data sent from the server 300 to the multifunction device 100A is sent as an HTTP response to the most recently received HTTP request. Alternatively, the communication between the multifunction device 100A and the server 300 may be communication according to another protocol, for example, communication using a constant connection according to XMPP (eXtensible Messaging and Presence Protocol).

[0041] When the server 300 receives the setting save request, in S12, the server 300 generates a handover keyword "KW_a" to be assigned to the multifunction device 100A. For example, the server 300 randomly selects a predetermined number of characters to generate a character string consisting of a predetermined number of characters as the handover keyword.

[0042] In S14, the server 300 stores each piece of information in association with each other. Specifically, the server 300 stores the information to be stored, that is, the handover keyword "KW_a" generated in S12, the device ID "DID_a", the port name "PN_a", and the other settings "OT_a" included in the setting storage instruction received in S10 in association with each other in the management database DB (FIG. 2(A)).

[0043] In S16, the server 300 transmits a setting save completion notification indicating that the setting information has been saved to the multifunction peripheral 100A that sent the setting save instruction. The setting save completion notification includes the handover keyword "KW_a" that has been generated in S12.

[0044] When the multifunction peripheral 100A receives the setting storage completion notification, the multifunction peripheral 100A saves the handover keyword "KW_a" included in the received setting storage completion notification in S18. That is, the multifunction peripheral 100A stores the handover keyword "KW_a" in the information database IB.

[0045] The processes of S10 to S16 may be executed automatically or in response to a user's instruction whenever the setting information is changed in the multifunction device 100A. The processes of S10 to S16 may be executed repeatedly periodically (for example, once a day at a fixed time), or may be executed when the multifunction device 100A transitions from an offline state to an online state.

[0046] It is assumed that a specific type of failure occurs in the multifunction device 100A while the setting information of the multifunction device 100A is stored in the management database DB of the server 300. The specific type of failure is, for example, a failure that requires replacement or repair of the multifunction device 100A, and in some cases, a failure that may require the multifunction device 100A to be replaced by a new one. The specific type of failure includes, for example, a failure that occurs in an important part such as a power supply device (not shown), a printing mechanism 170, or a reading mechanism 160.

[0047] When a specific type of failure occurs, in S20, the multifunction device 100A detects the failure. The failure is detected, for example, based on various signals transmitted from a sensor (not shown) provided for failure detection, the print mechanism 170, and the read mechanism 160.

[0048] When a specific type of failure is detected, in S22, the multifunction device 100A acquires time information indicating the current date and time using a clock function of the multifunction device 100A. In S23, the multifunction device 100A acquires the handover keyword "KW_a" received in S18 from the information database IB.

[0049] In S24, the multifunction device 100A prints a notification image NI including the time information and the handover keyword "KW_a". Specifically, the multifunction device 100A generates print data indicating the notification image NI using the time information already acquired in S22 and the handover keyword "KW_a" already acquired in S23. The multifunction device 100A uses the print data to control the printing mechanism 170 to print the notification image NI on a print medium such as paper. The paper on which the notification image NI is printed is also called a notification paper.

[0050] FIG. 6 is a diagram showing an example of a notification image NI. The notification image NI includes, for example, messages MS1 and MS2, a handover keyword WI, and a date and time TI. The message MS1 in FIG. 6 indicates that a failure has occurred and that the handover keyword is to be notified. The message MS2 in FIG. 6 indicates that the notification form should be scanned by the replacement machine in order to hand over the settings to the replacement machine. The handover keyword WI is, for example, the handover keyword "KW_a" already acquired in S23 described above. The date and time TI is, for example, the date and time indicated by the time information already acquired in S22 described above.

[0051] When the user uses a replacement machine in place of the broken multifunction machine 100A and wishes to transfer the setting information of the multifunction machine 100A to the replacement machine, the user has the replacement machine scan the notification form. When the user uses the replacement machine after repairing the broken multifunction machine 100A or when the user uses the replacement machine but does not want to transfer the setting information of the multifunction machine 100A to the replacement machine, the user does not use the notification form.

[0052] In the following, a case will be described in which the multifunction device 100B is used as a substitute device in place of the broken multifunction device 100A, and the setting information of the multifunction device 100A is taken over to the multifunction device 100B.

[0053] The user sets up the multifunction device 100B purchased as a replacement device so that it can communicate with the server 300. Specifically, the multifunction device 100B is connected to the local area network LN and is made capable of communicating with the server via the local area network LN and the Internet IT. The user then turns on the power of the multifunction device 100B.

[0054] 6 is printed on the multifunction device 100B. Specifically, the notice paper is placed on a platen or an ADF (Automatic Document Feeder) provided in the reading mechanism 160 of the multifunction device 100B so that it can be read by the reading mechanism 160. With the notice paper placed on the multifunction device 100B, the user inputs an instruction to read the notice paper to the multifunction device 100B. The reading instruction is, for example, an instruction to read the notice paper specifically, which is different from a normal reading instruction, and is input by performing a predetermined operation on the operation unit 150.

[0055] When the multifunction device 100B acquires the instruction to read the notice sheet, it reads the notice sheet in S30. Specifically, the multifunction device 100B controls the reading mechanism 160 to cause the reading mechanism 160 to read the notice sheet. As a result, the reading mechanism 160 generates scan data indicative of the notice sheet, in other words, scan data indicative of the notification image NI in FIG. 6.

[0056] In S32, the multifunction device 100B acquires the handover keyword WI (the handover keyword "KW_a") and the date and time TI contained in the notification image NI by analyzing the generated scan data. A known character recognition process is used to analyze the scan data.

[0057] In S34, the multifunction peripheral 100B transmits a handover request requesting setting information associated with the handover keyword to the server 300. The handover request includes the handover keyword "KW_a" acquired in S32 and time information indicating the date and time TI.

[0058] When the server 300 receives the takeover request, in S36 of FIG. 4, the server 300 judges whether the takeover request is within the valid period. The valid period is, for example, a period from the date and time TI when the takeover request is received until a specific time (for example, one to two weeks) has elapsed. Specifically, the server 300 acquires the current date and time (i.e., the date and time when the takeover request is received). The server 300 identifies the valid period based on the date and time TI indicated by the time information included in the takeover request. If the date and time when the takeover request is received is within the identified valid period, the server 300 judges that the takeover request is within the valid period. If the date and time when the takeover request is received is outside the valid period, the server 300 judges that the takeover request is not within the valid period.

[0059] If the takeover request is not within the valid period (S36: NO), the server 300 transmits a takeover impossible notification indicating that the setting information cannot be taken over to the multifunction device 100B in S38. In this case, the takeover-related processing is terminated without taking over the setting information.

[0060] If the takeover request is within the validity period (S36: YES), in S39, the server 300 searches the management database DB (FIG. 2(A)) for the takeover keyword "KW_a" included in the takeover request. In S40, the server 300 obtains information associated with the searched takeover keyword "KW_a" from the management database DB. As shown in FIG. 2(A), the port name "PN_a" and other settings "OT_a" associated with the takeover keyword "KW_a" are obtained from the management database DB.

[0061] In S42, the server 300 transmits the port name "PN_a" and other settings "OT_a" acquired in S40 to the multifunction peripheral 100B.

[0062] When the multifunction peripheral 100B receives the port name "PN_a" and the other settings "OT_a", in S44, it sets the port name "PN_a" received from the server 300 as the port name indicating itself. Specifically, as shown in the dashed frame F1 in Fig. 4, the server 300 stores the port name "PN_a" in its own information database IBb.

[0063] In S46, the multifunction peripheral 100B updates the setting information different from the port name set in itself, i.e., the other setting information. Specifically, as shown in the dashed frame F2 in Fig. 4, the server 300 changes the default other setting information "OT_b" stored in its own information database IBb to the other setting "OT_a" received from the server 300.

[0064] In S48, the multifunction peripheral 100B transmits to the server 300 a setting completion notification indicating that the setting of the port name and other setting information has been completed.

[0065] When the server 300 receives the setting completion notification, in S50, the server 300 updates the device ID in the management database DB. Specifically, as shown in a dashed frame F3 in Fig. 5, the device ID associated with the handover keyword "KW_a" included in the handover request received in S34 in Fig. 3 is changed from the device ID "DID_a" of the multifunction device 100A to the device ID "DID_b" of the multifunction device 100B. That is, the association between the port name "PN_a" and other setting information "OT_a" and the device ID "DID_a" of the multifunction device 100A is released, and the port name "PN_a" and other setting information "OT_a" are associated with the device ID "DID_b" of the multifunction device 100B. As a result, the fact that the device using the port name "PN_a" and other setting information "OT_a" has been changed to the multifunction device 100B (device ID "DID_b") is also recorded in the server 300.

[0066] In S52, the server 300 updates the takeover keyword in the management database DB. Specifically, as shown in a dashed frame F4 in FIG. 5, the takeover keyword "KW_a" associated with the port name "PN_a" and other setting information "OT_a" in the management database DB is changed to a new takeover keyword "KW_b". The new takeover keyword "KW_b" is newly generated in this step. As a result, the takeover keyword "KW_a" already used for takeover is invalidated. Since the takeover keyword "KW_a" has already been printed, for example, there is a possibility that it may be used again by mistake by a user or may be used illegally by a person other than the user. By invalidating the takeover keyword "KW_a" in this step, for example, it is possible to prevent the port name "PN_a" and other setting information "OT_a" from being illegally or erroneously acquired using the takeover keyword "KW_a".

[0067] In S54, the server 300 transmits the new takeover keyword "KW_b" to the multifunction peripheral 100B.

[0068] When the multifunction device 100B receives the handover keyword "KW_b", it saves the handover keyword "KW_b" in S56. That is, the multifunction device 100B stores the handover keyword "KW_b" in its own information database IBb. This allows the multifunction device 100A to print a notification image including the handover keyword "KW_b" when, for example, a specific type of failure occurs in the multifunction device 100B, as executed by the multifunction device 100A in S23 and S24 of FIG. 3. That is, by S50 to S54, preparations are made to hand over the setting information including the port name "PN_a" to the next substitute device when the multifunction device 100B fails.

[0069] In S58, the multifunction device 100B broadcasts a device search signal to the local area network LN. The device search signal is a signal for searching for a device having the port name "PN_a" set for the multifunction device 100B, and includes the port name "PN_a." If the communication function of the multifunction device 100A is not broken, the multifunction device 100A receives the device search signal.

[0070] At this point, the port name set in the multifunction device 100A is the same as the port name "PN_a" set in the multifunction device 100B. When the multifunction device 100A receives a device search signal including the port name "PN_a" indicating the multifunction device 100A, in S60, the multifunction device 100A transmits a response signal indicating that the multifunction device 100A is a device having the port name "PN_a". In addition, if there is a device with the same port name "PN_a" set in the local area network LN, there is a high possibility that a communication error due to a port name conflict will be detected when S58 is executed. For this reason, when the multifunction device 100B detects a communication error due to a port name conflict when executing S58, the multifunction device 100B may execute the process of S62 in the same manner as when the multifunction device 100B receives a response signal of S60.

[0071] When the multifunction device 100B receives the response signal, in S62, the multifunction device 100B transmits a stop use instruction to the multifunction device 100A, requesting the stop of use of the port name "PN_a". The port name "PN_a" is included in the stop use instruction. If there are multiple devices using the same port name in the local area network LN, for example, a problem may occur such that the terminal device 200 cannot specify one device to send a print job, so it is necessary to stop the use of the port name "PN_a" by the multifunction device 100A. In S62, it is considered that the multifunction device 100B cannot transmit the stop use instruction to the multifunction device 100A due to a communication error when its own port name is "PN_a" due to the conflict of the port name "PN_a". For this reason, in S62, the multifunction device 100B may temporarily change its own port name to a port name different from "PN_a" and then transmit the stop use instruction to the multifunction device 100A. On the other hand, if there is no device with the port name "PN_a" in the local area network LN, the multifunction device 100B does not receive a response signal. Therefore, after broadcasting a device search signal in S58, if the multifunction device 100B does not receive a response signal within a predetermined period of time, the multifunction device 100B ends the handover-related process.

[0072] When the multifunction peripheral 100A receives the use stop instruction, in order to stop the use of the port name "PN_a", in S64, the multifunction peripheral 100A changes the set port name "PN_a" stored in the information database IBa to another port name "PN_c" as shown in the dashed frame F5 in FIG. 5. The other port name "PN_c" is generated, for example, according to a predetermined generation rule. For example, the multifunction peripheral 100A generates another port name "PN_c" by adding a predetermined character string to the port name "PN_a" or by replacing a part of the character string of the port name "PN_a" with another character string, and stores the generated port name in the information database IBa. As a result, even if a print job specifying the port name "PN_a" as a destination is sent from the user's terminal device 200 to the multifunction peripheral 100A after this, the multifunction peripheral 100A does not receive the print job. In this way, it can be said that the change of the port name is a stop process for stopping communication with the terminal device 200 using the original port name (for example, reception of a print job from the terminal device 200).

[0073] In S66, the multifunction peripheral 100A transmits a change completion notice indicating that the port name has been changed to the multifunction peripheral 100B.

[0074] According to the present embodiment described above, an output process (S23, S24 in FIG. 3) is executed in which multifunction device 100A outputs the handover keyword "KW_a" assigned to multifunction device 100A, an input process (S30, S32 in FIG. 3) is executed in which multifunction device 100B receives input of the handover keyword "KW_a", and an acquisition process (S34 in FIG. 3-S42 in FIG. 4) is executed in which multifunction device 100B acquires the port name "PN_a" indicating multifunction device 100A within the local area network LN to which multifunction device 100A is connected, based on the handover keyword "KW_a". Furthermore, a setting process (S44 in FIG. 4) is executed in which the multifunction device 100B sets the port name "PN_a" acquired in the acquisition process as the port name indicating the multifunction device 100B within the local area network LN, and an instruction sending process (S62 in FIG. 5) is executed in which the multifunction device 100B sends a stop use instruction to the multifunction device 100A to stop communication using the port name "PN_a".

[0075] As a result, the multifunction device 100B acquires the port name "PN_a" based on the takeover keyword "KW_a" output from the multifunction device 100A, and sets the port name "PN_a" as the port name indicating the multifunction device 100B in the local area network LN. As a result, the multifunction device 100B can take over the port name "PN_a". Furthermore, the multifunction device 100B transmits a stop use instruction to the multifunction device 100A to stop communication using the port name "PN_a", so that it is possible to avoid the inconvenience that the port name "PN_a" becomes a port name indicating both the multifunction device 100A and the multifunction device 100B in the local area network LN. As a result, for example, the terminal device 200 can perform communication with the multifunction device 100B in the local area network LN similar to the communication performed with the multifunction device 100A.

[0076] Therefore, the terminal device 200 can send a print job to the substitute multifunction device 100B by simply executing the same process as that performed to send a print job to the multifunction device 100A, without changing any of its own settings. As a result, for example, the user does not need to change settings on the terminal device 200, and the burden on the user when using the multifunction device 100B instead of the multifunction device 100A can be reduced. In particular, when the multifunction device 100A is shared by multiple users, the burden on the users is significantly reduced because there is no need to change settings on the terminal device 200 owned by each user in response to the replacement of the multifunction device 100A with the multifunction device 100B.

[0077] Furthermore, according to this embodiment, a storing step (S14 in FIG. 3, FIG. 2(A)) is executed to store the port name "PN_a" in association with the handover keyword "KW_a" in the management database DB of the non-volatile storage device 330 of the server 300. Then, in the above-mentioned acquiring step (S34 in FIG. 3-S42 in FIG. 4), a request step (S34 in FIG. 3) in which the multifunction device 100B transmits a handover request including the handover keyword "KW_a" to the server 300, and a sending step (S42 in FIG. 4) in which the server 300 transmits the port name "PN_a" stored in the management database DB in association with the handover keyword "KW_a" to the multifunction device 100B in response to receiving the handover request is executed, whereby the multifunction device 100B acquires the port name "PN_a". As a result, the port name "PN_a" of the multifunction device 100A can be handed over to the multifunction device 100B via the server 300.

[0078] For example, if the multifunction device 100A breaks down, depending on the state of the breakdown, it may not be possible to transmit the port name "PN_a" of the multifunction device 100A to the multifunction device 100B. By storing the port name "PN_a" and other setting information "OT_a" in advance in the server 300, the port name "PN_a" can be reliably handed over to the multifunction device 100B. Also, for example, even if the amount of information in the other setting information "OT_a" is large, the other setting information "OT_a" can be easily handed over to the multifunction device 100B.

[0079] Furthermore, after the notification image NI is printed by the multifunction device 100A, handover is possible only between the multifunction device 100B and the server 300. Therefore, even if the multifunction device 100A is unable to communicate due to a malfunction, for example, the setting information including the port name "PN_a" can be handed over from the multifunction device 100A to the multifunction device 100B.

[0080] Furthermore, according to this embodiment, the information output by the multifunction device 100A by printing includes time information indicating the date and time TI for defining the validity period in addition to the handover keyword "KW_a" (S22, S24 in FIG. 6 and FIG. 3). The server 300 uses the time information to determine whether the date and time of receipt of the handover request is within the validity period (S36 in FIG. 4). If the date and time of receipt of the handover request is within the validity period (YES in S36 in FIG. 4), the server 300 transmits the port name "PN_a" to the multifunction device 100B (S42 in FIG. 4), and if the date and time of receipt of the handover request is outside the validity period (NO in S36 in FIG. 4), the server 300 does not transmit the port name "PN_a" to the multifunction device 100B. For example, when the handover keyword is printed, the printed handover keyword may be known by a person other than the user. Also, if the user wishes to take over the setting information such as the port name "PN_a", it is considered that the takeover keyword is printed relatively quickly and the notification paper is read by the multifunction device 100B to take over. For this reason, if the date and time of receipt of the takeover request is after an excessive amount of time has passed since the handover keyword was printed, there is a high possibility that a person other than the user has had the notification paper read by his / her own multifunction device with the purpose of illegally obtaining the setting information such as the port name "PN_a". For this reason, in this embodiment, the server 300 transmits the setting information such as the port name "PN_a" only if the date and time of receipt of the takeover request is within the validity period. This reduces the possibility that the setting information that may include personal information such as an email address is transmitted to a device (e.g., a multifunction device) of a person other than the user.

[0081] Furthermore, according to this embodiment, the server 300 stores the port name "PN_a" in the management database DB in association with the device ID "DID_a" of the multifunction device 100A (FIGS. 2A and S14 in FIG. 3). After transmitting the port name "PN_a" to the multifunction device 100B (S42 in FIG. 4), the server 300 releases the association between the port name "PN_a" and the device ID "DID_a" of 100A in the management database DB, and associates the port name "PN_a" with the device ID "DID_b" of the multifunction device 100B (S50 in FIG. 5). This allows the server 300 to manage that the port name "PN_a" is the port name of the multifunction device 100B. For example, when the port name "PN_a" is subsequently handed over to another multifunction device or printer, the server 300 becomes able to transmit an instruction to stop using the port name "PN_a" to the multifunction device 100B.

[0082] Furthermore, according to this embodiment, the server 300 generates a handover keyword "KW_a" (S12 in FIG. 3), and stores the port name "PN_a" in association with the generated handover keyword "KW_a" in the management database DB (S14 in FIG. 3). The server 300 further transmits the generated handover keyword "KW_a" to the multifunction device 100A (S16 in FIG. 3). As a result, the server 300 can manage setting information such as the port name "PN_a" of the multifunction device 100A in association with the handover keyword "KW_a" generated by the server 300 itself. Furthermore, by receiving the handover keyword "KW_a" from the server 300, the multifunction device 100A can print a notification image NI including the handover keyword "KW_a" in the event of a breakdown.

[0083] Furthermore, according to this embodiment, the multifunction device 100A detects its own failure (S20 in FIG. 3), and when a failure of the multifunction device 100A is detected, it outputs the handover keyword "KW_a" (prints a notification image NI including the handover keyword "KW_a"). As a result, when a failure occurs in the multifunction device 100A, the setting information of the multifunction device 100A, such as the port name "PN_a", can be handed over to the multifunction device 100B.

[0084] Furthermore, according to this embodiment, the multifunction device 100B transmits a search signal into the local area network LN to search for the presence of a device (e.g., the multifunction device 100A) that uses the same port name "PN_a" as the multifunction device itself (S58 in FIG. 5). When the multifunction device 100B confirms through the search signal that a device (e.g., the multifunction device 100A) that uses the port name "PN_a" exists (S60 in FIG. 5), it transmits a usage suspension instruction to the device (S62 in FIG. 5). As a result, by the multifunction device 100A transmitting the search signal to the local area network LN, it is possible to more reliably avoid the inconvenience of the port name "PN_a" being used as information indicating multiple devices within the local area network LN.

[0085] Furthermore, according to this embodiment, the output of the handover keyword "KW_a" is performed by the multifunction device 100A printing a notification image NI including the handover keyword "KW_a" on a print medium. The input of the handover keyword "KW_a" is performed by the multifunction device 100B acquiring scan data generated by optically reading the print medium (notification paper in this embodiment) on which the notification image NI is printed. As a result, even if the multifunction device 100A is in a state in which it cannot communicate due to a breakdown, for example, the first printer of the multifunction device 100A can output the handover keyword "KW_a", and the multifunction device 100B can receive the handover keyword "KW_a".

[0086] Furthermore, according to this embodiment, as described above, the port name "PN_a" is used as information indicating the destination of a print job when the terminal device 200 transmits the print job to the local area network LN. Therefore, a print job transmitted from the terminal device 200 with the port name "PN_a" as the transmission destination is received by the multifunction device 100A before the handover-related process is executed, and is received by the multifunction device 100B after the handover-related process is executed. As a result, when printing using the terminal device 200, if the multifunction device 100A breaks down, the user can use the multifunction device 100B as a substitute device.

[0087] As can be seen from the above explanation, the multifunction device 100A of this embodiment is an example of a first printer, and the multifunction device 100B is an example of a second printer. The handover keyword "KW_a" of this embodiment is an example of specific information, and the port name "PN_a" is an example of specific destination information. The device ID "DID_a" of this embodiment is an example of first identification information, and the device ID "DID_b" is an example of second identification information.

[0088] B. Modifications (1) In the above embodiment, the suspension instruction is sent from multifunction device 100B to multifunction device 100A (S62 in FIG. 5). Alternatively, the suspension instruction may be sent from server 300 to multifunction device 100A. FIG. 7 is a sequence diagram of the handover-related process of the modified example. In the modified example, S100 to S114 in FIG. 7 are executed instead of S50 to S66 in FIG. 5. Other processes in the modified example are the same as those in the embodiment (for example, the processes in FIGS. 3 and 4).

[0089] In S100, the server 300 acquires the device ID of the device (the multifunction device 100A in this modification) to which the suspension instruction should be sent from the management database DB. Specifically, the device ID "DID_a" (FIG. 2(A)) associated with the handover keyword "KW_a" included in the handover request received in S34 of FIG. 3 is acquired.

[0090] In S102, the server 300 transmits a stop use instruction to the multifunction device 100A, requesting that the use of the port name "PN_a" be stopped. For example, in this modification, while the multifunction device 100A is powered on, a constant connection such as XMPP is established between the multifunction device 100A and the server 300. The stop use instruction is transmitted using this constant connection.

[0091] When the multifunction peripheral 100A receives the instruction to stop use, in S104, in order to stop use of the port name "PN_a", the set port name "PN_a" stored in the information database IBa is changed to another port name "PN_c". The process of S104 is the same as the process of S64 in FIG. 5 in the embodiment.

[0092] In S106, the multifunction peripheral 100A transmits to the server 300 a change completion notice indicating that the port name has been changed.

[0093] When the server 300 receives the change completion notification, in S108, the server 300 updates the device ID in the management database DB. That is, as in S50 in Fig. 5, the server 300 changes the device ID associated with the handover keyword "KW_a" included in the handover request received in S34 in Fig. 3 from the device ID "DID_a" of the multifunction device 100A to the device ID "DID_b" of the multifunction device 100B, as shown in the dashed-line frame F3 in Fig. 5.

[0094] In S110, the server 300 updates the takeover keyword in the management database DB. That is, the server 300 changes the takeover keyword "KW_a" associated with the port name "PN_a" and other setting information "OT_a" in the management database DB to a new takeover keyword "KW_b" as shown in the dashed frame F4 in Fig. 5, similarly to S52 in Fig. 5.

[0095] In S112B, the server 300 transmits the new takeover keyword "KW_b" to the multifunction peripheral 100B, similarly to S54 in FIG.

[0096] When the multifunction peripheral 100B receives the takeover keyword "KW_b", in S114, it stores the takeover keyword "KW_b" in the same manner as in S56 of FIG.

[0097] According to the above-described modified example, in response to receiving a handover request (S34 in FIG. 3), the server 300 transmits a usage suspension instruction to the multifunction device 100A identified by the device ID "DID_a" associated with the port name "PN_a" in the management database DB (S52B in FIG. 7). As a result, by transmitting a usage suspension instruction from the server 300 to the multifunction device 100A, it is possible to avoid the inconvenience of the port name "PN_a" being used as information indicating both the multifunction device 100A and the multifunction device 100B in the local area network LN. Furthermore, according to this modified example, even if the multifunction device 100B does not have a function for transmitting a usage suspension instruction to the multifunction device 100A, it is possible to cause the multifunction device 100A to stop using the port name "PN_a".

[0098] (2) In the above embodiment, as the stop process for stopping the use of the port name "PN_a", the multifunction device 100A changes the port name of the multifunction device 100A (S64 in FIG. 5). Alternatively, as the stop process, the multifunction device 100A may execute a process for making a setting to prohibit the reception of print jobs. Alternatively, as the stop process, the multifunction device 100A may execute a process for making a setting to prohibit printing by the print mechanism 170.

[0099] (3) In the above embodiment, the multifunction device 100A outputs the specific information by printing a notification image NI including the specific information (specifically, the handover keyword "KW_a") (S24 in FIG. 3). Alternatively, the multifunction device 100A may output the specific information by displaying the specific information on the display unit 140. The multifunction device 100A may also output the specific information by wireless communication such as Bluetooth (registered trademark). Instead of outputting the specific information as it is, the multifunction device 100A may encrypt the specific information using a predetermined encryption method and output (e.g., print, display, communicate), or may encode the specific information into a two-dimensional code (e.g., QR code (registered trademark)) or a one-dimensional code (e.g., a barcode) and output (e.g., print or display).

[0100] (4) In the above embodiment, the multifunction device 100B receives the input of the specific information by reading the notification image NI including the specific information. Alternatively, the multifunction device 100B may receive the input of the specific information by the user's operation via the operation unit 150, for example. Also, for example, when a single-function printer without a reading mechanism is used instead of the multifunction device 100B, scan data indicating the notification image NI including the specific information may be generated by a single-function scanner connected to the local area network LN, and the single-function printer may receive the scan data from the single-function scanner via the local area network LN. Also, the multifunction device 100B may receive the specific information from, for example, a user's terminal device 200 (for example, a smartphone) via the local area network LN. The terminal device 200 may receive the specific information to be transmitted to the multifunction device 100B by input by the user's operation, or by capturing a notification image NI including the specific information with a digital camera.

[0101] (5) In the above embodiment, the setting information including the port name "PN_a" is handed over from the multifunction device 100A to the multifunction device 100B via the server 300. Alternatively, the setting information including the port name "PN_a" may be handed over from the multifunction device 100A to the multifunction device 100B without the server 300. In this case, for example, the multifunction device 100A prints on a sheet a print image including all the setting information to be handed over including the port name "PN_a". The multifunction device 100B generates scan data by reading the notification image with the printing mechanism 170, and acquires the scan data. The multifunction device 100B analyzes the scan data by character recognition processing to acquire the setting information including the port name "PN_a", and stores the setting information in its own information database IBb. In this modified example, the print image showing the setting information including the port name "PN_a" is an example of specific information.

[0102] (6) In the above embodiment, the specific information used for handing over the setting information including the port name “PN_a” is the handover keyword “KW_a.” The specific information used for handing over is not limited to the handover keyword “KW_a,” and may be unique information assigned to the multifunction peripheral 100A, for example, the device ID “DID_a” of the multifunction peripheral 100A.

[0103] (7) The handover-related processing in the above embodiment is merely an example, and may be modified or omitted as appropriate. For example, in S24 in Fig. 3, the multifunction device 100A prints a notification image NI including the handover keyword and date and time information, but may print a notification image NI including only the handover keyword. In this case, S36 and S38 in Fig. 4 are omitted, and S39 in Fig. 4 is executed after S34 in Fig. 3.

[0104] (8) In the above embodiment, the processes are executed in the order of the process related to the setting of the port name (S44 to S48 in FIG. 4), the process related to the update of the management database (S50 to S56 in FIG. 5), and the process related to the suspension of use (S58 to S66 in FIG. 5), but the order of these processes may be changed. Specifically, after the multifunction device 100B receives the port name and other setting information in S42 in FIG. 4, the multifunction device 100A and the multifunction device 100B execute the process related to the suspension of use (S58 to S66 in FIG. 5). After the process related to the suspension of use (S56 to S66 in FIG. 5) is executed, the multifunction device 100A and the server 300 execute the process related to the setting of the port name (S44 to S48 in FIG. 4). Furthermore, after the process related to the setting of the port name (S44 to S48 in FIG. 4) is executed, the server 300 and the multifunction device 100B execute the process related to the update of the management database (S50 to S56 in FIG. 5). This temporarily eliminates the period during which the port name "PN_a" is duplicated, making it possible to prevent problems caused by the duplication of the port name "PN_a."

[0105] (9) In the above embodiment, by executing S50 to S54 in Fig. 5, preparations are made for handing over the setting information including the port name "PN_a" to the next substitute device in the event of a breakdown of the multifunction device 100B. Alternatively, S50 to S54 in Fig. 5 may be omitted. In this case, for example, after the handover-related processing, the multifunction device 100B and the server 300 may prepare for handing over the setting information including the port name "PN_a" to the next substitute device by executing processing similar to the processing executed by the multifunction device 100A and the server 300 in S10 to S18 in Fig. 3.

[0106] (10) In the above embodiment, the server 300 generates a handover keyword and transmits it to the multifunction peripheral 100A (S12, S26 in FIG. 3). Alternatively, the multifunction peripheral 100A may generate a handover keyword and transmit the generated handover keyword to the server 300 together with a setting save request in S10 in FIG.

[0107] (11) In the above embodiment, when a malfunction occurs in the multifunction device 100A, the multifunction device 100A prints a notification image NI including a handover keyword. This is not limiting, and the multifunction device 100A may print a notification image NI including a handover keyword, for example, when a print instruction is input by the user. In this case, even if the multifunction device 100A is not malfunctioning, for example, when the user wants to replace the multifunction device 100A with a new multifunction device 100B, the setting information including the port name "PN_a" can be easily handed over from the multifunction device 100A to the multifunction device 100B.

[0108] (12) Either or both of the multifunction peripherals 100A and 100B in the above embodiments may be a single-function printer that does not include an image reading mechanism and has only a printing mechanism.

[0109] (13) In the above embodiment, the setting information of the multifunction device including the port name "PN_a" is handed over from the multifunction device 100A to the multifunction device 100B. Not limited to this, various information related to the multifunction device may be handed over from the multifunction device 100A to the multifunction device 100B. For example, if the multifunction device 100A provides a predetermined service provided by the server 300, the service information related to the predetermined service may be handed over from the multifunction device 100A to the multifunction device 100B. The service information may include information indicating the type of the service and information indicating the service usage history. The predetermined service may be a service of various types, for example, a printing material management service in which the server 300 manages the consumption of printing materials such as ink in the multifunction device by a user paying a certain amount of fee every month, and the server 300 automatically orders printing materials according to the consumption of the printing materials in the multifunction device. The print service may also be a service that executes remote printing by transmitting a print job from the terminal device 200 to the server 300, and the server 300 transmitting the print job to the multifunction peripheral using a constant connection.

[0110] (14) In the above embodiments, part of the configuration realized by hardware may be replaced by software, and conversely, part or all of the configuration realized by software may be replaced by hardware.

[0111] The present invention has been described above based on examples and modifications, but the above-described embodiments of the invention are intended to facilitate understanding of the present invention and are not intended to limit the present invention. The present invention may be modified or improved without departing from the spirit and scope of the claims, and equivalents thereof are included in the present invention. [Explanation of symbols]

[0112] 1000...system, 100A, 100B...multifunction device, 110...CPU, 120...volatile storage device, 130...non-volatile storage device, 140...display unit, 150...operation unit, 160...reading mechanism, 170...printing mechanism, 180...communication IF, 200...terminal device, 300...server, 310...CPU, 320...volatile storage device, 330...non-volatile storage device, 380...communication IF, DB...management database, IB...information database, IT...Internet, LN...local area network, PGp, PGs...computer program

Claims

1. 1. A method performed with a first printer and a second printer to be used in place of the first printer, comprising: an output step in which the first printer outputs specific information regarding the first printer; an input step of the second printer receiving an input of the specific information; an acquisition step in which the second printer acquires specific destination information indicating the first printer within the local network to which the first printer is connected based on the specific information; a setting step of setting the specific destination information as destination information indicating the second printer within a local area network by the second printer; an instruction transmission step in which either the second printer or a server capable of communicating with the first printer transmits to the first printer an instruction to execute a stop process for stopping communication using the specific destination information; A method for performing.

2. 10. The method of claim 1 further comprising: a storage step of storing the specific destination information in a storage device of the server in association with the specific information; The obtaining step includes: a request step of the second printer transmitting to the server an information request including the specific information, the information request requesting the specific destination information; a destination information transmission step of the server transmitting the specific destination information stored in association with the specific information to the second printer in response to receiving the information request; a step of: causing the second printer to obtain the specific destination information by executing the step of:

3. 3. The method of claim 2, The output step further includes outputting time information for defining a validity period of the specific information, In the destination information transmitting step, The server uses the time information to determine whether the date and time of receipt of the information request is within the validity period; The method includes the server sending the specific destination information to the second printer if the date and time of receiving the information request is within the validity period, and not sending the specific destination information to the second printer if the date and time of receiving the information request is outside the validity period.

4. 3. The method of claim 2, The storing step stores the specific destination information in association with first identification information that identifies the first printer, The method further comprises: The method includes a correspondence step in which, after the destination information sending step, the server cancels the association between the stored specific destination information and the first identification information, and associates the specific destination information with second identification information that identifies the second printer.

5. 3. The method of claim 2, In the storing step, the server generates the specific information, and stores the specific destination information in the storage device in association with the generated specific information; The method further includes a specific information transmitting step of the server transmitting the specific information to the first printer.

6. 10. The method of claim 1 further comprising: a detection step of detecting a fault in the first printer, The method, wherein the outputting step is executed if a failure of the first printer is detected in the detecting step.

7. 2. The method of claim 1 , The method further comprises: a search step in which the second printer transmits a search signal to the local area network to search for a printer using the same destination information as the specific destination information; The instruction sending step is a step of sending an instruction to execute the stop process to a printer using the same destination information when it is confirmed in the search step that a printer using the same destination information exists.

8. 3. The method of claim 2, The storing step stores the specific destination information in association with first identification information that identifies the first printer, The method further comprises: The instruction sending process is a process in which the server, in response to receiving the information request, sends an instruction to execute the stop processing to the first printer identified by the first identification information associated with the specific destination information.

9. 2. The method of claim 1 , the output step is a step of printing a specific image including the specific information on a print medium by the first printer; The method, wherein the input step is a step of acquiring scan data generated by optically reading the print medium on which the specific image is printed.

10. 2. The method of claim 1 , the specific destination information is information used as information indicating a destination of a print job when a terminal device transmits the print job to the local area network, A method in which the print job sent from the terminal device with the specific destination information as a destination is received by the first printer before the setting step and the instruction sending step are executed, and is received by the second printer after the setting step and the instruction sending step are executed.

11. 1. A communication system comprising: A first printer; a second printer to be used in place of the first printer; Equipped with The first printer outputs specific information regarding the first printer; The second printer receives the input of the specific information; the second printer acquires specific destination information indicating the first printer within the local network to which the first printer is connected based on the specific information; The second printer sets the specific destination information as destination information indicating the second printer within a local area network; A communication system in which either the second printer or a server capable of communicating with the first printer sends an instruction to the first printer to execute a stop process to stop communication using the specific destination information.

Images