JP2001290773A - Network type system for providing service - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a simple system for suppressing service use by an illegal user in service providing through a communication network. SOLUTION: A service providing server generates a password, stores them relating the password to a user ID (1201), generates an initial message including the user ID and the password (1202), transmits the initial message to a user client 301 (1203), receives a message including the user ID and the password from the client 301 (1204), collates the received password with the stored password (1205), generates a new password, stores them relating the new password to the user ID when the passwords coincide with each other (1206), generates and transmits a message including the user ID and the password (1207 and 1208) and repeats the process from a step (1204) in which the message is received. Thus, the service use of the illegal user resulting from opening a password, etc., to the illegal user by a legal user is suppressed.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to providing services on a communication network, and more particularly to a system for safely providing a user with a plurality of paid services on an open communication network.

[0002]

2. Description of the Related Art In recent years, with the spread of the Internet, a plurality of systems for providing a user with paid services a plurality of times via a communication network have been developed. here,
Specifically, multiple paid services include services that allow users to freely browse digital content (Web pages on the Internet, etc.) for a predetermined period of time (for example, 24 hours) or use an online dictionary for a predetermined number of times Refers to services that can be enabled.

Conventionally, as a system for providing the service, a service providing server generates a random number and sends the random number to a user client of a legitimate user (a user who has been recognized as a legitimate recipient of a paid service by paying a price or the like). There has been a system in which a random number is transmitted as a password, and the user client transmits the password to the service providing server every time a service is requested. Hereinafter, this system is referred to as a simple password system. In the simple password system, a service providing server authenticates a password, and transmits service information (for example, digital content or an online dictionary search result) to a user client when the authentication is successful.

As another system for providing the service, Japanese Patent Application Laid-Open No. H11-149502 is known. Hereinafter, this system is referred to as a member authentication system. In the member authentication system, a user (member) who has registered user registration information (credit number, password, etc.) in the member management server in advance inputs member information (password, etc.) from a terminal (user client), and the entered member information is , Only the member management server is transmitted to the member management server via a providing server that provides encrypted content in a form that can be decrypted, and the member management server authenticates the member. Send paid content to the user client.

[0005] As another system for providing the service, a service providing server transmits a random number to a user client, and the user client uses the secret key in a public key cryptosystem to store the random number and service request related information (request). A service code for specifying the service), and transmits the encrypted data to the service providing server. The service providing server decrypts the received data with the private key and the corresponding public key,
There has been a system that compares a transmitted random number with a combined random number, and if they match, the user client is considered to be legitimate and transmits service information. Hereinafter, this system is referred to as a challenge response authentication system.

[0006]

However, the above-mentioned prior art has the following problems.

[0007] (1) In the case of the simple password system, there is a problem that a legitimate user discloses user authentication information to an unauthorized user, whereby an unauthorized user can use a service. Here, the improper user refers to a user who has not executed a necessary process, such as payment, to be recognized as a legitimate payee of the paid service. The user authentication information is included in a service request message transmitted by the user client to the service providing server to use the service, and the service providing server verifies the service request message to determine that the sender of the service request message is a valid user. Data. In the case of a simple password system, the user authentication information is a password.

(2) In the case of the member authentication system, there is a problem that it cannot be applied to a type of service in which billing is not performed after the service is used. In this system, a legitimate user is charged when a service is used, thereby preventing the disclosure of user authentication information (ID and password in this system) from a legitimate user to an unauthorized user. If the charging at the time of using the service or the charging after using the service is not executed in the member authentication system, there is a possibility that the user authentication information is disclosed to an unauthorized user as in the simple password system. This is because, even if the legitimate user discloses the user authentication information to the unauthorized user, the legitimate user can continue to use the service and does not charge. In addition, as an example of a type of service that does not execute charging when using the service, after payment for the service,
There are services that allow you to freely browse web pages and use online dictionaries only within a predetermined time or number of times.

(3) In the challenge-response authentication system, there is a problem in a means for encrypting random numbers and a system for distributing secret key data used for encryption to user clients. When a user client downloads the encryption means and the secret key data via a communication network and installs the encryption means and the secret key data on the user client, communication costs for the download are incurred. In addition, when a user operates a program such as a user client to execute download or installation, an operation cost is incurred on the user side.

