Network device, method for controlling network device, and program

Abstract

Enable network devices to provide PWAs according to user permissions. [Solution] An image forming apparatus 102 having a web server 411 that can be used by multiple users with different levels of authority, wherein the web server 411 provides a means for providing a website for installing software as a progressive web application to a user terminal to provide at least some of the functions of the image forming apparatus 102, and the means for providing the website is characterized in that it provides a progressive web application with different functions available depending on the authority of the user who has logged into the website.

Description

Technical Field

[0003]

[0001] The present invention relates to a network device, a control method for a network device, and a program.

Background Art

[0002] An image forming apparatus provides a function of a remote user interface (RUI) that allows a client terminal accessing the image forming apparatus via a network to check the operating status of the image forming apparatus, operate jobs, perform various settings, and the like. The image forming apparatus includes a web server inside, and by accessing the URL of the RUI from a client terminal using a web browser or the like, it is possible to refer to information in the image forming apparatus and change the settings of the image forming apparatus. Here, there is a technology called Progressive Web App (PWA). PWA is a technology that allows a website to be used as if it were a native app. Unlike conventional native apps, there is no need for the user to download and install the app from the app store himself / herself. For a website that supports PWA, it can be easily installed and used via a web browser. After installing the PWA, an icon is generated on the terminal's desktop, home screen, etc., just like a native app. By combining the technologies of RUI and PWA, the RUI of the image forming apparatus can be provided as a PWA.

[0003] Among the information and settings of the image forming apparatus, there is information that only the administrator of the image forming apparatus can know and settings that only the administrator of the image forming apparatus can change. Patent Document 1 discloses an image forming apparatus that specifies the user's authority and changes the display content of a screen for instructing to install an application in the image forming apparatus according to the user's authority.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

[0005] General users who simply use the functions of an image forming apparatus should not be able to access information known only to the administrator of the image forming apparatus, nor should they be able to change settings that only the administrator can access, using the RUI (Rules of Use Interface) of the image forming apparatus provided as a PWA (Progressive Web App). Therefore, it is necessary to provide the PWA after determining the functions to be provided by the PWA, which is a network device, according to the user's authority.

[0006] The present invention aims to enable network devices to provide PWAs according to the user's permissions. [Means for solving the problem]

[0007] To solve the above problems, the present invention provides a network device that can be used by multiple users with different levels of authority, has a web server, and has a provisioning means that provides a website for installing software as a progressive web application to a user terminal to provide at least some of the functions of the network device, and the provisioning means provides the website so that it can provide a progressive web application with different functions available depending on the authority of the user who has logged into the website. [Effects of the Invention]

[0008] According to the present invention, network devices can be enabled to provide PWAs according to the user's permissions. [Brief explanation of the drawing]

[0009] [Figure 1] This is a diagram showing the configuration of the management system. [Figure 2] This figure shows the hardware configuration of the image forming apparatus 102, which is a network device. [Figure 3] This diagram shows the hardware configuration of the user terminal 103, which is a client device. [Figure 4] This figure shows the software configuration of the image forming apparatus 102, which is a network device. [Figure 5] This diagram shows the software configuration of the user terminal 103, which is a client device. [Figure 6] This sequence describes the PWA installation process performed within the management system. [Figure 7] This figure shows an example of a login screen for a RUI that appears in a browser 505 error. [Figure 8] This figure shows an example of a PWA screen for a regular user with different privileges than administrator privileges. [Figure 9] This figure shows an example of a PWA screen for an administrator user with administrator privileges. [Figure 10] This figure shows an example of a typical RUI provided by the image forming apparatus 102. [Figure 11] This is a flowchart showing the login process performed by a PWA. [Figure 12] This figure shows an example of a login screen displayed during the PPWA login process. [Modes for carrying out the invention]

[0010] Figure 1 shows the overall configuration of the management system. The management system is a system for managing network devices. The management system has network devices to be managed and client devices that can communicate with the network devices. In this embodiment, the management system 100 has an image forming apparatus 102 which is a network device and user terminals 103 (user terminals 103a and 103b) which are client devices. The management system may also have a server that provides various services related to the network devices, and the management system 100 in this embodiment has a push server 104.

[0011] The image forming apparatus 102, the user terminal 103, and the push server 104 are connected to each other via a network 101 so that they can communicate with one another. The network 101 is a so-called communication network, which can be implemented using, for example, a LAN, WAN, telephone line, dedicated digital line, ATM or frame relay line, cable television line, or wireless line for data broadcasting. The push server 104 may be built on the intranet environment used by the image forming apparatus 102 and the user terminal 103, or it may be interconnected with the intranet environment via the Internet.

[0012] The image forming apparatus 102 is an example of a network device with a web server that can be used by multiple users with different levels of privileges. The network device provides functions that allow client devices that access it via the network to check the operating status of the network device, perform job operations, and configure various settings. This function provides at least some of the functions of the network device and is called a remote user interface (hereinafter referred to as RUI or remote UI). In other words, the image forming apparatus 102 provides the RUI to the user terminal 103. The user terminal 103 can access the RUI URL using a web browser or the like. The screens, functions, and settings provided by the image forming apparatus 102 via the RUI vary depending on the user's privileges. User privileges for the image forming apparatus 102 include administrator privileges and privileges other than administrator privileges (privileges without administrator privileges).

