JP2010134808A - Internet access request system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To automatically perform browsing/use application to a web page to be applied from employees, determination about whether the web page is truly required on a business, and browse/use permission, most of which conventionally rely on labor by eliminating the labor as much as possible. <P>SOLUTION: Whether the requested web page is a new case is determined according to attributes such as affiliation of an applicant, it is determined that the requested web page is not permitted when it is the new case, and when the requested web page is not the new case, to what of predetermined classification the requested web page corresponds is determined, and according to the results, whether automatic determination is possible is determined. <P>COPYRIGHT: (C)2010,JPO&INPIT

Description

  The present invention relates to a technique for controlling access to a so-called web page (site). In particular, the present invention relates to a technique for efficiently performing an access application for obtaining access permission to a predetermined web page.

  Currently, companies and the like often restrict access to Web pages that are not related to business (only web pages related to business are allowed access). Here, web pages that need to be accessed (including browsing) are often changed depending on business, and therefore, accessible pages are restricted by employees or the like.

  For example, in Patent Document 1, as a conventional technique, a search is made as to whether or not a specific harmful keyword is included. If a harmful keyword is included, display of the information is prohibited and the URL of the source of the information is changed. It records and controls subsequent access ". Further, it is disclosed that “if a harmful word keyword exists, the message is refused to be posted on an electronic bulletin board system such as the Internet”.

JP 2001-282797 A

  However, when the web page accessible by the employee is changed, it cannot be determined whether the access is possible only with a specific harmful keyword. That is, it has been difficult to efficiently determine which web page is allowed to be accessed (or restricted) for each employee, business, or organization.

  Therefore, in the present invention, it is determined whether or not an access request to a prohibited web page is permitted as follows. That is, according to the attribute of the requester, it is determined whether the requested web page is a new case, it is determined that it is not allowed in the case of a new case, and if it is not a new case, it corresponds to any of the predetermined classifications It is determined whether or not automatic determination is possible according to the result.

  Here, the requested web page is specified by the URL, and the partial URL is extracted from the URL in a predetermined order, and whether or not there is a URL that is a past case that includes the URL is compared in the predetermined order. It is also included in the present invention to determine whether this is a new case.

  According to the present invention, it is possible to efficiently determine which web page is allowed to be accessed for each employee, business, or organization.

Embodiments of the present invention will be described below with reference to the drawings.
FIG. 1 shows a block diagram of an embodiment of a web browsing application processing system to which the present invention is applied. In FIG. 1, reference numerals 100 and 110 denote terminals used by the applicant A and the administrator B, and are connected to the intranet by communication lines. Reference numeral 200 denotes an AP server, which has an automatic application availability determination mechanism and an automatic application level determination mechanism. In addition, 300 is a DB server, a URL list table in which past application cases are accumulated for each URL, an application information list table in which all past application cases are accumulated, a level for determining whether automatic application is possible (hereinafter, application level) The application level determination information URL matching result table that stores the information for determining (see FIG. 2 for details of each table).

Hereinafter, the processing content of this Embodiment is demonstrated.
The automatic application processing by this Web browsing application processing system will be described according to the flowcharts of FIGS. 3-1 to 3-5. Figures 3-1 to 3-5 show that when Applicant A wants to browse an access-prohibited site, he / she can input the necessary data for the entered browsing application and can the AP server automatically process the application based on the entered data? This shows the case of determining whether or not. Figure 3-1 shows the registration of Web browsing application data, Figure 3-2 shows past case searches, and Figure 3-3 shows whether or not automatic application is possible at application levels (1) to (3) (see Figure 5, application level) Fig. 3-4 shows the decision on whether or not to apply automatically at application levels (4) to (7), and Fig. 3-5 shows the processing after the decision on whether or not to apply automatically.

