JP2017138688A - Information processing device, information processing system, information processing method and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide an information processing device, information processing system, information processing method and program that make it possible to share shared conference information among conference participants without loosing convenience and security even after the conference is over.SOLUTION: An information processing device (functional block 400 of a management server) allowing information to be shared among a plurality of information terminals through a network 408 comprises: a conference control unit 402 that controls a creation start of shared information and creation end thereof; a conference material management unit 405 that creates a conference material to be shared from information to be transmitted from the plurality of information terminals; a password creation unit 406 hat creates first information for encrypting the conference material; and an execution file preparation unit 404 that creates execution means for causing the conference material to be browsed in response to a request from the plurality of information terminals. The execution means and the conference material encrypted by the first information are stored in a cloud server connected via the network, and after storage of the conference material is ended, the conference material is deleted from the cloud server.SELECTED DRAWING: Figure 4

Description

  The present invention relates to an information processing apparatus, an information processing system information processing method, and a program.

  Up to now, there has been known a conference support system that can provide a conference participant with an information sharing space for storing and browsing materials used for a conference at the time of the conference, thereby enabling the conference to be supported. In this conference support system, a closed one-time network that can be accessed only by conference participants is built, conference participants can participate in conferences using smart devices and PCs, and conference materials can be easily shared It becomes.

  A conventional conference system is a closed one-time network, and a file shared at the end of the conference is deleted from the system. In many cases, only meeting organizers can download meeting materials during a meeting in consideration of security. For this reason, when a conference participant wants to refer to the conference material after the conference, it takes time and effort to individually contact and acquire the conference organizer.

  In addition, for example, by storing meeting materials on a server on an open network before the end of the meeting and sharing the URL among the participants, the meeting participants do not have to contact the meeting organizer individually. It becomes possible to refer to the conference material. However, even in this case, it is necessary for each participant to create an account for an open network service in which conference materials are stored, which is not sufficient in terms of convenience. In addition, when the URL storing the conference material leaks, there is a security problem in that the conference material can be browsed even by non-conference participants.

  As such a conference system, Japanese Patent Application Laid-Open No. 2004-259161 (Patent Document 1) is known. Patent Document 1 automatically acquires authentication information of a mobile terminal held by a conference participant at the time of the conference, and creates an information sharing space for the conference participant on a server on the Internet based on the obtained personal authentication information. The technology is described. However, the technique described in Patent Document 1 does not solve how to secure the security of the conference material.

  It is an object of the present invention to share information shared during a conference among conference participants without losing convenience and security even after the conference ends.

According to the present invention,
An information processing apparatus for sharing information among a plurality of information terminals through a network,
Means for controlling the generation start and end of shared information;
Means for generating the shared information to be shared from information sent by a plurality of information terminals;
Means for generating first information for encrypting the shared information;
Generating means for causing the shared information to be browsed in response to requests from the plurality of information terminals;
The execution means stores the shared information encrypted with the first information in a second information processing apparatus connected via a network, and deletes the shared information from itself after the storage of the shared information is completed. An information processing apparatus can be provided.

  According to the present invention, information shared during a conference can be shared between conference participants without losing convenience and security even after the conference ends.

