JP2011113371A - Conference material data management system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a conference material data management system for restricting access to conference material data recorded in a server apparatus by simple operation without using an dedicated terminal. <P>SOLUTION: A conference material management server apparatus 10 includes a table in which conference material data, information concerned with conference participants and a security code for controlling access to the conference material data are associated with one another to be recorded to control access to the conference material data. A security code writing/reading device 20 receives a security code transmitted from the conference material management server apparatus 10 and writes the received code in an ID code 40 owned by each conference participant. The conference material management server apparatus 10 receives a security code transmitted from a conference material reading terminal A31, and when the code has been already recorded into the table, permits access to conference material data recorded by being associated with the code. <P>COPYRIGHT: (C)2011,JPO&INPIT

Description

  The present invention relates to a conference material data management system, and more particularly to a conference material data management system that controls access to conference material data.

  Conventionally, conference materials are recorded and managed in a file server device after being digitized. The conference participant accesses the conference material data recorded in the file server device and uses the data.

  Various techniques for improving convenience in accessing such conference material data have been proposed. For example, Patent Document 1 simplifies access to conference participant data by transmitting the recording destination information of conference material data referenced (displayed) during the conference to the terminal of the conference participant. Technology is disclosed.

  Various techniques for preventing unauthorized access to a network to which a file server device or the like is connected have been proposed. For example, Patent Document 2 reads ID card data held by a user of a personal computer accessing the network, and prevents unauthorized access to the network by a person who does not have access permission to the network based on the read data (ID data). Techniques to do this are disclosed.

JP 2002-49595 A JP 2006-293508 A

  In order to prevent information leakage of the conference material data, it is necessary to limit access to the conference material data recorded in the file server device to a specific person such as a conference organizer or a conference participant.

  If the technique disclosed in Patent Document 1 is used, the recording destination information of the conference material data is transmitted to the terminal of the conference participant, so that the access to the conference material data can be restricted only to the conference participant. However, if a person other than the conference participant, for example, illegally looks at the recording destination information of the conference material data (peeps) and knows the recording destination information of the conference material data, the conference material data can be easily accessed. Yes, there is a risk of information leakage.

  In addition, since the conference participants must have a terminal that can receive the recording destination information of the conference material data, if you forget the terminal or if the battery of the terminal runs out, the conference material data Can not access.

  Further, the technology disclosed in Patent Document 2 only prevents unauthorized access to the network, and does not prevent unauthorized access to individual conference material data.

  The present invention has been made in view of such circumstances, and provides a conference material data management system that restricts access to conference material data recorded in a server device with a simple operation without using a dedicated terminal. With the goal.

  The first technical means includes a recording unit that records conference material data, and a table that records at least information related to conference participants and a security code for access control to the conference material data of the conference in association with each other. A security code writing device that receives the security code transmitted from the server device and writes the received security code in a memory of an ID card possessed by a participant in the conference, and the ID A security code written in the memory of the card is read, transmitted to the server device, and connected to a terminal that requests access to the conference material data recorded in the server device. The transmitted security code is received, and the security code is When recorded in the table is the conference material data management system and permits access to the conference material data recorded in correspondence with the security code.

  According to a second technical means, in the first technical means, the server device records an access authority level indicating an access level for the conference material data in the table for each participant of the conference or for each conference material data. Even if access to the conference material data for the conference participants is permitted, the access to the conference material data for the conference participants is further controlled based on the access authority level. It is characterized by.

  According to a third technical means, in the first technical means, the server device records identification information for identifying the terminal such as an IP address in the table for each participant of the conference or for each conference material data, Permitting the participants of the conference to access the conference material data when the identification information for identifying the terminal such as the IP address transmitted from the terminal matches the identification information recorded in the table. It is a feature.

  According to a fourth technical means, in the first technical means, the server device detects a reception time of the security code transmitted from the terminal, and permits access to the conference material data for the conference participants. Even if it is, the access to the conference material data for the participants of the conference is further controlled based on the reception time.

  A fifth technical means is the fourth technical means, wherein the server device records a conference opening time in the table and receives the security code transmitted from the terminal within the conference holding time. Access to the conference material data is permitted for participants of the conference.

  A sixth technical means is characterized in that, in any one of the first to fifth technical means, the server device and the terminal are integrally formed.

  A seventh technical means is the security code writing apparatus according to any one of the first to fifth technical means, wherein the security code writing device is provided in an entrance management device that manages opening and closing of a door for entering and exiting a conference room. When the security code transmitted from the server device is received, the entrance management device unlocks the entrance door of the conference room.

  According to the present invention, the security code for controlling access to the conference material data recorded in the server device is recorded on the ID card of the conference participant or the like, and access to the conference material data is restricted based on this security code. Access to the conference material data can be restricted with a simple operation without requiring a terminal.

