Network device, method and program product by network device

Abstract

A network device, a method performed by the network device, and a program product are provided. The network device provides a setting screen for operating the setting values of the plurality of setting items to the web browser using the web server, and reflects the setting values in the network device in response to an operation on the setting values. A network apparatus provides, through a web server, a website for installing software in a user terminal, the software being a progressive web application for providing a function of operating a setting value of at least one setting item among a plurality of setting items. The network device reflects the at least one setting value regardless of whether the setting screen has been provided in response to receiving details of an operation on the at least one setting value using the progressive web application from the user terminal.

Description

TECHNICAL FIELD

[0001] The present disclosure relates to a technology of information processing in a network device. BACKGROUND

[0002] A network device such as an image forming apparatus is provided with a function (hereinafter referred to as "remote UI") that allows a user to access the network device via a network using a terminal and confirm an operation status, various types of settings, and the like of the network device. The user can use the remote UI by accessing a predetermined URL of a web server operating in the network device using a web browser having an RSS function or the like.

[0003] Japanese Patent Application Publication No. 2010-267032 (Unexamined) discloses a technology of providing a user who requests to acquire information on an error occurrence or a job status with a job status of only a print job executed by the user among all print jobs using a remote UI provided by an image forming apparatus.

[0004] A manager or a general user of a network device can change settings and the like of the network device using a remote UI. However, for example, when communication with the network device cannot be performed (such as when the network device is not powered on), the remote UI cannot be used. Therefore, the manager or the general user cannot change the settings when intending to change the settings, and must wait for the network device to operate, open a setting change screen, and change the settings using the remote UI again. SUMMARY

[0005] The present disclosure provides a technology that enables appropriate settings of a network device regardless of a status of the network device.

[0006] A network device including a web server according to an aspect of the present disclosure includes a providing section configured to provide, by the web server, a setting screen for operating setting values of a plurality of setting items of the network device to a web browser via a network, and a reflecting section configured to reflect the setting values in the network device in response to an operation on the setting values. The providing section provides, using the web server, a website for installing software in a user terminal, the software being a progressive web application for providing a function of operating a setting value of at least one of the plurality of setting items. The reflecting section reflects at least one setting value in the network device in response to receiving details of an operation on at least one setting value using the progressive web application from the user terminal via the network, regardless of whether the setting screen has been provided by the network device.

[0007] The features of the present disclosure will become apparent from the following description of the embodiments with reference to the accompanying drawings. The following description of embodiments is presented by way of example. BRIEF DESCRIPTION OF DRAWINGS

[0008] Figure 1 This is a diagram illustrating an example of the system's construction.

[0009] Figure 2 This is a block diagram illustrating an example of the hardware construction of the devices that constitute the system.

[0010] Figure 3 This is a block diagram illustrating an example of the construction of software modules in MFP.

[0011] Figure 4 This is a block diagram illustrating an example of the software module construction of a push server.

[0012] Figure 5 This is a block diagram illustrating an example of the software module construction of a web browser.

[0013] Figure 6 This is a sequence diagram illustrating the processes involved in installing a PWA.

[0014] Figure 7 This is an example image showing a screen displayed by a web browser.

[0015] Figure 8 This indicates when PWA is displayed. Figure 7 The image shown is an example of a remote UI screen.

[0016] Figure 9 This is an example diagram showing a screen displayed by a PWA for requesting to receive push notifications.

[0017] Figure 10 This is a sequence diagram illustrating the process of changing the settings of the MFP according to the first embodiment.

[0018] Figure 11 It is shown Figure 10 The sequence diagram of subsequent processing.

[0019] Figure 12 This is a diagram showing an example of a settings change screen displayed by PWA in S804.

[0020] Figure 13 This is a diagram showing an example of a screen displayed by the PWA in S807.

[0021] Figure 14 This is a diagram illustrating an example of settings change details stored by the PWA in S805.

[0022] Figure 15A This is a diagram illustrating an example of a notification indicating that the MFP has performed and completed a setting change received in S804, and Figure 15B This is a diagram showing an example of a notification displayed in S832.

[0023] Figure 16A This is a diagram showing an example of a reboot screen displayed in S834. Figure 16B This is a diagram showing an example of a restart screen including a confirmation dialog box displayed in S836, and Figure 16C This is a diagram showing an example of the restart screen displayed in S841.

[0024] Figure 17 This is a sequence diagram illustrating the process of changing the settings of the MFP according to the second embodiment.

[0025] Figure 18 This is a sequence diagram showing the processing when the MFP is powered on.

[0026] Figure 19 This is a sequence diagram showing the processing when the details of the operation settings correspond to mode 1.

[0027] Figure 20 This is a sequence diagram showing the processing when the details of the operation settings correspond to mode 3.

[0028] Figure 21 This is an example diagram showing the operation settings screen when the MFP is powered on.

[0029] Figure 22A This is a diagram showing an example of a notification indicating that the MFP has been powered on, and Figure 22B This is a diagram showing an example of an MFP notification indicating that a restart has been completed, reflecting settings changes.

[0030] Figure 23 This is a sequence diagram illustrating the process when a web browser is launched according to a third embodiment.

[0031] Figure 24 This is a sequence diagram illustrating the process that begins when communication with the MFP is not possible in S806 according to the fourth embodiment. Detailed Implementation

[0032] Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. Not all of the multiple features in the embodiments of the present disclosure are essential, and multiple features can be combined arbitrarily. The constructions described in the following embodiments are merely examples, and the present disclosure is not limited to the constructions shown. Identical or similar constituent elements in the drawings will be denoted by the same reference numerals, and repeated descriptions thereof will be omitted.

[0033] [First Embodiment]

