JP5723338B2 - Data sharing system - Google Patents

Description

  The embodiment described in this specification relates to a technique for controlling sharing of an electronic material file used in a meeting or the like.

  In addition to materials on sheet media, a mode in which a personal computer (hereinafter referred to as a PC) is brought to a meeting such as a meeting or a meeting has been established. A conference participant who brings a PC downloads and browses a conference material file prepared in advance in a file server, for example. There are also systems that support file sharing.

  The following techniques are disclosed.

JP 2008-70952 A JP 2005-310096 A

  In the conventional system, it is necessary to register the participants in advance for each meeting, and the materials are distributed to the terminals used by the registered persons. However, sometimes people who were not scheduled to participate in the meeting suddenly jump in and participate. The conventional system cannot cope with this jump-in participation, and there is a problem that materials cannot be distributed to the jump-in participants.

  In addition, the conventional system needs to register a material file to be used for the conference in advance before distributing data electronically. However, there are cases where participants in the conference jump into the material during the conference, and there is a problem that the conventional system cannot cope with the sudden addition of the material file.

  One aspect of the present embodiment is made in order to solve the above-described problems, and aims to provide a technique that enables a participant to view a file of a conference material. To do.

  Another object of one embodiment of the present invention is to provide a technique that enables sudden addition of a material file from a participant.

The file sharing system according to one aspect of the embodiment includes a first terminal, a second terminal, and a server. The server receives the identification information of the meeting participant and the request message from the terminal, and when allowing the browsing of the file used in the meeting based on the identification information, the server generates first information and transmits the first information to the terminal. . The first terminal receives the first information to transmit the identification information of the first participant that is configured as a participant in association with the request message to the server, a terminal which viewing is allowed file. The second terminal acquires the first information received by the first terminal, the first information, or information derived based on the first information, and identification information of the second participant that is not set as a meeting participant Send. The server allows the second terminal to view the file if the access right of the second participant is higher than the average access right to the file of all the participants of the meeting, and the access of the second participant is higher than the average access right. If the authority is low, if the access authority of the first participant is lower than the average access authority, the second terminal is not allowed to view the file, and if the access authority of the first participant is higher than the average access authority, Allow browsing of files by two terminals.
The file sharing system according to one aspect of the embodiment includes a first terminal, a second terminal, and a server. The server receives the identification information of the meeting participant and the request message from the terminal, and when allowing the browsing of the file used in the meeting based on the identification information, the server generates first information and transmits the first information to the terminal. . The first terminal is a terminal that is allowed to view a file and transmits the identification information of the first participant set as a participant of the meeting and a request message to the server and receives the first information. The second terminal acquires the first information received by the first terminal, the first information, or information derived based on the first information, and identification information of the second participant that is not set as a meeting participant Send. The server allows the second terminal to view the file if the second participant's access authority to the file is higher than the lowest access authority of all meeting participants. If the access authority is lower than the lowest access authority, if the first participant is the participant with the lowest access authority, the first terminal does not allow the second terminal to view the file, and the first participant participates in the lowest access authority. If the user is not an authorized person, browsing of the file by the second terminal is permitted.

  The file sharing system according to one aspect of the embodiment includes a first terminal, a second terminal, and a server. The first terminal is a terminal used by the first user participating in the meeting, and transmits identification information of the first user. The second terminal is a terminal used by a user who is participating in the meeting and is different from the first user. The server receives the identification information of the first user from the first terminal, and determines whether or not to permit browsing on the second terminal for a predetermined file that is not pre-registered to be used for the meeting based on the identification information. .

It is a schematic diagram which shows an example of the whole structure of a system. It is a block diagram which shows the hardware structural example inside a server. It is a block diagram which shows an example of the hardware constitutions inside a tablet terminal. It is a figure which shows an example of the table which a meeting management server stores. It is a figure which shows an example of the roll value of an employee. It is a flowchart which shows the operation example of 1st Embodiment. It is a figure explaining operation | movement of 1st Embodiment. It is a flowchart which shows an example of the procedure operation | movement for making the jump-in participant of 1st Embodiment join a future meeting. It is a figure which shows an example of the file management table used by 2nd Embodiment. It is a flowchart which shows the operation example of 2nd Embodiment. It is a figure which shows the example of a screen transition when adding the data of 2nd Embodiment. It is a figure explaining operation | movement when lending the owner authority of 2nd Embodiment temporarily.