The figure which showed schematic structure of the information processing system 100 of 1st Embodiment in this indication. The figure which shows the hardware block 200 of the management server 107 of this embodiment. The figure explaining the hardware block of the information terminal 103 for the purpose of illustration. The figure which shows the functional block 400 of the management server 107 of this embodiment. The flowchart of the process which the management server of this embodiment performs. The figure which shows embodiment of the management information 600 which the management server 107 manages in this embodiment. The sequence diagram of the process which the information processing system 100 of this embodiment performs. The sequence diagram which shows the example of a change of the process which the information processing system 100 of this embodiment performs. The figure which shows embodiment of the notification information which notifies URL for accessing the meeting material sent in this embodiment. The figure which shows the starting screen of an executable file which an executable file displays. The sequence diagram which shows the example of a change of the process which the information processing system 100 of this embodiment performs. The figure which shows the graphical user interface (GUI) 1200 for selecting and instruct | indicating whether meeting material is preserve | saved at a cloud server in this embodiment. The figure which shows the further example of a change of the process which the information processing system 100 of this embodiment performs. The figure which shows embodiment of the error screen 1400 demonstrated in FIG. The figure which shows embodiment of the meeting material access user management data 1500 used in embodiment of FIG. The figure which shows the process sequence of the example of a change including the process which deletes meeting materials The sequence diagram which shows the further example of a change of the process which the information processing system 100 of this embodiment performs. The figure which shows the information processing system 1800 of 2nd Embodiment. The figure which shows the transaction between the participant 1905 (information terminal) and the cloud server 1820 in 2nd Embodiment. The figure which shows the functional block 2000 of the management server 1811 of 2nd Embodiment. The figure which shows the functional block 2100 of the execution file 1822 of this embodiment. The sequence diagram of the process which distributes URL of an execution file to a participant after the meeting completion. The sequence diagram of the process in which a participant accesses the execution file 1822 and accesses a meeting material. The flowchart of the process of the information terminal when the process which the execution file 1822 in this embodiment performs, and a participant accesses the meeting material file 1821 is shown. The figure which shows embodiment of the participant information 2510 and notification information 2520 which are used by this embodiment The figure which shows embodiment of GUI provided in order to perform the access to the meeting material file 1821 in this embodiment. The flowchart of the process which the execution file 1822 of 2nd Embodiment performs. The figure which shows the Example of GUI which sets the open period of the meeting material file 1821 in this embodiment. Each flowchart of embodiment with which execution file 1822 records the access log | history with respect to a browsing request in this embodiment, and notifies an access log | history to a participant. The figure which shows embodiment of the access log | history 3020 to GUI3010 which the management server 1811 presents in order to set an aggregation date, and an aggregation date. 6 is a flowchart of processing that enables selecting whether to notify an access history in this embodiment. 14 is a flowchart of processing executed by an execution file 1822 that sets a threshold for unauthorized access and performs access control in the present embodiment. The figure which shows embodiment of the notification information 3300 which notifies the account freezing sent by this embodiment. The flowchart of the process which calls attention to the participant who is another example of a change of this embodiment, and is not accessed by the end of an open period.

  Hereinafter, although this invention is demonstrated using embodiment, this invention is not limited to embodiment mentioned later. FIG. 1 is a diagram illustrating a schematic configuration of an information processing system 100 according to the first embodiment of the present disclosure. In the information processing system 100 of this embodiment, a plurality of devices 101 to 106 are connected via a network 110. The device 101 can be a projector that projects a video for a conference. The projector projects a video on a device 102 such as an electronic blackboard, and can be shared as conference material including a conference video.

  In addition, information devices such as notebook personal computers 105 and 106, a tablet terminal 104, and a smartphone 103 are connected to the network 110 so that conference information can be shared. In the present disclosure, the term “conference” means remote video conference, chat, content that can be participated remotely, game progress that can be accessed from a plurality of terminals via a network, and other information terminals 103 to 106 jointly. This means an operation to be performed on the same information file on the network that can be generated or changed.

  Further, a management server 107 (corresponding to the first information processing apparatus in the present embodiment) and a cloud server 108 (corresponding to the second information processing apparatus in the present embodiment) are connected to the network 110. Yes. The management server 107 manages the progress and conference information of a remotely held conference, sends the conference information managed in response to a request from the information terminals 103 to 106 to the information terminals 103 to 106, and shares the conference information Is possible. Note that the network path between the management server 107 and the information terminals 103 to 107 can be constructed, for example, as a VPN (Virtual Private Network). However, in this embodiment, the network path always passes through a network that performs secure communication. Is not what you need.

  The management server 107 transfers the stored conference material (corresponding to the shared information of the present embodiment) to the cloud server 108 via the network 110, and responds to the request from the information terminals 103 to 106 to the information terminals 103 to 106. By making it possible to browse asynchronously with respect to 106, the usability of the conference information is improved.

  In addition, the management server 107 authenticates the information terminals 103 to 106 and controls access to the conference information stored in the cloud server 108 when the information terminals 103 to 106 attempt to view the conference material. . The cloud server 108 is connected to an open network 110 such as the Internet. However, according to the present embodiment, the cloud server 108 securely stores the conference material with a password or the like, and the executable file generated corresponding to the conference material is sent as an authentication agent, so that the secure storage service can be used. providing.

  FIG. 2 shows the hardware block 200 of the management server 107 of this embodiment. Note that the cloud server 108 has substantially the same hardware configuration as that of the management server 107 except for the functions, and thus the description thereof is omitted in this disclosure. The management server 107 can be implemented as a workstation, server, or general purpose computer. The management server 107 includes a CPU 201, a RAM 202, a ROM 203, and a display device 204 that are interconnected by a system bus 211.

  The display device 204 provides a function of managing the OS and application status of the management server 107, and displays video information on the liquid crystal display using an appropriate protocol such as VGA, DVI, or HDMI (registered trademark). The communication device 205 includes a network interface card (NIC), and uses a protocol for optical communication such as Ethernet (registered trademark) and FTTH, via LAN and Ethernet (registered trademark). Data transfer using communication protocols such as HTTP, FTP, POP, and SMTP is possible.

  An I / O bus 212 is connected to the system bus 211 via a bus bridge 206 such as PCI or PCI Express. In addition, a storage device 207 such as an HDD, an optical recording device 208 such as a DVD, and an input / output device such as a keyboard and a mouse are connected to the I / O bus 212 via an appropriate protocol so that the processing of the management server 107 is possible. It is said. Further, an EEPROM (registered trademark) or EPROM (registered trademark) is used as an auxiliary storage device, and a USB device 210 capable of USB bus connection can also be connected.

  More specifically, the CPU used by the management server 107 includes, for example, PENTIUM (registered trademark) to PENTIUM IV (registered trademark), ATOM (registered trademark), CORE2DUO (registered trademark), CORE2QUAD (registered trademark), and COREi. In addition to the (Registered Trademark) series, XEON (Registered Trademark), PENTIUM (Registered Trademark) compatible CPU, POWER PC (Registered Trademark), and the like can be mentioned, but are not limited thereto.

  As an operating system (OS) to be used, Windows Server (registered trademark), UNIX (registered trademark), LINUX (registered trademark), OPENBSD, or any other suitable OS can be cited. Further, the management server 107 is written in a programming language such as assembler language, C, C ++, Visual C ++, Visual Basic, Java (registered trademark), Java Script (registered trademark), Perl, or Ruby, which operates on the OS described above. Application programs can be stored and executed.

  FIG. 3 is a diagram illustrating hardware blocks of the information terminal 103 for illustrative purposes. The information terminal 103 includes a CPU 301, a RAM 302, a ROM 303, and a communication device 304 that are interconnected by a system bus 305. An I / O bus 306 is connected to the system bus 305 via a bus bridge such as PCI or PCI Express.

  Also, an operation panel 307, a storage device 308 such as an HDD, a scanner device 309, and a print engine 310 are connected to the I / O bus 306 via an appropriate protocol. The operation panel 307 can be configured to include a touch panel including a liquid crystal display, and can perform various processes on the information terminal 103. The storage device 308 stores software such as an OS, a driver, and various applications, and loads a program into the RAM 302 of the MFP 102 in response to a request from the CPU 301 to execute various processes.

  The CPU 301 used by the information terminal 103 includes PENTIUM (registered trademark) to PENTIUM IV (registered trademark), ATOM (registered trademark), CORE2DUO (registered trademark), and CORE2QUAD (registered trademark) according to the types of the information terminals 103 to 106. ), COREi (registered trademark) series, PENTIUM (registered trademark) compatible CPU, POWER PC (registered trademark), MIPS, and other Tegra (registered trademark), Eynos (registered trademark), Snapdragon exclusively used by mobile terminals. (Registered trademark).

  As the operating system (OS) to be used, MacOS (trademark), Windows (registered trademark), UNIX (registered trademark), LINUX (registered trademark), CHROME (registered trademark), ANDROID (registered trademark), or other appropriate However, the present invention is not limited to these. Further, the MFP 102 stores and executes an application program written in a programming language such as assembler language, C, C ++, Visual C ++, Visual Basic, Java (registered trademark), Perl, or Ruby, which operates on the OS described above. can do.

  FIG. 4 is a diagram showing a functional block 400 of the management server 107 of this embodiment. Various processes in the management server 107 are provided as functional means realized on the information processing apparatus when the CPU 201 installed in the management server 107 executes various programs stored in the RAM 202 or the storage device 207. The function block 400 can include a network control unit 401, a conference control unit 402, an authentication control unit 403, and an execution file creation unit 404.

  A network control unit 401 (corresponding to means for controlling the network in this embodiment) controls connection with the network 408. The conference control unit 402 (corresponding to means for controlling generation start and end of shared information in the present embodiment) has a function of managing information related to the conference such as the conference status and conference participants, and starts the conference. In response to this, a pass code (second information) that uniquely identifies the conference information is generated and notified to each of the information terminals 103 to 106. Also, the authentication control unit 403 (corresponding to the means for authenticating the information terminal in the present embodiment) determines whether the access is made by the conference participant when there is an authentication request via the execution file. Use to confirm. If the access is by a conference participant, the authentication control unit 403 sends a password to the cloud server 108 (notifies the second information processing apparatus of first information for decrypting the encrypted shared information). Corresponds to the means).

  Then, the authentication control unit 403 can provide the conference material stored in the cloud server 108 to the conference participant with the password canceled. The execution file creation unit 404 creates an execution file (corresponding to execution means in the present embodiment) for making an authentication request, and stores it in the cloud server 108 at the end of the conference. In the present embodiment, the execution file can be implemented as a server program that can be sent to the cloud server 108 and operated, and can be implemented in languages such as Java (registered trademark), C ++, PERL, RUBY, PHP, and PYTHON. Can be described. In this embodiment, the executable file creation unit 404 generates runtime data used by the executable file at the time of execution in association with the conference material, and sends the runtime data together with the executable file to the cloud server 108. , Functioning as an authentication agent.

  Further, the management server 107 corresponds to a conference material management unit 405 (corresponding to means for managing shared information in the present embodiment) and a password generation unit 406 (corresponding to means for generating first information in the present embodiment). ) And a conference material information notifying unit 407 (corresponding to means for enabling access to the conference material (shared information) in the present embodiment). The meeting material management unit 405 executes processing for saving or deleting materials used during the meeting on the cloud server 108.

  In addition, the conference material information notification unit 407 manages the email addresses of the conference participants, authentication information, and the like. Further, the password generation unit 406 generates a password (corresponding to the first information in the present embodiment) for encrypting the conference material stored in the cloud server 108. Further, the conference material information notifying unit 407 generates a network address that can access the execution file with its own account, and notifies the conference participant managed by the conference material management unit 405 of the network address. (Corresponding to means for notifying the plurality of information terminals of information enabling access to the shared information value of the present embodiment).

  With the above configuration, the security of the conference information on the cloud server 108 is improved using a password. Each function unit shown in FIG. 4 is realized on information processing when the management server 107 of the present embodiment reads the program into the memory and the CPU 301 executes the program.

  FIG. 5 shows a flowchart of processing executed by the management server of this embodiment. The process starts from step S500, and in step S501, an instruction from the administrator is determined as to whether to save the conference material in the cloud server 108. If it is determined in step S501 that the cloud server 108 does not save (no), the process branches to step S512 and ends.

  On the other hand, when an instruction to save in the cloud server 108 is given (yes), the conference material encrypted with the password in step S502 is saved in the cloud server 108. In step S503, the authentication request execution file is stored in the cloud server. Thereafter, a network address such as a URL for accessing the executable file is notified to the conference participants.

  In step S505, a timer for starting the process of deleting the conference material from the cloud server 108 is started, and the expiration of the timer is monitored in step S506. If the timer has expired (yes), the conference information and the execution file of the cloud server 108 are deleted in step S507, and the process is terminated in step S512 (corresponding to means for deleting shared information in the present embodiment).

  On the other hand, if the timer has not expired (no), it is determined in step S508 whether there is an authentication request from the conference participant, and if not, the process returns to step S506 to check for expiration of the timer. On the other hand, when there is an authentication request (yes), authentication processing by the authentication control unit 403 is performed, and it is determined whether or not the authentication is passed. If the authentication is OK (yes), the password is passed to the execution file in step S510, and the process returns to step S506. On the other hand, if the authentication is not successful (no), the authentication result (NG) is notified to the execution file in step S511, and the process returns to step S506. Through the above processing, the conference material is prevented from being accessed by an unspecified number of third parties.

  FIG. 6 shows an embodiment of management information 600 managed by the management server 107 in this embodiment. The management server 107 generates a passcode for the participant to participate in the conference for each conference stored in the cloud server 108, and generates a conference start date / time, conference end date / time, and conference material expiration date. In addition, the management server 107 uses participant attributes (whether or not a host), name, terminal-specific information (terminal name, IP address, telephone number, UID, etc.), and e-mail address as information on participants in the conference. to manage. This information is used to perform authentication and access control to meeting materials.

  FIG. 7 is a sequence diagram of processing executed by the information processing system 100 according to the present embodiment. In FIG. 7, it is assumed that the organizer accesses from the information terminal A and the participant 1 accesses from the information terminal B. In step S701, the organizer notifies the management server of the start of the conference, the conference control unit of the management server 107 generates a passcode unique to the conference at this point, and notifies the organizer of the passcode in step S702. In step S703, the organizer notifies the participant 1 of the passcode, and in step S704, the participant 1 uses the passcode to participate in the conference. Thereafter, a conference session is started in step S705.

  After the conference is held and ended, the organizer notifies the management server 107 of the end of the conference in step S706. In step S707, the management server 107 generates a password for encrypting the conference material, encrypts the conference material, and uploads the encrypted conference material to the cloud server 108 in step S708. Thereafter, in step S709, the management server 107 generates an execution file for the cloud server 108 to make an inquiry to the management server 107, and uploads the executable file to the cloud server 108. In step S710, an HTML file for accessing the uploaded execution file is created, uploaded to the cloud server 108, and a network address, for example, a URL for accessing the HTML file is created.

  Thereafter, the management server 107 notifies the organizer of the generated URL in step S711, and notifies the participant 1 of the generated URL in step S712. After completing the above processing, the management server 107 deletes the conference material managed by itself in step S713. For this reason, the management server 107 does not need to record a plurality of conference materials even after the conference ends, so that the use of hardware resources can be improved. Thereafter, the conference session to be described ends in step S714.

  Step S714 and subsequent steps correspond to the process of controlling access to the conference material by the management server 107. In the embodiment to be described, the case where the organizer tries to access the conference material will be described as an example, but the same processing is applied to the participants. In step S715, the organizer accesses the URL of the cloud server 108 and activates the execution file. The execution file of the cloud server 108 requests the input of authentication information (passcode) from the access request source, in the embodiment to be described, to the organizer in step S717.

  In step S717, the organizer inputs a passcode as authentication information from the URL and returns it to the cloud server 108. The cloud server 108 sends the passcode as authentication information to the management server 107 in step S718, and waits for authentication by the management server 107. In step S719, the management server 107 determines whether or not the sent passcode is a value given at the start of the conference.

  In step S720, the management server 107 notifies the cloud server 108 of the authentication OK together with the encrypted password of the conference material. The cloud server 108 remotely decrypts the conference material with the password acquired in step S721, and causes the organizer to browse the conference material decrypted in step S722. If the authentication is successful in this way, the organizer can access the conference material.

  On the other hand, when the management server 107 notifies the cloud server 108 of authentication failure (NG) in step S723, the cloud server 108 notifies the access request source of authentication failure in step S724. With the above sequence, the safety of the conference material is ensured.

  The processing after step S725 in FIG. 7 corresponds to conference material deletion processing. If the management server 107 determines in step S725 that the meeting material deletion time has been reached, the cloud server 108 is instructed to delete the meeting material in step S726. Thereafter, in step S727, the management server 107 instructs the cloud server 108 to delete the authentication request execution file. With the above processing, the target conference material itself and the execution file are deleted from the cloud server 108, the safety of the conference information is improved, and the redundant storage of data on the network is improved.

  FIG. 8 is a sequence diagram illustrating a modification example of processing executed by the information processing system 100 according to the present embodiment. In FIG. 8, the organizer accesses from the information terminal A, the participant 1 accesses from the information terminal B, and the organizer and the participant respectively access the management server 107 using the terminal-specific information. It is. The organizer and the participants notify the management server 107 of participation in the conference in steps S800 and S801, and the management server 107 starts the conference in step S802.

  Thereafter, the conference proceeds and the organizer notifies the management server 107 of the end of the conference in step S803. In step S804, the management server 107 generates a password unique to the conference and encrypts it. Thereafter, the management server 107 uploads the conference material encrypted in step S805 to the cloud server 108. Further, the management server 107 uploads the authentication request execution file to the cloud server 108.

  In step S807, an HTML file for accessing the uploaded execution file is created, uploaded to the cloud server 108, and a network address, for example, a URL for accessing the HTML file is created.

  Thereafter, the management server 107 notifies the organizer of the generated URL in step S809, and notifies the participant 1 of the generated URL in step S810. After completing the above processing, the management server 107 deletes the conference material managed by itself in step S811. For this reason, the management server 107 does not need to record a plurality of conference materials even after the conference ends, so that the use of hardware resources can be improved. Thereafter, the conference session to be described ends in step S812.

  Step S813 and the subsequent steps correspond to the process of controlling access to the conference material by the management server 107. In the embodiment to be described, the case where the organizer tries to access the conference material will be described as an example, but the same processing is applied to the participants. In step S813, the organizer accesses the URL of the cloud server 108 and activates the execution file. The execution file of the cloud server 108 requests the input of authentication information (terminal-specific information) from the access request source, in the embodiment to be described, to the organizer in step S814.

  In step S815, the organizer inputs terminal-specific information as authentication information from the URL and returns it to the cloud server 108. In step S816, the cloud server 108 sends the terminal specific information as authentication information to the management server 107 and waits for authentication by the management server 107. In step S817, the management server 107 determines whether the sent terminal-specific information is a value given at the start of the conference.

  In step S818, the management server 107 notifies the cloud server 108 of authentication OK together with the encrypted password of the conference material. The cloud server 108 decrypts the conference material with the password acquired in step S819, and causes the organizer to browse the conference material decrypted in step S820. If the authentication is successful in this way, the organizer can access the conference material.

  On the other hand, when the management server 107 notifies the cloud server 108 of authentication failure (NG) in step S821, the cloud server 108 notifies the access request source of authentication failure in step S822. With the above sequence, the safety of the conference material is ensured. With the above processing, the target conference material itself and the executable file are deleted from the cloud server 108 using the terminal specific information, and the safety of the conference information is improved and the data is redundantly stored on the network. Is improved.

  FIG. 9 shows an embodiment of notification information for notifying the URL for accessing the conference material to be sent in this embodiment. In the embodiment shown in FIG. 9, the notification information is an email. In other embodiments, a structured document displaying access information can be displayed using browser software to the access requester using CGI. In the notification information, URL information for accessing the execution file, password, user name, and the like are displayed in addition to bibliographic information for identifying the conference.

  Those who participate in the conference can access the web page linked to the executable file using the access information shown in FIG. FIG. 10 shows an execution file startup screen displayed by the execution file. For example, the web page shown in FIG. 10 can be generated as a configuration for calling a CGI written in an appropriate language. At this time, a pass code and terminal-specific information are input to the web page. Display the input box. The participant can call the execution file by inputting the passcode sent from the management server 107 and terminal specific information such as the terminal name.

  FIG. 11 is a sequence diagram illustrating a modification example of processing executed by the information processing system 100 according to the present embodiment. The modified example in FIG. 11 is an embodiment in which the organizer can select whether or not to register the conference material in the cloud server 108. In FIG. 11, the organizer accesses from the information terminal A, and the participant 1 accesses from the information terminal B. The organizer and the participant use the passcode and the terminal-specific information to the management server 107, respectively. The point of accessing and starting the conference is as described with reference to FIGS.

  The process of FIG. 11 starts from the process in which the organizer ends the conference in step S1101, and in step S1102, the management server 107 inquires the organizer whether to save the conference material. The sequence starting from step S1103 is a sequence when the organizer sends a command to save the conference material through the information terminal A. In step S1103, the management server 107 receives an instruction to save the conference material from the organizer. In step S1104, the management server 107 generates a password for encrypting the conference material, and encrypts the conference material with the generated password.

  In step S <b> 1105, the management server 107 uploads the conference material to the cloud server 108. Thereafter, in step S1106, the management server 107 generates an execution file for the cloud server 108 to make an inquiry to the management server 107, and uploads the executable file to the cloud server 108. In step S1107, an HTML file for accessing the uploaded execution file is created, uploaded to the cloud server 108, and a network address, for example, a URL for accessing the HTML file is created.

  Thereafter, the management server 107 notifies the organizer of the generated URL in step S1108, and notifies the participant 1 of the generated URL in step S1109. After completing the above processing, the management server 107 deletes the conference material managed by itself in step S1110. For this reason, the management server 107 does not need to record a plurality of conference materials even after the conference ends, so that the use of hardware resources can be improved. Thereafter, the conference session to be described ends in step S1111.

  Step S1112 and subsequent steps correspond to the process of controlling access to the conference material by the management server 107. In the embodiment to be described, the case where the organizer tries to access the conference material will be described as an example, but the same processing is applied to the participants. In step S1112, the organizer accesses the URL of the cloud server 108 and activates the executable file. The execution file of the cloud server 108 requests input of authentication information (passcode, terminal-specific information, etc.) from the access request source, in the embodiment to be described, to the organizer in step S1113.

  In step S1114, the organizer inputs a passcode, terminal-specific information, and the like as authentication information from the URL, and returns them to the cloud server 108. The cloud server 108 sends authentication information to the management server 107 in step S1115, and waits for authentication by the management server 107. In step S1116, the management server 107 confirms whether or not the conference material sending source is registered as a conference participant.

  In step S <b> 1117, the management server 107 notifies the cloud server 108 of the authentication OK together with the encryption password of the conference material. The cloud server 108 decrypts the conference material with the password acquired in step S1118, and causes the organizer to view the conference material decrypted in step S1119. If the authentication is successful in this way, the organizer can access the conference material.

  On the other hand, when the management server 107 notifies the cloud server 108 of authentication failure (NG) in step S1120, the cloud server 108 notifies the access request source of authentication failure in step S1121. With the above sequence, the safety of the conference material is ensured.

  In the sequence shown in FIG. 11, if the organizer selects not to save the meeting material in the cloud server, a notification that the meeting material is not saved is sent from the information terminal A used by the organizer to the management server 107 in step S1122. The Upon receiving the notification, the management server 107 deletes the conference material without any further processing in step S1123 and ends the sequence. By using the processing of FIG. 11, information to be stored on the network can be managed, and hardware resources can be used efficiently.

  FIG. 12 shows a graphical user interface (GUI) 1200 for selecting / instructing whether or not to save the conference material in the cloud server in the present embodiment. The GUI 1210 is a management screen provided to the organizer by the management server 107 for participants in order to manage the conference. When the organizer checks the check box with an explanation that the conference is ended with the GUI 1010, a GUI 1220 for confirmation is displayed. When the organizer selects the “high” button for issuing a notification instructing to save the conference material in the cloud server 108, a GUI 1230 is displayed, indicating that the conference material is being saved.

  On the other hand, when “No” is selected on the GUI 1220, a GUI 1250 for notifying that the conference is ended is displayed. In addition, after the conference material is stored in the cloud server 108, a GUI 1240 indicating that the storage of the conference material is completed is displayed. After that, a GUI 1250 for notifying the end of the conference is displayed, and a series of processing ends.

  FIG. 13 shows a further modification of the processing executed by the information processing system 100 of this embodiment. The process in FIG. 13 starts from the process in which the participant 1 ends the conference in step S1300. In step S1302, the management server 107 generates a password for encrypting the conference material, encrypts the conference material with the generated password, and uploads the conference material to the cloud server 108. Thereafter, in step S1303, the management server 107 generates an execution file for the cloud server 108 to make an inquiry to the management server 107, and uploads the executable file to the cloud server 108. In step S1304, an HTML file for accessing the uploaded execution file is created, uploaded to the cloud server 108, and a network address, for example, a URL for accessing the HTML file is created.

  Thereafter, the management server 107 notifies the organizer of the generated URL in step S1305, and notifies the participant 2 of the generated URL in step S1306. After completing the above processing, the management server 107 deletes the conference material managed by itself in step S1307. For this reason, the management server 107 does not need to record a plurality of conference materials even after the conference ends, so that the use of hardware resources can be improved. Thereafter, the conference session to be described ends in step S1308.

  Step S1309 and subsequent steps correspond to the process for controlling access to the conference material by the management server 107. In step S1309, the participant 1 accesses the URL of the cloud server 108 and activates the execution file. The execution file of the cloud server 108 requests input of authentication information (passcode, terminal-specific information, etc.) from the access request source, in the embodiment to be described, to the participant 1 in step S1310.

  Participant 1 inputs a passcode, terminal-specific information, and the like as authentication information from the URL in step S1311 and returns them to cloud server 108. The cloud server 108 sends authentication information to the management server 107 in step S1312, and waits for authentication by the management server 107. In step S <b> 1313, the management server 107 confirms whether the conference material transmission source is registered as a conference participant.

  The management server 107 uploads the conference material access user management data to the cloud server 108 in step S1314. Thereafter, the access information of the participant 1 is updated in step S1315. In step S1316, the updated conference material access user management data is uploaded to the cloud server 108 in step S1314. In step 1317, when authentication is OK, a password for decrypting the conference material is sent to the cloud server 108. The cloud server 108 decrypts the conference material using the password in step S1318, and allows the access request issuer to view the conference material in step S1319.

  The processing after step S1320 corresponds to the processing when the management server 108 is down. In step S1320, it is assumed that the cloud server 108 has become inaccessible. In step S1321, the participant 2 accesses the URL and activates the execution file. In step S1322, the cloud server 108 requests authentication information from the participant 1, and the participant 2 sends the 3 authentication information to the cloud server 108 in step S1323. Since the management server 107 has stopped functioning due to a down or the like at this time, even if the cloud server 108 inquires the authentication information to the management server 107 in step S1324, no response is returned as in step S1325.

  The cloud server 108 detects the server down of the management server 107 in step S1326. Thereafter, the cloud server 108 analyzes the conference material access user management data in step S1327, generates an error screen, and causes the access request source to display the error screen in step S1328. Thereafter, by contacting the participant 1 in step S1329, a notification is issued to the participant 2 that there is a possibility of accessing the conference material, and the process is terminated. In this modified example, even when the management server 107 becomes unable to provide a service due to a power failure, a server down, etc., it becomes possible to access the conference material, and the use of the conference material can be made efficient.

  FIG. 14 shows an embodiment of the error screen 1400 described in FIG. The error screen displays information on the occurrence of the error and the participants (including the organizer) acquired by the access analysis. Therefore, a participant who has accessed the management server 107 after the service cannot be provided due to a power failure, server down, or the like can also access the conference material, and the use of the conference material can be made more efficient.

  FIG. 15 shows an embodiment of conference material access user management data 1500 used in the embodiment of FIG. The conference material access user management data 1500 can be extracted from the access log of the management server 107, is generated and updated as a table shown in FIG. 15, and is periodically uploaded to the cloud server 108.

  FIG. 16 shows a processing sequence of a modified example including processing for deleting the conference material. Steps S1601 to S1619 are generally the same as described with reference to FIG. 13, and thus will not be described in detail. In the process of FIG. 16, it reaches a predetermined time before the set conference material deletion time in step S1620. In step S1621, the management server 107 uploads the conference material access user management data to the cloud server 108. In step S1622, the management server 107 refers to the participants (users) who have accessed the conference material and extracts users who have not accessed the conference material. In step S1623, the management server 107 accesses the participant 2 (accesses the conference material). A reminder notification is issued to notify that the conference material will be deleted after a certain period of time. This process eliminates the sudden loss of access to the conference material before the participant accesses, and improves the usability of the conference material.

  Thereafter, when the meeting material deletion time is reached in step S1624, the management server 107 notifies the cloud server 108 to that effect, further deletes the meeting material in step S1625, deletes the authentication request execution file in step S1626, step In step S <b> 1627, the deletion of the conference material access user management data is notified, and the conference related material is deleted from the cloud server 108. According to this embodiment, it is possible to improve the robustness against information leakage without remaining unnecessary conference material in the cloud server 108.

  FIG. 17 is a sequence diagram illustrating a further modification of the process executed by the information processing system 100 according to the present embodiment. The processing in FIG. 17 is performed in substantially the same manner as described above until the meeting material deletion time is reached in step S1721, and thus detailed description thereof is omitted. In the processing shown in FIG. 17, when the meeting material deletion time is reached in step S1721, the management server 107 designates deletion of meeting material in step S1722, deletion of the authentication request execution file in step S1723, or meeting in step S1724. The material access user management data is left, and notifications can be made to participants who have subsequently accessed.

  Thereafter, when the participant 2 accesses the execution file in step S1725, the cloud server 108 may refer to the conference material access user management data in step S1726, and may already hold the conference material in step S1727. A user who has a message is extracted and notified to the participant 2, and the process is terminated. According to this embodiment, it is possible to improve the robustness against information leakage without remaining unnecessary conference material in the cloud server 108.

  Hereinafter, a second embodiment of the information processing system 100 will be described with reference to FIGS. FIG. 18 shows an information processing system 1800 according to the second embodiment. FIG. 18 shows a first network 1810 and a cloud server 1820 managed by the management server 1811. The first network 1810 is assumed to be a secure network such as VPN, but is not limited to this. The cloud server 1820 is an open environment that can be accessed by an unspecified number of people, and is connected to a network such as the Internet.

  The management server 1811 provides a remote conference service with the information terminals of the participants A to D. The management server 1811 uploads the password-protected conference material file 1821 to the cloud server 1820. Further, the management server 107 creates an execution file for accessing the conference material file 1821 and uploads it to the cloud server 1820 as in the first embodiment.

  However, in the information processing system 1800 of the second embodiment, execution file processing is different in that participant information is stored in the cloud server 1820. The second embodiment will be described in detail below. FIG. 19 is a diagram illustrating a transaction between the participant 1905 (information terminal) and the cloud server 1820 in the second embodiment.

  Participant 1905 accesses conference material file 1821 in transaction 1902. Thereafter, an authentication process is executed in transaction 1902 with the execution file 1822 stored in the cloud server. Thereafter, when the authentication is successfully completed, a URL and a password for accessing the conference material file 1821 from the execution file 1822 are sent in the transaction 1901. Thereafter, the participant 1905 can access the conference material file 1821 using the information, and can view the conference material.

  FIG. 20 shows a functional block 2000 of the management server 1811 of the second embodiment. The management server 1811 includes a participant management unit 2001, an execution file generation unit 2002, and a conference material generation unit 2003. A participant management unit 2001 manages conference participant information, an execution file generation unit 2002 generates an execution file of the present embodiment, and a conference material generation unit 2003 provides a function of generating conference material. .

  The management server 1811 further includes a mail generation unit 2004 and a network control unit 2005. The mail generation unit 2004 has a function of generating a mail that notifies a participant or the like of a URL, a password, and the like. The network control unit 2005 also controls exchanges with the network such as mail transmission control and execution file and meeting material storage in the cloud. Each function unit shown in FIG. 20 is realized on information processing when the management server 1811 of this embodiment reads a program into a memory and the CPU 301 executes the program.

  FIG. 21 is a diagram showing a functional block 2100 of the execution file 1822 of this embodiment. The execution file 1822 includes a conference material information management unit 2101, a participant information management unit 2102, and an authentication control unit 2103. The conference material information management unit 2101 manages URL and password information, which is the storage location of the conference material, and the participant information management unit 2102 manages conference participant information such as the participant name and the email address of the participant. . Also, the authentication control unit 2103 provides a function of determining whether access to the execution file is a participant.

  Further, the execution file 1822 includes a mail generation unit 2104 and a network control unit 2105. The mail generation unit 2104 generates a mail that notifies the conference participants of the URL and password of the conference material, and the network control unit 2105 performs control such as connection to the network.

  FIG. 22 is a sequence diagram of a process for distributing the URL of the executable file to the participants after the conference ends. After the conference ends, the management server 1811 uploads the conference material and the password for encrypting the conference material to the cloud server 1820. In step S2202, the management server 1811 obtains the URL and password of the conference material saved from the cloud server 1820. Thereafter, in step S2203, the management server 1811 uploads the URL of the conference material and the execution file in which the password information is embedded, and the participant information to the cloud server 1820.

  Thereafter, the management server 1811 acquires the URL of the execution file from the cloud server 1820, and notifies the participant A to the participant C of the URL of the execution file to each participant in steps S2206 to S2208.

  FIG. 23 is a sequence diagram of processing in which a participant accesses the execution file 1822 to access the conference material. First, the participant accesses the URL of the executable file in step S2301, and the executable file 1822 requests authentication information from the participant A in step S2302. In the present embodiment, the authentication information is information for identifying a participant such as a participant name and a password, and the information is not limited.

  In step S2303, when the participant A sends the authentication information to the execution file 1822, the execution file refers to the participant information management unit 2102 in step S2304 and executes the authentication process. If the authentication is successful (authentication OK) in step S2305, the participant information management unit 2102 sends a message indicating that the authentication has succeeded to the execution file 1822. After confirming that the authentication is valid, the execution file 1822 generates a mail notifying the URL of the conference material and the password for remotely decrypting the conference material file 1821 in step S2306 to generate the participant A. Send to. Participant A can access the conference material URL in step S2307 and enter the password in step S2306 to view the conference material. In the present embodiment, the process of the management server 1811 is distributed to conference management, thereby enabling more efficient conference management.

  FIG. 24 shows a flowchart of processing executed by the execution file 1822 and processing of the information terminal when the participant accesses the conference material file 1821 in this embodiment. Processing of the execution file 1822 starts from step S2400, and participant information and a password from the participant are input in step S2401. In step S2402, the participant information stored in the execution file 1822 is referred to, and in step S2403, it is authenticated whether the participant has a valid authority. When the authentication is successful (authentication OK) (yes), the URL of the conference material file and the browsing password are notified to the participant (access request source) in step S2404, and the process is terminated in step S2405. On the other hand, if the authentication fails (no), the process is branched to step S2405 and the process is terminated. According to this embodiment, it is possible to access the conference material file 1821 without intervening the management server 1811, and the processing of the management server 1811 can be distributed to conference management, so that efficient conference control is possible. It becomes.

  The participant who has received the notification starts access to the conference material file from the information terminal owned by the participant in step S2410. In step S 2411, a browsing password or the like is sent from the information terminal to the cloud server 1820. In step S2412, the cloud server 1820 executes an authentication process. If the authentication is successful (authentication OK) (yes), the access to the conference material file is permitted in step S2413, and the process ends in step S2414. On the other hand, if the authentication fails (no), the process branches to step S2414, and the process ends without accessing the conference material file.

  FIG. 25 shows an embodiment of participant information 2510 and notification information 2520 used in the present embodiment. In the participant information 2510, information such as a participant name, a password, and an e-mail address is registered. In the present embodiment, any other information can be registered. The participant information 2510 is generated by the management server 1811 and is sent to the cloud server 1820 after the conference is completed. Further, the notification information 2520 is described as being generated as a notification mail as a specific embodiment. The notification mail includes the bibliographic information for identifying the conference name, the URL of the conference information file, and the browsing password. The participant can access the conference material file 1821 using the processing described in steps S2410 to S2414 of FIG. 24 using the information described in the notification mail shown in FIG.

  FIG. 26 shows an embodiment of a GUI provided for accessing the conference material file 1821 in this embodiment. The GUI 2610 is a GUI for requesting input of participant information included in the participant information 2510 displayed by the execution file 1822 to the participants. When the input of the participant information is completed, an “OK” button for notifying completion of input is selected.

  If the authentication is successful, a notification mail 2620 is sent to the participant who is the access request source with reference to the participant information. By inputting the browsing password of the information to the GUI 2630, the conference material file 1821 can be accessed.

  FIG. 27 shows a flowchart of processing executed by the execution file 1822 of the second embodiment. The process in FIG. 27 starts from step S2700, and participant information and a password from the participant are input in step S2701. In step S2702, the participant information stored in the execution file 1822 is referenced, and in step S2703, it is authenticated whether the participant has a valid authority. If the authentication is successful (authentication OK) (yes), it is determined in step S2704 whether the conference material file 1821 is in a public period. If it is the publication period (yes), a notification mail is created in step S2705, the URL of the conference material file and the viewing password are notified to the participant (access request source), and the process is terminated in step S2707.

  On the other hand, if the authentication fails (no), the process branches to step S2706 to notify that it is outside the public period, and the process ends in step S2707. According to this embodiment, it is possible to access the conference material file 1821 without intervening the management server 1811, and the processing of the management server 1811 can be distributed to conference management, so that efficient conference control is possible. It becomes.

  FIG. 28 is an example of a GUI (corresponding to a means for setting the publication period of the conference material file for the execution file in the present embodiment) for setting the publication period of the conference material file 1821 in the present embodiment. The GUI 2810 is displayed on the information terminal when the meeting organizer accesses the management server 1811. The organizer sets the viewing period for the conference material file 1821 by inputting the start date and the end date of release in the input box of the GUI 2810 and selecting the “OK” button after the input.

  For a browsing request after passing the browsing period, a notification mail 2820 is sent as notification information, indicating that the participant is out of the period. In the embodiment, the browsing period information is sent to the cloud server 1820 together with the execution file 1822 as execution data of the execution file 1822.

  FIG. 29 is a flowchart of each of the embodiments in which the execution file 1822 records the access history for the browsing request and notifies the participant of the access history in the present embodiment. The process for creating the access history starts from step S2900, and the execution file 1822 receives the input of the participant name and password in step S2911. In step S2902, the execution file 1822 refers to the held participant information, and determines in step S2903 whether or not the authentication is successful.

  If the authentication is successful (yes), in step S2904, an email notifying the URL of the conference material file and the viewing password is generated and sent to the access request source. Thereafter, in step S2905, an access history is recorded, and the process ends in step S2906. On the other hand, if authentication fails in step S2903 (no), the process branches to step S2905 to generate an unauthorized access record history, and the process ends in step S2906. According to the present embodiment, it is possible to add information on prohibition of regular access and unauthorized access to the access history, and it is possible to reflect unauthorized access to access management for controlling access.

  FIG. 29 also shows an embodiment of processing for notifying access history by the execution file 1822. This process starts from step S2910, reads the data of the aggregation date and time when the execution file 1822 is designated in step S2911, and sets the date and time. Thereafter, the execution file 1822 starts a timer and monitors the set date and time. When the set date and time is detected in step S2913, the access history mail up to that time is notified to the organizer, for example, and the process ends in step S2915.

  FIG. 30 shows an embodiment of a GUI 3010 presented by the management server 1811 for setting the aggregation date and time and an access history 3020 until the aggregation date and time. From the GUI 3010 shown in FIG. 30, the meeting organizer designates the date and time of aggregation, and after designation, selects the “OK” button and sends it to the management server 1811. The total date and time is set as execution data of the execution file 1822 and is sent to the cloud server 1820 together with the execution file 1822.

  After the counting period, an access history 3020 is generated and sent to the organizer as a notification mail. The access history 3020 describes the number of frauds for each participant, making it easy to confirm unauthorized access to the conference material file.

  FIG. 31 is a flowchart of processing that makes it possible to select whether or not to notify the access history in this embodiment. In addition, FIG. 31 also shows notification information for notifying unauthorized access. The process of FIG. 31 starts from step S3100. In step S3101, the execution file 1822 receives input of a participant name and a password. In step S3102, the execution file 1822 refers to the held participant information, and starts authentication processing in step S3103.

  If the authentication process is successful (authentication OK), in step S3104, a mail for notifying the URL and access password for accessing the conference material file 1821 is created and sent to the access request source. In step S3105, an access history is recorded, and in step S3106, it is determined whether or not a setting for receiving a notification of access record is made. If it is set not to receive the access history notification (no), the process branches to step S3108 and the process is terminated.

  On the other hand, if notification is set (yes), the administrator of the management server 1811 is notified in step S3107 to alert the occurrence of unauthorized access, and the process ends in step S3108.

  The notification information 3120 for notifying unauthorized access, which is sent to the administrator in this embodiment, is shown in the form of a notification email. However, the notification information may be presented in a pop-up display instead of an email. it can. The notification mail shown in FIG. 31 shows the conference name, the display indicating the occurrence of unauthorized access, the name of the accessed content, and the number of unauthorized accesses.

  In addition, a threshold value is provided for the number of frauds, and for example, a process of detecting and notifying a brute force attack, a DOS attack, or a DDOS attack can be employed.

  FIG. 32 shows a flowchart of processing executed by the execution file 1822 that sets a threshold for unauthorized access and performs access control in this embodiment. The process of FIG. 32 starts from step S3200, and the process of FIG. 32 starts from step S3200. In step S3201, the execution file 1822 receives the input of the participant name and password. In step S3202, the execution file 1822 refers to the held participant information, and starts authentication processing in step S3203.

  If the authentication process is successful (authentication OK), a mail for notifying the URL and access password for accessing the conference material file 1821 is created in step S3204 and sent to the access request source. In step S3205, an access history is recorded, and in step S3206, it is determined whether or not there is unauthorized access. If it is determined that the access is based on valid authentication information and is not unauthorized access (no), the process branches to step S3209 and the process is terminated.

  On the other hand, if it is determined in step S3206 that the access is unauthorized (yes), it is determined in step S3207 whether the participant is an unauthorized access exceeding a threshold. When it is below the threshold (yes), the process is branched to step S3209 and the process is terminated. On the other hand, if the unauthorized access is equal to or greater than the threshold (yes), the process proceeds to step S3208, the corresponding account is frozen, and a notification that the account has been frozen is sent to the corresponding participant. Thereafter, the process ends in step S3209.

  According to the embodiment, unauthorized access can be effectively prevented, and the conference information file can be safely held.

  FIG. 34 shows an embodiment of notification information 3300 for notifying account freezing sent according to this embodiment. The notification information 3300 shown in FIG. 34 is created as a notification email, and is generated including bibliographic information for specifying a meeting name, a target participant and an account freezing and a solution method. According to the embodiment of FIG. 33, it becomes possible for the participant who performed unauthorized access to access the conference material file 1821 again.

  FIG. 34 is another example of modification of the present embodiment, and is a flowchart of processing for calling attention to a participant who does not have access before the end of the disclosure period. The process of FIG. 34 starts from step S3400, reads the data of the aggregation date and time specified by the execution file 1822 in step S3401, and sets the date and time. Thereafter, the execution file 1822 starts a timer in step S3402, and monitors the set date and time.

  When the set date and time is detected in step S3403, the access history so far is searched in step S3404, and it is determined in step S3405 whether or not there is an inaccessible participant. If there is a participant who does not have an access history (yes), a remind mail for urging the participant to access is generated in step S3406, sent to the corresponding participant, and the process ends in step S3407. On the other hand, if there is no inaccessible participant (no), the process branches to step S3407 and the process ends.

  FIG. 34 shows an embodiment of a remind mail 3410 generated and sent in this embodiment. The remind mail 3410 shown in FIG. 34 is generated including bibliographic information for designating a meeting name, a target participant, and a chest message in which the object material file is not accessed. According to the embodiment of FIG. 34, after the participant inadvertently passes the public period, the cloud server 1820 by accessing the conference material file reduces the processing burden on the side, and the participant also It is possible to efficiently access the conference material file 1821 without taking the trouble of inquiring the participants.

  The present invention has been described with the embodiment. However, the present invention is not limited to the embodiment, and other embodiments, additions, modifications, deletions, and the like can be conceived by those skilled in the art. Any of the embodiments is included in the scope of the present invention as long as the operations and effects of the present invention are exhibited.