[0034] Figure 1This is a diagram illustrating an example of the system configuration of a system 100 according to an embodiment of the present disclosure. The system 100 includes a multifunction peripheral (MFP) 102, a push server 103, and a terminal 104. The MFP 102, the push server 103, and the terminal 104 are connected to a network 101.

[0035] A network is, for example, a communication network that is implemented through any one of the following: LAN, WAN, telephone line, dedicated digital line, ATM, frame relay line, cable television line, and data broadcast wireless line, or through a combination of two or more of them. A LAN can be built within a company.

[0036] MFP 102 is a multi-functional peripheral (MFP) that is a network device with remote UI functionality. Push server 103 is a server provided for web browser providers to deliver push notification services via web browsers. Terminal 104 is an electronic device used by users of MFP 102 in business or other situations. Terminal 104 is, for example, a tablet computer, smartphone, or PC. Users of terminal 104 can use the remote UI of MFP 102 via a web browser operating on terminal 104.

[0037] Figure 2 This is a block diagram illustrating an example of the hardware configuration of MFP 102, push server 103, and terminal 104. The scanner 208 and printer 209 among these modules are devices primarily included in MFP 102.

[0038] CPU 201 centrally controls the overall hardware and controls the components connected to bus 200, enabling various functions such as printing and scanning. ROM 202 is a dedicated memory for reading data and, for example, stores the basic control program of MFP 102 in the case of MFP 102. RAM 203 is a memory capable of reading / writing data and, for example, serves as the working memory of CPU 201.

[0039] The CPU 201 can be replaced by a programmable logic device (PLD) such as a field-programmable gate array (FPGA). Alternatively, an application-specific integrated circuit (ASIC) or a digital signal processor (DSP) can be used.

[0040] Storage device 204 is an HDD, SSD, etc., and serves as a storage area for programs executed by CPU 201 or for data used in those programs. In the case of MFP 102, storage device 204 also serves as a storage area for images to be printed or scanned. Storage device 204 can be a device capable of reading and writing data relative to external media such as CDs, DVDs, or memory cards attached thereto.

[0041] Communication device 205 is connected to network 101 and enables network communication with other devices or services. In MFP 102, communication device 205 also receives print data or scan data sent from terminal 104.

[0042] Input device 206 is an operation unit that receives text or data input operations from a user. Input device 206 includes, for example, a keyboard, mouse, hardware buttons, and touch panel.

[0043] Display device 207 is a device that displays various screens, such as an LCD monitor or a touch panel. Users can input commands to the user interface (UI) screen displayed on display device 207 via input device 206, and provide instructions for operating and setting the MFP102. Input device 206 and display device 207 can be integrated using a touch panel.

[0044] Figure 3 This diagram illustrates an example of the construction of the software modules of the MFP 102. For example, this is achieved by having the CPU 201 read the program stored in ROM 202 into RAM 203 and execute the program. Figure 3 The software structure shown.

[0045] The remote UI request processing unit 301 receives a request from the web browser 500 (described later) of the terminal 104 and provides a menu screen for managing the MFP 102, or information for displaying the status information of the MFP 102 obtained from the status management unit 303 (described later). The remote UI request processing unit 301 performs the requested setting changes. The remote UI request processing unit 301 is mainly an example of a providing unit that provides a setting screen via the network to the web browser, displaying setting values ​​for multiple settings items for operating the network device.

[0046] When changing the settings of the MFP 102 according to this embodiment, depending on the settings details, it may or may not be necessary to restart the MFP 102 to reflect the changes. This is because, if a restart is required to reflect all settings changes, the MFP 102 may experience operational disruptions by reflecting the settings changes simultaneously with its operation.

[0047] The notification sending unit 302 receives a push notification request from the event management unit 304 (described later) and sends a push notification to the terminal 104, which is a pre-registered notification target. When it receives a push notification request from the event management unit 304, the notification sending unit 302 edits the request details into the format of a request to the push server 103 and sends the edited details to the push server 103. The notification sending unit 302 is an example of a notification unit that sends push notifications corresponding to events occurring in a network device to user terminals via a network.

[0048] The status management unit 303 performs printing control and anomaly management on the MFP 102, and also manages counter information and notification information. Counter information includes, for example, the quantity of print sheets in the MFP 102, the consumption level of components, and the remaining amount of consumables (such as toner bottles).

[0049] The event management unit 304 receives and manages events occurring in the MFP 102. The event information managed by the event management unit 304 includes events related to the MFP 102's power-on / power-off, user-issued print jobs, and errors (which may be referred to as obstacles). Examples of errors in the MFP 102 include high-urgency errors (such as hard drive errors) or warning-level errors (such as paper jams or insufficient toner). It also manages event information indicating toner bottle replacement, firmware updates, etc. The event management unit 304 detects the occurrence of events and, as needed, sends a request to the notification sending unit 302 for a push notification corresponding to the detected event.

[0050] The configuration management unit 305 manages various settings of the MFP 102 and responds to or changes various types of configuration information in response to requests from the remote UI request processing unit 301 or operations on the input device 206. The configuration management unit 305 receives requests from the remote UI request processing unit 301 and is also responsible for the processing of restarting the MFP 102. The configuration management unit 305 is an example of a response unit that reflects the manipulated configuration value in the network device in response to an operation on the configuration value. The configuration management unit 305 is also an example of a processing unit for initiating the process of restarting the network device.

[0051] Figure 4 This is a diagram illustrating an example of the software module structure 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 sending unit 406.

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

[0053] Storage unit 402 performs storage control on RAM 203, ROM 202, and storage device 204. In this embodiment, the objects of storage control include information about the target terminal of the push notification and information about the push notification request.

