Function execution device, computer program for function execution device, and method for controlling function execution device

The function execution device prioritizes log storage and security by distinguishing between encrypted and non-encrypted communication paths, enabling efficient monitoring and reducing risks in log management systems.

JP2024158280APending Publication Date: 2024-11-08BROTHER KOGYO KK
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
JP2023073355
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Filing Date
2023-04-27
Publication Date
2024-11-08

AI Technical Summary

Technical Problem

Existing log management systems in function execution devices do not adequately differentiate between encrypted and non-encrypted communication logs, making it difficult for administrators to efficiently monitor and manage security and operational events.

Method used

Implementing a function execution device with separate communication paths for encrypted and non-encrypted communication, prioritizing the storage of log information based on the type of communication, ensuring that logs from non-encrypted scans are given higher priority for monitoring, and enhancing security by preventing unauthorized access to authentication information.

Benefits of technology

Improves administrative convenience by allowing administrators to effectively track and manage non-encrypted communication events, thereby enhancing security and reducing the risk of unauthorized data access.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2024158280000001_ABST
    Figure 2024158280000001_ABST
Patent Text Reader

Abstract

To provide a technique that can improve convenience for an administrator of a function execution device.SOLUTION: A function execution device includes: a function execution engine; a first receiving unit that receives a first function execution instruction from an external device via a first communication path for executing encrypted communication; a first engine control unit that causes the function execution engine to execute a predetermined function that is in accordance with the first function execution instruction; a second receiving unit that receives a second function execution instruction from the external device via a second communication path for executing unencrypted communication; a second engine control unit that causes the function execution engine to execute the predetermined function that is in accordance with the second function execution instruction; and a storage control unit that stores second log information indicating that the predetermined function that is in accordance with the second function execution instruction has been executed in a predetermined memory preferentially than first log information indicating that the predetermined function that is in accordance with the first function execution instruction has been executed.SELECTED DRAWING: Figure 3
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] This specification discloses a technique for managing log information. [Background technology]

[0002] Patent Document 1 discloses an image processing device that scans an original. When the image processing device receives a scan start request from a processing terminal, the image processing device scans the original and generates scan data. The scan data is transmitted from the image processing device to the processing terminal or a cloud storage service. [Prior art documents] [Patent documents]

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

[0004] This specification provides a technique that can improve convenience for administrators of function executing devices. [Means for solving the problem]

[0005] A function execution device disclosed in this specification may include a function execution engine, a first receiving unit that receives a first function execution instruction from an external device via a first communication path for performing encrypted communication, a first engine control unit that causes the function execution engine to execute a predetermined function in accordance with the first function execution instruction when the first function execution instruction is received from the external device, a second receiving unit that receives a second function execution instruction from the external device via a second communication path for performing unencrypted communication, a second engine control unit that causes the function execution engine to execute the predetermined function in accordance with the second function execution instruction when the second function execution instruction is received from the external device, and a storage control unit that preferentially stores second log information indicating that the predetermined function has been executed in accordance with the second function execution instruction in a predetermined memory over first log information indicating that the predetermined function has been executed in accordance with the first function execution instruction.

[0006] According to the above configuration, the function executing device preferentially stores in a predetermined memory the second log information indicating that a predetermined function has been executed in accordance with a second function execution instruction via a second communication path for executing unencrypted communication. Therefore, the administrator of the function executing device can properly grasp the second log information. This can improve the convenience of the administrator.

[0007] A computer program for implementing the above-mentioned function-performing apparatus, a computer-readable recording medium for storing the computer program, and a method for controlling the function-performing apparatus are also novel and useful. [Brief description of the drawings]

[0008] [Figure 1] FIG. 1 is a configuration diagram of a communication system. [Diagram 2] 11A to 11C are diagrams showing the contents of each setting value, table, and list. [Diagram 3] 11 is a flowchart of a process executed by the multi-function device. [Figure 4] 13 is a flowchart of an encryption scan process. [Diagram 5] 13 is a flowchart of a plain text scanning process. [Figure 6] FIG. 11 is a sequence diagram of case A in the first embodiment. [Figure 7] FIG. 11 is a sequence diagram of cases B and C in the first embodiment. [Figure 8] FIG. 11 is a sequence diagram of case D in the first embodiment. [Figure 9] FIG. 11 is a sequence diagram of cases E and F in the second embodiment. [Figure 10] FIG. 13 is a sequence diagram of cases G and H in the third embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] (First embodiment) (Configuration of communication system 2; Figure 1) As shown in FIG. 1, the communication system 2 includes a plurality of terminals 10A to 10C, a multi-function device 100, and a server 200. The devices 10A to 10C, 100 are connected to a Local Area Network (LAN) 4. The devices 10A to 10C, 100 can communicate with each other via the LAN 4. The LAN 4 may be a wired LAN or a wireless LAN. The server 200 is connected to the Internet 6. The LAN 4 is connected to the Internet 6. Therefore, the devices 10A to 10C, 100 can communicate with the server 200 via the LAN 4 and the Internet 6.

[0010] (Configuration of terminal 10A) The terminal 10A is a portable terminal device such as a mobile phone, a smartphone, a PDA, or a tablet PC. In a modified example, the terminal 10A may be a stationary PC, a laptop PC, or the like. The terminal 10A is a terminal used by a user X of the multi-function device 100. The terminal 10A supports a predetermined encryption protocol. That is, the terminal 10A can communicate data encrypted by the predetermined encryption protocol with the multi-function device 100. The terminal 10A includes an operation unit 12, a display unit 14, a communication interface 16, and a control unit 30. Each unit 12 to 30 is connected to a bus line. In the following, the interface is referred to as "I / F".

[0011] The operation unit 12 is an I / F that allows a user to input various information to the terminal 10A, and includes, for example, a touch screen and buttons. The user can input various information to the terminal 10A via the operation unit 12. The display unit 14 is a display for displaying various information. The communication I / F 16 is connected to the LAN 4.

[0012] The control unit 30 includes a CPU 32 and a memory 34. The memory 34 stores an OS program 36 and an application program 38. The CPU 32 executes various processes in accordance with the OS program 36 and the application program 38. The memory 34 is, for example, a ROM or a RAM. Hereinafter, the OS program will be simply referred to as "OS." Also, the application program will be simply referred to as "app."

[0013] The OS 36 controls the basic operations of the terminal 10A. The application 38 is a program for causing the multi-function device 100 to execute functions such as scanning and printing. The application 38 is downloaded from a server on the Internet provided by the vendor of the multi-function device 100, for example, and installed in the terminal 10A.

[0014] (Configuration of terminal 10B) The terminal 10B is a terminal used by a user Y of the multi-function device 100. The configuration of the terminal 10B is similar to that of the terminal 10A, except that the terminal 10B does not support the above-mentioned predetermined encryption protocol. The terminal 10B cannot communicate encrypted data with the multi-function device 100, but can communicate unencrypted data (hereinafter referred to as "plain data") with the multi-function device 100.

[0015] (Configuration of terminal 10C) The terminal 10C is a terminal used by a user Z (a so-called public user) who is not a user of the multi-function device 100. The configuration of the terminal 10C is similar to the configuration of the terminal 10B. That is, the terminal 10C does not support the above-mentioned predetermined encryption protocol.

[0016] (Configuration of multi-function device 100) The multi-function device 100 is a peripheral device capable of performing multiple functions such as a scan function, a print function, a copy function, a facsimile function, etc., such as a peripheral device for the terminals 10A to 10C. The multi-function device 100 supports the above-mentioned predetermined encryption protocol.

[0017] The multi-function device 100 includes an operation unit 112, a display unit 114, a communication I / F 116, a scan engine 118, a print engine 120, and a control unit 130. Each unit 112 to 130 is connected to a bus line. The operation unit 112 is an I / F that allows a user to input various information to the multi-function device 100, and includes, for example, a touch screen and buttons. The user can input various information to the multi-function device 100 via the operation unit 112. The display unit 114 is a display for displaying various information. The scan engine 118 includes, for example, a CCD type or CIS type scan mechanism. The print engine 120 includes, for example, an inkjet type, laser type, or thermal type print mechanism.

