Network device, control method, and storage medium

Abstract

If the RUIs of a plurality of image processing apparatuses are installed as PWAs in one terminal, icons of similar images and names are generated, and it is difficult to distinguish the icons of the image processing apparatuses.SOLUTION: A network device including a server includes a provision means for providing a setting screen for setting a parameter to be used for installing a progressive web application of the network device by using the server, and a transmission means for transmitting a manifest file corresponding to the parameter to a terminal in order to install the progressive web application in the terminal.SELECTED DRAWING: Figure 10

Description

[Technical Field]

[0001] The present invention relates to a technique for realizing notification from a network device such as an image processing device to a client device. [Background technology]

[0002] Conventionally, network devices such as image processing devices have been able to display their operational status on their displays, such as the occurrence of errors in the network device, counter information, information on the degree of consumption of consumables, and notifications from administrators.

[0003] Network devices also provide functions that allow client devices accessing them via the network to check the operating status of the image processing device, operate jobs, and configure various settings. This function is called a remote user interface (RUI). Network devices have an internal web server, and display the RUI by accessing the URL of the RUI using a web browser on an external device. RUIs are often used within a local area network (LAN), and are accessed by entering the private IP address assigned to the image processing device as the URL in a web browser on a terminal (PC or tablet).

[0004] Patent Document 1 discloses a technique for improving the accessibility to an RUI, in which an image processing device automatically generates a shortcut icon to eliminate the need to input an IP address to access the RUI. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] Japanese Patent Application Laid-Open No. 2009-271727 Summary of the Invention [Problem to be solved by the invention]

[0006] Here, there is a technology called Progressive Web Apps (hereinafter referred to as PWA). PWA is a technology that allows websites to be used as if they were native apps. Conventional native apps are applications that users can use by operating their information processing devices themselves, downloading the application from an app store to their information processing device, and installing it. On the other hand, PWA is a technology that allows users to access a PWA-compatible website using the web browser of their information processing device, install the PWA via the website, and use the website (web application) on their information processing device with the same operational feel as a native app.

[0007] The present invention aims to provide a mechanism for improving user operability on an information processing device on which a PWA is installed when the network device provides at least some of its built-in functions (such as an RUI) as a PWA. [Means for solving the problem]

[0008] A network device equipped with a server is characterized by having a providing means for using the server to provide a setting screen for setting parameters used in installing a progressive web app on the network device, and a transmitting means for transmitting a manifest file corresponding to the parameters to the terminal in order to install the progressive web app on the terminal. [Effects of the Invention]

[0009] According to the present invention, when a network device provides at least some of its built-in functions as a PWA, a mechanism can be provided to improve user operability on the information processing device on which the PWA is installed. [Brief explanation of the drawings]

[0010] [Figure 1] A diagram showing an example of a network system configuration [Figure 2] Hardware configuration diagram [Figure 3] Software Configuration Diagram [Figure 4] Figure showing an example of the Remote User Interface (RUI) display [Figure 5] A diagram showing the installation sequence for a Progressive Web App (PWA) [Figure 6] An example of how the RUI appears when installing a PWA [Figure 7] An example of the display when RUI is launched as a PWA [Figure 8] An example of the icon generated after installing a PWA [Figure 9] Diagram showing the installation sequence of a PWA [Figure 10] Figure showing an example of the installation URL generation page [Figure 11] An example of the icon generated after installing a PWA [Figure 12] Figure showing an example of the page for setting PWA icons from the RUI [Figure 13] An example of what will be displayed when you access the installation URL generation page after the PWA icon has been set DETAILED DESCRIPTION OF THE INVENTION

[0011] In this embodiment, a network device has a mechanism for providing a combination of two technologies: a remote user interface (RUI) and a progressive web app (PWA).

[0012] For example, a PWA supporting at least some of the functions of the network device can be downloaded and installed on an information processing device on which the web browser is executed by accessing the RUI of the network device using a web browser. Here, at least some of the functions of the RUI as a web application can be provided as functions supported by the PWA.

[0013] In addition, 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 that provides the PWA, and the icon is generated based on the name and image that directly indicates, for example, the model of the network device, the firmware type, etc.

[0014] Here, it is assumed that the primary user of the RUI is a user (administrator) with administrative privileges who manages network devices. In an office, for example, this administrator may manage multiple network devices by himself or herself. Furthermore, in an office, multiple network devices of the same model may be installed on the office network. When an administrator attempts to manage devices using a PWA under such a management system, multiple similar or identical icons for multiple PWAs corresponding to multiple different network devices are generated and displayed on the administrator's information processing device. This often makes it difficult for administrators to distinguish between network devices by their icons, leaving room for improvement in usability.