(First embodiment)
FIG. 1 is a diagram illustrating an example of a system configuration of the embodiment. The conference management system 100 (file sharing system) includes a client PC 1, a management server 2, a document distribution server 3, and tablet terminals 4A to 4N.

  The client PC 1 is a terminal for uploading the created material file and inputting necessary information about the conference. The created material file is uploaded to the document distribution server 3 via the client PC 1. Information about the conference is input by the client PC 1 and transmitted to the management server 2. The client PC 1 is an input terminal dedicated to the conference management system 100, and does not accept conference information from PCs other than the client PC 1. However, each PC that an employee uses for business is directly used as a client PC 1. The implementation to be used may be used. That is, there may be a plurality of client PCs.

  The management server 2 is a server that receives conference information from the client PC 1 and manages it. Note that “management” in the present embodiment is a generic term for data search, new registration, deletion, and update operations. Each process of search, registration, deletion, and update is performed by receiving a request message from another device. It also includes a series of operations of performing ancillary processing if necessary, and returning the result to the device that sent the message.

  The document distribution server 3 is a server that permanently stores a document file used for a conference, and is requested when a file request message is received from the tablet terminals 4A to 4N, and the conditions such as the access right are satisfied. If the file is not satisfied, the file is not returned.

  The tablet terminals 4A to 4N are slate terminals provided with a user interface such as a touch panel, and are tablet PCs used during a conference here. In the following description, when it is not necessary to specify the tablet terminals 4A to 4N, they are referred to as tablet terminals 4.

  Each of these client PC 1, management server 2, document distribution server 3, and tablet terminal 4 communicate with each other via a network 50. The communication means of the client PC 1, the management server 2, and the document distribution server 3 is wired, and the communication means of the tablet terminal 4 is wireless, but the mode is not limited to this.

  FIG. 2 is a diagram showing an example of the hardware configuration inside the management server 2 and the document distribution server 3. In the following description, the management server 2 will be described, but the document distribution server 3 is the same. The reference numerals in parentheses in FIG. 2 are the reference numerals of the hardware inside the document distribution server 3.

  The management server 2 includes a processor 21 that is an arithmetic processing unit such as a CPU (Central Processing Unit) and an MPU (Micro Processing Unit), a RAM (Random Access Memory) 22 that is a volatile storage device, and a ROM that is a read-only storage device. (Read Only Memory) 23 and HDD (Hard disk drive) 24 which is a nonvolatile auxiliary storage device. In addition, an input device 25 such as a keyboard and a mouse, an output device 26 such as a monitor, and a network I / F (I / F: Interface) 27 that controls communication with an external device are included. Each of these devices transmits and receives data and signals to and from each other via the bus 28. Since this hardware configuration is the same as that of a conventional computer, detailed description thereof is omitted. A configuration without an input device or an output device may be used. The client PC 1 has the same configuration.

  FIG. 3 is a diagram illustrating an example of a hardware configuration inside the tablet terminal 4. The tablet terminal 4 includes a processor 41, a RAM 42, a ROM 43, and a network I / F 47. These functions are the same as those of the management server 2 described above. The tablet terminal 4 includes a flash memory 44 that is an auxiliary storage device that stores large data in a nonvolatile manner, and includes a touch panel display 45 that also serves as an input device and an output device. The tablet terminal 4 has a camera unit 48 including a lens and an image sensor, images the outside, and stores the image captured in the flash memory 44. Each of these units transmits and receives data via the bus 49. Since the internal configuration of the tablet terminal 4 is the same as the conventional configuration, detailed description thereof is omitted.

  Next, the operation of the conference management system 100 will be described. First, registration of conference information and uploading of material files will be described. FIG. 4 is a diagram illustrating an example of a table managed by the management server 2. In the following description, an employee ID (ID: Identification) is assigned to each employee, and it is assumed that the employee ID is used to log in to the client PC 1 or the tablet terminal 4. As a result, the employee is associated with the PC or terminal used by the employee.

  The person who sets up and registers the conference (hereinafter referred to as the conference owner or simply the owner) uses the date and time of the conference, the conference name, the employee ID of the participant of the conference, the name of the agenda held at the conference, and each agenda The name of the material file to be input is input on the client PC 1. After the input, when the conference owner presses a predetermined transmission button on the screen, the client PC 1 transmits the input information to the management server 2 together with the login user ID (owner employee ID). Although the owner participates in the conference, in this embodiment, it may be handled separately from the conference participation, such as a simple operator of the client PC 1.

  The management server 2 generates a conference ID based on the combination of the conference name and date information in the received information. The conference ID may be a combination of the conference name and the registration date / time. Further, the management server 2 derives the role values of the received participant information, and calculates the average value and the maximum value of the obtained role values.

  Here, the roll value will be described. In the present embodiment, authority is provided for each employee, and the management server 2 manages this authority value (role value) and employee identification information in association with each other. The role value means the access right to the file, and is defined based on the in-house title in this example, but the mode is not limited to this.

  The management server 2 holds the correspondence between the role value and the employee ID illustrated in FIG. 5, and derives each role value based on the received employee ID of the participant based on this correspondence. The role value is a value indicating an access authority to information. In this example, the role value is defined as an employee who has authority when the value is small and has no authority when the value is large. In addition, the calculation of the average value and the maximum value of the roll value is not considered for the owner in this embodiment, and is calculated only by the role value of the participant, but is calculated using the role value of the owner or the participant. May be.

  The management server 2 registers (stores) the conference ID, the date and time of the conference, the conference name, the owner's employee ID, the employee ID of the participant, the role average value, and the maximum role value as one record in its own HDD 24 (FIG. 4 (A)). In addition, the conference ID, the proposal number (the system assigns a number), the proposal name, and the file name of the material used in the proposal are associated with each other so as to be included in one record and registered in the HDD 24 (FIG. 4 ( B)).

  When the registration is completed, the management server 2 transmits a message to that effect to the client PC 1, transmits the generated conference ID to the client PC 1, and transmits the conference ID and the proposal name to the document distribution server 3.

  The document distribution server 3 creates a folder with the received meeting ID as an identification name in its own HDD 34, and further creates a subfolder with the proposal name as an identification name in the folder. Thereafter, the document distribution server 3 notifies the client PC 1 of a file transmission instruction directly or via the management server 2. Upon receiving the notification, the client PC 1 transmits the conference ID, the bill name, and the material file to the document distribution server 3. At this time, the agenda name and the material file are transmitted in a pair. The document distribution server 3 stores the corresponding material file in the agenda name folder in the created conference ID folder. In addition to this example, there are various modes for holding the document file.

  After the conference is set up and the material file is uploaded in this way, the conference is actually opened. The operation of downloading the material file at this time will be described. First, a participant in the conference performs a predetermined operation on the tablet terminal 4 logged in with his / her employee ID. The tablet terminal 4 receives, from the management server 2, a list of conference IDs in which the employee participates, by using this predetermined operation as a trigger, and displays it. The participant selects the conference ID to be performed this time from the displayed list.

  The tablet terminal 4 transmits the employee ID (login ID) and the selected conference ID to the document distribution server 3. The document distribution server 3 determines whether or not there is a folder with the conference ID or a document in the folder, and transmits the received employee ID and conference ID to the management server 2. The management server 2 determines whether there is a transmitted employee ID among the participant IDs included in the conference ID record. The determination result is returned to the document distribution server 3, and when the determination result is satisfactory, the document distribution server 3 transmits the document file in the folder to the tablet terminal 4 that is the transmission source. The conference participant acquires the conference material in this way. This operation is merely an example, and various operations can be constructed by design.

  An example of operation when a conference proceeds and a jump-in participant occurs will be described with reference to the flowchart of FIG. 6 and the schematic diagram of FIG. It is assumed that the tablet terminal of the existing participant is 4A and the tablet terminal of the jump-in participant is 4B.

  The tablet terminal 4A performs a procedure for setting sharing (ACT001), and issues a one-time password issuance request together with the ID of the current conference and the ID (login ID) of the employee using the tablet terminal 4A. Is transmitted to the management server 2 (ACT002). This operation is performed when the button B1 shown in FIG. 7 is pressed.

  The management server 2 determines whether or not a one-time password can be issued based on the transmitted employee ID (ACT003). This determination is made based on a roll value such as whether the employee ID is a participant in the conference or whether the roll value of the employee ID is below the average roll value of the conference. When the issue condition is not satisfied (ACT003, NG), the fact that the condition is not satisfied is transmitted to the tablet terminal 4A, and the process is terminated.

  In ACT002, when the ID of a jump-in participant is also transmitted, in ACT003, the employee of the jump-in participant such as whether the roll value of this ID is below the average roll value or below the maximum roll value, etc. When the determination is made based on the ID and the employee ID of the existing participant and the condition is not satisfied (when the roll value of the jump-in participant is high), that fact is transmitted and the process ends.

  When the issuance conditions are satisfied (ACT003, OK), the management server 2 generates a one-time password (first information) and transmits it to the tablet terminal 4A, and the tablet terminal 4A displays the received one-time password. (ACT004) (Refer to the right figure of the tablet terminal 4A in FIG. 7).

  The jump-in participant receives this one-time password from an employee (existing participant) who uses the tablet terminal 4A and inputs the password to the tablet terminal 4B used by the employee via the touch panel display 45 ( ACT005). When the transmission button B2 (see FIG. 7) is pressed after input, the tablet terminal 4B transmits the employee ID of the participant (login ID of the tablet terminal 4B) and the input password to the management server 2. Inquires about the validity of the password (ACT006). In addition, about this transmission, the tablet terminal 4B may calculate the hash value of an input password using a hash function, and the implementation which transmits this hash value may be sufficient.

  The management server 2 compares the password received from the tablet terminal 4B with the one-time password generated by itself (ACT007). When the data from the tablet terminal 4B is a hash value, the management server 2 calculates the hash value of the one-time password generated by itself using the same hash function as that of the tablet terminal 4B, and compares it. If the determination of ACT007 is bad (ACT007, NG), the fact that the password is different is transmitted to the tablet terminal 4B, and the process ends. When the determination of ACT007 is good (ACT007, OK), the management server 2 jumps into the participant column of the record, updates the employee ID of the participant, and transmits that the registration is completed to the tablet terminal 4B ( ACT008). Thereby, browsing of the material file of the jump-in participant is permitted.

  Thereafter, by performing the download procedure exemplified above, the material is distributed to the tablet terminal 4B and can be viewed (ACT009) (see also the right diagram of the terminal 4B in FIG. 7).

  The above is an example using a one-time password, but it may be performed with a QR code or a barcode. The management server 2 encodes the one-time password or a key to be replaced with a QR code or a barcode into a machine-readable format, and transmits the encoded image data to the tablet terminal 4A of the existing participant. The tablet terminal 4 </ b> A displays a QR code or barcode image transmitted to its own touch panel display 45. The camera unit 48 of the tablet terminal 4B captures an image of the displayed QR code or barcode. The processor 41 of the tablet terminal 4B obtains a code value (password or key) from the captured image and transmits it to the management server 2 via the network I / F 47. The subsequent operations are the same as those in ACT007 to ACT009.

  In addition to these methods, data can be transferred from the tablet terminals 4A to 4B using a proximity wireless communication such as infrared communication. When the proximity wireless communication means is included in the network I / F 47 for both the tablet terminals 4A and 4B, the passwords and keys issued from the management server 2 can be transmitted and received by bringing them close to each other.

