A management device, a computer program for the management device, and a method performed by the management device.

Abstract

To provide a technology allowing a manager who manages lending-out and return of a plurality of mobile devices to appropriately manage the plurality of mobile devices.SOLUTION: A management device includes a memory capable of storing a plurality of pieces of associated information corresponding to a plurality of mobile devices. Each of the plurality of pieces of associated information includes mutually associated pieces of: device identification information for identifying a corresponding mobile device; user identification information for identifying a user having lent the corresponding mobile device; and history information regarding lending-out and return of the corresponding mobile device. When a prescribed condition regarding the lending-out of a first mobile device is satisfied, the management device executes, on the basis of first associated information corresponding to the first mobile device, a prescribed inquiry to a first user. When response information to the prescribed inquiry is acquired, the management device stores the first device identification information and the response information in the memory in association with each other, and outputs the first device identification information and the response information to an output unit.SELECTED DRAWING: Figure 8

Description

Technical Field

[0001] This specification discloses a technology related to a management device that outputs response information acquired from a mobile device.

Background Art

[0002] Patent Document 1 discloses a photo printer. When the photo printer is first powered on, it executes a questionnaire process. In the questionnaire process, when an answer from the user is acquired, the photo printer prints the answer to the questionnaire.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] This specification provides a technology that enables an administrator who manages the lending and return of a plurality of mobile devices to appropriately manage the plurality of mobile devices.

Means for Solving the Problems

[0005] This specification discloses a management device for managing the lending and return of a plurality of mobile devices. The management device may include: a memory capable of storing a plurality of related information corresponding to the plurality of mobile devices, wherein each of the plurality of related information is information associated with device identification information that identifies the corresponding mobile device, user identification information that identifies the user who has borrowed the corresponding mobile device, and history information related to the lending and / or return of the corresponding mobile device; an inquiry unit that, based on the first related information corresponding to the first mobile device among the plurality of related information, executes a predetermined inquiry related to the lending of the first mobile device to a first user identified by the first user identification information included in the first related information when predetermined conditions related to the lending of the first mobile device are met; a storage control unit that, when answer information to the predetermined inquiry is obtained, associates the first device identification information that identifies the first mobile device with the answer information and stores it in the memory; and an output control unit that, after the first device identification information and the answer information have been associated and stored in the memory, causes the first device identification information and the answer information to output to an output unit.

[0006] According to the above configuration, the management device executes a predetermined query to the first user when predetermined conditions are met, based on first related information corresponding to the first mobile device. When the management device obtains response information to the predetermined query, it stores the first device identification information and the response information in memory in association with each other, and outputs the first device identification information and the response information. Therefore, an administrator using the management device can check the responses related to the lending of the first mobile device. Consequently, the administrator can properly manage multiple mobile devices.

[0007] The methods, computer programs, and computer-readable recording media used by the above-mentioned management device are also novel and useful. Furthermore, the communication system including the management device and the first mobile device is also novel and useful. [Brief explanation of the drawing]

[0008] [Figure 1] This shows the configuration of the communication system. [Figure 2] An example of each table is shown. [Figure 3] This shows a flowchart of the lending process performed by the management device. [Figure 4] This shows a flowchart of the return process performed by the management device. [Figure 5] This shows a flowchart of the inquiry transmission process performed by the management device. [Figure 6] This shows a flowchart of the response reception process performed by the management device. [Figure 7] This shows a flowchart of the printer operations performed by a mobile printer. [Figure 8] This shows the sequence for Case A, where a mobile printer is loaned out. [Figure 9] The tables in Case A are shown below. [Figure 10] The sequence for Case B, in which a mobile printer is loaned out, is shown in the third embodiment. [Figure 11] The tables in Case B are shown below. [Figure 12] The flowchart for the loan process performed by the management device in the fourth embodiment is shown. [Figure 13] The flowchart for the return process performed by the management device in the fourth embodiment is shown. [Figure 14] The sequence for Case B in which a mobile printer is loaned out is shown in the fourth embodiment. [Figure 15] The tables in Case C are shown below. [Figure 16] In the fifth embodiment, a flowchart of the determination process performed by the control device is shown. [Figure 17] An example of the inquiry screen displayed in the fifth embodiment is shown. [Modes for carrying out the invention]

[0009] (First embodiment) (Configuration of communication system 2; Figure 1) As shown in Figure 1, the communication system 2 comprises multiple mobile printers 10A to 10C, a PC 100, a reader 110, and a management device 200. The PC 100, reader 110, and management device 200 are installed inside a facility 60. Facility 60 is, for example, a company or a university. The PC 100 and reader 110 are installed in a storage room 70 within facility 60. The multiple mobile printers 10A to 10C are stored in the storage room 70. The management device 200 is installed in a different location from the multiple mobile printers 10A to 10C, the PC 100, and the reader 110. Users working at facility 60 can borrow the mobile printers 10A to 10C and use them externally (in a location different from the storage room 70 within facility 60, such as a business trip location). In the following, the mobile printers 10A to 10C may be referred to simply as "printer 10A to 10C," omitting the "mobile" part. Also, in the following, printers 10A to 10C may be collectively referred to as "printer 10."

[0010] (Configuration of printers 10A-10C) The printer 10A is a portable peripheral device (i.e., a peripheral device such as a PC) capable of performing printing functions. The printer 10A comprises an operation unit 12, a display unit 14, a print execution unit 16, a battery mounting unit 18, a communication interface 20, and a control unit 30. The printer 10A is assigned a device ID "DV1" to identify it. The printer 10A has a housing (not shown) to which an information code (hereinafter sometimes referred to as "device code") encoding the device ID "DV1" is attached. Hereafter, the interface will be referred to as "I / F".

[0011] The operation unit 12 includes a plurality of keys. By operating the operation unit 12, the user can input various instructions to the printer 10A. The display unit 14 is a display for displaying various information. The printing execution unit 16 is a printing mechanism such as an inkjet method or a laser method. A battery such as a lithium ion battery can be attached to the battery attachment unit 18. The communication I / F 20 may be a wireless I / F or a wired I / F.

[0012] The control unit 30 includes a CPU 32 and a memory 34. The CPU 32 executes various processes according to the program 36 stored in the memory 34. The memory 34 is composed of a volatile memory, a non-volatile memory, etc.

[0013] The printers 10B and 10C have the same configuration as the printer 10A, except that they have device IDs "DV2" and "DV3".

[0014] (Configuration of the PC 100) The PC 100 is a stationary PC, but in a modification example, it may be a portable device such as a notebook PC. The PC 100 is a device used when lending or returning the printers 10A to 10C. On the desk where the PC 100 is installed in the storage 70, there are stickers indicating an information code (hereinafter sometimes referred to as "lending code") encoding information indicating that an operation for receiving the lending of the printer 10 has been performed (hereinafter sometimes referred to as "lending operation information"), and an information code (hereinafter sometimes referred to as "return code") encoding information indicating that an operation for returning the printer 10 has been performed (hereinafter sometimes referred to as "return operation information").

[0015] (Configuration of the reading device 110) The reader 110 is a portable device that is communicatively connected to the PC 100. The reader 110 is a device for capturing images of information codes (e.g., barcodes, etc.) and reading the data recorded in the captured information codes. The reader 110 transmits the read data to the PC 100.