The present invention has been made in view of the above circumstances, and has as its object to realize a service providing system satisfying the following requirements.

(1) Even in a type of service in which charging is not performed after use of a service, a legitimate user discloses user authentication information to an unauthorized user, thereby preventing an unauthorized user from using the service. .

(2) Encryption / decryption means other than the means for encrypting and decrypting the entire message transmitted / received between the user client and the service providing server (means for encrypting only specific data in the message and means for adding a signature) Is unnecessary.

[0013]

Means for achieving the above object will be described below with reference to FIGS. 1 and 2.

A first invention is a service providing system in a service providing server, wherein the service providing system includes the following steps.

A password is generated, and the password is stored in association with the user ID (step 1201).
And an initial message including the password is generated (step 1202), and the initial message is transmitted to the user client 301.
(Step 1203), a message including the user ID and the password is received from the user client 301 (step 1204), and the received password is compared with the stored password (step 1205). A password is generated, stored in association with the user ID (step 1206), a message including the user ID and the password is generated (step 1207), transmitted to the user client (step 1208), and the user ID and the password are stored. Repeat from the step of receiving the message including the message from the user client (step 1204).

If the passwords do not match in step 1205, a message for notifying the user that the passwords did not match is generated and transmitted to the user client (step 1209). finish.

According to a second aspect of the present invention, there is provided a service providing system in a service providing server, wherein the service providing system includes the following steps.

A password is generated, and the password is stored in association with the user ID (step 1201).
And a message including the password is generated (step 12).
02) and send it to the user client (step 1203),
A message including the user ID and the password is received from the user client (Step 1204), and the received password is compared with the stored password (Step 2101).
Retrieve the saved message in 2103 (step 21
04) In step 1208, the obtained message is transmitted to the user client. If the obtained message matches the password stored last time (step 1205), a new password is generated and the password is stored in association with the user ID (step 2102). A message including the user ID and the password is generated (step 1207), the generated message is stored in association with the user ID (step 2103), and transmitted to the user client (step 1208). The process is repeated from the step of receiving the message including the password from the user client (step 1204).

If the password collation does not match in step 1205, a message for notifying the user that the password collation did not match is generated and transmitted to the user client (step 1209). finish.

[0020]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS A first embodiment of the present invention will be described below with reference to FIGS.

FIG. 3 is a system configuration diagram of a service providing system according to the present invention, comprising a user client 301, a communication network 302, a service providing server 303, and a user information storage unit 304. The figure shows the user client
Although only one each of the 301 and the service providing server 303 is drawn, a plurality of each may be actually provided. FIG. 4 is a flowchart illustrating a procedure of a service providing process performed by the user client 301 and the service providing server 303. FIG. 5 is a configuration example of a user information file held in the user information storage unit 304. FIG. 6 is an example of a screen display on the user client 301.

In FIG. 3, the user client 301
Is an information processing apparatus that transmits a service information request to the user providing server 303, receives service information, and uses the received service information. Specifically, such information processing apparatuses include a workstation (WS), a personal computer (PC), a personal digital assistant (PDA), and a mobile phone. The service information received by the user client 301 is, for example, a Web page or image information in the case of a digital content browsing service, and translation result information in the case of a dictionary search service.

The communication network 302 is a line for transmitting and receiving messages (telegrams) between the user client 301 and the service providing server 303. Examples of such communication networks include the Internet, VAN (Value Add
ed Network), WAN (Wide Area Network), and public telephone line network. When transmitting and receiving a message in the communication network 302, it is desirable to encrypt the entire message in order to prevent information leakage to a third party.

The service providing server 303 is an information processing apparatus that receives a request for service information from the user client 301, determines whether or not the service can be provided, and transmits the service information when the service can be provided. Specifically, such information processing devices include a WS, a PC, and a host computer.

[0038] The user information storage unit 304 is a storage unit that holds information related to users handled by the service providing server 303. Specifically, examples of the storage unit that realizes such a function include a database system and a file system.

Next, based on FIGS. 4 and 5, the user client 301 and the service providing server 303 in FIG.
Will be described. In the present embodiment, it is assumed that the server-side service code 5103 and the client-side service code are already stored in the service providing server 303. The contents of the server-side service code 5103 and the client-side service code will be described later.