[0054] The request receiving unit 403 receives a request sent from the web browser 500 operating in the terminal 104 that is registered as a target for push notification, or a push notification request from the notification sending unit 302.

[0055] The response generation unit 404 sends the push subscription object, which will be described later, as a response to the request registered as the target of the push notification to the web browser 500, which is the source of the request.

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

[0057] The notification sending unit 406 sends a push notification to the target terminal based on the endpoint information included in the push notification request received from the notification sending unit 302. In addition to notifications indicating that the MFP 102 according to this embodiment is powered on, the notification may also include information such as errors occurring in the MFP 102, information on the level of consumable consumption, or notifications from the administrator.

[0058] Figure 5 This is a block diagram illustrating an example of the software construction of a web browser 500 operating in terminal 104. This is achieved, for example, by having CPU 201 read a program stored in ROM 202 or storage device 204 into RAM 203 and execute that program. Figure 5 The software structure shown.

[0059] Assume that the web browser 500 according to this embodiment corresponds to a Progressive Web Application (hereinafter referred to as PWA). A PWA is a technology that enables a website to be used like a native application, and it is an application in itself. A PWA is a (web) application having at least some of the functions that can be provided by the MFP 102 via a network or from a remote UI. The MFP 102 provides a remote UI to a web browser that has accessed an address (URL, IP address, etc.) assigned to its remote UI. The user can install the PWA for the MFP 102 according to this embodiment on the terminal 104 via the remote UI. The user does not need to access an app store and download the PWA as with native applications in the prior art; instead, when the user accesses a website that provides the PWA, the user can simply install and use the website via a web browser. Similar to native applications, icons for using the PWA can be added to the desktop, home screen, etc. of the terminal 104.

[0060] The web page processing unit 501 performs the following processing based on instructions received from the user at terminal 104: such as communicating with the remote UI request processing unit 301 of MFP 102 or displaying web content received from the remote UI request processing unit 301. For example, the web content may be described using Hypertext Markup Language (HTML), JavaScript, or Cascading Style Sheets (CSS). The web content may include service workers (scripts that operate as background processes) as elements of the PWA, or manifest files (files describing the installation settings of the PWA).

[0061] The service worker processing unit 502 executes a service worker that is received as a PWA element from the remote UI request processing unit 301 of the MFP 102.

[0062] Data storage area 503 is an area for temporary or permanent storage of data, such as web content received from the remote UI request processing unit 301 of MFP 102, or details of instructions received from the user of terminal 104. Specifically, data storage area 503 is configured in RAM 203 or storage device 204 of terminal 104. Web page processing unit 501 and service worker processing unit 502 use data storage area 503 for appropriate processing.

[0063] Figure 6 This is a diagram illustrating the sequence up to the point where the PWA is installed in terminal 104 from MFP 102 and the PWA is able to receive push notifications from MFP 102. Figure 6 In this context, assume that user 600 is a user of terminal 104 and changes the settings of MFP 102 via terminal 104.

[0064] exist Figure 6 In the various processes shown, the CPU 201 of the MFP 102 is used to... Figure 3 The program of the software module shown and stored in storage device 204 is read into RAM 203 and executed to achieve the processing performed by MFP 102. This is achieved by causing the CPU 201 of push server 103 to... Figure 4 The program of the software module shown and stored in storage device 204 is read into RAM 203 and executed to realize the processing performed by push server 103. Similarly, the CPU 201 of terminal 104 is made to... Figure 5 The program of the software module shown and stored in storage device 204 is read into RAM 203 and executed to realize the steps performed by terminal 104.

[0065] In S601, user 600 instructs web browser 500, which operates in user 600's terminal 104, to access the remote UI of MFP 102. Specifically, user 600 instructs access to the remote UI of MFP 102 by entering the address information assigned to the remote UI in MFP 102 into the address bar of web browser 500.

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

[0067] In S603, the remote UI request processing unit 301 of MFP 102 returns the requested web content as a response. The returned web content includes, in addition to the screen information of the remote UI displayed on the web browser 500, a manifest file or service worker for installing and executing the remote UI as a PWA.

[0068] In S604, the web page processing unit 501 of terminal 104 analyzes the details of the web content obtained in S603 and displays the remote UI on the web browser 500.

[0069] In S605, the web page processing unit 501 of terminal 104 registers the service workers included in the web content acquired in S603 in the data storage area 503. The service workers registered here are scripts used to define push notification functions (i.e., PWA features) or behaviors such as offline operations, and are executed in the background by the service worker processing unit 502. In other words, when a user does not access the remote UI through a web browser, push notifications to installed PWAs, etc., are achieved via the service workers operated in the background by the service worker processing unit 502.

[0070] Instructions associated with cache control can be described in the service worker. In this case, the service worker processing unit 502 stores the web content obtained in S603 as cache in the data storage area 503 based on the description details at the time of registration.

[0071] In S606, the web page processing unit 501 of terminal 104 displays a screen on web browser 500 to prompt the user to install PWA based on the manifest file included in the web content obtained in S603.

[0072] Figure 7 This is a diagram illustrating an example of screen 711 displayed on web browser 500 in S606. Button 731 is displayed when the web content includes a manifest file. Dialog box 733 is displayed to allow user 600 to confirm whether to install the PWA. In this embodiment, dialog box 733 is displayed automatically when the web content includes a manifest file. However, dialog box 733 may also be displayed in response to user 600 pressing button 731.

[0073] Button 735 is the button pressed by user 600 when installing the PWA. Button 737 is the button pressed by user 600 when not installing the PWA. In this embodiment, the scenario where user 600 presses button 735 to begin installing the PWA will be described.

[0074] In S607, user 600 presses button 735 and instructs web browser 500 running in terminal 104 to install PWA.