[0016] (Configuration of the control device 200) The management device 200 is a device for managing the lending and return of printers 10A to 10C. The management device 200 is a device managed by an administrator who manages the lending and return of printers 10A to 10C. In this embodiment, the management device 200 is a stationary PC, but in modified versions, it may be a server or the like. The management device 200 comprises an operation unit 212, a display unit 214, a communication I / F 220, and a control unit 230.

[0017] The control unit 212 is equipped with multiple keys. By operating the control unit 212, the user can input various instructions to the management device 200. The display unit 214 is a display for showing various information. The management device 200 is connected to the PC 100 via a communication interface 220.

[0018] The control unit 230 comprises a CPU 232 and a memory 234. The CPU 232 performs various processes according to a program 236 stored in the memory 234. The memory 234 is composed of volatile memory, non-volatile memory, etc. The memory 234 further comprises a user table 238, a first device table 240, a second device table 242, a query table 244, and a response table 246.

[0019] (Structure of each table; Figure 2) Next, referring to Figure 2, the contents of the user table 238, the first device table 240, the second device table 242, the inquiry table 244, and the response table 246 within the management device 200 will be explained.

[0020] Inquiry table 244 is a table for managing inquiry information for making inquiries to users. Inquiry table 244 stores inquiry IDs and inquiry information in association with each other. Inquiry information includes information including a device ID, and includes information related to the lending of printer 10 identified by that device ID.

[0021] User table 238 is a table for managing information about users. User table 238 stores a user ID, email address, and inquiry ID in association with each user.

[0022] The first device table 240 is a table for managing the lending and return of printers 10A to 10C. In the first device table 240, the device ID, user ID, lending date and time information, and return date and time information are stored in association with each other. The lending date and time information indicates the most recent lending date and time when printer 10 was borrowed. The return date and time information indicates the most recent return date and time when printer 10 was returned.

[0023] The second device table 242 is a table for managing the printers 10 to which inquiry signals should be sent. The inquiry signal is information containing inquiry information included in the inquiry table 244, and is a signal for executing an inquiry related to the lending of printer 10. In the second device table 242, the device ID and the inquiry ID are stored in association.

[0024] The response table 246 is a table for managing response information to inquiries. In the response table 246, device IDs and response information are stored in association. The response information is information that indicates the response to an inquiry related to the lending of printer 10, which is identified by the device ID associated with the response information.

[0025] (Loan processing; Figure 3) Referring to Figure 3, the lending process performed by the CPU 232 of the management device 200 will be described. Note that the communication performed by each device is carried out via the communication interface of each device (for example, the communication interface 220 of the management device). For this reason, in the following, when describing the process related to communication via the communication interface, the phrase "via the communication interface" will be omitted.

[0026] In S10, the CPU 232 monitors for the reception of loan information from the PC 100. The loan information includes the device ID of the printer 10 to be loaned (hereinafter sometimes referred to as the "device ID to be loaned") and the user ID of the user who wishes to borrow the printer 10 (hereinafter sometimes referred to as the "user ID to be loaned"). When the user performs an operation (hereinafter sometimes referred to as a "loan operation") to read the loan code, device code, and information code (hereinafter sometimes referred to as the "user code") attached to a card or the like owned by the user that encodes the user ID that identifies the user, the reader 110 decodes each code to obtain the loan operation information, device ID, and user ID, and supplies the loan operation information, device ID, and user ID to the PC 100. Then, when PC100 obtains loan operation information, device ID, and user ID from reader 110, it determines that an operation to borrow printer 10 has been performed based on the loan operation information, and sends the loan information, including device ID and user ID, to management device 200. When CPU232 receives loan information from PC100, it determines YES in S10 and proceeds to S12.

[0027] In S12, CPU232 stores the user ID of the device to be borrowed in the first device table 240, associating it with the device ID of the device to be borrowed. CPU232 also stores the current date and time as borrowing date and time information in the first device table 240, associating it with the device ID of the device to be borrowed.

[0028] In S14, the CPU 232 determines whether or not it has received error information from the printer 10, which is identified by the device ID of the device being loaned. The error information indicates that an error detectable by the printer 10 has occurred in the printer 10. If the CPU 232 has received error information from the printer 10 (YES in S14), it terminates the process shown in Figure 3. If it has not received error information from the printer 10 (NO in S14), it proceeds to S20.

[0029] In S20, CPU232 determines in user table238 whether an inquiry ID is associated with the user ID to be borrowed. If an inquiry ID is associated with the user ID to be borrowed (YES in S20), CPU232 proceeds to S22. If an inquiry ID is not associated with the user ID to be borrowed (NO in S20), the process shown in Figure 3 is terminated.

[0030] In S22, the CPU 232 identifies the inquiry ID associated with the user ID to be borrowed in the user table 238, and stores the identified inquiry ID in association with the device ID to be borrowed in the second device table 242.

[0031] In S30, CPU232 identifies the email address associated with the user ID to be borrowed in user table 238, and identifies the inquiry information associated with the inquiry ID identified in S22 in inquiry table 244. Then, CPU232 sends an email containing the identified inquiry information and the identified email address as the recipient email address. When S30 finishes, CPU232 terminates the process shown in Figure 3.

[0032] (Return process; Figure 4) Referring to Figure 4, the return process performed by the CPU 232 of the management device 200 will be described. The CPU 232 performs the return process shown in Figure 4 in parallel with the lending process shown in Figure 3.

[0033] In S50, the CPU 232 monitors for the reception of return information from the PC 100. The return information includes the device ID of the printer 10 to be returned (hereinafter sometimes referred to as the "device ID to be returned") and the user ID of the user returning the printer 10 (hereinafter sometimes referred to as the "user ID to be returned"). When the user performs an operation to read the return code, device code, and user code (hereinafter sometimes referred to as the "return operation"), the reader 110 decodes each code to obtain the return operation information, device ID, and user ID, and supplies the return operation information, device ID, and user ID to the PC 100. When the PC 100 obtains the return operation information, device ID, and user ID from the reader 110, it determines that an operation to return the printer 10 has been performed based on the return operation information, and transmits the return information, including the device ID and user ID, to the management device 200. When CPU232 receives return information from PC100, it determines YES in S50 and proceeds to S52.

[0034] In S52, CPU232 determines in user table 238 whether or not a query ID is associated with the user ID to be returned. If a query ID is associated with the user ID to be returned (YES in S52), CPU232 proceeds to S60; otherwise, if a query ID is not associated with the user ID to be returned (NO in S52), it proceeds to S70.

[0035] In S60, CPU232 identifies the inquiry ID associated with the user ID to be returned in user table238, and determines in second device table242 whether the device ID to be returned is associated with the identified inquiry ID. If the device ID to be returned is associated with the identified inquiry ID (YES in S60), CPU232 proceeds to S62; if the device ID to be returned is not associated with the identified inquiry ID (NO in S60), it proceeds to S70.

[0036] In S62, CPU232 removes the combination of the device ID to be returned and the identified inquiry ID from the second device table 242.