[0013] The mechanism for providing information about network devices via the network by the management system is implemented using a RUI (Rules-Based User Interface) on a website, as well as a Progressive Web App (PWA). In other words, the RUI provided by the image forming apparatus 102 can be implemented using a PWA. A PWA is a technology that allows a web application on a website to be used as if it were an application running on a client device. A PWA is application software that can be downloaded and installed via a web browser, and is built using common web technologies such as HTML, CSS, JavaScript, and WebAssembly.

[0014] A PWA does not need to be downloaded by a user from an application store deployed by, for example, a vendor that provides an operating system (OS) and installed on a client device. For example, a user can access a website compatible with the PWA on the web browser of the client device and use the PWA by downloading it. The content of the PWA can also be freely designed by the provider of the website.

[0015] The network device includes a RUI and a web server that provides a website that can provide a PWA having a RUI function. The web server creates software as a PWA for providing at least some functions of the network device, and provides a website for installing the created PWA on the user terminal 103 via the network. The image forming apparatus 102, which is a network device, is, for example, a multifunction printer (MFP) in which a plurality of functions such as a printing function, a reading function, and a FAX function are integrated. Note that the network device may be a device such as a printer, a scanner device, a 3D printer, an information processing device such as a PC, an image processing device such as a camera, a digital medical device, or a smart home appliance, which includes a web server and can provide a RUI and a PWA.

[0016] The user terminal 103 is an example of a client device. The user terminal 103 is, for example, a client device such as a personal computer (PC) used by a user for business or the like. The client device may be a smartphone or a tablet terminal in addition to a PC. In the present embodiment, the user terminal 103a is a terminal used by a user (hereinafter referred to as an administrator user) having the authority of the administrator of the image forming apparatus 102. On the other hand, the user terminal 103b is a terminal used by a user who does not have the authority of the administrator of the image forming apparatus 102, that is, a user having a different authority from the administrator's authority (hereinafter referred to as a general user).

[0017] The push server 104 provides a push service. The push server 104 is prepared for web browsers and OS vendors to provide push services. In a PWA, by leveraging the functions of Service Workers, it is also possible to realize push notifications from a web server built by the provider of a website, etc., to a client device, as well as the display of icons on the home screen. The push notification is realized via the push server 104, and in this case, a predetermined API supported by the OS or web browser of the client device is used. The push server 104 mediates the communication between the image forming apparatus 102 and the user terminal 103 in order to realize push notifications from the web server of the image forming apparatus 102 to the client device using a PWA. The push server 104 is constructed, for example, using a server computer that communicates with the image forming apparatus 102 and the user terminal 103. Alternatively, the push server 104 can also be constructed by adopting cloud computing technology or the like.

[0018] FIG. 2 is a diagram showing the hardware configuration of the image forming apparatus 102 which is a network device. The image forming apparatus 102 includes a CPU 201, a ROM 202, a RAM 203, a storage device 204, a network I / F 205, a device control unit 207, an input / output I / F 209, and a web server 211. These units are connected via an internal bus 206. Further, the image forming apparatus 102 includes an input / output device 210 connected to the input / output I / F 209, and a printing unit 208 connected to the device control unit 207.

[0019] The CPU (Central Processing Unit) 201 controls the image forming apparatus 102. The CPU 201 loads programs stored in memory (ROM 202 or storage device 204) into RAM 203 as needed and executes them, comprehensively controlling each unit connected to the internal bus 206. The ROM (Read Only Memory) 202 stores various programs, such as the basic control program for the image forming apparatus 102. The RAM 203 (Random Access Memory) functions as the memory and work area for the CPU 201. For example, the RAM 203 stores device information of the user terminal 103, user information, event information generated in the image forming apparatus 102, various counter information, wear status information of consumable parts, and various logs.

[0020] The storage device 204 stores management information necessary for managing the image forming apparatus 102. Specifically, it stores device configuration information such as firmware information and the identification number of the image forming apparatus 102, various counter information, wear status information of consumable parts, the operation history of the image forming apparatus 102, and history information (log data) representing various abnormal states. The storage device 204 also stores image data, device information of the user terminal 103 that communicates with the image forming apparatus 102, user information, and application programs. Furthermore, in addition to the RUI, the storage device 204 stores the web server program necessary to provide PWA, data such as HTML and scripts, and related setting information. The CPU 201 performs program execution processing together with the ROM 202 and RAM 203, and also performs processing to record image data on recording media such as the storage device 204.

[0021] The network interface 205 exchanges data with external network devices or personal computers (PCs) via the network 101, either unidirectionally or bidirectionally. The input / output device 210 accepts user input and operations as an input unit. The input / output device 210 may have hardware keys such as a button board. The input / output device 210 also has a display as an output unit, which displays various information to the user. The input / output device 210 may be configured as a touch panel. By associating input coordinates with display coordinates on the touch panel, a GUI can be configured that makes it appear as if the user can directly operate the screen displayed on the touch panel. The input / output interface 209 is an interface with the input / output device 210 and transmits user input and operations to various processing units such as the CPU 201. The input / output interface 209 also outputs image data to be displayed on the display of the input / output device 210.

