JP2020095568A - Information processor, control method of information processor, and program - Google Patents

Abstract

To prevent a storage region reserved for a Web browser gets tight due to an unnecessary cache related to the Web application that operates the device connected to the information processor which is operated by the Web browser.SOLUTION: When a client computer 102 on which a Web browser 320 operates makes access to a website that provides the web application that operates a device 103 connected by USB or Bluetooth, an authorization prompt is displayed (S422). When the connection is permitted with the authorization prompt, a ServiceWorker for executing the web application in the background separately from the web browser is installed according to a script provided by the Website (S425). On the other hand, when the connection is not permitted with the authorization prompt, the Service Worker is not installed even when there is the above script.SELECTED DRAWING: Figure 4

Description

The present invention relates to an information processing device in which a web browser operates, a control method of the information processing device, and a program.

There are technologies called WebUSB and WebBluetooth that can be operated by connecting to a USB device or Bluetooth device connected to a client computer from a Web application. In this technology, when a web application (Javascript) requests a connection to a USB device or a Bluetooth device, the web browser displays a connection permission prompt and asks the user for permission to connect. When the user selects connection permission from the connection permission prompt displayed on the web browser, the web application can connect to the USB device or the Bluetooth device, and the device can be operated from the web application. Bluetooth and JavaScript are registered trademarks.

While the device can be operated from the web application, there is a problem that it cannot be used offline due to the nature of the web application. Therefore, a technology has been proposed in which Java Script that operates in the background of a Web browser called ServiceWorker is used and the Web application is cached when online so that it can be used even offline.

JP, 2010-170257, A

In the technology using ServiceWorker, Javascript is automatically executed at the time of accessing a website that provides a web application, and the service worker is registered and the web application is cached. The cached Web application is stored in the storage area reserved for the Web browser. An upper limit is set for the capacity of the storage area reserved for this Web browser for each Web browser or each client computer.

Since a Web application for realizing WebUSB and WebBluetooth includes a program corresponding to a driver of a conventional native application, it is desirable that it can be used even offline. On the other hand, even though there is an upper limit to the storage area reserved for the Web browser, even the Web application that does not require offline operation is automatically cached by using the ServiceWorker. Therefore, there is a problem that the storage area reserved for the Web browser becomes tight due to the Web application that the user does not need to cache. It should be noted that since a Web application that is supposed to use WebUSB or WebBluetooth includes a program having a relatively large size corresponding to a driver, this storage area is particularly likely to be tight.

Patent Document 1 proposes a technique for preventing the storage area of the main body of the multifunction device from becoming tight by using an external storage device when installing an application in the multifunction device. However, since the storage area reserved for the above-described Web browser is reserved in the storage device in which the Web browser itself is installed, it is not possible to cache only the Web application in the external storage device according to Patent Document 1. Can not. As described above, the conventional technique cannot solve the problem that the web application is cached and the storage area reserved for the web browser is tight when the ServiceWorker is used.

The present invention has been made to solve the above problems. SUMMARY OF THE INVENTION It is an object of the present invention to provide a mechanism for preventing a storage area reserved for a web browser from being overwhelmed by an unnecessary cache related to a web application that operates a device connected to an information processing apparatus. Is.

The present invention is an information processing device in which a web browser operates, and when a web application providing a web application for operating a device connected to the information processing device by USB or Bluetooth is accessed, the web application is Display means for displaying a screen for confirming whether to permit connection to the device, and, if connection to the device via the screen is permitted, according to a script provided by the website, Installation means for installing an application program for executing a web application in the background separately from the web browser, wherein the script is executed when connection to the device via the screen is not permitted. Even if there is, the application program is not installed.

According to the present invention, it is possible to prevent a storage area reserved for a web browser from being tight due to an unnecessary cache related to a web application that operates a device connected to an information processing apparatus.

The block diagram of the network system which shows this embodiment. Hardware configuration diagram. Software configuration diagram. The figure which shows the sequence at the time of caching a Web application. The figure which shows UI at the time of caching a Web application. The figure which shows UI at the time of deleting connection information. The figure which shows the sequence when it fails in the cache of a Web application. The figure which shows UI when cache of a Web application fails.