In addition, the determination of ACT003 may be made by providing the following rules in addition to the above. These are merely examples, and various other implementations are possible.
1. Judgment based on roll average value When the roll value of a jump-in participant is lower than the roll average value of the conference (position is up), any one-time password issued to the tablet terminal 4 of any existing participant Allow jump-in, but if the roll value of the jump-in participant is higher than the roll average value (position is lower ) , payout to the tablet terminal 4 of the existing participant lower than the roll average value (position higher ) If you do not have a one-time password, you will not be allowed to jump in.
2. Judgment based on the maximum role value If the role value of the jumping participant is lower than the maximum role value (position is up), any existing participant's one-time password issued to the tablet terminal 4 jumps into the conference If the role value of a jump-in participant is higher than the maximum role value (position is lower), existing participants who are below the maximum role value (existing participants with the same value as the maximum role value are included) No one is allowed to jump in unless it is a one-time password issued to the tablet terminal 4.

  In addition, in the case of permitting in-participation participation for one agenda in the conference, the above example can be applied by associating participants for each agenda. Specifically, a participant column is further provided in the table shown in FIG. 4B, and IDs of employees who participate in each proposal are associated. When there is a jump-in participant, the tablet terminal 4A notifies the management server 2 of the name of the proposal with the jump-in participation at the processing timing of ACT001 or ACT002. If the processing from ACT003 to ACT007 continues, and if ACT007 is satisfactory, the management server 2 jumps into the participant column provided in the table of FIG. 4B at the timing of ACT008 and adds the participant ID. The document distribution server 3 performs a file distribution process based on the data in the participant column provided in the table of FIG. 4B at the timing of ACT009.

  FIG. 8 shows an operation example when adding a jump-in participant as a participant to a future conference when the conference with the jump-in participation is a regular conference.

  The meeting owner applies for the diversion creation of the next meeting on the application screen displayed on the client PC 1 (ACT 101). The management server 2 notifies the client PC 1 that there was a jump-in participant in the previous meeting and the name or employee ID of the jump-in participant (ACT 102). The client PC 1 displays this notification content in a dialog and also displays a button (a button labeled “Yes” or “No”) for inquiring of the owner whether or not to treat it as a participant in the next meeting.

  If the “Yes” button is pressed here (ACT 103, Yes), the conference server 2 adds the employee ID of the existing participant and the employee ID of the jump-in participant to the participant column, and displays the result in FIG. A record to be exemplified is newly registered (ACT 104). On the other hand, when the “No” button is pressed (ACT 103, No), the management server 2 does not add the employee ID of the jump-in participant to the participant column, but only the employee ID of the existing participant as shown in FIG. (1) is newly registered (ACT 105). In ACT 104 and ACT 105, the values that can be determined at the present time, such as the owner, the average roll value, and the maximum roll value, are entered, and the date and time column and the document column shown in FIG. For data that does not exist, a new record is registered as blank. The blank will be registered as soon as it is decided. Moreover, in ACT104 and ACT105, the process which updates the existing record which is the information about the last meeting instead of new registration may be sufficient.