[0022] The device control unit 207 controls the printing unit 208 according to print requests and other instructions. The printing unit 208 is an image output device that forms an image according to a received print job and outputs it to paper, or outputs an image optically read by a scanner to paper. In addition to the printing unit 208 that provides printing functionality, the image forming apparatus 102 may also have devices that provide functions such as a scanner.

[0023] Figure 3 shows the hardware configuration of the user terminal 103, which is a client device. The user terminal 103 has a CPU 301, ROM 302, RAM 303, storage device 304, network interface 305, and input / output interface 307. Each of these units is connected via an internal bus 306. Furthermore, the user terminal 103 has an input / output device 308 connected to the input / output interface 307.

[0024] The CPU 301 controls the user terminal 103. The CPU 201 loads programs stored in memory (ROM 302 or storage device 304) into RAM 203 as needed and executes them, and comprehensively controls each unit connected to the internal bus 306. ROM 302 stores various programs, such as the basic control program for the user terminal 103. RAM 303 functions as memory and a work area for the CPU 201. Storage device 304 stores various data, such as application programs and image data.

[0025] The input / output device 308 is an operating unit consisting of a keyboard, mouse, liquid crystal display, touch panel, etc., and is connected to the CPU 301 via the input / output interface 307. The user terminal 103 communicates with external network devices such as the image forming apparatus 102 via the network interface 305. The network interface 305 communicates with external network devices via the network 101.

[0026] Figure 4 shows the software configuration of the image forming apparatus 102, which is a network device. The image forming apparatus 102 includes a transmission unit 401, a storage unit 402, an image forming unit 403, a state management unit 404, an operation unit 405, a display unit 406, an event management unit 407, a web server 411, a notification transmission unit 408, a login processing unit 409, and a PWA generation unit 410. These software modules are interconnected by a device interface 400.

[0027] The transmission unit 401 transmits data processed by the image forming apparatus 102 to an external source via the network. For example, the transmission unit 401 first acquires device information of the image forming apparatus 102, event information generated by the image forming apparatus 102, various counter information, and wear status information of consumable parts from the storage device 304. Then, in order to notify the user's terminal 103 of the acquired information via push notification, the transmission unit 401 edits the acquired information into a format for transmission to the push server 104 and sends it to the push server 104. The transmission unit 401 also receives data from external sources via the network. For example, the transmission unit 401 also receives print data from the user terminal 103. Protocols such as SMTP, HTTP / HTTPS, SMNP, FTP, and SMB are used for sending and receiving data. The device information includes identification information (serial number), network information (e.g., IP address), and operational information of the image forming apparatus 102, and any of this information is used for notifications as needed.

[0028] The memory unit 402 performs memory control, such as saving and reading information from the ROM 202, RAM 203, and storage device 204. The memory unit 402 also stores management information necessary for managing the image forming apparatus 102. For example, the memory unit 402 stores firmware information, device information such as the identification number of the image forming apparatus 102, network setting information, various counter information, wear status information of consumable parts, the operation history of the image forming apparatus 102, and history information (log data) indicating abnormal conditions. In addition, the memory unit 402 stores information related to the user terminal 103, user information, and information related to the push server 104. User information includes information on user permissions.

[0029] The image forming unit 403 has the function of generating and outputting print data to be passed to the printing unit 208. The status management unit 404 controls the printing of the image forming apparatus 102 and manages abnormal conditions, as well as managing counter information and notification information. Counter information includes, for example, the number of printed pages printed by the image forming apparatus 102 counted by sensors, and consumable information indicating the degree of wear of parts or the remaining amount of consumables such as toner bottles, which is stored and managed in the storage unit 402.

[0030] The operation unit 405 is an interface that enables the user to issue operation instructions to the image forming apparatus 102, including print instructions. The display unit 406 controls the display of UI screens to the user, showing status information of the image forming apparatus 102, information on the consumption rate of various consumables (including toner level information), setting information, and function buttons.

[0031] The event management unit 407 receives events occurring in the image forming apparatus 102 and manages event information. The event information managed by the event management unit 407 includes events such as print jobs issued by users of the image forming apparatus 102, errors (failures), and general status information of the image forming apparatus 102. For example, errors in the image forming apparatus 102 include high-priority errors such as hard disk errors, and warning-level errors such as paper jams or toner low. Similarly, event information indicating toner bottle replacement and firmware updates are also notified to the event management unit 407 via the device interface 400. The event management unit 407 also detects the occurrence of an event and processes the issuance of a push notification request to the notification transmission unit 408.

[0032] The web server 211 functions as a means of providing a website to the image forming apparatus 102. As a web server, the web server 211 provides the RUI of the image forming apparatus 102 and a website for providing a PWA having RUI functionality. The web server 411 also performs processing related to the Progressive Web Application (PWA) that provides RUI functionality via the website. The web server 211 includes a notification transmission unit 408, a login processing unit 409, and a PWA generation unit 410.

