Network device, control method, non-transitory computer-readable storage medium, and program product

Abstract

The invention discloses a network apparatus, a control method, a non-transitory computer-readable storage medium, and a program product. A network device equipped with a server includes: a providing unit configured to provide, using the server, a setting screen for setting a parameter for installing a progressive Web application corresponding to the network device; and a transmitting unit configured to transmit a manifest file corresponding to the parameter to a terminal to install the progressive Web application on the terminal.

Description

Technical Field

[0001] This invention relates to a technology for sending notifications from network devices such as image processing devices to client devices. Background Technology

[0002] Network devices, such as image processing equipment, can display their operational status on their own monitors. Examples of network device operational status include error occurrences, counter information, information about consumable consumption levels, and notifications from administrators.

[0003] In addition, network devices provide the ability for client devices that have accessed the network to verify the network's operational status, perform tasks, and configure various settings. This ability is called a Remote User Interface (RUI). Each network device is equipped with an internal network server and uses a web browser, for example, from an external device to access the RUI's Uniform Resource Locator (URL) to display the RUI. The RUI is typically used within a Local Area Network (LAN) and can be accessed by entering the private Internet Protocol (IP) address assigned to the network device as the URL into a web browser on a terminal (PC or tablet).

[0004] Japanese Patent Application Publication No. 2009-271727 describes a technology that improves the accessibility of the RUI by enabling the image processing device itself to automatically generate shortcut icons, thereby eliminating the need to enter an IP address to access the RUI.

[0005] Furthermore, Progressive Web Apps (PWAs) are a technology that enables websites to be used like native apps. In this context, a traditional native app is an app that a user must manually download and install from an app store onto their device. In contrast, a PWA can be installed by accessing a PWA-enabled website via a web browser on the device, and it's a technology that allows users to use the website (web app) on their device with a similar user experience to native apps. Summary of the Invention

[0006] A network device equipped with a server includes: a providing unit configured to use the server to provide a settings screen for setting parameters for installing a progressive web application corresponding to the network device; and a sending unit configured to send a manifest file corresponding to the parameters to a terminal to install the progressive web application on the terminal.

[0007] The features of this disclosure will become apparent from the following description of embodiments with reference to the accompanying drawings. The following description of embodiments is by way of example. Attached Figure Description

[0008] Figure 1 This is a diagram illustrating an example configuration of a network system.

[0009] Figure 2A and Figure 2B This is a hardware configuration diagram.

[0010] Figure 3 This is a software configuration diagram.

[0011] Figure 4 This is an image showing a sample screen of a Remote User Interface (RUI).

[0012] Figure 5 This is a diagram showing the installation sequence for Progressive Web Applications (PWAs).

[0013] Figure 6 This is an image showing a sample screen of the RUI during PWA installation.

[0014] Figure 7 This is a screenshot showing an example screen when RUI is launched as a PWA.

[0015] Figure 8 This is an example screenshot showing the display icon generated after PWA installation.

[0016] Figure 9 This is a diagram showing the installation sequence of the PWA.

[0017] Figure 10 This is a screenshot showing an example of a page displaying the PWA installation URL generation page.

[0018] Figure 11 This is an example screenshot showing the display icon generated after PWA installation.

[0019] Figure 12 This is an image showing a sample screen of the display page, through which PWA icon settings are configured via RUI.

[0020] Figure 13 This is an example screenshot showing the PWA installation URL generation page when the PWA icon settings are configured. Detailed Implementation

[0021] In this embodiment, the network device has a mechanism that provides a combination of two technologies: Remote User Interface (RUI) and Progressive Web Application (PWA).

[0022] For example, by accessing the RUI of a network device through a web browser, a PWA that supports at least one or more functions of the network device can be downloaded and installed on an information processing device running a web browser. In this case, as a function supported by the PWA, at least one or more functions of the RUI can be provided for use as a web application.

[0023] Furthermore, the icon displayed on the information processing device for the PWA installed on the information processing device depends on the information preset on the website providing the PWA. For example, the icon is generated based on the name and image that directly indicate, for example, the model of the network device and the type of firmware.

[0024] In this scenario, assume the primary user of the RUI is an administrator with administrative privileges (the administrator) managing network devices. Such an administrator might manage multiple network devices in an office or similar environment. In an office, multiple network devices of the same model might be installed on the office network. In this management environment, when an administrator attempts to manage devices using a PWA, multiple similar or identical icons will be generated for the multiple PWAs corresponding to the different network devices and displayed on the administrator's information processing device. Therefore, it is often difficult for the administrator to distinguish network devices by their icons, leaving room for improvement in operability.

[0025] In the following description, this embodiment will use the accompanying drawings and other information to illustrate an example in which the above-described operability of the RUI and the corresponding PWA provided by the image processing device used as a network device is improved.

[0026] First Embodiment

