Information processing apparatus, storage medium, and control method

Abstract

This invention provides an information processing apparatus, a storage medium, and a control method. The information processing apparatus is capable of communicating with external devices and executing applications using a simple network management protocol. The control method includes: obtaining an engine identifier from one or more external devices by broadcasting a request to obtain an engine identifier; based on the obtained engine identifier, sending a request to an external device configured to send an engine identifier including predetermined information to obtain Management Information Base (MIB) information, and obtaining the MIB information; and displaying external devices supported by the application as search results based on the obtained MIB information, wherein external devices not supported by the application are not displayed as search results based on the obtained MIB information.

Description

[0001] This application is a divisional application of the invention patent application filed on April 23, 2020, with application number 202010328414.2 and title "Information Processing Apparatus, Storage Medium and Control Method". Technical Field

[0002] This disclosure relates to techniques for searching external devices and displaying search results. Background Technology

[0003] In recent years, high-performance mobile terminals known as smartphones have become widespread, and applications have emerged that use these mobile terminals to communicate with image processing devices such as multifunction printers (MFPs), enabling print or scan commands to be issued from the mobile terminal (hereinafter referred to as an MFP application). Such MFP applications search for MFPs on a network via wireless communication and determine the MFP the user will use based on the search results. The MFP application then allows the user to select a file stored on the mobile terminal, such as a Joint Picture Experts Group (JPEG) image file or a Portable Document Format (PDF) file, and send that file and the user-specified print settings to the MFP.

[0004] Meanwhile, one method for searching for MFPs on a network is to broadcast packets using a communication protocol called Simple Network Management Protocol (SNMP) and determine whether the responding MFP is an MFP supported by an MFP application based on information obtained from the Management Information Base (MIB) sent by the responding MFP. Japanese Patent Application Publication No. 2008-146410 discusses a method for searching for print processing devices using SNMP version 1 (SNMPv1) and SNMP version 3 (SNMPv3).

[0005] To enable mobile terminals to search for MFPs using SNMPv3, information such as authentication information needs to be configured on the mobile terminal. However, there are situations where users are unaware that such configuration is necessary, or they have configured it incorrectly. In such cases, the following problem arises: if the user expects an MFP with settings only for responding to SNMPv3, the incorrect configuration will prevent the expected MFP from being found even during a search. Summary of the Invention

[0006] According to embodiments of this disclosure, a control method for an information processing device is provided, the information processing device being able to communicate with an external device via a Simple Network Management Protocol (SMMP) and being able to perform a first setting regarding the SMMP, the control method comprising: providing a notification to a user indicating that the first setting is incorrect if the first setting is incorrect.

[0007] Other features of this disclosure will become clear from the following description of exemplary embodiments with reference to the accompanying drawings. Attached Figure Description

[0008] Figure 1 This is a diagram illustrating the construction according to an exemplary embodiment.

[0009] Figure 2 This is a diagram illustrating the hardware structure of a mobile terminal.

[0010] Figure 3 This is a diagram illustrating the software architecture of a mobile terminal.

[0011] Figure 4 This is a diagram illustrating the hardware structure of an image processing device.

[0012] Figure 5 This is a flowchart illustrating a Simple Network Management Protocol version 1 (SNMPv1) search process performed by a multifunction printer (MFP) application according to a first exemplary embodiment.

[0013] Figure 6 This is a flowchart illustrating the SNMP version 3 (SNMPv3) search process performed by an MFP application according to a first exemplary embodiment.

[0014] Figure 7 This is a flowchart illustrating the device search process performed by an MFP application according to a first exemplary embodiment.

[0015] Figure 8 This is a flowchart illustrating the device search process performed by an MFP application according to a second exemplary embodiment.

[0016] Figure 9 This shows an example of a setup screen for SNMPv1 settings that will be displayed in MFP.

[0017] Figure 10 This shows an example of a setup screen for SNMPv3 settings that will be displayed in MFP.

[0018] Figure 11 An example of an SNMP setup screen that will be displayed by an MFP application is shown.

[0019] Figure 12A , Figure 12B , Figure 12C and Figure 12D Each example shows a device search screen that will be displayed by the MFP application.

[0020] Figure 13A and Figure 13BEach example shows a device search screen to be displayed by an MFP application according to a second exemplary embodiment. Detailed Implementation