1: Participant 100: Information processing system 101: Device 103: Information terminal 104: Tablet terminal 105: Notebook personal computer 106: Notebook personal computer 107: Management server 108: Management server 110: Network 200: Hardware block 201: CPU
202: RAM
203: ROM
204: Display device 205: Communication device 206: Bus bridge 207: Storage device 208: Optical recording device 210: USB device 211: System bus 212: I / O bus 301: CPU
302: RAM
303: ROM
304: Communication device 305: System bus 306: I / O bus 307: Operation panel 308: Storage device 309: Scanner device 310: Engine 400: Function block 402: Conference control unit 403: Authentication control unit 404: Execution file creation unit 405 : Conference material management unit 406: Password generation unit 407: Conference material information notification unit 408: Network 600: Management information 1400: Error screen 1500: Conference material access user management data 1800: Information processing system 1810: First network 1811: Management server 1821: Meeting material file 1822: Execution file 1901: Transaction 1902: Transaction 1905: Participant

JP 2004-259161 A

Claims (12)

An information processing apparatus for sharing information among a plurality of information terminals through a network,
Means for controlling the generation start and end of shared information;
Means for generating the shared information to be shared from information sent by a plurality of information terminals;
Means for generating first information for encrypting the shared information;
Generating means for causing the shared information to be browsed in response to requests from the plurality of information terminals;
The execution means stores the shared information encrypted with the first information in a second information processing apparatus connected via a network, and deletes the shared information from itself after the storage of the shared information is completed. Information processing device. The information processing apparatus further includes:
Means for generating information enabling access to the shared information;
Means for generating second information uniquely attached to the shared information and notifying the information terminal;
Means for notifying the second information processing device of first information for decrypting the encrypted shared information;
Means for notifying the plurality of information terminals of information enabling access to the shared information, and when the inquiry including the second information is successfully authenticated, the first information is transmitted via the network. The information processing apparatus according to claim 1, wherein the information can be shared by the plurality of information terminals by sending the information to the outside and remotely decoding the shared information. An information processing system for sharing information among a plurality of information terminals through a network,
A first information processing device for generating shared information to be shared from information sent by a plurality of information terminals;
A second information processing apparatus connected via the network, storing the shared information in a sharable manner, and sharing the information in response to requests from the plurality of information terminals,
The first information processing apparatus
Means for controlling generation start and end of the shared information;
Means for generating first information for encrypting the shared information;
Generating means for causing the shared information to be browsed in response to requests from the plurality of information terminals;
The information processing system, wherein the execution means stores the shared information encrypted with the first information in the second information processing apparatus, and deletes the shared information from itself after the storage of the shared information is completed. The first information processing apparatus further includes:
Means for generating information enabling access to the shared information;
Means for generating second information uniquely attached to the shared information and notifying the information terminal;
Means for notifying the second information processing device of first information for decrypting the encrypted shared information;
Means for notifying the plurality of information terminals of information enabling access to the shared information, and when the inquiry including the second information is successfully authenticated, the first information is converted to the second information. The information processing system according to claim 3, wherein the information can be shared by the plurality of information terminals by sending the information to a processing device and decoding the shared information.   5. The information according to claim 4, wherein at least one information terminal sends the second information to information enabling access to the shared information, and enables authentication by the first information processing apparatus. 6. Processing system.   The execution means operates in the second information processing apparatus to decrypt the encrypted shared information and provide the decrypted shared information to the plurality of information terminals. The information processing system according to claim 1.   The first information processing apparatus further stores the first information in the second information processing apparatus, and when the authentication by the execution unit operating on the second information processing apparatus is successful, the first information and the first information The information processing system according to any one of claims 3 to 6, wherein information can be supplied by sending information enabling access to shared information to at least one information terminal that has been successfully authenticated. .   The first information processing apparatus includes means for setting a public information disclosure period for the execution means, and sends the public information period to the second information processing apparatus as execution data of the execution means. Item 8. The information processing system according to any one of Items 3 to 7.   The second information processing apparatus accumulates an access history by the execution means, extracts unauthorized access from the access history, and notifies at least one information terminal corresponding to the unauthorized access authentication information. The information processing system of any one of -8. An information processing method for sharing information between a plurality of information terminals through a network, wherein the information processing apparatus comprises:
A step for controlling generation start and end of shared information;
Generating shared information to be shared from information sent by a plurality of information terminals; generating first information for encrypting the shared information;
Generating execution means for browsing the shared information in response to requests from the plurality of information terminals,
Storing the execution information, the shared information encrypted with the first information in a second information processing apparatus connected via a network;
And a step of deleting the shared information from itself after the step of storing the shared information is completed. further,
Generating information enabling access to the shared information;
Generating second information uniquely attached to the shared information and notifying the information terminal;
Notifying the second information processing device of first information for decrypting the encrypted shared information;
Notifying the plurality of information terminals of information enabling access to the shared information;
When the inquiry including the second information is successfully authenticated, the information can be shared by the plurality of information terminals by sending the first information to the second information processing device and decrypting the shared information. The information processing method according to claim 10, comprising the steps of: An information processing apparatus executable program for sharing information among a plurality of information terminals via a network, the information processing apparatus comprising:
Means for controlling the generation start and end of shared information;
Means for generating the shared information to be shared from information sent by a plurality of information terminals;
Means for generating first information for encrypting the shared information;
Function as means for generating execution means for browsing the shared information in response to requests from the plurality of information terminals;
The execution means stores the shared information encrypted with the first information in a second information processing apparatus connected via the network, and deletes the shared information from itself after the storage of the shared information is completed. Program.