JP2001034520A - Device and method for sharing information stored in database - Google Patents

Abstract

PROBLEM TO BE SOLVED: To obtain a device and method which allow each user to optionally set a group and authenticate the members of the group by the identity of a code and mutually authentication by the members when arbitrary users share stored information of a database. SOLUTION: Each user sends a request to retrieve, add, modify, or delete information characteristic of the user to the database 10. A database device 1 confirms that a user ID and a password that the user sends through a terminal 2 coincide with information stored in a user information table 11 and then authenticates the user as a regular user when the confirmation is successful.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a database storage information sharing apparatus in which, when sharing information stored in a database between arbitrary users, a group for sharing data is arbitrarily set by each user and members authenticate each other. About the method.

[0002]

2. Description of the Related Art An example of a conventional system for sharing information stored in a database between arbitrary users is disclosed in Japanese Patent Application Laid-Open No. 10-2891.
No. 43 is described. The database information input, search processing method and stored information sharing method described in this publication include a database unit, a user identification code data table for authenticating a user identification code, an information identification number issuing device, A data conversion device, a character data encoding device that associates actual data, symbols, and symbols, an information identification number area, a group authentication code table that performs authentication of a group identification code, and actual data and symbols are associated with each other. An item data table, a user information address table in which actual user information is associated with a user identification number, and a search condition symbolizing device are provided.

Conventionally, as described above, a group identification code has been used as a means for sharing information stored in a database between arbitrary users.

[0004]

However, using a group identification code involves issuing a group identification code,
Since the work of registering the group identification code together with the user identification code and the user identification number in the user dedicated terminal has to be performed, it may take time. In addition, since the search for the stored information between the groups can be performed only by the authentication of the group identification code, the confidentiality of the stored information is reduced.

[0005] An object of the present invention is that each user can arbitrarily set a group (between users) to share data, and a member of a group to share data is authenticated by code identity and mutual authentication of members. An object of the present invention is to provide an apparatus and method for sharing information stored in a database.

[0006]

According to the present invention, there is provided a database storage information sharing apparatus in which a user outputs instructions of various processes and notifies the user of the results of the processes, and obtains instructions from the terminals. A database device that stores various data and programs, allows each user to arbitrarily set a group for sharing data, and performs a member authentication of a group sharing data by the same code and mutual authentication of members. It is characterized by having.

The method for sharing information stored in a database according to the present invention comprises the steps of: a) each user adding and requesting a user ID and a password to an instruction for searching, adding, changing, or deleting database stored information; Determining whether the user ID and the password included in the user ID are correct; c) if the result of the determination is incorrect, requesting re-input of the user ID and the password and returning to step a; and d) step If the result of the determination in b indicates that the request is correct, the user is authenticated as a regular user, and it is determined whether the requested content is any one of the storage information among the shared information table between users, the user specific information table, the user information table, and the database information table E) comparing and determining the group code with the group code in the user information table. When, f) of the determination result, if the group code does not match the steps of the process proceeds to step i,
g) When the group codes match as a result of the determination in step e, a step of determining from the database information table whether or not the acquired table setting of the corresponding table is the same as the instruction from the user; And if the result of the determination is not the same, returning the result to the user as not accepting the request and returning to step a;
i) if the result of the determination in step g is the same, the request is accepted, and the request is processed; the result is output; and the processing is terminated.

[0008]

DESCRIPTION OF THE PREFERRED EMBODIMENTS The present invention relates to a method for sharing information stored in a database between arbitrary users. Each user can arbitrarily set a group (between users) for sharing data, and share data. Group member authentication is performed based on code identity and mutual member authentication.

The configuration of an embodiment of the present invention will be described in detail with reference to FIG. FIG. 1 is a diagram showing the configuration of the present invention.

The storage information sharing device of the present invention includes a database device 1 and a terminal 2 as shown in FIG. The database device 1 includes a database unit 10, a user information management unit 20, a stored information management unit 30, and a user authentication unit 40. The database unit 10 includes a user information table 11
And a user-specific information table 12, an inter-user shared information table 13, and a database information table 14.
The database unit 10 stores the user-specific information table 1
2, a plurality of shared information tables between users 13 and a plurality of database information tables 14.