1 is a schematic diagram of a conference material data management system according to the present invention. FIG. It is a functional block diagram of a conference material management server device, a security code writing / reading device, and a conference material browsing terminal. It is an example of a meeting material registration table. It is a flowchart explaining the registration process of the information relevant to a meeting. It is a flowchart explaining the process which writes the produced | generated security code in a conference participant's ID card. It is a flowchart explaining the process in which the owner of an ID card accesses meeting material data using the ID card in which the security code is written. It is an example of the meeting material registration table in which the access authority level was recorded. It is an example of the conference material registration table in which the IP address of the conference material browsing terminal is recorded as the security level. It is another functional block diagram of a meeting material management server apparatus. It is the schematic of a meeting material data management system at the time of providing a security code writing / reading apparatus in an entrance management apparatus.

  FIG. 1A is a schematic diagram of a conference material data management system 1 according to the present invention. The conference material data management system 1 includes a conference material management server device (server device) 10, a security code writing / reading device (security code). Writing device) 20, a conference material browsing terminal A31 such as a PC, and a conference material browsing terminal B32. The devices (10, 20) and the terminals (A31, B32) are connected via, for example, the network N, but the devices (10, 20) and terminals (A31, B32) are not connected via the network N. ) May be connected to each other.

  FIG. 1B is a diagram for explaining a storage medium possessed by a conference participant or the like, for example, an ID card 40 that also functions as an employee ID card. The ID card 40 has a memory 41 for storing various types of data. 41 has an area for storing the owner name of the ID card 40, a security code to be described later, and the like. In addition to the owner name, for example, an ID such as an employee number may be used.

  The conference material management server device 10 includes a recording unit that records conference material data, and a table that records at least information related to conference participants and a security code for access control for conference material data in association with each other. Control access to document data. In addition, the conference material management server device 10 transmits a security code to the security code writing / reading device 20.

  For example, the security code writing / reading device 20 is provided in the conference room, receives the security code transmitted from the conference material management server device 10, and writes the security code to the ID card 40 possessed by the conference participant. Execute.

  The conference material browsing terminal A31 is provided, for example, in a conference room, and the terminal B32 is provided outside the conference room. The conference material browsing terminal A31 or the like reads the security code written in the ID card 40 possessed by the conference participant and transmits it to the conference material management server device 10, whereby the conference material recorded in the conference material management server device 10 is recorded. Request access to data.

The conference material management server device 10 receives the security code transmitted from the conference material browsing terminal A31 or the like, and when the security code is recorded in the table, it is recorded corresponding to the security code. Allow access to meeting material data.
Since the conference material browsing terminal A31 and the terminal B32 are terminals having the same function, both terminals A31 and B32 will be described as the conference material browsing terminal 30 (see FIG. 2) in the following description.

FIG. 2 is a functional block diagram of the conference material management server device 10, the security code writing / reading device 20, and the conference material browsing terminal 30. Although not shown, the devices (10, 20) and the terminal 30 are connected via the network N (see FIG. 1).
(Meeting Material Management Server Device 10)
The functional blocks of the conference material management server device 10 will be described.
Reference numeral 101 denotes a network I / F that provides an interface function to the network N and executes data transmission / reception with other devices such as the security code writing / reading device 20 connected to the network N.

  An input I / F 102 provides an interface function for an input device (not shown) such as a keyboard and a mouse. Reference numeral 103 denotes a display I / F that provides an interface function for a display device (not shown) such as a liquid crystal panel.

  Reference numeral 104 denotes a memory composed of a ROM, a RAM, and the like for storing various control information. Reference numeral 105 denotes an application such as word processing software, spreadsheet software, presentation software, a browser, and an HDD for recording various data.

  Reference numeral 111 denotes a conference material data recording unit which records conference material data created by the conference organizer or the like before the conference using word processing software, presentation software, or the like. It is also possible to record data such as meeting material data created during the meeting or minutes created after the meeting.