[0027] Figure 1 This is a diagram illustrating an example configuration of a network system. Figure 1 In this disclosure, push server 131, terminal 151, and multifunction peripheral device (MFP) 171 are interconnected via networks 111 and 113. Networks 111 and 113 are so-called communication networks such as the Internet, implemented using, for example, LANs, WANs, telephone lines, dedicated digital lines, asynchronous transmission mode (ATM) lines, frame relay lines, cable television lines, and wireless lines for data broadcasting. It is sufficient for networks 111 and 113 to be capable of sending and receiving data. In this disclosure, network 111 is the Internet, and network 113 is, for example, the Internet or a wired or wireless LAN established on a network within a typical home or office.

[0028] Push server 131 is a server computer that communicates with terminal 151 and MFP 171. Alternatively, push server 131 can be constructed using, for example, cloud computing technology. The functionality of push server 131 can be implemented by a single server or a single virtual server, or by multiple servers or multiple virtual servers. Alternatively, multiple virtual servers can run on a single server. Note that push server 131 is a necessary server for implementing push notification functionality as one of the PWA features.

[0029] Terminal 151 is an example of an information processing device used by users such as administrators. Specifically, terminal 151 is a device capable of running a web browser, such as a personal computer (PC), laptop, smartphone, or tablet. Terminal 151 can also be a mobile terminal with an internal environment in which various programs, such as a general-purpose operating system (OS), can run.

[0030] Terminal 151 has the functions of receiving notification messages from push server 131, displaying RUI provided by MFP 171, and accepting operations from user 153 to send data to and receive data from various information processing devices. User 153 uses the management system according to this embodiment to manage device setting information about MFP 171 or monitor the status of MFP 171.

[0031] The MFP 171 is an example of an image processing device used as a network device. The MFP 171 shown is a multi-functional peripheral device and, for example, an image processing device having at least one or more functions such as scanning, printing, faxing, and communication. Other examples of network devices to which this embodiment can be applied include devices equipped with a network server and capable of providing a RUI, such as network routers, surveillance cameras, and digital medical devices.

[0032] Each MFP 171 has the function of providing a RUI in response to a request from terminal 151, and the RUI can be accessed through an application (such as a web browser) on terminal 151. MFP 171 detects its device status and events (e.g., parts replacement and internal device error alarms), stores them as device information within MFP 171, and can provide this various types of device information to terminal 151 via the RUI. MFP 171 has the function of sending the aforementioned various types of device information to an external management server, which can then manage MFP 171 by receiving and processing the various types of device information sent from MFP 171. Furthermore, by using push server 131, when an internal event occurs, MFP 171 can send push notifications to terminal 151 used by user 153 according to preset rules.

[0033] Figure 2A and Figure 2B This is a diagram illustrating an example of the hardware configuration of information processing devices such as push server 131, terminal 151, and each MFP 171.

[0034] Figure 2A This is a diagram showing the hardware configuration of push server 131 and terminal 151.

[0035] System bus 212 manages the data flow within the device. Central processing unit (CPU) 214 controls the entire device. CPU 214 executes applications and the operating system, such as those stored in hard disk drive (HDD) / solid-state drive (SSD) 222, and performs control to store information, files, and other information required for program execution in random access memory (RAM) 218. Graphics processing unit (GPU) 216 performs arithmetic processing primarily required for displaying images and videos. RAM 218 is a temporary storage unit and serves as the main memory, workspace, etc., for CPU 214 and GPU 216. Read-only memory (ROM) 220 is a storage unit that internally stores various types of data, such as basic I / O programs. HDD / SSD 222 is an external storage unit. HDD / SSD 222 serves as a large storage unit and stores applications such as web browsers, server group programs, the operating system, and related programs. Network interface card (NIC) 224 exchanges data with external devices via NIC 224 and networks 111 and 113. Camera 226 is located on terminal 151 and includes a rear camera for capturing images of the surrounding area and a front camera for capturing images of the user. By analyzing the QR code captured by camera 226 using an application stored in HDD / SSD 222, a website can be accessed or a specific application can be launched. Display 228 is a display unit that displays information needed to operate, for example, the UI provided by an external web server and MFP 171. Furthermore, display 228 can be a device with the ability to accept operation commands from the user, such as a touch panel. Proximity communication interface (I / F) 230 is an I / F for proximity communication such as NFC and Bluetooth. Data exchange between information processing devices can be achieved using proximity communication I / F 230. Input-output I / F 232 is an interface for controlling input and output to external devices and controlling input-output devices such as a mouse and keyboard connected to input-output I / F 232.