[0033] The notification transmission unit 408 is implemented as a function of the application server installed in the image forming apparatus 102. Upon receiving a request from the event management unit 407, the notification transmission unit 408 issues data for push notifications to pre-registered user terminals 103 that are targets for notifications. When the notification transmission unit 408 receives a push notification request from the event management unit 407, it edits the data related to the notification content into a predetermined format for sending a request to the push server 104, and then sends it to the push server 104. The notification content includes, for example, device information of the image forming apparatus 102 stored in the storage device 304, event information generated in the image forming apparatus 102, various counter information, and wear status information of consumable parts.

[0034] The login processing unit 409 performs user authentication. For example, the login processing unit 409 performs authentication processing when a user logs into the RUI using the user terminal 103 to obtain information about the image forming apparatus 102 or to change settings. The login processing unit 409 also performs user authentication in response to a user authentication request from the PWA installed on the user terminal 103 and responds to the PWA with the authentication result. The authentication processing is performed, for example, based on user authentication information received from the user and user information stored in the storage unit 402. User authentication information can be, for example, a combination of username and password entered by the user, information stored on an IC card, biometric information, etc., and the method of authentication processing is not limited. The PWA generation unit 410 has the function of generating a PWA that provides RUI functions according to the user information when the user terminal 103 accesses the RUI.

[0035] Figure 5 shows the software configuration of the user terminal 103, which is a client device. The user terminal 103 has a transmitter 501, a storage unit 502, an operation unit 503, a display unit 504, a browser 505, a web page 506, and a Service Worker 507. These are interconnected via an internal path 508. Note that Figure 5 shows the software configuration before the PWA is installed; after the PWA is installed on terminal 103, the PWA is added here.

[0036] The transmission unit 501 transmits data processed by the user terminal 103 to an external device via the network. For example, the transmission unit 501 transmits user authentication information such as user ID and password entered by the user via the operation unit 503 to the image forming apparatus 102. The storage unit 502 performs storage control, such as saving and reading information to and from the RAM 302, ROM 303, and storage device 304 of the user terminal 103. The operation unit 503 is an interface that enables the user to give operation instructions to the user terminal 103. The display unit 504 performs control of the display on the screen, such as converting and transmitting screen data for display on the input / output device 308 of the user terminal 103.

[0037] The user terminal 103 displays a website (web page) provided by the image forming apparatus 102 via the browser 505. In this embodiment, the website provided by the image forming apparatus 102 is a RUI provided by the image forming apparatus 102. The user terminal 103 also downloads a PWA for device management, which has one or more functions provided by the image forming apparatus 102 using its main screen or RUI, via the RUI displayed on the browser 505. The browser 505 has the functions of a web page 506, which is a website, and the functions of a Service Worker 507.

[0038] Web page 506 is a RUI provided by the image forming apparatus 102. Service Worker 507 is a program (JavaScript) that defines the behavior of PWA functions such as background operation, cache control, push notifications, and icon display on the home screen. The operations performed by Service Worker 507 are executed in the background, separately from the website provided by the browser 505. In other words, even when the browser 505 is not connected to the RUI, push notifications for the installed PWA are realized via Service Worker 507 running in the background. When a user installs a PWA via the RUI from the image forming apparatus 102, the browser 505 downloads Service Worker 507 from the image forming apparatus 102 via the RUI and registers it with the browser 505 as part of the PWA.

[0039] Figure 6 is a sequence diagram illustrating the PWA installation process performed in the management system. The PWA installation process involves generating a PWA, providing a website for installing the PWA on the user terminal 103, and causing the browser 505 on the user terminal 103 to install the PWA. In this embodiment, the functions to be provided by the PWA are determined according to the user privileges of the user who accessed the RUI (website), the PWA is generated, and provided to the user terminal 103. Each process performed by the image forming apparatus 102 shown in Figure 6 is realized by the CPU 201 of the image forming apparatus 102 calling and executing a program from memory. Each process performed by the user terminal 103 shown in Figure 6 is realized by the CPU 301 of the user terminal 103 calling and executing a program from memory.

[0040] In step S601, the browser 505 of the user terminal 103 accesses the RUI of the website provided by the image forming apparatus 102 based on the user's operation and makes a login request to the image forming apparatus 102. This process is when user 600 logs in to the RUI provided by the image forming apparatus 102 using the user terminal 103. The login request is sent to the web server 411 of the image forming apparatus 102 when user 600 enters user authentication information on the login screen displayed in the browser 505 of the user terminal 103 and presses the login button. An example of the login screen is shown in Figure 7. Figure 7 is a diagram showing an example of the login screen for the RUI displayed in the browser 505. The login screen 700 is displayed, for example, when user 600 accesses the RUI of the image forming apparatus 102 using the user terminal 103. The login screen 700 displays an input area for entering a combination of username 701 and password 702 as user authentication information, and a login button 703. User authentication information may include a user ID, email address, phone number, biometric information, or IC card information. When user 600 enters user authentication information and clicks the login button 703, a login request is sent from user terminal 103 to the web server 411 of the image forming apparatus 102.