[0015] In the present embodiment, an embodiment in which the operability described above is improved for the RUI and PWA provided by the image processing apparatus as a network device will be described below with reference to the drawings.

[0016] Example 1 Fig. 1 is a diagram showing an example of the configuration of a network system. In Fig. 1, push server 131, terminal 151, and MFP (Multi Function Peripheral) 171 are connected via networks 111 to 113. Networks 111 to 113 are so-called communication networks realized by, for example, a LAN such as the Internet, a WAN, a telephone line, a dedicated digital line, an ATM or frame relay line, a cable television line, a wireless line for data broadcasting, or the like. Networks 111 to 113 may be any network as long as they are capable of transmitting and receiving data. In the present invention, network 111 is the Internet, and network 113 is a wired or wireless LAN set up on the Internet or a general home or office network.

[0017] The push server 131 is constructed using a server computer that communicates with the terminal 151 and the MFP 171. Alternatively, it can be constructed by adopting cloud computing technology or the like. The functions of the push server 131 may be realized by a single server or a single virtual server, or may be realized by multiple servers or multiple virtual servers. Alternatively, multiple virtual servers may be executed on a single server. The push server 131 is a server required to realize the push notification function, which is one function of the PWA.

[0018] Terminal 151 is an example of an information processing device used by a user such as an administrator. Specifically, terminal 151 is a device capable of executing a web browser, such as a personal computer (PC), a notebook PC, a smartphone, or a tablet. Terminal 151 is also a mobile terminal that incorporates an execution environment for various programs, such as a general-purpose operating system (OS).

[0019] The terminal 151 has functions to receive messages sent from the push server 131, display the RUI provided by the MFP 171, and receive and transmit data to and from each information processing device in response to operations from the user 153. The user 153 represents a user who uses the management system of this embodiment to manage the device setting information of the MFP 171 and monitor the status of the MFP 171.

[0020] The MFP 171 is an example of an image processing device as a network device. The illustrated MFP 171 is a multi-function peripheral device, and is an image processing device that has at least some of multiple functions such as scanning, printing, faxing, and communication functions. Other examples of network devices to which this embodiment can be applied include devices that have a web server and can provide an RUI, such as a network router, a surveillance camera, and a digital medical device.

[0021] The MFP 171 has a function of providing an RUI in response to a request from the terminal 151, and the RUI can be accessed via an application such as a web browser provided on the terminal 151. The MFP 171 also detects its own device status and events (for example, part replacement or internal device abnormality alerts) and stores them internally as device information, and can provide this various device information to the terminal 151 via the RUI. The MFP 171 has a function of transmitting the various device information described above to an external management server, and the external management server can receive and process the various information transmitted from the MFP 171, thereby managing the MFP 171. Furthermore, by using the push server 131, the MFP 171 can also send a push notification to the terminal 151 used by the user 153 in accordance with preset rules when an event occurs internally.

[0022] FIG. 2 is a diagram showing an example of the hardware configuration of information processing devices such as the push server 131, the terminal 151, and the MFP 171. As shown in FIG.

[0023] FIG. 2A shows the hardware configuration of the push server 131 and the terminal 151. The system bus 212 controls the flow of data within the device. The CPU (Central Processing Unit) 214 controls the entire device. The CPU 214 executes application programs, an OS, and the like stored in the HDD / SSD 222, and controls the temporary storage of information, files, and the like required for program execution in the RAM 218. The GPU (Graphics Processing Unit) 216 mainly performs arithmetic processing required for image and video display. The RAM 218 is a temporary storage unit and functions as the main memory, work area, and the like for the CPU 214 and GPU 216. The ROM (Read Only Memory) 220 is a storage unit and stores various data such as basic I / O programs. The HDD (Hard Disk Drive) / SSD (Solid State Drive) 222 is one of the external storage units. The HDD / SSD 222 functions as a large-capacity memory and stores application programs such as a web browser, programs for service servers, the OS, related programs, and the like. The NIC (Network Interface Card) 224 exchanges data with external devices via the NIC 224 and the networks 111 to 113. The camera 226 is an external camera that captures images of the surroundings of the terminal 151 or an internal camera that captures an image of the user. A two-dimensional code captured by the camera 226 can be analyzed by an application program stored in the HDD / SSD 222, allowing access to a website or launching a specific application. The display 228 is a display unit that displays information necessary for operating an external web server or a UI provided by the MFP 171. The display 228 may also be a device that has a function of accepting operation instructions from a user, such as a touch panel. The proximity communication I / F 230 is a network I / F for proximity communication, such as NFC or Bluetooth. Using the proximity communication I / F 230, data can be transmitted and received between information processing devices.The input / output I / F 232 is an interface for controlling input / output with external devices, and controls input / output devices such as a mouse and a keyboard connected to the input / output I / F 232, for example.