Embodiments for carrying out the present invention will be described below with reference to the drawings.
[First Embodiment]
<Network configuration>
FIG. 1 is a diagram showing an example of a configuration of a network system showing an embodiment of the present invention.
The server 101 is a server that provides a web application (also referred to as “web application”) to the client computer 102 via the network 104.
The client computer 102 is an information processing device used by a user. As the client computer 102, a personal computer, laptop computer, tablet computer, smartphone, or the like can be used.
The device 103 is a device such as a scanner or printer that is used by connecting to the client computer 102 via the USB 105.

The network 104 is a so-called communication network. The network 104 is realized by, for example, a LAN such as the Internet, a WAN, a telephone line, a dedicated digital line, an ATM or a frame relay line, a cable TV line, a data broadcasting wireless line, or a combination thereof.

Reference numeral 105 denotes a USB (Universal Serial Bus) for connecting the client computer 102 and the device 103. In the present embodiment, a configuration in which the client computer 102 and the device 103 are connected by the USB 105 will be described as an example, but the 105 is not limited to the USB. For example, 105 may be another standard such as Bluetooth or NFC (Near Field Communication).

<Hardware configuration>
FIG. 2 is a diagram showing an example of a hardware configuration of the server 101 having an information processing function, the client computer 102, and the device 103. The hardware of the server 101, the client computer 102, and the device 103 need not have all the configurations shown in FIG.

The CPU 201 executes a program read from the RAM 202, ROM 203, storage device 204, or the like. The RAM 202 functions as a temporary memory area. The ROM 203 stores embedded programs and data.

The storage device 204 is a secondary storage device such as a hard disk drive (HDD) or a solid state drive (SSD). The storage device 204 stores a program that realizes an OS (Operating System) 330 (FIG. 3) described later and an application program that realizes a Web browser 320 (FIG. 3) operating on the OS. The CPU 201 loads these programs stored in the storage device 204 into the RAM 202 as needed and executes them. Further, the application program for realizing the web browser 320 executed here supports APIs such as WebUSB and WebBluetooth.

The user interface 205 is a user interface such as a keyboard, a pointing device (mouse, touch pad, touch panel, trackball, etc.), display or the like. The network interface 206 is connected to a network such as a LAN and communicates with other devices connected to the network. The USB interface 207 is connected according to the USB standard and communicates with an external device. As described above, in the present embodiment, the case where the USB is used as the 105 is described, but when the 105 is another standard such as Bluetooth or NFC, the 207 uses an interface compliant with the 105 standard.
The respective units constituting the hardware such as 201 to 207 are connected via an internal bus 208.

<Software configuration>
Hereinafter, the software configurations of the server 101, the client computer 102, and the device 103 will be described with reference to FIG.
FIG. 3A is a diagram showing an example of the software configuration of the server 101. The software configuration of the server 101 shown in FIG. 3A is realized by the CPU 201 of the server 101 executing a program stored in the storage device 204 or the like.
As shown in FIG. 3A, the Web server 310 includes a network communication unit 311 and a Web application management unit 312.

The network communication unit 311 is a software module for communicating with an external system such as the client computer 102.
In response to a request from the web browser 320, the web application management unit 312 provides a web application made up of web content such as HTML or Javascript. Further, the Web application management unit 312 also provides various data in a format such as XLM or JSON by using WebAPI. In the present embodiment, the Web application provided by the Web application management unit 312 includes JavaScript for connecting to the device 103 and operating it. Further, it also includes JavaScript that instructs the web browser 320 to cache the web application provided by the web application management unit 312.

FIG. 3B is a diagram showing an example of the software configuration of the client computer 102. The software configuration of the client computer 102 shown in FIG. 3B is realized by the CPU 201 of the client computer 102 executing a program stored in the storage device 204 or the like.
As shown in FIG. 3B, the web browser 320 includes a network communication unit 321, a display unit 322, a script execution unit 323, a data management unit 324, and a USB communication unit 325.