The user information table 11 stores a user ID,
A password, a group code, a party code, a party member and other information are stored, and each user can freely add / change / delete a party code row and a party member row corresponding to his / her own user. The user unique information table 12 stores information unique to each user (unshared information). The inter-user shared information table 13 stores information on each user that can be shared between users. Database information table 14
Stores information on each table setting (eg, the type of request accepted by the table).

When there is a change in the user information table 11, the user information management unit 20 collates the party code of each user with the party member, and specifies the same party code and each party member's user ID. The same group code is created and assigned to the group code column on the user information table 11 of the user who is currently running. Even if the party codes are different or the party codes are the same, the user information management unit 20 determines that the party members have not specified their user IDs with each other.
The same group code is not assigned to each user. Information unique to each user can be shared between users having the same group code assigned by the user information management unit 20.

If the request is for storage information in the inter-user shared information table 13, the storage information management unit 30 stores the group code of the requesting user and the group code of the user who is the holder of the storage information in the user information. Table 11
, The request is not accepted unless the same group code is assigned.

If the same group code is assigned, the storage information management unit 30 reads the table setting of the corresponding table from the database information table 14, and
If the user's request is the same as the acceptance request type set in the corresponding table, the user's request is accepted.

When each user requests the database device 1 via the terminal 2 to search, add, change, or delete information stored in the database, the user authentication unit 40 It is confirmed that the ID and the password match the information stored in the user information table 11, and if the confirmation is obtained, the user is authenticated as a regular user. If they do not match, a request is made to re-enter the user ID and password.

The storage information management unit 30 determines whether the database storage information requested by the authorized user to search, add, change, or delete is the storage information in the user information table 11, the storage information in the user unique information table 12, Information stored in the shared information table 13 or the database information table 14
Is stored information.

When each user issues a request to the database 10 for searching for, adding / changing / deleting user-specific information, the database device 1 uses the user ID and password transmitted by the user via the terminal 2 Confirm that the information matches the information stored in the information table 11, and if the confirmation is obtained, authenticate as a regular user.

Next, the operation of the embodiment of the present invention will be described in detail with reference to FIGS. FIG. 2 is a diagram showing the operation of the present invention. FIG. 3 is a diagram showing an operation when a database device is requested to add / change / delete a user information table according to the present invention. FIG. 5 is a diagram showing an example of an implementation result of the example of the present invention.

Referring to FIG. 2, the operation when each user requests the database device to search, add / change / delete information stored in the database will be described.

Each user inputs a request to search or add / change / delete database storage information to the database device 1 via the terminal 2 (step A1). The user authentication unit 40 receives the request (Step A2). The user authentication unit 40 determines whether or not the user ID and the password transmitted from the terminal 2 match the information stored in the user information table 11 (Step A3). If the result of the determination is that they do not match, a request is made to re-enter the user ID and password (step A4), and steps A1 and A2
Return to As a result of the determination, if they match, it is determined that a confirmation has been obtained, and the user is authenticated as an authorized user. Next, a group code of the authenticated user ID is obtained from the user information table 11 (step A5).
Is used to determine which table is the storage information of the request (step A6).

If the request is for information stored in the shared information table 13 between users, the group code of the requesting user and the group code of the user who is the holder of the stored information stored in the user information table 11 are stored. It is acquired (step A61). The acquired two group codes are compared and determined (step A62). If the result of the determination is that the group codes do not match, the process returns to step A10.
When the group codes match as a result of the determination, the storage information management unit 30 reads the table settings of the corresponding table from the database information table 14. It is determined whether or not the user's request is the same as the reception request type set in the corresponding table (step A63). If the result of the determination is that the request contents are not the same, the flow returns to step A10. If the result of the determination is that the request contents are the same, the request contents are processed assuming that the user's request is accepted and the result is output (step A6).
4), end the process.

At step A5, user specific information table 1
If the request is for the storage information of No. 2, the user ID of the requesting user and the user ID of the holder of the storage information stored in the user information table 11 are acquired (step A71). A comparison is made between the acquired user IDs (step A72). If the result of the determination is that they are not the same user ID, the request is not accepted and the process returns to step A10. If the result of the determination is that the user IDs are the same, the stored information management unit 30 reads the table settings of the corresponding table from the database information table 14. It is determined whether the user's request is the same as the reception request type set in the corresponding table (step A73). If the result of the determination is not the same, the process returns to step A10. If the result of the determination is that they are the same, it is determined that the user's request is accepted, the request is processed and the result is output (step A74), and the processing is terminated.

