JP2014182553A - Proxy device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To increase a speed using cache even when there exists a page in which correction of one display contents affects display contents of another screen, in proxy processing to an HTTP server having a plurality of screens in which the contents of the displayed screens have correlation with one another.SOLUTION: A proxy device stores a dependency table 13 in which dependency between screens provided by a Web-GUI bundle 22 is described, and a setting change URL table 15 in which a URL designated when changing setting on the Web-GUI bundle 22 is described, and when the URL requested by a request is described in the setting change URL table 15, the proxy device invalidates cache information having dependency on the requested URL. The proxy device includes a change parameter relevant screen table 17 in which a parameter is related to the screen, receives information of the changed parameter from a parameter change notification section 16, identifies a screen related to the changed parameter, and invalidates the cache information.

Description

  The present invention relates to a technique for increasing the speed by relaying communication between a server and a client.

  Until now, HGW vendors have created Web-GUIs (setting screens) for HGWs (home gateways) according to their implementations. A server prepared for displaying this screen is assumed to be an HTTP server (Native). By creating a common Web-GUI as a Java application (bundle) and mounting it on each company's HGW, functions can be unified and costs can be reduced. At this time, an HTTP server used when Java displays a screen is assumed to be an HTTP server (Java).

  Normally, when performing standby on the HTTP server side, the 80th port is generally used. Although it is desirable to use port 80 when waiting with the HTTP server (Java) function, the HTTP servers (Native) used by HGW vendors that have been used in the past are not only screen displays but also extensions. It is also used for the simple number payout function and the like, and it is essential that the 80th port waits on the HTTP server (Native) side. Therefore, the Java side waits at another port, for example, 8888 port. In addition to the above, the GUI screen displayed by Java needs to secure connectivity from the remote maintenance system prepared for the customer's maintenance / setting support service, but the existing remote maintenance system is 80 from the viewpoint of security. Since communication other than the port that is waiting on the number is blocked, if the port 8888 is assigned to the Java side, the connectivity from the remote maintenance system cannot be secured.

  Therefore, the reverse proxy function is installed in the HGW, and all communications for the HTTP server (Java) are made to wait at the 80th port once, and the HGW internal function is processed again by the HTTP server (Java) waiting at another port. Proxying solves the above two problems.

  After terminating the request from the client, the reverse proxy regenerates a new request with the reverse proxy itself as the client. Since it takes time to perform the above processing for each request, a method of responding to the request using a cache is used. For example, in Patent Document 1, a proxy system is arranged between a client and a server, and the proxy system caches server data in advance to increase the speed.

JP 2009-187466 A

  However, if there are many pages for changing the setting information and the setting contents of one page affect the display of another page, the cached page may not match the actual setting information. FIG. 9 shows an example of the configuration of the setting screen that the HGW has. In the example shown in the figure, there are pages for performing basic setting, telephone setting, and detailed setting below the TOP screen, and there are pages for performing DNS setting and static NAT setting under the detailed setting. On the static NAT setting page, a list of the entries of the set static NAT is displayed. An edit button is arranged next to each entry, and when the edit button is pressed, the entry edit page is displayed and a static NAT entry page is displayed. You can edit the NAT settings. When the entry setting is changed on the entry edit page, the entry information on the static NAT setting page is also changed. Therefore, if you return to the static NAT setting page after editing the entry on the entry edit page, it should be reflected on the static NAT setting page, but the cache of the static NAT setting page is not reflected and the old information remains unchanged. turn into.

  In order to deal with the above problem, a method that does not use a cache in the reverse proxy is also conceivable, but the reverse proxy processing is heavy for the HGW, and the response to the client is delayed.

  The present invention has been made in view of the above, and in proxy processing for an HTTP server having a plurality of screens correlated with the content of the screen to be displayed, the modification of one display content is changed to the display content of the other screen. The purpose is to increase the speed by using a cache even when there is an affected page.

  A proxy device according to a first aspect of the present invention is a proxy device that relays communication between a server having a screen data whose contents to be displayed are changed by a change in a parameter setting value and a client terminal. A cache storage unit that holds the acquired screen data, and a request received from the client terminal. If the screen data that is the target of the request is held in the cache storage unit, the screen data is stored from the cache storage unit. When the screen data is read and returned to the client terminal, and the screen data is not held in the cache storage unit, the server is requested to acquire the screen data, and the request is a request to change the parameter setting value Sends the request to the server and also holds the image stored in the cache storage means. It characterized by having a a proxy means for disabling the screen data associated with the parameter of the data.

  In the proxy device, the proxy unit includes a dependency relationship table describing dependency relationships between screen data of the server, and a setting change request table describing a list of requests for changing setting values of the parameters. When the request received from the client terminal corresponds to a request described in the setting change request table, the screen data having a dependency relationship with the request is identified with reference to the dependency relationship table, and the cache Screen data having a dependency relationship with the request among the screen data held by the storage means is invalidated.

  The proxy device has a parameter-related screen table that describes parameters and screen data related to the parameter, and the proxy device changes the parameter changed from the server when the parameter is changed in the server. Receiving information, referring to the parameter-related screen table, identifying screen data related to the parameter, and invalidating screen data related to the parameter among screen data held by the cache storage means It is characterized by.

  In the proxy apparatus, the proxy unit invalidates the screen data held by the cache storage unit, and then acquires the corresponding screen data from the server and causes the cache storage unit to hold the screen data.

  According to the present invention, in a proxy process for an HTTP server having a plurality of screens that are correlated with the content of the screen to be displayed, there is a page in which the modification of one display content affects the display content of the other screen Even so, the cache can be used to increase the speed.