Reference numeral 112 denotes a conference material data registration unit, for example, a conference name (conference name) and a conference held by the conference organizer or the like input to the conference material registration table 51 shown in FIG. 3 via the input I / F 102. The time, the name of the conference material data recorded in the conference material data recording unit 111, the recording destination information, the conference organizer, and information related to the conference participants are recorded.
The information related to the meeting organizer and the meeting participant means an ID such as a name and an employee number, as well as a department to which the affiliation belongs, a job title, and the like. In addition to the name of the conference, a conference room number or the like may be recorded.

  In the conference material registration table 51 of FIG. 3, at least information related to the participants of the conference and a security code (described later) for the conference material data of the conference may be recorded. Here, the conference name, holding time ( Schedule), the name of the meeting material data used for the meeting, the recording destination information of the data, the name of the meeting organizer, the name of the participant, and the security code are recorded.

Reference numeral 113 denotes a conference material data access control unit that controls data access to the conference material data recorded in the conference material registration table 51.
The security code generation unit 113a generates a security code required when a conference participant or the like accesses the conference material data. The security code is recorded in the conference material registration table 51 of FIG. The security code may be composed of, for example, a meeting name, a meeting room number, and a meeting holding time.

  As will be described later, the security code generated by the security code generation unit 113a is written in the ID card 40 of a conference participant or the like.

Reference numeral 114 denotes a data transmission unit that executes various data transmission processes. For example, the security code generated by the security code generation unit 113 a is transmitted to the security code writing / reading device 20.
Reference numeral 115 denotes a data receiving unit that executes various data receiving processes, and receives, for example, a command (hereinafter referred to as a data access command) that requests access to conference material data transmitted from the conference material browsing terminal 30. The data access command will be described later.
Reference numeral 116 denotes a control unit that controls each functional block.

(Security code writing / reading device 20)
A functional block of the security code writing / reading device 20 will be described.
Reference numeral 201 denotes a network I / F that provides an interface function for the network N and executes data transmission / reception with other devices such as the conference material management server device 10 connected to the network N.

  A card reader / writer 202 is hardware that executes a process of reading data stored in the memory 41 of the ID card 40 and a process of writing data to the memory 41.

  A data reading unit 203 controls a process of reading various data such as an owner name of the ID card 40 stored in the memory 41 of the ID card 40.

  Reference numeral 204 denotes a security code request command generation unit. The security code request command is a conference material management so that the security code corresponding to the owner name (meeting organizer, meeting participant) of the ID card 40 read by the data reading unit 203 is transmitted to the security code writing / reading device 20. This is a command requested to the server device 10 and includes the owner name of the ID card 40.

  Reference numeral 205 denotes a data transmission unit that executes various data transmission processes. For example, the security code request command generated by the security code request command generation unit 204 is transmitted to the conference material management server apparatus 10.

A data receiving unit 206 executes various data receiving processes, and controls, for example, a process of receiving a security code transmitted from the conference material management server apparatus 10.
Reference numeral 207 denotes a data writing unit which controls a process of writing, for example, a security code received by the data receiving unit 206 in the memory 41 of the ID card 40.

Reference numeral 208 denotes a memory for temporarily storing data. For example, the data stored in the memory 41 of the ID card 40 read by the data reading unit 203 and the security code received by the data receiving unit 206 are temporarily stored. To do.
A control unit 209 controls each functional block.