[0037] In S70, the CPU 232 determines whether the time the printer 10 to be returned was used by the user (hereinafter sometimes referred to as "usage time") is less than a first predetermined time (for example, 20 minutes). The CPU 232 identifies the loan date and time information associated with the device ID to be returned in the first device table 240, and identifies the difference time between the loan date and time indicated by the identified loan date and time information and the current date and time (i.e., the return date and time) as the usage time. If the usage time is less than the first predetermined time (YES in S70), the CPU 232 proceeds to S80, and if the usage time is equal to or greater than the first predetermined time (NO in S70), the CPU 232 proceeds to S90.

[0038] In S80, CPU 232 updates inquiry table 244. CPU 232 generates a new inquiry ID and stores the newly generated inquiry ID in inquiry table 244, associating it with the inquiry information. The inquiry information includes the device ID to be returned, as well as information to inquire about the reason why the usage time of printer 10, identified by the device ID to be returned, was short.

[0039] In S82, CPU232 updates user table 238. CPU232 stores the new query ID generated in S80 in user table 238, associating it with the user ID to be returned. After S82 finishes, CPU232 proceeds to S90.

[0040] In S90, CPU232 updates the first device table 240. CPU232 deletes the user ID associated with the device ID to be returned from the first device table 240, and stores the current date and time in the first device table 240 as return date and time information associated with the device ID to be returned. When S90 finishes, CPU232 terminates the process shown in Figure 4.

[0041] (Inquiry transmission process; Figure 5) Referring to Figure 5, the inquiry transmission process performed by the CPU 232 of the management device 200 will be described. The CPU 232 executes the inquiry transmission process shown in Figure 5 in parallel with the lending process shown in Figure 3 and the return process shown in Figure 4.

[0042] In S110, the CPU 232 monitors for the reception of a query request from the printer 10. The query request is a signal requesting the transmission of a query signal and includes the device ID of the sending printer 10. If the CPU 232 receives a query request from the printer 10, it determines YES in S110 and proceeds to S112. S112 is the same as S14 in Figure 3. If the CPU 232 determines YES in S112, it terminates the process in Figure 5, and if it determines NO in S112, it proceeds to S120.

[0043] In S120, CPU232 identifies the device ID included in the query request.

[0044] In S122, the CPU 232 determines whether the second device table 242 contains the identified device ID. If the second device table 242 contains the identified device ID (YES in S122), the CPU 232 proceeds to S124. If the second device table 242 does not contain the identified device ID (NO in S122), the process shown in Figure 5 is terminated.

[0045] In S124, the CPU 232 sends a query signal to the printer 10. The CPU 232 identifies the query ID associated with the identified device ID in the second device table 242, and identifies the query information associated with the identified query ID in the query table 244. Then, the CPU 232 generates a query signal containing the identified query information and sends the generated query signal to the printer 10. When S124 is completed, the CPU 232 terminates the process shown in Figure 5.

[0046] (Response reception processing; Figure 6) Referring to Figure 6, the response reception process performed by the CPU 232 of the management device 200 will be described. The CPU 232 performs the response reception process shown in Figure 6 in parallel with the lending process shown in Figure 3, the return process shown in Figure 4, and the inquiry transmission process shown in Figure 5.

[0047] In S140, the CPU 232 monitors for the reception of a response signal from the printer 10, which is a response to the inquiry signal. The response signal contains information including the device ID of the printer 10 that sent the response signal (hereinafter sometimes referred to as the "source device ID") and response information. The response information includes the device ID included in the inquiry information, as well as information indicating the answer to the inquiry. If the CPU 232 receives a response signal from the printer 10, it determines YES in S140 and proceeds to S142.

[0048] In S142, the CPU 232 updates the response table 246. The CPU 232 identifies the device ID included in the response information within the received response signal. The CPU 232 then associates the identified device ID with the response information and stores it in the response table 246.

[0049] In S144, the CPU 232 updates the second device table 242. The CPU 232 identifies the source device ID in the response signal and deletes the combination of the identified device ID and the inquiry ID associated with that device ID from the second device table 242. If a combination of a device ID different from the source device ID and a deleted inquiry ID exists in the second device table 242, the CPU 232 also deletes that combination from the second device table 242.

[0050] In S146, CPU232 updates user table 238. CPU232 removes the query ID that was deleted in S144 from user table 238.

[0051] In S148, CPU 232 updates the query table 244. CPU 232 deletes the query IDs deleted in S144 and the query information associated with those query IDs from the query table 244. When S148 finishes, CPU 232 terminates the process shown in Figure 6.

[0052] (Printer processing; Figure 7) Referring to Figure 7, the printer processing performed by the CPU 32 of the printer 10A will be described. When the power of the printer 10A is turned ON, the CPU 32 starts the processing shown in Figure 7.

[0053] In S160, CPU32 monitors whether a network connection is established. For example, CPU32 determines that a network connection has been established when a network connection operation is performed by the user. If a network connection is established, CPU32 determines YES in S160 and proceeds to S170.

[0054] In S170, the CPU 32 uses the established network connection to send a query request containing the device ID "DV1" to the management device 200.

[0055] In S172, the CPU 32 determines whether or not it has received an inquiry signal from the management device 200. If the CPU 32 has received an inquiry signal from the management device 200 (YES in S172), it proceeds to S174; if it has not received an inquiry signal from the management device 200 (NO in S172), it proceeds to S180.

[0056] In S174, the CPU 32 displays the inquiry screen 500 on the display unit 14. The inquiry screen 500 includes a message to inquire about the reason why the printer 10 was used for a short time. The inquiry screen 500 also includes four checkboxes corresponding to "Battery not installed," "Problem with paper transport," "No paper loaded," and "Other," as well as an OK button and a Cancel button.

[0057] In S176, the CPU 32 determines whether the response operation was performed by the user. If the CPU 32 accepts an operation to check one or more checkboxes, or an operation to select the OK button, it determines YES in S176 and proceeds to S178. On the other hand, if the CPU 32 accepts an operation to select the Cancel button, it determines NO in S176 and proceeds to S180.

[0058] In S178, the CPU 32 sends a response signal to the management device 200. The response signal includes the device ID "DV1" of the printer 10A and response information. The response information includes the device ID included in the received inquiry information and information indicating the response corresponding to the checkbox that was checked in S176.

[0059] In S180, the CPU32 determines whether or not an error has occurred in printer 10A. If an error has occurred in printer 10A (YES in S180), the CPU32 proceeds to S182; if no error has occurred in printer 10A (NO in S180), the CPU32 proceeds to S184. An error occurring in printer 10A could be, for example, an error requiring parts replacement.

[0060] In S182, the CPU 32 sends error information indicating the error identified in S180 to the management device 200.

[0061] In S184, the CPU 32 displays the top screen on the display unit 14. When S184 is finished, the CPU 32 terminates the process shown in Figure 7. The CPU 32 periodically executes the process in S180 while the printer 10A is powered on. The CPUs of printers 10B and 10C (not shown) also execute the same process as in Figure 7.

[0062] (Case A; Figures 8 and 9) Next, with reference to Figures 8 and 9, a specific case A realized by the communication system 2 of this embodiment will be described. In the initial state of case A, three mobile printers 10A to 10C are stored in the storage unit 70 (see Figure 1). That is, the user ID in the first device table 240 is empty. Also, the inquiry ID in the user table 238 is empty. Furthermore, the second device table 242, the inquiry table 244, and the answer table 246 are empty. In this case, we assume that the battery is not installed in the battery mounting section 18 of printer 10A.