[0018] The communication I / F 116 is connected to the LAN 4. The communication I / F 116 includes an encryption port for communication of encrypted data and a plaintext port for communication of plaintext data. That is, the multi-function device 100 has a communication path for performing encrypted communication (i.e., a communication path with the encryption port as a destination) and a communication path for performing unencrypted communication (i.e., a communication path with the plaintext port as a destination). When the power supply of the multi-function device 100 is ON, the multi-function device 100 is controlled to a state in which communication using the encryption port can be performed. Hereinafter, such a state is expressed as "opening the encryption port". Also, the multi-function device 100 is controlled to either a state in which communication using the plaintext port can be performed or a state in which communication using the plaintext port cannot be performed according to a plaintext setting value 140 described later. Hereinafter, the former state is expressed as "opening the plaintext port" and the latter state is expressed as "closing the plaintext port". In addition, in a modified example, the encrypted communication and the unencrypted communication may be performed on the same port.

[0019] The control unit 130 includes a CPU 132 and a memory 134. The CPU 132 executes various processes in accordance with a program 136 stored in the memory 134. The memory 134 further stores a plaintext setting value 140, an authentication setting value 142, an authentication table 144, a priority table 146, and a priority setting value 148.

[0020] The plaintext setting value 140 indicates either "ON" corresponding to opening the plaintext port or "OFF" corresponding to closing the plaintext port. The authentication setting value 142 indicates either "ON" corresponding to the necessity of user authentication to execute a function of the multi-function device 100 (e.g., a scan function) or "OFF" corresponding to the necessity of user authentication. Details of the authentication table 144, the priority table 146, and the priority setting value 148 will be described later with reference to FIG. 2. Each of the setting values ​​140, 142, 148 and each of the tables 144, 146 can be specified by an administrator of the multi-function device 100.

[0021] (Configuration of Server 200) The server 200 manages log information indicating logs related to events (e.g., scanning, printing) that have occurred in the multi-function device 100. The server 200 includes a communication I / F 216 and a control unit 230. The units 216 and 230 are connected to a bus line. The communication I / F 216 is connected to the Internet 6.

[0022] The control unit 230 includes a CPU 232 and a memory 234. The CPU 232 executes various processes in accordance with a program 236 stored in the memory 234. The memory 234 further stores a log information list 238. Details of the log information list 238 will be described later with reference to FIG.

[0023] (Tables, settings, and list contents; Figure 2) Next, the contents of the tables 144, 146, the priority setting value 148, and the log information list 238 will be described with reference to FIG.

[0024] The authentication table 144 is a table that stores a user ID, a password, and a permission setting value for each function in association with each other. In this embodiment, the user ID and password of the user X of the terminal 10A and the user Y of the terminal 10B are registered (i.e., stored) in the authentication table 144. On the other hand, the user ID and password of the user Z of the terminal 10C are not registered in the authentication table 144. Here, the "permission setting value for each function" is a setting value indicating whether or not to permit execution of each function (e.g., a scan function, a print function, a copy function) that the multi-function device 100 can execute, and indicates either "permission" or "not permission." In particular, the user ID "Public" is a setting value indicating whether or not to permit execution of each function for a public user who is not an individual user of the multi-function device 100 (i.e., an individual user who has been registered in the authentication table 144). Therefore, in the authentication table 144, the user ID "Public" is not associated with a password. In other words, each permission setting value of each function associated with the user ID "Public" can be said to be information indicating whether or not execution of the function is permitted without executing user authentication.

[0025] The priority table 146 is a table that stores the event name of an event that occurs in the multi-function device 100 in association with a priority for storing log information indicating the occurrence of the event in the server 200. Here, the event name "encrypted scan" indicates that the multi-function device 100 executes a scan in accordance with communication via an encrypted port. The event name "plaintext scan" indicates that the multi-function device 100 executes a scan in accordance with communication via a plaintext port. The priority indicates the priority of the log information. In this embodiment, the priority is one of "high", "medium", and "low". The event name "encrypted scan" is associated with the priority "low", and the event name "plaintext scan" is associated with the priority "high". In a modified example, the priority may be, for example, a severity level defined in syslog.

[0026] Here, the reason why the priority associated with the event name "plaintext scan" is higher than the priority associated with the event name "encrypted scan" will be explained. For example, when the administrator of the multi-function device 100 finds a security vulnerability of the multi-function device 100, it is necessary to check whether or not there is information illegally obtained by a third party. At this time, the administrator checks the log information stored in the server 200. In the encrypted scan, the information communicated is encrypted. Therefore, even if information related to the encrypted scan (e.g., scan data) is leaked to the outside, problems are unlikely to occur. On the other hand, if information related to the plaintext scan is leaked to the outside, for example, the contents of the original document from which the scan data is based may be obtained by a third party. For this reason, the administrator should give priority to checking the log information of the plaintext scan. Therefore, the priority of the "plaintext scan" is set higher than the priority of the "encrypted scan". As a result, the convenience of the administrator when checking the log information is improved.

[0027] The priority setting value 148 is a setting value that specifies which priority of log information should be sent to the server 200. In this embodiment, the priority setting value 148 indicates any one of (1) OFF, (2) recording log information of "high" priority, (3) recording log information of "high" and "medium" priority, and (4) recording all log information. "(1) OFF" means that log information of any priority is not sent to the server 200. "(2) Recording log information of "high" priority" means that log information of "high" priority is sent to the server 200, and log information of "medium" or "low" priority is not sent to the server 200. "(3) Recording log information of "high" and "medium" priority" means that log information of "high" or "medium" priority is sent to the server 200, and log information of "low" priority is not sent to the server 200. "(4) Recording all log information" means that log information of any priority is sent to the server 200.

[0028] The log information list 238 is a list for storing log information received from a device (e.g., the multi-function device 100), and stores an event name, a time, a device name, and a SourceIP in association with each other. The time indicates the time when the event occurred in the device. The device name indicates the name of the device where the event occurred. The SourceIP indicates the IP address of the device (e.g., the terminal 10A, etc.) that sent the instruction that triggered the event.

[0029] (Scanning process on a multifunction device; Figure 3) Next, a scan process that is realized by the CPU 132 of the multi-function device 100 executing the program 136 will be described with reference to Fig. 3. The process in Fig. 3 is started when the power of the multi-function device 100 is turned ON.

[0030] In S10, the CPU 132 opens an encrypted port. When the encrypted port is opened, the multi-function device 100 is in a state in which it can receive signals via a communication path for performing encrypted communication according to the above-mentioned predetermined encryption protocol. The protocol used by the encrypted port is, for example, Hypertext Transfer Protocol Secure (HTTPS), and the port number is 443.

[0031] In S12, the CPU 132 determines whether the plaintext setting value 140 in the memory 134 indicates "ON" or "OFF." If the plaintext setting value 140 indicates "ON" (YES in S12), the CPU 132 proceeds to S14, and if the plaintext setting value 140 indicates "OFF" (NO in S12), the CPU 132 skips S14 and proceeds to S20.

[0032] In S14, the CPU 132 opens the plaintext port. When the multi-function device 100 opens the plaintext port, the multi-function device 100 is in a state in which it can receive signals via a communication path for performing unencrypted communication. The protocol used by the plaintext port is, for example, Hypertext Transfer Protocol (HTTP), and the port number is 80.

[0033] In S20, the CPU 132 monitors whether a connection instruction is received from a terminal (for example, the terminal 10A). The connection instruction is a command that instructs the multi-function device 100 to establish a communication session for performing various communications for scanning. When the CPU 132 receives a connection instruction from a terminal, the CPU 132 determines YES in S20 and proceeds to S22. Hereinafter, the terminal that is the source of the connection instruction is referred to as the "target terminal." In addition, in this embodiment, the CPU 132 receives a connection instruction from the target terminal via either an encryption port or a plaintext port. In particular, a connection instruction via an encryption port includes encrypted information, and a connection instruction via a plaintext port includes unencrypted information. The same applies to various communications described below.

[0034] In S22, the CPU 132 judges whether or not a scan process is being executed. Although details will be described later, when the multi-function device 100 receives a connection instruction from the target terminal and establishes a communication session with the target terminal, it executes various communications using the communication session to execute scanning of the document. Then, the multi-function device 100 transmits scan data generated by scanning the document to the target terminal using the above-mentioned communication session. The "scan process" in S22 means a series of processes from receiving a connection instruction to transmitting scan data. That is, in S22, if the first connection instruction is received before the second connection instruction received in S20 and scan data has not yet been transmitted in response to the first connection instruction and the subsequent scan execution instruction, the CPU 132 judges that a scan process is being executed (YES in S22) and proceeds to S24. On the other hand, if the CPU 132 judges that a scan process is not being executed (NO in S22), it proceeds to S26.

