Terminal device, electronic meeting system, and session management method and program

【0001】

[Technical field to which the invention belongs]

The present invention relates to an electronic conferencing system, a terminal device thereof, a session management method and a program.

【0002】

[Conventional technology]

Communication activities such as various forms of meetings and meetings occupy an important position in the work of office workers. In the past, materials printed on paper were distributed to participants and face-to-face meetings were mainly held, or telephone conferences were the main focus, but with the development of network technology, various electronic conference systems will be used. Is becoming.

【0003】

Conventionally, electronic conferencing systems that comply with the T.120 recommendations of ITU-T (see, for example, Non-Patent Document 1) have been developed and used by multiple vendors. For example, Microsoft's NetMeeting^TMIs well known (see, for example, Non-Patent Document 2). In addition to NetMeeting, Exchange 2000 Server and IBM's Lotus^TM Sametime^TMEtc. can be used as a conference system that complies with the T.120 recommendation. With these products, application sharing, whiteboard sharing, etc. can be performed between multiple computers.

【0004】

The T.120 recommendation takes a tree-type topology with a communication control device as a node, or a topology in which one of the computers participating in the electronic conference serves as a server and the remaining computers connect to the server. For this reason, computer conferencing systems that comply with the T.120 recommendations, such as NetMeeting, are often used mainly by connecting points that are far apart, and either gather in a place equipped with dedicated equipment or use them. A fixedly installed computer such as a desktop computer is often used.

【0005】

In recent years, electronic conferencing systems having a P2P (Peer-to-peer) type architecture have also appeared. As a P2P type electronic conferencing system, for example, Groove Workspace developed by Groove Network.^TM(See, for example, Non-Patent Document 3). Since Groove Workspace is P2P type software, there is no problem that the load is concentrated on a specific participant of the conference system like NetMeeting, or the conference cannot be continued when a specific participant leaves the conference.

【0006】

In addition, SPANworks is a conferencing system suitable for ad hoc network environments.^TM By using 2000, it is possible to use the electronic conferencing system without the trouble of network setting.

【0007】

With the recent spread of wireless LAN networks and the availability of lightweight, compact computers with sufficient performance, combining electronic conferencing systems that are highly compatible with ad hoc network environments such as SPANworks 2000 Instead of going to a fixed location like before, you can take your computer where you need it and use the electronic conferencing system at any time.

【0008】

By the way, as described above, the electronic conferencing system can be used at any time, and as the opportunities for use increase, the amount of data used in the conference also increases. If it can be used for daily meetings, it will be possible to electronically distribute and refer to materials that were previously printed on paper and distributed, and using data sharing applications such as whiteboard sharing. , There will be more opportunities to create data during the meeting. Electronic data is accumulated in this way, but electronic data has the advantage of being easier to modify and reuse than materials printed on paper, leading to more efficient operations.

【0009】

However, as a drawback of electronic data, the listability is generally inferior to that of printed materials, so in order to take advantage of reusability and the like, it is necessary to save the data so that it can be easily searched. When multiple data are shared in a conference, the data is often related, but in traditional electronic conferencing systems, when trying to save the shared data, each one It is necessary to specify the storage location independently for each application. As a result, there is a problem that even if you try to refer to it later, you have to search for the storage location one by one, or you have to specify the same location one by one when saving. In addition, as a clue to identify the material, although the meeting information such as the date and time of the meeting and the members participating in the meeting is one of the valid information, there is mutual communication between the stored data and the information about the meeting. There is a problem that a means for searching materials from the meeting information is not provided because there is no means for referencing or there is no means for recording the meeting information in the first place.

【0010】

In addition, many of the daily meetings are held on a regular basis. In addition, even if not being performed on a regular basis, for example, a project is sometimes such as to hold a plurality of times in conjunction with the conference on the defect in the progression phase of the project. Since these meetings are related, it will be easier to use if the materials handled there are also managed in a related manner. NetMeeting can manage the schedule for one meeting in cooperation with schedule management software. Also, if it is a regular meeting, schedule management is possible by creating a regular schedule, but the relationship that exists between irregular meetings cannot be used by the user, and the data data can be managed in the first place. Not linked with management function. On the other hand, in the case of Groove Workspace, since it adopts a model of sharing data regardless of whether it is actually communicating, it is said that information is managed in a form corresponding to the actual meeting to be held in the first place. It's hard to say, and you can't manage relationships between different meetings like NetMeeting and others.

【0011】

[Non-Patent Document 1]

ITU-T Recommendation T.120, Data protocols for multimedia conferencing, 1996 [0012]

[Non-Patent Document 2]

Official Microsoft NetMeeting Book, Microsoft Press, 1998 [0013]

[Non-Patent Document 3]

"Groove Starter Guide", by Satoshi Yoshida, Ohmsha 2001 [0014]

[Problems to be Solved by the Invention]

As mentioned above, electronic conferencing systems have become available on a daily basis, but conventionally, there have been systems that manage interrelated conference information and easily use the data used in the conference. Absent.

【0015】

The present invention has been made in consideration of the above circumstances, and is a terminal device of an electronic conference system, an electronic conference, which enables easy reference and use of conference information and data used in a conference in an electronic conference system. The purpose is to provide systems, session management methods and programs.

【0016】

[Means for solving problems]

The terminal device according to the present invention is a communication means for performing data communication with another terminal device, and real-time data between one or a plurality of the other terminal devices via the communication means. The means for carrying out a session with sharing, the first management means for managing the session information for each of the sessions, and the meeting information for the meeting set for managing the session information in association with each other are managed. It is characterized by having a second management means.

【0017】

In this way, the first management unit stores and manages the information related to the session corresponding to one meeting, so that the user can access any session information. The second management department manages the related session information (for example, information on a series of sessions on one theme) collectively by managing the meeting information for managing the association of multiple session information. Will be able to. For example, information about multiple meetings can be categorized and information about interrelated meetings can be easily used.

【0018】

Preferably, a third management means for managing data information about the data that can be shared in any of the sessions may be further provided. Further, preferably, each of the session information may include information that identifies the data shared in the session among the data managed by the third management means. This makes it possible to identify data related to the session from the session information and start / reference the data.

【0019】

Also, preferably, a fourth management means for managing application information about the application that can be launched in any of the sessions may be further provided. Further, preferably, each of the session information may include information that identifies an application to be started in the session among the applications managed by the fourth management means. This makes it possible to identify an application related to the session from the session information and start the application. Further, preferably, each of the meeting information may include information for identifying an application to be started in the session associated with the meeting among the applications managed by the fourth management means. As a result, it is possible to identify and start an application related to the session associated with the meeting from the meeting information.

【0020】

Further, preferably, a fifth management means for managing user information regarding the other terminal device capable of participating in any of the sessions may be further provided. Further, preferably, each of the session information may include information for identifying another terminal device that participates in the session among the other terminal devices managed by the fifth management means. This makes it possible to identify other terminal devices related to the session from the session information. Further, preferably, each of the session information is information that identifies another terminal device that participates in the session associated with the meeting among the other terminal devices managed by the fifth management means. It may be included. This makes it possible to identify other terminal devices related to the session associated with the meeting from the meeting information.

【0021】

Also, preferably, the implementing means distributes information necessary for conducting the session to one or a plurality of the other terminal devices scheduled to participate in the session before starting the session. The means may further include means for capturing information necessary for conducting the session, which is distributed from any of the other terminal devices before the session is started.

【0022】