[0063] In T10, when a user performs a lending operation for printer 10A using a reader 110 connected to PC100, PC100 obtains lending operation information, the device ID "DV1" and the user ID "U1" of the device to be lent from the reader 110, and in T12, transmits the lending information, including the device ID "DV1" and the user ID "U1" of the device to be lent, to the management device 200.

[0064] When the management device 200 receives loan information from the PC 100 in T12 (YES in S10 of Figure 3), in T14, it associates the loaned user ID "U1" and loan date and time information "3 / 27 10:00" with the loaned device ID "DV1" and stores them in the first device table 240 (S12). Next, the management device 200 determines that it has not received error information from the printer 10A (NO in S14), and determines in the user table 238 that no inquiry ID is associated with the loaned user ID "U1" (NO in S20). In this case, the management device 200 does not send an inquiry signal by email.

[0065] As described above, in this case, the battery is not installed in the battery mounting section 18 of printer 10A. Therefore, the user returns printer 10A to storage 70 as soon as possible. In this case, the user returns printer 10A to storage 70 at "3 / 27 10:10".

[0066] In T30, when a user performs a return operation of the printer 10A using the reader 110 connected to the PC 100, the PC 100 obtains the return operation information, the device ID "DV1" and the user ID "U1" of the device to be returned from the reader 110, and in T32, transmits the return information, including the device ID "DV1" and the user ID "U1" of the device to be returned, to the management device 200.

[0067] When the management device 200 receives return information from the PC 100 at T32 (YES at S50 in Figure 4), it determines in the user table 238 that no inquiry ID is associated with the user ID "U1" to be returned (NO at S52). Next, the management device 200 identifies the loan date and time information associated with the device ID "DV1" to be returned in the first device table 240, identifies the difference time between the loan date and time "3 / 27 10:00" indicated by the loan date and time information and the current date and time "3 / 27 10:10" as the usage time "10 minutes", and determines that the usage time "10 minutes" is less than the first predetermined time (YES at S70). In this case, the management device 200 generates a new inquiry ID "IQ1", and at T40, associates the inquiry ID "IQ1" with the inquiry information "IN1(DV1)" which includes the device ID "DV1" to be returned, and stores it in the inquiry table 244 (S80) (see Figure 9). Next, at T42, the management device 200 associates the inquiry ID "IQ1" with the user ID "U1" to be returned and stores it in the user table 238 (S82) (see Figure 9). Next, at T44, the management device 200 deletes the user ID "U1" associated with the device ID "DV1" to be returned from the first device table 240, and stores the return date and time information "3 / 27 10:10" in the first device table 240, associating it with the device ID "DV1" to be returned (S90) (see Figure 9).

[0068] After returning printer 10A, the user performs an operation to borrow printer 10B, which has a battery installed. In T50, when the user performs the operation to borrow printer 10B using the reader 110 connected to PC 100, PC 100 obtains the borrowing operation information, the borrowed device ID "DV2", and the borrowed user ID "U1" from the reader 110, and in T52, transmits the borrowing information, including the borrowed device ID "DV2" and the borrowed user ID "U1", to the management device 200.

[0069] When the management device 200 receives loan information from the PC 100 in T52 (YES in S10 of Figure 3), in T54 it associates the loaned user ID "U1" and loan date and time information "3 / 27 10:15" with the device ID "DV2" and stores them in the first device table 240 (S12). Next, the management device 200 determines that it has not received error information from the printer 10A (NO in S14), determines in the user table 238 that the loaned user ID "U1" is associated with the inquiry ID "IQ1" (YES in S20), and in T60 it associates the loaned device ID "DV2" with the inquiry ID "IQ1" and stores them in the second device table 242 (S22) (see Figure 9). Next, the management device 200 identifies the email address MA1 associated with user ID "U1" in the user table 238, and identifies the inquiry information "IN1(DV1)" associated with inquiry ID "IQ1" in the inquiry table 244. Then, in T70, the management device 200 sends an email ML containing the inquiry information "IN1(DV1)" and the email address MA1 as the recipient email address (S30). As a result, the email ML is sent to the terminal device 300 owned by the user. When the user opens the email ML, a screen containing the same information as the inquiry screen in Figure 7 is displayed on the terminal device 300.

[0070] When printer 10B receives an operation to turn on the power of printer 10B at T80 and an operation to connect to the network (YES at S160 in Figure 7), it sends an inquiry request including device ID "DV2" to the management device 200 at T90 (S170).

[0071] When the management device 200 receives an inquiry request from the printer 10B at T90 (YES at S110 in Figure 5), it determines that it has not received any error information from the printer 10B (NO at S112) and identifies the device ID "DV2" included in the inquiry request (S120). Next, the management device 200 determines that the second device table 242 contains the identified device ID "DV2" (YES at S122), identifies the inquiry ID "IQ1" associated with the identified device ID "DV2" in the second device table 242, and identifies the inquiry information "IN1(DV1)" associated with the identified inquiry ID "IQ1" in the inquiry table 244. Next, at T92, the management device 200 generates an inquiry signal containing the identified inquiry information "IN1(DV1)" and transmits the generated inquiry signal to the printer 10B.

[0072] When printer 10B receives an inquiry signal from the management device 200 at T92 (YES at S172 in Figure 7), it displays an inquiry screen at T94. The inquiry screen in this case is the same as inquiry screen 500 in Figure 7, except that the device ID "DV1" is displayed in the area where the device ID "xxx" is displayed. When printer 10B receives an operation to check the checkbox corresponding to "Battery not installed" and an operation to select the OK button at T96 (YES at S176), it sends a response signal to the management device 200 at T98, which includes the source device ID "DV2" and the response information "RE1(DV1)" (S178). The response information "RE1(DV1)" includes the device ID "DV1" included in the inquiry information "IN1(DV1)" and information indicating the response to the inquiry, "Battery not installed". Although not shown in the diagram, printer 10B then determines that there is no error in printer 10B (NO in S180) and displays the top screen (S184).

[0073] When the management device 200 receives a response signal from the printer 10B at T98 (YES at S140 in Figure 6), at T100, it associates the device ID "DV1" with the response information "RE1(DV1)" and stores it in the response table 246 (S142). At T102, it deletes the combination of device ID "DV2" and inquiry ID "IQ1" from the second device table 242 (S144). At T104, it deletes the inquiry ID "IQ1" from the user table 238 (S146). At T106, it deletes the combination of inquiry ID "IQ1" and inquiry information "IN1(DV1)" from the inquiry table 244 (S148).

[0074] When the management device 200 receives an operation to display the response result at T110, it displays the response result screen on the display unit 214 of the management device 200 at T112. The response result screen includes information that associates the device ID "DV1" with the response information "RE1(DV1)". This allows the administrator to know that the printer 10A was returned prematurely because the battery was not installed in the battery mounting section 18 of the printer 10A.

[0075] (Effects of Case A) As shown in Case A, the management device 200 performs an inquiry to find out why the printer 10A was returned early if the difference in usage time of "10 minutes" between the loan date and time "3 / 27 10:00" indicated by the loan date and time information associated with the device ID "DV1" in memory 234 and the return date and time "3 / 27 10:10" when the printer 10A is returned is less than a first predetermined time (T92~T96 in Figure 8). With this configuration, the administrator can find out why the printer 10A was returned early and take measures to prevent the printer 10A from being returned early. Therefore, the administrator can properly manage multiple printers 10.