If the request is for the stored information in the database information table 14 in step A5, the user ID of the requesting user and the user ID of the holder of the stored information are obtained (step A81). The obtained user ID is compared and determined (step A82). If the result of the determination is that they are not the same user ID, the request is not accepted and the process returns to step A10. If the result of the determination is that the user IDs are the same, the stored information management unit 30 reads the table settings of the corresponding table from the database information table 14. It is determined whether or not the user's request is the same as the reception request type set in the corresponding table (step A83). If the result of the determination is not the same, the process returns to step A10. If the result of the determination is that they are the same, it is determined that the user's request is accepted, the request is processed, the result is output (step A84), and the processing is terminated.

If the request is for the stored information in the user information table 11 in step A5, the user ID of the requesting user and the user ID of the holder of the stored information are obtained (step A91). A comparison is made between the acquired user IDs (step A92). As a result of the judgment, the same user ID
If not, the process returns to step A10. If the result of the determination is that the user IDs are the same, the stored information management unit 30 reads the table settings of the corresponding table from the database information table 14. It is determined whether the user's request is the same as the reception request type set in the corresponding table (step A93). If the result of the determination is not the same, the process returns to step A10. If the result of the determination is that they are the same, the request for the search and addition / change / deletion of the party code and the party member is accepted (step A94).

Steps A62, A63, A72, A7
If A3, A83, A92, and A93 are not the same, the request is rejected and the result is output (step A1).
0), return to steps A1 and A2 and wait for an input from the user.

Next, referring to FIG. 3, each user adds / changes / adds to the user information table out of the information stored in the database.
The operation when a request for deletion or the like is made to the database device 1 will be described.

The operations in steps B1 to B4 are the same as the operations in steps A1 to A4 described above, and will not be described.

Next, the user ID of the requesting user
Is compared with the user ID of the holder of the stored information (step B5). If the result of the determination is that they are not the same user ID, the request is not accepted and the result is output (step B6). If the result of the determination is that the user IDs are the same, the stored information management unit 30 accepts requests for searching for party codes and party members and for addition / change / deletion. The user information management unit 20 stores the user information table 11
A new group code is created from the party code and the party member information (step B7).

Next, the n-th (n =
The user ID (Un) of the user information stored in 1) is read, and it is determined whether or not the user IDs (Un) have been read for the number of users (step B8). As a result of the determination, if the data is read for the number of persons, the processing is terminated. If the result of the determination is that the party code has not been read, the party code PC (Un) of the user Un is read (step B9). The user information management unit 20 stores the user U
The n party members PID (Un) are read (step B10).

The party code PC (PID (Un)) and the party member PID (PID (Un)) of the user specified by PID (Un) are read. PC (Un) = P
C (PID (Un)) and PID (PID (Un)) =
It is determined whether Un is satisfied (step B11).
If the result of the determination is not satisfied, the operation proceeds to step B14. As a result of the determination, if the condition is satisfied, the user Un and the user P
Since the same party code is set in the party code column of ID (Un) and each party is designated as a party member, the group code G (U) of the user Un
n) and the group code G (PI of the user PID (Un)
D (Un)) by the user information management unit 20. In this embodiment, G (Un) = G
(PID (Un)) = j (Step B1)
2) Perform j ++ (for example, j = j + 1) (step B13).

Here, as long as the group code assigned by the user information management unit 20 is unique, any code may be assigned. In the embodiment, sequential numbers are assigned.

The count of n is n ++ (for example, n = n +
1) (step B14). Repeat (n ++) for the number of users stored in the user information table.
As a result, a new group code is generated for each user. FIG. 5 shows the generated example.

Next, another embodiment of the present invention will be described with reference to FIGS.
This will be described in detail with reference to FIG. FIG. 4 is a diagram showing another embodiment of the present invention. FIG. 6 is a diagram showing an example of an implementation result of another embodiment of the present invention. Referring to FIG. 4, the present embodiment is different from the embodiment shown in FIG. 3 in that a plurality of party codes and party members of each user can be set. Steps C1 to C7 are the same as steps B1 to B7, and will not be described.