[0075] 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 based on the details of the manifest file. In the following description, the PWA executed in the web browser 500 in terminal 104 is described as the operation subject. The web page processing unit 501 can generate an icon for launching the PWA on the desktop, main screen, etc. of terminal 104 when installing the PWA.

[0076] Figure 8This is an example image showing a remote UI displayed by the PWA when the PWA is installed. Figure 8 The display details of screen 751 shown are as follows: Figure 7 The details displayed on screen 711 are the same as those shown in a regular web browser, but they differ from the display in a regular web browser, appearing as if operating a local application, for example, by not displaying the address bar. When user 600 launches the installed PWA, it is displayed on web browser 500. Figure 8 The image shown is 751.

[0077] In S609, the PWA operating in terminal 104 displays a message requesting user 600 to allow receiving push notifications.

[0078] Figure 9 This is an example diagram showing a screen displayed by the PWA in S609 for requesting permission to receive push notifications. Figure 9 In the dialog box, dialog box 771 is displayed to request user 600 to allow receiving push notifications. When allowing push notifications, user 600 presses the allow button 773. When disallowing push notifications, user 600 presses the block button 775. In this embodiment, the scenario where user 600 presses the allow button 773 to allow receiving push notifications will be described.

[0079] In S610, user 600 presses permission button 773 and instructs web browser 500 to allow receiving push notifications.

[0080] In S611, web browser 500 sends a request to push server 103 to register the PWA operated in terminal 104 as a push notification target.

[0081] In S612, upon receiving the request from S611, the request receiving unit 403 of push server 103 sends the details of the request to notification target management unit 405. Then, notification target management unit 405 registers the PWA operating in terminal 104 as the target of the push notification and issues a push subscription object. The push subscription object includes information for associating the sender and receiver of the push notification, which is required when the notification sending unit 302 of MFP 102, described later, sends the push notification to the PWA operating in terminal 104. Specifically, the push subscription object includes endpoint information of push server 103, which includes the URL of push server 103 and endpoint text that varies depending on the target of the push notification.

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

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

[0084] In S615, the remote UI request processing unit 301 of MFP 102 registers the received push subscription object in the notification sending unit 302. The push subscription object registered here is used by the notification sending unit 302 of MFP 102 to request the push server 103 to send a push notification to the terminal 104 to be notified.

[0085] The following will refer to Figure 10 and Figure 11 This describes the sequence of actions taken when user 600 changes the settings of MFP102 via PWA in the event of a power outage. Figure 10 and Figure 11 In the various processes shown, the CPU 201 of the MFP 102 is used to... Figure 3 The program of the software module shown and stored in storage device 204 is read into RAM 203 and executed to achieve the processing performed by MFP 102. This is achieved by causing the CPU 201 of push server 103 to... Figure 4 The program of the software module shown and stored in storage device 204 is read into RAM 203 and executed to realize the processing performed by push server 103. Similarly, the CPU 201 of terminal 104 is made to... Figure 5 The program of the software module shown and stored in storage device 204 is read into RAM 203 and executed to realize the processing performed by the constituent device of terminal 104.

[0086] In S801, user 600 instructs the PWA operating in terminal 104 to display a settings change screen, for example, for changing the settings of MFP 102.

[0087] In S802, the PWA changes the screen display settings using information stored in the data storage area 503 before communicating with the MFP 102. This operation is used to improve responsiveness to display requests from the user 600.

[0088] In S803, the PWA requests the MFP 102 to obtain the latest settings change screen. When the MFP 102 is operating normally, this request is received and responded to by the remote UI request processing unit 301. However, in this example, because the MFP 102 is powered off, the request is neither received nor responded to.

[0089] In S804, user 600 enters settings changes on the settings change screen displayed in the PWA.

[0090] Figure 12 This is a diagram showing an example of a settings change screen displayed by PWA in S804. Figure 12 The settings change screen 911 shown is a screen used to register the destination settings in the send scanned image function provided in MFP 102. Settings change screen 911 is an example of a settings screen that includes multiple settings items for manipulating settings values. Type selection object 931 is a group of radio buttons for selecting the sending method. For example, email, fax, or document can be selected. Input form object 933 is an input field for entering the name or address of the destination, etc. OK button 935 is a button used to confirm the selections and inputs made on settings change screen 911 and send a settings change request to MFP 102. Cancel button 937 is a button used to discard the selected and entered information and return to the screen before transitioning to settings change screen 911. In this description, it is assumed that user 600 makes selections and inputs on settings change screen 911 and presses OK button 935.

[0091] Figure 12 The address book settings change screen shown is only an example of a settings screen used to manipulate the settings values ​​of the MFP 102. Additional settings screens include environment settings or application settings for the MFP 102. Address book settings are one type of application setting.

[0092] In S805, the PWA operating in terminal 104 stores the details of the input setting changes in data storage area 503.

[0093] Figure 14 This is an example diagram showing details of setting changes stored in the PWA in S805. "Setting Category" indicates the setting object in MFP 102. "Operation" indicates what kind of change is to be made (e.g., adding, changing, or deleting) and indicates operation details, which here indicate adding the destination to the address book. "Type," "Name," etc., are address book settings and details selected or entered via the setting change screen 911.

[0094] In S806, the PWA requests the MFP 102 to change its settings. When the MFP 102 is operating normally, this request is received by the remote UI request processing unit 301 and the settings are changed. However, in this example, because the MFP 102 is powered off, the request is not received and no settings are changed.

[0095] In S807, the PWA detects that there is no response to the request in S806 due to timeout or other reasons, and displays a message indicating that communication with MFP 102 is not possible.

