Network devices, methods performed by network devices, and programs

Abstract

This technology provides the ability to properly configure network devices regardless of their current state. [Solution] The network device (MFP102) provides a setting screen to a web browser via a web server for manipulating the setting values ​​of multiple setting items, and reflects the setting values ​​in the network device according to the manipulation of the setting values. The network device provides a website via a web server for installing software as a progressive web application on the user terminal to provide the function of manipulating the setting values ​​of at least some items. Then, regardless of whether the setting screen is provided or not, the network device receives the content of the setting value manipulation performed using the progressive web application from the user terminal 104 (S815) and reflects the setting values ​​(S816).

Description

Technical Field

[0001] This disclosure relates to a technique for information processing in network devices.

Background Art

[0002] Network devices such as image forming apparatuses are provided with a function (hereinafter, Remote UI) that allows a user to access the network device via a network from a terminal and check the operating status of the device and perform various settings. The user can use the Remote UI by accessing a predetermined URL of a Web server operating inside the network device using a Web browser having an RSS function or the like.

[0003] Patent Document 1 discloses a technique for providing, in the Remote UI provided by an image forming apparatus, the job status of only the print jobs executed by the user who made the acquisition request among all print jobs to the user who made the acquisition request for the occurrence status of an error or the job status.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] The Remote UI allows network device administrators and general users to change the settings of those devices. However, if communication with the device is not possible, such as when the network device is powered off, the Remote UI cannot be used. As a result, administrators and general users cannot change settings when they want to, and are forced to wait for the device to be operational before opening the settings screen in the Remote UI and making the changes.

[0006] This disclosure provides a technology that enables proper configuration of network devices regardless of the state of the network devices. [Means for solving the problem]

[0007] A network device according to one embodiment of the present disclosure includes a web server, a provisioning means that provides a setting screen for manipulating the setting values ​​of a plurality of setting items for the network device to a web browser via the network, and a reflection means that reflects the setting values ​​on the network device in accordance with the manipulation of the setting values. The provisioning means further provides a website for the web server to install software as a progressive web application on a user terminal for providing a function to manipulate the setting values ​​of at least some of the plurality of setting items. The reflection means reflects the setting values ​​on the network device in response to receiving from the user terminal via the network the content of the manipulation of the setting values ​​performed using the progressive web application, regardless of whether the network device provides the setting screen. [Effects of the Invention]

[0008] According to this disclosure, network devices can be configured appropriately regardless of the state of the network devices. [Brief explanation of the drawing]

[0009] [Figure 1] This diagram shows an example of the system configuration. [Figure 2] This block diagram shows an example of the hardware configuration of each device that makes up the system. [Figure 3] This is a block diagram showing an example of the module configuration for MFP software. [Figure 4] This is a block diagram showing an example of a push server software module configuration. [Figure 5] A block diagram showing an example of a web browser's software configuration. [Figure 6] This is a sequence diagram showing the process during PWA installation. [Figure 7] This is an example of a screen displayed by a web browser. [Figure 8] This is an example of a remote UI screen when a PWA displays the screen shown in Figure 7. [Figure 9] This is an example of a PWA screen that requests permission to receive push notifications. [Figure 10] This is a sequence diagram of the process for changing the settings of the MFP in the first embodiment. [Figure 11] This is a sequence diagram showing the continuation of Figure 10. [Figure 12] This is an example of a settings change screen displayed by a PWA on the S804. [Figure 13] This is an example of a screen displayed by a PWA on the S807. [Figure 14] This is an example of the configuration changes that a PWA remembers on the S805. [Figure 15] (A) is an example of a notification indicating that the configuration change received in S804 has been executed on the MFP and completed, and (B) is an example of a notification displayed in S832. [Figure 16] (A) is an example of a restart screen displayed in S834, and (B) is an example of a restart screen including a confirmation dialog displayed in S836. [Figure 17] This is a sequence diagram showing the process of changing the settings of the MFP in the second embodiment. [Figure 18] It is a sequence diagram showing the processing from when the power of the MFP is turned on. [Figure 19] It is a sequence diagram showing the processing when the content of the operation setting is Pattern 1. [Figure 20] It is a sequence diagram showing the processing when the content of the operation setting is Pattern 3. [Figure 21] It is an example of an operation setting screen when the power of the MFP is turned on. [Figure 22] (A) is an example of a notification indicating that the power of the MFP has been turned on, and (B) is an example of a notification indicating that the restart of the MFP to reflect the setting change has been completed. [Figure 23] It is a sequence diagram showing the processing when the Web browser is launched in the third embodiment. [Figure 24] It is a sequence diagram showing the processing started when communication with the MFP could not be established at S806 in the fourth embodiment.

Embodiments for Carrying Out the Invention

[0010] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings. Not all of the plurality of features in the embodiments of the present disclosure are essential, and the plurality of features may be arbitrarily combined. Also, the configurations shown in the following embodiments are merely examples, and the present disclosure is not limited to the illustrated configurations. By assigning the same reference numerals to the same or similar configurations in the drawings, duplicate descriptions are omitted.