The network communication unit 321 is a software module for the web browser 320 to communicate with an external system such as the web server 310.
The display unit 322 is a software module for displaying a UI (User Interface) generated from HTML, CSS, Java Script, etc. included in the Web browser 320 itself or the Web application.

The script execution unit 323 is a software module for analyzing and executing JavaScript included in the Web application acquired by the network communication unit 321.
The data management unit 324 corresponds to the storage area reserved for the web browser, and stores the cache of the web application, work data, and data such as ServiceWorker described later in the storage area reserved for the web browser. to manage.

The USB communication unit 325 is a software module for operating the USB device 103 from Java Script operating in the web browser 320. JavaScript executed by the script execution unit 323 uses the USB communication unit 325 to connect to the USB device 103 via the USB control unit 331 included in the OS 330 to perform an operation.
The OS 330 includes a USB control unit 331. The OS 330 includes many software modules other than the USB control unit 331, but they are omitted in the description of this embodiment.
The USB control unit 331 is a software module for controlling USB communication with the USB interface 207.

Here, the ServiceWorker used in this embodiment to cache the Web application will be described.
ServiceWorker is Javascript that operates in the background of a Web browser. The Web application provided by the Web application management unit 312 includes Java Script for registering and operating the ServiceWorker in the Web browser 320. First, the web browser 320 acquires the web application provided by the web application management unit 312. When the script execution unit 323 executes JavaScript for registering and operating the ServiceWorker included in the acquired Web application, the ServiceWorker is stored in the data management unit 324. Below, an example of the registration information of ServiceWorker is shown in the JSON format data.

{
"service_worker": [
{
"origin": "https://xxx.com",
"source": "sw.js",
"version": "3",
"status": "active"
}
]
}

Then, the content is cached by designating the content to be cached in the Javascript in the ServiceWorker. Below, an example of the content to be cached is shown in JSON format data.

{
"cache_storage": [
{
"origin": "https://xxx.com",
"cache_name": "v3",
"contents": [
{
"path": "index.html",
"content_type": "text/html",
"content_length": "1000",
"cache_time": "2018/01/01 12:00:00",
"header": {
...
},
"body": {
...
}
},
{
"path": "controller.js",
"content_type": "text/JavaScript",
"content_length": "30000",
"cache_time": "2018/01/01 12:00:01",
"header": {
...
},
"body": {
...
}
},
{
"path": "logo.png",
"content_type": "image/png",
"content_length": "10000",
"cache_time": "2018/01/01 12:00:02",
"header": {
...
},
"body": {
...
}
}
]
}
]
}

The content to be cached is stored in the data management unit 324 by the script execution unit 323. After that, when accessing the “origin” and “path” of the cached content from the Web browser 320, if there is no change in the value shown in “cache_name” offline, the content stored (cached) in the data management unit 324 is Read. If there is a change in the value indicated by "cache_name" while online, ServiceWorker acquires the Web application from the Web application management unit 312 and updates the cache. By configuring the Web application as described above, the client computer 102 can be used even when it is offline. Note that the ServiceWorker notifies the website of the information and the like acquired from the device 103 when the client computer 102 is brought online while the above is offline.

FIG. 3C is a diagram showing the software configuration of the device 103. The software configuration of the device 103 shown in FIG. 3C is realized by the CPU 201 of the device 103 executing a program stored in the ROM 203 or the like.
As shown in FIG. 3C, the USB control unit 341 is a USB control unit in the device 103, and is a software module for controlling USB communication with the USB interface 207.

The device function execution unit 342 is a software module for executing the function of the device 103, and realizes a scan function when the device 103 is a scanner and a print function when the device 103 is a printer, for example. It is also possible for the USB control unit 341 to execute the function of the device 103 by receiving a command from an external system such as the client computer 102 and issuing a command to the device function execution unit 342.

<Sequence diagram and UI>
The cache behavior of the Web application when WebUSB is used, which is a feature of this embodiment, will be described with reference to the sequence diagram of FIG. 4 and the UI of FIG.
FIG. 4 is a sequence diagram showing an example of processing from the user 401 connecting the device 103 to the client computer 102 to the cache of the Web application. In this sequence diagram, the processing of the device 103 is realized by the CPU 201 of the device 103 executing a program stored in the ROM 203 or the like. The processing of the client computer 102 is realized by the CPU 201 of the client computer 102 executing a program stored in the storage device 204 or the like. The processing of the web server 310 is realized by the CPU 201 of the server 101 executing a program stored in the storage device 204 or the like.