(Second Embodiment)
In the second embodiment, an implementation example will be described in which a file brought by a participant and not scheduled to be used for a conference is added to a server as a material file during the conference. The system configuration, the hardware configuration of each device, and the data configuration will be described using the first embodiment as it is (see FIGS. 1 to 5). Moreover, the following description demonstrates the example of mounting which adds the file memorize | stored in the tablet terminal 4A jumping in during a meeting.

  In the second embodiment, the table illustrated in FIG. 9 is further managed and held by the management server 2. As shown in FIG. 9, the document file is associated with the file name, the file ID that uniquely defines the file, the ID of the employee who created the file (“owner ID” in FIG. 9), and the viewing attribute. When the viewing attribute is “event”, the conference ID is also associated. The viewing attribute is data indicating an access range, and only the user who created the file can view or modify the “private” file. In addition, a file with the viewing attribute “event” is a file that can be browsed and modified by the user who created the file, and can be viewed by the participants of the meeting regarding the associated conference ID.

  FIG. 10 is a flowchart illustrating an operation example of the conference management system according to the second embodiment. The user displays a file to be added as conference material on the tablet terminal 4A, and presses the “file sharing” button (ACT 201). FIG. 11A is a diagram showing a state displayed on the tablet terminal 4A at this time. A user who is using the tablet terminal 4A during a meeting displays a file to be added as a document and presses a button B3 displayed by a predetermined operation. Accordingly, the tablet terminal 4A displays a conference list to which materials are added (see FIG. 11B). The operation at this time will be described. The tablet terminal 4 </ b> A transmits the login ID (employee ID) of the user who is using the tablet terminal 4 </ b> A to the management server 2. The management server 2 searches the table shown in FIG. 4A for the ID of the conference in which the user having the ID participates. The management server 2 transmits all the conference IDs obtained from the search results to the tablet terminal 4A, and the tablet terminal 4A receives the conference ID and displays a list in the dialog D1 (see FIG. 11B).

  After the display shown in FIG. 11B, the user selects a conference ID for sharing the file from the list (ACT 202). In this example, it is assumed that the meeting “2011031711000-Sales PJ” is selected. The tablet terminal 4A transmits a message of a file sharing request to the management server 2 together with the selected conference ID (2011031711000-sales PJ) (ACT 203). The management server 2 determines whether the previously transmitted employee ID is a participant in the meeting, or compares and determines the role value of the employee ID and the roll average value and the maximum roll value of the meeting. Thus, the request is verified (ACT 204). When the condition is not satisfied (ACT 204, NG), a message indicating that fact is transmitted to the tablet terminal 4A, and the process ends. On the other hand, if the condition is satisfied (ACT 204, OK), the management server 2 permits the file sharing for the conference “2011031711000-sales PJ”, and allows the tablet terminal 4A and the document distribution server 3 to share the file. A key (referred to as K1 in this example) is issued (ACT 205). The tablet terminal 4A and the document distribution server 3 receive the key K1 from the management server 2.

  The tablet terminal 4A transmits to the document distribution server 3 the file to be added as the material, the key K1, and the ID of the conference to be added (2011031711000-sales PJ) (ACT 206). The document distribution server 3 receives the file and the key K1, and verifies whether the key K1 previously transmitted from the management server 2 matches the key transmitted from the tablet terminal 4A. If it is, the file is added and held in the folder whose folder name is the conference ID (ACT 207). In addition, since the name of the agenda cannot be known at the present time, in this embodiment, an additional file is stored immediately below the conference ID folder. Also, the file name of the added file and a message indicating that the file has been added are transmitted to the management server 2.

  The management server 2 receives this message, registers a new record in the table shown in FIG. 4B, and registers the received file name in the document column. Note that the agenda number and agenda name cannot be known at this stage, so there is no value.

  When the additional file is not registered in the table shown in FIG. 9, the management server 2 creates a record for the additional file. That is, the management server 2 pays out the file ID and registers the file name, the owner, the viewing attribute (becomes “event”), and the conference ID in association with each other so as to form one record. If the additional file is a file already registered in FIG. 9, the management server 2 updates the viewing attribute from “private” to “event” and associates the conference ID with it.

  When the update or registration of each data table is completed, the management server 2 transmits a message indicating that the file has been added to the tablet terminal 4 to which the participant participating in the conference has logged in (ACT 208). . A display example of the tablet terminal 4 at this time is shown in FIG. Since the viewing attribute of the added file is “event”, other conference participants can also browse the additional file.

  Also, in the above flow, it is possible to specify a bill associated with the conference instead of specifying the conference. In this case, in ACT 202, it is possible to add a material file to the meeting proposal by specifying the proposal after the meeting is specified.