[0041] The login processing unit 409 of the web server 411 of the image forming apparatus 102 receives a login request from the browser 505 of the user terminal 103. The login processing unit 409 performs login processing using the user authentication information received from user 600. The user authentication information is, for example, a combination of username and password. The login processing unit 409 compares the user authentication information received from user 600 with pre-registered user information. Pre-registered user information, such as username and password, may be stored in the storage unit 402 (ROM 202 or storage device 204) within the image forming apparatus 102, or in some terminal or server outside the image forming apparatus. If the login processing unit 409 successfully authenticates user 600, the process in step S602 is performed.

[0042] In step S602, the login processing unit 409 of the web server 411 of the image forming apparatus 102 issues a PWA generation method execution instruction to the PWA generation unit 410 of the web server 411. The PWA generation method execution instruction is an instruction to execute the generation process of a device management PWA to be installed on the user terminal 103. In step S603, the login processing unit 409 of the web server 411 of the image forming apparatus 102 transmits the permission information of user 600, who is the logged-in user, to the PWA generation unit 410. The permission information of the logged-in user may be stored in the storage unit 402 (ROM 202 or storage device 204) within the image forming apparatus 102, or in some terminal or server outside the image forming apparatus. Therefore, in S602 and S603, the PWA generation unit 410 of the web server 411 obtains the PWA generation method execution instruction and user permission information corresponding to the logged-in user to be used when generating the PWA.

[0043] In step S604, the PWA generation unit 410 of the web server 411 of the image forming apparatus 102 determines the functions of the PWA to be generated according to the login user's privileges and generates the software as a PWA. In this embodiment, the PWA generation unit 410 determines the functions that can be used in the Progressive Web App depending on whether the login user has administrator privileges or privileges other than administrator privileges (general user privileges). If the login user has administrator privileges, the PWA generation unit 410 determines that only functions (content) predetermined to be provided to administrator users will be provided as functions in the PWA. On the other hand, if the login user has privileges other than administrator privileges, the PWA generation unit 410 determines that only content predetermined to be provided to general users will be provided as functions in the PWA. The PWA generation unit 410 then generates a PWA that provides the determined functions.

[0044] The device management PWA provides event information, various counter information, wear status information for consumable parts, various logs, and errors generated by the image forming apparatus 102. The device management PWA also provides functions to change device information, network settings, user settings, and user terminal 103 information of the image forming apparatus 102. For example, it is undesirable for general users of the image forming apparatus 102 to be able to access the network setting change function provided by the device management PWA. Therefore, it is predetermined that the network setting change function will only be provided to the PWA for administrative users and not to the PWA for general users. The PWA generation unit 410 decides whether or not to include the network setting change function in the device management PWA based on the user 600's authorization information received from the login processing unit 409.

[0045] Functions provided only to administrators may include, in addition to network setting changes, some or all of the following functions: for example, device settings for the image forming apparatus 102, security settings, user settings, and functions related to user terminals 103. Furthermore, functions provided only to administrators may include some or all of the functions for providing information such as event information, various counter information, wear status information for consumable parts, various logs, and errors generated by the image forming apparatus 102. General users must not be able to use functions intended for administrators (functions that only administrators can use). On the other hand, administrators may be limited to using only administrator-only functions, or they may also be able to use functions intended for general users. There may be functions provided to both general users and administrators. Whether each function is provided to administrators or general users is predetermined.

[0046] In step S605, the PWA generation unit 410 of the web server 411 of the image forming apparatus 102 requests the browser 505 of the user terminal 103 used by user 600 to install the generated PWA. That is, the PWA generation unit 410 provides a website so that the generated PWA can be provided to the browser 505 of the user terminal 103 that sent the login request.

[0047] In step S606, the browser 505 displays an installation confirmation screen to ask the user for permission to uninstall, based on the PWA installation request received from the web server 411 of the image forming apparatus 102. The installation confirmation screen displays, for example, "Allow" and "Deny" buttons for the user 600 to choose whether or not to install the PWA. In step S607, the user 600 chooses whether or not to allow the installation of the PWA. If the user 600 denies (does not allow) the installation of the PWA, the image forming apparatus 102 provides a normal RUI (Rules of Use) as page data such as an HTML file, which is not a PWA, and displays it to the browser 505. An example of a normal RUI will be described later using Figure 10. The following describes the case where the user 600 allows the installation of the PWA. When the user 600 selects the "Allow PWA installation" button on the installation confirmation screen, the web server 411 detects that the user 600 has allowed the installation of the PWA.

[0048] In step S608, the PWA generation unit 410 of the web server 411 of the image forming apparatus 102 provides the generated PWA software by downloading it to the browser 505 on the user terminal 103 used by the user 600. After the PWA download is complete, the process in step S609 is performed. In step S609, the browser 505 on the user terminal 103 installs the PWA downloaded from the web server 411 of the image forming apparatus 102. After the PWA is installed, an icon is generated on the desktop or home screen of the user terminal 103, similar to a native application.