In step 42011, the service providing server 303 adds a record of the user information file 51 held in the user information storage unit 304. Specifically, a random number is generated, and the value is used as the server-side user ID 5101.
In 42053, service end data 5104 which is a reference value for determining the end of service provision is generated, and a set of the server side user ID 5101, the service end data 5104, and the server side service code 5103 held by the service providing server 303 is generated. Information file as a record
Newly added to 51.

Here, the server-side user ID 5101 includes:
Instead of using random numbers, they may be obtained from an external device. However, when a random number is used, there is an advantage that user anonymity can be realized. In other words, information such as the name and address of the user who operates the user client 301 can be hidden from the operator of the service providing server 303. In the service end data 5104, the current date and time of the service providing server 303 is set when the elapse of a predetermined time from the start of the service is set as a condition for service end. When permitting the user client 301 to use the service a predetermined number of times, a numerical value “0” or a numerical value of the predetermined number is set. In the present embodiment, the current date and time are set as service end data 5104. The server side service code 5103 is the user client 301
Is a code for identifying a service permitted to be provided by the service providing server 303 to the service. For example, when implementing an English-Japanese dictionary search service, the code "etoj" is used. In the code, "etoj" indicates that the use of the English-Japanese dictionary search service is permitted.

Next, a password is generated and stored in the record of the user information file 51 as the server-side password 5102 (step 42012). The record of the storage destination is the record added in step 42011. As a password generation system, for example, a random number is generated and its value is converted into a character code to be used as a password. The value “ehfhdc” of the server-side password 5102 shown in the first record in the user information file 51 shown in FIG. 5 is an example in which the generated random number is converted into a character code.

Next, service information to be provided to the user client 301 is generated based on the client-side service code (step 42013). Here, the client-side service code is a code for specifying service information to be generated. For example, when implementing an English-Japanese dictionary search service, a code “etoj_have” is used. In the code, "etoj" indicates that the English-Japanese dictionary search service is used, and "have" indicates a word desired to be translated. In this case, “have”, which is a translation result of “have”, is generated as service information. Note that the service information may not be generated by the service providing server 303, but may be generated by an external device and acquired by the service providing server 303.

Next, the service providing server 303 generates a service response message including the server-side user ID 5101, the server-side password 5102, and the generated service information (step 4202), and transmits it to the user client 301. (Step 4203).

The user client 301 receives the service response message (step 4101), and determines whether it is an error message (step 4102). The error message will be described later. If the message is not an error message, the service information included in the service response message is used. For example, in the case of a dictionary search service, step
The service information “has” generated in 42013 is displayed on the screen of the user client 301.

Next, the user client 301 determines the end of the service (step 4104). As a service end determination system, for example, the user client 301 inquires of the user whether or not to end. When the user instructs end, the end is determined. When the user instructs continuation, the end is determined not to end. If it is determined to end, the process ends.

If it is determined in step 4104 that the process is not to be terminated, the user client 301 generates a service request message (step 4105). The service request message includes a client-side user ID, a client-side password, and a client-side service code. The client-side user ID and the client-side password include the server-side user ID 5101 and the server-side password included in the received service response message.
Set 5102 respectively. In the client side service code, a code for specifying a service requested by the user is set. For example, in the case of an English-Japanese dictionary search service, a user is requested to input an English word (such as “run”) desired to be searched, and the value “etoj_run” obtained by concatenating the input value and the value of “etoj” is used as the client-side service code. .

After generating the service request message, the user client 301 sends the service request message to the service providing server 303 (step 4106).

The service providing server 303 transmits the service request message transmitted by the user client
Receive the password at 204 and verify the password (step 4
2051). The password verification comprises the following steps. The client-side user ID is acquired from the received service request message, the server-side user ID 5101 that matches the client-side user ID is searched from the user information file 51, and a record including the matched server-side user ID 5101 is acquired (hereinafter, referred to as “record”). The acquired record is referred to as a current record). Further, the server-side password 5102 included in the current record is obtained, and it is determined whether the client-side password in the service request message matches the server-side password 5102. If the two passwords match, step 42052 is executed. If the two passwords do not match, or if the server-side user ID 5101 that matches the client-side user ID does not exist in the user information file 51, step 4209 is executed.