[0036] Figure 2BThis diagram illustrates the hardware configuration of the MFP 171 and shows an image processing device as an example. The CPU 254 reads the program stored in the ROM 258 and provides overall control of the entire device via the internal bus 252. RAM 256 serves as the CPU 254's memory or working area. The HDD / SSD 260 is a storage device for storing various types of data. The NIC 262 exchanges data unidirectionally or bidirectionally with external network devices. The print controller 264 controls the print unit 266 and issues print commands to the print unit 266 based on various control commands for the MFP 171. The print unit 266 executes printing based on commands from the print controller 264. The input-output device 270 indicates multiple components responsible for inputting to and outputting from the MFP 171. Specifically, it accepts input from the user (button input, etc.) and sends signals corresponding to the input to each of the aforementioned processing units via the input-output I / F 268. In addition, the input-output device 270 also includes a display device (such as a touch panel) for providing necessary information to the user and accepting user operations. Furthermore, the input-output device 270 also includes a scanning device for reading documents and accepting them as electronic data, and sensors for detecting the remaining quantity and replacement of parts and consumables.

[0037] Note that the configuration of the information processing equipment described above is an example and is not limited to this. Figure 2A and Figure 2B The example configuration is shown below. For example, depending on the characteristics of the data and programs, the storage location of the data and programs can be, for example... Figure 2A and Figure 2B Changes can be made between RAM, ROM, HDD / SSD, etc., as shown. Furthermore, Figure 2A and Figure 2B Each CPU and each GPU described herein executes processing based on a program stored in its respective HDD / SSD, thereby achieving, as Figure 3 The processing in the software configuration shown.

[0038] Figure 3 The software configuration that includes selected functions relevant to this embodiment is shown within terminal 151 and MFP 171.

[0039] Terminal 151 includes an OS display unit 311 and a web browser 321. The web browser 321 includes a web browser display unit 323, a content acquisition unit 325, a data acquisition unit 327, a data sending unit 329, and a web application processing unit 331, which are internal software modules. The web browser 321 also includes a service worker processing unit 333, a content storage unit 335, a device information storage unit 337, and a PWA installation processing unit 339.

[0040] OS display unit 311 is a software module that displays the functions provided by the OS as a graphical user interface (GUI) on the display 228. When user 153 operates terminal 151 through the GUI, or after installing the PWA described below, OS display unit 311 has the function of displaying the corresponding PWA icons added to the desktop, folders, home screen, etc.

[0041] Next, each software module of the web browser 321 will be described. The web browser display unit 323 is a software module that displays the RUI provided by the MFP 171 on the display 228. In this embodiment, it will be described as follows, wherein each MFP 171 is equipped with a web server, the RUI provided by the MFP 171 is provided as a web application, and the RUI is displayed on the web browser display unit 323.

[0042] Content acquisition unit 325 is a software module that acquires the web content required to display the RUI on the web browser display unit 323 from content provision unit 357. Examples of web content are based on Hypertext Markup Language (HTML), JavaScript, and Cascading Style Sheets (CSS). Furthermore, examples of web content include service workers (scripts running as background processes) and manifest files (files describing PWA installation settings), which are components of the PWA.

[0043] The data acquisition unit 327 is a software module that communicates with the data providing unit 359 to obtain device information such as setting values ​​within the MFP 171. The data acquired by the data acquisition unit 327 and the aforementioned web content are combined and displayed on the web browser display unit 323 to implement RUI. The data acquisition unit 327 can also asynchronously acquire data from the data providing unit 359 via operations performed relative to the user 153 to achieve dynamically changing RUI content. The data sending unit 329 is a software module that sends the setting values ​​to be applied to the MFP 171, as well as input values ​​and files from the user 153, to the data receiving unit 361, and sends the user ID and password used to log in to the RUI.

[0044] The web application processing unit 331 is a software module that analyzes various types of web content and data obtained from the MFP 171 and fully controls the behavior of web applications running on the web browser 321.

[0045] The service worker processing unit 333 is a software module that registers the service workers acquired by the content acquisition unit 325 in the web browser 321 and runs the service workers in the background. Since the service workers operate in the background, functions such as improving RUI display speed can be achieved through caching control, offline operation, background synchronization, and push notifications.

[0046] Content storage unit 335 is a storage area and module within web browser 321 used to store various types of web content acquired by content acquisition unit 325. Specifically, service worker processing unit 333 stores registration information about service workers in content storage unit 335 and stores various types of web content in content storage unit 335 when performing cache control.

[0047] The device information storage unit 337 is a storage area and storage module within the web browser 321 used to store device information about the MFP 171, such as that acquired by the data acquisition unit 327, and is stored in a storage area such as local storage. By storing device information in the device information storage unit 337, an improved RUUI display speed, similar to web content caching, can be expected. Furthermore, even when the MFP 171 is offline, device information about the MFP 171 can be referenced, and settings to be applied to the MFP 171 can be pre-entered.

[0048] PWA installation processing unit 339 is a software module that performs processing related to PWA installation. The PWA installation method and installation sequence will be described below.