[0049] Through the above process, the image forming apparatus 102 provides pre-determined content (functions) to be provided to the administrator user as a device management PWA if the logged-in user has administrator privileges. On the other hand, if the logged-in user has privileges different from those of an administrator user, only the pre-determined content (functions) to be provided to the general user as a device management PWA is provided. The image forming apparatus 102 then provides the RUI (website) via the web server 411 so that the user terminal 103 can be provided with PWAs that have different functions available depending on the privileges of the user who logged into the RUI (website).

[0050] In this embodiment, an example was described in which the PWA generation unit 410 determines the functions to be provided by the PWA according to the user's privileges in step S604 and generates the PWA, but this is not the only example. For example, the PWA generation unit 410 may determine the functions to be provided by the PWA according to the user's privileges in step S604, and then, if permission for installation is obtained from the user, generate and provide the PWA according to the determined functions.

[0051] Furthermore, although this embodiment has been described on the premise that PWAs are also provided to general users with privileges different from administrator privileges, whether or not to provide PWAs to general users can be configured by the administrator user. Users with administrator privileges can configure whether or not to allow the installation of PWAs to users with privileges different from administrator privileges (general users) on a configuration screen provided by the web server 411, which is different from the RUI website. In step S604, the web server 411 checks the user's privileges, and if the confirmed user's privileges are those of a general user, it checks whether or not to allow the installation of PWAs to general users, and if permitted, it generates a general-purpose PWA.

[0052] Next, using Figures 8 and 9, examples of device management PWA screens displayed on the user terminal 103 will be explained for each user privilege. Figure 8 shows an example of a PWA screen for a general user with privileges different from administrator privileges. PWA screen 800 is the screen displayed by the PWA that provides RUI functionality, which is installed in step S609 when a general user logs in. On PWA screen 800, general users can view event information, various counter information, wear status information of consumable parts, various logs, and error information generated by the image forming apparatus 102. In addition, the PWA for general users also has a function to change some device settings of the image forming apparatus 102 that can be set by general users. On the other hand, the PWA for general users does not provide a function to change device settings that can only be set by users with administrator privileges, such as changing network settings.

[0053] Furthermore, the PWA for general users may include text, a link, and a push notification indicating that the PWA for administrator users can also be installed. The administrator user link 801 is an example of displaying text on the general user PWA indicating that the administrator user PWA can also be installed, along with a link to the login screen. The same content as the administrator user link 801 may be notified via push notification. When the administrator user link 801 is selected, the web server 411 provides the browser 505 with the login screen 700 shown in Figure 7. The web server 411 then performs user authentication based on the user authentication information obtained from the login screen 700, and if the user authorized to log in is a user with administrator privileges, it generates and provides the administrator PWA. By performing user authentication using the user authentication information of a user with administrator privileges on the login screen 700, the administrator user PWA can also be downloaded and installed.

[0054] FIG. 9 is a diagram showing an example of a screen of a PWA for a management user having administrative authority. The PWA screen 800 is a screen displayed by a PWA that provides an RUI function and is installed in step S609 when the management user logs in. In the PWA for administrators, in addition to the RUI function for general users, functions such as changing network settings and changing user settings are provided as management functions 802.

[0055] In addition, the functions provided to the management user may include some or all of the function of providing information such as event information generated by the image forming apparatus 102, various counter information, consumption degree information of consumable parts, various logs, and errors. Further, the functions provided to the management user may include some or all of functions such as device settings of the image forming apparatus 102 and functions of changing information related to the user terminal 103. Some of the functions provided to the management user are not provided to general users and are functions provided only to management users.

[0056] FIG.  10 is a diagram showing an example of a normal RUI provided by the image forming apparatus 102. The RUI 1000 is a screen of an RUI displayed on the browser 505 when page data such as HTMP is provided from the image forming apparatus 102, which is not a PWA. When the user does not permit the installation of the PWA in step S607, a normal RUI that is not a PWA is provided from the image forming apparatus 102. Even when the user does not permit the installation of the PWA and the PWA is not installed, the user can use the RUI 1000. The RUI 1000 is an example of an RUI provided to a general user having a different authority from the administrative authority, and the functions provided to the RUI 1000 are the same as the functions provided to the PWA screen 800 excluding the management user link 801. Also, the functions of the normal RUI provided when the logged-in user is a user having administrative authority are the same as the functions provided on the PWA screen 900 for administrators.

[0057] Figure 11 is a flowchart of the login process performed by a PWA. A PWA is created according to user privileges. Therefore, in the login process, the PWA determines whether the user attempting to log in has the user privileges targeted by this PWA. Each process performed by the user terminal 103 on which the PWA shown in Figure 11 is installed is realized by the CPU 301 of the user terminal 103 calling and executing the program from memory.