(Meeting document browsing terminal 30)
The functional blocks of the conference material browsing terminal 30 will be described.
Reference numeral 301 denotes a network I / F that provides an interface function to the network N and executes data transmission / reception with other devices such as the conference material management server device 10 connected to the network N.

  An input I / F 302 provides an interface function for an input device (not shown) such as a keyboard and a mouse. Reference numeral 303 denotes a display I / F, which provides an interface function for a display device (not shown) such as a liquid crystal panel.

  Reference numeral 304 denotes a memory composed of a ROM, a RAM, and the like for storing various control information. Reference numeral 305 denotes an application such as word processing software, spreadsheet software, a browser, and an HDD for recording various data.

  Reference numeral 311 denotes a card reader, which is hardware that executes processing for reading data stored in the memory 41 of the ID card 40.

  Reference numeral 312 denotes a data reading unit that controls processing for reading various data stored in the memory 41 of the ID card 40 such as an owner name of the ID card 40.

A data access unit 313 executes an access process to the conference material data recorded in the conference material data recording unit 111 of the conference material management server device 10.
The data access command generation unit 313a generates a conference material data access command (hereinafter referred to as a data access command) used for accessing the conference material data.

  The data access command is a command for requesting the server device 10 to access the conference material data recorded in the conference material management server device 10, and the owner name of the ID card 40 read by the data reading unit 312 and the security code Is included.

  Reference numeral 314 denotes a data transmission unit that executes various data transmission processes. For example, the data access command generated by the data access command generation unit 313 a is transmitted to the conference material management server apparatus 10.

  Reference numeral 315 denotes a data receiving unit that executes various data receiving processes, and controls, for example, processing for receiving conference material data transmitted (response) by the conference material management server device 10 based on a data access command transmitted by the data transmitting unit 314. To do.

  Reference numeral 316 denotes a control unit that controls each functional block.

Hereinafter, the process of controlling access to conference material data executed by the conference material data management system 1 according to the present invention will be described with reference to the flowcharts of FIGS.
FIG. 4 is a flowchart for explaining registration processing of information related to the conference. It is assumed that the conference material data used in the conference is already recorded in the conference material data recording unit 111 of the conference material management server device 10.

First, the meeting organizer, via the input I / F 102 of the meeting material management server apparatus 10, names of the meeting scheduled to be held, holding time (scheduled), name of meeting material data used for the meeting, and recording destination of the data Information, conference organizer name, and conference participant name are input (step S1).
When the input in step S1 ends, the conference material data registration unit 112 records the information input in step S1 in each corresponding column of the conference material registration table 51 in FIG. 3 (step S2).

Next, the security code generation unit 113a generates a security code for each conference organizer and conference participant recorded in the conference material registration table 51 in FIG. 3, and records the generated security code in the table 51 (step). S3).
In the example of FIG. 3, the security code “DEV_CONF1220_AABB” is recorded corresponding to the conference organizer “AABB”, and the security code “DEV_CONF1220_CCDD” is recorded corresponding to the conference participant “CCDD”.
This completes the registration process for information related to the conference.

Next, a process of writing the generated security code to the conference participant ID card 40 will be described with reference to the flowchart of FIG.
For example, “CCDD” as a conference participant enters the conference room and passes his / her ID card 40 through the card reader / writer 202 of the security code writing / reading device 20 (step S11).
The data reading unit 203 reads the owner name (“CCDD”) of the ID card 40 stored in the memory 41 of the ID card 40 (step S12), and outputs it to the security code request command generation unit 204.

  Upon receiving the owner name, the security code request command generation unit 204 generates a security code request command including the owner name (step S13) and outputs it to the data transmission unit 205. Note that the security code request command may include a conference room number or the like.

  The data transmitting unit 205 that has received the security code request command transmits the security code request command to the conference material management server apparatus 10 (step S14).

  The data receiving unit 115 of the conference material management server apparatus 10 receives the security code request command (step S15) and outputs it to the conference material data access control unit 113.

  Upon receiving the security code request command, the conference material data access control unit 113 extracts the owner name (“CCDD”) from the security code request command (step S16), and the owner name is the conference material in FIG. It is detected whether or not it is recorded in the registration table 51 (step S17). When the conference room number is included in the security code request command, it is detected whether this conference room number is recorded in the table 51.

  When the owner name (“CDDD”) is recorded in the conference material registration table 51 of FIG. 3 (step S18 / YES), the conference material data access control unit 113 uses the security code via the data transmission unit 114. A security code (“DEV_CONF1220_CCDD”) corresponding to the owner name (“CCDD”) is transmitted to the writing / reading device 20 (step S19).

  The data receiving unit 206 of the security code writing / reading apparatus 20 receives the security code (step S20) and outputs it to the data writing unit 207.

  The data writing unit 207 that has received the security code writes the security code (“DEV_CONF1220_CCDD”) in the memory 41 of the ID card 40 (step S21).

  In step S18, if the input owner name is not recorded in the conference material registration table 51 of FIG. 3 (step S18 / NO), the conference material data access control unit 113 passes the data transmission unit 114. The NG code may be transmitted to the security code writing / reading device 20. Upon receiving the NG code, the security code writing / reading apparatus 20 displays on the display panel (not shown) that the owner of the ID card 40 is not a conference participant.

  This completes the process of writing the generated security code to the conference participant's ID card 40.

  Next, a process in which the owner “CCDD” of the ID card 40 accesses the conference material data using the ID card 40 in which the security code is written will be described using the flowchart of FIG.