[0096] Figure 13 This is a diagram showing an example of a screen displayed by PWA in S807. Figure 13 In the diagram, dialog box 951 is the area that displays a message indicating that communication with MFP 102 is impossible. As shown, dialog box 951 may also display a message indicating that settings will be automatically configured when communication with MFP 102 is restored.

[0097] Figure 11 This is a diagram showing the sequence of processes performed after S806 when MFP 102 is powered on. Figure 11 Strictly show that after the MFP 102 is powered on, when Figure 3 The sequence of operations of the software module of the MFP 102 is shown. In this embodiment, this state is represented as powered on.

[0098] In S811, the event management unit 304 of MFP 102 detects power-on as an event in MFP 102 and requests the notification sending unit 302 to send a push notification of the power-on event.

[0099] In S812, the notification sending unit 302 sends a push notification request to the push server 103 to notify the registered terminal 104 to be notified that the MFP 102 has been powered on.

[0100] In S813, the request receiving unit 403 of the push server 103 receives the push notification request from S812 and sends its details to the notification sending unit 406. Based on the information included in the push notification request, the notification sending unit 406 sends a push notification indicating that the MFP 102 has been powered on to the terminal 104 to be notified.

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

[0102] In S814, the PWA confirms whether the setting change details are stored in the data storage area 503. In this embodiment, it is assumed that the setting change details are stored in S805, and that the setting change details are stored in the data storage area 503.

[0103] In S815, PWA requests setting changes in MFP 102 based on the setting change details obtained in S814.

[0104] In S816, the remote UI request processing unit 301 of MFP 102 receives the setting change request in S815 and makes setting changes on the setting management unit 305 based on the details of the request.

[0105] Regarding follow-up processing, we will describe whether or not an MFP 102 restart is needed to actually reflect the changes. This is because, when a restart is not needed, the settings are reflected through the processing up to the present; while when a restart is needed, the settings changes are in a semi-completed state and have not been reflected, a situation that should be avoided.

[0106] First, the sequence of events described in S816 where a configuration change does not require a restart of MFP 102 will be presented. In S821, the remote UI request processing unit 301 returns a response indicating that the configuration change has been completed and a restart is not required, as a response to the configuration change request in S815.

[0107] In S822, the PWA operating in terminal 104 receives the response in S821 and displays a notification on terminal 104 via web browser 500 indicating that the setting change received in S804 has been performed and completed by MFP 102. Figure 15A This shows an example of notification 1111 that is displayed at this time.

[0108] The sequence of events following the description of the configuration change in S816 that requires a restart of MFP 102 is then described. In S831, the remote UI request processing unit 301 returns a response indicating that a restart is required to complete the configuration change, as a response to the configuration change request in S815.

[0109] In S832, the PWA operating in terminal 104 receives the response in S831 and displays a notification indicating that the setting change received in S804 has been made in MFP 102, and a notification indicating that MFP 102 needs to be restarted to reflect the change. Figure 15B An example of notification 1121 displayed in S832 is shown. Figure 15B Link 1125 is used to display the reboot screen for restarting the MFP 102, which will be described later.

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

[0111] In S834, PWA responds to the instructions in S833 and uses the information stored in data storage area 503 to display the restart screen 1211. Figure 16AWhen the restart screen information is not stored in the data storage area 503, it is assumed that the PWA communicates with the MFP 102 and obtains and displays the restart screen information.

[0112] Figure 16A An example of the restart screen 1211 displayed in S834 is shown. The restart execution button 1231 is a button used to receive a restart command from user 600.

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

[0114] In S836, PWA receives instructions from S835 and displays a confirmation dialog box asking user 600 whether they want to actually restart MFP102.

[0115] Figure 16B An example of a restart screen 1211 is shown, including a confirmation dialog box 1251 displayed in S836. The OK button 1255 is a button used to receive permission from user 600 to restart.

[0116] In S837, user 600 presses the OK button 1255 on the confirmation dialog box 1251 displayed in S836, and is authorized to restart MFP 102.

[0117] In S838, PWA receives permission from S837 and requests MFP 102 to restart. In S839, MFP 102 begins the restart process. In S840, MFP 102 returns a response indicating that restart has begun.

[0118] In S841, PWA receives the response from S840 and displays a screen indicating that the restart of MFP 102 has begun. Figure 16C An example of screen 1271 displayed in S841 is shown.

[0119] As described above, when details of an operation on a setting value are received from the PWA, the MFP 102 according to this embodiment reflects the setting change, regardless of whether a setting screen is provided. Therefore, the user can asynchronously and appropriately set the MFP 102 regardless of its state. Specifically, even if the MFP 102 is not powered on and therefore cannot provide a setting screen to the user terminal, the user 600 can still open the setting screen (setting change screen) on the terminal 104 and perform a setting change operation (S804 and S805). When the MFP 102 is powered on, the PWA in the terminal 104 receives a push notification from the MFP 102 and automatically performs a setting change on the MFP 102 (S812 to S816). Therefore, the user 600 does not need to open the setting change screen and operate the settings after the MFP 102 is powered on.

[0120] When an automatic setting change requires a restart of MFP 102, terminal 104 can receive a notification indicating the requirement (S831). Therefore, user 600 can be prevented from missing the restart required to complete the setting change, and user 600 can restart the MFP immediately after making the setting change.

[0121] Following S841, the PWA can receive a push notification from the MFP 102 indicating that a restart has been completed via the push server 103, and display the received notification on the terminal 104 via the web browser 500. Therefore, the user 600 can be aware that the timed restart (reflecting the setting change) has been completed.

[0122] [Second Embodiment]

