JP2004086787A - Information disclosure service system for specific person - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide an information disclosure service system for specific persons capable of retrieving and referring to information without burying key information. <P>SOLUTION: In this information disclosure service system for specific persons in which a client apparatus is connected to a server apparatus through a network, the server apparatus comprises a disclosure request processing part and an information disclosure processing part. When the disclosure request processing part receives a message indicating clients to which the disclosure of information is desired and what information is requested from the client device of clients stored in the user information database to which the disclosure of information is desired, the disclosure request processing part stores the message in the disclosure request control information database. The information disclosure processing part notifies the client device of an information owner to which the disclosure of information is desired that there is a client who desires to disclose information and, when receiving the approval of the disclosure of information from the client device to which the disclosure of information is desired, stores the approved personnel for the disclosure of information, approving personnel for disclosure of information, and information for specifying the information to be disclosed in the disclosure control information database and notifies the client device of the approved personnel that the disclosure of information is approved. <P>COPYRIGHT: (C)2004,JPO

Description

[0001]
TECHNICAL FIELD OF THE INVENTION
The present invention relates to an information disclosure service system for a specific person.
[0002]
[Prior art]
When a person who refers to information refers to specific information, it is common to use a search system such as YAHOO. However, in this case, all the information must be disclosed on the Internet.If you want to exchange information among members before releasing it in a regular procedure, such as university research information, close the group. It is necessary to build a search system and register key information for the search in advance on the premise of the search.
[0003]
Japanese Patent Application Laid-Open No. 2002-92436 discloses a technique for displaying only information that the user wants to refer to in a specific field. According to this publication, it is possible to display only necessary information by registering search conditions for displaying information that the user wants to refer to in the server, but the information is registered only at the timing of the information presenter. Since the information viewer displays the information completely asynchronously with the registration timing, he or she cannot refer to the necessary information at the required timing.
[0004]
[Problems to be solved by the invention]
However, the conventional information disclosure technology has the following problems. As described above, in the case where information registered as personal information within a specific range is disclosed to a specific person, there is a problem that the conventional technology cannot refer to the information at a desired timing. In addition, when the information is not intended to be disclosed, the key information for the search is not embedded from the beginning, so that there is a problem that the search and the reference of the information are difficult.
[0005]
The present invention has been made in view of the above, and an information disclosure service system that synchronizes an information presenter and an information referrer and publishes information to a specific person without embedding key information for search. The purpose is to provide.
[0006]
[Means for Solving the Problems]
FIG. 1 is a diagram illustrating the principle of the present invention. As shown in FIG. 1, in the information disclosure service system for specific persons, a client device 2 # i (i = 1, 2,...) And a server device 4 are connected via a network 6. The server device 4 includes a user information database 8, a public information storage database 10, a public request management information database 12, a public management information database 14, a public request processing unit 16, and an information public processing unit 18.
[0007]
The user information database 8 stores information on clients whose information is to be disclosed. The public information storage database 10 stores information and the owner of the information. Upon receiving a message indicating the client who desires information disclosure and what information is desired from the client device 2 # i who desires information disclosure, the disclosure request processing unit 16 requests the client who desires information disclosure and the information disclosure. And a message indicating what information the client wants and what information he / she wants.
[0008]
The information disclosure processing unit 18 notifies the client device 2 # j that wants to release the information stored in the disclosure request management information database 12 that there is a client that wants to release the information. When the information disclosure consent is received from the client device 2 # j, the disclosure management information database 14 stores information for specifying the information disclosure consent, the information disclosure consent, and the information to be disclosed. Notify the client device 2 # i that the information disclosure has been accepted.
[0009]
BEST MODE FOR CARRYING OUT THE INVENTION
FIG. 2 is a configuration diagram of the information disclosure service system for specific persons according to the embodiment of the present invention. In the present embodiment, a class notebook will be described as an example of public information. However, the information is not limited to the class notebook, and any information may be used when information is disclosed within a specific group. As shown in FIG. 2, the information disclosure service system for specific persons includes a plurality of client devices 20 # i (i = 1, 2,...) And a server device 22. The client device 20 # i and the server device 22 are connected via a network 24. The network 24 is a LAN, a WAN, the Internet, or the like.
[0010]
The client device 20 # i is a terminal such as a personal computer used by the information presenter or the presentee, and includes an input device 30 # i, an output device 32 # i, an input / output control interface unit 34 # i, a RAM 36 # i, It has a unit 38 # i, a ROM 40 # i, a hard disk (HD) 42 # i, and a communication control interface unit 44 # i. The input device 30 # i is a device for inputting characters and the like such as a mouse and a keyboard. The output device 32 # i is a device that outputs characters and the like, such as a display.
[0011]
The input / output control interface unit 34 # i manages an interface between the control unit 38 # i, the input device 30 # i, and the output device 32 # i. The RAM 36 # i is a random access memory that stores an execution program and data. The control unit 38 # i performs control for receiving provision of the information disclosure service, and includes the Web browser 50 # i. The Web browser unit 50 # i transmits / receives a page described in HTML to / from the server device 22 according to TCP / IP and displays the page on the output device 32 # i. The ROM 40 # i is a read-only memory that stores a program. The HD 42 # i is a hard disk that stores programs and the like. The communication control interface unit 44 # i performs communication with the server device 22 via the network 24. The communication protocol is not particularly limited as long as communication with the server device 22 is possible, but TCP / IP is generally used.
[0012]
The server device 22 includes a control unit 70, a user information DB 72, a note information DB 74, a note management information DB 76, a note borrowing request management information DB 78, and a communication control interface unit 80. The control unit 70 performs control for disclosing information to a specific person, and includes a user authentication processing unit 100, a note registration processing unit 102, a page registration processing unit 104, a note borrowing request processing unit 106, and a note lending process. It has a unit 108.
[0013]
FIG. 3 is a detailed block diagram of the control unit 70 in FIG. The user authentication processing unit 100 has the following functions. (1) The client device 20 # i is requested to input a login ID. {Circle around (2)} The login ID is received from the client device 20 # i, and it is checked whether or not the user of the login ID is registered in the user management information DB 72 with reference to the user management information DB 72. {Circle around (3)} If not registered in the user management information DB 72, the client device 20 # i is notified of the fact, and if registered in the user management information DB 72, the process is continued.
[0014]
The note registration processing unit 102 has the following functions. (1) The page related to the registration screen is transmitted to the client device 20 # i. {Circle around (2)} The note input in the registration screen is stored in the note information storage DB 74, and the note list screen is transmitted to the client device 20 # i.
[0015]
The page registration processing unit 104 has the following functions. (1) When a page registration request is received from the presenter, a page registration screen is transmitted to the client device 20 # i. {Circle around (2)} Upon receipt of the note input by the presenter on the page registration screen and transmission of the note and each page in the note from the client device 20 # i, the note information is stored in the note information storage DB 74. The note borrowing request processing unit 106 has the following functions. {Circle around (1)} Upon receiving a note borrowing request from the client device 20 # i, a note borrowing request screen is transmitted. {Circle around (2)} Upon receiving note borrowing request information indicating a user and a note of a partner who wants to borrow a note, which is input in the note borrowing request screen from the client device 20 # i, the note borrowing request management information DB 78 stores it.
[0016]
The note lending processing unit 108 includes a note borrowing approval unit 120, a note lending unit 122, a note lending stop unit 124, and a page information search unit 126. The note borrowing approval unit 120 has the following functions. {Circle around (1)} A note list screen including a message indicating that a note borrowing request has been made is transmitted to the client device 20 # i to which a note borrowing request has been stored in the note borrowing request management information DB 78. {Circle over (2)} Upon receiving a note lending approval screen request from the client device 20 # i, the system sends a note lending approval screen to the client device 20 # i. {Circle around (3)} Upon receiving the note lending consent input on the note lending consent screen from the client device 20 # i, it stores it in the note management information DB 76.
[0017]
The note lending unit 122 has the following functions. {Circle around (1)} A note list screen including a list of notes borrowed from another person is transmitted to the client device 20 # i of the presentee whose note lending has been accepted. (2) When a note borrowed from another person is designated by the client device 20 # i, the contents of the note borrowed are transmitted to the client device 20 # i.
[0018]
The note lending stopping unit 124 has the following functions. {Circle around (1)} When an instruction to delete a note is issued from the client device 20 # i, information relating to the note lending is deleted from the note management information DB 76. (2) The canceled note is not transmitted to the client device 20 # i whose note lending has been canceled.
[0019]
The page information search unit 126 has the following functions. {Circle around (1)} Upon receiving a search keyword for a note to be borrowed from the client device 20 # i, the notebook management information DB 74 searches for a note including the content that matches the search keyword. (2) A note search result indicating the note name of the corresponding note and the presenter of the note is transmitted to the client device 20 # i.
[0020]
FIG. 4 is a configuration diagram of the user information DB 72 in FIG. As shown in FIG. 4, the user information DB 72 includes items of a user ID, a password name, and a group name. The user ID is an identifier for identifying a user. The password is the user's password. The name is a user name. The group name is the name of the group to which the user belongs. This is in order to approve the note lending on a group basis.
[0021]
FIG. 5 is a configuration diagram of the note information DB 74 in FIG. As shown in FIG. 5, the note information DB 74 includes items of a user ID, a note name, a page name, information, and an attached file. The user ID is an identifier of the presenter of the note. The note name is the note name to be lent. The information is information indicating the contents of the note. The attached file is a file name when a file is attached to the note.
[0022]
FIG. 6 is a configuration diagram of the note management information DB 76 in FIG. As shown in FIG. 6, the note management information DB 76 includes items of a user ID, a note name, a borrower ID, and a borrowing period. The user ID is an identifier of the presenter of the notebook to be lent. The note name is a note name being lent / not lent. The borrower ID is the identifier of the presentee of the note, and NULL is an unlent note. The borrowing period is a period during which the note borrower can borrow.
[0023]
FIG. 7 is a configuration diagram of the note borrowing request management information DB 78 in FIG. As shown in FIG. 7, the note borrowing request management information DB 78 includes items of a user ID, a reception date, a sender ID, a title, and a text. The user ID is the user ID of the partner who wants to borrow the notebook when the user wants to borrow the notebook, and is the user ID of the partner who accepts the borrowing of the notebook. The receipt date is the date on which the borrowing of the note was applied or the date on which the borrowing was accepted. The sender ID is a user ID of a person who desires to borrow a note or a user ID of a person who accepts borrowing of a note. The title is the title of a message related to borrowing or accepting a note. The text is the text of a message relating to the borrowing or acceptance of the note.
[0024]
The communication control interface unit 80 in FIG. 2 controls communication with the client device 20 # i via the network 24. The Web server 110 transmits and receives a page described in HTML with the client device 20 # i according to HTTP.
[0025]
(A) Creation of user information DB 72
A user ID, a password, a name, and a group name are registered in the user information DB 72 for a user who wants to disclose information.
[0026]
(B) Operation at login
FIG. 8 is a flowchart showing the operation at the time of login. As shown in FIG. 8, in step S2, the server device 22 transmits the Web data of the login screen to the client device 20 # i. In step S20, the client device 20 # i displays a login screen. The login screen has items for inputting a user ID and a password, and the user inputs these items. The client device 20 # i transmits the user ID and the password information to the server device 22.
[0027]
In step S4, it is determined whether the password matches the password corresponding to the user ID stored in the note information DB 72. If they match, the process proceeds to step S6. If they do not match, the process proceeds to step S12. In step S6, a note name corresponding to the user ID is searched from the note information storage DB 74. In step S8, it refers to the note management information DB 76 to determine whether a note lending corresponding to the user ID has been set. If the lending has been set, the corresponding note is also searched.
[0028]
In step S10, a search is made for a borrowing request with reference to the note borrowing request management information DB 78 corresponding to the user ID. Hereinafter, the search from step S6 to step S10 is referred to as note list data search. In step S12, a message that the user ID or the password does not match is notified by a message. In step S14, the Web data of the initial screen (note list) is edited and transmitted to the client device 20 # i.
[0029]
FIG. 9 is a diagram showing a note list screen. As shown in FIG. 9, on the note list screen, “note note”, “note registration”, “borrow note”, “note note”, “note note”, “person who wants to borrow note” "", "End", and "Note Ichiran" include "List of notes owned by me", "Register page" and "Delete note" for each note, and "Borrow from others". Notes and borrowing period "and" indicate that there is a note borrowing request ". In step S24, the client device 20 # i displays the note list screen shown in FIG.
[0030]
(C) Note registration and page registration
FIG. 10 is a sequence chart of note registration / page registration. FIG. 11 is a flowchart showing the operation at the time of presenter note registration. FIG. 12 is a flowchart showing the operation when registering the presenter page. As shown in (2) in FIG. 10, the above-described authentication at the time of login is performed. In step S70 in FIG. 11, when the authentication is OK, a search process of the note list data is performed. In step S72, the Web data of the note list screen is transmitted to the client device 20 # i. The presenter clicks the note registration shown in FIG. In step S52, the client device 20 # i transmits a note new registration selection to the server 22. In step S74, the server 22 transmits the Web data of the note registration screen to the client device 20 # i as shown in (4). In step S54, the client device 20 # i displays a new note registration screen.
[0031]
FIG. 13 shows a note registration screen. As shown in FIG. 13, the note registration screen includes items of “note name”, “note color”, “registration”, and “quit”. “Note name” is an item in which the name of the note to be registered is input. "Note color" specifies a color for displaying a note. “Registration” is an item for registering a note. "Stop" is an item for stopping registration of a note.
[0032]
The presenter inputs “note name” and “note color” and then clicks “register”. In step S56, the client device 20 # i specifies a note name and a color and transmits a registration request. In step S76, the server device 22 registers in the note management information D76. In step S78 and step S110 in FIG. 12, the server device 22 searches for note list data. In step S80 and step S112 in FIG. 12, as shown in (8), the server device 22 transmits Web data of the note list screen to the client 20 # i. In step S58 and steps S92 to S92 in FIG. 12, the client device 20 # i displays a note list screen. Here, since the note has been registered, the registered note name is displayed in “Note Ichiran”. The presenter clicks “Page Registration” of the note displayed in “Note Ichiran”.
[0033]
In step S92 in FIG. 12, the client device 20 # i transmits the selected note name to be registered to the server device 22. In step S114, the server device 22 transmits the Web data of the page registration screen to the client device 20 # i. In step S94, the client device 20 # i displays a page information registration screen.
[0034]
FIG. 14 is a diagram showing a page registration and content reference screen. As shown in FIG. 14, the page registration and content reference screens include “Previous”, “Next”, “Page title”, “Body”, “Attached file name”, “Change”, “Erase page” and It consists of "stop" items. The presenter inputs a page title, a text and an attached file name. In step S96 in FIG. 12, the client device 20 # i transmits the page name and the page information to the server device 22. In step S116, the server device 22 registers the page name and the page information in the note management information DB 76. In step S118, the server device 22 searches the note list data. In step S120, the server device 22 transmits the Web data of the note list screen. In step S98, the client device 20 # i displays a note list screen. When "next" in the figure is selected, a screen for inputting information of the next page is displayed.
[0035]
(D) Note borrowing request, lending
FIG. 15 is a sequence chart of notebook borrowing and lending. FIG. 16 is a flowchart showing the operation at the time of a note borrowing request from the presentee. FIG. 17 is a flowchart showing the presenter's note lending process. As shown in (20) in FIG. 15, the above-described authentication at the time of login is performed on the presented person. In step S150 in FIG. 16, when the authentication is OK, the server device 22 performs a search process of the note list data. In step S152, the server device 22 transmits the Web data of the note list screen to the client device 20 # 1.
[0036]
In step S170, the client device 20 # 1 displays a note list screen as shown in (26). The presentee clicks "borrow note". In step S172, the client device 20 # 1 transmits the selection of the note borrowing request screen to the server device 22. In step S154, the server device 22 transmits the Web data of the note borrowing request screen to the client device 20 # 1. In step S174, the client device 20 # 1 displays a note borrowing request screen.
[0037]
FIG. 18 is a diagram showing a notebook borrowing request screen. As shown in FIG. 18, the note borrowing request screen includes “borrow a note”, which includes items of “who wants to borrow a note”, “message”, “send”, and “stop”. The presentee selects “a person who wants to borrow a note” and inputs a “message”. In step S176, the client device 20 # 1 transmits a note borrowing request including the note borrower and the contents to the server 22 as shown in (28).
[0038]
In step S156, the server device 22 records the fact that the request is a borrowing request and the content in the note borrowing request management information DB 78 of the note borrower. In step S158, note list data search is performed. In step S160, the Web data of the note list screen is transmitted. In step S176, the client device 20 # 1 displays a note list screen.
[0039]
Thereafter, it is assumed that the client device 20 # 2 of the presenter of the notebook that the presentee wants to borrow logs in. As shown at (40) in FIG. 15, the above-mentioned authentication is performed for the presenter. In step S200 in FIG. 17, when the authentication is OK, the server device 22 performs a search process of the note list data. In step S202, the Web data of the note list screen is transmitted to the client device 20 # 2. In step S220, the client device 20 # 2 displays a note list screen. Here, since there is a presentee who wants to borrow the note of the presenter, the screen of “Note Ichiran” indicates that there is a request to borrow the note. The presenter clicks "person who wants to borrow a note" in FIG. In step S222, the client device 20 # 2 selects the icon of "the person who wants to borrow a note" and transmits the icon to the server device 22. In step S204, as shown in (44), the server device 22 transmits the Web data of the note lending approval screen to the client device 20 # 2 and makes a note borrowing request. In step S224, the client device 20 # 2 displays a note lending approval screen.
[0040]
FIG. 19 is a diagram showing a note lending approval screen. As shown in FIG. 19, “person who wants to borrow a note” includes “name” of the person who wants to borrow a note and “contents”, “kasu”, “kasuna”, and “kasu” that indicate which note to borrow Return "item. The presenter clicks "Kasuga" to accept the note lending, and clicks "Kasuga" to reject the acceptance.
[0041]
In step S226, the client device 20 # 2 determines whether or not the lending approval of the notebook has been selected. When accepting the lending, the agreement is transmitted to the server device 22, and the process proceeds to step S206. When rejecting the lending, the refusal is transmitted to the server device 22 and the process proceeds to step S208. In step S206, the server device 22 transmits the Web data of the note lending screen. In step S208, the borrowing request is deleted from the note borrowing request management information DB 78. In step S228, the client device 20 # 2 displays a note lending screen.
[0042]
FIG. 20 is a diagram showing a notebook lending screen. As shown in FIG. 20, the screen of “leave notes” includes items of “notes to be made”, “parties to be made”, “period to be made”, “weed” and “stop”. The "note to be stolen" specifies the name of the lent note. The “people to start out” specifies the name of the person who accepts the note lending. To lend to all, specify "all". The “scratch period” specifies a period for renting a note. The presenter specifies “note to be made”, “people to be made”, and “period to be made”, and then clicks “to make”.
[0043]
In step S230, as shown in (46), the client device 20 # 2 transmits a note borrowing permission including a "note to start", a "party to start", and a "period to start". In step S210, the server device 22 stores the lender and the period in the designated note management information DB 76, and deletes the permitted note borrowing request from the note borrowing request management information DB 78. In step S212, the server device 22 searches the note list data. In step S214, the server device 22 transmits the Web data of the note list screen. In step S232, the client device 22 # 2 displays a note list screen.
[0044]
As shown in (34), the presentee who has accepted the note borrowing clicks on “Note Ichiran” or logs in, so that the client device 20 # 1 refers to the note. As shown in (36), the server device 22 searches the note list data with reference to the note management information DB 76 and the note borrowing request management information DB 78, transmits the note list screen, and displays the note information. The client device 20 # 1 displays the note list screen. At this time, the notes borrowed from another person are displayed in a list together with the loan period in “Note Ichiran” in FIG. 9, and the presentee can click here to view the contents of the notes. It becomes.
[0045]
(E) Cancellation of note borrowing
FIG. 21 is a sequence chart showing the note borrowing cancellation. When the presenter cancels the note borrowing, the client device 20 # 2 logs in as shown in (100). As shown in (102), the server device 20 transmits the note list screen. The presenter clicks on “Notes that are present” in FIG. The client device 20 # 2 transmits a request for a list of hidden notes. The server device 22 transmits the note lending list screen to the client 20 # 2. The client 20 # 2 displays the note lending list screen.
[0046]
FIG. 22 is a diagram showing a notebook lending list screen. As shown in FIG. 22, the list of the notebook names lent by the presenter, and the names of the borrowed parties and “delete” are displayed for “notes that are present”. In order to cancel the borrowing of the note, the presenter clicks on “delete” corresponding to the name of the borrower. The client device 20 # 2 transmits the note borrow cancellation to the server device 22 as shown in (104). The server device 22 deletes the note name related to the note borrowing cancellation and information corresponding to the borrower from the note management information DB 76.
[0047]
As shown in (110), the client device 20 # 1 of the presentee whose notebook borrowing has been canceled logs in. As shown in (112), the server device 20 transmits the note list screen. The client device 20 # 2 displays the note list. The note whose note borrow has been canceled is not displayed in “Note Ichiran” in FIG. 9. As shown in (114), note information is not displayed as shown in (116) even when the presentee attempts to refer to a note.
[0048]
(F) Note search
FIG. 23 is a flowchart showing a note borrowing request from the presentee. In step S350, the server device 22 performs a note list data search process. In step S352, the Web data of the note list screen is transmitted to the client 20 # 1. In step S300, the client device 20 # 1 displays a note list screen. The presentee clicks “search for notes”. The client device 20 # 1 transmits the note search screen selection to the server device 22. In step S354, the server device 22 transmits the Web data of the note search screen to the client 20 # 1. In step S302, the client device 20 # 1 displays a note search screen.
[0049]
FIG. 24 is a diagram showing a note search screen. As shown in FIG. 24, the note search screen includes a “search keyword”, a “note search”, and a “search result”. The “search keyword” is a keyword indicating the content of the note for which the user wants to borrow the note. “Note search” is a search specification of a note having contents including a search keyword. The “search result” displays the search result of the note, and includes “name”, “note name”, and “note borrow”. “Name” is the name of the presenter of the note corresponding to the keyword. “Note name” is a note name corresponding to the keyword. "Note borrowing" designates note borrowing.
[0050]
The presentee inputs the search keyword and clicks “borrow note”. In step S306, the client device 20 # 1 transmits the search keyword. In step S <b> 356, the server device 22 performs a character string search on all contents of members in the same group as the presentee in the note information storage DB 74 using the specified search keyword. If there is a match, only the note holder name and note name are extracted. In step S358, the server device 22 transmits the Web data of the search result display screen to the client device 20 # i. In step S308, the client device 20 # i displays the search result display screen shown in FIG.
[0051]
The presentee clicks the note borrowing corresponding to the user name and the note name from the search result. The client device 20 # 1 transmits the user name and the note name to the server device 22. In step S360, the server device 22 transmits to the client device 20 # 1 Web data in which the name and the note name are embedded in the note lending screen. In step S312, the client device 20 # 1 displays a note lending screen in FIG. The presentee inputs a "message" on the note borrowing request screen. In step S314, the note borrower and the contents are transmitted to the server device 22.
[0052]
In step S362, the note name and content are recorded in the note borrower's note borrowing request management information DB 78. In step S364, the server device 22 performs a note list data search process. In step S366, the server device 22 transmits the Web data of the note list screen to the client 20 # 1. In step S316, the client device 20 # 1 displays a note list screen.
[0053]
The present invention includes the following supplementary notes.
[0054]
(Supplementary Note 1) In an information disclosure service system for specific persons in which a client device and a server device are connected via a network,
The server device,
A user information database that stores information about clients to be disclosed;
A public information storage database for storing information and an owner of the information,
A disclosure request management information database that stores a client that desires information disclosure, a client that desires information disclosure, and a message indicating what information is desired;
A disclosure management information database for storing information for specifying a consent of information disclosure, a consent of information disclosure and information to be disclosed;
When a message indicating the client who desires information disclosure and what information is desired is received from the client device of the client stored in the user information database which desires information disclosure, a disclosure request stored in the disclosure request management information database A processing unit;
Notifying the client device of the information owner stored in the public information storage database that the information stored in the disclosure request management information database is desired to be disclosed to the effect that there is a client who wants to release the information, Is received from the client device that desires the information disclosure, the information for specifying the information disclosure consent, the information disclosure consent and the information to be disclosed is stored in the disclosure management information database, and the consent An information disclosure processing unit that notifies the client device that information disclosure has been accepted;
An information disclosure service system for specific persons, characterized by comprising:
[0055]
(Supplementary Note 2) The server device issues an authentication request from a client device of a client that owns the information, and includes a user authentication processing unit that controls so that only the client stored in the user management database is made public. The information disclosure service system for specific persons according to claim 1, further comprising:
[0056]
(Supplementary note 3) The server device according to supplementary note 1, wherein the server device includes an information registration processing unit that stores the information in the public information storage database when receiving the information from the client device of the client that owns the information. Information disclosure service system.
[0057]
(Supplementary Note 4) The information disclosure processing unit deletes the corresponding information from the disclosure management information database when the information disclosure approval is canceled from the client device of the information owner who has approved disclosure. An information disclosure service system for specific persons according to Appendix 1.
[0058]
(Supplementary Note 5) When the information disclosure processing unit receives a message indicating what information the client desires to release from the client device, the information disclosure processing unit searches the public information storage database and owns information corresponding to the message. 2. The information disclosure service system for specific users according to claim 1, wherein the client device notifies the client device about the client to perform.
[0059]
(Supplementary Note 6) The server device transmits a menu screen for specifying an information list, information registration, information disclosure request, and information being published to the client device. When the client device specifies the information list, the server device stores the public information. Notifying the client device of a list of information owned by the client of the client device stored in the database, a list of information permitted to be disclosed to the client, and the fact that there is a client who desires information disclosure. An information disclosure service system for specific persons according to supplementary note 1 characterized by the above-mentioned.
[0060]
【The invention's effect】
According to the present invention described above, since it is not necessary to register information for the purpose of information disclosure, it is not necessary to embed a search key, and the number of steps of information registration can be reduced. Further, the time required for the information viewer to be able to refer to the desired information can be reduced.
[Brief description of the drawings]
FIG. 1 is a diagram illustrating the principle of the present invention.
FIG. 2 is a configuration diagram of a specific person information disclosure service system according to an embodiment of the present invention.
FIG. 3 is a configuration diagram of a control unit in the server device in FIG. 2;
FIG. 4 is a configuration diagram of a user information DB in FIG. 2;
FIG. 5 is a configuration diagram of a note information DB in FIG. 2;
FIG. 6 is a configuration diagram of a note management information DB in FIG. 2;
FIG. 7 is a configuration diagram of a note borrowing request management information DB in FIG. 2;
FIG. 8 is an operation flowchart at the time of login.
FIG. 9 is a diagram showing a note list screen.
FIG. 10 is a sequence chart of note registration and page registration.
FIG. 11 is an operation flowchart at the time of presenter note registration.
FIG. 12 is an operation flowchart when registering presenter page information.
FIG. 13 is a diagram showing a note registration screen.
FIG. 14 is a diagram showing a page registration and content reference screen.
FIG. 15 is a sequence chart of a note borrowing request and lending.
FIG. 16 is a flowchart of a note borrowing request from a presentee.
FIG. 17 is a flowchart of a presenter's note lending process.
FIG. 18 is a diagram showing a notebook borrowing request screen.
FIG. 19 is a diagram showing a note lending approval screen.
FIG. 20 is a diagram showing a notebook lending screen.
FIG. 21 is a sequence chart of note borrowing cancellation.
FIG. 22 is a diagram showing a notebook lending list screen.
FIG. 23 is a flowchart of a note borrowing request from a presentee.
FIG. 24 is a diagram showing a note search screen.
[Explanation of symbols]
2 # i (i = 1, 2,...) Client device
4 Server device
6 Network
8 User information database
10. Public information database
12 Release request management information database
14 Public Management Information Database
16 Publication request processing unit
18 Information disclosure processing section