It is a functional block diagram which shows the structure of HGW in 1st Embodiment. It is a figure which shows the example of a dependency relationship table. It is a figure which shows the example of a cache table. It is a figure which shows the example of a setting change URL table. It is a figure which shows the flow of a process of a reverse proxy when a request is received from a client. It is a functional block diagram which shows the structure of HGW in 2nd Embodiment. It is a figure which shows the example of a change parameter relevant screen table. The example of a structure of the setting screen which HGW has is shown.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings.

[First Embodiment]
FIG. 1 is a functional block diagram showing the configuration of the HGW in the first embodiment.

  The HGW 1 shown in FIG. 1 operates in the native environment 10 on the OS of the HGW 1, and includes an HTTP server 11, a reverse proxy 12, a dependency table 13, a cache table 14, a setting change URL table 15, and a virtual execution environment 20 of the HGW 1. An HTTP server 21 and a Web-GUI bundle 22 that operate in Each unit included in the HGW 1 may be configured by a computer including an arithmetic processing device, a storage device, and the like, and the processing of each unit may be executed by a program. This program is stored in a storage device included in the HGW 1, and can be recorded on a recording medium such as a magnetic disk, an optical disk, or a semiconductor memory, or provided through a network.

  The reverse proxy 12 receives a request for a setting screen request from the user from the LAN side interface, and receives a request for a remote maintenance function usage screen from the WAN side interface. If the received request is for the HTTP server 21 on the virtual execution environment 20, the following process is performed and the received request is transferred to the HTTP server 21.

  If the data requested by the received request exists in the cache table 14 and the expiration date of the data has not expired, the reverse proxy 12 acquires the corresponding data from the cache table 14 and requests the request source To the client. If the requested data does not exist in the cache table 14 or the expiration date of the data has expired, the reverse proxy 12 transmits a request to the HTTP server 21.

  In addition, when the request transmitted to the HTTP server 21 changes the parameter setting value, the reverse proxy 12 transmits the request to the HTTP server 21 and deletes the associated cache information from the cache table 14. Or invalidate as expired. Details of the reverse proxy process including the process of invalidating the cache information will be described later.

  The dependency relationship table 13 is a table describing dependency relationships between screens provided by the Web-GUI bundle 22. For example, when a value set on the screen B is displayed on the screen A, the screen A has a dependency relationship with the screen B. In the configuration shown in FIG. 9, the static NAT setting page displays the parameter setting values updated on the entry editing page, so the static NAT setting page has a dependency relationship with the entry editing page. . FIG. 2 shows an example of the dependency relationship table 13. In the example of FIG. 2, the screen displayed as index2.html has a dependency relationship with index1.html and index4.html.

  The cache table 14 sets an expiration date for the data acquired from the HTTP server 21 and holds it as cache information. FIG. 3 shows an example of the cache table 14.

  The setting change URL table 15 describes a list of URLs to be specified when changing settings for the Web-GUI bundle 22. FIG. 4 shows an example of the setting change URL table 15. The setting change URL table 15 describes the setting change URL in a regular expression, and when a request matching the regular expression is received, it is determined that the setting is changed. When the URL requested by the received request corresponds to the URL described in the setting change URL table 15, the reverse proxy 12 refers to the dependency table 13, the screen on which the setting change request has occurred, and the screen Invalidate cache information for screens that have a dependency relationship with.

  The HTTP server 21 operates on the virtual execution environment 20 and waits for a request at a port (number 8888 in FIG. 1) different from that of the HTTP server 11 operating on the native environment 10.

  The Web-GUI bundle 22 is a software module that operates on the virtual execution environment 20 that provides a setting screen for changing the setting value of the parameter of the HGW 1. By creating the Web-GUI as a software module that operates on the virtual execution environment 20, it is possible to operate even HGWs of different companies with different hardware. The setting screen is composed of a plurality of hierarchies, and parameter setting values changed in the lower hierarchy are displayed as a list of parameters in the upper hierarchy.

  Next, the operation of the reverse proxy in this embodiment will be described.

  FIG. 5 is a flowchart showing a processing flow of the reverse proxy 12 when a request is received from a client.

  When the reverse proxy 12 receives the request, the setting change URL table 15 is checked (step S11), and it is determined whether or not the URL requested by the request is a request for setting change (step S12).

  If the request is for a setting change (YES in step S12), the dependency relationship table 13 is checked, and the cache information having a dependency relationship with the requested URL is expired (step S13).

  Then, a request is transmitted to the HTTP server 21, and a response result from the HTTP server 21 is transmitted to the client (step S14).

  Further, for the cache information expired in step S13, the HTTP server 21 is accessed to acquire data, and the cache information including the expiration date is updated (step S15). At this time, if there is other cache information that has expired, the cache information may also be updated by acquiring data from the HTTP server 21 for the cache information.

  On the other hand, if it is not a request for changing the setting (NO in step S12), the cache table 14 is checked (step S16), and cache information corresponding to the requested URL exists and is within the expiration date. It is determined whether or not (step S17).

  When the cache information exists (YES in step S17), the cache information is acquired from the cache table 14 and responded to the client (step S18).

  If there is no cache information (YES in step S17), a request is transmitted to the HTTP server 21 and a response result from the HTTP server 21 is transmitted to the client (step S19).

  As described above, according to the present embodiment, the dependency table 13 that describes the dependency relationship between the screens provided by the Web-GUI bundle 22 and the setting for changing the setting for the Web-GUI bundle 22 are specified. If the URL requested by the request is described in the setting change URL table 15 when the reverse proxy 12 receives the request, the setting change URL table 15 describing the URL to be processed is stored. By disabling cache information with dependencies, screens that do not have dependencies will continue to be cache-accelerated, while screens with dependencies will be subjected to reverse proxy operation to reflect setting changes. Can be displayed.

  After invalidating the cache information of the screen having a dependency relationship with the screen whose setting has been changed, the screen data having the cache information invalidated is acquired from the HTTP server 21 and cached again, whereby the screen having the dependency relationship is obtained. Acceleration by cache can also be applied to access.

  Note that, from the viewpoint of speeding up, the reverse proxy 12 may acquire all the screens provided by the Web-GUI bundle 22 at the time of activation and hold them as cache information. However, in this case, if the internal setting of the HGW 1 changes dynamically due to an external factor (opposite server, etc.), the cache information is acquired after the setting is fixed after a certain period of time. is necessary.