[0021] Exemplary embodiments of the present disclosure will now be described with reference to the accompanying drawings. These exemplary embodiments are not intended to be limiting, and not all combinations of features described in the exemplary embodiments are to be considered essential.

[0022] Exemplary embodiments of this disclosure will now be described in detail with reference to the accompanying drawings.

[0023] Figure 1 This is a diagram illustrating the construction of a data processing system according to a first exemplary embodiment of the present disclosure. Figure 1 In this example, mobile terminal 100 is used as an information processing device. Mobile terminal 100 is a computer for providing instructions to send print jobs to each of the multifunction printer (MFP) 110, single-function printer (SFP) 120, and SFP 130.

[0024] The MFP 110, SFP 120, and SFP 130 are examples of image processing devices. In addition to printing functions, the MFP 110 also has functions such as copying, scanning, and faxing. Figure 1 A wireless local area network (LAN) terminal 101 is shown. In this exemplary embodiment, in each of the image processing devices 110, 120, and 130, the communication protocol, particularly Simple Network Management Protocol version 3 (SNMPv3), is set to ON, and authentication and encryption of security settings are enabled. Hereinafter, a device with SNMPv3 set to ON is referred to as a device (device) having SNMPv3 settings.

[0025] LAN 10 is the network to which the aforementioned devices are connected, and the devices communicate with each other via LAN 10. Wireless LAN terminal 101 is a base station for the wireless LAN and has general network / router functions. Wireless LAN terminal 101 provides a wireless LAN in locations such as homes or offices. By enabling the wireless LAN function, mobile terminal 100 can connect to LAN 10 via wireless LAN terminal 101. When entering a wireless LAN area provided by wireless LAN terminal 101, mobile terminal 100 can automatically connect to the network of LAN 10 using pre-set authentication information.

[0026] Next, we will refer to Figure 2The hardware configuration of the mobile terminal 100 is described. The mobile terminal 100 of this exemplary embodiment is a device such as a smartphone or a tablet personal computer (PC), but may be other types of devices (if the device is an information processing device capable of performing wireless communication).

[0027] The Central Processing Unit (CPU) 201 reads the control program stored in the Read-Only Memory (ROM) 202 and executes various processes for controlling the operation of the mobile terminal 100 based on the control program. The ROM 202 stores the control program. The Random Access Memory (RAM) 203 serves as a temporary storage area, acting as the main memory, working area, etc., of the CPU 201. The Flash Memory 204 stores various data such as images and electronic documents. The Flash Memory 204 also stores the Operating System (OS) 350 and the MFP application 300, which will be described below. The Real-Time Clock (RTC) 205 holds the time.

[0028] In the case of mobile terminal 100, one CPU 201 executes the various steps of the processes in the flowcharts described below, but other modes may be used. For example, multiple CPUs may also cooperate with each other to execute the various steps of the processes in the flowcharts described below.

[0029] The operation panel 206 has a touch panel function that enables the detection of user touch operations and displays various screens provided by the OS350 or MFP application 300. The user can input desired operation commands into the mobile terminal 100 by inputting touch operations on the operation panel 206.

[0030] When a user speaks to someone via a connection to another mobile terminal or landline, speaker 207 and microphone 208 are used. Camera 209 captures images based on the user's camera commands. Images captured by camera 209 are stored in a predetermined area of ​​flash memory 204.

[0031] The wireless communication unit 211 is connected to, for example, a wireless communication LAN or a public line to perform wireless communication.

[0032] Next, we will refer to Figure 3 Describe the software structure of the mobile terminal 100. Figure 3 This is a functional block diagram showing the software implemented by the CPU 201 by reading the control program stored in the ROM 202 or flash memory 204.

[0033] OS 350 is software used to control the operation of the entire mobile terminal 100. Various applications, including the MFP application 300 described below, can be installed on the mobile terminal 100. OS 350 exchanges information with these applications and changes the screen displayed on the operation panel 206 based on instructions received from each application. OS 350 includes a group of device drivers for controlling various hardware components and provides application programming interfaces (APIs) for applications operating on the OS to use these hardware components.

[0034] MFP Application 300 is an application installed on Mobile Terminal 100. MFP Application 300 enables users to perform operations such as printing and scanning on the MFP. In addition to MFP Application 300, various other applications are also installed on Mobile Terminal 100, but their descriptions will be omitted.