[0024] FIG. 2B shows the hardware configuration of the MFP 171, exemplifying an image processing device. The CPU 254 loads programs stored in the ROM 258 and controls the entire device via the internal bus 252. The RAM 256 functions as memory and a work area for the CPU 254. The HDD / SSD 260 is a storage device that stores various data. The NIC 262 exchanges data with external network devices one-way or two-way. The print control unit 264 is a control unit for controlling the print unit 266 and issues print (print) instructions to the print unit 266 based on various control commands in the MFP 171. The print unit 266 executes printing based on commands from the print control unit 264. The input / output device 270 represents multiple components responsible for input and output to the MFP 171. Specifically, the input / output device 270 receives input from the user (such as a button press) and transmits a signal corresponding to the input to each of the aforementioned processing units via the input / output I / F 268. In addition, a display device (such as a touch panel) for providing necessary information to the user and accepting user operations is also included in the input / output device 270. Furthermore, a scanning device for accepting electronic data by reading an original document as input, and sensors for detecting remaining amounts and replacement of parts and consumables are also included in the input / output device 270.

[0025] The configuration of the information processing device described above is an example and is not limited to the example configuration shown in Figure 2. For example, the storage destination of data and programs can be changed to the RAM, ROM, HDD / SSD, etc. shown in Figures 2(A) and 2(B) depending on their characteristics. In addition, the processing in the software configuration shown in Figure 3 is realized by the CPUs and GPUs shown in Figures 2(A) and 2(B) executing processing based on the programs stored in the HDD / SSD.

[0026] FIG. 3 illustrates the software configuration of the terminal 151 and the MFP 171, extracting functions related to this embodiment.

[0027] The terminal 151 includes an OS display unit 311 and a web browser 321. The web browser 321 includes, as internal software modules, a web browser display unit 323, a content acquisition unit 325, a data acquisition unit 327, a data transmission unit 329, and a web application processing unit 331. The web browser 321 further 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.

[0028] The OS display unit 311 is a software module for displaying functions provided by the OS as a GUI (Graphical User Interface) on the display 228. The OS display unit 311 is a function required when the user 153 operates the terminal 151 using the GUI, and for displaying a PWA icon added to the desktop, folder, home screen, etc. of the terminal 151 after installing the PWA (described later).

[0029] Next, we will explain each software module of the web browser 321. The web browser display unit 323 is a software module for displaying the RUI provided by the MFP 171 on the display 228. In this embodiment, the explanation will proceed assuming that the 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.

[0030] The content acquisition unit 325 is a software module for acquiring web content required to display the RUI on the web browser display unit 323 from the content provider 357. The web content is, for example, HTML (HyperText Markup Language), Java Script, or CSS (Cascading Style Sheets). The web content also includes components of the PWA, such as a ServiceWorker (a script that runs as a background process) and a manifest file (a file that describes the installation settings for the PWA).

[0031] The data acquisition unit 327 is a software module for communicating with the data provision unit 359 and acquiring device information such as setting values ​​within the MFP 171. The RUI is realized by combining the data acquired by the data acquisition unit 327 with the above-mentioned web content and displaying it on the web browser display unit 323. The data acquisition unit 327 can also realize an RUI whose display content changes dynamically by acquiring data from the data provision unit 359 asynchronously with operations by the user 153. The data transmission unit 329 is a software module for transmitting setting values ​​to be reflected in the MFP 171, input values ​​and files from the user 153, to the data reception unit 361, and for transmitting a user ID and password for logging in to the RUI.

[0032] The Web application processing unit 331 is a software module that analyzes various Web contents and data acquired from the MFP 171 and controls the overall behavior of Web applications running on the Web browser 321 .

[0033] The ServiceWorker processing unit 333 is a software module that registers the ServiceWorker acquired by the content acquisition unit 325 in the Web browser 321 and executes it in the background. By having the ServiceWorker operate in the background, it is possible to realize functions such as improving the RUI display speed through cache control, offline operation, background synchronization, and push notifications.

[0034] The content storage unit 335 is a storage area and storage module within the web browser 321 for storing various web contents acquired by the content acquisition unit 325. In particular, the ServiceWorker processing unit 333 stores the registration information of the ServiceWorker in the content storage unit 335, and stores the cache of various web contents in the content storage unit 335 when cache control is performed.