[0035] In S24, the CPU 132 transmits a busy response indicating that the scan process is being executed to the target terminal. As a result, information indicating that the multi-function device 100 is busy is displayed on the target terminal, so that the user of the target terminal can know that the multi-function device 100 cannot execute a scan because the multi-function device 100 is busy. When the process of S24 ends, the CPU 132 returns to the monitoring process of S20 again.

[0036] In S26, CPU 132 determines whether the connection instruction received in S20 was received via an encrypted port or a plaintext port. If the connection instruction was received via an encrypted port (YES in S26), CPU 132 proceeds to S30, and if the connection instruction was received via a plaintext port (NO in S26), CPU 132 proceeds to S40.

[0037] In S30, the CPU 132 executes encrypted scan processing. The encrypted scan processing is a scan processing including encrypted communication.

[0038] In S40, the CPU 132 executes a plaintext scan process. The plaintext scan process is a scan process that does not include encrypted communication.

[0039] In S42, CPU 132 identifies the priority of the event that has occurred (i.e., in this embodiment, "encrypted scan" or "plain text scan") from priority table 146. If CPU 132 determines that no event has occurred (for example, if S140 in FIG. 4 described below has been executed, or S240 in FIG. 5 has been executed), CPU 132 does not execute the processes in S44 and onward, and returns to the monitoring process in S20.

[0040] In S44, the CPU 132 judges whether or not the log information of the occurring event should be transmitted. Specifically, the CPU 132 compares the priority of the occurring event with the priority setting value 148 in the memory 134 to judge whether or not the log information of the occurring event should be transmitted. For example, when the priority setting value 148 indicates "(2) Record log information of "high" priority", the CPU 132 judges that the log information should be transmitted if the priority of the occurring event is "high" (YES in S44), and judges that the log information should not be transmitted if the priority of the occurring event is "medium" or "low" (NO in S44). When the CPU 132 judges YES in S44, it proceeds to S46, and when the CPU 132 judges NO in S44, it returns to the monitoring process of S20 without executing the process of S46.

[0041] In S46, the CPU 132 transmits log information of the occurring event to the server 200 via the communication I / F 116. The log information includes an event name, a current time, a device name of the multi-function device 100, and an IP address of the target terminal. The IP address of the target terminal is, for example, a source IP address included in the connection instruction of S20. When S46 is executed, the log information is stored by the server 200. When the process of S46 ends, the CPU 132 returns to the monitoring process of S20. In a modified example, when YES is determined in S44, the log information may be stored in the memory 134 of the multi-function device 100 in S46 without transmitting the log information to the server 200. Then, when a trigger for transmitting the log information to the server 200 occurs (for example, the arrival of a predetermined timing, storage of a predetermined number of log information), the CPU 132 may transmit the log information stored in the memory 134 to the server 200.

[0042] (Encryption scanning process; Figure 4) Next, the encryption scan process of S30 in Fig. 3 will be described with reference to Fig. 4. In S110, the CPU 132 transmits a connection OK response to the target terminal. As a result, a communication session is established between the target terminal and the multi-function device 100. This communication session is a communication session for performing encrypted communication, and information included in various communications using this communication session is encrypted. For this reason, the security of the communication between the target terminal and the multi-function device 100 is high.

[0043] In S112, the CPU 132 receives a capability information request from the target terminal using the communication session. The capability information request is a signal requesting transmission of capability information indicating the capabilities of the multi-function device 100, in particular capabilities related to the scan function of the multi-function device 100 (e.g., resolution, whether color scanning can be performed, scannable document size, etc.).

[0044] In S114, the CPU 132 uses the communication session to transmit the capability information to the target terminal. As a result, the capability information is displayed on the target terminal, so that the user of the target terminal can know the capabilities of the multi-function device 100, in particular the capabilities related to the scan function of the multi-function device 100. In addition, the user can specify scan settings (e.g., resolution, color scan or monochrome scan, document size, etc.).

[0045] In S116, the CPU 132 receives a scan execution instruction from the target terminal using the communication session. The scan execution instruction is a signal that requests the multi-function device 100 to start scanning a document.

[0046] In S120, the CPU 132 determines whether the authentication setting value 142 in the memory 134 indicates "ON" or "OFF." If the authentication setting value 142 indicates "ON" (YES in S120), the CPU 132 proceeds to S122, and if the authentication setting value 142 indicates "OFF" (NO in S120), the CPU 132 skips S122 to S132 and proceeds to S134. In this way, the multi-function device 100 can switch between performing authentication or not, depending on the value of the authentication setting value 142.

[0047] In S122, CPU 132 determines whether the permission setting value of the scan function associated with user ID "Public" in authentication table 144 in memory 134 indicates "permitted" or "not permitted." If the permission setting value indicates "permitted" (YES in S122), CPU 132 skips S124 to S132 and proceeds to S134, and if the permission setting value indicates "not permitted" (NO in S122), proceeds to S124.

[0048] In S124, the CPU 132 uses the communication session to transmit an authentication information request to the target terminal. The authentication information request is a signal requesting transmission of authentication information (i.e., a user ID and a password). As a result, an input screen for inputting the authentication information is displayed on the target terminal. When the user of the target terminal inputs the authentication information on the input screen, a scan execution instruction including the input authentication information, more precisely, a scan execution instruction including authentication information obtained by encrypting the input authentication information, is transmitted from the target terminal to the multi-function device 100.

[0049] In S126, CPU 132 determines whether a scan execution instruction including authentication information has been received from the target terminal. Specifically, CPU 132 decrypts information included in the scan execution instruction received from the target terminal, and determines whether the decrypted information includes authentication information. If the decrypted information includes authentication information, CPU 132 determines YES in S126 and proceeds to S130. On the other hand, if the decrypted information does not include authentication information, CPU 132 determines NO in S126 and proceeds to S140.

[0050] In S130, the CPU 132 judges whether the authentication of the authentication information is successful. Specifically, the CPU 132 identifies the authentication information (i.e., the user ID and password) included in the decrypted information. Hereinafter, the user ID and password identified here will be referred to as the "target user ID" and the "target password", respectively. That is, the target user ID and the target password are the user ID and password of the user of the target terminal, respectively. Next, the CPU 132 judges whether the combination of the target user ID and the target password is stored in the authentication table 144. If the combination of the target user ID and the target password is stored in the authentication table 144, the CPU 132 judges YES in S130 and proceeds to S132. On the other hand, if the combination of the target user ID and the target password is not stored in the authentication table 144, the CPU 132 judges NO in S130 and proceeds to S140. Since the user authentication is performed in this manner, the scan function can be provided only to appropriate users.

[0051] In S132, the CPU 132 determines whether the permission setting value for the scan function associated with the target user ID in the authentication table 144 in the memory 134 indicates "permission" or "prohibition." If the permission setting value indicates "permission" (YES in S132), the CPU 132 proceeds to S134, and if the permission setting value indicates "prohibition" (NO in S134), the CPU 132 skips S134 and S136 and ends the processing in FIG.

[0052] In S134, the CPU 132 scans the document and generates scan data.

[0053] In S136, the CPU 132 uses the communication session to transmit the generated scan data to the target terminal. When the process of S136 ends, the process of FIG.

[0054] In S140, CPU 132 uses the communication session to transmit information indicating that authentication has failed to the target terminal. Here, "authentication has failed" includes cases where authentication information has not been received from the target terminal (NO in S126) and cases where authentication information has been received from the target terminal but the authentication information is not stored in authentication table 144 (NO in S130). When the process of S140 ends, the process of FIG. 4 ends.

[0055] (Plain text scanning process; Figure 5) Next, the encryption scan process of S40 in FIG. 3 will be described with reference to FIG. 5. The processes of S210 and S212 in FIG. 5 are similar to the processes of S120 and S122 in FIG. 4, respectively. When the CPU 132 judges YES in S212, it proceeds to S220, and when the CPU 132 judges NO in S212, it proceeds to S240. The processes of S220 to S226 are similar to the processes of S110 to S116 in FIG. 4, respectively. However, the communication session established in S220 is a communication session for performing unencrypted communication, and information included in various communications using the communication session is not encrypted. The process of S228 is similar to the process of S134 in FIG. 4. The process of S230 is similar to the process of S136 in FIG. 4, except that a communication session for performing unencrypted communication is used. In this way, even in a situation where the authentication setting value 142 indicates "ON", if the permission setting value associated with the user ID "Public" indicates "ON", the user of the target terminal can cause the multi-function device 100 to execute a scan process. Furthermore, normally, in a situation where the authentication setting value 142 indicates "ON", user authentication is required when causing the multi-function device 100 to execute each function such as the scan function, print function, and copy function. On the other hand, as in this embodiment, since the permission setting value for each function is associated with the user ID "Public", it is possible to set whether or not user authentication is required for each function. This allows for flexible setting according to the administrator's intentions.