In addition, there are a method of giving sharing authority to all the conference participants belonging to the conference “2011031711000-sales PJ” and a method of giving sharing authority by the in-house role value. For example, in the case of the conference “2011031711000-Sales PJ”,
-President A and General Manager B, who are members of role values below the in-house role average value of 2.7, have sharing authority.
・ President A, general manager B, and employee J, who are members with a role value of 5 or less within the company role, have sharing authority.
It is also possible to limit sharing authority by such a method.

Further, an implementation example in which files are added by other participants when only the meeting owner can add a file due to the security policy will be described with reference to FIG. The tablet terminal 4A of the participant who desires to add a file communicates with the tablet terminal (4C in this example) logged in with the owner authority by using proximity communication or the like, and temporarily grants the owner authority. To add the file to the meeting. The method is described below.
(ACT301) The tablet terminal 4A presses the “Share this file” button B3 while displaying a file belonging to “private” to be shared.
(ACT 302) The tablet terminal 4A displays a screen for selecting a shared conference belonging to “event” (see FIG. 11B). Here, it is assumed that the conference “2011031711000-Sales PJ” is selected as the conference to which the file is added.
(ACT 303) The tablet terminal 4A performs proximity communication with the tablet terminal 4C logged in with the owner authority, and requests temporary grant of the owner authority to the tablet terminal 4A.
(ACT 304) When the tablet terminal 4C receives a request for temporary grant of owner authority from the tablet terminal 4A, the tablet terminal 4C refers to the role value held in the management server 2 with respect to the tablet terminal 4A. After determining whether to grant temporarily, temporary grant is determined.
(ACT 305) The tablet terminal 4C issues a key (here referred to as key K2) having owner authority to the tablet terminal 4A using proximity communication or the like. This key K2 is a key issued from the management server 2.
(ACT 306) The tablet terminal 4A to which the owner authority is temporarily given sends the additional file for the conference “2011031711000-sales PJ” together with the key K2 to the document distribution server 3 and requests it.
(ACT307) Upon receiving the file AP and the key K2 from the tablet terminal 4A, the document distribution server 3 requests the management server 2 to validate the key AP2 together with the key K2.
(ACT 308) The management server 2 verifies the validity, for example, whether the issued key K2 and the key transmitted from the document distribution server 3 match. Allow adding files.
(ACT309) The document distribution server 3 adds a file.
(ACT 310) The management server 2 notifies the electronic browsing terminal 4B to which the participant participating in the conference has logged in that the file has been added to the conference “2011031711000-Sales PJ”. At this time, information about the additional file is also added and updated in each data table.

  Further, in the above ACT 305, it is possible to take a form in which the one-time password is displayed on the tablet terminal 4C and is input on the tablet terminal 4A instead of the proximity communication.

  In the first and second embodiments, a server that manages general information is referred to as a management server 2, and a server that manages files is referred to as a document distribution server 3, as shown in FIGS. 4, 5, and 9. Although the table has been described as being stored in the management server 2, the aspect is not limited to this. A part of the data table may be stored in the document distribution server 3, or the document distribution server 3 may be responsible for a part of the function of the management server 2. Conversely, the management server 2 may be responsible for some of the functions of the document distribution server 3. This depends on the server configuration and hardware performance. Moreover, the implementation which one server housing | casing may store all the information and process execution may be sufficient.

  Moreover, the aspect demonstrated in 1st Embodiment and the aspect demonstrated in 2nd Embodiment can also be combined.

  The first information corresponds to a one-time password, a key, a QR code, and a barcode in this embodiment. These pieces of information are information paid out from the server as temporarily valid information in the present embodiment.

  As described in detail above, according to the technology of one aspect described in this specification, whether or not browsing on another terminal is determined through a terminal that has already been permitted to browse the predetermined file, For example, even when a jump-in participant occurs at a meeting or the like, information on a predetermined file can be provided to the person while ensuring confidentiality, and information can be shared.

  In addition, according to the technique of one aspect described in this specification, it is possible to add information about a file used for the meeting and information about the file to be added to the participant even during the meeting.

  The present invention can be implemented in various other forms without departing from the spirit or main features thereof. Therefore, the above-described embodiment is merely an example in all respects and should not be interpreted in a limited manner. The scope of the present invention is indicated by the scope of claims, and is not restricted by the text of the specification. Further, all modifications, various improvements, alternatives and modifications belonging to the equivalent scope of the claims are all within the scope of the present invention.

  1 client PC, 2 management server, 3 document distribution server, 4A to 4N tablet terminal, 100 conference management system.