[0035] The device information storage unit 337 is a storage area and storage module within the web browser 321 for storing the device information of the MFP 171 acquired by the data acquisition unit 327, and is stored in a storage area such as local storage. Storing device information in the device information storage unit 337 is expected to improve the display speed of the RUI, similar to caching web content. In addition, the device information of the MFP 171 can be referenced even when offline, and setting values ​​that will be reflected in the MFP 171 can be input in advance.

[0036] The PWA installation processing unit 339 is a software module that performs processing related to the installation of a PWA. The PWA installation method and installation sequence will be described later.

[0037] The MFP 171 includes a device information generation unit 351, a device information storage unit 353, a content storage unit 355, a content providing unit 357, a data providing unit 359, a data receiving unit 361, a device information update unit 363, a login processing unit 365, and a user information storage unit 367. The MFP 171 further includes a manifest file generation unit 369, a manifest file update unit 371, and a manifest file storage unit 373, which are features of the present invention.

[0038] Device information generation unit 351 is a software module for generating device information such as the latest status and setting values ​​inside MFP 171. Device information storage unit 353 is a software module for storing device information such as the status generated by device information generation unit 351 and setting values ​​inside MFP 171 updated by device information update unit 363 (described later). Content provision unit 357 is a software module for providing various Web contents that constitute the RUI in response to a request from content acquisition unit 325.

[0039] The data providing unit 359 is a software module for providing data such as device information and setting values ​​of the MFP 171 in response to a request from the data acquiring unit 327. The data receiving unit 361 is a software module for receiving a request transmitted from the data transmitting unit 329.

[0040] The device information update unit 363 is a software module for updating the device information generated by the device information generation unit 351 and the setting value change request received by the data reception unit 361 to the latest device information, and stores the updated device information in the device information storage unit 353. The login processing unit 365 is a software module that receives a login request to the RUI from the data transmission unit 329 via the data reception unit 361, collates the request with the user's account information stored in the user information storage unit 367, and determines whether or not the login is permitted. The user information storage unit 367 is a software module for storing the account information of the user who uses the RUI.

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

[0042] [Table 1]

[0043] The user ID column is an ID that uniquely identifies a user. The password column is the basic authentication password used when logging in with the user ID. The login processing unit 365 compares the user ID and password combination included in the login request from the data transmission unit 329 with Table 1, and if they match, returns a login result of success to the data transmission unit 329. The role column indicates the user's authority level; for example, an "administrator" can use all of the RUI's functions. A "maintainer" can only use functions related to maintenance of the MFP 171, and a "viewer" can only view device information. This is an attribute used to realize access control. Whether or not login processing is required when accessing the RUI can be switched by the settings of the MFP 171. If login is not required, that is, if all users within the LAN are permitted to use the RUI, no authority control is performed.

[0044] The manifest file generation unit 369 is a software module for generating a manifest file that describes the installation settings of the PWA. The manifest file update unit 371 is a software module that executes a manifest file update process when updating the manifest file in response to an instruction from the user 153. The manifest file storage unit 373 is a software module for storing the manifest file generated or updated by the manifest file generation unit 369 or 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 the present invention, will be described later.

[0045] 4 shows an example of the display of an RUI provided by a typical MFP. Screen 411 shows one screen of the RUI displayed on web browser display unit 323.

[0046] Next, an example of a processing sequence when installing an RUI provided by the MFP 171 as a PWA into the terminal 151 and an example of a display on the web browser display unit 323 will be described with reference to FIGS.

[0047] Fig. 5 is a diagram showing a sequence in which terminal 151 accesses the RUI of MFP 171 in response to an instruction from user 153 and installs a PWA. Fig. 6 is a diagram showing an example of a display on web browser display unit 323 when a PWA is installed. Fig. 7 is a diagram showing an example of a display on web browser display unit 323 when an RUI is displayed as a PWA. Fig. 8 is a diagram showing an example of an icon displayed on OS display unit 311 after a PWA has been installed.

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

[0049] In S513, the content acquisition unit 325 requests web content for displaying the RUI on the web browser display unit 323 from the content provision unit 357. In S515, the content provision 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 processes the web browser display unit 323 to display the RUI.

[0050] In S519, the ServiceWorker processing unit 333 analyzes the ServiceWorker script included in the Web content acquired in S515, and registers the ServiceWorker in the content storage unit 335. At this time, if a command related to cache control is described in the ServiceWorker script, the ServiceWorker processing unit 333 stores the Web content acquired in S515 in the content storage unit 335 as a cache in accordance with the described command.

[0051] In S521, PWA installation processing unit 339 executes pre-installation processing and checks whether the Web content acquired in S515 includes a manifest file. If it is determined that a manifest file is included, PWA installation processing unit 339 performs processing to display various objects such as those shown in Fig. 6 on Web browser display unit 323. Note that, although it is assumed here that the manifest file is transmitted from MFP 171 to terminal 151 as part of the Web content, the manifest file may also be transmitted from MFP 171 to terminal 151 separately from the Web content.