[0123] In the first embodiment, when a setting change requires restarting the MFP, the MFP 102 notifies the terminal 104 that a restart is needed. However, it is conceivable that the restart timing is delayed when the user ignores the notification, so automatic restarting may be desirable. In some cases, it may be desirable to confirm the latest setting information and make setting changes at the MFP power-on timer. In the second embodiment, the PWA's operation can be configured when a notification indicating that the MFP is powered on is received from the MFP 102, to flexibly handle such situations. In this embodiment, descriptions of the same parts as in the first embodiment will be omitted, and only the differences will be described.

[0124] The following will refer to Figure 17 This describes the sequence of processes performed when user 600 changes the settings of MFP 102 via PWA during a power outage, according to the second embodiment. Figure 17 In the various processes shown, the CPU 201 of the MFP 102 is used to... Figure 3The program of the software module shown and stored in storage device 204 is read into RAM 203 and executed to achieve the processing performed by MFP 102. Similarly, the CPU 201 of push server 103 is made to... Figure 4 The program of the software module shown and stored in storage device 204 is read into RAM 203 and executed to realize the processing performed by push server 103. Similarly, the CPU 201 of terminal 104 is made to... Figure 5 The program of the software module shown and stored in storage device 204 is read into RAM 203 and executed to perform the steps performed by the constituent device of terminal 104.

[0125] Figure 17 This is a diagram illustrating the sequence according to the second embodiment until the operation setting screen 1411 (described later) when the MFP 102 is powered on is displayed and the operation setting input on that screen is received. Figure 17 The difference from the first embodiment is that, in Figure 10 The process S1301 to S1303 follows S806. The difference will be described below.

[0126] In S1301, the PWA operating in terminal 104 displays an operation settings screen when MFP 102 is powered on. In the first embodiment, the PWA displays a message indicating that communication with MFP 102 is not possible (S807). However, in this embodiment, displaying the operation settings screen allows the user to configure operations more specifically when MFP 102 is powered on.

[0127] Figure 21 This shows an example of the operation setup screen 1411 displayed in S1301 when the MFP 102 is powered on. Figure 21 In this configuration, item 1421 is an option to display a notification indicating that the MFP 102 is powered on on terminal 104 when the MFP 102 is powered on. Item 1422 is an option to automatically apply settings changes stored in S805 to the MFP 102 when it is powered on and display a notification indicating that the MFP 102 is powered on on terminal 104. Item 1423 is a checkbox selected when item 1422 is selected, requiring the MFP 102 to be restarted to reflect the settings, and additionally automatically restarting the MFP 102. When item 1421 is selected, item 1423 will be disabled, and therefore cannot be enabled / disabled. Items 1421 and 1422 are in radio button format, and only one can be selected. The OK button 1424 is used to confirm the settings made on the operation settings screen 1411 when the MFP 102 is powered on.

[0128] In this embodiment, item 1422 is selected and the checkbox for item 1423 is turned off, which is the default state of the operation settings screen 1411. This is a setting for performing the same operation as in the first embodiment.

[0129] The settings modes that can be configured on the operation settings screen 1411 and the PWA operations in each mode are shown in Table 1. Details of the PWA operations in each mode will be described later.

[0130] Table 1

[0131]

[0132] In S1302, user 600 sets the operation when MFP 102 is powered on on the operation setting screen 1411 displayed in S1301, and presses the OK button 1424.

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

[0134] Figure 18 This is a diagram showing the sequence of processes performed after S1303 when MFP 102 is powered on. Figure 18 S811 to S813 and Figure 11 S811 to S813 are the same, so their description will be omitted.

[0135] In S1311, when a push notification is received in S813, the PWA operating in terminal 104 retrieves the operation settings details stored in data storage area 503 in S1303. Then, the PWA performs processing corresponding to the retrieved operation settings details.

[0136] The following will refer to Figure 19 Describes the sequence of processes when the operation setting details obtained in S1311 are in mode 1.

[0137] In S1321, the PWA operating in terminal 104 displays a notification on terminal 104 indicating that MFP102 has been powered on via web browser 500. Figure 22A An example of notification 1511 displayed at this time is shown. In this embodiment, notification 1511 displays a link 1512 for displaying a settings change screen for the settings to be changed. This is because the user 600, who does not want automatic settings, can check the latest settings details of the MFP 102 and change the settings change details as needed. In this case, it is convenient to easily display the settings change screen.

[0138] In S1322, for example, user 600 presses link 1512 in the notification displayed in S1321 and instructs PWA to display a settings change screen for the settings to be changed.

[0139] In S1323, similar to S802, the PWA uses information stored in the data storage area 503 to display the settings change screen before communicating with the MFP 102.

[0140] In S1324, similar to S803, PWA requests MFP 102 to obtain the latest settings to change the screen.

[0141] In S1325, the remote UI request processing unit 301 of MFP 102 obtains the setting information managed by the setting management unit 305 or the status information managed by the status management unit 303 of MFP 102 as needed, and generates the latest setting change screen information.

[0142] In S1326, the remote UI request processing unit 301 of MFP 102 will return the latest settings change screen information generated in S1325 as a response to PWA.

[0143] In S1327, the PWA receives the response from S1326 and displays the latest settings change screen. Subsequently, the user 600 confirms the screen details and makes additional settings changes as needed.

[0144] When the operation setting details obtained in S1311 are mode 2, the processing is the same as according to the first embodiment. Figure 11 The processing after S814 is the same, so its description will be omitted.

[0145] The following will refer to Figure 20 Describes the sequence of processes when the operation setting details obtained in S1311 are in mode 3.

[0146] Figure 20 S814 to S816 in the first embodiment Figure 11 The same applies to S821 and S822 when no restart is required, and S831 when a restart is required. The processing after S831 when a restart is required will be described below.

[0147] In S1351, the PWA operating in terminal 104 receives the indication in S831 that a restart is needed to complete the response to the setting change, and requests MFP 102 to restart.