First, the owner “CDDD” of the ID card 40 passes his / her ID card 40 through the card reader 311 of the conference material browsing terminal 30 (step S31).
The data reading unit 312 reads the owner name (“CCDD”) and security code (“DEV_CONF1220_CCDD”) of the ID card 40 stored in the memory 41 of the ID card 40 (step S32), and outputs them to the data access unit 313. To do.

  The data access command generation unit 313a of the data access unit 313 that has received the security code or the like generates a data access command including the owner name and security code read by the data reading unit 312 (step S33), and the data transmission unit 314 Output to.

  The data transmission unit 314 that has received the data access command transmits the data access command to the conference material management server apparatus 10 (step S34).

  The data receiving unit 115 of the conference material management server apparatus 10 receives the data access command (step S35) and outputs it to the conference material data access control unit 113.

  Upon receiving the data access command, the conference material data access control unit 113 extracts a security code from the data access command (step S36), and whether or not the security code is recorded in the conference material registration table 51 of FIG. Is detected (step S37).

  When the security code is recorded in the conference material registration table 51 of FIG. 3 (step S38 / YES), the conference material data access control unit 113 sets the conference material data corresponding to the security code (development conference material, specifications, An access permission command for permitting access to the design drawing) is transmitted to the conference material browsing terminal 30 (step S39).

  The data receiving unit 315 of the conference material browsing terminal 30 receives the access permission command (step S40) and outputs it to the data access unit 313. The conference material browsing terminal 30 can access the conference material data corresponding to the security code (step S41). In the example of FIG. 3, the owner “CCDD” of the ID card 40 can access conference material data such as development conference materials, specifications, and design drawings corresponding to the security code (“DEV_CONF1220_CCDD”).

  That is, the conference material data access control unit 113 of the conference material management server device 10 permits access to the conference material data corresponding to the security code from the conference material browsing terminal 30 that has transmitted the access permission command.

  Various access methods can be used. For example, if the conference material management server apparatus 10 has a WEB server function, the conference material data can be accessed (browser display) from the conference material browsing terminal 30 via a browser. Further, the conference material data may be transmitted to the conference material browsing terminal 30 together with the access permission command.

  If the security code is not recorded in the conference material registration table 51 of FIG. 3 (step S38 / NO), the conference material data access control unit 113 sends the conference material data to the conference material browsing terminal 30 via the data transmission unit 114. NG code is transmitted. The conference material browsing terminal 30 that has received the NG code displays via the display I / F 303 that the conference material data cannot be accessed.

  As described above, since the security code for controlling access to the conference material data is written in an ID card such as an employee ID card that is always carried when in the office, the employee does not need to have a dedicated terminal. Then, using the ID card in which the security code is written, the conference material data can be accessed from the conference material browsing terminal 30 with a simple operation, and the convenience of the conference participant is improved. Further, access to the conference material data from a person who does not have the ID card can be denied.