[0052] Screen 611 in Figure 6 shows an example of the display on the web browser display unit 323 at the time the processing of S521 is executed. Button 631 is a button that is displayed when the web app being viewed can be installed as a PWA. 633 is a notification object that is displayed when button 631 is pressed by the user 153. Button 635 is a button that the user 153 presses when installing the PWA. Button 637 is a button that the user 153 presses when not installing the PWA. Here, we will explain the case where the user 153 presses button 635 to start installing the PWA (executing S523).

[0053] In S523, the PWA installation processing unit 339 accepts a PWA installation instruction based on the user 153 pressing button 635, and proceeds to the processing of S525. In S525, the PWA installation processing unit 339 executes the PWA installation processing. Here, we will explain the manifest file used when the PWA installation processing unit 339 executes the PWA installation processing.

[0054] An example of a manifest file (JSON format) is shown below. { “name”:“Product-AAA”, “short_name”:“proAAA”, “start_url”:“ / ”, “lang”:“ja-jp”, “display”:“standalone”, “background_color”:“#fff”, “theme_color”:“#e88c31”, “description”:“Remote User Interface (Product-AAA)”, “scope”:“ / ”, “orientation”:“any”, "icons":[ { “src”:“ / default512.png”, “sizes”:“512x512”, “type”:“image / png” } ] }

[0055] There are other keys that can be specified in addition to the keys shown in the above example. Here, the "name", "short_name", and "icons" keys that are related to the features of this embodiment will be explained.

[0056] The value of the "name" key specifies the name (application name) that is assigned to the icon generated when the PWA is installed by the PWA installation processing unit 339.

[0057] Like "name," "short_name" is a key for specifying the name of an icon generated when the PWA is installed by the PWA installation processing unit 339. However, the PWA installation processing unit 339 determines whether to use the value of "name" or "short_name" depending on the type of terminal 151. For example, if the terminal 151 is a terminal with a relatively large display 228 such as a PC, the value of the "name" key is used, and if the terminal 151 is a terminal with a small display 228 such as a smartphone, the value of the "short_name" key is used. In other words, the normal application name is generally specified in the "name" key, and a shortened application name is specified in "short_name."

[0058] The value of the "icons" key specifies the name of the image file to be used as the icon image generated when the PWA is installed by the PWA installation processing unit 339. The "src" key within the "icons" key specifies the URL where the image file to be used as the icon image is located, and in the above example, a relative path is used. The "sizes" key specifies the dimensions of the image. The "type" key specifies the MIME (Multipurpose Internet Mail Extensions) type (media type) of the image. The value for the "icons" key is an array, and multiple values ​​can be specified, so the PWA installation processing unit 339 will use an image of the appropriate size depending on the type of terminal 151, just like "name" and "short_name".

[0059] In this embodiment, the example manifest file described above is a manifest file set by default in the MFP 171, and it is assumed that if the model and firmware version of the MFP 171 are the same, a similar manifest file will be generated. When the PWA installation processing unit 339 performs the PWA installation process in S525, a profile for executing various web content that constitutes the RUI of the MFP 171 is installed in the web browser 321. At the same time, an icon for launching the PWA is generated on the OS display unit 311 (desktop, home screen, etc.) according to the contents of the manifest file. In this way, by the PWA installation processing unit 339 performing the PWA installation process, the user 153 can use the RUI of the MFP 171 as a PWA app.

[0060] Since the PWA runs as a process of the web browser 321, the PWA icon generated during installation is assumed to be an executable file for launching the web browser 321 and a shortcut icon with launch options specified. However, since the means for realizing the PWA-related functions depends on the implementation of the web browser, it is not necessarily limited to this implementation means. The user 153 can launch the PWA of the RUI of the MFP 171 by pressing the icon generated by the PWA installation processing unit 339.

[0061] 7 is an example of the display of an application (RUI app) screen that is provided when the user 153 launches an installed PWA. The web content displayed on screen 711 is the same as that displayed on screen 411, but unlike a normal web browser display, for example, there is no address bar, allowing the user to experience operating a native app.

[0062] Moving on to FIG. 8 , screen 811 is an example of the screen display on the OS display unit 311 after the PWA installation processing unit 339 has installed a PWA. Screen 811 displays an icon for a file deployed to a specific path in the file system. Icon 831 is an icon for launching the PWA of the RUI of the MFP 171. The group of icons displayed on screen 811 is an example of icons generated when the RUIs of multiple MFPs 171 are installed as PWAs on a single terminal 151. In this case, a manifest file is not configured to distinguish between the MFPs 171, so the PWA installation processing unit 339 generates icons with similar images and names. Therefore, it is difficult for the user 153 to tell which icon corresponds to which PWA of which MFP 171's RUI. To solve this problem, a PWA installation method according to the present invention will be described using FIGS. 9 , 10 , and 11 .

[0063] Fig. 9 is a diagram showing the sequence up to installation in this embodiment. Fig. 10 is a setting screen (hereinafter referred to as a PWA installation URL generation page) provided by MFP 171 for configuring settings related to the PWA icon before installing the PWA on the terminal. Fig. 11 is a diagram showing a display example of the icon generated by PWA installation processing unit 339 after the PWA is installed.

[0064] In S911, the web browser 321 of the terminal 151 receives an instruction from the user 153 to access the PWA installation URL generation page of the MFP 171. Specifically, the user 153 enters the URL of the PWA installation URL generation page in the address bar of the web browser 321 to access a web page provided by the MFP 171 that is separate from the normal RUI shown in Fig. 4. A display example of the PWA installation URL generation page and its behavior as a web page will be described later.

[0065] In S913, the content acquisition unit 325 requests the content providing unit 357 to provide web content for displaying a 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.

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

[0067] The PWA installation URL generation page will now be described with reference to Fig. 10. Screen 1011 is a screen in which the PWA installation URL generation page is displayed on the web browser display unit 323. In this embodiment, a manifest file is dynamically generated according to the values ​​entered on this PWA installation URL generation page and returned to the content acquisition unit 325, thereby controlling the icon that the PWA installation processing unit 339 generates when the PWA is installed.

[0068] Input field 1031 is a field for specifying the name of the icon, and a value to be set in the “name” key of the manifest file is input therein. Input field 1033 is a field for specifying the abbreviated name of the icon, and a value to be set in the “short_name” key of the manifest file is input therein. Note that setting values ​​such as the device name and installation location that can be set in the RUI of MFP 171 may be input as default values ​​in input fields 1031 and 1033. Pull-down 1035 is a pull-down for selecting an image to be used for the icon, and the selected image is set in the “icons” key of the manifest file. Images that can be selected in pull-down 1035 are images that are pre-stored in the content storage unit 355 of MFP 171. Button 1037 is a button for selecting an image to be used for the icon, similar to pull-down 1035, but pressing button 1037 allows the user 153 to select an image that they have prepared (an image stored in terminal 151). An area 1039 is used to display a preview of an icon generated by the PWA installation processing unit 339 based on the setting values ​​input in 1031, 1033, 1035, or 1037.

[0069] In S919, the Web application processing unit 331 accepts input of setting values ​​by the user 153 in 1031, 1033, 1035, or 1037. In S921, the Web application processing unit 331 displays a preview of an icon in area 1039 based on the input setting values. Button 1041 is a button for transitioning to the installation page, that is, the RUI of the MFP 171 as shown in FIG. 6.

[0070] In S923, the Web application processing unit 331 accepts an instruction in response to the user 153 pressing the button 1041. Thereafter, S925, S927, and S929 are processes that are executed if the user 153 has selected a unique image from the button 1037.

[0071] In S925, the data transmission unit 329 uploads the image selected by the user 153 by transmitting it to the data reception unit 361. In S927, the data reception unit 361 stores the image received in S925 in the content storage unit 355. In S929, the data reception unit 361 returns a response to the data transmission unit 329 indicating that the image upload has been successfully completed. In S931, the Web application processing unit 331 generates a URL with parameters. Here, a URL with parameters is, for example, the following URL, which is a URL in which parameters corresponding to the "name", "short_name", and "icons" keys of the manifest file are embedded in addition to the URL string of the RUI:

[0072] Example of a URL with parameters: GET https: / / 192.168.10.5 / portal_top?name=Product-AAA_%E3%83%93%E3%83%ABA1F%E5%8D%97%E8%A5%BF_AAAAA01&short_name=AAAAAA01&icons=%2Fmfp_icon.png

[0073] In the above URL example, the "sizes" and "type" in the "icons" key are omitted because they can be automatically determined by the MFP 171.

[0074] In S933, the content acquisition unit 325 uses the parameter-attached URL generated in S931 to send a request to acquire the Web content that constitutes the RUI to the content providing unit 357. In S935, upon receiving the request to acquire the Web content, the content providing unit 357 instructs the manifest file generating unit 369 to generate a manifest file according to the parameters of the parameter-attached URL. The manifest file generating unit 369 then maps values ​​to corresponding keys in the manifest file based on the parameters of the parameter-attached URL, and generates the manifest file.

[0075] An example of a manifest file generated by the manifest file generation unit 369 is shown below. { “name”:“Product-AAA_Building A1F Southwest_AAAAA01”, “short_name”:“AAAAA01”, “start_url”:“ / ”, “lang”:“ja-jp”, “display”:“standalone”, “background_color”:“#fff”, “theme_color”:“#e88c31”, “description”:“Remote User Interface (Product-AAA)”, “scope”:“ / ”, “orientation”:“any”, "icons":[ { “src”:“ / mfp_icon.png”, “sizes”:“512x512”, “type”:“image / png” } ] }

[0076] In S937, the content providing unit 357 returns the same Web content as in S515 to the content acquiring unit 325, but returns the manifest file generated in S935. When the processing of S937 is completed, the process proceeds to S939, but the processing executed in S939, S941, S943, S945, and S947 is the same as S517, S519, S521, S523, and S525, so description thereof will be omitted.

[0077] 9 and 10. Screen 1111 is a screen displayed on the OS display unit 311, similar to screen 811. Icon 1131 is an icon generated by the PWA installation processing unit 339 in S947. Icon 1131 and the group of icons in the display area of ​​screen 1111 are not similar images and names like icon 831, but rather are icons with images and names specified by the user 153 himself on the PWA installation URL generation page.

[0078] In this way, by dynamically generating a manifest file using a URL with parameters, the user 153 can control the icons generated during installation, making it easier to determine which MFP 171's RUI each icon represents. In this embodiment, a method for setting a PWA icon via a PWA installation URL generation page has been described. However, the same effect can be achieved without using this PWA installation URL generation page. For example, the user 153 can perform the same process by preparing a parameterized URL in a text editor or the like and directly entering the parameterized URL into the address bar of the web browser display unit 323. Therefore, the means for transmitting parameters is not limited as long as the terminal 151 can send parameters to the MFP 171 by some means and dynamically generate a manifest file for installing a PWA according to those parameters. Furthermore, in addition to the “name,” “short_name,” and “icons” keys primarily described in this embodiment, the manifest file for installing a PWA contains other keys that can be set as options. These keys can also be set via URL parameters.

[0079] Example 2 In the first embodiment, a method for generating a PWA icon with a name and image specified by the user 153 using an installation URL generation page or a URL with parameters was described. However, instead of each user 153 specifying the name and image of the PWA icon each time, a user 153 with administrator privileges can also set the PWA icon in advance using the RUI of the MFP 171, etc. In the second embodiment, a method for a user 153 with administrator privileges to set the PWA icon in the MFP 171 in advance will be described.

[0080] First, Fig. 12 is a diagram showing a display example of an RUI provided by the MFP 171 in the second embodiment. Screen 1211 shows the RUI screen displayed on the web browser display unit 323, and displays a setting screen related to PWA. Screen 1211 is also a screen that is displayed when a user 153 with administrator privileges logs in to the RUI. For example, a user with the "administrator" role shown in Table 1 corresponds to a user with administrator privileges. Button 1231 is the same as button 631 and is a button for installing a PWA. Checkbox 1233 is a checkbox for selecting whether or not to allow user 153 to use the RUI of the MFP 171 as a PWA.

[0081] In the first embodiment, the explanation is given on the assumption that the RUI of the MFP 171 is used as a PWA, but it is also possible to control the user 153 so that the RUI is not used as a PWA by using a setting such as checkbox 1233. If checkbox 1233 is unchecked, that is, if the setting is made so that the RUI is not permitted to be used as a PWA, the content providing unit 357 does not return a manifest file to the content acquiring unit 325. Checkbox 1235 is a checkbox for selecting whether or not to customize the icon generated by PWA installation processing unit 339 on the MFP 171 side when the PWA is installed.

[0082] In the first embodiment, the icon name and image are specified on the PWA installation URL generation page. However, by setting the check box 1235 and the input field group 1237, the icon can be set in advance on the MFP 171 side. Reference numeral 1239 denotes an area for previewing an icon reflecting the setting values ​​of the input field group 1237. This area is similar to that described in FIG. 10 , and therefore a description thereof will be omitted. A button 1241 is a button for saving the setting values ​​of the check box 1233, the check box 1235, and the input field group 1237 and updating the manifest file. When the user 153 presses the button 1241 after setting input values ​​in the fields 1233, 1235, and 1237, the manifest file update unit 371 updates the manifest file stored in the manifest file storage unit 373 based on the input setting values. The contents of the manifest file are similar to those described in the first embodiment, and therefore a description thereof will be omitted. The updated manifest file on the screen 1211 is then returned by the content providing unit 357. In this way, the user 153 with administrator privileges can configure the PWA icon in advance via the RUI of the MFP 171, and change the manifest file that the content provider 357 returns by default.

[0083] Here, if check box 1235 is enabled and the PWA icon is customized on the MFP 171 side, it is also possible to disable the installation URL generation page (screen 1011) described in the first embodiment. In other words, it is possible to give priority to the icon settings set with administrator privileges to user 153 who uses the PWA of the RUI of the MFP 171.

[0084] Fig. 13 is a diagram showing a PWA installation URL generation page, similar to Fig. 10. Screen 1311 is the screen that appears when the PWA installation URL generation page is accessed after the PWA icon has been set on screen 1211.

[0085] A message 1331 is displayed on the screen 1311 to inform the user that the icon has already been set by the administrator.

[0086] The input field group 1333 is the same as 1031, 1033, 1035, and 1037, but the user 153 cannot set an input value because the PWA icon has already been set on the screen 1211. Like 1039, 1335 is an area for previewing the PWA icon, and the icon displayed in 1335 is the set icon, i.e., the same icon as the icon displayed on 1239. The button 1337 is a button for transitioning to the same installation page as the button 1041, that is, the RUI of the MFP 171. On the screen 1311, the user 153 cannot set values ​​in the input field group 1333, but can press the button 1337. When the user 153 presses the button 1337, the screen transitions to the RUI screen of the MFP 171, and the installation page shown on the screen 611 is displayed on the web browser display unit 323. At this time, the content providing unit 357 returns the manifest file set on the screen 1211 with administrator privileges. By performing the above control, content providing unit 357 can provide MFP 171 with a set manifest file preferentially.

[0087] In the second embodiment, a method has been described in which the manifest file stored in the manifest file storage unit 373 is updated and the manifest file provided by the content providing unit 357 as a default is changed by configuring a PWA icon on the screen 1211. Alternatively, it is also possible to prepare a manifest file for each set of setting values ​​for a PWA icon and switch the manifest file provided as a default as needed. In this case, instead of updating and reusing a single manifest file stored in the manifest file storage unit 373, the manifest file generation unit 369 generates a manifest file for each set of setting values ​​and stores the manifest file in the manifest file storage unit 373. Thereafter, the user 153 with administrator privileges can specify a setting value set on the screen 1211 that corresponds to the manifest file the user wants to provide as a default, thereby switching the manifest file provided by the content providing unit 357 as a default.

[0088] In addition, in the second embodiment, the explanation focused on updating the PWA icon settings from screen 1211, but as in the first embodiment, it is also possible to change items other than the icon setting values, which can be achieved by updating the values ​​corresponding to each key in the manifest file.

[0089] (Other Examples) The present invention also includes an apparatus or system configured by appropriately combining the above-described embodiments, and a method thereof.

[0090] Here, the present invention is a device or system that executes one or more pieces of software (programs) that realize the functions of the above-described embodiments. Also, a method for implementing the above-described embodiments executed by the device or system is also one aspect of the present invention. The program is supplied to the system or device via a network or various storage media, and is read into one or more memories and executed by one or more computers (CPUs, MPUs, etc.) of the system or device. In other words, the present invention also includes the program itself, or various storage media that store the program and are readable by a computer. The present invention can also be realized by a circuit (e.g., ASIC) that realizes the functions of the above-described embodiments. [Explanation of symbols]

[0091] 131 Push Server 151 devices 171 MFP

Claims

1. A network device comprising a server, a provision means for providing, by using the server, a setting screen for setting parameters used in installing the progressive web app on the network device; a transmitting means for transmitting a manifest file corresponding to the parameters to the terminal in order to install the progressive web app on the terminal.

2. 2. The network device according to claim 1, further comprising an update unit that updates a manifest file based on parameters set on the setting screen.

3. 2. The network device according to claim 1, wherein the parameter is information regarding at least one of a name and an icon image to be displayed on the terminal when the progressive web app is installed on the terminal.

4. The providing means further provides information for displaying to receive an instruction to install the progressive web app; 2. The network device according to claim 1, wherein the transmission means transmits the manifest file to the terminal in accordance with the installation instruction.

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

6. A control method for a network device including a server, comprising: a provision step of providing, using the server, a setting screen for setting parameters used in installing the progressive web app on the network device; a transmitting step of transmitting a manifest file corresponding to the parameters to the terminal in order to install the progressive web app on the terminal.

7. A computer as a network device with a server, a provision means for providing, by using the server, a setting screen for setting parameters used in installing the progressive web app on the network device; a program for causing the program to function as a transmitting means for transmitting a manifest file corresponding to the parameters to the terminal in order to install the progressive web app on the terminal;

Images