[0035] The software architecture of the MFP application 300 will be described in more detail. The screen control unit 301 controls the screen displayed on the operation panel 206 via the OS 350. The screen control unit 301 displays the MFP application screen on the operation panel 206. Furthermore, the screen control unit 301 determines the operation commands input by the user via the operation panel 206. The communication unit 302 controls the wireless communication unit 211 via the OS 350 to perform wireless communication, for example, sending and receiving commands.

[0036] The print job generation unit 305 generates a print job. The print job generated by the print job generation unit 305 is sent to the MFP by the wireless communication unit 211, and the MFP performs printing based on the print job.

[0037] The wireless LAN connection control unit 310 controls the connection to the wireless LAN and instructs the OS 350 to perform the connection.

[0038] Application storage unit 306 temporarily stores various information.

[0039] The scan job control unit 307 provides scan commands to the MFP via the wireless communication unit 211 and controls the scan data received from the MFP. When scan data needs to be saved, it is temporarily stored in the application storage unit 306. The document management unit 308 manages the saved scan data.

[0040] The device search control unit 311 provides the function of enabling the mobile terminal 100 to search for network devices managed by SNMP on the LAN 10 to which the mobile terminal 100 is connected, and to search among these network devices for MFPs to which the mobile terminal 100 can provide instructions. In this exemplary embodiment, SNMPv1 and SNMPv3 are each used as the search protocol.

[0041] Clock unit 304 holds time via RTC 205.

[0042] Figure 4 An example of the internal structure of MFP 110 is shown. SFP 120 and SFP 130 of this exemplary embodiment, in addition to being single-function, each have a similar structure to MFP 110.

[0043] Figure 4 The overall structure of the MFP 110 is shown. The MFP 110 includes a CPU 3020, which executes software stored in ROM 3030 or a large storage device 3110 such as a hard disk (HD). The CPU 3020 provides full control over devices connected to the system bus 3010.

[0044] RAM 3040 serves as the main memory and working area for CPU 3020. The panel controller (PANELC) 3060 controls command input from various buttons or touch panels (panels) 3070 provided in the MFP 110. The display controller (DISPC) 3080 controls the display from a display module (display) 3090, such as a liquid crystal display. The disk controller (DKC) 3100 controls a large storage device (HD) 3110.

[0045] The Network Interface Card (NIC) 3050 exchanges data with other network devices or devices such as file servers via LAN 10. The Wireless LAN (WLAN) 3400 is a wireless communication module that connects to an access point or operates in access point mode, enabling the MFP 110 to operate as an access point and connect directly to mobile terminals via wireless communication. The Printer 3200 is a printing unit that uses an electrophotographic system to print on paper. The printing system used may not be an electrophotographic system.

[0046] Scanner 3300 is an image reading unit that reads images printed on paper. In many cases, as an option, an automatic document feeder (ADF) (not shown) is mounted on scanner (image reading unit) 3300, allowing multiple originals to be read automatically. In some cases, large storage device (HD) 3110 can be used as a temporary image storage location.

[0047] Figure 9An operation screen for setting up SNMPv1 information is shown, and this screen is displayed on the display module 3090 included in MFP 110. Checkbox 901 is provided to enable / disable SNMPv1-based responses. Item 902 is provided to set the SNMPv1 community name, with "Public" set to the general default value. Drop-down menu 903 is provided to set Management Information Base (MIB) access permissions, and in addition to "Read," "Read / Write" can be selected. In this exemplary embodiment, the access requested by mobile terminal 100 is for MIB acquisition; therefore, "Read" access permission is required. In this exemplary embodiment, image processing devices 110, 120, and 130 are all configured to disable SNMPv1.

[0048] Figure 10 A setup operation screen for SNMPv3 configuration is shown, and this screen is displayed on the display module 3090 included in the MFP 110. Checkbox 1001 is provided to enable / disable SNMPv3-based responses. Item 1002 is provided to set the SNMPv3 username. There is no general default value, so the user needs to set some text string as the username. Drop-down menu 1003 is provided to set MIB access permissions, enabling settings similar to those in drop-down menu 903 described above. Drop-down menu 1004 is provided for security settings, allowing the user to select "Authentication / No Encryption" and "No Authentication / No Encryption" in addition to "Authentication / Encryption". In this exemplary embodiment, "Authentication / Encryption" is set. In "Authentication", a user attempting to obtain the device's MIB via SNMPv3 is authenticated when making the attempt. In "Encryption", packets in SNMPv3 are encrypted. Item 1005 is provided to select an authentication algorithm in the authentication settings. Item 1006 is provided to set an authentication password. Item 1007 is provided to select an encryption algorithm in the encryption settings. Project 1008 is provided to set an encryption password. In this exemplary embodiment, image processing devices 110, 120, and 130 are all configured to enable SNMPv3.