First, in Step 2101, when the applicant A wants to browse the access-prohibited site, the AP server 200 blocks access. In step 2103, the applicant terminal 100 accepts input of data (applicant name, URL, department, department, purpose of use, etc.) necessary for the browsing application and makes a browsing application. Here, the applicant terminal 100 performs the above-described browsing application process by transmitting the input information to the AP server 200.
In step 21024, the AP server 200 registers the input and transmitted data (that is, application data) in the application information list table 320, and then collates the application data with the data in the URL list table 310, and automatically applies in the following procedure. Determine whether processing is possible.

  First, in step 2106, the AP server 200 searches for past cases from the URL list table 310 using the domain of the application data as a key. Next, in step 2108, when there is no past case, it is determined that automatic application processing is not possible.

  When a past case exists, in step 2110, matching is performed from the second level domain onward of the URL of the applied data and the URL of the past case, that is, the URL stored in the URL list table 310. If there is no matching domain, automatic application processing is disabled. On the other hand, if there is a matching domain, URL path names are matched from the front, separated by slashes. When the path name of the URL is considered in the directory hierarchy structure, if the URL of the application data (hereinafter referred to as the application URL) is a child directory in the URL of the past case (hereinafter referred to as the past case URL), the URL of the past case is It is said that the applied URL is included, and when the applied URL becomes a parent directory in the URL of the past case, the applied URL includes the URL of the past case (see FIG. 6).

  In step 2111, the matching result is registered in the URL matching result table 330. Searches for past case URLs that include the applied URL, past case URLs that match the application URL, or past case URLs that all match the path name, and if found, the past case (s) Record. If no URL is found, the URL of the past case included in the applied URL is searched for by matching. If found, the past case (s) is recorded and automatic application processing is disabled. If found, in step 2115, the application level of the corresponding past case is examined, and whether or not automatic application is possible is determined according to the application level. The application level is a level for determining whether or not automatic application processing is determined in advance by the system administrator. In addition, even if the URL of an inclusive past case is not found by matching, automatic application processing is disabled.

  In determining whether or not automatic application is possible, next, the corresponding past cases are collated in descending order of numerical values at the application level. The application level is a level for determining whether or not automatic application processing can be determined in advance by the system administrator (see FIG. 5, application level determination will be described later). If the level is (1), step 2118 is performed. In, automatic application processing is allowed unconditionally. If the level is (2), in step 2116, the purpose of use of the application data is matched with the purpose of use of past cases. If they match, automatic application processing is possible, and if they do not match, automatic application processing is not possible. To do. If the level is (3), in step 2117, the department in which the application data is applied and the department of the past case are matched. If they match, automatic application processing is possible, and if they do not match, automatic application processing is impossible. If the level is (4), matching of the purpose of use is performed in step 2122 and department matching is performed in step 2123.

  As a result, automatic application processing is possible if they match, and automatic application processing is not possible if they do not match. If the level is (5), the application department is matched with the department of the past case in step 2124. If they match, automatic application processing is possible, and if they do not match, automatic application processing is impossible. Use slash separators from the front. The department also considers the tree structure in the same way as the URL, and searches for past cases that include the applied department name or past cases that all match the department name by matching. If not found, automatic application processing is disabled. If the level is (6), use purpose matching is performed in step 2120, and department matching is performed in step 2121. If they match, automatic application processing is possible, and if they do not match, automatic application processing is not possible. If the level is (7), in step 2129, automatic application processing is unconditionally impossible.

  Automatic application processing is possible if there is a department name of a past case that matches the purpose of use and includes the applied department name, or matches all of the applied department names, otherwise automatic application processing is not possible . This operation is repeated for the corresponding past cases, and ends when automatic application processing becomes possible.

  After determining whether automatic application processing is possible, the result is registered in the application information list table 320 in step 2130.

  Next, application level determination by the Web browsing application processing system will be described with reference to the flowcharts of FIGS. Figures 4-1 to 4-2 are based on past case data recorded by matching the application data entered with the pathname of the URL for the application for which the administrator B terminal 110 is disabled for automatic application processing. This shows a case where the AP server 200 presents the application level that can be selected by the AP server to the administrator B to determine whether the application level is appropriate when it is desired to determine the determined application level.

  If the administrator B terminal 110 wants to determine the application level, in step 2201, it requests a URL whose application level is not yet determined. In step 2202, the AP server 200 searches the application information list table 320 for application data for which automatic application processing is disabled. In step 2205, the administrator B terminal 110 selects and requests one target URL from the list, and the application data AP server 200 searches the URL matching result table 330 for past cases in step 2206. From the URL list table, the past case data with the best URL path name is retrieved, and in step 2209, the administrator B terminal 110 determines the application level based on the information. At that time, the AP server 200 presents and determines application levels that can be selected as to whether the level determined by the administrator B terminal 110 is appropriate in the following procedure.

  In the case where the URL of the past case includes the applied URL, in step 2211, it is determined to be appropriate when a level lower than the application level of the past case is determined, and otherwise determined to be inappropriate. Can be selected for application data. Next, if all of the submitted URLs match the URLs of past cases, if it is possible to view and not to be mixed in step 2213, it is determined to be appropriate when the application level (3) or higher is determined. Otherwise, it is determined to be inappropriate. Can be selected, otherwise any application level can be selected. If the submitted URL includes the URL of the past case, in step 2212 it is judged appropriate if the application data is judged to be higher than the past case application level, otherwise it is judged inappropriate. To do. Can be selected. In other cases where there is no inclusive relationship between the submitted URL and the URL of the past case, in Step 2211 it is judged appropriate if any application level is judged, otherwise it is judged inappropriate Can be selected. If it is determined to be inappropriate, the administrator B terminal 110 is made to perform the determination of the application level again. If it is determined to be appropriate, the AP server 200 registers the application level in the URL list table 310 in step 2214.

  The selection of an appropriate level from the selectable application levels from the administrator B is accepted, and application data is registered in the URL list table according to the accepted contents.

  Although the embodiment of the present invention has been described above, in FIG. 1, it is possible to consider the position of the applicant in addition to the department / department / purpose of use as a determination material for determining whether automatic application is possible.