First, in step S411, the user 401 connects the device 103 to the client computer 102.
In step S412, the web browser 320 monitors the connection of the device 103. Then, in step S413, when the web browser 320 detects the connection of the device 103 based on the connection event of the device 103 or the connection state of the device 103 that can be acquired from the USB control unit 331 of the OS 330, the process proceeds to step S414.

In step S<b>414, the web browser 320 makes a request to the USB control unit 331 of the OS 330 to acquire the descriptor of the device 103. The descriptor is detailed information of a device owned by the device 103 based on the USB standard, and includes, for example, information such as a vendor ID or a product ID of the device 103, power consumption, and a transfer method. Among them, the information indicating the landing page is included as a descriptor for WebUSB. The landing page is a URL of a website that provides a web application for operating the device 103, and is set in the device 103 by the device vendor.

In response to the request of S414, in S415, the USB control unit 331 of the OS 330 requests the USB control unit 341 of the device 103 to obtain a descriptor.
In response to the request of S415, in S416, the USB control unit 341 of the device 103 returns the descriptor to the USB control unit 331 of the OS 330.
When the returned descriptor is acquired, the USB control unit 331 of the OS 330 returns the acquired descriptor to the Web browser 320 in S417.

When the returned descriptor is acquired, the web browser 320 presents the landing page included in the acquired descriptor to the user 401 in step S418, as illustrated in FIG. 5A. Here, the screen for presenting the landing page will be described with reference to FIG.

FIG. 5A is a diagram showing an example of the desktop screen of the client computer 102 when the Web browser 320 presents the landing page to the user 401 in S418.

The screen 510 is a desktop screen of the client computer 102.
The window 511 is a notification window of the Web browser 320, and is displayed when the device 103 having the landing page in the descriptor is connected to the client computer 102.
The message 512 is a message that prompts the user 401 to guide to the landing page. When the button 513 is pressed by the user 401, the UI of the Web browser 320 shown in FIG. 5B is activated, and the processing of S419 in FIG. 4 is started. When the button 514 is pressed, the sequence of FIG. 4 ends. By setting the landing page in the device 103, it is possible to guide the user to a web application provider necessary for operating the device 103 when connecting to the client computer 102. Even if the button 514 is pressed and the notification window 511 is closed, the web application can be acquired by directly inputting the URL of the website in the UI of the web browser 320 later.

Hereinafter, the description returns to FIG.
In step S419, the user 401 presses the button 513 to instruct the web browser 320 to access the landing page. In response to the instruction, in step S420, the web browser 320 accesses the website provided by the web server 310 indicated by the landing page.
In response to the access in S420, in S421, the Web application management unit 312 of the Web server 310 returns the Web application for operating the device 103 to the Web browser 320. When the web browser 320 executes the Javascript included in the returned web application, a UI as shown in FIG. 5B is displayed. This UI will be described below with reference to FIG.

FIG. 5B is a diagram showing an example of the UI of the web browser 320.
Reference numeral 521 is a prompt (hereinafter, referred to as “connection permission prompt”) for confirming whether or not the connection (operation) from the Web application to the device 103 is permitted. The connection permission prompt 521 is displayed when the script execution unit 323 executes Java Script that asks whether connection to the device is possible, and is requested for each origin that provides the Web application.

Reference numeral 522 is a list of devices 103 connected to the client computer 102, and at this point of time, the connection from the Web application to the device 103 has not been permitted. The user 401 can select, from the device list 522, the device 103 permitted to connect from the Web application. The connection permission prompt 521 is for protecting the device 103 from a malicious web application.

When the user 401 presses the button 523 with the device selected in the device list 522, the connection from the Web application to the selected device 103 is permitted. After that, the script execution unit 323 generates connection information, which is a combination of the device and the origin permitted to connect from the Web application, and stores the connection information in the data management unit 324.
On the other hand, when the user 401 presses the button 524, the connection from the Web application to the device 103 is not permitted and the connection permission prompt 521 is closed.