[Second Embodiment]
FIG. 6 is a functional block diagram showing the configuration of the HGW in the second embodiment. The HGW 1 shown in the figure is different from the HGW of the first embodiment in that it includes a parameter change notification unit 16 and a change parameter related screen table 17 without including the dependency relationship table 13 and the setting change URL table 15. .

  The parameter change notification unit 16 notifies the reverse proxy 12 of the changed parameter information when the parameter setting value is changed via the Web-GUI bundle 22.

  The changed parameter related screen table 17 holds the parameter whose setting has been changed and related information on the screen related to the parameter. The screen related to the parameter is a screen that displays the setting value of the parameter. FIG. 7 shows an example of the change parameter related screen table 17.

  The reverse proxy 12 in the second embodiment receives the information of the changed parameter from the parameter change notification unit 16, refers to the changed parameter related screen table 17, identifies the screen related to the changed parameter, The cache information of the related screen is deleted or expired.

  Next, the operation of the reverse proxy in this embodiment will be described with reference to FIG.

  When a request for the HTTP server 21 on the virtual execution environment 20 is received from the client (step S21), the reverse proxy performs the following processing and transfers the request to the HTTP server (Java) 21.

  At that time, the reverse proxy 12 checks whether or not the cache information corresponding to the requested URL exists in the cache table 14 (step S22).

  If the cache information corresponding to the requested URL exists in the cache table 14 and is within the expiration date, the reverse proxy 21 acquires the corresponding cache information from the cache table 14 and responds to the client (step S23-1). ).

  On the other hand, if the cache information corresponding to the requested URL does not exist in the cache table 14 or has expired, the reverse proxy 21 transmits a request to the HTTP server 21 (step S23-2), from the HTTP server 21. Send the returned data to the client.

  At this time, when the setting value of the parameter is changed in the Web-GUI bundle 22, the reverse proxy 12 receives information on the changed parameter from the parameter change notification unit 16 (step S24).

  Then, the reverse proxy 12 refers to the changed parameter related screen table 17 (step S25), and expires the cache information of the screen having a dependency relationship with the changed parameter (step S26).

  Similarly to the first embodiment, for the cache information that has expired, the HTTP information is accessed by accessing the HTTP server 21 and the cache information including the expiration date is updated.

  As described above, according to the present embodiment, the parameter change notification unit 16 that notifies the reverse proxy 12 when the parameter setting value is changed, and the change parameter that holds the parameter and the screen related to the parameter. A related screen table 17 is provided, and when the reverse proxy 12 receives changed parameter information from the parameter change notification unit 16, the changed parameter related screen table 17 is referred to and the screen related to the changed parameter is specified. By disabling the cache information of the related screens, the screen is not applied to the changed parameters and the cache acceleration is still applied, while the reverse proxy operation is performed for the screens related to the changed parameters. Display a screen that reflects the changed settings It can be.

  Here, the proxy process for the HTTP server 21 operating on the HGW 1 has been described, but the present invention can also be applied to a proxy process for a general HTTP server.