[0148] In S1352, the remote UI request processing unit 301 of MFP 102 requests the setting management unit 305 to restart MFP 102, and the setting management unit 305 starts the restart of MFP 102.

[0149] In S1353, the remote UI request processing unit 301 of MFP 102 returns a response to PWA indicating that a restart has begun.

[0150] In S1354, the PWA stores information in data storage area 503 indicating the standby state after a restart is completed along with a setting change.

[0151] In S1355, similar to S841, the PWA displays screen 1271 indicating that the restart of MFP 102 has begun. Figure 16C ).

[0152] In S1356, the event management unit 304 of MFP 102 detects that MFP 102 has been powered on through the restart performed in S1352 as an event in MFP 102, and requests the notification sending unit 302 to send a push notification of the power-on event.

[0153] In S1357, similar to S812, the notification sending unit 302 of MFP 102 sends a push notification request to the push server 103 to notify the registered notification objects that MFP 102 has been powered on.

[0154] In S1358, similar to S813, the request receiving unit 403 of the push server 103 receives the push notification request from S1357 and sends its details to the notification sending unit 406. Based on the information included in the sent push notification request, the notification sending unit 406 sends a push notification indicating that the MFP 102 has been powered on to the terminal 104 to be notified.

[0155] In S1359, the PWA operating in terminal 104 checks whether the data storage area 503 contains information indicating a standby state indicating a restart completion accompanied by a setting change. In this embodiment, it is assumed that in S1354, terminal 104 stores information indicating a standby state indicating a restart completion accompanied by a setting change.

[0156] In S1360, the PWA displays a notification. This notification indicates that a setting change received in S804 has been made on the MFP 102, and indicates that a reboot of the MFP 102 reflecting the setting change has been completed. Figure 22B The notification 1521 displayed at this time is shown.

[0157] As described above, in this embodiment, the PWA operation (S1301 to S1303) can be configured when a push notification indicating power-on is received from MFP 102 (S1311) (S813). Therefore, the system 100 can flexibly respond to situations such as wanting to automatically restart MFP 102 to reflect setting changes, or wanting to determine the latest setting information and make setting changes at a time when MFP 102 is powered on.

[0158] When in Figure 17 When setting Mode 1 in Table 1 in S1302, the setting change details stored in S805 can be discarded. This is because, as Figure 19 As shown, in Mode 1, the latest settings change screen is retrieved after S1324. In this case, Figure 22A In notification 1511, link 1512 can be omitted.

[0159] [Third Embodiment]

[0160] In the first embodiment, the PWA service worker can receive a push notification indicating that the MFP 102 is powered on by operating the service worker processing unit 502 of the web browser 500. However, it is possible that the web browser 500 of the terminal 104 stops due to certain factors, and the service worker also stops. In this case, it is conceivable that the PWA will not receive the push notification indicating that the MFP 102 is powered on, and will not be able to automatically perform the setting changes received in S804. This allows the PWA in the third embodiment to perform the setting changes received in S804 even in this situation. In this embodiment, the description of the same parts as in the first embodiment will be omitted, and only the differences will be described.

[0161] Figure 23 This is a diagram illustrating the sequence of processes when a stopped web browser 500 is started in terminal 104. Figure 23 In the various processes shown, the CPU 201 of terminal 104 is used to... Figure 5 The program of the software module shown and stored in storage device 204 is read into RAM 203 and executed to perform the steps performed by the constituent device of terminal 104.

[0162] In S1601, the PWA is started when the web browser 500 on terminal 104 is started. For example, the web browser 500 is started as a trigger, such as when terminal 104 is restarted or when a command from user 600 is given to start the web browser 500 or the PWA.

[0163] In S1602, the PWA retrieves the settings change details for MFP 102 stored in data storage area 503. At this point, if the retrieved settings change details are empty (no settings change details are stored), the PWA ends this sequence. When stored settings change details are retrieved, the PWA proceeds... Figure 11 The processing after S815 is shown.

[0164] Therefore, even if the web browser stops and cannot receive push notifications indicating that the MFP 102 is powered on, the PWA can still automatically change the storage settings on the MFP 102 at a scheduled time when it starts.

[0165] [Fourth Embodiment]

[0166] There is a possibility that, besides the power failure of MFP 102, the PWA in the first embodiment may also be unable to make configuration changes due to a defect in the communication path with MFP 102. In this case, when communication with MFP 102 becomes possible, the PWA in the fourth embodiment will automatically make configuration changes. In this embodiment, descriptions of parts identical to those in the first embodiment will be omitted, and only the differences will be described.

[0167] Figure 24 This illustrates when according to the first embodiment Figure 10 The diagram shows the sequence of processes in S806 when communication with MFP 102 fails. As for situations where communication with MFP 102 fails, one can imagine situations such as a power outage on MFP 102 or a defect in the communication path between terminal 104 and MFP 102.

[0168] exist Figure 24 In the various processes shown, the CPU 201 of the MFP 102 is used to... Figure 3 The program of the software module shown and stored in storage device 204 is read into RAM 203 and executed to achieve the processing performed by MFP 102. Similarly, the CPU 201 of terminal 104 is made to... Figure 5 The program of the software module shown and stored in storage device 204 is read into RAM 203 and executed to perform the steps performed by the constituent device of terminal 104.

[0169] Suppose that S1701 and S1703 described below are repeated when storing the settings change details of MFP 102 in data storage area 503.

[0170] In S1701, the PWA operating in terminal 104 sends a status confirmation request to MFP 102.

[0171] In S1702, when communication with MFP 102 is restored and the status confirmation request from S1701 is received, the remote UI request processing unit 301 of MFP 102 returns a response indicating that the request has been received. When this response is returned, Figure 11 The processing after S814 is performed and excluded from repeated processing.