[0056] The CPU 132 transmits a connection NG response to the target terminal in S240. Usually, if YES is obtained in S210 and NO is obtained in S212, user authentication is required to execute the scan function. However, if communication of authentication information for user authentication is executed via a plaintext port, the authentication information may be acquired by a third party. Therefore, in this embodiment, the multi-function device 100 transmits a connection NG response to the target terminal in S240 without executing communication of authentication information in order to prevent unauthorized acquisition of authentication information. In particular, after receiving a connection instruction from the target terminal, the multi-function device 100 transmits a connection NG response to the target terminal without executing communication of capability information and communication of a scan execution instruction (see S222 to S226). This prevents unnecessary communication from being executed. When the process of S240 ends, the process of FIG. 5 ends.

[0057] (Case A; Figure 6) Next, specific cases realized by the processing in Fig. 3 to Fig. 5 will be described. First, with reference to Fig. 6, case A will be described in which user X corresponding to user ID "AAA" uses terminal 10A to cause multi-function device 100 to execute a scan. In the initial state of case A, both plaintext setting value 140 and authentication setting value 142 indicate "ON". In addition, the permission setting value of the scan function associated with user ID "AAA" in authentication table 144 indicates "permitted", and the permission setting value of the scan function associated with user ID "Public" indicates "not permitted".

[0058] In the following, for ease of understanding, the processes executed by the CPU (e.g., 32, 132) of each device (e.g., terminal 10A, multi-function device 100) will be described as the subject of processing, rather than each CPU being described as the subject of processing. Also, communication between each device is executed via a communication I / F (e.g., 16, 116). Therefore, in the following description, when describing communication, the phrase "via a communication I / F" will be omitted.

[0059] When the multi-function device 100 receives an operation to turn on the power from the user X in T100 (trigger in FIG. 3), it opens both the encrypted port and the plaintext port in T102 (YES in S10 and S12, S14). Then, the user X of the terminal 10A places a document on the document platen of the multi-function device 100 in T104.

[0060] At T110, the user X executes a scan operation on the terminal 10A to cause the multi-function device 100 to execute a scan. In this case, at T112, the terminal 10A transmits a connection instruction to the multi-function device 100. Since the terminal 10A supports the above-mentioned predetermined encryption protocol, the connection instruction of T110 is transmitted to the encryption port as a destination.

[0061] When the multi-function device 100 receives a connection instruction from the terminal 10A via the encryption port in T112 (YES in S20 in FIG. 3), it transmits a connection OK response to the terminal 10A in T114 (NO in S22, YES in S26, S110 in FIG. 4).

[0062] In T114, the terminal 10A receives a connection OK response from the multi-function device 100. As a result, a communication session for performing encrypted communication according to the above-mentioned predetermined encryption protocol is established between the terminal 10A and the multi-function device 100. As a result, the following communications are performed using the communication session. In T116, the terminal 10A transmits a capability information request to the multi-function device 100.

[0063] When the multi-function device 100 receives a capability information request from the terminal 10A at T116 (S112), the multi-function device 100 transmits a capability information response to the terminal 10A at T118 (S114).

[0064] In T118, the terminal 10A receives a capability information response from the multi-function device 100. Thereafter, when the terminal 10A accepts a designation of scan settings according to the capability information from the user X, in T120, the terminal 10A transmits a scan execution instruction according to the designated scan settings to the multi-function device 100.

[0065] In T120, the multi-function device 100 receives a scan execution instruction from the terminal 10A (S116). In this case, the authentication setting value 142 indicates "ON" (YES in S120), and the permission setting value of the scan function associated with the user ID "Public" in the authentication table 144 indicates "not permitted" (NO in S122). In this case, the multi-function device 100 transmits an authentication information request to the terminal 10A in T122 (S124).

[0066] When the terminal 10A receives an authentication information request from the multi-function device 100 in T122, the terminal 10A displays an authentication information input screen SC1 in T124. The authentication information input screen SC1 includes a user ID input field, a password input field, and an OK button. In T126, the terminal 10A accepts input of the user ID "AAA" in the user ID input field and input of the password "XXX" in the password input field from the user X, and then accepts selection of the OK button. In this case, in T130, the terminal 10A uses the communication session to transmit a scan execution instruction to the multi-function device 100, the scan execution instruction including information obtained by encrypting the input user ID "AAA" and password "XXX".

[0067] When the multi-function device 100 receives a scan execution instruction from the terminal 10A in T130, it decrypts the information included in the scan execution instruction to acquire the user ID "AAA" and password "XXX" (YES in S126). Because the combination of the acquired user ID "AAA" and password "XXX" is stored in the authentication table 144, the multi-function device 100 determines in T132 that the authentication has been successful (YES in S130). Also, because the permission setting value corresponding to the scan function associated with the acquired user ID "AAA" in the authentication table 144 indicates "permitted" (YES in S132), the multi-function device 100 starts scanning the document in T134.

[0068] While the multi-function device 100 is scanning an original, the terminal 10C receives a scan operation from the user Z in T140 to cause the multi-function device 100 to execute a scan, and transmits a connection instruction to the multi-function device 100 in T142.

[0069] When the multi-function device 100 receives a connection instruction from the terminal 10C in T142 (YES in S20 in FIG. 3), since the multi-function device 100 is currently scanning an original (YES in S22), the multi-function device 100 transmits a busy response to the terminal 10C in T144 (S24). This allows the user Z of the terminal 10C to know that the multi-function device 100 cannot scan because the multi-function device 100 is busy.

[0070] Thereafter, when the multi-function device 100 completes scanning of the document and generates scan data in T150, it transmits the scan data to the terminal 10A in T152. In this manner, the user X of the terminal 10A can obtain the scan data representing the document. As described above, the scan data is transmitted using a communication session for performing encrypted communication (i.e., the scan data is encrypted and transmitted). This prevents the contents of the document from being leaked to the outside.

[0071] After that, the multi-function device 100 identifies the priority "low" associated with the event name "encrypted scan" from the priority table 146 (S42 in FIG. 3). Next, the multi-function device 100 identifies the priority setting value 148. In this case, the priority setting value 148 is "(2) Record log information with a 'high' priority." Therefore, the multi-function device 100 does not transmit the log information to the server 200 (NO in S44).

[0072] (Case B; Figure 7) Next, case B will be described with reference to Fig. 7. Case B is a case in which user Y corresponding to user ID "BBB" uses terminal 10B to cause multi-function device 100 to execute a scan. In the initial state of case B, both plaintext setting value 140 and authentication setting value 142 indicate "ON". Also, the permission setting value of the scan function associated with user ID "Public" in authentication table 144 indicates "not permitted". The processes of T200 to T204 are the same as the processes of T100 to T104 in Fig. 6, respectively.

[0073] In T210, user Y executes a scan operation on terminal 10B to cause multi-function device 100 to execute a scan. In this case, in T212, terminal 10B transmits a connection instruction to multi-function device 100. Since terminal 10B does not support the above-mentioned predetermined encryption protocol, the connection instruction of T210 is transmitted to the plaintext port as the destination.

[0074] In T212, the multi-function device 100 receives a connection instruction from the terminal 10B via the plaintext port (YES in S20, NO in S22, and NO in S26 in FIG. 3). In case B, the authentication setting value 142 indicates "ON" (YES in S210 in FIG. 5), and the permission setting value of the scan function associated with the user ID "Public" in the authentication table 144 indicates "not permitted" (NO in S212). In this case, the multi-function device 100 transmits a connection NG response to the terminal 10B in T214 (S240). This prevents the authentication information from being illegally obtained by a third party. Also, in this case, since scanning is not performed by the multi-function device 100, the log information is not transmitted to the server 200.

[0075] (Case C; Figure 7) Next, case C will be described with reference to Fig. 7. Case C is a case in which user Z, a public user, uses terminal 10C to cause multi-function device 100 to execute a scan. In the initial state of case C, both plaintext setting value 140 and authentication setting value 142 indicate "ON". Also, the permission setting value of the scan function associated with user ID "Public" in authentication table 144 indicates "permitted". The processes of T300 to T304 are the same as the processes of T100 to T104 in Fig. 6, respectively.