[0058] This process begins when a user attempts to log in to a PWA created according to user privileges and installed on user terminal 103. In step S1101, the PWA on user terminal 103 receives user authentication information from the user via browser 505. User authentication information is, for example, a combination of username and password. In step S1102, the PWA requests user authentication (login authentication) for the user attempting to log in to the image forming apparatus 102. When requesting user authentication, the PWA sends the user authentication information obtained in step S1101 to the image forming apparatus 102. The image forming apparatus 102 performs user authentication in response to the login authentication request received from the PWA on user terminal 103 and responds to user terminal 103 with the authentication result. In step S1103, the PWA determines whether the login authentication received from the image forming apparatus 102 was successful. If the login authentication is successful, the PWA performs the process in step S1104. On the other hand, if the login authentication is unsuccessful, the PWA performs the process in step S1107.

[0059] In step S1104, the PWA requests the image forming apparatus 102 to retrieve the user privileges held by the logged-in user. The image forming apparatus 102 responds to the user terminal 103 with the user privileges held by the logged-in user in response to the user privilege retrieval request received from the PWA on the user terminal 103. In step S1105, the PWA verifies whether the user privileges of the logged-in user received from the image forming apparatus 102 match the user privileges supported by the PWA. If the user privileges of the logged-in user and the user privileges supported by the PWA match, the PWA considers the verification successful and proceeds to step S1106. On the other hand, if the user privileges of the logged-in user and the user privileges supported by the PWA do not match, the PWA considers the verification unsuccessful and proceeds to step S1107. In this embodiment, administrator privileges and privileges other than administrator privileges are set as user privileges. For example, if a logged-in user has different user privileges than administrator privileges (e.g., regular user privileges), and the PWA supports administrator privileges, the user privileges will not match, and the matching will fail. Similarly, if a logged-in user has administrator privileges, and the PWA supports different user privileges, the user privileges will not match, and the matching will fail. On the other hand, if a logged-in user has administrator privileges, and the WA supports administrator privileges, the user privileges match, and the matching will succeed.

[0060] In step S1106, the PWA displays the PWA that was generated according to the logged-in user's permissions and installed on the user terminal 103. In step S1107, the PWA displays a login failure notification on the user terminal 103. That is, the PWA displays a login failure notification if user authentication fails or if the logged-in user's permissions and the user permissions corresponding to the PWA do not match. Note that the login failure notification displayed in step S1107 may differ depending on whether the user authentication process in step S1103 fails or the user permission matching in step S1105 fails.

[0061] In this embodiment, an example where a user can log in to a PWA only when the user authority of the logged-in user matches the user authority corresponding to the PWA has been described. However, the PWA corresponding to the administrator authority is not limited to this. The PWA corresponding to the administrator authority may be able to provide the RUI of the PWA for general users when accepting a login with the authority of a general user. The PWA corresponding to the administrator authority can provide the RUI of the PWA for management users and the RUI of the PWA for general users according to the authority of the logged-in user. Thereby, in order for management users to be able to check the functions of general users, management users can log in to the PWA for general users (for users without administrator authority). Therefore, in the PWA for administrators, instead of determining a match of user authorities in the verification of the user authority of the logged-in user in step S1105 and the user authority corresponding to the PWA, the RUI of the PWA to be provided is determined according to the user authority of the logged-in user. Specifically, the PWA for administrators determines that the UIR of the PWA for administrators is displayed and performs the process of S1106 when the user authority of the logged-in user is an administrative authority. On the other hand, the PWA for administrators determines that the UIR of the PWA for general users is displayed and performs the process of S1106 when the user authority of the logged-in user is a different authority from the administrative authority. Thereby, management users can use the PWA for general users and check the functions of the PWA for general users. When an administrator with administrative authority logs in to the PWA with the authority of a general user, only the functions of the device management PWA for general users are provided, and the functions of the device management PWA for management users are not provided.

[0062] Figure 12 shows an example of a login screen displayed during the login process to a PWA. Figure 12(A) is an example of a PWA login screen. The login screen 1200 is displayed when a PWA created according to the user permissions installed on the user terminal 103 is opened. The login screen 1200 displays an input area for entering a combination of username 1201 and password 1202 as user authentication information, and a login button 1203. Note that the user authentication information may also be a user ID, email address, phone number, biometric information, or IC card information. When the user terminal 103 detects that the user has entered the user authentication information and clicked the login button 1203, it executes a process (step S1101) to send a login authentication request to the web server 411 of the image forming apparatus 102.

[0063] Figure 12(B) shows an example of a login failure notification on the login screen. Login failure notification 1211 is an example of a message indicating that the user's permissions corresponding to the user authentication information do not match the user's permissions corresponding to the PWA. Login failure notification 1211 is displayed on the login screen 1210 in step S1107 if the user's permissions do not match during the PWA login process (No in step S1105). Note that the login failure notification message displayed when user authentication fails (No in step S1103) is different from login failure notification 1211. The login failure notification message when user authentication fails may, for example, indicate that the entered user authentication information is incorrect.