[0172] In S1703, when communication with MFP 102 is not restored, PWA waits for a predetermined time and repeats the process of S1701.

[0173] Therefore, even if communication with MFP 102 is unavailable and MFP 102 is powered off, PWA can automatically change the stored settings on MFP 102 when communication with MFP 102 is restored.

[0174] [Other Embodiments]

[0175] At least two embodiments from the first, second, third, and fourth embodiments can be combined. For example, in the third embodiment, when the stored settings change details are obtained after S1602, PWA performs... Figure 11 The processing after S815 in the first embodiment (but it can also be performed) Figure 20 The processing after S815 (second embodiment). In the fourth embodiment, similarly, when a response indicating that the status acknowledgment request in S1701 has been received is sent, PWA performs... Figure 11 The processing after S814 in the first embodiment (but it can also be performed) Figure 20 The processing after S814 (second embodiment).

[0176] In the above embodiments, MFP is described as an example of a network device, but devices that include a web server and are capable of providing a remote UI (such as a network router, surveillance camera, or digital medical device) can be used.

[0177] In the above embodiments, push server 103 and MFP 102 are different devices, but MFP 102 may include push server.

[0178] Embodiments of the invention 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 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 device, 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.

[0179] 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.

[0180] While this disclosure has been described with reference to exemplary 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 cover all such variations and equivalent structures and functions.

[0181] This application claims priority to Japanese Patent Application No. 2024-151355, filed on September 3, 2024, the entire contents of which are incorporated herein by reference.

Claims

1. A network device including a web server, the network device comprising: a providing section configured to provide, by the web server, a setting screen for operating setting values of a plurality of setting items of the network device to a web browser via a network; and a reflecting section configured to reflect the setting values in the network device in response to an operation on the setting values, wherein the providing section provides, using the web server, a website for installing software in a user terminal, the software being a progressive web application for providing a function of operating a setting value of at least one of the plurality of setting items, and wherein the reflecting section reflects at least one setting value in the network device in response to receiving details of an operation on at least one setting value using the progressive web application from the user terminal via the network, regardless of whether or not the network device has provided the setting screen.

2. The network device of claim 1, further comprising: a notifying section configured to send, to the user terminal via the network, a push notification corresponding to an event that occurs in the network device.

3. The network device of claim 2, wherein, The notifying section sends, as the push notification, a notification indicating whether or not the network device is to be restarted to reflect the setting values.

4. The network device of claim 3, further comprising: a processing section configured to cause the network device to start a restart process in response to receiving, from the user terminal via the network, a request for a restart of the network device based on the notification.

5. The network device of claim 2, wherein, When the network device is powered on, the notifying section sends a notification indicating that the network device is powered on, and wherein, after sending the notification indicating that the network device is powered on, the reflecting section reflects the setting values in the network device in response to receiving details of an operation on the setting values from the user terminal via the network.

6. The network device of claim 2, wherein, The providing section additionally provides, using the software of the progressive web application, an operation setting screen for receiving a setting at the time of power-on of the network device.

7. The network device of claim 6, wherein, The operation setting screen includes an item for receiving an instruction to automatically perform a restart of the network device to reflect the setting values.

8. The network device of claim 6, wherein, The providing section provides, via the network, a latest setting screen in response to receiving, from the user terminal via the network, a request for acquiring the latest setting screen.

9. The network device of claim 6, further comprising: a processing section configured to start a restart process in response to receiving, from the user terminal via the network, a request for restarting the network device based on the push notification, and wherein the notifying section additionally sends, to the user terminal, a notification indicating that the network device has been restarted.

10. The network device of claim 2, wherein, When the notification indicating that the network device is powered on is sent as the push notification while the software of the progressive web application of the user terminal is stopped, the reflecting section reflects the setting values in the network device in response to details of an operation on the setting values after the software of the progressive web application of the user terminal is started.

11. The network device of claim 1, wherein, When communication between the network device and the user terminal cannot be performed due to a reason other than the network device being powered off, the reflecting section reflects the setting value in the network device in response to details of an operation on the setting value being received from the user terminal via the network after the communication can be performed.

12. The network device of any of claims 1 to 11, wherein, The network device is an image processing apparatus including a scanner or a printer.

13. The network device of claim 12, wherein, The plurality of setting items are included in settings related to an environment or an application of the image processing apparatus.

14. A method of a network device including a web server, the method comprising: providing, using the web server, a setting screen for operating setting values of a plurality of setting items of the network device to a web browser via a network; and reflecting the setting values in the network device in response to the operation, wherein the providing the setting screen includes providing, by the web server, a website for installing software in a user terminal, the software being a progressive web application for providing a function of operating the setting values of at least one setting item among the plurality of setting items, and wherein the reflecting the setting values includes reflecting at least one setting value in the network device in response to details of an operation on the at least one setting value using the progressive web application being received from the user terminal via the network, regardless of whether the network device has provided the setting screen.

15. A non-transitory storage medium storing a program of a network device including a web server, the program causing a computer to perform steps of a method of the network device, the method comprising: providing, using the web server, a setting screen for operating setting values of a plurality of setting items of the network device to a web browser via a network; and reflecting the setting values in the network device in response to the operation, wherein the providing the setting screen includes providing, by the web server, a website for installing software in a user terminal, the software being a progressive web application for providing a function of operating the setting values of at least one setting item among the plurality of setting items, and wherein the reflecting the setting values includes reflecting at least one setting value in the network device in response to details of an operation on the at least one setting value using the progressive web application being received from the user terminal via the network, regardless of whether the network device has provided the setting screen.

Images