At step 42052, the user client 3
It determines whether or not the service requested by 01 can be provided. This determination is made by comparing the client-side service code included in the service request message with the server-side service code 5103 included in the current record. For example, the client side service code is “etoj_run”,
When the server side service code 5103 is “etoj”, “
Since the client-side service code before “_” matches the server-side service code 5103, it is determined that provision is possible. If the client-side service code is “jtoe_run”, it is determined that provision is not possible. If it is determined that the service can be provided, step 42053 is performed. If it is determined that the service cannot be provided, step 4209 is performed.

In step 42053, the end of the service is determined based on the value of the service end data 5104 in the current record. The value of the service end data 5104 in the current record (step 42011 in this embodiment)
And the difference between the current date and time in the service providing server 303 is calculated (for example, the current date and time is "01-13-2000 22:14" and the service providing start date and time is "01-13"). For -2000 00:00 ”, the difference is“
00-00-0000 22:14 "), if the difference value exceeds a predetermined time (for example, 24:00), it is determined to end. If it is shorter than the predetermined time, it is determined to continue. Performs step 4209.

In the case of continuation, the processing is repeated from step 42012. However, the storage destination record of the password generated in step 42012 is the current record.

In step 4209, the service providing server 303 generates an error message and transmits it to the user client 301. The error message includes an error code indicating an error type. The error type is an unknown user ID (when it is determined in step 42051 that the server-side user ID 5101 that matches the client-side user ID does not exist in the user information file 51), and when the password does not match (when it is determined in step 42051 that the password does not match). , Service cannot be provided (step 4205
2) (when it is determined that the service cannot be provided) and service termination (when it is determined that the service is terminated in step 42053).

In step 4101, when the error message is received and in step 4102 it is determined that the message is an error message, the user client 301
Execute In step 4107, an error screen corresponding to the error code is displayed. For example, if the error code indicates a password mismatch, the service request rejection screen
Display 601. When the service end is indicated, a use time excess screen 602 is displayed.

According to the above-described embodiment, the legitimate user discloses the user authentication information (the client-side user ID and the client-side password) to the unauthorized user, thereby enabling the unauthorized user to use the service. Can be suppressed. The reason is shown below.

In step 4101, the user client 301 possessed by the legitimate user
Receiving a service response message containing D = cuid and client-side password = cpw-a,
And cpw-a are disclosed. An unauthorized user operates a user client different from the user client 301 and uses the cuid and cpw-a to provide a service providing server.
It is possible to use the services provided by 303.
However, in step 42012 the server-side password 510
Since 2 is updated, if an unauthorized user uses the service, an authorized user cannot use the service newly. To avoid this disadvantage, a legitimate user will keep the client-side user ID and client-side password confidential to a third party.

As described above, in this embodiment, means for encrypting only specific data in a message and means for adding a signature are unnecessary.

Next, a second embodiment of the present invention will be described.

The second embodiment is an embodiment in which retransmission of a service request message accompanying non-arrival of a message is considered.
In the case of the first embodiment, the service response message transmitted by the service providing server 303 in step 4203 does not arrive at the user client 301, and the service request message transmitted in step 4106 is
If 301 is retransmitted, step 42051 is performed because the server-side password 5102 has been updated in step 42012.
It is determined that the passwords do not match. That is, there is a problem that the service request is rejected. The second embodiment aims at solving this problem.

The system configuration in the second embodiment (FIG. 3) and the example of the screen display in the user client 301 (FIG. 6) are the same as those in the first embodiment. Hereinafter, operations of the user client 301 and the service providing server 303 that are different from those of the first embodiment will be described with reference to FIGS. 7 and 8.

Steps 42011 to 4202 are the same as in the first embodiment. However, the information is stored not in the user information file 51 but in the user information file 81. In addition,
Not limited to the above steps, the user information file handled by the service providing server 303 in this embodiment is not 51 but 81
It is.

The service response message generated in step 4202 is stored by the service providing server 303 as a previous transmission message 8102 (step 7201). The storage destination record is a record in which the server-side user ID 5101 generated or obtained in step 42011 is stored. The previous transmission message 8102 is stored in step 72 described later.
Used in 04.

Step 4203 and steps 4101 to 4107 are the same as in the first embodiment.