[0076] In T310, user Z executes a scan operation on terminal 10C to cause multi-function device 100 to execute a scan. In this case, in T312, terminal 10C transmits a connection instruction to multi-function device 100. Since terminal 10C does not support the above-mentioned predetermined encryption protocol, the connection instruction of T310 is transmitted to the plaintext port as the destination.

[0077] In T312, the multi-function device 100 receives a connection instruction from the terminal 10C via the plaintext port (YES in S20, NO in S22, and NO in S26 in FIG. 3). In case C, the authentication setting value 142 indicates "ON" (YES in S210 in FIG. 5), and the permission setting value of the scan function associated with the user ID "Public" in the authentication table 144 indicates "permitted" (YES in S212). In this case, the multi-function device 100 transmits a connection OK response to the terminal 10C in T314 (S220). As a result, a communication session for performing unencrypted communication is established between the terminal 10C and the multi-function device 100.

[0078] The processes of T316 to T320 are similar to the processes of T116 to T120 in Fig. 5, respectively, except that a communication session for performing unencrypted communication is used. The processes of T334 and T350 are similar to the processes of T134 and T150 in Fig. 5, respectively. The process of T352 is similar to the process of T152 in Fig. 5, respectively, except that a communication session for performing unencrypted communication is used. That is, in T352, the multi-function device 100 transmits unencrypted scan data to the terminal 10C.

[0079] Thereafter, the multi-function device 100 identifies the priority "high" associated with the event name "plaintext scan" from the priority table 146 (S42 in FIG. 3). Next, the multi-function device 100 identifies the priority setting value 148. In this case, the priority setting value 148 is "(2) Record log information of "high" priority." Therefore, the multi-function device 100 transmits the log information to the server 200 in T360 (YES in S44, S46).

[0080] When the server 200 receives log information from the multi-function device 100 in T360, the server 200 stores, in T362, each piece of information included in the log information in the log information list 238. In this way, the server 200 can store log information of events with a "high" priority.

[0081] (Case D; Figure 8) Next, case D will be described with reference to FIG. 8. Case D is a case in which the plaintext setting value 140 indicates "OFF." The processing of T400 is similar to the processing of T100 in FIG. 6. In case D, since the plaintext setting value 140 indicates "OFF," the multi-function device 100 opens the encryption port in T402 (NO in S10 and S12 in FIG. 3). That is, in case D, the plaintext port is closed. Then, user Y of terminal 10B places a document on the document platen of the multi-function device 100 in T404.

[0082] The process of T410 is the same as the process of T210 in FIG. 7. In T412, the terminal 10B transmits a connection instruction to the multi-function device 100. Since the terminal 10B does not support the above-mentioned predetermined encryption protocol, the connection instruction of T410 is transmitted to the plaintext port as the destination. However, in case D, the plaintext port is closed. Therefore, the connection instruction is not received by the multi-function device 100 (NO in S20 in FIG. 3). In this way, the administrator of the multi-function device 100 can prevent the multi-function device 100 from executing unencrypted communication by specifying the plaintext setting value 140 as "OFF". Therefore, the security of the multi-function device 100 can be improved. Furthermore, in this case, the multi-function device 100 does not execute a scan, so that the log information is not transmitted to the server 200.

[0083] (Effects of the first embodiment) According to the above configuration, the multi-function device 100 does not transmit to the server 200 log information indicating that an encrypted scan has been executed, and transmits to the server 200 log information indicating that a plaintext scan has been executed. That is, the multi-function device 100 preferentially stores in the server 200 log information indicating that a plaintext scan has been executed. Therefore, the administrator of the multi-function device 100 can properly grasp the log information indicating that a plaintext scan has been executed. This can improve the convenience for the administrator.

[0084] Furthermore, according to the above configuration, when the multi-function device 100 receives a connection instruction from the terminal 10B with the plaintext port as the destination (T212 in FIG. 6), the multi-function device 100 does not transmit an authentication information request to the terminal 10B (see FIG. 4). This makes it possible to prevent the authentication information from being transmitted with the plaintext port as the destination, from being obtained by a third party. This makes it possible to improve security in the multi-function device 100, which executes a scan process in response to an instruction from a terminal (for example, terminals 10A to 10C) and transmits the scan data to the terminal.

[0085] (Correspondence) The terminals 10A to 10C are an example of an "external device". The terminal 10C is an example of an "other external device". The multi-function device 100 is an example of a "function executing device". The scan engine is an example of a "function executing engine". The scan function is an example of a "predetermined function". The memory 234 of the server 200 is an example of a "predetermined memory". A communication path for performing encrypted communication and a communication path for performing unencrypted communication are examples of a "first communication path" and a "second communication path", respectively. Log information including the event name "encrypted scan" and log information including the event name "plaintext scan" are examples of "first log information" and "second log information", respectively. The plaintext setting value 140 is an example of a "first setting value". "ON" and "OFF" of the plaintext setting value 140 are examples of a "first value" and a "second value", respectively. "ON" and "OFF" of the authentication setting value 142 are examples of a "third value" and a "fourth value", respectively. The permission setting value of the scan function associated with the user ID "Public" in the authentication table 144 is an example of an "permission setting value." A combination of a user ID and a password is an example of "user authentication information." Information obtained by encrypting the user ID "AAA" and the password "XXX" is an example of "specific authentication information." A connection instruction is an example of an "associated instruction." The scan execution instruction of S116 in FIG. 34 and the scan execution instruction of S226 in FIG. 5 are examples of a "first function execution instruction" and a "second function execution instruction," respectively. The connection NG response sent at S240 in FIG. 5 is an example of an "error signal."

[0086] The process of S20 and the process of S46 in FIG. 3 are examples of processes executed by the "instruction receiving unit" and the "storage control unit", respectively. The process of S112, the process of S116, the process of S124, the process of S126, and the process of S130 in FIG. 4 are examples of processes executed by the "capability information request receiving unit", the "first receiving unit", the "request transmitting unit", the "authentication information receiving unit", and the "authentication executing unit", respectively. The process of S134 in FIG. 4 is an example of a process executed by the "first engine control unit". The process of S226 and the process of S228 in FIG. 5 are examples of processes executed by the "second receiving unit" and the "second engine control unit", respectively. The process of S240 in FIG. 5 is an example of a process executed by the "error transmitting unit".

[0087] (Second Example) Next, a second embodiment will be described. In the second embodiment, the process related to the transmission of log information is different from that in the first embodiment. As shown in Fig. 1, the multi-function device 100 of the second embodiment does not store a priority setting value 148. Also, as shown in Fig. 2, the log information list 238 stored in the server 200 of the second embodiment stores a priority in association with each piece of information stored in the first embodiment.

[0088] (Scanning process on a multifunction device; Figure 3) The scan processing realized by the CPU 132 of the multi-function device 100 of the second embodiment executing the program 136 will be described with reference to Fig. 3. The description of the same processing as in the first embodiment (i.e., the processing of S10 to S42 in Fig. 3) will be omitted.

[0089] In S50, CPU 132 transmits log information of the occurring event to server 200 via communication I / F 116. The log information includes the priority determined in S42 in addition to each piece of information included in the log information of the first embodiment. When the process of S50 ends, CPU 132 returns to the monitoring process of S20.

[0090] (Case E; Figure 9) Next, specific cases realized by the processing of Fig. 3 to Fig. 5 in the second embodiment will be described. First, with reference to Fig. 9, case E will be described in which user X corresponding to user ID "AAA" uses terminal 10A to cause multi-function device 100 to execute a scan. The initial state of case E is the same as the initial state of case A. In case E, first, processing similar to T100 to T152 in Fig. 6 is executed.

[0091] After that, the multi-function device 100 identifies the priority level "low" associated with the event name "encrypted scan" from the priority level table 146 (S42 in FIG. 3). Then, the multi-function device 100 transmits log information including the priority level "low" to the server 200 in T560.

[0092] When the server 200 receives log information from the multi-function device 100 in T560, the server 200 stores, in T562, each piece of information included in the log information in the log information list 238. In this way, the server 200 can store log information of events with a "low" priority.

[0093] (Case F; Figure 9) Next, case F will be described with reference to Fig. 9. Case F is a case in which user Z, who is a public user, uses terminal 10C to cause multi-function device 100 to execute a scan. The initial state of case F is similar to the initial state of case C. In case C, first, processes similar to T300 to T352 in Fig. 7 are executed.

[0094] After that, the multi-function device 100 identifies the priority "high" associated with the event name "plain text scan" from the priority table 146 (S42 in FIG. 3). Then, the multi-function device 100 transmits log information including the priority "high" to the server 200 in T660.