In this way, before starting the session, the session information is distributed, and each participant of the session inputs the session information, so that the participants can also confirm the session information and prepare in advance. You will be able to do it.

【0023】

In addition, preferably, the information necessary for carrying out the session may include data shared in the session or information for acquiring the data.

【0024】

As a result, the participants of the session who input the session information including the shared data can confirm the contents of the shared data in advance, and it is not necessary to send the shared data at the start of the session, so that the session can be started. The time required for the session can be shortened.

【0025】

Further, the electronic conferencing system according to the present invention is characterized by including a plurality of the terminal devices.

【0026】

Further, the present invention is a session management method in a terminal device, in which one or a plurality of the other terminal devices are used with each other via a communication means for performing data communication with the other terminal device. It has a step of performing a session with real-time data sharing, a step of managing session information about each said session, and a step of managing meeting information about a meeting set for associating and managing the session information. It is characterized by that.

【0027】

The present invention relating to the device is also valid as an invention relating to the method, and the present invention relating to the method is also valid as an invention relating to the device. In addition, the present invention relating to an apparatus or method provides a function for causing a computer to perform a procedure corresponding to the present invention (or for causing the computer to function as a means corresponding to the present invention, or for causing the computer to perform a function corresponding to the present invention. It also holds as a program (for realization), and also as a computer-readable recording medium on which the program is recorded.

【0028】

BEST MODE FOR CARRYING OUT THE INVENTION

Hereinafter, embodiments of the invention will be described with reference to the drawings.

【0029】

(First Embodiment) FIG. 1 shows a configuration example of an information processing device (terminal device) 100 according to the first embodiment of the present invention.

【0030】

As shown in FIG. 1, the information processing apparatus 100 of the present embodiment includes a communication unit 101, a user management unit 102, an application management unit 103, a document management unit 104, a session management unit 105, a meeting management unit 106, and an operation unit 107. It has.

【0031】

Here, the user refers to an information processing device, and a natural person who uses the information processing device is called a user.

【0032】

A session is a group of users created for one-time collaboration (with real-time data sharing between multiple users) such as a conference among a plurality of users, or a group of the users. Refers to a single collaborative work such as a meeting held by.

【0033】

Further, the meeting is, for example, managing a plurality of related session information collectively among the session information consisting of the above-mentioned collaborative work between users and one collaborative work such as a user group and a conference by a user group. Refers to information to be done.

【0034】

The application refers to each application program executed on the information processing device and operated by the user during the session.

【0035】

A document refers to data used in an application, such as a document or data file (ie, a generic term for all formats of data available to the application, not just text files and image data).

【0036】

The operation unit 107 is for providing a user interface function such that the user operates the information processing device and the information processing device presents information to the user. .. Specifically, for example, it is for providing users with functions such as creating a meeting, starting / ending a session, starting a document, starting an application, referencing information, and searching information. The operation unit 107 can be configured by using, for example, a keyboard, a voice input device, a mouse, a display device, a voice output device, and the like.

【0037】

The communication unit 101 is for communicating with other information processing devices by using communication means such as wired communication, wireless communication, and infrared communication. Specifically, for example, it detects information processing devices existing in the surroundings, manages communication connections with those information processing devices, and enables an application to send and receive data using those communication connections. To do. For the communication unit 101, for example, the one shown in JP-A-7-336370 can be used. The communication unit 101 may be provided with a plurality of communication methods and may be used as appropriate.

【0038】

FIG. 2 shows an example of a network configuration in which a plurality of information processing devices 100 of the present embodiment gather to perform a session. In (a), when all six information processing devices # A to C (terminal device 100 in the figure) belong to one meeting, all the information processing devices belonging to the meeting belong to network N1 (in the figure, It shows how one session is performed via 120).

【0039】

In this embodiment, it is assumed that it can be applied to an ad hoc network environment, and since each information processing device 100 holds at least the data necessary for itself, two or more belonging to a certain meeting. Once the information processing devices of the above are gathered, a session belonging to the meeting can be held. (b) shows a session belonging to the meeting only with the information processing devices # A to C, and (c) shows a session belonging to the meeting only with the information processing devices # D to F. Shown.

【0040】

Further, when the information processing device can support a plurality of communication methods, it is not always necessary to conduct a session via the same network. For example, as in (c), a network different from (a). It is also possible to hold a session belonging to the meeting via N1 (121 in the figure).

【0041】

Of course, it is also possible to form a plurality of meetings with the same user group. Further, one information processing device can belong to a plurality of meetings having different constituent users. (d) shows how a user belonging to one meeting in (a) conducts a session belonging to another meeting having a different constituent user.

【0042】

Basically, the user may decide how to use the meeting or session. As an example, each project A regular meeting that is actually held with the attribute of the meeting called "Project A regular meeting" as one meeting ... For example, "Project A regular meeting" held on 2002/04/01 ( It can be used in various ways, such as "2002/04/01)", "Project A Regular Meeting (2002/04/08)" held on 2002/04/08, etc. as sessions.

【0043】

It is also possible to have different definitions and correspondences of meetings and sessions for each individual user. For example, one user may define a project A regular meeting meeting and a project B regular meeting meeting separately, and another user may define one meeting that includes the project A regular meeting and the project B regular meeting. Is also possible.

【0044】

Below, user information, application information, document information, session information and meeting information, and user management unit 102, application management unit 103, document management unit 104, session management unit 105, and meeting management unit 106 that manage each information, respectively. explain.

【0045】

Here, for the sake of simplicity, the information processing apparatus 100 handles information about the sessions that the information processing apparatus 100 has participated in among the sessions conducted at the meeting to which the own apparatus belongs, and the user management unit 102 is obtained from the communication unit 101. In addition, it shall manage information about users other than its own device. When the information processing device 100 manages both the information about the session in which the own device participated and the information about the session in which the own device did not participate, for example, whether or not the own device participated in the information about the session. A method of adding information indicating the above, a method of managing information about the own device by the user management unit 102, or the like may be used. Similarly, when the information processing device 100 also manages information about a session held in a meeting to which the own device does not belong, for example, is the meeting to which the own device belongs to the information about the meeting and / or the information about the session? A method of adding information indicating whether or not the session is held at the meeting to which the own device belongs, a method in which the user management unit 102 also manages information about the own device, or the like may be used. Information about the session that the own device did not participate in may be obtained from, for example, a user who later participated in the session. Similarly, information about a session held in a meeting to which the own device does not belong may be obtained later, for example, from a user who belongs to the meeting.

【0046】

The user management unit 102 manages information about users related to meetings and sessions.

【0047】

The user management unit 102 provides user information (see the example in FIG. 4), for example, for each user, a "user number", a "user name", an "address", and a "state of being able to communicate with the user". To store and manage information such as.

【0048】

Since the user information itself is information unique to each information processing device, the number assigned to the user may be determined for each information processing device, and of course, it is globally unique, unique within the meeting, or within the session. You may use something that is unique. For example, when a new user is detected by the communication unit 101, a new number is assigned to that user and stored together with the detected user name (or another name corresponding to the detected user name) and its address. To do. As described above, in the description used in the present embodiment, the user means an information processing device other than the own device, and in the variation of managing the own device, the user can also mean the own device. ..

【0049】

The user name may also be determined for each individual information processing device, and of course, a user name that is globally unique, unique within the meeting, or unique within the session may be used. For example, it may be the name of the user of the information processing device, it may be the globally unique hardware number of the information processing device, or whatever it is as long as it is distinguished. May be good.

【0050】

The address differs depending on the protocol used by the communication unit 101, but for example, when the TCP / IP protocol is used, the IP address can be used.

【0051】

The status of being able to communicate with a user indicates the status of being able to communicate with that user for a registered user. For example, "True" indicates that communication is possible and "False". Indicates that communication is not possible. When the state changes, its contents are changed.

【0052】

The user may be able to directly edit the user information.

【0053】

Each information processing device may store and manage basic data related to its own device (for example, the address of its own device, a user name, etc.) in the user management unit 102, or a storage unit (not shown). It may be memorized in.

【0054】

The application management unit 103 manages information about applications that can be used in the own device (self-information processing device).

【0055】

The application management unit 103 provides application information (see the example in FIG. 5), for example, "application number", "application name", "application executable file location", and "application startup state" for each application. Information such as is stored and managed.

【0056】

Since the application information itself is information unique to each information processing device, the number assigned to the application may be determined for each information processing device, and of course, it is globally unique, unique within the meeting, or within the session. You may use something that is unique. The same applies to the application name. If the application is stored in local memory, the location of the application's executable file will vary from one information processor to another.

【0057】

The application startup status indicates whether or not the registered application is running. For example, True indicates that the application is running and False indicates that the application is not running. ..

【0058】

When the application management unit 103 receives an application start request from other parts (for example, operation unit 107, session management unit 105, document management unit 104), the application management unit 103 starts the application and changes the start state of the application. It also monitors the status of running applications and changes the launch status of applications when the application is terminated.

【0059】

The user may be able to directly edit the application information.

【0060】

The document management unit 104 manages information about documents used in its own device.

【0061】

The document management unit 104 provides document information (see the example in FIG. 7), for example, for each document, "document number", "document name", "document file location", and "to start the document". Stores and manages information such as "application number".

【0062】

Since the document information itself is information unique to each information processing device, the number assigned to the document may be determined for each information processing device, and of course, it is globally unique, unique within the meeting, or within the session. You may use something that is unique. The same applies to the document name. If the document is stored in local memory, the location of the document will vary from one information processor to another.

【0063】

Here, the application number for starting the document is the "application number" in the application information (see the example of FIG. 5) managed by the application management unit 103. It is also possible to use information other than this "application number" to associate the application for starting the document.

【0064】

When the document management unit 104 receives a document registration request from other parts (for example, operation unit 107, session management unit 105), the document management unit 104 stores the document name, location, and application number together with a new number. When a document start request is received from another part, the application management unit 103 is requested to start the application corresponding to the application number by using the document of the contents of the location column as an argument.

【0065】

The user may be able to directly edit the document information.

【0066】

The session management unit 105 manages information related to the session.

【0067】

The session management unit 105 provides session information (see the example in FIG. 8), for example, for each session, "session number", "session name", "number of user who participated in the session", and "session start date and time". , "Number of application used in session", "Number of document used in session", etc. are stored and managed.

【0068】

Since the session information itself is information unique to each information processing device, the number assigned to the session may be determined for each information processing device, and of course, it is globally unique, unique within the meeting, or within the session. You may use something that is unique. The same applies to the session name.

【0069】

Here, the number of the user who participated in the session, the number of the application used in the session, and the number of the document used in the session are described in "User information managed by the user management unit 102 (see the example in FIG. 4)". "User number", "Application number" in the application information managed by the application management unit 103 (see the example in FIG. 5), "Document number" in the document information managed by the document management unit 104 (see the example in FIG. 7). Is. It is also possible to use information other than this "user number" to associate the users who participated in the session, and the same applies to the application used in the session and the association of documents used in the session. Is.

【0070】

When a new session is created, the session management unit 105 stores the session name, the users who are participating in the session at that time, and the start date and time. In addition, the contents of each are changed by increasing or decreasing the number of participating users, starting the application, and starting the document.

【0071】

The user may be able to directly edit the session information.

【0072】

The meeting management unit 106 manages information related to the meeting.

【0073】

The meeting management unit 106 provides meeting information (see the example in FIG. 6), for example, for each meeting, "meeting number", "meeting name", "meeting-related user number", and "meeting-related". Store and manage information such as "session number".

【0074】

Since the meeting information itself is information unique to each information processing device, the number assigned to the meeting may be determined for each information processing device, and of course, it is globally unique, unique within the meeting, or within the session. You may use something that is unique. The same applies to the meeting name.

【0075】

The user number related to the meeting and the session number related to the meeting are described here by the "user number" in the user information managed by the user management unit 102 (see the example in FIG. 4) and the session management unit 105, respectively. This is the "session number" in the session information to be managed (see the example in Fig. 8). It is also possible to use information other than this "user number" to associate the users related to the meeting, and the same applies to the association of the sessions related to the meeting.

【0076】

The user may be able to directly edit the meeting information.

【0077】

Further, as described above, it is possible to make the link structure between the meeting and the session different for each information processing device.

【0078】

When the user number or user name is unique only within each information processing device, when exchanging data related to the specific user between the information processing devices in a certain session, at least it is unique within the session. Information that identifies the user shall be used for. For that purpose, it is sufficient to manage the correspondence between the information that identifies the user globally uniquely, uniquely within the meeting, or uniquely within the session, and the unique user number or user name only within the own device. The same applies to the session number and session name, the program number and program name, and the document number and document name.

【0079】

Hereinafter, the operation of the present embodiment will be described with reference to specific examples.

【0080】

Figure 3 shows an example of the operating procedure of the information processing device that starts the session.

【0081】

In the following, an operation example of the information processing device that starts the session will be described, and then operation examples of other information processing devices will be referred to. The difference between the former and the latter is basically that the former makes some request to other information processing devices to participate in the session, while the latter makes other information processing devices participate in the session. It is a point that starts from receiving some request.

【0082】

(Step S1: Creating a meeting) The user of this information processing device refers to the list display of existing meetings, for example, and if the existing meeting does not exist yet, or if the existing meeting exists, it will start from now on. When trying to manage a new meeting in a new meeting, first, the operation unit 107 is used to create a new meeting.

【0083】

In this case, the user inputs the instruction for creating a new meeting, then inputs the meeting name of the newly created meeting, and if necessary, the user who participates in the meeting or the meeting. Enter the application to start. The participating user and the application to be started do not necessarily have to be entered.

【0084】

The operation unit 107 has, for example, a function of displaying a list of other users and a list of available applications, and the user can select a user who participates in the meeting and an application to be started from the displayed list. You may select and input, or you may use this function and the manual input function together.

【0085】

When the list display function is provided, the operation unit 107 acquires information about the user from the user management unit 102 and displays the information.

【0086】

FIG. 4 shows an example of user information held by the user management unit 102. In this example, the user management unit 102 holds, for each user, information on the user's number, user name, address, and flags indicating whether or not the user can currently communicate as a table. As described above, for example, when the communication unit 101 detects a new user, the user name and address are added to the table together with the new number. In addition, when a notification that a user existing in this table has become communicable is received, the content of the communicable column is changed to True, and when a notification that communication becomes impossible is received from the communication unit 101, communication is possible. Change the contents of the column to False. In the case of the specific example shown in Fig. 4, the three users "Murai", "Iwamura", and "Ikeda" are currently in a state where communication is possible, while the two users "Horiguchi" and "Ikegami" are currently in a state where communication is not possible. It has become.

【0087】

In addition, the operation unit 107 acquires information on available applications from the application management unit 103 and displays the information.

【0088】

FIG. 5 shows an example of application information held by the application management unit 103. In this example, the application management unit 103 holds information on the application number, the application name, the location of the application executable file, and the flag indicating whether the application is currently running as a table. The application number, application name, and location of the application executable file are given in advance. As described above, when the application management unit 103 receives an application start request from another part, it starts the application with the contents of the location column, changes the contents of the running column to True, and monitors the state of the application. , When the application is closed, change the contents of the running column to False. In the case of the specific example shown in Fig. 5, four applications of "whiteboard", "presentation", "chat", and "notebook" are available.

【0089】

When the user creates a new meeting, the operation unit 107 passes the information about the meeting to the meeting management unit 106, and the meeting management unit 106 stores the meeting information given by the operation unit 107.

【0090】

FIG. 6 shows an example of the meeting information held by the meeting management unit 106. In this example, the meeting management unit 106 has the meeting number, the meeting name, the number of the user who joins the meeting (the number of the user who joins the session belonging to the meeting), and the number of the application started in the meeting (in the session belonging to the meeting). It has information on the number of the application to be started) and the number of the session related to the meeting as a table. As mentioned above, when a new meeting is created, a new number will be assigned. Further, for the users participating in the meeting, the user number stored in the user management unit 102 is stored. Similarly, for the application to be started, the application number stored in the application management unit 103 is stored. In the case of the specific example shown in Fig. 6, a new "Project A regular meeting" meeting is created, and the participating users are "Murai", "Iwamura", and "Ikeda", and the startup application is "Note". In the case of a newly created meeting, the session column is left blank because the session has not been created yet at this point.

【0091】

If it is allowed to temporarily suspend the association between the sessions and the meetings so that they can be performed again later, step S1 can be performed in step S2, and step S1 can be performed in step S2. It is also possible to do it after S2.

【0092】

(Step S2: Creating a session) Next, the user creates a session using the operation unit 107 in preparation for holding a meeting.

【0093】

The user selects the meeting to which the session belongs. In addition, the user inputs the name of the newly created session. In addition, the user inputs the session name, the users who join the session, and the application to be started in the session. At that time, for example, if the user who participates in the meeting to which the session belongs and the application to be started are set as default values and they are presented to the user, the user can confirm that the default value can be used. You don't have to enter. If you want the content to be different from the default value, you can change it.

【0094】

When the user inputs a document to be used in the session, the operation unit 107 passes information about the document to the document management unit 104, and the document management unit 104 stores the information given by the operation unit 107.

【0095】

FIG. 7 shows an example of the document information held by the document management unit 104. In this example, the document management unit 104 holds information on the document number, the document name, the location of the document file, and the application number for launching the document as a table. In the case of the specific example shown in FIG. 7, the document of the "whiteboard" application called "idea diagram" is stored.

【0096】

When the user creates a new session, the operation unit 107 passes information about the session to the session management unit 105, and the session management unit 105 stores the information given by the operation unit 107.

【0097】

FIG. 8 shows an example of session information held by the session management unit 105. In this example, the session management unit 105 determines the session number, the session name, the number of users who participate in the session, the number of the application launched in the session, the number of the document used in the session, the start date and time of the session, and the session. Information on the end date and time is held as a table. In the case of the concrete example shown in Fig. 8, a new "Project A regular meeting (2002/04/01)" session is created, the participating users are "Murai", "Iwamura", and "Ikeda", and the launched application is "Note". The usage document is a document of a "whiteboard" application called "idea diagram".

【0098】

When the user creates a new session, the session management unit 105 passes information about the session to the meeting management unit 106, and the meeting management unit 106 stores the information given by the session management unit 105.

【0099】

FIG. 9 shows an example of the meeting information held by the meeting management unit 106 when a new session is created. Add the newly created session number given by the session management unit 105 to the session number column. In the case of the specific example shown in FIG. 9, "Project A regular meeting (2002/04/01)" is added as a session related to the "Project A regular meeting" meeting.

【0100】

It is also possible to create a session without selecting a specific meeting. If a session is created without specifying a specific meeting, a new meeting with an appropriate name may be created according to the created session and managed as belonging to that meeting. , A special meeting to which a session created without specifying a specific meeting belongs is prepared, and a session created without specifying a specific meeting is managed as belonging to the special meeting. You may do so.

【0101】

(Step S3: Start of session) Next, in order to start the actual conference, the user instructs the operation unit 107 to execute the process for starting the session.

【0102】

When the process is started, the session management unit 105 confirms with the user management unit 102 whether the other user specified in the stored session information is currently communicable, and establishes a communication connection with the communicable user. Request the communication unit 101 to generate it. Upon receiving the request, the communication unit 101 requests, for example, each communicable user to generate a communication connection, and generates a communication connection with the user who has sent an acknowledgment. Of course, any protocol may be used to generate the communication connection.

【0103】

When a communication connection is created, information about the session is exchanged with each user on the communication connection. The information about the session is not the session information itself held by the own device, but each user creates session information, updates other information as needed, and newly creates meeting information as needed. It includes content to enable you to, for example, information to identify the session, information to identify users participating in the session, and the application to be launched in the session. Information for identifying documents used in the session. If the session information is configured to consist only of information unique to the communication partner user, it is possible to distribute the session information to the communication partner user.

【0104】

The document management unit 104 exchanges the contents of the specified document with another user on the communication connection. If the specified document is stored in a common storage device that can be accessed from each information processing device, information indicating the storage location of the document content is exchanged instead of the document content. You may do so.

【0105】

(Step S4 to Step S8: Implementation of session) Now, when the preparation for the start of the session is completed, the session is started.

【0106】

In each information processing device that participated in the session, the session management unit 105 displays information about the session on the display screen of the operation unit 107, the application management unit 103 starts the specified application, and the specified document is documented. Management unit 104 starts.

【0107】

When the session is started, the session management unit 105 of the information processing apparatus adds the date and time when the session was started to the session information.

【0108】

FIG. 10 shows an example of session information held by the session management unit 105 when a session is started. In the case of the specific example shown in FIG. 10, it is recorded that the "Project A regular meeting (2002/04/01)" session was started at "2002/04/01 13:00:00".

【0109】

After the session is started, the user can perform operations that will be held in the conference, such as operations on the running application and operations on the running document, as well as document startup and application operations. Operations such as activation can be performed, and in the flowchart of FIG. 3, the process branches according to the operation performed by the user.

【0110】

After the session is started, the user uses the operation unit 107 to perform an operation for the conference ... For example, an operation for a running application, an operation for a running document, etc. Operations such as starting a document, starting an application, and ending a session can be performed. In the flowchart of FIG. 3, the process branches according to the operation performed by the user.

【0111】

When an operation for a running application or an operation for a running document is performed (step S4), a process corresponding to the operation is performed (step S8).

【0112】

When instructed to launch a document (steps S4, S5), launch the specified document (step S6). When a new document is started, the contents of this document are exchanged with other users on the communication connection as well as the document started at the start of the session, and the document is started by each information processing device. When a new document is started in the session, new information is added to the document management unit 104, and the contents of the session information stored in the session management unit 105 are updated.

【0113】

FIG. 11 shows an example of the document information held by the document management unit 104 when the document is started after the session is started. In the case of the specific example shown in FIG. 11, a new document of the "presentation" application called "examination progress" has been added.

【0114】

When instructed to start the application (steps S4, S5), the specified application is started (step S7). When a new application is started, the number corresponding to this application is added as the application number for this newly started application as well.

【0115】

In addition, the user can start the application by using the operation unit 107 after the session is started. When a new application is started, this application is also started by each information processing device in the same manner as the application started at the start of the session. When a new application is started in the session, the contents of the session information stored in the session management unit 105 are updated.

【0116】

FIG. 12 shows an example of session information held by the session management unit 105 when the application and the document are started after the session is started. In the case of the specific example shown in FIG. 12, the documents of the "chat" application and the "presentation" application called "examination progress" are newly added.

【0117】

(Steps S4 and S9: End of session) When the user intends to end the actual meeting, the operation unit 107 is used to instruct the execution of the process for ending the session.

【0118】

When this process is started, the session management unit 105 notifies another user of the end of the session and requests the communication unit 101 to destroy the communication connection. Each information processing device that participates in the session ends the session.

【0119】

It should be noted that only the information processing device that started the session may be able to notify the end of the session, and the information processing devices other than the information processing device that started the session also end the session by themselves or the information processing device that started the session. You may be able to notify by asking.

【0120】

Further, when one information processing device notifies the end of the session, it may be determined that the session is ended, or in response to the notification, a predetermined condition such as all or a majority is satisfied. A session may be terminated only if a number of information processors consent to the termination of the session. In the latter case, even if the number of consents does not satisfy the end condition and the session is continued, the information processing device that wants to end the session should end the session for its own device, for example, by leaving the session. Is possible.

【0121】

When the session is terminated, the session management unit 105 of the information processing apparatus adds the date and time when the session was terminated to the session information.

【0122】

FIG. 13 shows an example of session information held by the session management unit 105 when the session is terminated. In the case of the specific example of FIG. 13, it is shown that the Project A regular meeting (2002/04/01) session was completed at 2002/04/01 15:00:00.

【0123】

The above is an example of the processing flow related to one session.

【0124】

Here, the operation of the information processing device other than the information processing device that starts the session will be referred to.

【0125】

FIG. 14 shows an example of the operation procedure in the information processing device other than the information processing device that starts the session.

【0126】

In this procedure example, the information processing apparatus that receives this request always participates in the session.

【0127】

In this case, the processing in each information processing device starts from the point where the information processing device that starts the session described so far receives some request for participation in a certain session (step S11). This request may be made, for example, at the time of setting the communication connection described above, before setting the communication connection, or after setting the communication connection.

【0128】

Each information processing device that receives the above request performs a process for starting a session (step S12). This process corresponds to the process in step S3 in Fig. 3, which includes creating a communication connection (if a communication connection has not yet been created), exchanging information about the session, exchanging the contents of the document, and launching the application. Launching documents, creating session information, selecting the meeting to which the session belongs, creating meeting information or updating meeting information, etc.

【0129】

In the procedure example of FIG. 14, the information processing device that receives the request always participates in the session, but instead, for example, the situation of the own device and the situation of the communication network are taken into consideration. It is also possible to determine whether or not to accept the request, and to participate in the session only when it is determined that the request is to be received.

【0130】

After that, it is basically the same as step S4 and after in the procedure example of FIG.

【0131】

It is also possible to confirm with the user of the own device whether or not to participate in the session.

【0132】

FIG. 15 shows an example of the processing procedure in this case.

【0133】

In this case, when each information processing device receives some request from the information processing device that starts the session described above to request participation in a certain session (step S21), it asks the user whether or not to start the session. Confirm (step S22).

【0134】

When the user gives an instruction to start the session (step S23), the process for starting the session is performed in the same manner as described above (step S24).

【0135】

After that, it is basically the same as step S4 and after in the procedure example of FIG.

【0136】

On the other hand, when the user gives an instruction not to start (step S23), for example, a message to the effect of refusal is sent to the information processing device of the request source to end the process.

【0137】

By the way, the user can create a plurality of sessions in one meeting by repeating the procedure as described above. It is also possible to create multiple meetings.

【0138】

FIG. 16 shows an example of the document information held by the document management unit 104 when a new session is added. In the case of the specific example shown in FIG. 16, the document of the "presentation" application called "examination result" is added.

【0139】

FIG. 17 is an example of session information held by the session management unit 105 when a new session is added. In the example of Fig. 17, a new "Project A regular meeting (2002/04/08)" session was created, the participating users were "Murai", "Iwamura", and "Ikeda", and the startup applications were "whiteboard" and "chat". "Notes", usage documents are "whiteboard" application documents called "idea diagram" and "whiteboard" application documents called "examination results", start date and time is "2002/04/08 13:00:00", end The date and time is stored as "2002/04/08 14:00:00".

【0140】

FIG. 18 shows an example of the meeting information held by the meeting management unit 106 when a new session is added. In the case of the specific example shown in FIG. 18, "Project A regular meeting (2002/04/08)" is added as a session related to the "Project A regular meeting" meeting.

【0141】

In this way, as the user repeats each session of each meeting, the meeting information, the session information, the user information, the application information, and the document information are accumulated.

【0142】

FIG. 19 shows an example of a link structure between a meeting and a session formed in the present embodiment. In the figure, 300 is a root node, 301 to 303 are nodes indicating a meeting, and 304 to 308 are nodes indicating a session. Although omitted in the figure, information about users, programs, and documents is linked to the node indicating the meeting and the node indicating the session.

【0143】

By the way, in the example of FIG. 19, the session node is linked to only one parent node, but the session node may be linked to a plurality of parent nodes. Further, although the hierarchy of the meeting node was a single hierarchy, the hierarchy of the meeting node may have a multi-layer structure or a network structure.

【0144】

Figure 20 shows an example when a session node can be linked to multiple parent nodes. In this example, for example, a session called Project A Regular Meeting (2002/04/01) is linked to both a meeting called Project A and a meeting called Regular Meeting.

【0145】

Figure 21 shows an example of a meeting node having two hierarchies. In this specific example, for the Project A regular meeting, the one in which the user of the own device attended (the own device participated) and the one in which the user of the own device was absent (the own device did not participate) were separated. For example, a session called Project A Regular Meeting (2002/04/01) is not directly linked to the node of Project A Regular Meeting, but to the parent node called Attendance, which is its child node. doing.

【0146】

Of course, FIGS. 20 and 21 are examples, and various link structures other than these are possible. It should be noted that such a complicated link structure may be formed when a new link is created, or the link structure may be directly edited by the user later. At that time, it is possible to edit the data of the meeting information and the session information, but the link structure of the meeting or the session is visually displayed as shown in FIGS. It is preferable to provide a GUI that edits the node image and the link image by adding, deleting, modifying, moving, etc., and automatically reflects this editing in various information.

【0147】

In the following, reference to various information will be described.

【0148】

In the present embodiment, since the information that enables the session belonging to the relevant meeting to be identified is stored in the meeting information, the session belonging to the specific meeting can be searched, the session to which the specific session belongs can be searched, or the specific session can be searched. It is possible to search for other sessions belonging to the meeting to which the session belongs, and to search for users, programs, and documents related to each meeting and each session.

【0149】

In the present embodiment, the information that enables the session belonging to the session to be identified is stored in the meeting information, but instead or in addition to the information, the meeting belonging to the session can be specified in the session information. You may want to store the information to be used.

【0150】

FIG. 22 shows an example of the procedure for referring to various information.

【0151】

In this procedure, the user can refer to the information of the meeting, the information of the session created in the past, and the information of the application and the document started in each session through the operation unit 107.

【0152】

The operation unit 107 displays a list of meetings stored in the meeting management unit 106 (step S31).

【0153】

When the user selects the desired meeting from the meeting list (step S32), the operation unit 107 informs about the meeting (for example, the meeting name, the list of participating users, the list of launched applications, the list of related sessions). Is inquired to and displayed in the meeting management unit 106, the user management unit 102, the application management unit 103, and the session management unit 105 (step S33). The user may be able to change this information through the operation unit 107.

【0154】

When the user selects a desired session from the session list (step S34), the operation unit 107 displays information about the session (for example, session name, list of participating users, list of launched applications, list of launched documents, start). The date and time (date and time, end date and time) are inquired and displayed in the session management unit 105, the application management unit 103, and the document management unit 104 (step S35).

【0155】

When the user selects the desired application from the list of launched applications (displayed in step S33 or S35) (step S36), the operation unit 107 asks the application management unit 103 to start the selected application. Then the application is launched (step S37).

【0156】

When the user selects the desired document from the list of startup documents (displayed in step S33 or S35) (displayed in step S38), the operation unit 107 tells the document management unit 104 the selected document. Is requested to start, and the document starts (step S39).

【0157】

In addition, the user can return to the desired list as appropriate. Further, although omitted in FIG. 22, the user may end the process at a desired time point when the target reference or the like is completed.

【0158】

Of course, in addition to the above, various variations are possible.

【0159】

For example, the operation unit 107 visually displays a link structure such as a meeting or a session as shown in FIGS. 20 or 21 instead of the above-mentioned list display function, and the user clicks a desired node. It may have a function that can be selected. In addition, it may have both a list display function and a visual display function so that the user can appropriately select and use it.

【0160】

It is also possible to search for a corresponding meeting or session by entering a desired key, for example.

【0161】

(Second Embodiment) This embodiment also makes it possible to distribute the session information to other users in advance and prepare for the session, and distribute the session information in advance. It is basically the same as the first embodiment except for the configuration for enabling the above. In the following, the differences from the first embodiment will be mainly described.

【0162】

FIG. 23 shows a configuration example of the information processing apparatus 200 according to the second embodiment of the present invention. As shown in FIG. 23, the information processing apparatus 200 of the present embodiment includes a communication unit 201, a user management unit 202, a session management unit 203, a meeting management unit 204, an application management unit 205, a document management unit 206, and an input / output unit. It consists of 207 and operation unit 208.

【0163】

The communication unit 201 is basically the same as the first embodiment. For example, the communication unit 201 detects a communicable information processing device and performs data communication with the detected information processing device.

【0164】

The user management unit 202 manages information about users related to meetings and sessions. The user management unit 202 stores and manages information such as "user ID", "address", "communication status", and "e-mail address" for each user as user information. The user management unit 202 may also manage, for example, an address, a telephone number, and the like as information about the user.

【0165】

The user ID is information for identifying a user who uses the information processing device, and is defined by using, for example, a UUID. If the information processing device and the user can be associated one-to-one and the address is a value unique to the information processing device, the address can be used as the user ID. Alternatively, the user's e-mail address or the like can be used.

【0166】

The address differs depending on the protocol used by the communication unit 201, but for example, when the TCP / IP protocol is used, the IP address can be used.

【0167】

The communication state is a variable indicating whether it is in a state where it can communicate with the information processing device or in a state where it cannot communicate. For example, it is set to True in the state where communication is possible, and set to False in the state where communication is not possible. When the communication unit 201 detects a new user, for example, the communication unit 201 notifies the user management unit 202 of the address of the detected user.

【0168】

When the address is used as the user ID, the user management unit 202 generates an entry in which the address is used as the user ID. In other cases, for example, the user management unit 202 may acquire the user ID from the information processing device using the communication unit 201 and generate a new entry in order to acquire the user ID. At this time, information such as an e-mail address and an address may be acquired together with the user ID. If you do not get an e-mail address with your user ID, you can get the information by another means and set it, but until it is set, you have not got an e-mail address etc. It becomes a setting. In either case, the communication status of the generated entry is True.

【0169】

When the communication unit 201 detects that it cannot communicate with any of the information processing devices, it notifies the user management unit 202. The user management unit 202 changes the communication status of the notified information processing device entry to False.

【0170】

If an entry having the user ID of the information processing device detected by the communication unit 201 already exists, the user management unit 202 changes the communication state of the entry to True.

【0171】

The application management unit 205 is basically the same as the first embodiment, and manages information about applications that can be used in its own device.

【0172】

The application management unit 205 stores and manages information such as "application ID", "application execution method", and "application startup state" for each application as application information.

【0173】

The application ID is an identifier unique to the application and is assigned by the application developer or the like.

【0174】

The method of executing the application is, for example, the path of the executable file when the application is an executable file. Further, for example, when using a form such as a COM server, the interface ID is saved.

【0175】

The document management unit 206 is basically the same as the first embodiment, and manages information about documents used in its own device.

【0176】

The document management unit 206 stores and manages as document information, for example, information such as "document ID", "document storage location", and "application ID of an application that handles documents" for each document. When controlling access to a document to be distributed in advance, it is preferable to further store and manage information indicating, for example, "access right to the document" as document information.

【0177】

The document ID is an identifier unique to the document, and a unique value is used for each document by UUID or the like. Documents shared by a plurality of information processing devices are associated with the same document ID in all the information processing devices. If each document is saved as a single file, keep the path of that file as the document storage location. When storing a plurality of documents in a database or the like, it is possible to adopt a different format as the document storage location format depending on the storage method.

【0178】

The document access right indicates whether the information processing apparatus can change or delete the document. In addition, the access rights for document changes can be configured to have a single access right for all changes, or multiple access rights depending on the type of change. .. For example, in a document structured as a set of a plurality of items, it is possible to set independent access rights for adding an item and changing an item.

【0179】

The session management unit 203 is basically the same as the first embodiment, and manages information related to the session.

【0180】

The session management unit 203 provides session information such as "session ID", "version number", "meeting to which the session belongs", "list of participants in the session", and "list of documents used in the session" for each session. , "List of applications used in the session", etc. are stored and managed.

【0181】

The version number is updated every time the session information held by the session management unit 203 is changed, and is a value that can specify the chronological order. For example, use an integer value that is incremented by 1 each time it is changed.

【0182】

The session ID is a unique identifier for each session, and UUID or the like is used. The session ID holds the same value in the information processing device used by all users participating in the session.

【0183】

The meeting management unit 204 is basically the same as the first embodiment, and manages information related to the meeting.

【0184】

The meeting management unit 204 stores and manages information such as "meeting ID" and "session list" for each meeting as meeting information.

【0185】

The meeting ID is an identifier uniquely assigned to each meeting, and UUID or the like is used.

【0186】

The meeting information can also include a list of participating users and a list of applications.

【0187】

The input / output unit 207 is added in the present embodiment, and has a function of transmitting session information to another information processing device and a function of performing processing necessary for capturing session information received from the other information processing device. And have.

【0188】

When transmitting the session information, necessary information is taken out from the session management unit 203, the meeting management unit 204, the user management unit 201, and the application management unit 205, and the session information in a predetermined format is created and transmitted.

【0189】

When the information processing device receives the session information, the input / output unit 207 analyzes the session information and sets the session management unit 203, the meeting management unit 204, the user management unit 202, and the application management unit 205.

【0190】

Based on the above example, the session information includes the session ID, the version number of the session information, the list of user IDs of the users participating in the session, the list of application IDs of the applications used in the session, and the session to which the session belongs. Contains the meeting ID.

【0191】

The operation unit 208 is basically the same as in the first embodiment, in which the user operates the information processing device and the information processing device presents information to the user. It is for providing user interface functions such as.

【0192】

Hereinafter, the operation of this embodiment will be described.

【0193】

The processing procedure for exchanging information about the session at the start of the session, instead of distributing the session information to other users in advance, is the same as that of the first embodiment (for example, FIG. 3). If the session information is distributed in advance, steps S1 and S2 (or only step S2) in FIG. 3 may be performed in advance, and the session information may have already been distributed in the part of step S3. It is corrected to the processing assuming. Note that FIG. 24 shows an example of the processing procedure of the pre-creation / distribution part when the session information is distributed in advance. In addition, FIG. 25 shows an example of the processing procedure of the receiving / capturing part when the session information distributed in advance is fetched.

【0194】

In the following, the procedure for distributing session information in advance will be mainly described.

【0195】

(Steps S1 and S41: Creating a meeting) When the user creates new session information, the operation unit 208 is used to execute the session information creation procedure.

【0196】

First select a meeting and create a session that belongs to the selected meeting. If a list of users participating in the meeting or a list of applications is set, these values may be used as initial values of the list of users participating in the session and the application list. Users add and remove participating users and applications as needed.

【0197】

It is also possible to create a session without selecting a specific meeting. In this case, neither the participating user nor the application is set, so the user needs to set at least the participating user.

【0198】

When a session is created without specifying a meeting, for example, a new meeting is created according to the created session and managed as belonging to the meeting. Alternatively, for example, it is managed as belonging to a special meeting to which a session created without specifying a specific meeting belongs.

【0199】

When a session is created, it is assigned a new session ID.

【0200】

(Steps S42, S43: Pre-creation and pre-distribution of session information, Steps S51, S52: Reception and capture of session information) Session information is not only shared at the start of the session, but also distributed to participants in advance. It is also possible.

【0201】

By distributing the session information to the participants in advance, it becomes possible for the participants other than the creator of the session information to register the application to be used in the session in advance. In addition, it is possible to set a schedule at the scheduled time of the session by linking the session information and the schedule management software.

【0202】

In order to distribute session information in advance, session information data related to the session information to be distributed is created and distributed to participants by e-mail, for example. Participants to whom the session information data is distributed reads the session information data and sets the session information.

【0203】

[Pre-creation and pre-distribution of session information]

To create the session information data, the operation unit 208 instructs the input / output unit 207 to create the session information data.

【0204】

The input / output unit 207 reads the session information from the session management unit 203. Further, the user information is read from the user management unit 202 for each user in the participating user list of the session information. Also, the meeting information is read from the meeting management unit 204. If the application is registered in the session information, the application information is read from the application management unit 205.

【0205】

The user information included in the session information data includes the user ID. Of course, it is also possible to include information other than the user ID stored in the user management unit 204 in the session information data. If all user information is included in the session information data, the amount of data will increase. Therefore, the session information data should include only the user ID, and the information other than the user ID should be included in the session by the participants who need such information. It is also possible to reduce the amount of session information data by providing a means for acquiring the information data from the participants who distributed it. Similarly, it is not always necessary to include all the information regarding the meeting information, the session information, and the application information in the session information data, and only the meeting ID, the session ID, and the application ID can be included in the session information data.

【0206】

The input / output unit 207 creates session information data by serializing the information read from each part according to a predetermined format.

【0207】

By giving the input / output unit 207 an SMTP client function, it is possible to directly send the session information data created by the input / output unit 207 to the participants. In this case, by using the participant's e-mail address for the user information managed by the user management unit 202, it is of course possible to prevent the user from entering the e-mail address again. ..

【0208】

The means for distributing the session information data can be various methods other than giving the input / output unit 207 an SMTP client function, and is not limited to the use of e-mail as described here. For example, even when using e-mail, it is naturally possible to output the session information data as a file and send it using external e-mail software. Further, for example, the same purpose can be achieved by arranging the session information data output as a file on the Web server and downloading it using the HTTP protocol.

【0209】

[Receive and capture session information]

Regardless of which means is used to distribute the session information data, each participant reads the session information data in the input / output unit 207.

【0210】

The input / output unit 207 analyzes the session information data and notifies the session management unit 203 of the session information.

【0211】

The session management unit 203 searches the session information based on the session ID included in the notified session information, and if there is no session information entry having the same session ID, creates a new session information entry. Set the session ID etc. In addition, the meeting information to which this session information belongs and the session ID are notified to the meeting management unit 204.

【0212】

The meeting management unit 204 searches for the notified meeting information from the managed meeting information, and if the meeting information already exists, adds it to the session list of the meeting information. If the meeting information is not found, create a new meeting information and add the session ID to the list of sessions.

【0213】

Similarly, the participating user list and user information are notified to the user management unit 202, the user management unit 202 searches for the user information entry based on the user ID, and if the entry does not exist, the new user information entry. To create. If session information with the same session ID as the session ID included in the notified session information is found, the version information of the session information is compared. If the version of the distributed session information is newer than the version information of the session information already stored, the session information stored by the distributed session information is updated.

【0214】

By adding the version information to the session information in this way, even the session information once distributed can be changed and redistributed.

【0215】

By the way, if the session information can be freely changed even by the participants, the changes will conflict with each other, so it is desirable to perform appropriate access control. For example, if only the creator can change the session information and participants other than the creator cannot change the session information, the changes will not conflict.

【0216】

In this case, even if the session information is distributed in advance, the participants to whom the session information is distributed may only be able to see the session information. Therefore, for example, the participants to whom the session information is distributed can also access control such that the application and the document can be added and the application and the document added by the participant can be deleted. In this case, the participants to whom the session information is distributed keep a record of the applications and documents that they have added, and simply distribute all the information when the session information with the new version information is distributed. Instead of changing with the updated session information, you can add the applications and documents you added to the updated session information. It is also possible for the creator of the session information to give a specific participant the right to change when the session information is distributed to the participating members.

【0217】

(Step S3: Start of session) To start the session, the operation unit 208 instructs the session management unit 203 to start the session.

【0218】

The session management unit 203 inquires the user management unit 202 about the communication status of each user included in the participating user list of the session information, and requests the communication unit 201 to create a communication connection with the information processing device of the user who can communicate. .. When the communication unit 201 creates a communication connection with the designated information processing device, the session management unit 203 transmits the session information to each information processing device.

【0219】

In the information processing apparatus that has received the session information, the session management unit 203 analyzes the session information and searches for an entry of the session information having a session ID equal to the session ID included in the received session information.

【0220】

If the session information entry is not found, it means that the session information has not been distributed in advance.

【0221】

In this case, create a new session information entry and set session information such as session ID. In addition, the meeting information to which this session information belongs and the session ID are notified to the meeting management unit 204. The meeting management unit 204 searches for the notified meeting information entry from the managed meeting information, and if the meeting information entry already exists, adds it to the list of sessions of the meeting information. Also, if the meeting information entry is not found, create a new meeting information and add this session to the session list of the created meeting information. Similarly, the information of the participating users and the application is notified to the user management unit 202 and the application management unit 205, respectively, and if the entry does not exist, a new entry is created.

【0222】

If the session management unit 203 has an entry for session information having the same session ID as the received session information, it means that the session information has been distributed in advance.

【0223】

In this case, the values of each field of session information are compared, and if there is a difference, it is updated. Further, when a user included in the participating user list of the newly received session information is added, the user management unit 202 is notified of the information about the added user, and the user management unit 202 is an unknown user. Add a new user information entry. The same applies to applications and the like. If the meeting to which the session belongs has been changed, the session ID, the meeting ID of the previously set meeting, and the meeting information of the new meeting are notified to the meeting management unit 204. The meeting management unit 204 deletes the session from the meeting information to which the session previously belonged, and adds the session to the meeting information of the new meeting. If there is no meeting information entry corresponding to the new meeting information, create a new meeting information entry. Participants who added the application before the session started need to have other participants add the application to the session information, so send a message containing the application ID of the added application to other participants. Send to participants. Participants who receive this message add the application to the session information.

【0224】

By distributing the session information in advance and allowing participants other than the creator of the session information to change the session information such as adding applications, it is different from the person who intends to hold the meeting. Participants will also be able to prepare for the meeting.

【0225】

By the way, the session information data created for distributing the session information in advance can also include information about the document used in the conference. This case will be described below.

【0226】

The document information included in the session information data can be in a format including the content of the document itself or in a format including information for acquiring the document. If the session information data contains multiple documents, each format can be selected for each document.

【0227】

When document information is included in the session information data, when the input / output unit 207 creates the session information data, the document management unit 206 gives the document ID, the storage location of the document, the application ID of the application that handles the document, and the access right to the document. Is read.

【0228】

When the content of the document itself is included in the session information data, the document is read from the document storage location and added to the session information data together with other information. At this time, depending on the format of the session information data, processing such as encoding the contents of the document may be required.

【0229】

When distributing information for retrieving a document, several formats are possible depending on the method of retrieving the document. If the document is placed on a web server and the document is retrieved using the HTTP protocol, the URL of the document will be added to the session information data along with other information. It is also possible to configure the document management department to have a function to exchange documents independently of the session. In this case, the document can be specified by the document ID, so the document can be specified in addition to the document ID. It is not necessary to send specific information.

【0230】

When the session information data including the document information is distributed, the participant who receives the session information data analyzes the session information data in the input / output unit 207 and notifies the document management unit 206 of the document information. When the content of the document is included in the session information data, the document is saved according to the document management method used by the document management unit 206, and an entry for the document information is created. When the session information data includes information for acquiring the document instead of the contents of the document, the document management unit 206 acquires and saves the document based on the information included in the session information data.

【0231】

In either case, the pre-acquired document cannot be modified until the session has started. When the session is started, the document management unit 206 treats the documents with the same document IDs as the same documents if they already hold the documents based on the document IDs.

【0232】

By distributing the document together with the session information in this way, the time required for preparation for starting the meeting can be shortened, and the meeting can be started promptly. In addition, if the document is distributed in advance, it is possible for each participant to confirm the content of the document in advance. Although it is possible to simply send the document used in the meeting by e-mail etc. with the conventional technology, it will be treated as a document different from the document actually shared in the session, and the document There is a problem that the management of is complicated. On the other hand, according to the present embodiment, the document distributed in advance and the document shared in the session are treated as one document, which facilitates management.

【0233】

It should be noted that each of the above functions can be realized even if it is described as software and processed by a computer having an appropriate mechanism. Further, the present embodiment can also be implemented as a program for causing the computer to execute a predetermined means, for the computer to function as a predetermined means, or for causing the computer to realize a predetermined function. In addition, it can be implemented as a computer-readable recording medium on which the program is recorded.

【0234】

It should be noted that the configuration illustrated in the embodiment of the present invention is an example, and is not intended to exclude other configurations, and a part of the illustrated configuration may be replaced with another or one of the illustrated configurations. It is also possible to obtain another configuration by omitting a part, adding another function or element to the illustrated configuration, or combining them. In addition, another configuration that is logically equivalent to the illustrated configuration, another configuration that includes a part that is logically equivalent to the illustrated configuration, another configuration that is logically equivalent to the main part of the illustrated configuration, and the like are also possible. is there. Further, another configuration that achieves the same or similar purpose as the illustrated configuration, another configuration that has the same or similar effect as the illustrated configuration, and the like are also possible. In addition, various variations of the various constituent parts illustrated in the embodiment of the present invention can be appropriately combined and implemented. Moreover, the embodiment of this invention is an invention as an individual device, an invention about two or more related devices, an invention as a whole system, an invention about a component inside an individual device, or a method corresponding thereto. It includes / inherently inventions related to various viewpoints, stages, concepts or categories such as inventions. Therefore, the invention can be extracted from the contents disclosed in the embodiment of the present invention without being limited to the illustrated configuration.

【0235】

The present invention is not limited to the above-described embodiment, and can be implemented with various modifications within the technical scope thereof.

【0236】

[Effect of the invention]

According to the present invention, conference information, data used in a conference, and the like can be easily referred to and used in an electronic conference system.

[Simple explanation of drawings]

FIG. 1 is a diagram showing a configuration example of an information processing device according to an embodiment of the present invention. FIG. 2 is a diagram showing a network configuration example when a plurality of information processing devices according to the same embodiment are gathered to perform a session. 3] A flowchart showing an example of a processing procedure of the information processing apparatus according to the same embodiment [Fig. 4] A diagram showing an example of information held by the user management unit in the same embodiment [Fig. 5] Information held by the application management unit in the same embodiment. FIG. 6 is a diagram showing an example of information held by the meeting management unit in the same embodiment. FIG. 7 is a diagram showing an example of information held by the document management unit in the embodiment. FIG. 8 is a diagram showing an example of information held by the document management unit in the embodiment. [Fig. 9] Fig. 9 shows an example of information held by the meeting management unit when a new session is created in the same embodiment. [Fig. 10] Fig. 10 shows an example of information held by the session management unit in the same embodiment. FIG. 11 is a diagram showing an example of information held by the session management unit when the session is started. [Fig. 11] Fig. 11 is a diagram showing an example of information held by the document management unit when a document is started after the session in the same embodiment is started. FIG. 12 is a diagram showing an example of information held by the session management unit when an application is started and a document is started after the session in the same embodiment is started. [Fig. 13] When the session in the same embodiment is terminated. FIG. 14 is a diagram showing an example of the processing procedure of the information processing apparatus according to the same embodiment. FIG. 15 is a flowchart showing an example of the processing procedure of the information processing apparatus according to the same embodiment. FIG. 16 is a diagram showing an example of information held by the document management unit when a new session is added in the same embodiment. FIG. 17 is a diagram showing information held by the session management unit when a new session is added in the same embodiment. A diagram showing an example [Fig. 18] A diagram showing an example of information held by the meeting management unit when a new session is added in the same embodiment [Fig. 19] A diagram for explaining a link structure between a meeting and a session [Fig. 20] ] Diagram to explain the link structure of meetings and sessions [FIG. 21 is a diagram for explaining a link structure between a meeting and a session. FIG. 22 is a flowchart showing an example of a processing procedure of the information processing device according to the embodiment. FIG. 23 is another configuration of the information processing device according to the embodiment. FIG. 24 is a flowchart showing an example of a processing procedure of the information processing apparatus according to the same embodiment. FIG. 25 is a flowchart showing an example of a processing procedure of the information processing apparatus according to the same embodiment.

100,200 ... Information processing device, 101,201 ... Communication department, 102,202 ... User management department, 103,205 ... Application management department, 104,206 ... Document management department, 105,203 ... Session management department, 106,204 .. .Meeting management department, 107,208 ... operation department, 207 ... input / output department