[0049] Figure 11The SNMP settings screen in MFP application 300 is shown. Button 1101 is provided to return to the previous settings screen. Item 1102 is provided to set whether SNMPv1 is used in the search for MFPs. Item 1103 is provided to set the community name when using SNMPv1, and it needs to match the corresponding setting on the MFP expected to be found in the search. Similar to item 902 on the MFP side, "Public" is set to the general default value. Item 1104 is provided to set whether SNMPv3 is used in the search for MFPs. Item 1105 is provided to set the SNMPv3 username, and it needs to match the corresponding setting on the MFP expected to be found in the search. Because there is no general default value, the user needs to set some text string. Drop-down menu 1106 is provided to set MIB access permissions. Drop-down menu 1107 is provided for security settings, and it needs to match the corresponding setting on the MFP expected to be found in the search. Additionally, this drop-down menu allows the user to select "Authentication / No Encryption" and "No Authentication / No Encryption" in addition to "Authentication / Encryption". Item 1108 is provided to select the algorithm used for authentication, and it must match the corresponding settings on the MFP expected to be found in the search. Item 1109 is provided to set the password used for authentication, and it must match the corresponding settings on the MFP expected to be found in the search. Item 1110 is provided to set the algorithm used for encryption, and it must match the corresponding settings on the MFP expected to be found in the search. Item 1111 is provided to set the password used for encryption, and it must match the corresponding settings on the MFP expected to be found in the search.

[0050] Next, we will refer to Figure 12A , Figure 12B , Figure 12C and Figure 12D To describe the MFP search screen of mobile terminal 100. Here, select Figure 11 The “use” of SNMPv1 and SNMPv3.

[0051] When display Figure 12A , Figure 12B , Figure 12C and Figure 12D When searching in each of the various screens, SNMPv1 search processing and SNMPv3 search processing begin asynchronously. Provided Figure 12A Button 1201 is used to return to the previous screen. Area 1202 displays the status of the MFP not being found immediately after the search process begins. Once a device is found, the search results are displayed as a list of found devices, arranged sequentially from top to bottom.

[0052] If MFP is not found as a search result, the following is displayed: Figure 12BThe screen displays a notification to the user that no MFP was found. If no MFP supported by MFP Application 300 is found as a search result, but there are candidate MFPs with SNMPv3 settings that can be supported by MFP Application 300, the following message is displayed: Figure 12C The screen displays a notification to the user of the status (No MFP found, but there are candidate MFPs with SNMPv3 settings that can be supported by MFP application 300, meaning the SNMPv3 configuration is incorrect). Here, the MFP supported by MFP application 300 is the model corresponding to MFP application 300, and the model to which MFP application 300 can issue operational commands. Candidate MFPs that can be supported by MFP can be determined based on the engine identifier (ID) obtained from the MFP in the SNMPv3-based search. This will be described in detail below. Figure 12C In the middle, window 1204 is displayed to ask the user whether to perform SNMPv3 settings. When "Yes" is selected in window 1204, the following appears: Figure 12D The screen shows window 1205, which is the SNMPv3 settings input window. After entering the settings and pressing OK, a re-search is performed.

[0053] Figure 5 , Figure 6 and Figure 7 Each flowchart illustrates a method for controlling the MFP search screen executed by the MFP application 300.

[0054] Reference Figure 5 The SNMPv1 search process is described. In step S501, the MFP application 300 broadcasts a packet in SNMPv1 format on LAN 10 to obtain information for determining the MIBs supported by the MFP. Examples of MIBs used to determine supported MFPs include product model names.

[0055] In step S502, the MFP application 300 analyzes the MIB of the MFP indicated by the IP address in response to the broadcast, and picks up supported MFPs based on the analysis. The product model name obtained from the MIB of the MFP in response to the broadcast is compared with a support list based on product model pre-saved by the MFP application 300 to determine the supported MFPs.