[0095] When the server 200 receives log information from the multi-function device 100 in T660, the server 200 stores, in T662, each piece of information included in the log information in the log information list 238. In this way, the server 200 can store log information of events with a "high" priority.

[0096] (Effects of the second embodiment) As described above, the multi-function device 100 transmits log information including the priority "low" to the server 200 when an encrypted scan is performed. Also, the multi-function device 100 transmits log information including the priority "high" to the server 200 when a plaintext scan is performed. That is, the multi-function device 100 preferentially stores log information indicating that a plaintext scan with a high priority has been performed in the server 200. Therefore, the administrator of the multi-function device 100 can properly understand the log information indicating that a plaintext scan has been performed by checking the log information associated with the priority "high" from the log information list 238. This can improve the convenience of the administrator. The priority "low" and the priority "high" are examples of the "first priority" and the "second priority", respectively.

[0097] (Third Example) Next, a third embodiment will be described. In the second embodiment, the process related to the transmission of log information is different from the first and second embodiments. As shown in FIG. 1, the multi-function device 100 of the third embodiment does not store the priority table 146 and the priority setting value 148. In addition, the server 200 of the third embodiment stores the priority table 246 and the priority setting value 248. The priority table 246 and the priority setting value 248 are the same as the priority table 146 and the priority setting value 148 stored in the multi-function device 100 of the first embodiment, respectively. However, the meaning of each setting value of the priority setting value 248 is as follows. "(1) OFF" means that no log information of any priority is stored (i.e., even if log information is received, the log information is discarded). "(2) Record log information of priority "high"" means that log information of priority "high" is stored, and log information of priority "medium" or "low" is not stored. "(3) Record log information of "high" and "medium" priority" means that log information of "high" or "medium" priority is stored, and log information of "low" priority is not stored. "(4) Record all log information" means that log information of any priority is stored. In a modified example, server 200 may store log information including priority in log information list 238 (see second embodiment). In this case, server 200 does not need to store priority setting value 248.

[0098] (Scanning process on a multifunction device; Figure 3) A scan process implemented by the CPU 132 of the multi-function device 100 of the third embodiment executing the program 136 will be described with reference to Fig. 3. A description of the same processes as those in the first embodiment (i.e., the processes of S10 to S40 in Fig. 3) will be omitted.

[0099] In S60, CPU 132 transmits log information of the occurring event to server 200 via communication I / F 116. The log information transmitted here is similar to the log information transmitted in S46 of the first embodiment. If CPU 132 determines that an event has not occurred, it does not execute the processes from S60 onwards and returns to the monitoring process of S20. When the process of S60 ends, CPU 132 returns to the monitoring process of S20.

[0100] (Case G; Figure 10) Next, specific cases realized by the processing of Fig. 3 to Fig. 5 in the third embodiment will be described. First, with reference to Fig. 9, case Gr will be described in which user X corresponding to user ID "AAA" uses terminal 10A to cause multi-function device 100 to execute scanning. The initial state of case G is similar to the initial state of case A. In case G, first, processing similar to T100 to T152 in Fig. 6 is executed.

[0101] After that, in T760, the multi-function device 100 transmits the log information to the server 200. The log information transmitted here includes the event name "Encrypted Scan".

[0102] In T760, the server 200 receives log information including the event name "encrypted scan" from the multi-function device 100. In this case, the server 200 first identifies the priority "low" associated with the event name "encrypted scan" from the priority table 246. Next, the server 200 identifies the priority setting value 248. In this case, the priority setting value 248 is "(2) Record log information of "high" priority." Therefore, the server 200 does not store log information including the event name "encrypted scan." Note that, in a modified example, the server 200 may store log information in which the event name "encrypted scan" is associated with the priority "low" in the log information list 238.

[0103] (Case H; Figure 10) Next, case H will be described with reference to Fig. 10. Case H is a case in which user Z, who is a public user, uses terminal 10C to cause multi-function device 100 to execute a scan. The initial state of case H is similar to the initial state of case C. In case H, first, processes similar to T300 to T352 in Fig. 7 are executed.

[0104] After that, in T860, the multi-function device 100 transmits the log information to the server 200. The log information transmitted here includes the event name "plain text scan".

[0105] In T860, the server 200 receives log information including the event name "plaintext scan" from the multi-function device 100. In this case, the server 200 first identifies the priority "high" associated with the event name "plaintext scan" from the priority table 246. Next, the server 200 identifies the priority setting value 248. In this case, the priority setting value 248 is "(2) Record log information of "high" priority". Therefore, the server 200 stores log information including the event name "plaintext scan" in T862. In this manner, the server 200 can store log information of an event with a "high" priority. Note that, in a modified example, the server 200 may store log information associated with the event name "plaintext scan" and the priority "high" in the log information list 238.

[0106] (Effects of the third embodiment) According to the above configuration, the server 200 does not store log information indicating that an encrypted scan has been performed, but stores log information indicating that a plaintext scan has been performed. That is, the multi-function device 100 preferentially stores log information indicating that a plaintext scan has been performed. Therefore, the administrator of the multi-function device 100 can properly grasp the log information indicating that a plaintext scan has been performed. This can improve the convenience of the administrator. The combination of the multi-function device 100 and the server 200 is an example of a "function executing device." In particular, the multi-function device 100 and the server 200 are examples of a "specific device" and a "server," respectively.

[0107] Although specific examples of the technology disclosed in this specification have been described in detail above, these are merely examples and do not limit the scope of the claims. The technology described in the claims includes various modifications and variations of the specific examples exemplified above. Modifications of the above embodiments are listed below.

[0108] (Variation 1) The memory 134 of the multi-function device 100 may store the log information list 238, and the server 200 may not store the log information list 238. In this case, in S46, S50, and S60 of Fig. 3, the multi-function device 100 may store the log information in the log information list 238 in the memory 134 of the multi-function device 100 instead of transmitting the log information to the server 200. In this variation, the memory 134 of the multi-function device 100 is an example of a "predetermined memory."

[0109] (Variation 2) In the above embodiment, the case where the multi-function device 100 is caused to execute a scan function has been described. In a variation, the technology described in the above embodiment can be applied to a case where the multi-function device 100 is caused to execute a function other than the scan function, for example, a print function. That is, the multi-function device 100 does not need to transmit to the server 200 log information indicating that the print function has been executed in accordance with a print instruction via a communication path for executing encrypted communication. Also, the multi-function device 100 may transmit to the server 200 log information indicating that the print function has been executed in accordance with a print instruction via a communication path for executing unencrypted communication. In this variation, the print engine 120 and the print function are examples of a "function execution engine" and a "predetermined function", respectively.

[0110] (Variation 3) The multi-function device 100 does not need to store the plaintext setting value 140. In this case, the multi-function device 100 can omit the process of S12 in FIG.

[0111] (Variation 4) When the power supply of the multi-function device 100 is ON, the multi-function device 100 may open the plaintext port. In this situation, the plaintext setting value 140 indicating "ON" may mean that the device is in a state where a process is executed according to a signal received via the plaintext port. Furthermore, the plaintext setting value 140 indicating "OFF" may mean that the device is in a state where a process is not executed according to a signal received via the plaintext port.

[0112] (Variation 5) When the result of S212 in Fig. 5 is NO, the multi-function device 100 may execute the processes of S110 to S116 and S124 and thereafter in Fig. 4. In this variation, the "request sending unit" may "send an authentication information request to an external device" even when "a related instruction is received from an external device via the second communication path".

[0113] (Variation 6) When a scan execution instruction is received in S116 of Fig. 4, the multi-function device 100 may execute a scan of an original document to generate scan data. Then, when YES is determined in S130 and YES is determined in S132, the multi-function device 100 may transmit the generated scan data to the target terminal. On the other hand, when NO is determined in S130, the multi-function device 100 may not transmit the generated scan data to the target terminal. In this variation, scanning an original document but not transmitting the scan data to the target terminal is an example of "not executing a specified function".

[0114] (Variation 7) The multi-function device 100 does not need to store the authentication table 144, and for example, an external authentication server, an external storage device, or the like may store the authentication table 144. In this case, when a scan execution instruction including authentication information is received in S126 of Fig. 4, the multi-function device 100 may transmit the authentication information to the authentication server, the external storage device, or the like. In this variation, the "authentication execution unit" can be omitted.