1 ... HGW
DESCRIPTION OF SYMBOLS 10 ... Native environment 11 ... HTTP server 12 ... Reverse proxy 13 ... Dependency table 14 ... Cache table 15 ... Setting change URL table 16 ... Parameter change notification part 17 ... Change parameter related screen table 20 ... Virtual execution environment 21 ... HTTP server 22 ... GUI bundle

Claims (4)

A proxy device that relays communication between a server and a client terminal having screen data whose content to be displayed is changed by changing a parameter setting value,
Cache storage means for holding screen data acquired from the server;
When the request is received from the client terminal and the screen data that is the target of the request is held in the cache storage unit, the screen data is read from the cache storage unit and returned to the client terminal, and the screen data Is not held in the cache storage means, the server is requested to obtain the screen data, and when the request is a request to change a parameter setting value, the request is transmitted to the server, and Proxy means for invalidating screen data related to the parameter among screen data held by the cache storage means;
A proxy device comprising: A dependency table describing dependency relationships between screen data of the server;
A setting change request table describing a list of requests for changing the setting values of the parameters,
When the request received from the client terminal corresponds to a request described in the setting change request table, the proxy means identifies screen data having a dependency relationship with the request with reference to the dependency relationship table. 2. The proxy device according to claim 1, wherein screen data having a dependency relationship with the request among the screen data held by the cache storage unit is invalidated. It has a parameter related screen table that describes parameters and screen data related to the parameters,
When the parameter is changed in the server, the proxy device receives information on the changed parameter from the server, refers to the parameter related screen table, specifies screen data related to the parameter, 2. The proxy device according to claim 1, wherein screen data related to the parameter is invalidated among screen data held by the cache storage unit.   4. The proxy unit according to claim 1, wherein after the screen data held by the cache storage unit is invalidated, the corresponding screen data is acquired from the server and stored in the cache storage unit. A proxy device according to any one of the above.

Images