[0049] MFP 171 includes a device information generation unit 351, a device information storage unit 353, a content storage unit 355, a content provisioning unit 357, a data provisioning unit 359, a data receiving unit 361, a device information updating unit 363, a login processing unit 365, and a user information storage unit 367. Furthermore, MFP 171 includes a manifest file generation unit 369, a manifest file updating unit 371, and a manifest file storage unit 373, which are features of this disclosure.

[0050] Device information generation unit 351 is a software module that generates device information such as the latest status and setting values ​​within MFP 171. Device information storage unit 353 is a software module that stores device information such as the status generated by device information generation unit 351 and the setting values ​​within MFP 171 updated by device information update unit 363 (described below). Content providing unit 357 is a software module that provides various types of web content forming the RUI in response to requests from content acquisition unit 325.

[0051] The data providing unit 359 is a software module that provides data such as device information and setting values ​​about the MFP 171 in response to a request from the data acquiring unit 327. The data receiving unit 361 is a software module that receives requests sent from the data sending unit 329.

[0052] The device information update unit 363 is a software module that, in response to device information generated by the device information generation unit 351 and a change request for setting values ​​received by the data receiving unit 361, performs an update to obtain the latest device information. The device information update unit 363 stores the updated device information in the device information storage unit 353. The login processing unit 365 is a software module that receives login requests for the RUI from the data sending unit 329 via the data receiving unit 361 and compares the received data with user account information stored in the user information storage unit 367 to determine whether login is permitted. The user information storage unit 367 is a software module that stores account information about users using the RUI.

[0053] Table 1 below shows an example of data managed by the user information storage unit 367.

[0054] Table 1

[0055] User ID password Role User A ********** administrator User B ********** maintainers User C ********** Viewer

[0056] The User ID column corresponds to a unique ID that identifies the user. The Password column corresponds to the basic authentication password used to log in using the User ID. The Login Processing Unit 365 compares the combination of User ID and password included in the login request from the Data Sending Unit 329 with Table 1. If they match, the Login Processing Unit 365 returns a login result indicating a successful login to the Data Sending Unit 329. The Role List indicates the user's permission level. For example, if the user is an "Administrator," the user can use all RUI functions. If the user is a "Maintainer," the user can only use functions related to the maintenance of the MFP 171. If the user is a "Viewer," the user can only view device information. These attributes are used to implement this access control. When accessing the RUI, the requirement for login processing can be toggled through the settings of the MFP 171. If login is not required, i.e., if all users within the local area network are allowed to use the RUI, access control is not enforced.

[0057] The manifest file generation unit 369 is a software module that generates manifest files describing the PWA installation settings. The manifest file update unit 371 is a software module that performs update processing on the manifest file in response to a command from user 153 to update the manifest file. The manifest file storage unit 373 is a software module that stores the manifest files generated and updated by the manifest file generation unit 369 and the manifest file update unit 371. The operation of the manifest file generation unit 369 and the manifest file update unit 371, which are features of this disclosure, will now be described.

[0058] Figure 4This is a diagram showing an example screen of the RUI provided by a typical MFP. Screen 411 shows the screen of the RUI displayed on the web browser display unit 323.

[0059] Next, use Figures 5 to 8 This document describes an example of the processing sequence for installing the RUI provided by MFP 171 as a PWA on terminal 151, and an example screen on web browser display unit 323.

[0060] Figure 5 This diagram illustrates the sequence from user 153 accessing the RUI of MFP 171 via command terminal 151 to installing the corresponding PWA. Figure 6 This is a diagram showing an example screen on the web browser display unit 323 when a PWA is installed. Figure 7 This is a diagram showing an example screen on the web browser display unit 323 when the RUI is displayed as PWA. Figure 8 This is a diagram showing an example screen of the display icons displayed on the OS display unit 311 after PWA is installed.

[0061] First, in S511, user 153 commands the web browser 321 of terminal 151 to access the RUI of MFP 171. Specifically, user 153 accesses the RUI of MFP 171 by entering the IP address assigned to MFP 171 in the address bar of web browser 321.

[0062] In S513, the content acquisition unit 325 requests web content from the content providing unit 357 for displaying the RUI on the web browser display unit 323. In S515, the content providing unit 357 returns the requested web content to the content acquisition unit 325. In S517, the web application processing unit 331 analyzes the details of the web content acquired in S515 and performs processing to display the RUI on the web browser display unit 323.

[0063] In S519, the service worker processing unit 333 analyzes the service worker script included in the web content acquired in S515 and registers the service worker in the content storage unit 335. In this case, if the service worker script describes commands related to cache control, the service worker processing unit 333 stores the web content acquired in S515 as a cache in the content storage unit 335 based on the described information.