The service providing server 303 determines in step 4204
After receiving the service request message in step, execute step 7202. In step 7202, it is determined whether the received message is a retransmission request message. First, a client-side user ID is acquired from the received message, a server-side user ID 5101 that matches the client-side user ID is searched from the user information file 81, and a record including the matched server-side user ID 5101 is acquired (hereinafter, referred to as a record). The acquired record is referred to as a current record). Next, the server-side previous password 81 included in the current record
01 is obtained, and it is determined whether the password on the client side in the received message matches the previous password 8101 on the server side. If the two passwords match, step 7204 is executed. If the two passwords do not match, or if the server-side user ID 5101 that matches the client-side user ID does not exist in the user information file 81, step 42051 is executed.

In step 7204, the previous transmission message 8102 included in the current record is obtained. After that, in step 4203, the acquisition message is transmitted to the user client 301.

Steps 42051 to 42053 and step 4209 are the same as in the first embodiment. However, if it is determined in step 42053 that the service is to be continued, the service providing server 303 executes step 7203. Step 7
In 203, the service providing server 303 overwrites the value of the server-side previous password 8101 in the current record with the value of the server-side password 5102 in the current record. Thereafter, the processing is repeated from step 42012.
The storage destination record of the password generated in step 42012 is set as the current record, as in the first embodiment.

According to the present embodiment described above, in addition to the effects of the first embodiment, it is possible to cope with a retransmission request accompanying a non-arrival of a service response message. Step 4203
In the case where the service response message transmitted by the service providing server 303 does not reach the user client 301 and the user client 301 retransmits the service request message transmitted in step 4106, the service providing server 303 Is received, the retransmission is determined in step 7202, the previous transmission message is obtained in step 7204, and the obtained message is transmitted to the user client 301 in step 4203.

[0055]

According to the present invention, as described above, even in the case of providing a type of service in which billing is not performed after the use of a service, a legitimate user can disclose user authentication information to an unauthorized user, As a result, it is possible to prevent an unauthorized user from using the service, and there is no need to encrypt only specific data in the message or add a signature, and the user can use the service anonymously. .

[Brief description of the drawings]

FIG. 1 is a flowchart showing a procedure of a service providing process according to the first invention.

FIG. 2 is a flowchart showing a procedure of a service providing process in the second invention.

FIG. 3 is a system configuration diagram of a service providing system including a user client, a communication network, a service providing server, and a user information storage unit.

FIG. 4 is a flowchart illustrating a procedure of a service providing process according to the first embodiment.

FIG. 5 is a diagram illustrating an example of a user information file according to the first embodiment.

FIG. 6 is a diagram showing a screen display example in a user client.

FIG. 7 is a flowchart illustrating a procedure of a service providing process according to the second embodiment.

FIG. 8 is a diagram illustrating an example of a user information file according to the second embodiment.

[Explanation of symbols]

301: User client, 1201: Password generation and update step, 1202: Initial message generation step, 1303: Initial message transmission step, 1
204: service request message receiving step, 120
5: Password collation step, 1206: Password generation and update step, 1207: Service response message generation step, 1208: Service response message transmission step, 1209: Error message generation and transmission step.

Claims (2)

[Claims] 1. A service providing system in a service providing server comprising a service providing server for providing a service via a network and a user client using the provided service, the service providing system comprising: It is characterized by including the following steps. Generate a password, store the password in association with the user ID, send a message including the user ID and the password to the user client, receive a message including the user ID and the password from the user client, and receive the received password. If the passwords match, a new password is generated, the password is stored in association with the user ID, a message including the user ID and the password is transmitted to the user client, Repeat from receiving the message containing the ID and password from the user client. 2. A service providing system in a service providing server comprising a service providing server for providing a service via a network and a user client using the provided service, wherein the service providing system comprises: It is characterized by including the following steps. Generate a password, store the password in association with the user ID, send a message including the user ID and the password to the user client, receive a message including the user ID and the password from the user client, and receive the received password. If the password matches the password stored two times before, the previously transmitted message is sent again.If the password matches the password stored last time, a new password is generated and the password is set as the user ID. The message including the user ID and the password is transmitted to the user client, and the message including the user ID and the password is received from the user client.