It has been described that the Web application can be used even offline by using the ServiceWorker. Here, consider a case where the user 401 presses the button 524 (connection refusal) or the Web application ends without pressing any of the buttons 523 and 524. In this case, since the connection from the Web application to the device 103 is not permitted, the device 103 cannot be operated even if the cache is performed by the ServiceWorker. In other words, if the connection from the Web application to the device 103 is not permitted, the storage area of the data management unit 324 becomes tight, and therefore it is not desirable to perform the cache by ServiceWorker. However, when the web browser 320 accesses the website and the script execution unit 323 executes Java Script included in the web application, the cache process is executed. It is possible to avoid the cache process so that the cache process is not executed if the connection is not permitted by the connection permission prompt 521, but the cache process is not necessarily executed because the implementation differs depending on the Web server 310. .. Therefore, a method for preventing unnecessary caching based on the judgment of the Web browser will be described below.

Hereinafter, the description returns to FIG.
After S421, S422 to S425 or S431 to S435 are executed.
Steps S422 to S425 are a sequence in the case where the user 401 first selects connection permission/rejection, and then the cache process is executed.
S431 to S435 are a sequence in the case where the cache process is executed before the user 401 selects connection permission/rejection.

First, using S422 to S425, a sequence will be described in which the user 401 first selects connection permission/rejection, and then cache processing is executed.
In step S422, the script execution unit 323 executes the Java script of the web application to display the connection permission prompt 521 on the display unit 322 of the web browser 320.

Next, in step S423, the user 401 selects connection permission/rejection. When the user 401 has selected the connection permission in S423, the script execution unit 323 executes S424.
In step S424, the script execution unit 323 generates connection information that is a combination of the device 103 and the origin permitted to connect from the Web application described above. Next, in step S425, the script execution unit 323 executes JavaScript for registering ServiceWorker and caching (holding) the Web application. That is, ServiceWorker is installed.
On the other hand, when the user 401 has selected connection refusal in S423, the script execution unit 323 does not execute S424 and ends the sequence.

Next, a sequence in the case where the cache process is executed before the user 401 selects the connection permission/rejection will be described using S431 to S435.
In step S431, the script execution unit 323 executes Java Script for registering ServiceWorker and caching the Web application.
Next, in step S432, the script execution unit 323 executes the Javascript of the web application to display the connection permission prompt 521 on the display unit 322 of the web browser 320.

Next, in step S433, the user 401 selects connection permission/rejection. If the user 401 has selected connection refusal, the script execution unit 323 executes S434. In step S434, the script execution unit 323 deletes the ServiceWorker and cache of the Web application stored in the data management unit 324.
On the other hand, when the user 401 has selected connection permission, the script execution unit 323 executes S435. In S435, the script execution unit 323 generates connection information, as in S424 described above.

As described above, the Web browser 320 executes S422 to S425 or S431 to S435 in accordance with the execution order of the programs of the Web application, thereby controlling not to perform unnecessary cache. By this control, it is possible to prevent the storage area of the data management unit 324, which is a storage area reserved for the Web browser, from being overwhelmed by unnecessary cache. Further, since the ServiceWorker itself is deleted together with the unnecessary cache, it is possible to prevent the background processing unnecessary for the user 401 from being executed.

[Second Embodiment]
In the above-described first embodiment, the method of not caching or deleting the cache when the user 401 rejects the connection from the Web application to the device 103 in the connection permission prompt 521 has been described. By this method, it is possible to prevent the storage area reserved for the Web browser from being overwhelmed by unnecessary cache.
On the other hand, there is a case in which the cache was used at the beginning of using the Web application, but it is no longer needed at a certain point of time and it is desired to delete the cache. In that case, it is possible to select and delete the target cache by the function of the Web browser 320. However, considering the use of the Web application off-line, it is assumed that Local Storage, Indexed DB, or the like is used as a storage area for work data. That is, it is desirable to delete not only the cache of Web contents such as HTML and Javascript by ServiceWorker, but also the work data stored in Local Storage, Indexed DB and the like.
In the second embodiment, a configuration will be described in which the connection permission by the connection permission prompt 521 is permitted, and the cache and work data of a Web application that is no longer needed is deleted efficiently.