Claims (5)

In an information disclosure service system for specific persons in which a client device and a server device are connected via a network,
The server device,
A user information database that stores information about clients to be disclosed;
A public information storage database for storing information and an owner of the information,
A disclosure request management information database that stores a client that desires information disclosure, a client that desires information disclosure, and a message indicating what information is desired;
A disclosure management information database for storing information for specifying a consent of information disclosure, a consent of information disclosure and information to be disclosed;
When a message indicating the client who desires information disclosure and what information is desired is received from the client device of the client stored in the user information database which desires information disclosure, a disclosure request stored in the disclosure request management information database A processing unit;
Notifying the client device of the information owner stored in the public information storage database that the information stored in the disclosure request management information database is desired to be disclosed to the effect that there is a client who wants to release the information, Is received from the client device that desires the information disclosure, the information for specifying the information disclosure consent, the information disclosure consent and the information to be disclosed is stored in the disclosure management information database, and the consent An information disclosure processing unit that notifies the client device that information disclosure has been accepted;
An information disclosure service system for specific persons, characterized by comprising: The server device further includes a user authentication processing unit that makes an authentication request from a client device of a client that owns the information and controls so that only the client stored in the user information database is disclosed. 2. The information disclosure service system for specific persons according to claim 1, wherein: 2. The information disclosure service for a specific person according to claim 1, wherein the server device has an information registration processing unit that stores the information in the public information storage database when the server device receives information from a client device that owns the information. system. 2. The information disclosure processing unit, upon receiving a cancellation of information disclosure approval from a client device of an information owner who has approved disclosure, deletes the corresponding information from the disclosure management information database. Information disclosure service system for specific persons described. When the information disclosure processing unit receives a message indicating what information the client desires to release from the client device, the information disclosure processing unit searches the public information storage database, and searches for the client that owns the information corresponding to the message. 2. The information disclosure service system for specific persons according to claim 1, wherein the information is notified to a client device.

Images