[0064] In S521, the PWA installation processing unit 339 performs pre-installation processing to check whether the web content obtained in S515 includes a manifest file. If it is determined that a manifest file is included, the PWA installation processing unit 339 performs processing such that... Figure 6 The various types of objects shown are displayed on the web browser display unit 323. Note that in this case, it is assumed that the manifest file is sent from MFP 171 to terminal 151 as part of the web content; however, the manifest file can be sent from MFP 171 to terminal 151 separately from the web content.

[0065] Figure 6 Screen 611 shows an example screen on the web browser display unit 323 during the processing in S521. Button 631 is displayed when the web application being viewed can be installed as a PWA. When user 153 presses button 631, a notification object represented by 633 is displayed. Button 635 is the button pressed by user 153 when selecting to install the PWA. Button 637 is the button pressed by user 153 when selecting not to install the PWA. In this case, the scenario where user 153 presses button 635 to begin installing the PWA will be described (execution of S523).

[0066] In S523, the PWA installation processing unit 339 accepts the PWA installation command based on user 153 pressing button 635, and the processing proceeds to S525. In S525, the PWA installation processing unit 339 executes the PWA installation process. The following describes the manifest file used by the PWA installation processing unit 339 to execute the PWA installation process.

[0067] Here is an example of a manifest file (JSON format).

[0068]

[0069] In addition to the keys described in the examples above, other keys can be specified. The “name” key, “short_name” key, and “icons” key, which are relevant to the features of this embodiment, are described below.

[0070] The value of the “name” key specifies the name (application name) to be assigned to the icon generated when the PWA is installed in the PWA installation processing unit 339.

[0071] Similar to the "name" key, the "short_name" key is used to specify the name of the icon generated when the PWA is installed in the PWA installation processing unit 339.

[0072] However, the PWA installation processing unit 339 determines which value to use—the "name" key or the "short_name" key—based on the type of terminal 151. For example, if terminal 151 is a terminal with a relatively large display 228 (such as a PC), the value of the "short_name" key is used. If terminal 151 is a terminal with a small display 228 (such as a smartphone), the value of the "short_name" key is used. That is, the normal application name is usually specified in the "name" key, and the shortened application name is specified in the "short_name" key.

[0073] The value of the "icons" key specifies the filename of the image used as the icon generated by the PWA installation processing unit 339 when installing the PWA. The "src" key within the "icons" key specifies the URL of the image file to be used as the icon image; in the example above, a relative path is used. The "sizes" key specifies the dimensions of the image. The "type" key specifies the Multipurpose Internet Mail Extensions (MIME) type of the image. The value of the "icons" key is an array, allowing multiple values ​​to be specified. Therefore, in the same manner as for the "name" and "short_name" keys, the PWA installation processing unit 339 uses an image of appropriate size based on the type of terminal 151.

[0074] In this embodiment, the example manifest file is the default manifest file set in MFP 171. If the device type or firmware version of MFP 171 is the same, it is assumed that the manifest file is similar to the manifest file of another MFP 171. In S525, when PWA installation processing unit 339 performs PWA installation processing, configuration files for executing various types of web content constituting the RUI of MFP 171 are installed on web browser 321. At the same time, according to the information described in the manifest file, an icon for launching PWA is generated on OS display unit 311 (desktop, main screen, etc.). Thus, as a result of PWA installation processing unit 339 performing PWA installation processing, user 153 can use the RUI of MFP 171 as a PWA.

[0075] Note that the PWA operates as a processing mechanism of the web browser 321; therefore, it is assumed that the actual PWA icon generated during installation is, for example, a shortcut icon specifying the executable file and startup options for launching the web browser 321. However, since the implementation method of PWA-related functions depends on the implementation of the web browser, the implementation method of PWA-related functions is not necessarily limited to this method. User 153 can launch the PWA corresponding to the RUI of MFP 171 by pressing the icon generated by the PWA installation processing unit 339.

[0076] Figure 7 Screen 711 is a sample screen of the application (RUI application) provided when user 153 launches the installed PWA. The web content displayed on screen 711 is the same as that displayed on screen 411, but it differs from the display of a regular web browser in that, for example, screen 711 does not have an address bar. This provides a user experience similar to the original application.

[0077] Reference Figure 8 Screen 811 is an example screen on the OS display unit 311 after the PWA installation processing unit 339 installs the PWA. Screen 811 displays icons of files located at certain paths within the file system. Icon 831 is the icon used to launch the PWA corresponding to the RUI of the MFP 171. The group of icons displayed on screen 811 is an example of the display icons generated when multiple RUIs of the MFP 171 are installed as PWAs on a single terminal 151. In this case, the manifest file is not set up so that the MFP 171s can be distinguished from each other, so the PWA installation processing unit 339 generates icons with similar images and names. Therefore, it is difficult for the user 153 to grasp the correspondence between the icons and the PWAs corresponding to the RUIs of the MFP 171. To solve this problem, the following method is used... Figure 9 , Figure 10 and Figure 11 This describes the PWA installation method according to this disclosure.