FIG. 6 is a diagram showing an example of a UI of the Web browser 320 for managing the connection information of the device 103 permitted to connect in the client computer 102.
FIG. 6A is a UI that displays a list of connection information generated by the script execution unit 323 when the user 401 presses the button 523.
FIG. 6B is a UI for confirming whether or not to delete the connection information.

As described in the first embodiment, the connection information of the device permitted to connect from the web application by the connection permission prompt is information on the combination of the device and the origin permitted to connect from the web application. When the button 611 associated with each piece of connection information is pressed on the UI in FIG. 6A, the web browser 320 makes a screen transition to the UI in FIG. 6B.

In FIG. 6B, the modal dialog 620 has a message 621 for confirming whether or not to delete the selected connection information, a check box 622, a button 623, and a button 624.

The check box 622 is a check box for selecting whether to delete the data generated at the origin of the connection information together with the connection information. The generated data includes not only the ServiceWorker and the cache, but also the data stored in the above-mentioned Local Storage, Indexed DB, or the like. These data are data generated based on the same origin policy, and are data managed for each origin.

An example of work data is shown below in JSON format.
An example of the data related to the ServiceWorker and the cache has been shown in the first embodiment, and will be omitted. These data are stored in the data management unit 324, which is a storage area reserved for the Web browser.

{
"local_storage": [
{
"origin": "https://xxx.com",
"data": {
"picture_title_001": "river",
"picture_title_002": "sea",
"picture_title_003": "mountain"
}
}
],
"indexed_db": [
{
"origin": "https://xxx.com",
"object_store": [
{
"store_name": "store1",
"data": {
"river": ...,
"sea": ...,
"mountain": ...
}
}
]
}
],
"cookies": [
{
"origin": "https://xxx.com",
"data": [
{
"name": "ID",
"value": "608e2e7b-46a5-448f-b8ba-02cb57609e77",
"domain": "xxx.com",
"path": "/"
}
]
}
]
}

When the “Yes” button 623 is pressed with the check box 622 checked, the Web browser 320 deletes the connection information, the ServiceWorker and cache of the same origin as the connection information, and the work data. For example, the data regarding "https://xxx.com" to be deleted in FIG. 6B is searched from the JSON format data shown in the first embodiment and immediately before, and the value of "origin" is obtained. Delete the matching data.

On the other hand, when the “Yes” button 623 is pressed while the check box 622 is not checked, the web browser 320 deletes only the connection information.
If the “No” button 624 is pressed, nothing is executed and the web browser 320 returns to the UI shown in FIG.

As described above, the connection information of the device 103 is deleted, and at the same time, the service worker, the cache, and the work data of the same origin as the connection information are deleted, so that the data unnecessary for the user 401 can be efficiently deleted. it can. As a result, it is possible to prevent the storage area of the data management unit 324, which is a storage area reserved for the Web browser, from becoming tight due to unnecessary data.

[Third Embodiment]
In the sequence shown in FIG. 4 of the above-described first embodiment, the case where the cache process ends normally has been described. However, when the script execution unit 323 executes the cache process, the ServiceWorker and the Web content to be cached are stored in the data management unit 324, but the process may fail due to insufficient free space in the storage area. In this case, the web application is not cached even though the user 401 presses the button 523 (select connection permission) on the connection permission prompt 521, and the user 401 cannot be aware that the processing has failed.
Therefore, in the third embodiment, even when the free space of the data management unit 324 is insufficient, the user 401 can notice the fact and presents the recovery method to the user 401 with reference to FIGS. 7 and 8. Explain.

FIG. 7 is a sequence diagram for explaining the third embodiment and corresponds to a sequence diagram obtained by expanding the sequence of FIG. In this sequence diagram, the processing of the device 103 is realized by the CPU 201 of the device 103 executing a program stored in the ROM 203 or the like. The processing of the client computer 102 is realized by the CPU 201 of the client computer 102 executing a program stored in the storage device 204 or the like. The processing of the web server 310 is realized by the CPU 201 of the server 101 executing a program stored in the storage device 204 or the like.