(Example 2)
The conference material management server device 10 records the access authority level in the conference material registration table for each conference participant or conference material data, and even if access to the conference material data is permitted for the conference participants, Based on the access authority level, access to the conference material data for the conference participants may be further controlled. The access authority level means, for example, an access level to the conference material data such that the conference material data can be browsed, cannot be edited (enabled), and cannot be copied (enabled).

FIG. 7 is a conference material registration table 52 in which the access authority level is recorded. Here, for each conference participant including the conference organizer, each conference material data (development conference material, specifications, design drawing) is shown. The access authority level is recorded.
For example, when the conference material data access control unit 113 of the conference material management server device 10 receives an access request (data access command) to the conference material data by the conference participant “CCDD”, the control unit 113 Only viewing is allowed, editing and copying are not allowed. The access authority level may be recorded for each conference material data.

  In addition, a security code generated by the security code generation unit 113a may be used. In this case, the security code generation unit 113a includes the access authority level in the security code corresponding to the conference material data and the conference participant (host). For example, in the example of FIG. 7, the access of the conference participant “CCDD” to the “specification document” (D: ¥ devconf1220 ¥ SPEC.pdf), which is the conference material data, includes the security code DEV_CONF1220_CCDD_SPEC_ONLY_VIW etc. Generate.

  Based on the security code, the conference material data access control unit 113 allows only the browsing of the conference participant “CCDD” to access the “specification” that is the conference material data.

(Example 3)
The conference material management server device 10 records identification information for identifying the conference material browsing terminal 30 such as an IP address in the conference material registration table for each conference participant or for each conference material data, and is transmitted from the conference material browsing terminal 30. If the identification information matches the identification information recorded in the conference material registration table, the conference participant may be permitted to access the conference material data.

FIG. 8 is a conference material registration table 52 in which the IP address of the conference material browsing terminal is recorded as the security level. Here, the IP address is recorded for each conference participant including the conference organizer.
Security level refers to, for example, restricting access to conference material data such as confidential to the department, confidential to the public, or unlimited. In the case of confidentiality, the conference material can be viewed in the department related to the conference (for example, development department room). Only the access from the terminal 30 is possible. In the case of confidential inside, only the access from the conference material browsing terminal 30 arranged in the company is possible. In the unlimited case, the access level is permitted even from the external PC. means.

  For example, when the conference material data access control unit 113 of the conference material management server apparatus 10 receives an access request (data access command) for conference material data by the conference participant “CCDD”, the control unit 113 is included in the data access command. The IP address of the conference material browsing terminal 30 is extracted. Then, the conference material data access control unit 113, when this IP address is “192.168.253.130” or “192.168.253.131”, only the conference material data for the conference participant “CCDD”. Permit access to (development meeting materials, specifications, blueprints). This IP address is assumed to be the IP address of the conference material browsing terminal 30 located in the department related to the conference.

  As the identification information for identifying the conference material browsing terminal 30, when the communication between the conference material management server device 10 and the conference material browsing terminal 30 is executed using TCP / IP, the conference material included in the communication packet is used. It is preferable to use the IP address or MAC address of the browsing terminal 30. In addition, an identification name (PC name) assigned to the conference material browsing terminal 30 can also be used.

A security level may be set for each position.
By limiting the access authority level / security level in this way, the security for the conference material data is improved.

Example 4
The conference material data access control unit 113 of the conference material management server device 10 detects the reception time of the data access command including the security code transmitted from the conference material browsing terminal 30 and, as described above, the conference material for the conference participants. Even if access to data is permitted, access to the conference material data for the participants of the conference may be further controlled based on the reception time.

  For example, the access to the conference material data for the conference participants may be permitted only when the security code transmitted from the conference material browsing terminal 30 is received within the conference opening time. In this case, it is determined whether access is permitted or not with reference to the conference opening time recorded in the conference material registration table 51 shown in FIG. In addition, what is necessary is just to utilize the time measuring function (clock function) with which the control part 316 of the meeting material browsing terminal 30 is equipped for the detection of the said reception time.

  In addition, when it is detected that the predetermined date and time has passed since the conference opening time, the conference material data access control unit 113 lowers the access authority level / security level described in the second and third embodiments, and the conference participants If so, it may be freely accessible (editing, copying, etc.).