[0056] In step S503, MFP application 300 displays the MFPs picked up in step S502 in a list format in area 1202. In step S504, MFP application 300 determines whether the upper limit of the search time since the start of the search process has been reached. If the upper limit of the search time has been reached (yes in step S504), the SNMPv1 search process ends. If the upper limit of the search time has not been reached (no in step S504), the process returns to step S501. In step S502 of the second or subsequent round, responses from the same IP addresses as in the first round are excluded from the picked objects. When the process returns to step S501, a wait time of approximately a few seconds is expected because the frequent broadcasts in step S501 cause network load. Due to the network load, the upper limit of the search time is also set to tens of seconds. In the SNMPv1 search process, security settings such as authentication and passwords are not required for MIB acquisition on mobile terminal 100.

[0057] Reference Figure 6 The description describes the SNMPv3 search process, which is executed in parallel with the start of the SNMPv1 search process. In step S601, the MFP application 300 broadcasts an SNMPv3 packet on LAN 10 to obtain the engine ID. The SNMPv3 packet used to obtain the engine ID is called a discovery packet (or discovery message). In the SNMPv3 specification, a username and security settings including authentication and password are not required. Therefore, the response from the image processing device to the SNMPv3 packet used to obtain the engine ID is very fast.

[0058] In step S602, the MFP application 300 analyzes the engine ID from the response IP address (MFP) and, based on this analysis, extracts MFPs with company IDs supported by the MFP application 300 as candidates for supported MFPs (devices). The first four octets of the engine ID correspond to the company ID.

[0059] In step S603, the MFP application 300 determines whether a candidate for a supported SNMPv3 device extracted in step S602 exists. If a candidate exists (yes in step S603), the process proceeds to step S604. If a candidate does not exist (no in step S603), the process proceeds to step S608.

[0060] If a candidate MFP is found in step S603, the MFP application 300 cannot determine whether the candidate is a supported MFP because no information representing the MIB was obtained in this step. Therefore, in step S604, the MFP application 300 sends an SNMPv3 packet for obtaining the MIB to the IP address of the MFP picked up as a candidate in step S602 to determine whether the MFP is a supported MFP. Obtaining the MIB requires a username and security settings including authentication and password. Similar to step S501 in the SNMPv1 search process, the MIB to be obtained is the product model name.

[0061] In step S605, the MFP application 300 acquires the MIB and determines whether a supported device exists based on the acquired MIB. If a response is received within a timeout period of approximately a few seconds, the MFP application 300 determines that a supported device exists. If a supported device exists ("Yes" in step S605), the process proceeds to step S606. If no supported device exists ("No" in step S605), the process proceeds to step S607. In step S606, the MFP application 300 displays the devices identified as supported devices in a list format.

[0062] In step S607, the MFP application 300 sets a flag indicating a mismatch in SNMPv3 configuration information. Hereinafter, a device with this flag set will be referred to as a supported device candidate with SNMPv3 configuration. This device is one that has SNMPv3 configuration and can communicate with mobile terminal 100, but is not recognized as a supported device due to improper settings on mobile terminal 100, such as SNMPv3 security settings. Examples of improper configuration include: no settings are entered, resulting in insufficient configuration information due to reasons such as blank spaces; and settings are entered, but the configuration information on mobile terminal 100 differs from the device's configuration information.

[0063] In step S608, MFP application 300 sets a flag indicating that there is no information about an SNMPv3 device.

[0064] Figure 7 This is a flowchart illustrating the entire search process. As an example, a notification is issued when, although the user selects "Use" SNMPv3 on mobile terminal 100, no SNMPv3 security settings have been configured. The flowchart begins with the state where the user provides instructions for device search on mobile terminal 100.

[0065] When a search instruction is provided, in step S701, execution is performed. Figure 5The SNMPv1 search process is shown. In step S702, the following steps are performed: Figure 6 The SNMPv3 search process is shown. Steps S701 and S702 are executed in parallel.

[0066] In step S703, it is determined whether a supported SNMP device was found in each of steps S701 and S702. If a supported SNMP device was found ("Yes" in step S703), the process ends. If no supported SNMP device was found ("No" in step S703), the process proceeds to step S704.