[0076] Furthermore, if the user requests a different printer 10B than printer 10A after the usage time of "10 minutes" has fallen below the first predetermined time (T50), the management device 200 sends inquiry information to printer 10B (T92). With this configuration, the user can send response information to the inquiry information to the management device 200 by operating printer 10B (T96, T98). Therefore, the likelihood of the management device 200 receiving the response information can be increased.

[0077] Furthermore, if the usage time of "10 minutes" is less than the first predetermined time, the management device 200 sends inquiry information via email to the email address MA1 associated with user ID "DV1" (T70). With this configuration, the user can check the inquiry information using the terminal device 300 or the like that the user uses. Therefore, the user can send response information to the inquiry information to the management device 200 by operating the terminal device 300 or the like. Consequently, the likelihood of the management device 200 receiving the response information can be increased.

[0078] (Effects of this embodiment) According to the above configuration, the management device 200 makes an inquiry to the user (S30 in Figure 3, S124 in Figure 5) when a predetermined condition (usage time is less than the first predetermined time) is met (YES in S70 in Figure 4). Then, when the management device 200 obtains answer information to the inquiry (YES in S140 in Figure 6), it associates the device ID with the answer information and stores it in memory 234 (S142). Then, the management device 200 outputs the device ID and the answer information (T112 in Figure 8). Therefore, an administrator using the management device 200 can check the answers to inquiries related to the lending of the printer 10. Accordingly, the administrator can properly manage multiple printers 10.

[0079] Furthermore, the management device 200 will initiate a query to the user (S30 in Figure 3, S124 in Figure 5) if no error information is received from the printer 10 (NO in S14 in Figure 3, NO in S112 in Figure 5) and the usage time falls below the first predetermined time (YES in S70 in Figure 4). On the other hand, the management device 200 will not initiate a query if error information is received from the printer 10 (YES in S14 in Figure 3, YES in S112 in Figure 5). If error information has already been received from the printer 10, the administrator can find out that an error has occurred in the printer 10 by operating the management device 200. With the above configuration, it is possible to suppress the execution of unnecessary queries. Therefore, user convenience can be improved.

[0080] (Correspondence) Printers 10A to 10C are examples of "multiple mobile devices". Device ID, user ID, and loan date and time information are examples of "device identification information," "user identification information," and "history information," respectively. The device ID, user ID, and loan date and time information in the first device table 240 are examples of "related information." Printer 10A, device ID "DV1," and user ID "U1" are examples of "first mobile device," "first device identification information," and "first user identification information," respectively. The condition that is met when the usage time is less than the first predetermined time is an example of a "predetermined condition." The usage time is an example of the "first difference time." An inquiry to inquire about the reason why printer 10A was returned early is an example of a "predetermined inquiry." The display unit 214 of the management device 200 is an example of an "output unit." The loan date and time "3 / 27 10:00" and the return date and time "3 / 27 10:10" are examples of the "first loan date and time" and the "first return date and time," respectively. Printer 10B is an example of the "third mobile device." Email address MA1 is an example of the "first email address."

[0081] S30 in Figure 3 and S124 in Figure 5 are examples of processes executed by the "Inquiry Unit". S142 in Figure 6 is an example of a process executed by the "Memory Control Unit". T112 in Figure 8 is an example of a process executed by the "Output Control Unit".

[0082] (Second example) The second embodiment differs from the first embodiment in the processing performed in S30 of Figure 3. In the second embodiment, as shown in Figure 1, the web application 138 is already installed on the PC 100. In S30 of Figure 3, the CPU 232 of the management device 200 sends an inquiry signal containing inquiry information to the web application 138 installed on the PC 100 as the destination. When the PC 100 receives an inquiry signal from the management device 200, it displays an inquiry screen. With this configuration, the user can send response information to the inquiry information to the management device 200 by operating the PC 100. Therefore, the likelihood of the management device 200 receiving the response information can be increased.

[0083] (Correspondence) Web application 138 is an example of a "specific application."

[0084] (Third embodiment) The third embodiment differs from the first embodiment in the processing performed at S70 in Figure 4. As shown in Figure 2, the first device table 240 in this embodiment stores the device ID, user ID, loan date and time information, return date and time information, and remaining quantity information in association with each other. The remaining quantity information indicates the remaining quantity of consumables (ink cartridges, toner cartridges, etc.) installed in the printer 10 at the time of loan (hereinafter sometimes referred to as "loaned quantity"). The printer 10 is configured to periodically send a remaining quantity signal to the management device 200, which includes the device ID of the printer 10 and the remaining quantity information of the consumables installed in the printer 10, while the printer 10 is powered on. The management device 200 stores the remaining quantity information in the remaining quantity signal that is first received after the printer 10 is loaned out as remaining quantity information in the first device table 240.

[0085] As shown in Figure 4, in S70, the CPU 232 of the management device 200 determines whether the amount of consumables used in the printer 10 to be returned is below a threshold. The CPU 232 identifies the remaining amount information associated with the device ID to be returned in the first device table 240, and identifies the difference between the loaned amount indicated by the identified remaining amount information and the return amount indicated by the remaining amount information at the time of return as the amount used. The management device 200 identifies the remaining amount information in the last remaining amount signal received from the printer 10 to be returned as the return amount. If the amount used is below the threshold (YES in S70), the CPU 232 proceeds to S80, and if the amount used is above the threshold (NO in S70), the CPU 232 proceeds to S90.

[0086] (Case B; Figures 10 and 11) Next, with reference to Figures 10 and 11, we will describe a specific case B realized by the communication system 2 of this embodiment. The initial state of case B is the same as the initial state of case A in Figure 8. In this case, we assume a situation in which a malfunction occurs in the paper transport of the printer 10A.

[0087] T210~T214 are the same as T10~T14 in Figure 8. At T220, printer 10A receives an operation to turn on the power of printer 10A and, upon receiving a network connection operation (YES at S160 in Figure 7), sends an inquiry request including device ID "DV1" to the management device 200 at T230 (S170).

[0088] When the management device 200 receives an inquiry request from the printer 10A in T230 (YES in S110 in Figure 5), it determines that it has not yet received error information from the printer 10A (NO in S112) and identifies the device ID "DV1" included in the inquiry request (S120). Next, the management device 200 determines that the second device table 242 does not contain the identified device ID "DV1" (YES in S122). In this case, the management device 200 does not send inquiry information.

[0089] Printer 10A transmits a remaining ink level signal to the management device 200 at T232, which includes the device ID "DV1" and the remaining ink level information "80".

[0090] When the management device 200 receives a remaining ink signal from the printer 10A in T232, it stores the remaining ink information "80" in the remaining ink signal in the first device table 240 in T233, associating it with the device ID "DV1". The printer 10A continues to periodically send remaining ink signals to the management device 200 thereafter (see T234).

[0091] As described above, in this case, a malfunction has occurred in the paper transport of printer 10A. Therefore, the user will return printer 10A to storage 70 as soon as possible. In this case, the user will return printer 10A to storage 70 at "3 / 27 10:10".