Claims (3)

When receiving identification information and a request message of a meeting participant from a terminal, and permitting browsing by the terminal of a file used in the meeting based on the identification information, first information is generated and transmitted to the terminal And a server to
A first terminal for receiving said first information identification information and the request message of the first participant that is configured as a participant to send to the server of the meeting, the view of the file is allowed,
The first information received by the first terminal is acquired, and the first information, or information derived based on the first information, and identification information of a second participant not set as a participant in the meeting and a second terminal for transmitting,
The server permits the second terminal to view the file when the access authority of the second participant is higher than the average access authority to the file of all the participants of the meeting, and the average access authority If the access authority of the second participant is lower, or if the access authority of the first participant is lower than the average access authority, the second participant is not permitted to view the file, and the first participant A file sharing system that permits the second terminal to view the file when the access authority is higher than the average access authority . When receiving identification information and a request message of a meeting participant from a terminal, and permitting browsing by the terminal of a file used in the meeting based on the identification information, first information is generated and transmitted to the terminal And a server to
A first terminal that is permitted to view the file, and transmits the identification information and request message of the first participant set as a participant of the meeting to the server and receives the first information;
The first information received by the first terminal is acquired, and the first information, or information derived based on the first information, and identification information of a second participant not set as a participant in the meeting A second terminal that transmits
The server permits the second terminal to view the file when the second participant's access authority to the file is higher than the lowest access authority of all the participants in the meeting. If the access authority of the second participant is lower than the lowest access authority, and if the first participant is a participant with the lowest access authority, the second terminal is not permitted to view the file. A file sharing system that permits browsing of the file by the second terminal when the first participant is not the participant with the lowest access authority. The file sharing system according to claim 1 or 2 ,
The first terminal further displays the first information,
Said second terminal, said first said first information displayed on the terminal that is manually input by the user via the input unit, a file sharing system for acquiring the first information.

Images