[0067] In step S704, it is determined whether there are any supported device candidates with SNMPv3 settings. Specifically, it is determined whether there is a flag indicating a mismatch in SNMPv3 settings, set in the SNMPv3 search process in step S702. If a flag indicating a mismatch in SNMPv3 settings exists ("Yes" in step S704), the process proceeds to step S705. If no flag indicating a mismatch in SNMPv3 settings exists ("No" in step S704), the process ends.

[0068] In step S705, it is determined whether the procedure has been performed. Figure 11 The SNMPv3 settings are shown. For example, this determination is made by checking whether an item such as 1002, used to set the username for SNMPv3, is left blank. If the setting is made ("Yes" in step S705), the process ends. If the setting is not made ("No" in step S705), the process proceeds to step S706.

[0069] In step S706, a warning message is displayed (such as...). Figure 12C The message shown indicates that SNMPv3 settings have not been performed, and also displays a button asking whether to perform the settings.

[0070] In step S707, it is determined whether the user pressed the button for setting up (SNMPv3 setup). If the button for setting up was pressed ("Yes" in step S707), the process proceeds to step S708. If the button was not pressed ("No" in step S707), the process ends.

[0071] In step S708, the setting input window is displayed ( Figure 12D ).

[0072] In step S709, it is determined whether the input in the settings input window displayed in step S708 is complete. If the OK button is pressed, i.e., if the input is complete ("Yes" in step S709), the process returns to step S701, allowing a re-search. If a user's cancellation operation is detected, i.e., if the input is not complete ("No" in step S709), the process ends. This process allows notification to users who are unaware of settings such as security settings when searching for devices based on SNMPv3, indicating that such settings are necessary. Because notification is only provided when a supported device candidate with SNMPv3 settings exists, unnecessary notifications are prevented. If SNMPv3 settings such as security settings are performed on the mobile terminal 100 in step S705, the process ends. However, if there is no response from a supported device despite the settings being performed (MIB cannot be obtained), the SNMPv3 settings such as security settings may be incorrect. Therefore, in the case of SNMPv3 settings being performed in step S705, a warning can be displayed to indicate that... Figure 11 The settings entered on the screen may be incorrect.

[0073] The timing for displaying warning messages is not limited to the timings mentioned above. For example, when no warning message is displayed... Figure 11 If the user provides a command to start the device search process when the settings for items such as security in the SNMPv3 settings screen are blank, a warning message can be displayed at the time the user provides the search command. Furthermore, although the processes in step S701 and step S702 run in parallel, at the time when no supported device is found after completing the SNMPv1 search in step S701, it can be checked whether SNMPv3 settings such as security have been performed, and if not, a warning message can be displayed.

[0074] In the configuration described in the first exemplary embodiment, for example, even if a device with SNMPv1 settings can be found, a screen for prompting SNMPv3 settings can be displayed.

[0075] Even after a device with SNMPv1 settings is found, the expected printer is not found for the user who wants to search for devices with SNMPv3 settings, so a second search is performed. However, no matter how many times the search is performed, a device with SNMPv3 settings cannot be found because SNMPv3 settings, such as for security features, have not yet been configured.

[0076] Therefore, in the second exemplary embodiment, if an instruction for re-searching is provided even if a device with SNMPv1 settings is found, a device that is expected to have SNMPv3 settings is determined, and the user is notified that SNMPv3 settings are necessary.

[0077] Figure 13A and Figure 13B Each shows a search screen of the second exemplary embodiment. Figure 13A This is the screen to be displayed when the search is complete and only devices with SNMPv1 settings have been searched. A re-search button 1301 is provided to initiate a re-search, issuing a command to perform a device search again. If SNMPv3 candidate devices are present when the re-search button 1301 is pressed, the following screen will be displayed: Figure 13B The screen in the program informs the user that SNMPv3 settings are required.

[0078] The basic structure of the second exemplary embodiment is similar to that of the first exemplary embodiment. Therefore, only the search processing flow that includes points different from the first exemplary embodiment will be described. Figure 8 The flowchart in the document. Figure 8 The basic structure of the flowchart in the diagram is similar to Figure 7 The basic structure of the flowchart in the diagram.