The block diagram of the web browsing application processing system in one Embodiment of this invention. The figure which shows the various data tables used by one Embodiment of this invention. The flowchart (the 1) of the automatic application processing by a Web browsing application processing system. Flowchart (2) of automatic application processing by the Web browsing application processing system. Flow chart of automatic application processing by the web browsing application processing system (part 3). The flowchart (the 4) of the automatic application processing by a Web browsing application processing system. Flow chart of automatic application processing by the web browsing application processing system (part 5). The flowchart (the 1) of the determination process of the application level by a web browsing application processing system. Flow chart (part 2) of application level determination processing by the web browsing application processing system. The figure which shows the reference | standard table used for determination of whether automatic application is possible. The figure which shows whether applied URL includes URL of past example.

Explanation of symbols

100 ... Applicant A terminal, 110 ... Administrator B terminal, 200 ... AP server, 300 ... DB server

Claims (2)

In an Internet access request system comprising a user terminal of a user and a server connected to the user terminal and controlling access to the Internet of the user terminal,
Sending web page identification information for identifying the user's attributes and the web page requesting the use from the user terminal to the server;
The server stores, in a storage device, web page identification information of a web page that allows access for each user attribute,
In the server, it is determined whether the received web page identification information is stored in the storage device corresponding to the received attribute;
If it is determined that the request is not stored, the server determines that the request is not permitted,
When it is determined that the request is stored, the server can identify which of the classifications the request corresponds to in advance, and can automatically determine the request according to the specified classification An Internet access request system characterized by determining whether or not. The Internet access request system according to claim 1,
The web page identification information is a URL,
The server
An Internet access request system which extracts partial URLs from a transmitted URL in a predetermined order and determines whether the extracted partial URLs are stored in the storage device by comparing in the predetermined order .

Images