It should be noted that S411 to S421 are the same steps as those in FIG. 4 shown in the first embodiment, and therefore description thereof will be omitted. After S421, S711 to S715 or S721 to S726 are executed.
S711 to S715 are a sequence in the case where the connection permission/rejection is selected by the user 401 before the cache of the Web application.
S721 to S726 are a sequence in the case where the Web application is cached prior to the connection permission/rejection selection by the user 401.

First, S711 to S715 will be described.
In step S711, the script execution unit 323 displays the connection permission prompt 521 to the user 401 by executing the web application.
Next, in step S<b>712, the user 401 selects permission/rejection of connection from the Web application to the device 103. When the user 401 has selected the connection refusal in S712, the script execution unit 323 ends the sequence.

On the other hand, when the user 401 has selected connection permission in S712, the script execution unit 323 executes S713.
In S713, the script execution unit 323 generates connection information, as in S424 in the first embodiment.
Next, in step S<b>714, the script execution unit 323 executes JavaScript that registers ServiceWorker and caches the Web application.
If the script execution unit 323 normally ends the process in S714, the sequence ends.

On the other hand, in step S714, if the script execution unit 323 executes JavaScript and an error regarding insufficient free space in the data management unit 324 occurs, the process proceeds to step S715. The error relating to insufficient free space is, for example, “QUOTA_EXCEEDED_ERR”.
In step S715, the script execution unit 323 displays the prompt 810 of FIG. 8 on the display unit 322 on the web browser 320 to notify the user 401 that the process of step S714 has failed. Here, the prompt 810 will be described with reference to FIG.

FIG. 8A is a diagram showing an example of the UI of the Web browser 320 when the script execution unit 323 executes the cache process but the data management unit 324 cannot cache the data due to insufficient free space.

The prompt 810 has a message 811, a button 812, and a button 813 indicating that the cache has failed. When the button 812 is pressed, the web browser 320 displays the UI shown in FIG.
When the button 813 is pressed, the web browser 320 closes the prompt 810.

FIG. 8B is a diagram showing an example of a UI of the Web browser 320 for operating the data stored in the data management unit 324.
Reference numeral 821 is a list of data types stored in the data management unit 324. If you select each data type with the mouse cursor and expand it, you can browse the data contents for each origin. The user can increase the free area of the data management unit 324 by using this list to select and delete unnecessary data. The graph 822 is a graph showing the usage rate of the data stored in the data management unit 324 for each data type.

Hereinafter, returning to the description of FIG. 7, S721 to S726 will be described.
In step S<b>721, the script execution unit 323 executes Java Script that registers ServiceWorker and caches the Web application. In S721, if the cache fails due to the lack of free space in the data management unit 324, the script execution unit 323 stores the failure.
Next, in step S722, the script execution unit 323 displays the connection permission prompt 521 on the user 401.

Next, in step S723, the user 401 selects permission/rejection of connection from the Web application to the device 103. When the user 401 has selected the connection permission in S723, the script execution unit 323 executes S724.
In S724, the script execution unit 323 generates connection information, as in S424 in the first embodiment. After that, the script execution unit 323 confirms whether or not there is a failure stored in S721, and when it has not failed, the sequence ends.

On the other hand, in S724, if the cache fails due to the lack of free space in the data management unit 324 in S721, the script execution unit 323 executes S725.
In step S725, the script execution unit 323 notifies the user 401 that the processing in step S721 has failed, as in step S715.

On the other hand, if the user 401 has selected connection refusal in S723, the script execution unit 323 executes S726.
In S726, the script execution unit 323 deletes the ServiceWorker and the Web application cache registered in S721. Even if the cache process in S721 fails during the process, the data saved halfway is deleted.

As described above, by notifying the user 401 that the free space of the data management unit 324 is insufficient, the user 401 notices that the Web application cannot be cached and can perform the recovery operation. Further, the notification is given only when the user 401 selects the permission to connect to the device 103, that is, only when the user has the intention to cache the Web application. The operation can be performed.