The user ID (Un) of the user information stored in the n-th (n = 1) of the user information table is read,
It is determined whether or not the number of users has been reached (step C
8). If the result of the determination is that the time has been reached, the processing is terminated. If the result of the determination is that the party code has not been reached, the party code PCm (Un) of the user Un is read.

When reading the party code PCm (Un), it is determined whether or not there is data to be read (step C9).
As a result of the determination, if there is no data to be read, n ++ is performed (step C10), and the process returns to step C8. As a result of the determination, if there is data to be read, the party member PIDk (Un) of the user Un is read.

When reading the party member PIDk (Un), it is determined whether or not there is data to be read (step C1).
1). As a result of the determination, if there is no data to be read, m ++ is performed (step C12), and the process returns to step C9. As a result of the determination, if there is data to be read, PIDk (U
n) The party code PCm '(P
IDk (Un)) and party member PIDk '(PI
Dk (Un)).

PCm (Un) = PCm '(PIDk (U
n)) and determine whether or not PIDk ′ (PIDk (Un)) = Un holds (step C13). If the result of the determination is not satisfied, the operation proceeds to step C16. As a result of the determination, if the case is satisfied, the user Un and the user PIDk
Since the same party code is set in the party code column of (Un) and each party is designated as a party member, the group code Gp (U
n) and the group code Gp ′ of the user PIDk (Un)
The same group code is assigned to (PIDk (Un)) by the user information management unit 20. Any code may be assigned as long as the group code assigned by the user information management unit 20 is unique. In the embodiment, sequential numbers are assigned. In this embodiment, Gp
(Un) = Gp '(PIDk (Un)) = j is performed (step C14), and j ++ is performed (step C1).
5). Perform k ++ to read the next party member (step C16).

The process is repeated (n ++) for the number of users stored in the user information table. As a result, a new group code is generated for each user. Fig. 6 shows the generated example.
Shown in

[0039]

According to the database storage information sharing apparatus of the present invention, the group can be set by changing the personal information of each user by himself / herself. Therefore, the administrator who manages and sets the group. Since there is no need to provide a device, man-hours can be reduced and time can be saved.

Further, since the group member authentication is performed by setting the same party code and the party members to each other, higher confidentiality can be obtained than authentication based on the identity of only the code.

[Brief description of the drawings]

FIG. 1 is a diagram showing a configuration of the present invention.

FIG. 2 is a diagram illustrating the operation of the present invention.

FIG. 3 shows an addition / change / addition to a user information table according to the present invention.
FIG. 11 is a diagram illustrating an operation when a deletion or the like is requested from a database device.

FIG. 4 is a diagram showing another embodiment of the present invention.

FIG. 5 is a diagram showing an example of an implementation result of the example of the present invention.

FIG. 6 is a diagram showing an example of an implementation result of another embodiment of the present invention.

[Explanation of symbols]

 Reference Signs List 1 database device 2 terminal 10 database unit 11 user information table 12 user-specific information table 13 inter-user shared information table 14 database information table 20 user information management unit 30 storage information management unit 40 user authentication unit

Claims (6)