[0092] T240 and T242 are the same as T30 and T32 in Figure 8. When the management device 200 receives return information from PC 100 in T242 (YES in S50 in Figure 4), it determines in the user table 238 that no inquiry ID is associated with the user ID "U1" to be returned (NO in S52). Next, the management device 200 identifies the loan balance "80" indicated by the remaining balance information associated with the device ID "DV1" to be returned in the first device table 240, and identifies the return balance "78" indicated by the remaining balance information in the last remaining balance signal received from the printer 10A to be returned. Next, the management device 200 determines that the usage amount "2", which is the difference between the loan balance "80" and the return balance "78", is less than a threshold (for example, "10") (YES in S70). In this case, at T250, the management device 200 associates the inquiry ID "IQ2" with the inquiry information "IN2(DV1)" which includes the device ID to be returned "DV1", and stores it in the inquiry table 244 (S222) (see Figure 11). Next, at T252, the management device 200 associates the inquiry ID "IQ2" with the user ID "U1" to be returned and stores it in the user table 238 (S224). T254 is the same as T44 in Figure 8. T260 and T262 are the same as T50 and T52 in Figure 8, respectively.

[0093] Subsequently, the same process as T60 to T112 in Figure 8 is performed between the printer 10B, PC 100, management device 200, and terminal device 300. The inquiry screen 510 displayed at T94 in this case is the same as the inquiry screen displayed at T94 in Case A of Figure 8, except that it includes a message to inquire about the reason why the printer 10's consumable usage was low, and does not include information corresponding to "battery not installed". In addition, at T96 in this case, the user performs the operation to check the checkbox corresponding to "there is a problem with the paper transport for printing" and to select the OK button (YES at S176). Therefore, the response information in this case includes the device ID "DV1" included in the inquiry information "IN2(DV1)", as well as information indicating the response to the inquiry, "there is a problem with the paper transport for printing".

[0094] (Effect of Case B) As shown in Case B, the management device 200 queries the reason why the printer 10A's consumable usage was low when the usage amount "2", which is the difference between the loan balance "80" and the return balance "78" indicated by the loan balance information associated with the device ID "DV1" in memory 234, is less than a threshold (T92-T96 in Figure 8, referenced in Figure 10). With this configuration, the administrator can find out why the printer 10A's consumable usage was low and take measures to prevent the printer 10A from being returned prematurely. Therefore, the administrator can properly manage multiple printers 10.

[0095] (Correspondence) The remaining amount information at the time of lending is an example of "history information." The device ID, user ID, and remaining amount information at the time of lending in the first device table 240 are examples of "related information." The conditions that are met when the usage amount is below a threshold are an example of "predetermined conditions." The usage time is an example of "first differential time." An inquiry to ask why the amount of consumables used by printer 10A was low is an example of "predetermined inquiry." The remaining amount "80" is an example of "first remaining amount."

[0096] (Fourth embodiment) In the fourth embodiment, the CPU 232 of the management device 200 executes the lending process in Figure 12 and the return process in Figure 13, respectively, instead of the lending process in Figure 3 and the return process in Figure 4. As shown in Figure 2, the first device table 240 of this embodiment stores the device ID, user ID, lending date and time information, return date and time information, and previous user ID in association. The previous user ID is information for identifying the user who previously borrowed the printer 10, which is identified by the device ID associated with that previous user ID. The previous user ID is information stored when the printer 10 is returned.

[0097] (Loan processing; Figure 12) Referring to Figure 12, the lending process performed by the CPU 232 of the management device 200 will be described. S210 is the same as S10 in Figure 3.

[0098] In S220, the CPU 232 determines whether the re-lending time is less than a second predetermined time (for example, 10 minutes). First, the CPU 232 determines whether the user ID of the borrowed item is stored in the first device table 240 as the previous user ID. If the user ID of the borrowed item is not stored in the first device table 240 as the previous user ID, the CPU 232 determines NO in S220 and proceeds to S230. On the other hand, if the user ID of the borrowed item is stored in the first device table 240 as the previous user ID, the CPU 232 identifies the return date and time information associated with that previous user ID in the first device table 240. Then, the CPU 232 identifies the difference time between the return date and time indicated by the identified return date and time and the current date and time (i.e., the lending date and time) as the re-lending time. Then, CPU232 proceeds to S222 if the re-lending time is less than the second predetermined time (YES in S220), and to S230 if the re-lending time is equal to or greater than the second predetermined time (NO in S220). S222 and S224 are the same as S80 and S82 in Figure 4, respectively. S230, S240, S242, and S250 are the same as S12, S20, S22, and S30 in Figure 3, respectively.

[0099] (Return process; Figure 13) Referring to Figure 13, the return process performed by the CPU 232 of the management device 200 will be described. S260 to S272 are the same as S50 to S62 in Figure 4. In S280, the CPU 232 updates the first device table 240. The CPU 232 deletes the user ID associated with the device ID to be returned from the first device table 240 and stores the current date and time in the first device table 240 as return date and time information associated with the device ID to be returned. The CPU 232 also stores the user ID to be returned as the previous user ID associated with the device ID to be returned in the first device table 240. When S280 is completed, the CPU 232 terminates the process shown in Figure 13.

[0100] (Case C; Figures 14 and 15) Next, with reference to Figures 14 and 15, a specific case C realized by the communication system 2 of this embodiment will be described. The initial state of case C is the same as the initial state of case A in Figure 8. In this case, we assume a situation where the battery is not installed in the battery mounting section 18 of the printer 10A.

[0101] First, the same process as T10 to T32 in Figure 8 is performed between PC100 and management device 200. Next, at T344, management device 200 deletes the "User ID" associated with the device ID "DV1" to be returned from the first device table 240, and stores the return date and time information "3 / 27 10:10" and the previous user ID "U1" in the first device table 240, associating them with device ID "DV1" (S280 in Figure 13). T350 and T352 are the same as T50 and T52 in Figure 8, respectively.

[0102] When the management device 200 receives loan information from the PC 100 at T352 (YES at S210 in Figure 12), it determines that the user ID "U1" of the loaned item is stored in the first device table 240 as the previous user ID "U1", and identifies the return date and time information associated with the previous user ID "U1" in the first device table 240. Next, the management device 200 identifies the difference time between the return date and time "3 / 27 10:10" indicated by the return date and time information and the current date and time (i.e., loan date and time) "3 / 27 10:15" as the re-loan time "5 minutes", and determines that the re-loan time "5 minutes" is less than the second predetermined time (YES at S220). In this case, at T360, the management device 200 associates the inquiry ID "IQ3" with the inquiry information "IN3(DV1)" which includes the device ID "DV1" to be returned, and stores it in the inquiry table 244 (S222) (see Figure 15). Next, at T362, the management device 200 associates the inquiry ID "IQ3" with the user ID "U1" to be returned and stores it in the user table 238 (S224) (see Figure 15). T370 is the same as T54 in Figure 8. T372 is the same as T60 in Figure 8, except that the inquiry ID "IQ3" is stored in the second device table 242 (see Figure 15). Subsequently, the same processing as T70 to T112 in Figure 8 is performed between the printer 10B, PC 100, management device 200, and terminal device 300. The inquiry screen 520 displayed at T94 in this case is the same as the inquiry screen displayed at T94 in Case A of Figure 8, except that it includes a message to inquire about the reason why a new printer 10B was loaned out earlier than printer 10A.