As described above, according to each embodiment, it is possible to prevent a storage area reserved for a web browser from being tight due to an unnecessary cache relating to a web application that operates a device connected by USB or Bluetooth. it can.

The configurations and contents of the various data described above are not limited to this, and may be configured with various configurations and contents depending on the use and purpose.
Although one embodiment has been described above, the present invention can be implemented as, for example, a system, an apparatus, a method, a program, a storage medium, or the like. Specifically, it may be applied to a system composed of a plurality of devices, or may be applied to an apparatus composed of one device.
Further, the present invention also includes all configurations in which the above-described embodiments are combined.

(Other embodiments)
The present invention supplies a program that implements one or more functions of the above-described embodiments to a system or apparatus via a network or a storage medium, and one or more processors in a computer of the system or apparatus read and execute the program. It can also be realized by the processing. It can also be realized by a circuit (for example, ASIC) that realizes one or more functions.
Further, the present invention may be applied to a system including a plurality of devices or an apparatus including one device.
The present invention is not limited to the above-described embodiments, and various modifications (including organic combinations of the embodiments) are possible based on the gist of the present invention, which are excluded from the scope of the present invention. is not. That is, the present invention includes all configurations that combine the above-described embodiments and the modifications thereof.

Claims (10)

An information processing device on which a web browser operates,
When accessing a website that provides a web application that operates a device connected to the information processing apparatus by USB or Bluetooth, a screen for confirming whether the web application permits the connection to the device is displayed. Display means for displaying,
An installation that installs an application program for executing the web application in the background separately from the web browser according to a script provided by the website when it is permitted to connect to the device through the screen. And means,
An information processing apparatus, wherein the application program is not installed even if there is the script when connection to the device via the screen is not permitted. An information processing device on which a web browser operates,
When accessing a website that provides a web application for operating a device connected to the information processing apparatus by USB or Bluetooth, the web application is executed in a background separate from the web browser according to a script provided by the website. Installation means to install the application program to run in
Display means for displaying a screen for confirming whether the web application permits connection to the device;
Deleting means for deleting the installed application program when connection to the device via the screen is not permitted,
An information processing device comprising: 3. The web browser accesses the website according to information acquired from a device connected to the information processing device by USB or Bluetooth at a timing corresponding to the connection. The information processing device described. A storage unit that stores connection information that is a combination of information of a source of the web application and information of the device when connection to the device is permitted via the screen,
Instruction means for instructing deletion of the connection information,
Second deletion means for deleting the connection information and data associated with the provider of the application program corresponding to the connection information in response to an instruction from the instruction means,
The information processing apparatus according to claim 1, further comprising: The said installed application program notifies the information acquired from the said device to the said website, when it becomes online, while being offline, The information acquired from the said device is offline. Information processing device. The information processing apparatus according to claim 1, wherein, when the application program is installed, the web application is held in a storage area reserved for the web browser. .. The processing for holding the web application in the storage area, further comprising a notification means for notifying that the storage area is insufficient when the storage area is insufficient. 6. The information processing device according to item 6. A method for controlling an information processing device on which a web browser operates, comprising:
When accessing a website that provides a web application that operates a device connected to the information processing apparatus by USB or Bluetooth, a screen for confirming whether the web application permits the connection to the device is displayed. Display steps to display,
An installation that installs an application program for executing the web application in the background separately from the web browser according to a script provided by the website when it is permitted to connect to the device through the screen. Have steps and
A method for controlling an information processing apparatus, wherein the application program is not installed even if there is the script when connection to the device via the screen is not permitted. A method for controlling an information processing device on which a web browser operates, comprising:
When accessing a website that provides a web application for operating a device connected to the information processing apparatus by USB or Bluetooth, the web application is executed in a background separate from the web browser according to a script provided by the website. Installation steps to install the application program to run on
A display step of displaying a screen for confirming whether the web application allows the device to connect to the device;
A deleting step of deleting the installed application program when it is not permitted to connect to the device via the screen;
A method for controlling an information processing apparatus, comprising: A program for causing a computer to function as the unit according to any one of claims 1 to 7.