[0115] (Variation 8) The multi-function device 100 may not store the authentication setting value 142. In this case, the multi-function device 100 may omit the processes of S120 and S122 in Fig. 4 and execute the process of S124. The multi-function device 100 may also omit the processes of S210 and S212 in Fig. 5 and execute the process of S240.

[0116] (Modification 9) The authentication table 144 may not store the user ID "Public." That is, the multi-function device 100 may be configured to not permit functions (for example, a scan function) to public users.

[0117] (Modification 10) The multi-function device 100 can omit the processes of S22 and S24 in Fig. 3. That is, when the multi-function device 100 receives a new connection instruction while executing a scan process, the multi-function device 100 may execute the processes of S26 and subsequent steps in Fig. 3 in accordance with the connection instruction.

[0118] (Modification 11) The timing at which the processes of S210 and S212 in FIG. 5 are executed is not limited to the form of the embodiment. For example, the processes of S210 and S212 may be executed after the process of S222, or may be executed after the process of S226. In these circumstances, if NO is determined in S212, the multi-function device 100 may transmit an error signal to the target terminal in S240 instead of a connection NG response. In this modification, the above error signal is an example of an "error signal." Generally speaking, the timing at which the processes are executed by the "error transmission unit" is not limited to the form of the embodiment.

[0119] (Modification 12) The multi-function device 100 can omit the processes of S112 and S114 in Fig. 4. In this modification, the "capability information request receiving unit" can be omitted.

[0120] (Variation 13) In the above embodiment, the processing of each step in Figures 3 to 10 is realized by software (e.g., OS 36, application 38, program 136), but at least one of these processes may be realized by hardware such as a logic circuit.

[0121] The technical elements described in this specification or drawings have technical utility either alone 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 in this specification or drawings can achieve multiple objectives simultaneously, and achieving one of these objectives is itself technically useful.

[0122] In the scope of the claims at the time of filing of this patent application, even if each claim is dependent on only some of the claims, it is not limited to the fact that each claim can be dependent on only those some of the claims. Each claim can also be dependent on other claims that are not dependent on it at the time of filing to the extent that there is no technical contradiction. In other words, the technology of each claim can be combined in various ways as follows: (Item 1) A function-performing device, comprising: A function execution engine; a first receiving unit that receives a first function execution instruction from an external device via a first communication path for performing encrypted communication; a first engine control unit that, when the first function execution instruction is received from the external device, causes the function execution engine to execute a predetermined function according to the first function execution instruction; a second receiving unit that receives a second function execution instruction from the external device via a second communication path for performing unencrypted communication; a second engine control unit that, when the second function execution instruction is received from the external device, causes the function execution engine to execute the predetermined function according to the second function execution instruction; a storage control unit that stores second log information indicating that the predetermined function has been executed in accordance with the second function execution instruction in a predetermined memory with priority over first log information indicating that the predetermined function has been executed in accordance with the first function execution instruction; A function performing device comprising: (Item 2) The storage control unit, When the predetermined function is executed in accordance with the first function execution instruction, the first log information is not stored in the predetermined memory; storing the second log information in the predetermined memory when the predetermined function is executed in accordance with the second function execution instruction; Item 1. A device for performing the function according to item 1. (Item 3) The storage control unit, storing the first log information indicating a first priority in the predetermined memory when the predetermined function is executed in accordance with the first function execution instruction; storing, in the predetermined memory, the second log information indicating a second priority higher than the first priority when the predetermined function is executed in accordance with the second function execution instruction; Item 1. A device for performing the function according to item 1. (Item 4) the function execution device comprises a specific device and a server configured separately from the specific device; the specific device comprises the function execution engine, the first receiving unit, the first engine control unit, the second receiving unit, and the second engine control unit; 2. The function executing device according to item 1, wherein the server comprises the specified memory and the storage control unit. (Item 5) the function executing device further comprises a memory for storing a first setting value; the first setting value indicates either a first value corresponding to executing the predetermined function in accordance with a function execution instruction via the second communication path, or a second value corresponding to not executing the predetermined function in accordance with a function execution instruction via the second communication path; The second engine control unit includes: when the first setting value indicates the first value and the second function execution instruction is received from the external device via the second communication path, causing the function execution engine to execute the predetermined function in accordance with the second function execution instruction; when the first setting value indicates the second value, the function execution engine is not caused to execute the predetermined function in accordance with a function execution instruction received via the second communication path; 5. A function executing device according to any one of items 1 to 4. (Item 6) The function execution device further comprises: an instruction receiving unit that receives an instruction related to the execution of the predetermined function from the external device; a request sending unit that sends, when the association instruction is received from the external device via the first communication path, an authentication information request that requests transmission of specific authentication information to the external device; an authentication information receiving unit that receives the specific authentication information from the external device via the first communication path in response to the authentication information request being transmitted to the external device; Equipped with The first engine control unit includes: when the first function execution instruction is received from the external device and user authentication according to the specific authentication information is successful, causing the function execution engine to execute the predetermined function according to the first function execution instruction; when the first function execution instruction is received from the external device and the user authentication according to the specific authentication information fails, the predetermined function according to the first function execution instruction is not executed; 6. The function executing device according to any one of claims 1 to 5, wherein the request sending unit does not send the authentication information request to the external device when the related instruction is received from the external device via the second communication path. (Item 7) The function execution device further comprises: A memory configured to be able to store a plurality of pieces of user authentication information corresponding to a plurality of individual users; an authentication execution unit that executes the user authentication according to the specific authentication information and the plurality of pieces of user authentication information in the memory when the specific authentication information is received from the external device via the first communication path; 7. The function executing device according to item 6, comprising: (Item 8) the function executing device further comprises a memory for storing an authentication setting value, the authentication setting value indicating either a third value corresponding to a requirement of user authentication for executing the predetermined function or a fourth value corresponding to a requirement of no user authentication for executing the predetermined function; The request sending unit is sending the authentication information request to the external device when the associated instruction is received from the external device via the first communication path in a situation where the authentication setting value in the memory is the third value; when the authentication setting value in the memory is the third value and the related instruction is received from the external device via the second communication path, the authentication information request is not sent to the external device; the first engine control unit further causes the function execution engine to execute the predetermined function in accordance with the first function execution instruction when the first function execution instruction is received from the external device via the first communication path in a situation where the authentication setting value in the memory is the fourth value; The function execution device described in item 6 or 7, wherein the second engine control unit further causes the function execution engine to execute the specified function in accordance with the second function execution instruction when the second function execution instruction is received from the external device via the second communication path when the authentication setting value in the memory is the fourth value. (Item 9) the function execution device is capable of executing a plurality of functions including the predetermined function, the memory further stores, for each of the plurality of functions, a permission setting value indicating whether or not execution of the function is permitted without executing the user authentication when the authentication setting value indicates the third value; the second engine control unit, when receiving the second function execution instruction from the external device via the second communication path in a situation where the authentication setting value in the memory indicates the third value and the permission setting value in the memory corresponding to the predetermined function indicates permission for execution of the predetermined function without performing the user authentication, causes the function execution engine to execute the predetermined function in accordance with the second function execution instruction without performing the user authentication; The function executing device described in item 8, wherein the request sending unit does not send the authentication information request to the external device when the related instruction is received from the external device via the second communication path in a situation where the authentication setting value in the memory indicates the third value and the permission setting value corresponding to the specified function in the memory indicates that execution of the specified function is not permitted without performing the user authentication. (Item 10) The function executing device of any one of items 6 to 9, wherein the request sending unit does not send the authentication information request to the other external device even if the related instruction is received from the other external device via the first communication path between when the related instruction is received from the external device via the first communication path and when the scan data is sent to the external device via the first communication path. (Item 11) the association instruction is a connection instruction instructing the function performing device to establish a communication session between the scanner and the external device; the first receiving unit receives the first function execution instruction from the external device by using the communication session; the request transmission unit transmits the authentication information request to the external device when the first function execution instruction is received from the external device via the first communication path; the second receiving unit receives the second function execution instruction from the external device by using the communication session; The function execution device further comprises: 11. The function executing device according to any one of claims 6 to 10, further comprising an error sending unit that sends an error signal to the external device without sending the authentication information request to the external device when the connection instruction is received from the external device via the second communication path. (Item 12) the function performing device further includes a capability information request receiving unit that receives a capability information request from the external device by using the communication session after the communication session is established and before the first function performing instruction is received; Item 12. The function performing device according to item 11, wherein the capability information request is a signal requesting transmission of capability information indicating capabilities of the function performing device. [Explanation of symbols]