[0078] Figure 9 This is a diagram showing the sequence of installation up to the point in this embodiment. Figure 10 The setup screen provided by MFP 171 (hereinafter referred to as the "PWA Installation URL Generation Page") is shown. Before installing the PWA to the terminal, settings related to the PWA icon are configured through the setup screen. Figure 11 This is a diagram showing an example screen of the display icon generated by the PWA installation processing unit 339 after PWA installation.

[0079] In S911, the web browser 321 of terminal 151 receives a command from user 153 to access the PWA installation URL generation page of MFP 171. Specifically, user 153 enters the URL of the PWA installation URL generation page into the address bar of web browser 321 to access the PWA installation URL generation page provided by MFP 171. Figure 4 The webpage shown is different from the normal RUI. The following describes a sample screen displaying the PWA installation URL generation page and its behavior as a webpage.

[0080] In S913, the content acquisition unit 325 requests web content from the content providing unit 357 for displaying the PWA installation URL generation page on the web browser display unit 323. In S915, the content providing unit 357 returns the requested web content to the content acquisition unit 325.

[0081] In S917, the web application processing unit 331 analyzes the details of the web content obtained in S915 and performs processing to display the PWA installation URL generation page on the web browser display unit 323.

[0082] The following will use Figure 10 This describes the PWA installation URL generation page. Screen 1011 is a screen displaying the PWA installation URL generation page on the web browser display unit 323. In this embodiment, a manifest file is dynamically generated based on the values ​​input to the PWA installation URL generation page and returned to the content acquisition unit 325 so that the PWA installation processing unit 339 can control the icons generated during PWA installation.

[0083] Input field 1031 is used to specify the icon name and receives the value to be set in the "name" key of the manifest file. Input field 1033 is used to specify the abbreviated icon name and receives the value to be set in the "short_name" key of the manifest file. Note that settings such as the device name and installation location set via the RUI of the MFP 171 can be entered into input fields 1031 and 1033 as default values. Drop-down menu 1035 is a drop-down menu for selecting the image to be used for the icon, and the selected image is set in the "icon" key of the manifest file. The image that can be selected using drop-down menu 1035 is an image pre-stored in the content storage unit 355 of the MFP 171. Similar to drop-down menu 1035, button 1037 is a button for selecting the image to be used for the icon. However, pressing button 1037 allows user 153 to select a pre-prepared image (an image stored in terminal 151). 1039 represents the area where a preview of the icon generated by the PWA installation processing unit 339 is displayed based on the setting values ​​entered into the fields represented by 1031, 1033, and 1035 or 1037.

[0084] In S919, the web application processing unit 331 accepts setting values ​​input by user 153 into fields represented by 1031, 1033, and 1035 or 1037. In S921, the web application processing unit 331 displays a preview of the icon in area 1039 along with the input setting values. Button 1041 opens the installation page (i.e., as shown in the image). Figure 6 The button shown is the RUI button of the MFP 171.

[0085] In S923, the web application processing unit 331 accepts the command in response to the user 153 pressing button 1041. S925, S927, and S929 are processes performed when the user 153 presses button 1037 to select a pre-prepared image.

[0086] In S925, the data sending unit 329 uploads the image selected by user 153 to the data receiving unit 361. In S927, the data receiving unit 361 stores the image received in S925 in the content storage unit 355. In S929, the data receiving unit 361 returns a response to the data sending unit 329 indicating that the image upload was successfully completed. In S931, the web application processing unit 331 generates a parameterized URL. In this case, the parameterized URL is, for example, a URL obtained by embedding parameters corresponding to the "name" key, "short_name" key, and "icons" key of the manifest file into the URL string of the RUI.

[0087] Example of a parameterized URL:

[0088] GET https: / / 192.168.10.5 / portal_top? name=Product-AAA_%E3%83%93%E3%83%ABA1F%E5%8D%97%E8%A5%BF_AAAA01&short_name=AAAAA01&icons=%2Fmfp_icon.png

[0089] Note that in the URL example above, the "sizes" and "type" in the "icons" key are omitted because these "sizes" and "type" can be automatically determined on the MFP 171 side.

[0090] In S933, the content acquisition unit 325 sends a request to the content provision unit 357 for the web content constituting the RUI using the parameterized URL generated in S931. In S935, the content provision unit 357, having received the request for the web content, instructs the manifest file generation unit 369 to generate a manifest file corresponding to the parameters of the parameterized URL. Then, the manifest file generation unit 369 generates the manifest file by mapping values ​​to corresponding keys within the manifest file based on the parameterized URL parameters.

[0091] The following shows an example of a manifest file generated by manifest file generation unit 369.

[0092]

[0093]

[0094] In S937, the content providing unit 357 returns web content similar to that in S515 and the manifest file generated in S935 to the content obtaining unit 325. When the processing in S937 is complete, the processing proceeds to S939. The processes performed in S939, S941, S943, S945, and S947 are the same as those performed in S517, S519, S521, S523, and S525, and therefore will be omitted from the description.

