JPH08320846A - Interactive management type information providing method and device therefor - Google Patents

Abstract

PURPOSE: To enable high-level access control for WWW communication services intended for an unspecified number of users. CONSTITUTION: A client-side computer 101 and a server-side computer 102 are connected by a network, 103. The computer 101 issues an information acquisition request to the computer 102 according to a URL from a user and the 102 sends information in the information storage part 203 shown with the URL of the request to the 101. The service control part 401 of the 102 generates an interaction ID in the initial stage of access from the user, registers it in an interaction storage part 405, and provides information obtained by adding the interaction ID to the URL required for next access for the user. The interaction ID is taken over by the URL of the information acquisition request issued by the 101 and the 401 checks the interaction ID sent from the 101 to perform the access control.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an interactive management type information providing method and apparatus, and more particularly, to access control of a communication service for providing hypertext to a user on a computer network.

[0002]

2. Description of the Related Art Conventionally, WWW (World Wide Web) has been known as a communication service for providing a user with hypertext on a computer network, and as a method therefor, HTTP (Hyper Text Tr) is used.
ansfer Protocol). This method provides services to an unspecified number of users. Conventionally, the protocol and IP address in the information acquisition request are issued only when the information acquisition request is made for a series of operations on the user's hypertext. URL (Uniform Resource) that sets (server address), port number, information to be acquired, etc.
The information is acquired by connecting to the service provider specified by Locator).

[0003]

The HTTP in the conventional WWW is intended for communication services to an unspecified number of users. The same user is identified from a series of information acquisition requests and the operation history is stored for each user. However, there is a drawback that information cannot be protected by access history.

An object of the present invention is to eliminate the above-mentioned drawbacks of the prior art, to identify the same user, record a series of accesses, and check a predetermined access, and to provide a communication service for an unspecified number of users. It is an object of the present invention to provide an interactive management type information providing method and device that enables advanced access control.

[0005]

In the present invention, the most important thing is to add an identifier for identifying a series of information acquisition requests from the same user to a URL used in HTTP in WWW, and manage this with a server. Characterize.

[0006]

In the present invention, a series of accesses is called a dialogue, and in the initial stage of access from the user, the server generates an identifier (conversation ID) for the dialogue, and the dialogue is stored in the URL required for the next access. The hypertext to which the ID is added is provided to the user. The client is
When the user clicks a predetermined character on the transferred hypertext, the user accesses the server by the URL with the dialogue ID. The server analyzes the conversation ID in the URL transmitted from the client, identifies the same user, records a series of accesses, and checks a predetermined access. As a result, it becomes possible to perform sophisticated access control in a communication service for an unspecified large number of users.

[0007]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS An embodiment of the present invention will be described below with reference to the drawings.

FIG. 1 shows an embodiment of a computer network to which the present invention is applied. In the figure, 101 is a computer used by a user who receives a service (client-side computer), 102 is a computer for providing a service (server-side computer), and 103 is a network for providing a communication service between them. Is. Here, 101 is WWW
Is a computer on which various application software of the client is running, and 102 is a computer in which various daemon programs for providing WWW services and information for providing are accumulated.
The computers 101 and 102 are connected by a network 103. Note that, in reality, a plurality of computers 101 are connected to the computer 102 via the network 103.

FIG. 2 shows the mechanism of a conventional WWW system configuration. Inside the client side computer 101, 201 is various clients for receiving WWW service provision, and 202 is various operating systems for controlling the computer 101. On the other hand, reference numeral 203 denotes a storage unit for storing information (hypertext or the like) to be provided to the user by the server-side computer 102 in the WWW service, and 204 denotes WWW.
Various servers that provide services and 205 are various operating systems for controlling the computer 102.

FIG. 3 shows an example of a service providing sequence of a conventional WWW server. The client 201 issues an information acquisition request to the WWW server 204 on the network 103 according to the URL from the user input from the input device of the computer 101. Upon receiving the information acquisition request, the WWW server 204 reads the information in the information storage unit 203 indicated by the URL, and the client 2
Return to 01. The WWW server 204 returns information in the same procedure even when the same user issues information acquisition requests multiple times.

FIG. 4 shows the mechanism of the system configuration of the WWW of the present invention. In the figure, the conventional system configuration of FIG. 2 is, in the server computer 102, a service control unit (WWW server) 401 that provides a service, a common control unit 402, and a dialogue for identifying a series of dialogues. The difference is that it has an identification unit 403, a dialogue control unit 404 that controls information provision according to a series of dialogues, and that a dialogue storage unit (DB) 405 that records the history of dialogues is added.

FIG. 5 is a flowchart showing the operation of the service control unit (server) 401 in FIG. 4, and the portions surrounded by broken lines are the dialogue identification unit 403 and the dialogue control unit 404.
Other operations are operations of the common control unit 402.

In step 501, the server starts accepting a request from the client, in step 502, acquires an information acquisition request from the client, and in step 503, the U set in the information acquisition request.
According to the RL, it is determined whether it is the first information acquisition request or the second or later specific information acquisition request. Then, step 503
If the first information acquisition request is determined in step 5, step 5
In 04, the initial screen for issuing the URL of the information acquisition request with ID acquisition request is returned to the client.

On the other hand, when it is determined in step 503 that the second and subsequent acquisition requests for specific information have been made, step 505
At, it is determined whether the URL is an information acquisition request with an ID acquisition request. Here, when the URL indicates an information acquisition request with an ID acquisition request, a dialog ID is generated in step 506, the dialog ID is registered in the dialog storage unit (DB) 405 in step 507, and the request ID is registered in step 508. The dialog is added to the URL in the existing information, and the information (hypertext or the like) to which the dialog ID is added is returned to the client in step 509. This dialogue ID
Is inherited by the URL of the subsequent information acquisition request.