[0123] 2: communication system, 4: LAN, 6: Internet, 10A to 10C: terminal, 12, 112: operation unit, 14, 114: display unit, 16, 116, 216: communication I / F, 30, 130, 230: control unit, 32, 132, 232: CPU, 34, 134, 234: memory, 36: OS program, 38: application program, 118: scan engine, 120: print engine, 136: program, 140: plain text setting value, 142: authentication setting value, 144: authentication table, 146, 246: priority table, 148, 248: priority setting value

Claims

1. A function-performing device, comprising: A function execution engine; a first receiving unit that receives a first function execution instruction from an external device via a first communication path for performing encrypted communication; a first engine control unit that, when the first function execution instruction is received from the external device, causes the function execution engine to execute a predetermined function in accordance with the first function execution instruction; a second receiving unit that receives a second function execution instruction from the external device via a second communication path for performing unencrypted communication; a second engine control unit that, when the second function execution instruction is received from the external device, causes the function execution engine to execute the predetermined function in accordance with the second function execution instruction; a storage control unit that stores second log information indicating that the predetermined function has been executed in accordance with the second function execution instruction in a predetermined memory with priority over first log information indicating that the predetermined function has been executed in accordance with the first function execution instruction; A function performing device comprising:

2. The storage control unit, When the predetermined function is executed in accordance with the first function execution instruction, the first log information is not stored in the predetermined memory; storing the second log information in the predetermined memory when the predetermined function is executed in accordance with the second function execution instruction; 2. The function performing device according to claim 1.

3. The storage control unit, storing the first log information indicating a first priority in the predetermined memory when the predetermined function is executed in accordance with the first function execution instruction; storing, in the predetermined memory, the second log information indicating a second priority higher than the first priority when the predetermined function is executed in accordance with the second function execution instruction; 2. The function performing device according to claim 1.

4. the function execution device comprises a specific device and a server configured separately from the specific device; the specific device comprises the function execution engine, the first receiving unit, the first engine control unit, the second receiving unit, and the second engine control unit; 2. The function executing device according to claim 1, wherein said server comprises: said predetermined memory; and said storage control unit.

5. the function executing device further comprises a memory for storing a first setting value; the first setting value indicates either a first value corresponding to executing the predetermined function in accordance with a function execution instruction via the second communication path, or a second value corresponding to not executing the predetermined function in accordance with a function execution instruction via the second communication path; The second engine control unit includes: when the first setting value indicates the first value and the second function execution instruction is received from the external device via the second communication path, causing the function execution engine to execute the predetermined function in accordance with the second function execution instruction; when the first setting value indicates the second value, the function execution engine is not caused to execute the predetermined function in accordance with a function execution instruction received via the second communication path; 2. The function performing device according to claim 1.

6. The function execution device further comprises: an instruction receiving unit that receives an instruction related to the execution of the predetermined function from the external device; a request sending unit that sends, when the association instruction is received from the external device via the first communication path, an authentication information request that requests transmission of specific authentication information to the external device; an authentication information receiving unit that receives the specific authentication information from the external device via the first communication path in response to the authentication information request being transmitted to the external device; Equipped with The first engine control unit includes: when the first function execution instruction is received from the external device and user authentication according to the specific authentication information is successful, causing the function execution engine to execute the predetermined function according to the first function execution instruction; when the first function execution instruction is received from the external device and the user authentication according to the specific authentication information fails, the predetermined function according to the first function execution instruction is not executed; The function executing device according to claim 1 , wherein the request transmitting unit does not transmit the authentication information request to the external device when the associated instruction is received from the external device via the second communication path.

7. The function execution device further comprises: A memory configured to be able to store a plurality of pieces of user authentication information corresponding to a plurality of individual users; an authentication execution unit that executes the user authentication according to the specific authentication information and the plurality of pieces of user authentication information in the memory when the specific authentication information is received from the external device via the first communication path; The function performing device according to claim 6 , comprising:

8. the function executing device further comprises a memory for storing an authentication setting value, the authentication setting value indicating either a third value corresponding to a requirement of user authentication for executing the predetermined function, or a fourth value corresponding to a requirement of no user authentication for executing the predetermined function; The request sending unit is sending the authentication information request to the external device when the associated indication is received from the external device via the first communication path in a situation where the authentication setting value in the memory is the third value; when the associated instruction is received from the external device via the second communication path in a situation where the authentication setting value in the memory is the third value, not sending the authentication information request to the external device; the first engine control unit further causes the function execution engine to execute the predetermined function in accordance with the first function execution instruction when the first function execution instruction is received from the external device via the first communication path in a situation where the authentication setting value in the memory is the fourth value; 7. The function executing device according to claim 6, wherein the second engine control unit further causes the function executing engine to execute the specified function in accordance with the second function execution instruction when the second function execution instruction is received from the external device via the second communication path in a situation where the authentication setting value in the memory is the fourth value.

9. the function execution device is capable of executing a plurality of functions including the predetermined function, the memory further stores, for each of the plurality of functions, a permission setting value indicating whether or not execution of the function is permitted without executing the user authentication in a situation where the authentication setting value indicates the third value; the second engine control unit, when receiving the second function execution instruction from the external device via the second communication path in a situation where the authentication setting value in the memory indicates the third value and the permission setting value in the memory corresponding to the predetermined function indicates permission for execution of the predetermined function without performing the user authentication, causes the function execution engine to execute the predetermined function in accordance with the second function execution instruction without performing the user authentication; 9. The function executing device of claim 8, wherein the request sending unit does not send the authentication information request to the external device when the related instruction is received from the external device via the second communication path in a situation where the authentication setting value in the memory indicates the third value and the permission setting value corresponding to the specified function in the memory indicates that execution of the specified function is not permitted without performing the user authentication.

10. 7. The function executing device of claim 6, wherein the request sending unit does not send the authentication information request to another external device even if the related instruction is received from the other external device via the first communication path between when the related instruction is received from the external device via the first communication path and when the scan data is sent to the external device via the first communication path.

11. the association instruction is a connection instruction instructing the function performing device to establish a communication session between the scanner and the external device; the first receiving unit receives the first function execution instruction from the external device by using the communication session; the request transmission unit transmits the authentication information request to the external device when the first function execution instruction is received from the external device via the first communication path; the second receiving unit receives the second function execution instruction from the external device by using the communication session; The function execution device further comprises:

7. The function executing device according to claim 6, further comprising an error sending unit that, when the connection instruction is received from the external device via the second communication path, sends an error signal to the external device without sending the authentication information request to the external device.

12. the function performing device further includes a capability information request receiving unit configured to receive a capability information request from the external device by using the communication session after the communication session is established and before the first function performing instruction is received; 12. The function performing device according to claim 11, wherein the capability information request is a signal requesting transmission of capability information indicating capabilities of the function performing device.

13. A computer program for a function performing device, comprising: The function performing device comprises: A function execution engine; A computer, Equipped with The computer program causes the computer to operate in the following manner: receiving a first function execution instruction from an external device via a first communication path for performing encrypted communication; a first engine control unit that, when the first function execution instruction is received from the external device, causes the function execution engine to execute a predetermined function in accordance with the first function execution instruction; a second receiving unit that receives a second function execution instruction from the external device via a second communication path for performing unencrypted communication; a second engine control unit that, when the second function execution instruction is received from the external device, causes the function execution engine to execute the predetermined function in accordance with the second function execution instruction; a storage control unit that stores second log information indicating that the predetermined function has been executed in accordance with the second function execution instruction in a predetermined memory with priority over first log information indicating that the predetermined function has been executed in accordance with the first function execution instruction; A computer program that functions as a

14. 1. A method for controlling a function-performing device, comprising: the function execution device comprises a function execution engine; The method comprises: a first receiving step of receiving a first function execution instruction from an external device via a first communication path for performing encrypted communication; a first engine control step of causing the function execution engine to execute a predetermined function according to the first function execution instruction when the first function execution instruction is received from the external device; a second receiving step of receiving a second function execution instruction from the external device via a second communication path for performing unencrypted communication; a second engine control step of causing the function execution engine to execute the predetermined function according to the second function execution instruction when the second function execution instruction is received from the external device; a storage control step of storing, in a predetermined memory, second log information indicating that the predetermined function has been executed in accordance with the second function execution instruction, with priority over first log information indicating that the predetermined function has been executed in accordance with the first function execution instruction; A method comprising:

Citation Information

Patent Citations

  • Information processing apparatus, image processing apparatus, information processing method, and program

    JP2022136867A