(Example 5)
In the above embodiment, the conference material management server device 10 and the conference material browsing terminal 30 are separate bodies. However, the conference material management server device 10 and the conference material browsing terminal 30 may be configured integrally, for example, The functional block of the conference material browsing terminal 30 may be incorporated in the conference material management server device 10.

  FIG. 9 is a functional block diagram of the conference material management server device 50 in which the conference material management server device 10 and the conference material browsing terminal 30 are configured integrally. The conference material management server device 50 and the security code writing / reading device 20 may be directly connected without going through the network N.

  The functional block of the conference material management server apparatus 10 shown in FIG. 2 and the block having the same function as the functional block of the conference material browsing terminal 30 are denoted by the same reference numerals and description thereof is omitted.

  Reference numeral 115 ′ denotes a data receiving unit that executes various data receiving processes. Unlike the data receiving unit 115 described with reference to FIG. 2, the receiving process of the data access command transmitted from the conference material browsing terminal 30 is not performed.

  In this case, the process of accessing the conference material data by the owner “CCDD” of the ID card 40 using the ID card 40 in which the security code is written is executed as follows. Note that the conference material management server device 50 generates a security code, and further transmits the security code to the security code writing / reading device 20, and the security code writing / reading device 20 writes the security code to the ID card 40. Is the same as the processing described in FIG. 4 and FIG.

  First, the owner “CCDD” of the ID card 40 passes his / her ID card 40 through the card reader 311 of the conference material management server device 50. The data reading unit 312 reads the owner name and security code of the ID card 40 stored in the memory 41 of the ID card 40 and outputs them to the data access unit 313.

  The data access command generation unit 313a of the data access unit 313 that has received the security code or the like generates a data access command including the owner name and security code read by the data reading unit 312 and accesses the data access command to the conference material data access Output to the control unit 113.

  Thereafter, the conference material data access control unit 113 detects whether or not the security code of the data access command is recorded in the conference material registration table 51 of FIG. If recorded, the conference material data access control unit 113 outputs an access permission command for permitting access to the conference material data (development conference material, specifications, design drawing) corresponding to the security code to the data access unit 313. To do.

  Thereafter, the data access unit 313 enables access to the conference material data corresponding to the security code (access permission).

  Thus, by configuring the conference material management server device 10 and the conference material browsing terminal 30 as one body, the installation space of the device and the management burden of the device can be reduced.

(Example 6)
You may provide the entrance management apparatus which manages opening / closing of the door for entrance / exit of a conference room in the entrance / exit of the conference room demonstrated in FIG. The entrance management device manages opening / closing (unlocking, locking) of the door for entrance / exit, and, like the security code writing / reading device 20, the network I / F 201 and the card reader / writer 202 (only the card reader may be used). , A data reading unit 203, a data transmission unit 205, a data reception unit 206, and the like. When a conference participant passes the ID card through the entrance management device, the name of the owner of the ID card is read and the conference material management server device 10 On the other hand, an inquiry is made as to whether the owner name is recorded in the conference material registration table 51 of FIG.

  The room entrance management device unlocks the entrance door when receiving a response from the conference material management server device 10 that the owner name is recorded in the conference material registration table 51 of FIG. Note that when the response that the owner name is not recorded in the conference material registration table 51 of FIG. 3 is received from the conference material management server device 10, the door is locked.

In addition, as in the conference material data management system 1 ′ shown in FIG. 10, the security code writing / reading device 20 is provided in the room entry management device 60, and the security code writing / reading device 20 transmits the conference material management server device 10 When the received security code is received, the room entry management device 60 may unlock the entrance / exit door of the conference room.
By doing so, the entrance management to the conference room and the security code writing process can be executed at the same time, so the convenience of the conference participant is improved. Also here, the conference material management server device 10 and the conference material browsing terminal 30 may be configured integrally.