When the information acquisition request from the client is neither the first access nor the ID acquisition request, the conversation ID associated with the URL is extracted in step 510. Then, if the dialogue ID is added to the URL, the dialogue storage unit (DB) 40 in step 511.
5 is checked to see if the conversation ID is recorded, and the conversation ID is stored in the conversation storage unit (DB) 405.
In step 512, the information acquisition request access is recorded in the dialogue storage unit (DB) 405 (512 is optional), and in step 513, the dialogue ID is added to the URL in the information to be returned to the client. In step 514, the information storage unit 203 is accessed and the information (hypertext or the like) to which the conversation ID is added is returned to the client. Also, step 5
If the conversation ID cannot be extracted in step 10, it is regarded as an unauthorized access that did not access the initial screen, and access is denied in step 515. Further, when it is determined in step 511 that the conversation ID is not recorded in the conversation storage unit (DB) 405, it is regarded as a forgery of the conversation ID, and step 5 is also performed.
Access is denied at 15.

FIG. 6 shows an example of a sequence between the client and the server in the present invention. First (first time), the client issues an information acquisition request to the server according to the URL from the user. This is the same as the conventional one. The server responds to this initial information acquisition request
The information storage unit 203 is accessed, and the initial screen for issuing the URL of the information acquisition request with ID acquisition request is returned to the client. In response to this, next (second time), the client issues an information acquisition request for the URL with the ID acquisition request to the server. When the server determines the information acquisition request with an ID acquisition request, it generates a dialogue ID, registers it in the dialogue storage unit 405, adds the dialogue ID to the URL in the requested information, and returns it to the client. To do. After that, the client adds the conversation ID to the URL and issues various information acquisition requests to the server. The server checks the dialogue ID associated with this URL by referring to the dialogue storage unit 405, and if correct, accesses the information storage unit 203 to determine the UR.
The conversation ID is added to L and the information is returned to the client. On the other hand, the server checks the conversation ID attached to the URL of the information acquisition request from the client,
Is not extracted, or the corresponding conversation ID is the conversation storage memory 405.
If it is not registered in, send an error message to the client.

FIG. 7 shows the information acquisition request U in the present invention.
3 shows a specific example of RL. In FIG. 7, the URL for the first access is the same as the conventional one. In this example, at the second access, "check" is added to this URL.
Is added to indicate that the request is an ID acquisition request. The server is
This check is discriminated to generate a dialogue ID, which is registered in the dialogue storage unit and returned to the client. In the third and subsequent accesses, this dialogue ID is inherited by the URL.

[0018]

As described above, in the conventional WWW, since the service is provided to the access from an unspecified large number, the access from the same user cannot be identified in the series of access. In the present invention, a dialogue identifier is issued in the initial stage of access, and access is performed by the URL address system to which the identifier is added to identify the same user, record a series of accesses, and check a predetermined access. This makes it possible to perform sophisticated access control in communication services targeting an unspecified number of users.

[Brief description of drawings]

FIG. 1 is a schematic block diagram of a system configuration to which the present invention is applied.

FIG. 2 is an example of a system configuration for providing a conventional WWW service.

FIG. 3 is an example of a sequence in a conventional WWW service server and client.

FIG. 4 is an example of a system configuration for providing a WWW service of the present invention.

5 is an example of an operation flowchart in the service control unit of FIG.

FIG. 6 is an example of a sequence in the server and the client in the present invention.

FIG. 7 is an example of transition in each access of URL according to the present invention.

[Explanation of symbols]

 101 client side computer 102 server side computer 103 network 201 WWW client 202 operating system 203 information storage unit 205 WWW server 205 operating system 401 service control unit 402 common control unit 403 dialogue identifying unit 404 dialogue control unit 405 dialogue storage unit

Claims (2)

[Claims] 1. A server computer having a World Wide Web for providing information is connected to a client computer via a computer network to form a HyperText Trans.
In the method of providing information by fer Protocol, when the information acquisition request is received from the client side, it is determined whether it is the first information acquisition request or the second or subsequent information acquisition request. In the case of the first information acquisition request, the ID An initial screen for issuing a Uniform Resource Locator (hereinafter abbreviated as URL) of an information acquisition request with an acquisition request is returned to the client side, and at the time of the second or subsequent information acquisition request, if there is an ID acquisition request, the conversation ID Is generated, the dialogue ID is registered in the dialogue storage unit, the dialogue ID is added to the URL in the information of the acquisition request, the information is sent to the client side, and the information acquisition request is not the ID acquisition request. , If the dialogue ID is added to the URL, it is checked whether the dialogue ID is recorded in the dialogue storage unit, and if it is recorded, the access is recorded, and the URL in the information to be transmitted. The pair talk ID
Is added, the information is sent to the client side, and the URL
A dialogue management type information providing method characterized by performing access denial when the dialogue ID is not added to or the corresponding dialogue ID is not recorded in the dialogue storage unit. 2. An information providing apparatus for providing World Wide Web Information to a client computer connected by a computer network by Hyper Text Transfer Protocol, and an interactive identification means for identifying a series of accesses from the same user, and an identical user. A dialogue management type information providing apparatus, comprising: a dialogue storing means for storing the access history of the user; and a dialogue control means for controlling information provision according to the access history.