[0064] As described above, according to this embodiment, when the image forming apparatus 102 provides a Web page of the RUI as a PWA, it can dynamically determine the functions of the RUI according to the user's privileges and then provide the PWA to the user's terminal. Therefore, a PWA corresponding to the user's privileges is installed on the user's terminal, and users with administrator privileges can use administrator-only functions and content in the PWA. On the other hand, general users with privileges other than administrator privileges can not use administrator-only functions and content in the PWA. This prevents general users without administrator privileges from viewing some or all of the information regarding the image forming apparatus 102 or the user terminal connected to the image forming apparatus 102. Furthermore, it prevents general users without administrator privileges from making some or all of the changes to the settings of the image forming apparatus 102.

[0065] The disclosure of this embodiment includes the following network device configuration. (Composition 1) A network device that has a web server and can be used by multiple users with different levels of privileges, The aforementioned web server has a means of providing a website for installing software as a progressive web application on a user terminal to provide at least some of the functions of the network device, The aforementioned providing means is a network device that provides a website so that it can provide a progressive web application with different functions available depending on the permissions of the user who has logged into the website. (Configuration 2) The network device in Configuration 1 is characterized in that the providing means determines the functions available in the progressive web application depending on whether the user's privileges are administrator privileges or different from administrator privileges, and generates a progressive web application to be provided to the user terminal. (Composition 3) The network device according to configuration 1 or 2, characterized in that a user with administrator privileges can configure whether or not to allow the installation of a progressive web application with privileges other than administrator privileges through a settings screen provided by a web server different from the aforementioned website. (Composition 4) The network device according to any one of configurations 1 to 3, characterized in that the progressive web application installed on the user terminal checks the permissions of the user logging into the progressive web application, and displays a login failure notification if the permissions do not match those of the user supported by the progressive web application. (Composition 5) The network device according to any one of configurations 1 to 4, characterized in that the progressive web application installed on the user terminal, which supports administrator privileges, provides a remote UI for the progressive web application that supports users with privileges other than administrator privileges when the user logs in with privileges other than administrator privileges. (Composition 6) A network device according to any one of configurations 1 to 5, characterized in that, when a user logs in to a progressive web application with permissions different from administrator privileges, the network device notifies the user, either through a screen provided by the progressive web application or via a push notification to the user terminal, that a progressive web application with administrator privileges is available. (Composition 7) The network device according to configuration 6, characterized in that, if the user who has received the notification selects the link in the notification, the network device provides a login screen to the website, performs user authentication based on user authentication information obtained from the login screen, and if the user authorized to log in has administrator privileges, the providing means provides the website so that it can provide a progressive web application corresponding to administrator privileges.

[0066] (Other embodiments) The present invention can also be realized by supplying a program that implements one or more of the functions of the above-described embodiments to a system or device via a network or storage medium, and by having one or more processors in the computer of that system or device read and execute the program. It can also be realized by a circuit (e.g., an ASIC) that implements one or more functions.

[0067] Although preferred embodiments of the present invention have been described above, the present invention is not limited to these embodiments, and various modifications and changes are possible within the scope of its gist.

Claims

1. A network device that has a web server and can be used by multiple users with different levels of privileges, The aforementioned web server has a means of providing a website for installing software as a progressive web application on a user terminal to provide at least some of the functions of the network device, The aforementioned providing means is a network device that provides a website so that it can provide a progressive web application with different functions available depending on the permissions of the user who has logged into the website.

2. The network device according to claim 1, characterized in that the providing means determines the functions available in the progressive web application depending on whether the user's privileges are administrator privileges or different from administrator privileges, and generates a progressive web application to be provided to the user terminal.

3. The network device according to claim 1, characterized in that a user with administrator privileges can configure whether or not to allow the installation of a progressive web application with privileges other than administrator privileges through a settings screen provided by a web server different from the aforementioned website.

4. The network device according to claim 1, characterized in that the progressive web application installed on the user terminal checks the permissions of the user logging into the progressive web application, and displays a login failure notification if the permissions do not match those of the user supported by the progressive web application.

5. The network device according to claim 1, characterized in that the progressive web application installed on the user terminal, which supports administrator privileges, provides a remote UI of the progressive web application that supports users with privileges other than administrator privileges when the user logs in with privileges other than administrator privileges.

6. The network device according to claim 1, characterized in that, when a user logs in to a progressive web application with permissions different from administrator privileges, the network device notifies the user, either through a screen provided by the progressive web application or via a push notification to the user's terminal, that a progressive web application with administrator privileges is available.

7. The network device according to claim 6, characterized in that, if the user who has received the notification selects the link in the notification, the network device provides a login screen to the website, performs user authentication based on user authentication information obtained from the login screen, and if the user authorized to log in has administrator privileges, the providing means provides the website so that it can provide a progressive web application corresponding to administrator privileges.

8. A method for controlling a network device having a web server, which can be used by multiple users with different levels of privileges, The process includes providing a website on the user terminal for installing software as a progressive web application to provide at least some of the functions of the network device, via the aforementioned web server. A method for controlling a network device, characterized in that the above step provides a website so that it can provide a progressive web application with different functions available depending on the permissions of the user who has logged into the website.

9. A program that causes a computer in a network device to perform each of the steps described in claim 8.

Images