[0011] [[ID=][First Embodiment] FIG. 1 is a diagram showing an example of the system configuration of a system 100 according to an embodiment of the present disclosure. The system 100 includes an MFP (Multi Function Peripheral) 102, a push server 103, and a terminal 104. These MFP 102, push server 103, and terminal 104 are connected to a network 101.

[0012] A network is a communication network implemented using one or more of the following: LAN, WAN, telephone lines, dedicated digital lines, ATM, frame relay lines, cable television lines, wireless lines for data broadcasting, etc. A LAN may be built within a company.

[0013] MFP102 is a Multi-Function Peripheral (MFP), a type of network device, and has remote UI functionality. Push Server 103 is a server provided by web browser vendors, etc., to offer push notification services via web browsers. Terminal 104 is an electronic device used by users who manage or use MFP102 for work or other purposes. Terminal 104 can be, for example, a tablet, smartphone, or PC. Users of Terminal 104 can use the MFP102's remote UI via a web browser running on Terminal 104.

[0014] Figure 2 is a block diagram showing an example of the hardware configuration of the MFP 102, push server 103, and terminal 104. Of these blocks, the scanner device 208 and printer device 209 are mainly devices provided by the MFP 102.

[0015] The CPU 201 comprehensively controls all hardware components and controls each part connected to the bus 200 to execute various functions such as printing and scanning. The ROM 202 is a memory dedicated to data reading; for example, in the MFP 102, it stores the basic control program for the MFP 102. The RAM 203 is a memory that allows data reading and writing, and is used, for example, as the working memory for the CPU 201.

[0016] In addition to the CPU201, other PLDs (Programmable Logic Devices) such as FPGAs (Field Programmable Gate Arrays) may be used. Alternatively, ASICs (Application Specification Integrated Circuits) or DSPs (Digital Signal Processors) may be used.

[0017] The storage device 204 is an HDD or SSD, and is used as a storage area for the program itself executed by the CPU 201, as well as the data used by each program. In the case of the MFP 102, the storage device 204 is also used as a storage area for images to be printed or scanned. The storage device 204 may also be a device that can read / write data by inserting external media such as a CD, DVD, or memory card.

[0018] The communication device 205 connects to the network 101 and enables network communication with other devices and services. In the MFP 102, the communication device 205 also receives print data and scan data transmitted from the terminal 104.

[0019] The input device 206 is an operating unit that accepts input operations of characters and data by the user. The input device 206 may be, for example, a keyboard, mouse, hard keys, or touch panel.

[0020] The display device 207 is a device for displaying various screens, such as a liquid crystal display or a touch panel. The user can give instructions via the input device 206 on the user interface (UI) screen displayed on the display device 207 to perform job execution instructions and settings on the MFP 102. In addition, the input device 206 and the display device 207 may be integrated into a single unit by using a touch panel.

[0021] Figure 3 shows an example of the software module configuration of the MFP102. The software configuration shown in Figure 3 is realized when the CPU 201 reads a program stored in, for example, ROM 202 into RAM 203 and executes it.

[0022] The remote UI request processing unit 301 receives requests from the Web browser 500 of the terminal 104 (described later) and provides information for displaying a menu screen for managing the MFP 102, as well as status information of the MFP 102 obtained from the status management unit 303 (described later). The remote UI request processing unit 301 also executes the requested configuration changes. The remote UI request processing unit 301 is primarily an example of a means of providing a configuration screen for manipulating the setting values ​​of multiple configuration items for a network device to a Web browser via the network.

[0023] In this embodiment, when changing the settings of the MFP102, a restart of the MFP102 may or may not be necessary for the changes to take effect, depending on the settings. This is because if a restart were required to reflect all setting changes, the MFP102 would be operating while the settings were being applied, potentially causing problems with its own operation.

[0024] The notification transmission unit 302 receives a push notification request from the event management unit 304 (described later) and issues a push notification to the pre-registered notification target terminal 104. When the notification transmission unit 302 receives a push notification request from the event management unit 304, it edits the content into a format for sending a request to the push server 103 and then sends it to the push server 103. The notification transmission unit 302 is an example of a notification means that sends push notifications to user terminals via the network in response to events occurring within a network device.

[0025] The status management unit 303 controls the printing of the MFP102 and manages abnormal conditions, as well as managing counter information and notification information. Counter information includes, for example, the number of pages printed by the MFP102, the degree of wear on parts, and wear information indicating the remaining amount of consumables such as toner bottles.

[0026] The event management unit 304 receives events occurring in the MFP102 and manages event information. The event information managed by the event management unit 304 includes events such as the MFP102's power on / off, print job events issued by users, and errors (sometimes called failures). For example, MFP102 errors include high-priority errors such as hard disk errors, paper jams, and warning-level errors such as toner low. It also manages event information such as toner bottle replacement and firmware updates. Furthermore, the event management unit 304 detects the occurrence of an event and, if necessary, requests a push notification from the notification transmission unit 302 corresponding to the detected event.

[0027] The configuration management unit 305 manages various settings of the MFP 102 and responds to and modifies various setting information in response to requests from the remote UI request processing unit 301 and operations on the input device 206. The configuration management unit 305 also handles the process of restarting the MFP 102 in response to a request from the remote UI request processing unit 301. The configuration management unit 305 is an example of a means for reflecting the manipulated setting value to the network device in accordance with the operation of the setting value. The configuration management unit 305 is also an example of a means for initiating the restart process of the network device.

[0028] Figure 4 shows an example of the software module configuration of the push server 103. The push server 103 includes a communication unit 401, a storage unit 402, a request receiving unit 403, a response generation unit 404, a notification target management unit 405, and a notification forwarding unit 406.

[0029] The communication unit 401 has the function of communicating with the MFP 102 and the terminal 104. Specifically, the communication unit 401 receives push notification requests sent from the MFP 102 and sends push notifications to the web browser 500 running on the terminal 104, which will be described later.

[0030] The memory unit 402 controls the storage of information in the RAM 203, ROM 202, and storage device 204. In this embodiment, the information that can be stored includes information about the target terminal for push notifications and information about push notification requests.

[0031] The request receiving unit 403 receives requests from the web browser 500 running on terminal 104 to register as a target for push notifications, and push notification requests from the notification sending unit 302.

[0032] The response generation unit 404 sends a push subscription object, described later, to the requesting web browser 500 as a response to the request to register as a target for push notifications.

[0033] The notification target management unit 405 manages information about devices registered as targets for push notifications. The information about devices registered as targets for push notifications includes an identifier for identifying the target device and a push subscription object. In this embodiment, device 104 is registered as a target for push notifications.

[0034] The notification forwarding unit 406 forwards the push notification request to the notification target terminal based on the endpoint information included in the push notification request received from the notification sending unit 302. In addition to a notification informing that the MFP 102 has been powered on according to this embodiment, notifications may also include, for example, information about errors that have occurred in the MFP 102, information about the wear level of consumables, or announcements from the administrator.

[0035] Figure 5 is a block diagram showing an example of the software configuration of a web browser 500 operating on terminal 104. The software configuration shown in Figure 5 is realized by the CPU 201 reading a program stored, for example, in ROM 202 or storage device 204 into RAM 203 and executing it.

[0036] In this embodiment, the Web browser 500 is assumed to support Progressive Web Apps (PWAs). A PWA is a technology that allows a website to be used as if it were a native app, and is a type of application. A PWA is a (web) application that possesses at least some of the functionality that the MFP102 can provide via the network and the functionality that it provides on the remote UI. The MFP102 provides the remote UI to a Web browser that accesses the address (URL, IP address, etc.) assigned to the remote UI of its device. The user can install the PWA for the MFP102 in this embodiment on the terminal 104 via this remote UI. Unlike conventional native apps, users do not need to access an app store to download a PWA; by accessing the website that provides the PWA, the user can easily install and use the PWA on the spot via a Web browser. In addition, similar to native apps, it is possible to add an icon for using the PWA to the desktop or home screen of the terminal 104.

[0037] The web page processing unit 501 performs processing such as communication with the remote UI request processing unit 301 of the MFP 102 and displaying web content received from the remote UI request processing unit 301, in accordance with instructions received from the user of terminal 104. Web content is written using, for example, HTML (HyperText Markup Language), JavaScript, and CSS (Cascading Style Sheets). Furthermore, web content also includes components of a PWA, such as a Service Worker (a script that runs as a background process) and a manifest file (a file that describes the PWA installation settings).

[0038] The ServiceWorker processing unit 502 executes the Service Worker, which is a component of the PWA, received from the MFP102's remote UI request processing unit 301.

[0039] The data storage area 503 is an area for temporarily or permanently storing data such as web content received from the remote UI request processing unit 301 of the MFP 102 and the content of instructions received from the user of the terminal 104. Specifically, the data storage area 503 is located on the RAM 203 or storage device 204 of the terminal 104. The web page processing unit 501 and the ServiceWorker processing unit 502 also perform processing while utilizing the data storage area 503 as appropriate.

[0040] Figure 6 shows the sequence of events from installing the PWA from the MFP102 to the terminal 104, enabling it to receive push notifications from the MFP102. In Figure 6, user 600 is the user of terminal 104, and the settings of the MFP102 are changed via terminal 104.

[0041] Of the processes shown in Figure 6, the processes executed by MFP102 are realized by the CPU201 of MFP102 reading the software module programs shown in Figure 3, which are stored in the storage device 204, into the RAM203 and executing them. Similarly, the processes executed by push server 103 are realized by the CPU201 of push server 103 reading the software module programs shown in Figure 4, which are stored in the storage device 204, into the RAM203 and executing them. Also similarly, the steps executed by terminal 104 are realized by the CPU201 of terminal 104 reading the software module programs shown in Figure 5, which are stored in the storage device 204, into the RAM203 and executing them.

[0042] In S601, user 600 instructs the web browser 500 running on terminal 104 to access the remote UI of MFP 102. Specifically, user 600 instructs the web browser 500 to access the remote UI of MFP 102 by entering the address information assigned to the remote UI on MFP 102 into the address bar of the web browser 500.

[0043] In S602, the web page processing unit 501 of the web browser 500 running on terminal 104 requests the web content of the remote UI from the remote UI request processing unit 301 of MFP 102, according to the address information entered in S601.

[0044] In S603, the MFP102's remote UI request processing unit 301 responds with the requested web content. The web content responded with includes screen information of the remote UI displayed on the web browser 500, as well as a manifest file and Service Worker for installing and running the remote UI as a PWA.

[0045] In S604, the Web page processing unit 501 of terminal 104 analyzes the content of the Web content acquired in S603 and displays the remote UI screen on the Web browser 500.

[0046] In S605, the Web page processing unit 501 of terminal 104 registers the Service Worker included in the Web content acquired in S603 in the data storage area 503. The Service Worker registered here is a script that defines behaviors such as push notification functionality, which is a characteristic of PWAs, and offline operation, and is executed in the background by the Service Worker processing unit 502. In other words, the Service Worker processing unit 502 enables push notifications for installed PWAs and other functions via the Service Worker running in the background, even when the user is not connected to the remote UI via a web browser.

[0047] In addition, the Service Worker may contain instructions related to cache control. In that case, the Service Worker processing unit 502 stores the web content acquired by S603 as a cache in the data storage area 503 according to the instructions during registration.

[0048] In S606, the web page processing unit 501 of terminal 104 displays a screen prompting the installation of the PWA on the web browser 500, according to the manifest file included in the web content acquired in S603.

[0049] Figure 7 shows an example of a screen 711 displayed on the web browser 500 in S606. Button 731 is displayed when the web content includes a manifest file. Dialog 733 is displayed to confirm with user 600 whether or not to install the PWA. In this embodiment, dialog 733 is automatically displayed when the web content includes a manifest file. However, dialog 733 may also be displayed when button 731 is pressed by user 600.

[0050] Button 735 is the button that user 600 presses when installing the PWA. Button 737 is the button that user 600 presses when not installing the PWA. In this embodiment, we will proceed with describing the case in which user 600 presses button 735 to start the PWA installation.

[0051] In S607, user 600 presses button 735, instructing the web browser 500 running on terminal 104 to install the PWA.

[0052] In S608, the Web page processing unit 501 of terminal 104 installs the web content of the remote UI obtained in S603 as a PWA according to the contents of the manifest file. From this point onward, terminal 104 will be described with the PWA running on the Web browser 500 as the main function. Note that when installing the PWA, the Web page processing unit 501 may also generate an icon on the desktop or home screen of terminal 104 to launch the PWA.

[0053] Figure 8 shows an example of the remote UI screen displayed by a PWA when it is installed. The content displayed on screen 751 in Figure 8 is equivalent to that displayed on screen 711 in Figure 7, but it differs from the display of a normal web browser, for example, the address bar is not displayed, making it appear as if you are operating a native application. Note that when user 600 launches an installed PWA, screen 751 shown in Figure 8 is displayed on the web browser 500.

[0054] In S609, the PWA running on terminal 104 displays a message to user 600 requesting permission to receive push notifications.

[0055] Figure 9 shows an example of a screen displayed by the PWA in S609 requesting permission to receive push notifications. In Figure 9, dialog 771 is displayed to request permission from user 600 to receive push notifications. If user 600 wants to allow receiving push notifications, they press the allow button 773. If user 600 does not want to allow receiving push notifications, they press the block button 775. In this embodiment, we will proceed with the explanation of the case where user 600 presses the allow button 773 to allow receiving push notifications.

[0056] In S610, user 600 presses the allow button 773, instructing the web browser 500 to allow the reception of push notifications.

[0057] In S611, the web browser 500 sends a request to the push server 103 to register the PWA running on terminal 104 as a target for push notifications.

[0058] In S612, when the request receiving unit 403 of the push server 103 receives the request in S611, it transmits its contents to the notification target management unit 405. The notification target management unit 405 then registers the PWA running on terminal 104 as a target for push notifications and issues a push subscription object. A push subscription object is information that associates the sender and receiver of a push notification and includes the information necessary for the notification sending unit 302 of the MFP 102, described later, to send a push notification to the PWA running on terminal 104. Specifically, the push subscription object includes the URL of the push server 103 and endpoint information of the push server 103, which consists of different endpoint texts for each target of the push notification.

[0059] In S613, the response generation unit 404 of the push server 103 sends the push subscription object issued in S612 to the PWA that sent the request, as a response to the request received in S611.

[0060] In S614, the PWA sends the received push subscription object to the remote UI request processing unit 301 of the MFP102.

[0061] In S615, the remote UI request processing unit 301 of the MFP102 registers the received push subscription object with the notification sending unit 302. The push subscription object registered here will be used by the notification sending unit 302 of the MFP102 when it requests the push server 103 to send a push notification to the target terminal 104.

[0062] Next, the processing sequence when a user 600 changes the settings of the MFP 102 via PWA while the MFP 102 is powered off will be explained using Figures 10 and 11. Of the processes shown in Figures 10 and 11, the processes executed by the MFP 102 are realized by the CPU 201 of the MFP 102 reading the software module program shown in Figure 3, which is stored in the storage device 204, into the RAM 203 and executing it. Similarly, the processes executed by the push server 103 are realized by the CPU 201 of the push server 103 reading the software module program shown in Figure 4, which is stored in the storage device 204, into the RAM 203 and executing it. Also similarly, the processes executed by each device of the terminal 104 are realized by the CPU 201 of the terminal 104 reading the software module programs shown in Figure 5, which are stored in the storage device 204, into the RAM 203 and executing them.

[0063] In S801, user 600 gives an instruction via PWA running on terminal 104 to display a settings change screen for changing the settings of, for example, MFP102.

[0064] In S802, before communicating with MFP102, the PWA displays the configuration change screen using the content information stored in the data storage area 503. This operation is intended to improve the response performance to display requests from user 600.

[0065] In S803, the PWA requests the MFP102 to retrieve the latest configuration change screen. If the MFP102 is operating normally, the remote UI request processing unit 301 receives this request and responds. However, in this case, the MFP102 is powered off, so this request is not received and no response is given.

[0066] In S804, user 600 enters settings to change on the settings change screen displayed by the PWA.

[0067] Figure 12 shows an example of a settings change screen displayed by the PWA on S804. The settings change screen 911 in Figure 12 is a screen for registering the destination settings for the function of sending scanned images provided by the MFP102. The settings change screen 911 is an example of a settings screen that includes multiple setting items for manipulating setting values. The type selection object 931 is a group of radio buttons for selecting the sending method. For example, email, I-fax, and file can be selected. The input form object 933 is an input field for entering the recipient's name, address, etc. The OK button 935 is a button for confirming the selection and input made on the settings change screen 911 and requesting the settings change from the MFP102. The cancel button 937 is a button for discarding the selected and entered information and returning to the screen before transitioning to the settings change screen 911. Here, we will proceed with the explanation assuming that the user 600 has made selections and inputs on the settings change screen 911 and pressed the OK button 935.

[0068] The address book settings screen shown in Figure 12 is just one example of a settings screen used to manipulate the MFP102's settings. Other settings screens include environment settings and application settings for the MFP102. Address book settings are one of the application settings.

[0069] In S805, the PWA running on terminal 104 stores the entered configuration changes in data storage area 503.

[0070] Figure 14 shows an example of the configuration changes that the PWA stores in S805. "Configuration Category" represents the target of the settings in MFP102. "Operation" indicates what kind of change will be made (e.g., add, modify, delete, etc.), and in this case, it indicates that the operation is to add a destination to the address book. Note that "Type" and "Name" are address book setting items and are the content selected or entered on the configuration change screen 911.

[0071] In S806, the PWA requests a configuration change from the MFP102. If the MFP102 is operating normally, the remote UI request processing unit 301 receives this request and the configuration change is performed. However, in this case, the MFP102 is powered off, so this request is not received and no configuration change is performed.

[0072] In S807, the PWA detects that there is no response to the request from S806 due to a timeout or other reason, and displays a message indicating that it was unable to communicate with MFP102.

[0073] Figure 13 shows an example of a screen displayed by the PWA on the S807. In Figure 13, dialog 951 is the area that displays that communication with the MFP102 failed. As shown in the example, dialog 951 can also display that the settings will be automatically configured when communication with the MFP102 is restored.

[0074] Figure 11 shows the processing sequence from the point after S806 when the MFP102 is powered on. More precisely, Figure 11 shows the sequence from the point when the MFP102 is powered on until each software module of the MFP102 shown in Figure 3 becomes operational. In this embodiment, this state is referred to as the point when the power is turned on.

[0075] In S811, the event management unit 304 of the MFP102 detects that the power has been turned on as an event within the MFP102 and requests the notification transmission unit 302 to send a push notification of the power-on event.

[0076] In S812, the notification transmission unit 302 sends a push notification request to the push server 103 to inform the registered notification target terminal 104 that the MFP 102 has been powered on.

[0077] In S813, the request receiving unit 403 of the push server 103 receives the push notification request from S812 and sends its contents to the notification forwarding unit 406. Based on the information contained in the push notification request, the notification forwarding unit 406 forwards a push notification to the target terminal 104 indicating that the MFP 102 has been powered on.

[0078] In S814, when the PWA operating on terminal 104 receives a push notification from S813, it retrieves the configuration change details stored in the data storage area 503 in S805. In this embodiment, the PWA does not display the notification corresponding to the received push notification, but it may display the notification to inform the user 600 that the MFP 102 has been powered on.

[0079] In S814, the PWA checks whether there are any configuration changes stored in the data storage area 503. In this embodiment, we will proceed with the assumption that the configuration changes were stored in S805 and that there are configuration changes stored in the data storage area 503.

[0080] In S815, the PWA requests a configuration change from the MFP102 based on the configuration change information obtained in S814.

[0081] In S816, the remote UI request processing unit 301 of the MFP102 receives the setting change request from S815 and performs the setting change according to the content of the request on the setting management unit 305.

[0082] Next, we will explain the cases where a restart of the MFP102 is necessary to actually reflect the changes, and where it is not. This is because, if a restart is not required, the settings will be reflected in the previous steps, but if a restart is required, there is a risk that the setting changes will not be fully reflected, and this is to avoid that.

[0083] First, we will explain the sequence when the configuration change made in S816 does not require a restart of the MFP102. In S821, the remote UI request processing unit 301 responds to the configuration change request in S815 by indicating that the configuration change is complete and that a restart is not required.

[0084] In S822, the PWA running on terminal 104 receives a response from S821 and displays a notification on terminal 104 via browser 500 indicating that the configuration changes received in S804 have been executed on MFP 102 and completed. Figure 15(A) shows an example of the notification 1111 displayed at this time.

[0085] Next, we will describe the sequence when the configuration change made in S816 requires a restart of the MFP102. In S831, the remote UI request processing unit 301 responds to the configuration change request in S815 by indicating that a restart is required to complete the configuration change.

[0086] In S832, the PWA running on terminal 104, upon receiving the response from S831, displays a notification indicating that the configuration changes received in S804 have been executed on MFP 102, and that a restart of MFP 102 is required for the changes to take effect. Figure 15(B) shows an example of notification 1121 displayed in S832. In Figure 15(B), link 1125 is a link to display the restart screen for restarting MFP 102, which will be described later.

[0087] In S833, user 600 receives a notification displayed in S832 and, for example, clicks link 1125 in notification 1121 to instruct the PWA to display a restart screen for restarting the MFP 102, which will be described later.

[0088] In S834, the PWA, upon receiving instructions from S833, displays the restart screen 1211 (Figure 16(A)) using the information stored in the data storage area 503. If the restart screen information is not available in the data storage area 503, the PWA communicates with the MFP 102 to obtain and display the restart screen information.

[0089] Figure 16(A) shows an example of the restart screen 1211 displayed in S834. The restart execution button 1231 is a button for receiving a restart command from user 600.

[0090] In S835, user 600 presses the restart execution button 1231 on the restart screen 1211 displayed in S834, instructing the MFP 102 to restart.

[0091] In S836, the PWA, in response to the instructions in S835, displays a confirmation dialog to ask user 600 for permission to restart MFP102.

[0092] Figure 16(B) shows an example of a restart screen 1211, including a confirmation dialog 1251 displayed in S836. The OK button 1255 is a button for receiving permission from user 600 to perform a restart.

[0093] In S837, user 600 presses the OK button 1255 in the confirmation dialog 1251 displayed in S836, thereby authorizing the restart of MFP102.

[0094] In S838, the PWA, having received permission in S837, requests a restart from MFP102. In S839, MFP102 begins the process of restarting itself. In S840, MFP102 responds that it has started the restart.

[0095] In S841, the PWA, upon receiving a response from S840, displays a screen indicating that the MFP102 restart has begun. Figure 16(C) shows an example of screen 1271 displayed in S841.

[0096] As described above, the MFP102 of this embodiment, regardless of whether or not a settings screen is available, will reflect the setting change in its own device when it receives a setting operation request from the PWA. This allows the user to appropriately configure the MFP102 asynchronously, regardless of the state of the MFP102. Specifically, for example, even if the MFP102 is not powered on and cannot provide a settings screen to the user terminal, user 600 can open the settings screen (setting change screen) on terminal 104 and perform setting changes (S804, 805). Then, the PWA on terminal 104 receives a push notification from the MFP102 when the MFP102 is powered on and automatically performs the setting change on the MFP102 (S812~816). As a result, user 600 does not need to open the setting change screen and perform setting operations after the MFP102 is powered on.

[0097] Furthermore, if an automatic configuration change requires a restart of the MFP102, terminal 104 can receive a notification to that effect (S831). Therefore, user 600 can prevent forgetting to restart the MFP102 to complete the configuration change, and can also restart it immediately after the configuration change.

[0098] Furthermore, after S841, the PWA may receive a push notification from the MFP102 via the push server 103 indicating that the restart is complete, and display this notification on the terminal 104 via the web browser 500. This allows the user 600 to know when the restart for reflecting the configuration changes is complete (when the configuration changes have been reflected).

[0099] [Second Embodiment] In the first embodiment described above, the MFP 102 notified terminal 104 that a restart was necessary if a configuration change required a restart of the device. However, if the user overlooks the notification, the restart timing may be delayed, so there may be cases where it is desirable to perform the restart automatically. Also, there may be cases where it is desirable to check the latest configuration information when the power is turned on before making configuration changes. In the second embodiment, in order to flexibly handle these cases, the operation of the PWA when it receives a power-on notification from the MFP 102 is configured. In this embodiment, the explanation of parts that overlap with the first embodiment is omitted, and only the differences are explained.

[0100] In the second embodiment, the sequence of operations when a user 600 changes the settings of the MFP 102 via PWA while the MFP 102 is powered off will be explained using Figure 17. Of the operations shown in Figure 17, the operations performed by the MFP 102 are realized by the CPU 201 of the MFP 102 reading the program of the software module shown in Figure 3, which is stored in the storage device 204, into the RAM 203 and executing it. Similarly, the operations performed by the push server 103 are realized by the CPU 201 of the push server 103 reading the program of the software module shown in Figure 4, which is stored in the storage device 204, into the RAM 203 and executing it. Also similarly, the steps performed by each device of the terminal 104 are realized by the CPU 201 of the terminal 104 reading the programs of each software module shown in Figure 5, which are stored in the storage device 204, into the RAM 203 and executing them.

[0101] Figure 17 shows the sequence in the second embodiment, from the display of the operation setting screen 1411 when the MFP102 is powered on (as will be described later) to the acceptance of operation setting input on that screen. Figure 17 differs from the first embodiment in that the processes S1301-S1303 are executed after S806 in Figure 10. These differences will be explained below.

[0102] In S1301, the PWA running on terminal 104 displays the operation settings screen for when the MFP 102 is powered on. In the first embodiment, the PWA displayed a message indicating that it could not communicate with the MFP 102 (S807), but in this embodiment, the operation settings screen is displayed to allow the user to configure the operation when the MFP 102 is powered on in more detail.

[0103] Figure 21 is an example of the operation setting screen 1411 displayed in S1301 when the MFP102 is powered on. In Figure 21, item 1421 is a selection item for displaying a notification on terminal 104 when the MFP102 is powered on. Item 1422 is a selection item for automatically applying the settings stored in S805 to the MFP102 when the MFP102 is powered on, and displaying a notification on terminal 104. Item 1423 is a check item to check if a restart of the MFP102 is required for the settings to be applied, or if the MFP102 should be restarted automatically, when item 1422 is selected. If item 1421 is selected, item 1423 is disabled and cannot be checked or unchecked. Items 1421 and 1422 use radio buttons, and only one of them can be selected. The OK button 1424 is used to confirm the settings made on the operation setting screen 1411 when the MFP is powered on.

[0104] In this embodiment, the default setting on the operation setting screen 1411 is that item 1422 is selected and item 1423 is unchecked. This setting performs the same operation as in the first embodiment.

[0105] Table 1 shows the configuration patterns that can be set on the operation settings screen 1411 and the PWA operation for each pattern. Details of the PWA operation for each pattern will be described later.

[0106] [Table 1]

[0107] In S1302, user 600 configures the operation settings for when the MFP102 is powered on on the operation setting screen 1411 displayed in S1301, and then presses the OK button 1424.

[0108] In S1303, the PWA stores the settings confirmed in S1302 in the data storage area 503.

[0109] Figure 18 shows the processing sequence from the point after S1303 when the MFP102 is powered on. Since steps S811-S813 in Figure 18 are the same as steps S811-S813 in Figure 11, their explanation is omitted.

[0110] In S1311, when the PWA running on terminal 104 receives a push notification from S813, it retrieves the operation settings stored in the data storage area 503 in S1303. Then, it performs processing according to the retrieved operation settings.

[0111] First, we will explain the processing sequence when the operation setting obtained in S1311 is Pattern 1, using Figure 19.

[0112] In S1321, the PWA running on terminal 104 displays a notification on terminal 104 via browser 500 indicating that the MFP 102 has been powered on. Figure 22(A) shows an example of the notification 1511 displayed at this time. In this embodiment, a link 1512 for displaying the settings change screen for the setting that the user was trying to change is displayed within the notification 1511. This is because a user 600 who has chosen not to perform the settings automatically may want to check the latest settings of the MFP 102 and change the settings as needed, and in that case, the settings change screen can be easily displayed.

[0113] In S1322, user 600, for example, clicks the notification link 1512 displayed in S1321 to instruct the PWA to display the settings change screen for the setting that the user was trying to change.

[0114] In S1323, similar to S802, the PWA displays a configuration change screen using the content information stored in the data storage area 503 before communicating with the MFP102.

[0115] In S1324, the PWA, similar to S803, requests the MFP102 to retrieve the latest configuration change screen.

[0116] In S1325, the MFP102's remote UI request processing unit 301 acquires the configuration information and status information managed by the MFP102's configuration management unit 305 and status management unit 303 as needed, and then generates the latest configuration change screen information.

[0117] In S1326, the remote UI request processing unit 301 of the MFP102 responds to the PWA with the latest configuration change screen information generated in S1325.

[0118] In S1327, the PWA, upon receiving the response from S1326, displays the latest configuration change screen. After this, user 600 reviews the contents of this screen and makes further configuration changes as needed.

[0119] The processing when the operation setting obtained in S1311 is pattern 2 is the same as from S814 onwards shown in Figure 11 of the first embodiment, so the explanation is omitted.

[0120] Next, we will explain the processing sequence when the operation setting obtained in S1311 is pattern 3, using Figure 20.

[0121] In Figure 20, steps S814 to S816 are identical to those in Figure 11 of the first embodiment, so their explanation is omitted. The same applies to steps S821 and S822 when a restart is not required, and to step S831 when a restart is required. The following describes the processing after step S831 when a restart is required.

[0122] In S1351, the PWA running on terminal 104 receives a response indicating that a restart is required to complete the configuration changes in S831, and requests a restart from MFP102.

[0123] In S1352, the remote UI request processing unit 301 of the MFP102 requests the configuration management unit 305 to restart the MFP102, and the configuration management unit 305 starts the restart of the MFP102.

[0124] In S1353, the remote UI request processing unit 301 of the MFP102 sends a response to the PWA indicating that a restart has been initiated.

[0125] In S1354, the PWA stores in data storage area 503 that it is waiting for a restart to complete following a configuration change.

[0126] In S1355, the PWA displays screen 1271 (Figure 16(C)) indicating that the MFP102 restart has begun, similar to S841.

[0127] In S1356, the event management unit 304 of the MFP102 detects that the power has been turned on due to the restart performed in S1352 as an event within the MFP102, and requests the notification transmission unit 302 to send a push notification of the power-on event.

[0128] In S1357, the notification transmission unit 302 of the MFP102, similar to S812, sends a push notification request to the push server 103 to inform registered notification recipients that the MFP102 has been powered on.

[0129] In S1358, the request receiving unit 403 of the push server 103 receives the push notification request in S1357, similar to S813, and passes its contents to the notification forwarding unit 406. Based on the information contained in the received push notification request, the notification forwarding unit 406 forwards a push notification to the target terminal 104 indicating that the MFP 102 has been powered on.

[0130] In S1359, it is checked whether the PWA running on terminal 104 has stored in the data storage area 503 that it is waiting for a restart to complete following a configuration change. In this embodiment, the explanation proceeds assuming that terminal 104 has stored in S1354 that it is waiting for a restart to complete following a configuration change.

[0131] In S1360, the PWA executes the configuration changes received in S804 on the MFP102 and displays a notification indicating that the restart of the MFP102 to reflect those changes has been completed. Figure 22(B) shows an example of the notification 1521 displayed at this time.

[0132] As described above, in this embodiment, the operation of the PWA can be configured when a power-on push notification (S813) is received from the MFP102 (S1311) (S1301-S1303). This allows the system 100 to flexibly handle cases such as when it is desired to automatically restart the MFP102 to reflect the setting changes, or when it is desired to check the latest setting information when the MFP102 is powered on and then make setting changes.

[0133] Furthermore, if the settings for Pattern 1 in Table 1 are made in S1302 of Figure 17, the settings changes stored in S805 may be discarded. This is because, in Pattern 1, the latest settings change screen is obtained from S1324 onwards, as shown in Figure 19. In that case, link 1512 in notification 1511 in Figure 22(A) may not be displayed.

[0134] [Third Embodiment] In the first embodiment, the PWA can receive a push notification that the MFP102 has been powered on when the Service Worker processing unit 502 of the Web browser 500 is activated. However, for some reason, the Web browser 500 of the terminal 104 may stop, and the Service Worker may also stop. In that case, the PWA may not be able to receive the push notification that the MFP102 has been powered on, and the configuration changes received by S804 may not be automatically executed. The PWA in the third embodiment is designed to perform the configuration changes received by S804 even in such cases. In this embodiment, the explanation of parts that overlap with the first embodiment will be omitted, and only the differences will be explained.

[0135] Figure 23 shows the sequence of processes when the Web browser 500, which was stopped on terminal 104, is started up. Of the processes shown in Figure 23, the steps executed by each device of terminal 104 are realized by the CPU 201 of terminal 104 reading the programs of each software module shown in Figure 5, which are stored in the storage device 204, into the RAM 203 and executing them.

[0136] In S1601, the PWA starts when the web browser 500 on terminal 104 is launched. The launch of the web browser 500 is triggered, for example, by a restart of terminal 104 or by a command from user 600 to launch the web browser 500 or the PWA.

[0137] In S1602, the PWA retrieves the configuration changes for the MFP102 stored in the data storage area 503. If the retrieved configuration changes are empty (no configuration changes are stored), the PWA terminates this sequence. If stored configuration changes are retrieved, the PWA performs the processing from S815 onwards as shown in Figure 11.

[0138] Therefore, even if a push notification indicating that the MFP102 has been powered on is not received while the Web Browser 500 is stopped, the PWA can automatically execute the configuration changes it had stored on the MFP102 when it starts up.

[0139] [Fourth Embodiment] In the first embodiment, the PWA may be unable to change its settings due to reasons other than the MFP102 being powered off, such as a malfunction in the communication path with the MFP102. In the fourth embodiment, the PWA automatically changes its settings when it becomes possible to communicate with the MFP102 in such cases. In this embodiment, the explanation of parts that overlap with the first embodiment will be omitted, and only the differences will be explained.

[0140] Figure 24 is a diagram showing the sequence of processes that are initiated when communication with the MFP102 fails, as shown in S806 of Figure 10 in the first embodiment. Cases in which communication with the MFP102 fails include when the MFP102 is powered off, as well as when there is a problem in the communication path between terminal 104 and the MFP102.

[0141] Of the processes shown in Figure 24, the processes executed by MFP102 are realized by the CPU201 of MFP102 reading the software module programs shown in Figure 3, which are stored in the storage device 204, into the RAM203 and executing them. Similarly, the steps executed by each device of terminal 104 are realized by the CPU201 of terminal 104 reading the software module programs shown in Figure 5, which are stored in the storage device 204, into the RAM203 and executing them.

[0142] Furthermore, steps S1701 and S1703, described below, will be repeatedly executed whenever there are configuration changes for the MFP102 stored in the data storage area 503.

[0143] In S1701, the PWA running on terminal 104 sends a status check request to MFP 102.

[0144] If communication with MFP102 is restored, in S1702, if the MFP102's remote UI request processing unit 301 receives the status confirmation request from S1701, it responds that it has been received. If this response is received, the processing from S814 onwards shown in Figure 11 is performed, and the loop is exited.

[0145] If communication with MFP102 has not been restored, in S1703, the PWA waits for a predetermined time and repeats the process of S1701.

[0146] As described above, even if communication with the MFP102 is not possible, other than when the MFP102 is powered off, the PWA can automatically execute the stored configuration changes on the MFP102 when communication with the MFP102 is restored.

[0147] [Other embodiments] At least two of the first, second, third, and fourth embodiments described above may be combined. For example, in the third embodiment, if the stored configuration change content is obtained after S1602, the PWA performs the processing from S815 onwards in Figure 11 (first embodiment), but may also perform the processing from S815 onwards in Figure 20 (second embodiment). Similarly in the fourth embodiment, if a response is received indicating that the status confirmation request S1701 has been received, the PWA performs the processing from S814 onwards in Figure 11 (first embodiment), but may also perform the processing from S814 onwards in Figure 20 (second embodiment).

[0148] In the embodiments described above, an MFP was used as an example of a network device, but other devices that have a web server and can provide a remote UI include network routers, surveillance cameras, and digital medical devices.

[0149] In the above embodiments, the push server 103 and the MFP 102 are separate devices, but the MFP 102 may also include the push server.

[0150] This embodiment includes the following configurations, methods, and programs. (Composition 1) A network device having a web server, The aforementioned web server provides a setting screen for manipulating the setting values ​​of multiple configuration items for the network device to a web browser via the network, and provides a means for doing so. The system includes a means for reflecting the setting value in the network device in accordance with the operation of the setting value, The aforementioned provision means further provides a website for installing software as a progressive web application on the user terminal, which provides a function to manipulate the setting values ​​of at least some of the multiple setting items via the web server. The reflection means reflects the settings on the network device in response to receiving the content of the settings operations performed using the progressive web application from the user terminal via the network, regardless of whether the network device provides the settings screen. A network device characterized by the following features. (Configuration 2) The system further includes notification means for sending push notifications to the user terminal via the network in response to events occurring within the network device. A network device as described in Configuration 1, characterized by the above. (Composition 3) The notification means provides a push notification regarding whether or not the network device needs to be restarted to reflect the setting value. A network device as described in configuration 2, characterized by the above. (Composition 4) The system further includes processing means that initiates a restart process in response to receiving a request to restart the network device based on the notification from the user terminal via the network. A network device as described in configuration 3, characterized by the above. (Composition 5) The notification means, when the power of the network device is turned on, will notify that the power has been turned on. The reflection means, after notification that the power has been turned on, reflects the setting value on the network device in response to receiving the details of the setting value operation from the user terminal via the network. A network device according to any one of configurations 2 to 4, characterized by the above. (Composition 6) The aforementioned provisioning means further provides an operation setting screen that accepts settings for operation when the network device is powered on, via the software of the progressive web application. A network device as described in configuration 2, characterized by the above. (Composition 7) The aforementioned operation settings screen includes an item that accepts the request to automatically restart the network device in order to reflect the settings. A network device according to configuration 6, characterized by the features described above. (Composition 8) The providing means, upon receiving a request from the user terminal via the network to obtain the latest settings screen, provides the latest settings screen via the network. A network device according to configuration 6 or 7, characterized by the above. (Composition 9) The system further includes processing means that initiates a restart process in response to receiving a request to restart the network device based on the push notification from the user terminal via the network, The notification means further notifies the user terminal that the network device has been restarted. A network device according to configuration 6 or 7, characterized by the above. (Composition 10) If a push notification indicating that the network device has been powered on is received while the software of the Progressive Web Application on the user terminal is stopped, the reflection means shall, after the software of the Progressive Web Application on the user terminal has started, reflect the setting value on the network device in accordance with the content of the operation of the setting value. A network device as described in configuration 2, characterized by the above. (Composition 11) If communication between the network device and the user terminal becomes impossible for reasons other than the network device being powered off, the reflection means shall, upon communication becoming possible and receiving the content of the setting value operation from the user terminal via the network, reflect the setting value on the network device. A network device as described in Configuration 1, characterized by the above. (Composition 12) The aforementioned network device is an image processing device equipped with a scanner or printer. A network device according to any one of configurations 1 to 11, characterized by the features described above. (Composition 13) The aforementioned multiple setting items are included in the environment or application settings of the image processing device. A network device according to configuration 12, characterized by the features described above. (method) A method performed by a network device having a web server, The web server provides a setting screen for manipulating the setting values ​​of multiple configuration items for the network device to a web browser via the network, a provision step, The system includes a reflection step in which the setting value is reflected in the network device according to the operation of the setting value, In the aforementioned provisioning process, the web server further provides a website for installing software as a progressive web application on the user terminal, which provides the functionality to manipulate the setting values ​​of at least some of the multiple setting items. In the reflection process, regardless of whether the network device provides the settings screen, the settings performed using the progressive web application are reflected on the network device in response to the user terminal receiving the settings via the network. A method characterized by the following: (program) A program that causes a computer to perform each of the steps described in the above method.

[0151] Although the present disclosure has been described in detail above based on its preferred embodiments, the present disclosure is not limited to the above embodiments, and various modifications are possible in accordance with the spirit of the present disclosure, and these modifications are not excluded from the scope of the present disclosure.

Claims

1. A network device having a web server, The aforementioned web server provides a setting screen for manipulating the setting values ​​of multiple configuration items for the network device to a web browser via the network, and provides a means for doing so. The system includes a means for reflecting the setting value in the network device in accordance with the operation of the setting value, The aforementioned provision means further provides a website for installing software as a progressive web application on the user terminal, which provides a function to manipulate the setting values ​​of at least some of the multiple setting items via the web server. The reflection means reflects the settings on the network device in response to receiving the content of the settings operations performed using the progressive web application from the user terminal via the network, regardless of whether the network device provides the settings screen. A network device characterized by the following features.

2. The system further includes notification means for sending push notifications to the user terminal via the network in response to events occurring within the network device. The network device according to feature 1.

3. The notification means provides a push notification regarding whether or not the network device needs to be restarted to reflect the setting value. The network device according to feature 2.

4. The system further includes processing means that initiates a restart process in response to receiving a request to restart the network device based on the notification from the user terminal via the network. The network device according to feature 3.

5. The notification means, when the power of the network device is turned on, will notify that the power has been turned on. The reflection means, after notification that the power has been turned on, reflects the setting value on the network device in response to receiving the details of the setting value operation from the user terminal via the network. The network device according to feature 2.

6. The aforementioned provisioning means further provides an operation setting screen that accepts settings for operation when the network device is powered on, via the software of the progressive web application. The network device according to feature 2.

7. The aforementioned operation settings screen includes an item that accepts the request to automatically restart the network device in order to reflect the settings. The network device according to feature 6.

8. The providing means, upon receiving a request from the user terminal via the network to obtain the latest settings screen, provides the latest settings screen via the network. The network device according to feature 6.

9. The system further includes processing means that initiates a restart process in response to receiving a request to restart the network device based on the push notification from the user terminal via the network, The notification means further notifies the user terminal that the network device has been restarted. The network device according to feature 6.

10. If a push notification indicating that the network device has been powered on is received while the software of the Progressive Web Application on the user terminal is stopped, the reflection means shall, after the software of the Progressive Web Application on the user terminal has started, reflect the setting value on the network device in accordance with the content of the operation of the setting value. The network device according to feature 2.

11. If communication between the network device and the user terminal becomes impossible for reasons other than the network device being powered off, the reflection means shall, upon communication becoming possible and receiving the content of the setting value operation from the user terminal via the network, reflect the setting value on the network device. The network device according to feature 1.

12. The aforementioned network device is an image processing device equipped with a scanner or printer. The network device according to feature 1.

13. The aforementioned multiple setting items are included in the environment or application settings of the image processing device. The network device according to feature 12.

14. A method performed by a network device having a web server, The web server provides a setting screen for manipulating the setting values ​​of multiple configuration items for the network device to a web browser via the network, a provision step, The system includes a reflection step in which the setting value is reflected in the network device according to the operation of the setting value, In the aforementioned provisioning process, the web server further provides a website for installing software as a progressive web application on the user terminal, which provides the functionality to manipulate the setting values ​​of at least some of the multiple setting items. In the reflection process, regardless of whether the network device provides the settings screen, the settings performed using the progressive web application are reflected on the network device in response to the user terminal receiving the settings via the network. A method characterized by the following:

15. A program that causes a computer to perform each of the steps described in claim 14.

Images