[Claims] 1. A terminal in which a user outputs instructions of various processes and notifies a result of the process to the user; and a group which acquires instructions from the terminals, stores various data and programs, and shares data. A database storage information sharing device comprising: a database device that can be set arbitrarily by each user and that performs member authentication of a group sharing data by performing code authentication and mutual member authentication. 2. The database device has a database unit for storing data, the database unit comprising at least a user ID, a password, a group code,
User information including party code and party member is stored, and each user can freely add, change or delete the corresponding party code column and party member column, and non-shared, user-specific information User-specific information table that stores the information of users, shared information table between users that stores information of users that can be shared between users, and table setting information that is information on the types of requests accepted by the table. 2. The database storage information sharing apparatus according to claim 1, further comprising: 3. The database device, when there is a change in the user information, checks the party code of each user with the party member, and designates the party code to be the same and the user ID of each party to the party member. A user information management unit that creates and assigns the same group code to the group code column on the user information table of the user who is present, and when there is a request for storage information of the inter-user shared information table, A storage information management unit that reads a group code and a group code of a user who is a holder of storage information from the user information table and compares the group code; and that each user searches, adds, changes, or deletes the database storage information from the terminal. Is requested, the user ID transmitted by the user via the terminal and the path Over de compares the information of the user information table, stores information sharing device database according to claim 2, further comprising a user authentication unit that authenticates the authorized user. 4. A step in which each user adds and requests a user ID and a password to an instruction to search, add, change or delete database storage information; and b) the user ID and password included in the request are C) a step of requesting re-entry of the user ID and password if the result of the determination is incorrect, and returning to step a. D) a result of the determination of step b. Authenticating the user as an authorized user, and obtaining whether the requested content is stored information of any of a shared information table between users, a user specific information table, a user information table, and a database information table; e) the user information table And f) obtaining the group code of the user ID from Step determines compares the group code or the user I,
D) a step of comparing and determining D with the user ID of the stored information holder; g) a step of proceeding to step i if the group code or the user ID does not match as a result of the determination; h) a result of the determination of step f; If the group code or the user ID matches, a step of judging from the database information table whether or not the acquired table setting of the corresponding table is the same as the instruction from the user; If not, return the result to the user as not accepting the request and return to step a. J) If the result of determination in step h is the same, accept the user's request and process the request and output the result. Ending the processing, the method of sharing information stored in a database. 5. A step in which each user adds and requests a user ID and password to an instruction to search, add, change, or delete database storage information; and b) the user ID and password included in the request are included. And c) if the result of the determination is incorrect, request the user to re-enter the user ID and password and return to step a. D) if the result of the determination in step b is correct, E) comparing and determining the user ID with the user ID of the stored information; e) outputting the result as rejecting the request if the result of the determination is that they are not the same user ID; f) determining the same as the result of the determination Accepting a search, addition, change or deletion request and storing the information; and g) n-th user information table Reading the user ID (Un) of the user information stored in (n is a natural number) and judging whether or not the number of users has been read; and h) as a result of the judgment, if the number of users has been read, the process ends; As a result of the judgment, if the number of the party code has not been read, the step of reading the party code PC (Un) of the user Un and the party member PID (Un) of the user Un; and i) the party code is specified by the PID (Un). User's party code PC (PID (Un)) and party member PI
Reading D (PID (Un)) and j) PC (Un) = PC (PID (Un)) and PID
(PID (Un)) = Un, a step of determining whether or not: k) If the result of the determination does not hold, proceed to step m; 1) If the result of the determination of step j holds, G ( U
n) = G (PID (Un)) = j (j is an integer) and performing j ++; and m) performing n ++ and returning to step g. Method. 6. A step in which each user adds a user ID and a password to an instruction for searching, adding, changing or deleting database storage information and requests the same; and b) the user ID and the password included in the request are included in the request. And c) if the result of the determination is incorrect, request the user to re-enter the user ID and password and return to step a. D) if the result of the determination in step b is correct, E) comparing and determining the user ID with the user ID of the stored information; e) outputting the result as rejecting the request if the result of the determination is that they are not the same user ID; f) determining the same as the result of the determination Accepting a search, add, change or delete request and storing the information; and g) identifying the nth (n is a natural number) Reading the user ID (Un) of the obtained user information and determining whether or not the number of users has been reached; and h) as a result of the determination, ending the processing if the number has reached, and determining that the number has not been reached. In this case, the party code PCm (Un) of the user Un is read, and the party code PCm (U
n) when reading (m is an integer), determining whether there is data to be read; i) performing n ++ if there is no data to be read as a result of the determination; returning to step g; and j) step. As a result of the judgment of h, if there is data to be read, the party member PIDk (Un) of the user Un
(K is an integer) and reads the party member PIDk (U
When reading n), determining whether there is data to be read; k) as a result of the determination in step j, if there is no data to be read, performing m ++ and returning to step h; l) determining in step j As a result, if there is data to be read, the party code PCm ′ (PIDk (Un)) and the party member PIDk ′ (PIDk (Un)) of the user specified by PIDk (Un) are read, and PCm (U
n) = PCm ′ (PIDk (Un)) and PIDk ′
(PIDk (Un)) = Un, a step of determining whether or not: m) If the result of the determination does not hold, go to step o; n) If the result of the determination holds, Gp (Un) = G
A method for sharing stored information in a database, comprising: performing p ′ (PIDk (Un)) = j and performing j ++; and o) performing k ++ to read party members and returning to step h.