[0095] In this case, Figure 11 The image shows the effect of using... Figure 9 and Figure 10 The description describes an example screen of the generated icon. Similar to screen 811, screen 1111 is a screen displayed on the OS display unit 311. Icon 1131 is an icon generated by the PWA installation processing unit 339 in S947. The icon group in the display area of ​​icon 1131 and screen 1111 is not an icon with a similar name and similar image as in the case of icon 831, but rather an icon with an image whose name is specified by the user 153 through the PWA installation URL generation page.

[0096] In this way, by dynamically generating a manifest file using a parameterized URL, user 153 can control the icon generated during installation and more easily identify the correspondence between the icon and the PWA corresponding to the RUI of MFP 171. Note that this embodiment has described a method for setting the PWA icon via a PWA installation URL generation page. However, essentially the same effect can be achieved even without using this PWA installation URL generation page. For example, a similar process can be performed by user 153 preparing a parameterized URL in advance in a text editor and directly entering the parameterized URL into the address bar of the web browser display unit 323. Therefore, it is sufficient to send parameters from terminal 151 to MFP 171 using some method and dynamically generate a manifest file for installing the PWA based on the parameters. Therefore, the method of sending parameters is not limited. In addition, besides the "name" key, "short_name" key, and "icons" key mainly described in this embodiment, the manifest file for installing the PWA also includes keys that can be set as options. These keys can also be set using URL parameters.

[0097] Second Embodiment

[0098] In the first embodiment, a method for generating a page using a PWA installation URL and generating a PWA icon with an image and name specified by the user has been described.

[0099] In contrast, for example, a user 153 with administrator privileges can pre-configure settings related to the PWA icon using the RUI of the MFP 171, instead of a single user 153 specifying the name and image of the PWA icon each time. In a second embodiment, a method will be described in which a user 153 with administrator privileges pre-configures the PWA icon settings for each MFP 171.

[0100] first, Figure 12 This is a diagram illustrating an example screen of the RUI provided by the MFP 171 in the second embodiment. Screen 1211 shows the RUI displayed on the web browser display unit 323, and displays a settings screen related to the PWA. Screen 1211 is displayed when a user 153 with administrative privileges logs into the RUI. For example, the user with the "Administrator" role shown in Table 1 corresponds to a user with administrative privileges. Button 1231 is the same as button 631, and is a button for installing the PWA. Checkbox 1233 is a checkbox for selecting whether to allow user 153 to use the MFP 171's RUI as a PWA.

[0101] The first embodiment is described assuming that the RUI of the MFP 171 is used as a PWA; however, it is also possible to restrict the user 153 from using the RUI as a PWA by using checkbox 1233 as a configuration setting. When checkbox 1233 is not selected, i.e., the setting disallows the use of the RUI as a PWA, the content providing unit 357 does not return the manifest file to the content acquiring unit 325. Checkbox 1235 is a box that receives the selection of whether to customize the icon generated by the PWA installation processing unit 339 when installing the PWA on the MFP 171 side.

[0102] In the first embodiment, the name and image of the icon are specified on the PWA installation URL generation page; however, the icon settings can be preset on the MFP 171 side by setting checkbox 1235 and input field group 1237. 1239 represents an area displaying a preview of the icon reflecting the setting values ​​of input field group 1237. Its description and use... Figure 10The description is the same, so it will be omitted. Button 1241 is used to save the settings of checkboxes 1233, 1235, and input field group 1237 to update the manifest file. When user 153 presses button 1241 after entering settings in checkboxes 1233, 1235, and input field group 1237, manifest file update unit 371 updates the manifest file stored in manifest file storage unit 373 based on the entered settings. The content of the manifest file is substantially the same as that described in the first embodiment, so it will be omitted. Thereafter, the manifest file updated via screen 1211 is returned to content providing unit 357. In this way, user 153 with administrator privileges can pre-configure settings related to the PWA icon via the RUI of MFP 171 to change the default manifest file to be returned by content providing unit 357.

[0103] In this case, if checkbox 1235 is selected and the PWA icon is customized on the MFP 171 side, the PWA installation URL generation page described in the first embodiment (screen 1011) can also be disabled. That is, users 153 using the PWA corresponding to the RUI of the MFP 171 can be given priority to use the icon settings configured under administrator privileges.

[0104] and Figure 10 similar, Figure 13 This is a diagram showing the PWA installation URL generation page. Screen 1311 is the screen displayed when the PWA installation URL generation page has been accessed after the PWA icon settings have been configured via screen 1211.

[0105] Message 1331 is displayed on screen 1311, indicating that the administrator has configured the icon settings.