[0103] (Effect of Case C) As shown in Case C, if the re-lending time of "5 minutes," which is the difference between the return date and time "3 / 27 10:10" indicated by the return date and time information associated with the device ID "DV1" in memory 234 and the lending date and time "3 / 27 10:15," is less than a second predetermined time, the management device 200 executes an inquiry to inquire about the reason why a new printer 10B was lent out earlier than printer 10A (T92-T96 in Figure 8, which is referenced in Figure 14). With this configuration, the administrator can find out the reason why a new printer 10B was lent out earlier than printer 10A, i.e., the reason why printer 10A was returned, and take action to ensure that printer 10A is available for use. Therefore, the administrator can properly manage multiple printers 10.

[0104] (Correspondence) The date and time information at the time of return is an example of "history information". The device ID, user ID, and date and time information at the time of return in the first device table 240 are examples of "related information". The conditions that are met when the re-lending time is less than the second predetermined time are an example of "predetermined conditions". The re-lending time is an example of "second differential time". An inquiry to find out why a new printer 10B was lent out earlier than printer 10A is an example of a "predetermined inquiry". The return date and time "3 / 27 10:10" and the lending date and time "3 / 27 10:15" are examples of "second return date and time" and "second lending date and time", respectively.

[0105] (Fifth example) In the fifth embodiment, the CPU 232 of the management device 200 executes the determination process shown in Figure 16. As shown in Figure 2, the first device table 240 of this embodiment stores the device ID, user ID, loan date and time information, return date and time information, loan count information, and past user IDs in association with each other. The loan count information indicates the number of times the printer 10 has been loaned out during a predetermined period (for example, one month) (hereinafter sometimes referred to as "loan count"). The past user ID indicates the user who has borrowed the printer 10 during a predetermined period (for example, one month).

[0106] (Decision process; Figure 16) Referring to Figure 16, the determination process executed by the CPU 232 of the management device 200 will be described. The CPU 232 executes the process shown in Figure 16 at a predetermined timing. In this embodiment, the predetermined timing is the timing when a predetermined period (for example, one month) has elapsed since the determination process was last executed.

[0107] In S310, CPU232 identifies one device ID (hereinafter sometimes referred to as "target device ID") from among one or more device IDs in the first device table 240.

[0108] In S320, CPU232 determines whether the number of loans is less than a predetermined number (for example, 3 times). CPU232 identifies the number of loans indicated by the loan count information associated with the target device ID in the first device table 240 and determines whether the identified number of loans is less than a predetermined number (for example, 3 times). If CPU232 determines that the number of loans is less than the predetermined number (YES in S320), it proceeds to S330; if the number of loans is equal to or greater than the predetermined number (NO in S320), it proceeds to S340.

[0109] In S330, CPU232 identifies one or more past user IDs associated with the target device ID in the first device table 240.

[0110] In S332, CPU232 identifies one or more email addresses associated with each of the one or more past user IDs identified in S330 in the user table 238. Next, CPU232 generates inquiry information including the target device ID and an inquiry related to the loan of printer 10 identified by the target device ID. Next, CPU232 sends one or more emails containing the generated inquiry information and the one or more identified email addresses as the recipient email addresses. When the email is opened by the user who received it, the inquiry screen 530 in Figure 17 is displayed. The inquiry screen 530 is the same as the inquiry screen displayed in T94 of Case A in Figure 8, except that it includes a message for inquiring about the reason why printer 10A has been loaned out infrequently.

[0111] In S340 of Figure 16, the CPU 232 determines whether the processes in S320 to S332 have been executed for all device IDs in the first device table 240. If the CPU 232 determines that the processes have been executed for all device IDs (YES in S340), it terminates the process in Figure 16. If it determines that the processes have not been executed for all device IDs (NO in S340), it returns to S310. When the CPU 232 terminates the process in Figure 16, it changes all loan count information in the first device table 240 to "0" and deletes past user IDs from the first device table 240.

[0112] (Effects of this embodiment) As described above, the management device 200, at a predetermined timing, if the number of times the printer 10 has been borrowed, as indicated by the count information associated with the device ID in memory 234, is less than a predetermined number (YES in S320 of Figure 16), executes a query to inquire about the reason why the printer 10 has been borrowed so few times (S332). With this configuration, the administrator can find out why the printer 10 has been borrowed so few times and take action to ensure that the printer 10A is used. Therefore, the administrator can properly manage multiple printers 10.

[0113] Furthermore, if two or more user IDs are associated with the target device ID, the management device 200, in memory 234, queries each of the two or more users identified by the two or more user IDs to inquire about the reason why the printer 10 has been borrowed so few times (S332). With this configuration, the management device 200 can receive two or more response pieces of information. Therefore, it can take more appropriate action to ensure that the printer 10A is used.

[0114] (Correspondence) The number of times an item has been borrowed is an example of "history information." The device ID, user ID, and the number of times an item has been borrowed at the time of borrowing in the first device table 240 are examples of "related information." The conditions that are met when the number of times an item has been borrowed is less than a predetermined number are an example of "predetermined conditions." An inquiry to find out why the printer 10 has been borrowed so few times is an example of a "predetermined inquiry." S332 in Figure 16 is an example of the process executed by the "inquiry unit."

[0115] Although specific examples of the present invention have been described in detail above, these are merely illustrative and do not limit the scope of the claims. The technology described in the claims includes various modifications and changes to the specific examples illustrated above. Modifications of the above embodiments are listed below.

[0116] (First variation) The “mobile device” is not limited to the printer 10, but may also be a portable mobile scanner, a mobile terminal, etc.

[0117] (Second Modification) When the management device 200 is a server, the management device 200 may send the response result screen data to the PC used by the administrator via the communication interface when it receives a request for result information from the PC. In this modification, the communication interface is an example of an "output unit".

[0118] (Third Modification) In the first and third embodiments, past user IDs may be stored in the first device table 240. In this case, the CPU 232 of the management device 200 sends one or more emails containing inquiry information in S30 of Figure 3.

[0119] (Fourth Modification) In the first and third embodiments, the CPU 232 of the management device 200 may, at S30 in Figure 3, send an email containing inquiry information and also send an inquiry signal containing inquiry information to the Web application 138 installed on the PC 100, with the Web application 138 already installed on the PC 100 as the destination.

[0120] (Fifth Modification) In the first to third embodiments, S30 in Figure 3 can be omitted. In another modification, in the first to third embodiments, the inquiry transmission process in Figure 5 can be omitted. In yet another modification, in the fourth embodiment, either S250 in Figure 12 or the inquiry transmission process in Figure 5 can be omitted.

[0121] (Sixth Modification) The printer 10 does not need to be able to detect its own errors. In this modification, steps S180 and S182 in Figure 7 can be omitted. In this modification, the "error information receiving unit" can be omitted.

[0122] (Seventh Modification) In each of the above embodiments, the processes shown in Figures 3 to 8, 10, 12 to 14, and 16 are implemented by software (for example, programs 36 and 236), but at least one of these processes may be implemented by hardware such as a logic circuit.