[0079] In the second exemplary embodiment, during the timing of step S803, it is determined whether there are any supported device candidates with SNMPv3 settings. Specifically, it is determined whether there is a flag set in the SNMPv3 search process in step S702 indicating a mismatch in SNMPv3 setting information. If a candidate exists ("Yes" in step S803), the process proceeds to step S804. If no candidate exists ("No" in step S803), the process ends.

[0080] In step S804, it is determined that in Figure 13A The system checks whether the re-search button 1301 has been pressed on the display screen. If a press of the re-search button 1301 is detected ("Yes" in step S804), the process proceeds to step S705. If no press of the re-search button 1301 is detected ("No" in step S804), the process ends. Similar to the first exemplary embodiment, if SNMPv3 settings are performed in step S705, a warning message may be displayed to indicate that the settings may be incorrect.

[0081] Even if a device with SNMPv1 settings is found, if the expected device is one with SNMPv3 settings and the SNMPv3 settings for items such as security are incorrect, the above process allows the user to be notified that SNMPv3 settings are necessary during a re-search. Furthermore, a warning message is displayed here when the user presses the re-search button, but this is not limiting. A warning message can be displayed to indicate that no SNMPv3 settings were performed even if a device with SNMPv1 settings could be found. (Supported devices exist, but are not displayed in the search results list because the MIB was not obtained.) Figure 11 The SNMPv3 security settings in the screen are incorrect or not configured correctly.

[0082] [Other exemplary embodiments]

[0083] If the user selects "Use" SNMPv3 for searching on mobile terminal 100 but does not configure SNMPv3 settings such as security, when the user... Figure 11 Warnings can be displayed on the SNMP setup screen to draw the user's attention to this status. For example, one could construct a screen where, after the user selects "Use" in item 1104 (which sets whether to use SNMPv3), a warning is displayed when the user closes the setup screen or changes screens without configuring items such as the username.

[0084] In the first and second exemplary embodiments, the image processing device (MFP) is used as a communication partner of the information processing device, but this is not limiting. The communication partner can be any type of device, as long as it is an external device capable of communicating with the information processing device.

[0085] Other embodiments

[0086] Embodiments of this disclosure can also be implemented by a computer that reads and executes computer-executable instructions (e.g., one or more programs) recorded on a storage medium (also more fully referred to as a "non-transitory computer-readable storage medium") to perform one or more functions in the above embodiments and / or includes a system or apparatus comprising one or more circuits (e.g., application-specific integrated circuits (ASICs)) for performing one or more functions in the above embodiments. Furthermore, embodiments of the invention can be implemented using a method by which the computer of the system or apparatus, for example, reads and executes the computer-executable instructions from the storage medium to perform one or more functions in the above embodiments and / or controls the one or more circuits to perform one or more functions in the above embodiments. The computer may include one or more processors (e.g., central processing unit (CPU), microprocessor unit (MPU)) and may include separate computers or a network of separate processors to read and execute the computer-executable instructions. The computer-executable instructions may be provided to the computer, for example, from a network or the storage medium. The storage medium may include, for example, a hard disk, random access memory (RAM), read-only memory (ROM), the memory of a distributed computing system, or an optical disc (such as a compact disc (CD), a digital versatile optical disc (DVD), or a Blu-ray disc (BD)). TM One or more of the following: flash memory devices and memory cards.

[0087] The embodiments of the present invention can also be implemented by providing software (programs) that perform the functions of the above embodiments to a system or device via a network or various storage media, and the computer or central processing unit (CPU) or microprocessor unit (MPU) of the system or device reads out and executes the program.

[0088] While this disclosure includes embodiments, it should be understood that this disclosure is not limited to the disclosed exemplary embodiments. The scope of the appended claims should be interpreted in the broadest possible sense to encompass all such variations and equivalent structures and functions.

Claims

1. A control method of an information processing apparatus that is capable of communicating with external apparatuses in Simple Network Management Protocol version 3 and executing an application, the control method comprising: acquiring engine identifications from one or more external apparatuses by broadcasting a request for acquiring the engine identifications; based on the acquired engine identifications, transmitting a request for acquiring management information base (MIB) information to an external apparatus configured to transmit an engine identification including predetermined information, and acquiring the MIB information; and displaying external apparatuses that the application supports as search results based on the acquired MIB information, wherein external apparatuses that the application does not support are not displayed as the search results based on the acquired MIB information, and transmitting a print job to an external apparatus that is searched out from among the external apparatuses that the application supports and displayed as the search results, as an external apparatus to which an instruction can be provided.