(Other)
A function block of the conference material browsing terminal 30 may be incorporated in a multi-function image forming apparatus (MFP: Multi Function Peripheral), and the function of the conference material browsing terminal 30 may be realized by the MFP. In this way, since the conference material data transmitted from the conference material management server device 10 can be immediately printed by the MFP, the convenience of conference participants is improved.
In addition, the functional block of the conference material management server apparatus 10 may be incorporated in the MFP.

  The ID card 40 may be a non-contact type ID card. In this case, the ID card 40 has a non-contact IC tag (also referred to as a non-contact data carrier or RFID). The non-contact IC tag includes a coil pattern on a substrate made of plastic or the like, and a resonance circuit is formed by the coil and a capacitive element so as to transmit / receive radio waves having a constant frequency. In this case, the card reader / writer 202 of the security code writing / reading device 20 and the card reader 311 of the conference material browsing terminal 30 use hardware corresponding to a non-contact type ID card.

  Note that the recording destination information of the conference material data recorded in the conference material registration table 51 and the like in FIG. 3 may be a URL as well as a file path.

  In the conference material registration table 51 of FIG. 3 and the like, different security codes are recorded for each participant, but may be the same for each participant.

DESCRIPTION OF SYMBOLS 1,1 '... Conference material data management system 10, 50 ... Conference material management server apparatus, 101 ... Network I / F, 102 ... Input I / F, 103 ... Display I / F, 104 ... Memory, 105 ... HDD, 111 ... Conference material data recording unit, 112 ... Conference material data registration unit, 113 ... Conference material data access control unit, 113a ... Security code generation unit, 114 ... Data transmission unit, 115, 115 '... Data reception unit, 116 ... Control , 20 ... Security code writing / reading device, 201 ... Network I / F, 202 ... Card reader / writer, 203 ... Data reading unit, 204 ... Security code request command generating unit, 205 ... Data transmitting unit, 206 ... Data receiving unit 207: Data writing unit 208: Memory 209 ... Control unit 30, 31, 32 ... Conference material review Terminal, conference material browsing terminal A, conference material browsing terminal B, 301 ... network I / F, 302 ... input I / F, 303 ... display I / F, 304 ... memory, 305 ... HDD, 311 ... card reader, 312 ... Data reading unit, 313 ... data access unit, 313a ... data access command generation unit, 314 ... data transmission unit, 315 ... data reception unit, 316 ... control unit, 40 ... ID card, 41 ... memory, 51-53 ... conference material Registration table, 60...

Claims (7)

A recording unit that records conference material data, and a server device that includes at least information related to the participants of the conference, and a table that records a security code for controlling access to the conference material data of the conference,
A security code writing device that receives the security code transmitted from the server device and writes the received security code to a memory of an ID card possessed by a participant of the conference;
A security code written in the memory of the ID card is read, transmitted to the server device, and connected to a terminal that makes an access request to the conference material data recorded in the server device,
The server device receives the security code transmitted from the terminal, and when the security code is recorded in the table, access to the conference material data recorded corresponding to the security code Conference material data management system characterized by allowing   The server device records an access authority level indicating an access level for the conference material data in the table for each participant of the conference or for each conference material data, and accesses the conference material data to the conference participants. 2. The conference material data management according to claim 1, further comprising controlling access to the conference material data for a participant of the conference based on the access authority level even if the access is permitted. system.   The server device records identification information for identifying the terminal such as an IP address in the table for each participant of the conference or for each conference material data, and identifies the terminal such as an IP address transmitted from the terminal. 2. The conference material data management system according to claim 1, wherein, when the identification information to be matched matches the identification information recorded in the table, access to the conference material data for the conference participants is permitted. .   The server device detects the reception time of the security code transmitted from the terminal, and even if access to the conference material data for the conference participants is permitted, based on the reception time, The conference material data management system according to claim 1, further comprising controlling access to the conference material data for a participant of the conference.   The server device records a conference opening time in the table and, when receiving the security code transmitted from the terminal within the conference holding time, gives access to the conference material data to the conference participants. 5. The conference material data management system according to claim 4, wherein permission is granted.   The conference material data management system according to claim 1, wherein the server device and the terminal are integrally configured.   When the security code writing device is provided in an entrance management device that manages the opening / closing of the entrance door of the conference room, and the security code writing device receives the security code transmitted from the server device, the entrance management device The meeting material data management system according to claim 1, wherein the door for entering and exiting the meeting room is unlocked.

Images