[0123] Furthermore, the technical elements described herein or in the drawings demonstrate technical usefulness individually or in various combinations, and are not limited to the combinations described in the claims at the time of filing. In addition, the technologies illustrated herein or in the drawings achieve multiple objectives simultaneously, and achieving even one of these objectives constitutes technical usefulness in itself. [Explanation of symbols]

[0124] 2: Communication system, 10A~10C: Mobile printer, 12: Operation unit, 14: Display unit, 16: Print execution unit, 18: Battery mounting unit, 20: Communication I / F, 30: Control unit, 32: CPU, 34: Memory, 36: Program, 60: Facility, 70: Storage unit, 100: PC, 110: Reader, 138: Web application, 200: Management device, 212: Operation unit, 214: Display unit, 220: Communication I / F, 230: Control unit, 232: CPU, 234: Memory, 236: Program, 238: User table, 240: First device table, 242: Second device table, 244: Inquiry table, 246: Answer table, 300: Terminal device

Claims

1. A management device for managing the lending and return of multiple mobile devices, A memory capable of storing multiple pieces of related information corresponding to the multiple mobile devices, wherein each of the multiple pieces of related information is information associated with device identification information that identifies the corresponding mobile device, user identification information that identifies the user who borrowed the corresponding mobile device, and history information related to the borrowing and / or return of the corresponding mobile device, Based on the first related information corresponding to the first mobile device among the plurality of related information, if predetermined conditions related to lending the first mobile device are met, an inquiry unit executes a predetermined inquiry related to lending the first mobile device to the first user identified by the first user identification information included in the first related information. When response information to the predetermined inquiry is obtained, a storage control unit associates the first device identification information that identifies the first mobile device with the response information and stores it in the memory, After the first device identification information and the response information are associated and stored in the memory, an output control unit causes the first device identification information and the response information to be output to the output unit, A control device equipped with the following features.

2. The history information in the memory includes loan date and time information indicating the most recent loan date and time when the mobile device identified by the device identification information associated with the history information was loaned out. The predetermined condition is satisfied when the first difference time between the first loan date and time indicated by the first loan date and time information associated with the first device identification information in the memory and the first return date and time when the first mobile device is returned after the first loan date and time is less than the first predetermined time. The management device according to claim 1, wherein the predetermined inquiry is an inquiry for the reason why the first mobile device was returned prematurely.

3. The aforementioned control device further, The system includes a remaining quantity information receiving unit that receives remaining quantity information indicating the remaining quantity of consumables installed in a mobile device that is currently on loan. The history information in the memory includes loan remaining amount information indicating the remaining amount of consumables installed in the mobile device identified by the device identification information associated with the history information at the time of loan, The predetermined condition is satisfied when the difference between the first loan balance information associated with the first device identification information in the memory, which indicates the remaining amount of the first consumables installed in the first mobile device at the time of loan, and the remaining amount of the first consumables to be returned at the time of return of the first mobile device is less than a threshold, The management device according to claim 1, wherein the predetermined inquiry is an inquiry for the reason why the amount of the first consumable attached to the first mobile device is small.

4. The history information in the memory includes return date and time information indicating the most recent return date and time when a mobile device identified by the device identification information associated with the history information was returned, The predetermined condition is satisfied when the second difference time between the second return date and time indicated by the first return date and time information associated with the first user identification information in the memory and the second loan date and time when the first user borrowed a second mobile device different from the first mobile device is less than the second predetermined time. The management device according to claim 1, wherein the predetermined inquiry is an inquiry for the reason why the second mobile device was lent out earlier than the first mobile device.

5. The history information in the memory includes count information indicating the number of times a mobile device identified by the device identification information associated with the history information has been loaned out during a predetermined period. The predetermined condition is satisfied when the first number of loans indicated by the first number of loans information associated with the first device identification information at a predetermined timing is less than the predetermined number of loans. The management device according to claim 1, wherein the predetermined inquiry is an inquiry for the reason why the first mobile device has been borrowed infrequently.

6. The aforementioned inquiry section, The management device according to claim 1, wherein, after the predetermined conditions are met based on the first related information, the first user borrows a third mobile device different from the first mobile device, and the management device transmits inquiry information indicating the predetermined inquiry to the third mobile device.

7. Each of the aforementioned multiple pieces of related information in the memory is further associated with two or more pieces of user identification information that identify each of two or more users who have previously borrowed the corresponding mobile device. The aforementioned inquiry section, The management device according to claim 1, wherein, when the predetermined conditions are met based on the first related information, the predetermined inquiry is performed for each of the two or more users identified by the two or more user identification pieces of information included in the first related information.

8. The memory further stores, in association with each of the one or more user identification pieces, the email address of the user identified by that user identification piece. The aforementioned inquiry section, The management device according to claim 1, wherein, when the predetermined conditions are met based on the first related information, it transmits inquiry information indicating the predetermined inquiry to a first email address associated with the first user identification information included in the first related information as the recipient.

9. The aforementioned inquiry section, The management device according to claim 1, wherein, when the predetermined conditions are met based on the first related information, it transmits inquiry information indicating the predetermined inquiry to a specific application program already installed on an external device available to the first user as the destination.

10. The aforementioned control device further, The system includes an error information receiving unit that receives error information from the first mobile device indicating that the first mobile device is in an error state. The aforementioned inquiry section, If the error information is not received from the first mobile device and the predetermined conditions are met based on the first related information, the predetermined inquiry is made to the first user. The management device according to any one of claims 1 to 9, wherein when the error information is received from the first mobile device, the predetermined inquiry is not performed.

11. A computer program for a management device, The management device comprises a memory capable of storing a plurality of related pieces of information corresponding to the plurality of mobile devices, wherein each of the plurality of related pieces of information is information associated with a device identification information that identifies the corresponding mobile device, a user identification information that identifies the user who borrowed the corresponding mobile device, and history information related to the borrowing and / or return of the corresponding mobile device. The aforementioned computer program controls the computer of the management device, Based on the first related information corresponding to the first mobile device among the plurality of related information, if predetermined conditions related to lending the first mobile device are met, an inquiry unit executes a predetermined inquiry related to lending the first mobile device to the first user identified by the first user identification information included in the first related information. When response information to the predetermined inquiry is obtained, a storage control unit associates the first device identification information that identifies the first mobile device with the response information and stores it in the memory, After the first device identification information and the response information are associated and stored in the memory, an output control unit causes the first device identification information and the response information to be output to the output unit, A computer program that functions as such.

12. A method performed by a management device, The management device comprises a memory capable of storing a plurality of related pieces of information corresponding to the plurality of mobile devices, wherein each of the plurality of related pieces of information is information associated with a device identification information that identifies the corresponding mobile device, a user identification information that identifies the user who borrowed the corresponding mobile device, and history information related to the borrowing and / or return of the corresponding mobile device. The aforementioned method, An inquiry step in which, based on the first related information corresponding to the first mobile device among the plurality of related information, if predetermined conditions related to lending the first mobile device are met, a predetermined inquiry related to lending the first mobile device is made to the first user identified by the first user identification information included in the first related information. When response information to the predetermined inquiry is obtained, a storage control step is performed to associate the first device identification information that identifies the first mobile device with the response information and store it in the memory. After the first device identification information and the response information are associated and stored in the memory, an output control step is performed to cause the first device identification information and the response information to be output to the output unit. A method that includes [a certain feature].

Images