[0106] Field group 1333 is the same as fields 1031, 1033, 1035, and 1037; however, since the PWA icon settings have already been configured via screen 1211, user 153 cannot input setting values. Similar to area 1039, 1335 represents the area displaying a preview of the PWA icon. The icon displayed in area 1335 is the one with the settings already configured, i.e., the same as the icon displayed in area 1239. Button 1337 is the button that opens the same installation page (i.e., the RUI of MFP 171) as button 1041. On screen 1311, user 153 cannot set values ​​in field group 1333, but can press button 1337. When user 153 presses button 1337, the screen of the RUI of MFP 171 is opened, and an installation page similar to that shown on screen 611 is displayed on the web browser display unit 323. In this case, content providing unit 357 returns the manifest file configured under management permissions via screen 1211. By performing the controls described above, the content providing unit 357 can preferentially provide the MFP 171 with a manifest file that has been configured.

[0107] In the second embodiment, a method has been described in which PWA icon settings are configured via screen 1211, updating the manifest file stored in manifest file storage unit 373 to change the default manifest file provided by content providing unit 357. Alternatively, manifest files can be prepared for each set of PWA icon setting values, and the default manifest file to be provided can be switched as needed. In that case, instead of updating and reusing a single manifest file stored in manifest file storage unit 373, manifest file generation unit 369 generates a manifest file for each set of setting values ​​and stores the manifest file in manifest file storage unit 373. Subsequently, user 153 with administrator privileges can switch the default manifest file to be provided by content providing unit 357 by specifying the set of setting values ​​corresponding to the default manifest file that user 153 wants to provide via screen 1211.

[0108] In the second embodiment, the description focuses on updating the PWA icon settings from screen 1211. However, similar to the first embodiment, it is also possible to change items other than the icon-related settings. This can be achieved by updating the values ​​corresponding to the individual keys in the manifest file.

[0109] Other implementation methods

[0110] The embodiments of this disclosure can also be implemented by a computer in a system or apparatus that reads and executes computer-executable instructions (e.g., one or more programs) recorded on a storage medium (which may also be 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 circuitry (e.g., application-specific integrated circuits (ASICs)) for performing one or more functions in the above embodiments, and by methods executed by the computer in the system or apparatus, such as reading and executing computer-executable instructions from the storage medium to perform one or more functions in the above embodiments and / or controlling one or more circuits to perform one or more functions in the above embodiments. The computer may include one or more processors (e.g., a central processing unit (CPU), a microprocessor unit (MPU)) and may include a network of separate computers or separate processors to read and execute computer-executable instructions. The computer-executable instructions may be provided to the computer, for example, from a network or storage medium. The storage medium may include one or more of, for example, a hard disk, random access memory (RAM), read-only memory (ROM), the memory of a distributed computing system, an optical disk (such as an optical disc (CD), digital versatile optical disc (DVD), or Blu-ray disc (BD)™), a flash memory device, a memory card, etc.

[0111] While this disclosure has been described with reference to embodiments, it should be understood that this disclosure is not limited to the disclosed embodiments. The scope of the following claims should be given the broadest interpretation to cover all such modifications and equivalent structures and functions.

Claims

1. A network device equipped with a server, comprising: A providing unit is configured to use the server to provide a setup screen for setting parameters for installing a progressive web application corresponding to the network device; as well as The sending unit is configured to send a manifest file corresponding to the parameters to a terminal to install the progressive web application on the terminal.

2. The network device according to claim 1, further comprising: The update unit is configured to update the manifest file using the parameters set via the settings screen.

3. The network device according to claim 1, wherein, The parameter is information related to at least one of the name and icon image displayed on the terminal, assuming the progressive web application is installed on the terminal.

4. The network device according to claim 1, wherein, The providing unit also provides information for displaying installation commands for the progressive web application; and The sending unit sends the manifest file to the terminal according to the installation command.

5. The network device according to claim 1, wherein, The network device is an image processing device.

6. A control method for a network device equipped with a server, the method comprising: The server is used to provide a setup screen for setting parameters for installing a progressive web application corresponding to the network device. as well as A manifest file corresponding to the parameters is sent to the terminal to install the progressive web application on the terminal.

7. The control method according to claim 6 further includes: Update the manifest file using the parameters set through the settings screen.

8. The control method according to claim 6, wherein, The parameter is information related to at least one of the name and icon image displayed on the terminal, assuming the progressive web application is installed on the terminal.

9. The control method according to claim 6, further comprising: Provides information for accepting the installation command for the progressive web application; as well as The manifest file is sent to the terminal according to the installation command.

10. A non-transitory computer-readable storage medium storing a program for causing a computer to perform the method of claim 6.

11. A computer program product for causing a computer to perform a method for a network device equipped with a server, the method comprising: The server is used to provide a setup screen for setting parameters for installing a progressive web application corresponding to the network device. as well as A manifest file corresponding to the parameters is sent to the terminal to install the progressive web application on the terminal.

Images