2. The control method according to claim 1, wherein the information processing apparatus is capable of a first setting with respect to Simple Network Management Protocol version 3, and at least one of the external apparatuses is capable of a second setting with respect to Simple Network Management Protocol version 3, the control method further comprising: broadcasting, in Simple Network Management Protocol version 3, a packet for requesting an engine identification that can be received regardless of a content of the first setting; based on engine identifications received from the external apparatuses that respond to the broadcast, making a first determination with respect to whether the external apparatuses that respond to the broadcast are candidates for external apparatuses that the application supports; and transmitting, in Simple Network Management Protocol version 3, a packet for requesting MIB information that can be received in a case where a content of the first setting satisfies a predetermined condition based on the second setting, to the external apparatuses determined to be candidates in the first determination, and wherein in a case where the MIB information is not received after the transmission, a notification indicating that the first setting is inappropriate is provided.

3. The control method according to claim 2, wherein The first setting and the second setting include at least one of a setting of a user name, a setting of an access right to the MIB information, an authentication setting, and an encryption setting.

4. The control method according to claim 3, wherein The authentication setting includes at least one of an authentication algorithm and an authentication password and is a setting that authenticates a user who receives the MIB information, and the encryption setting includes at least one of an encryption algorithm and an encryption password and is a setting that encrypts a packet for receiving the MIB information.

5. The control method according to claim 2, wherein The predetermined condition includes a match between the external apparatuses and the information processing apparatus at least in terms of the authentication algorithm and the authentication password or in terms of the encryption algorithm and the encryption password.

6. The control method according to claim 2, the control method further comprising: based on the MIB information, making a second determination with respect to whether the external apparatuses determined to be candidates are external apparatuses that the application supports.

7. The control method according to claim 1, wherein In a case where the information indicating the predetermined product model name is included in the acquired MIB information, the external device corresponding to the MIB information is determined to be an application-supporting external device and displayed as a search result, and in a case where the information indicating the predetermined product model name is not included in the acquired MIB information, the external device corresponding to the MIB information is determined to be an application-non-supporting external device and not displayed as a search result.

8. The control method according to claim 1, wherein The predetermined information is a predetermined company identification.

9. The control method according to claim 2, wherein, in the broadcasting, a packet for receiving third information capable of being received regardless of settings is broadcasted in Simple Network Management Protocol version 1, the control method further includes: based on the third information, a third determination is made as to whether an external device responding to the broadcasting in Simple Network Management Protocol version 1 is an application-supporting external device, and wherein the notification is provided in response to a predetermined instruction being received from a user even in a case where the external device responding to the broadcasting in Simple Network Management Protocol version 1 is determined to be an application-supporting external device in the third determination.

10. The control method according to claim 1, wherein The application is an application capable of commanding an external device to perform printing.

11. An information processing apparatus capable of communicating with an external device in Simple Network Management Protocol version 3 and executing an application, the information processing apparatus comprising: an acquisition unit configured to acquire engine identifications from one or more external devices by broadcasting a request for acquiring the engine identifications; a processing unit configured to, based on the acquired engine identifications, transmit a request for acquiring management information base (MIB) information to an external device configured to transmit an engine identification including predetermined information, and acquire the MIB information; and a display unit configured to display, as a search result based on the acquired MIB information, an application-supporting external device, wherein an application-non-supporting external device is not displayed as the search result based on the acquired MIB information, and a transmission unit configured to transmit a print job to an external device that is an external device to which an instruction can be provided, searched from among the application-supporting external devices displayed as the search result.

12. A non-transitory computer-readable storage medium storing a program executed by a computer of an information processing apparatus capable of communicating with an external device in Simple Network Management Protocol version 3 and executing an application, wherein the program causing the computer to: acquire engine identifications from one or more external devices by broadcasting a request for acquiring the engine identifications; based on the acquired engine identifications, transmit a request for acquiring management information base (MIB) information to an external device configured to transmit an engine identification including predetermined information, and acquire the MIB information; and display, as a search result based on the acquired MIB information, an application-supporting external device, wherein an application-non-supporting external device is not displayed as the search result based on the acquired MIB information, and transmit a print job to an external device that is an external device to which an instruction can be provided, searched from among the application-supporting external devices displayed as the search result.

Images