Communication program, communication method, and communication apparatus

The present invention relates to a communication program, a communication method, and a communication device, and more particularly to a communication program, a communication method, and a communication device that collaborate between client terminals using a plurality of types of communication means including device type information and user identification information.

Recently, it has been recognized that collaboration (collaboration) using a computer system by multiple people is effective for improving intellectual productivity. By performing this collaboration, it becomes easy to share data using the network, so that it is possible to smoothly carry out collaborative work by cooperation between network users. According to this, groupware products having a function of supporting communication between users such as address books, and electronic conference support applications for sharing applications to edit and browse files have been developed.

On the other hand, in recent years, one user has come to own a plurality of terminal devices, and there are various devices (tools) that can collaborate with each other. In this way, collaboration means are diversifying, and in parallel with this, it is becoming common to perform communication (multimodal) using a plurality of terminal devices and applications at the same time. For example, you can share a PC (Personal Computer) application while talking on the phone, or send text information such as URL (Uniform Resource Locator) and phone number to instant message (hereinafter referred to as "IM") or chat. Collaboration styles such as communicating with a computer have become established.

Therefore, for example, when there is a telephone call from the other party, is the other party making a call using a fixed IP (Internet Protocol) phone, or is the other party making a call using a softphone running on a PC, etc. Since the possible collaboration methods differ depending on the type, proper collaboration cannot be performed without confirming the status of the other party, and the procedure for collaboration has become extremely complicated.

In addition, when a user who owns multiple terminal devices and multiple IDs (Idetification) uses different terminal devices and IDs according to the location and time, the IP address of the PC used at that time, IM, or You need to look up the chat ID yourself or ask the other person for confirmation. Furthermore, when sharing applications and collaborating, it is necessary to confirm whether or not applications having an application sharing function are installed and whether or not there is a possibility of interconnection with each other. Moreover, even after the collaboration method is confirmed, it is necessary for the user to input the access destination information into the PC and start the collaboration.

Some softphones running on a PC have collaboration functions such as file transfer, application sharing, and shared whiteboard, in addition to simple call and message functions. In addition, some have a user status monitoring function called a buddy list. In this buddy list, the user pre-registers the SIP URI of a specific user (IP phone, IM, etc. SIP (Session Initiation). By registering an ID) for an application that communicates using Protocol), you can always check the user's softphone status (online / offline, etc.), and by selecting it, you can easily check it. You can call, send messages with IM, and share applications. However, the buddy list is closed within one terminal device and can only be used for phone calls and IMs using a softphone, and application sharing can only be used on a PC on which the softphone is installed. Also, you have to verbally check the applications that the other party can use, or if you can not share the application, you have to manually convert the format and send the file by some means, which is an appropriate collaboration method. The choice is not easy. Therefore, when one user uses a plurality of various terminal devices at the same time, a complicated procedure is required.

Therefore, there is known a method of retaining telephone call session information, identifying the other party from the call session and establishing a connection when there is an access request by another communication means (see, for example, Patent Document 1). According to Patent Document 1, in a call center, when a customer and an operator are responding by telephone, a Web (World Wide Web) screen can be shared or a telephone reservation can be made from the Web. Therefore, it is possible to make a call or share a Web page without specifying the ID of the other party.<patcit num="1"><text>Japanese Unexamined Patent Publication No. 2001-94671</text></patcit>

<p> However, in Patent Document 1, the usage environment is limited to the call center, and the collaboration method is limited to collaboration between the telephone and the Web, and it is difficult to apply to general collaboration that makes full use of various communication tools and applications. There was a problem.</p><p> Therefore, when a plurality of users collaborate while using a plurality of terminal devices, it is easy to know what kind of applications can be used by each other, which terminal device and ID should be used for access, and the like. In addition, there was a problem that it was not possible to easily control each other's communication media and applications, and it was not possible to collaborate smoothly.</p><p> The present invention has been made in view of these points, and is a communication program, a communication method, and a communication device capable of easily selecting and executing its own communication means according to the communication means available to the communication partner. The purpose is to provide.</p>

<p> In the present invention, in order to solve the above problem, a communication program as shown in FIG. 1 is provided. The communication program according to the present invention is a communication program in which client terminals collaborate with each other by using a plurality of types of communication means including device type information and user identification information.</p><p> The computer that executes the communication program of the present invention has the following functions. The profile management means 3 manages the unique information 3a in which the user ID is associated with the set of the device type information and the user identification information for each communication means.</p><p> When the session using any of the communication means is established between the users, the application control means 4 refers to the unique information 3a managed by the profile management means 3, and the device type information and the user identification information of the communication means for which the session is established. The pair with and is associated with the user ID.</p><p> The collecting means 5 collects presence information 5a in which the device type information and the user identification information for each communication means are associated with the state information indicating whether or not the communication means can be used.</p><p> When the user ID is specified by the application control means 4, the presence management means 6 refers to the presence information 5a, and is a communication means that can be used by the communication partner with respect to the client terminals 1 and 1a of the user for which the session has been established. Notify the user identification information of the communication partner.</p><p> According to such a communication program, the profile management means 3 manages the unique information 3a in which the user ID is associated with the set of the device type information and the user identification information for each communication means. Further, when the session using any of the communication means is established between the users by the application control means 4, the unique information 3a managed by the profile management means 3 is referred to, and the device type information of the communication means for which the session is established and the user. The pair with the identification information is associated with the user ID. Further, the collecting means 5 collects the presence information 5a in which the device type information and the user identification information for each communication means are associated with the state information indicating whether or not the communication means can be used. Then, when the user ID is specified by the application control means 4 by the presence management means 6, the presence information 5a is referred to, and the communication partner can use the communication with the client terminals 1 and 1a of the user whose session has been established. The user identification information of the communication partner in the means is notified.</p><p> Further, in order to solve the above problem, in a communication method in which client terminals collaborate using a plurality of types of communication means including device type information and user identification information, the device type information for each communication means is used. When a unique information in which a user ID is associated with a pair with the user identification information is managed and a session using any of the communication means is established between users, the unique information is referred to and the communication established by the session. Whether or not the communication means can be used for the device type information and the user identification information for each communication means by associating the user ID with the pair of the device type information and the user identification information of the means. When the user ID is specified by collecting the presence information associated with the state information indicating the above, the presence information is referred to, and the communication partner can use the client terminal of the user for whom the session has been established. Provided is a communication method characterized in that the presence information of the communication partner in the communication means is notified.</p><p> According to such a communication method, unique information in which a user ID is associated with a set of device type information and user identification information for each communication means is managed, and a session using either communication means is established between users. The unique information is referred to, and the pair of the device type information of the communication means established by the session and the user identification information is associated with the user ID. In addition, presence information in which the device type information and the user identification information for each communication means are associated with the state information indicating whether or not the communication means can be used is collected. Then, when the user ID is specified, the presence information is referred to, and the presence information of the communication partner in the communication means that can be used by the communication partner is notified to the client terminal of the user whose session has been established.</p><p> Further, in order to solve the above problem, in a communication device that collaborates between client terminals using a plurality of types of communication means provided with device type information and user identification information, the device type information for each communication means is used. When a profile management means that manages unique information in which a user ID is associated with a pair with the user identification information and a session using any of the communication means are established between users, the unique information managed by the profile management means. The application control means for associating the user ID with the pair of the device type information and the user identification information of the communication means established by the session, the device type information for each communication means, and the device type information for each communication means. When the user ID is specified by the collecting means for collecting presence information in which the user identification information is associated with the state information indicating whether or not the communication means can be used, and the application control means, the presence information is referred to. A communication device, further comprising a presence management means for notifying the client terminal of the user to whom the session has been established, the presence information of the communication partner in the communication means that can be used by the communication partner. Is provided.</p><p> According to such a communication device, the same processing as that of the computer that executes the communication program is executed.</p>

<p> According to the present invention, when a session using any of the communication means is established between users, each other's presence information is notified to the client terminal of the user for whom the session has been established. Collaboration using the desired communication means can be easily and surely realized without confirmation. As a result, the efficiency of collaboration can be improved.</p>

Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings. First, the outline of the invention applied to the embodiment will be described, and then the specific contents of the embodiment will be described.

FIG. 1 is an explanatory diagram of the principle of the present invention. The communication system 40 shown in FIG. 1 is composed of client terminals 1 and 1a and a server 2 having the same functions, respectively.

The client terminal 1 (1a) includes an information management means 7 (7a) and an application control UI 8 (8a). The information management means 7 (7a) collects information on the application status and peripheral devices / services from the communication means 23 (23a) in the terminal, and registers the information in the server 2.

The application control UI8 (8a) acquires and displays the computer environment information of the user himself / herself and the collaboration (collaboration) partner from the server 2, and performs an operation for collaboration with the client terminal 1a (1) which is the communication partner. It is a user interface.

The server 2 has a profile management means 3, an application control means 4, a collection means 5, and a presence management means 6. The profile management means 3 manages the unique information 3a in which the user ID is associated with the set of the device type information and the user identification information for each communication means.

When the session using any of the communication means is established between the users, the application control means 4 refers to the unique information 3a managed by the profile management means 3, and the device type information and the user identification information of the communication means for which the session is established. The pair with and is associated with the user ID.

In addition, the application control means 4 acquires session information from a dedicated server such as a SIP server or IM server when a new session is created or, for example, the communication means uses VoIP (Voice over Internet Protocol) or IM. Control various communication means such as sending files.

The collecting means 5 collects presence information 5a in which the device type information and the user identification information for each communication means are associated with the state information indicating whether or not the communication means can be used.

The presence information 5a stores data collected from the information management means 7 (7a), data collected from the communication means 21 and 22 via a dedicated server (not shown), and the like.

When the user ID is specified by the application control means 4, the presence management means 6 refers to the presence information 5a, and is a communication means that can be used by the communication partner with respect to the client terminals 1 and 1a of the user for which the session has been established. Notify the presence information of both parties.

According to such a communication system 40, the information management means 7, 7a aggregates the information about the communication means 21, 22, 23, 23a into the presence management means 6 of the server 2. Then, for example, when a session between the communication means 21 and 22 is established, the presence information of the communication partner is notified to the application control UIs 8 and 8a, respectively. This information includes information necessary for collaborating with a communication partner such as an IP address and a user ID. Therefore, by operating the application control UI8 (8a), the user can easily realize the collaboration without confirming the IP address, user ID, etc. with the other party or directly inputting them manually.

Hereinafter, embodiments of the present invention will be specifically described. FIG. 2 is a diagram showing a system configuration example of the first embodiment. The communication system 500 shown in FIG. 2 is a system having a function of dynamically adding collaboration based on existing session information, and the server 100, the client 200, 201, the SIP server 300, and the IM server 400 are connected to each other. It is connected with.

Further, in the communication system 500, a collaboration group 50 composed of the client 200 and the communication media 60 and a collaboration group 51 composed of the client 201 and the communication media 65 are formed.

Applications such as IM, e-mail, and file transfer means are installed on the clients 200 and 201, respectively. The communication media 60 includes a mobile phone 61, an IP phone 62 that has an IP address and makes a real-time voice call using the Internet, and a softphone (softwarephone) 63 that operates on the application of the client 200. are doing.

Each application of the client 200, the mobile phone 61, the IP phone 62, and the softphone 63 constitute a communication tool for collaborating with the collaboration group 51, respectively.

The communication media 65 includes a mobile phone 66, an IP phone 67, and a softphone 68, which have the same functions as the communication media 60, respectively. Each application of the client 201, the mobile phone 66, the IP phone 67, and the softphone 68 each constitute a communication tool for collaborating with the collaboration group 50.

User A and User B collaborate with each other using the communication tools of collaboration group 50 and collaboration group 51, respectively. The server 100 is a computer that collects and manages information from clients 200 and 201.

The SIP server 300 assists in processing such as VoIP session establishment, editing, and termination between communication tools as an intermediary. In addition, the IM server 400 has a function of managing, referencing, and transmitting / receiving IM of the user's presence information regarding IM. That is, the SIP server 300 and the IM server 400 have a function of notifying the outside of events and presence information related to VoIP and IM, and these servers are provided with an open interface such as Parlay (registered trademark). A server or a SIP application server that obtains a SIP signaling program is preferable.

Next, the hardware configuration of the server used in this embodiment will be described. FIG. 3 is a diagram showing a hardware configuration of the server used in this embodiment. The entire device of the server 100 is controlled by the CPU (Central Processing Unit) 101. A RAM (Random Access Memory) 102, a hard disk drive (HDD) 103, a graphic processing device 104, an input interface 105, and a communication interface 106 are connected to the CPU 101 via a bus 107.

RAM102 temporarily stores at least a part of OS (Operating System) programs and application programs to be executed by CPU101. In addition, various data required for processing by the CPU 101 are stored in the RAM 102. The OS and application programs are stored in the HDD 103. A program file is stored in the HDD 103.

A monitor 11 is connected to the graphic processing device 104. The graphic processing device 104 causes the image to be displayed on the screen of the monitor 11 according to the command from the CPU 101. A keyboard 12 and a mouse 13 are connected to the input interface 105. The input interface 105 transmits signals sent from the keyboard 12 and the mouse 13 to the CPU 101 via the bus 107.

The communication interface 106 is connected to the network 10. The communication interface 106 transmits / receives data to / from another computer via the network 10.

With the hardware configuration as described above, the processing function of the present embodiment can be realized. Although the configuration of the server 100 is shown in FIG. 3, the clients 200 and 201 can be realized by the same hardware.

In order to collaborate in a system having such a hardware configuration, the following functions are provided in the server 100 and the clients 200 and 201. FIG. 4 is a block diagram showing the functions of the server and the client.

The server 100 has an application control unit 110, a presence management unit 120, a presence DB (database) 130, a profile management unit 140, a profile DB 150, and an interface unit 160.

The application control unit 110 controls various applications and communication media 60 and 65 by creating a new session, acquiring session information from the SIP server 300 and IM server 400, and transmitting a file.

Further, when the application control unit 110 acquires the presence information from the SIP server 300 or the IM server 400, the application control unit 110 converts it into a format that can be read by the presence management unit 120 as necessary, and transmits the presence information to the presence management unit 120. The presence information to be notified is, for example, the SIP URI and IP address of the communication tool of user A, and if the communication tool is a mobile phone 61, an IP phone 62 or a soft phone 63, whether these are online, offline or in a call. Information, or the SIP URI of user B's mobile phone 66, IP phone 67, or soft phone 68, which is the other party of the call if the call is in progress.

When the presence management unit 120 acquires presence information from the application control unit 110 or the local application information management unit 230 described later, it stores and manages each user in the presence DB 130, and notifies the clients 200 and 201 according to the situation. ..

In the profile management unit 140, unique information in which the user ID of user A is associated with the information obtained by combining the media type (device type information) and the media ID (user identification information) for each communication media 60 or client 200 is associated with each other. When the user profile is acquired, it is stored and managed in the profile DB150. The user profile will be described in detail later.

The interface unit 160 performs data communication via the network 10 by TCP (Transmission Control Protocol) / IP. Next, clients 200 and 201 will be described.

Since the main parts of the functions of the clients 200 and 201 are equal to each other, the functions of the client 200 will be described as a representative. The client 200 has an application 210, an application control UI 220, a local application information management unit 230, a profile operation UI 240, and an interface unit 250.

Application 210 is an application installed on the client 200. The application control UI 220 is a user interface that acquires communication tool usage environment information of users A and B from the server 100 and performs operations for collaboration such as displaying the information on a monitor 11.

The local application information management unit 230 checks the status of the application 210, such as the type of the application 210 installed by referring to the registry or searching a specific folder, and whether or not the application 210 has a sharing function. Collect and register with server 100.

The profile operation UI 240 is a user interface that transmits the registration information to the profile management unit 140 when there is a user profile registration operation by input using the user's keyboard 12 or mouse 13.

The interface unit 250 has the same functions as the interface unit 160. In the following, the function possessed by the client 201 is represented by adding "a" to the end of each part of the function possessed by the client 200. For example, the application control UI of the client 201 is the application control UI 220a.

FIG. 5 is a diagram illustrating an outline of the operation of the communication system. In FIG. 5, a part of the functions of the IM server 400 and the server 100 and a part of the functions of the clients 200 and 201 are omitted.

When the client 200 is started, the local application information management unit 230 examines the application 210 installed in the client 200 and notifies the presence management unit 120 of the information as the presence information of the user A.

On the other hand, the presence information of the mobile phone 61, the IP phone 62 and the softphone 63 is transmitted from the SIP server 300 or the IM server 400, and is notified to the presence management unit 120 through the application control unit 110. This operation is performed on the communication tool for each user.

Here, which user's presence information is notified by the SIP server 300 and the IM server 400 is determined when user A and user B register their own SIP URI in the profile management unit 140 (user profile registration described later). The app control unit 110 (in the phase) gives instructions to the SIP server 300 and the IM server 400.

The presence management unit 120 classifies and manages the presence information notified from the application control unit 110 and the local application information management unit 230 for each user. Then, when a session between the communication tool of user A and the communication tool of user B is established, the presence management unit 120 (including the case where the session has already been established when the client is started) sends the presence information of both. To the app control UI 220 of the client 200 and the app control UI 220a of the client 201.

Here, for example, when the application control UI 220 receives the presence information of the user B, the presence information of the user B, that is, the communication tool that can be used by the user B is displayed by popping up to that effect on the monitor 11. This display method is not particularly limited, but for example, a method of displaying all the presences of the client 200 and the client 201 (source and destination) in a list, a method of highlighting only communication tools that can be used in common with each other, and the like. Can be mentioned. As a result, the user A can know what kind of application 210a and the communication medium 65 can be used by the user B.

FIG. 6 is a diagram showing an operation screen of the application control UI of the first embodiment. The application control UI 220 displays a collaboration confirmation unit 14 such as an icon for confirming the collaboration status on the operation screen 11a. Then, when the collaboration with the communication tool used by the user B is established, the user A is notified by displaying the balloon 15. When the user A selects (clicks) the collaboration confirmation unit 14, the communication tool usage environment screen 16 indicating the communication tools currently available to the user B is displayed on the operation screen 11a.

Further, on the communication tool usage environment screen 16, items and icons 16a to 16f related to the items are displayed for each communication tool. For example, as shown in FIG. 6, when a softphone, a fixed IP phone, or a mobile IP phone can be used as a voice communication means, these are displayed as each item of the telephone.

After that, when the communication tool displayed on the communication tool usage environment screen 16 is selected by the user A, for example, by double-clicking the icon 16a, the application control UI220 corresponds to the application control UI220a via the server 100. Let the process be executed. For example, the application control UI220 sends a file, and the application control UI220a takes a reaction corresponding to the file.

By selecting each item on the communication tool usage environment screen 16, user A can start collaboration with user B using the selected communication tool.

By the way, in order to perform such collaboration, the communication system 500 executes three phases of a user profile registration phase, a presence collection / notification phase, and an addition phase of collaboration means. Hereinafter, each phase will be described step by step.

&lt;User profile registration phase&gt; The user profile registration phase is a phase executed when user A registers a user profile, which is information about a user ID given to various communication media, in the server 100.

User A operates the profile operation UI 240 to access the profile management unit 140 of the server 100, and stores the user profile in the profile DB 150. At this time, when the information about the media is updated, by making an event notification request, the event information (for example, in the case of an IP phone, information such as when a call is in progress or when logging in) is surely sent to the SIP server. Notify 300. The event notification request will be described in detail later.

Next, the user profile stored in the profile DB150 will be described. In the present embodiment, the user profile is stored as a table. The user profile may be expressed in XML (eXtensible Markup Language), for example.

FIG. 7 is a diagram showing a user profile table. The user profile table 151 is provided with columns (attributes) for user ID, media type, media ID, and description. The items arranged horizontally in each column are related to each other to form one user profile.

In the user ID column, the user ID foo, which is the identifier of the user A in the communication system 500, and the user ID goo, which is the identifier of the user B, are set. In the media type column, the device type information of the communication media 60 and the application 210 that can be used by the user A is set in association with the user ID foo. Further, the device type information of the communication media 65 and the application 210a that can be used by the user B is set in association with the user ID goo.

Here, for example, "voip" of the user ID "foo" means the media type of the mobile phone 61, the IP phone 62 and the softphone 63, "im" means the media type of the instant message, and "mail" means the mobile phone. It means the media type of the email address of the phone 61, and "collabo" means the media type assigned to the client program of the client 200. That is, "collabo" is a concept including an application control UI 220, a local application information management unit 230, and a profile operation UI 240.

In the media ID field, an ID (unique to the communication media and application) that identifies the communication media or application is set. In the description column, a description (entry) of which media the media ID is specifically assigned to is set. The explanation set in this explanation column is described in each item of the communication tool usage environment screen 16.

In this way, the communication tool that notifies the presence information from the local application information management unit 230 and the local application information management unit 230a to the presence management unit 120, and the presence information that is notified from the SIP server 300 or the IM server 400 to the presence management unit 120. It is set separately from the communication tool to be used.

Next, the processing sequence (processing operation) of the user profile registration phase will be described by taking the IP phone registration phase as an example. FIG. 8 is a diagram showing a processing sequence of the user profile registration phase.

First, when the profile operation UI 240 confirms the login request by inputting the user ID and password by the user A, the login information (authentication information) is transmitted to the profile management unit 140 (step S11).

Next, when authentication is performed, the profile operation UI240 transmits the already acquired user profile, if any, to the profile management unit 140 (step S12). After that, when the profile operation UI240 is operated by the user A and the user profile is updated (registered / deleted), the profile operation UI240 sets the user profile including the updated media type, media ID, and description information in the profile management unit. Send to 140 (step S13).

Then, the profile management unit 140 makes an event notification request to the SIP server 300 (step S14). This event notification request, if the SIP URI is registered, instructs the SIP server 300 or the IM server 400 to subscribe the information and send the event. If the SIP URI is changed, the old SIP URI is deleted (unsubscribed) and then the new SIP URI is requested to be transmitted. If the SIP URI is deleted, the corresponding SIP URI is deleted.

After that, the profile management unit 140 updates the user profile table 151 (step S15). This completes the processing sequence of the user profile registration phase.

&lt;Presence collection / notification phase&gt; In the presence collection / notification phase, the current status (online, offline, busy, installed, etc.) of the communication media 60 and application 210 used by user A and the communication media 60 and communication media 60 used by user B and This is a phase in which the server 100 acquires the current state of the application 210a as presence information, and then the server 100 notifies the clients 200 and 201 communicating with each other of the acquired presence information of the communication partner. The method of collecting this presence information differs depending on the communication tool.

The presence information of the communication media 60 and 65 is notified to the application control unit 110 when the SIP server 300 and the IM server 400 raise a call event (event). When the event is notified, the application control unit 110 checks the format of the event, and if conversion is necessary, converts it into a format for writing to the presence DB 130. For example, when an XML format file is stored in Presence DB130, schema conversion is performed. In addition, the application control unit 110 refers to the user profile table 151 via the profile management unit 140, associates with the client 200 by searching for the user ID from the SIP URI of VoIP or IM, and has a presence on a user-by-user basis. Be ready to get. After that, the application control unit 110 transmits the presence information to the presence management unit 120. The presence management unit 120 stores the received presence information in the presence DB 130.

On the other hand, the presence information of the application 210 can be obtained by the local application information management unit 230 referring to the registry of the client 200, searching a specific folder, or registering the application to be used for collaboration by the user. Obtain from the database in which the setting data of the system and application software is recorded. Obtain the application 210a in the same way.

Presence information is stored in the presence DB 130 as a table, for example. FIG. 9 is a diagram showing a presence table.

The presence table 131 is provided with columns for media ID, media type, current status, status options, contacts, and time stamps. The items arranged horizontally in each column are related to each other to form one presence information. For example, media ID foo @ pc1, media type collabo, current state open, state option none, contact collabo: 10.20.30.40: 1010, timestamp 2005-06-08T01: 01: "47Z" constitutes one presence information.

In the media ID column, an ID that identifies an application (Notepad, Acrobat (registered trademark), etc.) installed on the communication media 60 or the client 200 is set. Regarding the ID of the communication media and the ID of the client 200, the same media ID set in the media ID field of the user profile table 151 is set. In the application media ID field, the ID of the client 200, that is, the media with the application identification information (; Notepad ,; Acrobat®; NetMeeting®) added after foo @ pc1. ID is set.

In the media type column, the type of communication media or application is set. Here, collabo means the media type of the client, that is, the client 200, and application / * (* is an extension) means an application.

In the current status column, the current status of the communication media or application is set. The current state of the communication media is set to open (online) if the application is available, closed (offline) if the application is unavailable, and others. If a session is being established with the application, "connected" is set. The current state of the application is set to installed.

In the status option column, the media ID of the other party whose session is being established is set when the current status of the communication media is "connected". In the contact column, the IP address of the client 200 and the port number of the user interface that serves as the contact point are set when the media type is "collabo" or "application". This IP address and port number are set when the client 200 logs in to the server 100.

The date and time when the presence was updated is set in the time stamp. According to this presence collection / notification phase, when the application control UI 220 instructs the local application information management unit 230 to register the application status information at the time of starting the client 200 or a request from the user, the local application The information management unit 230 collects the current state of the application 210 in the client 200 and sends it to the presence management unit 120. When the presence management unit 120 receives the current state of the application, it stores it in the presence DB 130. This updates the contents of Presence DB130.

Then, when updating the presence, since it is known in advance that the current state is connected, after the presence management unit 120 updates the presence DB 130, the client 200 is selected from the SIP URI set in the state option column. , 201 (both communicating clients) is searched, the presence information of both communicating with the application control UI 220 of the client 200 is transmitted, and the presence information of both clients is transmitted to the application control UI 220a of the client 201. Send the presence information of both communicating parties. The application control UI 220 that has received the presence information displays the information on the monitor 11.

Next, the processing sequence of the presence collection / notification phase of the communication media 60 will be described by taking the IP phone registration phase as an example. FIG. 10 is a diagram showing a processing sequence of the presence collection / notification phase of the communication media.

First, the user A makes a call request to the IP phone 67 using the IP phone 62, so that the user agent of the IP phone 62 (hereinafter referred to as UA1) and the user agent of the IP phone 67 (hereinafter referred to as UA2) are contacted. Call processing (one-call SIP signaling) is performed to establish a VoIP session for exchanging voice between them (steps S21 to S26). Specifically, the UA1 sends a connection request (INVITE) to the SIP server 300 to the SIP server 300 (step S21).

Next, the SIP server 300 confirms the IP address of the IP phone 67 and sends a connection request to the IP phone 67 (step S22). For example, when the connection of the IP phone 67 is confirmed by the off-hook of the handset, the UA2 returns a successful response (200 OK) to the SIP server 300 in response to the connection request (step S23).

Then, the SIP server 300 returns a success response to UA1 (step S24). Next, the UA1 sends an ACK response (session establishment understanding) to the SIP server 300 based on the success response from the SIP server 300 (UA2) (step S25).

The SIP server 300 then sends an ACK response to UA2 (step S26). As a result, a session is established between the IP phone 62 and the IP phone 67. Voice data is exchanged on the established session, and a call is entered.

Next, the SIP server 300 notifies the application control unit 110 of the call event (step S27). Then, when the application control unit 110 receives the call event, the schema conversion for writing to the presence table 131 is performed as necessary, and the presence management unit 120 is updated with the presence (step S28). As a result, the presence column of the IP phone 62 and the IP phone 67 in the presence table 131 is set from open to connected.

Next, the presence management unit 120 checks the current status column of the presence table 131 with the user ID of foo and the media type column of collabo (step S29).

Then, the presence information of the user A and the user B is notified to the client 200 (step S30). Next, the presence management unit 120 checks the current status column of the presence table 131 with the user ID of goo and the media type column of collabo (step S31).

Then, the presence information of the user A and the user B is notified to the client 201 (step S32). As a result, the balloon 15 shown in FIG. 6 is displayed.

When the call ends, the SIP server 300 notifies the application control unit 110 of the call event again, so that the current status column is updated from "connected" to "open".

When IM is used as the communication medium, the presence is performed by relaying the IM server 400, performing normal IM message transmission processing instead of steps S21 to S26, and notifying a message transmission event instead of S27. Is changed to connected. Unlike VoIP, IM cannot explicitly end a conversation, so if a certain amount of time has passed after sending a message, it will be considered that the conversation has ended and the presence will change from "connected" to "open". Update.

Next, the processing sequence of presence collection / notification of application 210 will be described. FIG. 11 is a diagram showing a processing sequence of application presence collection / notification.

First, when the client 200 is started, the application control UI 220 reads the setting files such as the address, ID, and password of the server 100 (step S41). Next, the application control UI 220 creates an operation screen 11a for displaying presence information on the monitor 11 (step S42). This screen is usually displayed as an icon in the task tray.

Next, the application control UI 220 creates an instance of the local application information management unit 230 (step S43). Next, the application control UI 220 instructs the local application information management unit 230 to register the application information (step S44).

Next, the local application information management unit 230 examines the application 210 installed in the client 200, and sends a presence update request together with the authentication information to the presence management unit 120 (step S45).

Next, the presence management unit 120 authenticates based on the authentication information (step S46), and when the authentication is performed, searches for a client whose current state is open based on the user ID (step S47).

Then, when the presence management unit 120 finds a client whose current state is open, it notifies the application control UI 220 of the presence (step S48). As a result, the status of the communication media and the application is displayed on the operation screen 11a.

In addition, the presence management unit 120 examines the session status, identifies the communication partner when the session is established, and continuously searches for the client whose current status of the communication partner is open (step S49). ).

Then, the presence management unit 120 notifies the application control UI 220a of the presence (step S50). This completes the application presence collection / notification operation.

&lt;Additional collaboration phase&gt; The addition phase of collaboration is a phase that is executed when user A selects a desired communication tool from the communication tools displayed on the communication tool usage environment screen 16. The procedure differs depending on the type of communication tool.

For example, when the communication tool is an IP phone, the application control UI220 controls the application including authentication information, user A (calling side) user ID foo, and user B (arriving side) user ID goo. Performs the call processing to be passed to the unit 110 and calls the API (Application Program Interface) of the SIP server 300. As a result, a SIP session is established between the IP phone 62 and the IP phone 67.

In addition, for example, when the communication tool is IM, the application control UI 220 performs IM transmission processing for passing information including authentication information, originator user ID, and arrival side user ID to the application control unit 110, and uses the API of the IM server 400. call. As a result, the monitor connected to the client 201 displays a screen for sending a message addressed to user B.

Further, for example, when the communication tool is a file transmission, the application control UI 220 instructs the application control unit 110 to transmit information including authentication information, a destination URI, a file name, and contents. The application control unit 110 transmits the file specified by the client 201 indicated by the destination URI, and the application control UI 220a displays the received file on the monitor connected to the client 201.

Further, for example, when the communication tool is an application sharing tool such as a network conference tool or a communication tool, the application control UI 220 implements application sharing using the API of the shared application in the client 200. Since the API may differ for each application, the driver may be pluggable so that it can be extended or changed.

Next, the case of adding the IP phone 62 for the processing sequence of the addition phase of the communication tool will be described as an example. FIG. 12 is a diagram showing a processing sequence of the collaboration addition phase of the IP phone.

First, when the user A selects the IP phone 62 from the communication tool displayed on the communication tool usage environment screen 16, the application control UI 220 performs a call processing to the application control unit 110 (step S51).

Next, the application control unit 110 executes a third-party call and calls the API of the third-party call server in the SIP server 300 (step S52). Next, SIP signaling is performed (steps S53 to S58). Specifically, the SIP server 300 first sends a connection request (INVITE) to UA1 (step S53), and then sends a connection request (INVITE) to UA2 (step S54).

When the UA1 receives the connection request, it returns a success response (200 OK) to the SIP server 300 in response to the connection request (step S55). When the UA2 receives a connection request, it returns a success response (200 OK) to the SIP server 300 (step S56).

The SIP server 300 then sends an ACK response to UA1 and UA2 based on the success response from UA1 and UA2 (steps S57, S58). Next, the SIP server 300 notifies the application control unit 110 of the call event (step S59).

Next, the application control unit 110 updates the presence and notifies (steps S60 to S64). Since this operation is the same as steps S28 to S32 in FIG. 10, the description thereof will be omitted.

Next, a case where a file is transmitted for the processing sequence (processing operation) of the additional phase of the communication tool will be described as an example. FIG. 13 is a diagram showing a processing sequence of the collaboration addition phase when the file is transmitted.

First, when user A selects file transmission from the communication tool displayed on the communication tool usage environment screen 16, the application control UI 220 transmits a file to the application control unit 110 (step S71).

Next, the application control unit 110 authenticates (step S72), and when authenticated, sends a file to the application control UI 220a of the client 201 (step S73). Next, the application control UI 220a sends an application start command to the application 210a (step S74). This launches the application 210a corresponding to the sent file.

On the other hand, in step S71, if the user A adds an option for sharing the file, the application control UI 220 starts the application 210 corresponding to the transmitted file (step S75).

As described above, according to the communication system 500, the client's local application information management unit 230, the SIP server 300, and the IM server 400 collect presence information about the communication tool used by the user in the presence management unit 120. Then, when a session using either communication tool is established between user A and user B, the application control UI 220 of the client 200 used by the communicating user A and the application control UI 220a of the client 200a used by the user B are used. The presence information of both parties is transmitted to. Presence information includes information necessary for collaborating with the other party, such as an IP address and a user ID. Therefore, by operating the application control UI 220, the user A can easily and surely collaborate without confirming the IP address, user ID, etc. with the other party or directly manually inputting the IP address and the user ID. As a result, collaboration can be performed smoothly and efficiently.

In the present embodiment, the e-mail is registered by the user A in the user profile table 151, but the e-mail is not limited to this, and a program such as Apache James (Java (registered trademark) Apache Mail Enterprise Server) is used. Presence information may be acquired by a mechanism similar to VoIP or IM using a possible mail server, or a plug-in for registering presence information may be incorporated in the mail application.

Further, in the present embodiment, the SIP server 300 and the IM server 400 have a function of notifying an event or presence related to VoIP or IM to the outside, but the communication media 60 and 65 (SIP terminal side) are not limited to this. May have a function of notifying event or presence information, in which case the SIP server 300 and IM server 400 need not have a function of notifying an event or presence to the outside.

Next, a second embodiment of the communication system will be described. FIG. 14 is a block diagram showing the system of the second embodiment. Hereinafter, the communication system 500a of the second embodiment will be described mainly on the differences from the first embodiment described above, and the same matters will be omitted.

In the collaboration addition phase of the first embodiment, the communication tool was selected by the user, but in the collaboration addition phase of the second embodiment, the information on the position of the communication tool and the media type are further detailed. The difference is that the communication tool to be used is selected based on the preference information regarding the information of the terminal type to be classified.

The communication system 500a of the second embodiment includes a server 100a further having a preference management unit 170 for receiving the preference management request and a preference DB 180 for storing the management data, and a client for executing the preference management request. It includes a client 200a further having a reference operation UI260 and a client 201a further having a preference operation UI260a for executing a preference management request.

FIG. 15 is a diagram showing a user profile table according to the second embodiment. Compared to the user profile table 151, the user profile table 151a has additional terminal type and position columns (attributes).

This information is set by user A using the profile operation UI240, for example. The type of communication tool is set in the terminal type column. For example, "mobile" is set for the mobile phone 61, "fixed" is set for the fixed IP phone 62, and "soft" is set for the softphone 63.

In the position column, location information is set for communication tools other than those whose media types are "collabo" and "mobile". Specifically, for a communication tool whose terminal type is "soft" or "fixed", the media ID of the client 200 having the closest positional relationship is set. Therefore, in the softphone 63, the media ID foo @ pc1 of the client 200 in which the software is installed is set. In the fixed IP phone 62, the media ID foo @ pc1 of the client 200 is set. In the case of mobile phone 61 mail, the mobile media ID "sip: foo@mobile. ***. Com" is set.

If user A can use a client other than client 200, the media ID of that client (foo @ pc2 in FIG. 15) can also be set. Further, the user A uses the preference operation UI260 to access the preference management unit 170 of the server 100a, and registers the priority of the communication tool in the preference DB 180 in advance. This information is stored, for example, in a table.

FIG. 16 is a diagram showing a preference table. The preference table 181 is provided with columns for user ID and preference. The items arranged horizontally in each column are related to each other.

In FIG. 16, mobile, fixed, and soft are set in the preference column of the user ID foo in descending order of priority. Then, for example, when the media type voip is selected in the additional phase of collaboration, the application control unit 110 sets the profile table 151a, the presence table 131, and the preference table 181 in the call processing (S51) of FIG. Browse and search for VoIP terminals that are in the same location as the client. Then, among the found VoIP terminals, the terminal with the status "open" and the highest priority is selected to make a call.

Next, the case where the IP telephone 62 is used for the collaboration addition phase of the second embodiment will be described in detail. In the collaboration addition phase of the second embodiment, the same processing as that of the first embodiment is performed for steps S52 to S64 shown in FIG. 12, and the following operations are executed immediately after step S51, which is appropriate. The call destination is decided.

FIG. 17 is a flowchart illustrating a processing sequence of the collaboration addition phase of the second embodiment. First, the application control unit 110 acquires the IM session information whose current state is connected (step S81).

Next, the application control unit 110 acquires the media ID from the IM session information (step S82). Next, the application control unit 110 instructs the profile management unit 140 to extract the user profile table 151a, and the application control unit 110 determines whether or not the position information of the extracted media has been acquired (step S83). ..

When the position information of the media cannot be acquired (No in step S83), for example, a predetermined error process such as notifying the monitor 11 that an error has occurred is executed to end the operation (step S84). On the other hand, if the location information of the media can be acquired (Yes in step S83), it is determined whether or not the communication tool of the media type voip whose location information matches has been acquired (step S85). If it cannot be obtained (No in step S85), the process proceeds to step S84, the predetermined error processing is executed, and the operation ends. On the other hand, if it is acquired (Yes in step S85), a list of communication tools whose current state is open is obtained from the list (Step S86). If there is no communication tool whose current state is open (No in step S86), the process proceeds to step S84, the predetermined error processing is executed, and the operation ends. On the other hand, if there is a communication tool whose current state is open (Yes in step S86), the communication tool for making a call is determined by referring to the preference information (step S87).

This completes the processing sequence of the collaboration addition phase of the second embodiment. According to the communication system 500a of the second embodiment, the same effect as that of the communication system 500 of the first embodiment can be obtained.

Then, according to the communication system 500a of the second embodiment, the user A sets the priority of the communication tool in the preference table 181 in advance, so that the user A collaborates using the desired terminal. be able to. Specifically, for example, when a collaboration request is made in a call from user B to user A, user A makes a desired terminal among a mobile phone 61, a fixed IP phone 62, and a softphone 63 receive an incoming call. Can be done.

Next, a third embodiment of the communication system will be described. In the third embodiment, application sharing is performed if application sharing is possible, and file transmission is performed as an example of an alternative method of application sharing if application sharing is possible, depending on the usage environment of both the client 200 and the client 201 that collaborate. Do. Also, when sending a file, if the client 201 cannot display the file sent from the client 200, convert the file format to a format that can be displayed by the client 201 and send it, etc. It is a collaboration.

FIG. 18 is a block diagram showing the system of the third embodiment. Hereinafter, the communication system 500b of the third embodiment will be described mainly on the differences from the first embodiment described above, and the same matters will be omitted.

The communication system 500b includes a file format conversion unit 190, a profile DB 150a having an application data profile table that tabulates file format conversion rules, and a server 100b further having a file providing unit 191.

The file format conversion unit 190 converts the format of the file input according to the instruction of the application control unit 110, and transmits the file format to the application control UI 220. FIG. 19 is a diagram showing an application data profile table.

The application data profile table 152 is provided with columns for application type and conversion method. In addition, the conversion method is divided into target type and program items. The items arranged horizontally in each column are related to each other.

The file extension is set in the application type column. In the target type column, the extension of the file that converts the extension of the application type is set.

In the program column, the storage destination of the program for converting to the extension of the target type is set. This will be explained by returning to FIG. 18 again.

The file providing unit 191 has a function of converting a file into HTML (Hyper Text Markup Language) and holding the file when the application control unit 110 provides the file. In addition, the file providing unit 191 has a Web server function, reads the provided file using a browser, and sends the URL for accessing the file to the client 201.

Next, the processing sequence of the collaboration addition phase of the third embodiment will be described. In the following, a case where application sharing is performed when collaboration is established will be described.

20 and 21 are flowcharts illustrating a processing sequence of the collaboration addition phase of the third embodiment. When the application sharing is selected from the client 200 by the user A, the application control unit 110 first acquires the VoIP session information whose current state is connected (step S91).

Next, the application control unit 110 acquires the media ID from the VoIP session information (step S92). Next, the application control unit 110 instructs the profile management unit 140 to extract the user profile table 151a, and the application control unit 110 determines whether or not the position information of the extracted media has been acquired (step S93). .. If the position information of the media information cannot be acquired (No in step S93), error processing is executed and the determination operation is terminated (step S94). On the other hand, when the location information of the media information can be acquired (Yes in step S93), the media ID of the application 210 whose location information matches is acquired (step S95).

If the media ID of the application cannot be obtained (No in step S95), the process proceeds to step S94, error processing is executed, and the judgment operation ends. On the other hand, if the media ID of the application can be obtained (Yes in step S95), the application control unit 110 refers to the presence DB 130 to see if the application of the data to be shared is available, that is, the current state is installed. Check whether or not (step S96 in FIG. 16). If the application for the data you want to share is available (Yes in step S96), check if a sharing application for sharing the application for the data you want to share (for example, an application with messenger function) is available (step). S97). If the sharing application is available (Yes in step S97), the sharing process is executed using the sharing application (step S98), and the determination operation is terminated. If the shared application is not available (No in step S97), the process proceeds to step S99.

On the other hand, when the application of the data to be shared is not available (No in step S96), the application control unit 110 refers to the application data profile table 152 (step S99).

Next, the application control unit 110 confirms whether or not the data to be shared can be converted into a data format that can be displayed in the environment of the other client (step S100). If conversion is possible (Yes in step S100), the application control unit 110 transmits data to the file format conversion unit 190, and the file format conversion unit 190 executes the file format conversion and transmission process (step S101). The judgment operation is terminated. If the conversion is not possible (No in step S100), the application control unit 110 sends the data to the file providing unit 191 and the file providing unit 191 performs HTML conversion and sends the URL to the client 201 (step S102). ).

As a result, the application control UI220a that received the URL starts the browser and displays the document of the received URL. This completes the collaboration addition phase of the third embodiment.

According to the communication system 500b of the third embodiment, the same effect as that of the communication system 500 of the first embodiment can be obtained. Application sharing cannot be performed unless an application having an application sharing function is installed on the user's personal computer, but according to the communication system 500b of the third embodiment, the target information can be shared by transmitting a file. Can be achieved.

Next, a fourth embodiment of the communication system will be described. In the first embodiment to the third embodiment, the communication media 60 and the application 210 were targeted as the collaboration tool, but in the fourth embodiment, the collaboration tool is connected to the network 10. The difference is that they also use other devices and services.

Hereinafter, the communication system of the fourth embodiment will be described mainly on the differences from the first embodiment described above, and the same matters will be omitted. In the communication system of the fourth embodiment, the local application information management unit 230 has a function of UPnP (Universal Plug and Play).

The local application information management unit 230 discovers a communication tool in the same segment by the UPnP protocol, and stores (registers) the obtained information in the presence DB 130 as presence information. At the time of storage, the current information and time stamp fields of the presence table 131 are set in the same manner as in the first embodiment. Then, set the URL of the UPnP action in the media ID field, set "upnp / (service device type)" in the media type field, and set the parameters required for the action in the status option field. , Set the URL of the UPnP action in the contact field as well as the media ID.

Then, as in the first embodiment, when the session is established, the presence information is notified, and the UPnP service is selected as the communication tool, the URL of the UPnP action is called and the service is executed.

According to the communication system of the fourth embodiment, the same effect as that of the communication system 500 of the first embodiment can be obtained. Then, according to the communication system of the fourth embodiment, as described in the third embodiment, for example, instead of sending a file as an alternative means when application sharing is not possible, a UPnP compatible printer is found. If so, the file can be printed and information can be shared, and collaboration that maximizes each other's computer environment can be realized.

In the present embodiment, UPnP is used as the function of the control point, but the present invention is not limited to this. Next, a fifth embodiment of the communication system will be described.

Hereinafter, the communication system 500c of the fifth embodiment will be described mainly on the differences from the first to fourth embodiments described above, and the same matters will be omitted. In the first to fourth embodiments, when the session is established, the server 100 notifies the client 200 of the presence information of the user B, and the client 201 notifies the client 201 of the presence information of the user A. In the form of, when the client requests the presence information, the server 100 notifies the client 200 of the presence information of the user B, and notifies the client 201 of the presence information of the user A.

FIG. 22 is a block diagram showing the system of the fifth embodiment. The clients 200b and 201b of the fifth embodiment further include user list management DBs 270 and 270a in which users to collaborate are registered.

For example, the user A registers the user list in the user list management DB270 in advance. The user list may be managed by the server 100, or the user ID may be directly entered manually.

The application control UI 220 displays the user list management DB 270 on the operation screen 11a as a pre-process for starting collaboration. When user A specifies a user to collaborate with, the application control UI 220 requests presence information from the presence management unit 120. Alternatively, the presence information may be read in advance like a buddy list (user list). Then, when the application control UI 220 acquires the presence information, the communication tools available to the user A and the user B are displayed on the operation screen 11a.

FIG. 23 is a diagram showing a communication tool usage environment screen displayed on the display screen. The communication tool usage environment screen 17 displayed on the operation screen 11a has a communication tool group 18 of the user A and a communication tool group 19 of the user B.

User A can collaborate by designating the communication tool he / she uses (fixed IP phone in Fig. 23) and the communication tool of user B (mobile phone in Fig. 23) who wants to collaborate, for example, using a mouse 13 or the like. It will be started.

According to the communication system 500c of the fifth embodiment, the same effect as that of the communication 500 of the first embodiment can be obtained. Then, according to the communication system 500c of the fifth embodiment, collaboration can be further easily achieved.

Although the preferred embodiments of the present invention have been described in detail above, the present invention is not limited to the specific embodiments. In each of the above-described embodiments, an example of communication between user A and user B (between clients 200 and 201) has been described, but the present invention is not limited to this, and the present invention is not limited to this, and a plurality of users (three or more clients) are described. It is also possible to collaborate between).

Further, the processing functions of the server 100, the clients 200, and 201 can be realized by a computer (by causing the computer to execute a predetermined communication program). In that case, a program that describes the processing contents of the functions that the server 100, the clients 200, and 201 should have is provided. By executing the program on a computer, the above processing function is realized on the computer. The program describing the processing content can be recorded on a computer-readable recording medium. Examples of computer-readable recording media include magnetic recording devices, optical disks, optical magnetic recording media, semiconductor memories, and the like. Examples of the magnetic recording device include a hard disk device (HDD), a flexible disk (FD), a magnetic tape, and the like. Examples of optical discs include DVD (Digital Versatile Disc), DVD-RAM (Random Access Memory), and CD-ROM (Compact Disc Read Only). Memory), CD-R (Recordable) / RW (ReWritable), etc. Examples of the magneto-optical recording medium include MO (Magneto-Optical disk) and the like.

When a program is distributed, for example, a portable recording medium such as a DVD or a CD-ROM on which the program is recorded is sold. It is also possible to store the program in the storage device of the server computer and transfer the program from the server computer to another computer via the network.

A computer that executes a communication program stores, for example, a program recorded on a portable recording medium or a program transferred from a server computer in its own storage device. Then, the computer reads the program from its own storage device and executes the processing according to the program. The computer can also read the program directly from the portable recording medium and execute the process according to the program. In addition, the computer can sequentially execute processing according to the received program each time the program is transferred from the server computer.

(Appendix 1) In a communication program in which client terminals collaborate using a plurality of types of communication means including device type information and user identification information, a computer is used for each user and the device type information for each communication means. A profile management means that manages unique information in which a user ID is associated with a pair of user identification information, and when a session using any of the communication means is established between users, the unique information managed by the profile management means. The application control means that associates the user ID with the pair of the device type information and the user identification information of the communication means established by the session, the device type information for each communication means, and the said. A collecting means for collecting presence information in which the user identification information is associated with state information indicating whether or not the communication means can be used. When the user ID is specified by the application control means, the presence information is referred to, and the communication partner in the communication means that can be used by the communication partner with respect to the client terminal of the user for whom the session has been established. A communication program characterized by functioning as a presence management means for notifying presence information.

(Appendix 2) When the client terminal during the establishment of the session requests the use of the communication means that can be used by the communication partner of the user, the application control means of the communication partner responds to the usage request. The communication program according to Appendix 1, wherein the client terminal is made to execute a process corresponding to the usage request.

(Appendix 3) The unique information further includes position information indicating a positional relationship with the client terminal for each communication means, and prioritizes information of the communication means having the computer and the device type information in common. When there is a plurality of device type information having the common position information related to the user ID of the user for whom the session has been established, the application control means has the priority order. The communication program according to Appendix 2, wherein the process corresponding to the client terminal of the communication partner is executed according to the above.

(Appendix 4) When the client terminal of the user who is establishing the session requests data communication using the communication means, the application control means is a user of the client terminal of the communication partner during which the session is being established. It is determined whether or not the communication means can be used, and when the client terminal of the communication partner cannot execute the communication means, the data is transmitted to the client terminal of the communication partner by using an alternative means. The communication program described in Appendix 1 characterized by.

(Appendix 5) The alternative means has a file format conversion means for converting a file format, and when the client terminal of the communication partner cannot execute the communication means, the file format conversion means determines the data. The communication program according to Appendix 4, wherein the data is converted into the file format of the above and transmitted to the client terminal of the communication partner.

(Appendix 6) The alternative means has an HTML conversion means for converting and holding a file format into an HTML format, and when the client terminal of the communication partner cannot execute the communication means, the HTML conversion means can be used. The communication program according to Appendix 4, wherein the data is converted into an HTML format and held, and the URL in the HTML format is transmitted to the client terminal of the communication partner.

(Appendix 7) The communication program according to Appendix 1, wherein the collecting means collects the presence information of the communication means in the same segment of the client terminal.

(Appendix 8) The communication program according to Appendix 1, wherein the communication means is provided with an IP address. (Appendix 9) The communication program according to Appendix 1, wherein the collecting means acquires the presence information from the session start protocol server when the communication means uses the session start protocol.

(Appendix 10) The communication program according to Appendix 1, wherein the presence management means notifies the user's own presence information when notifying the communication partner of the presence information.

(Appendix 11) In a communication method in which client terminals collaborate using a plurality of types of communication means including device type information and user identification information, the device type information and the user for each communication means are used for each user. Unique information in which a user ID is associated with a pair of identification information is managed, and when a session using any of the communication means is established between users, the unique information is referred to and the communication means established by the session. The pair of the device type information and the user identification information is associated with the user ID, and the device type information and the user identification information for each communication means indicate whether or not the communication means can be used. When the presence information associated with the state information is collected and the user ID is specified, the presence information is referred to, and the communication means that can be used by the communication partner with respect to the client terminal of the user for whom the session has been established. A communication method comprising notifying the communication partner and the presence information of oneself in the above.

(Appendix 12) In a communication device that collaborates between client terminals using a plurality of types of communication means having device type information and user identification information, for each user, the device type information for each communication means and the user. When a profile management means that manages unique information in which a user ID is associated with an identification information and a session using any of the communication means are established between users, the unique information managed by the profile management means is referred to. Then, the application control means that associates the user ID with the pair of the device type information and the user identification information of the communication means established by the session, the device type information for each communication means, and the user. A collection means that collects presence information in which the identification information is associated with state information indicating whether or not the communication means can be used. When the user ID is specified by the application control means, the presence information is referred to, and the communication partner in the communication means that can be used by the communication partner with respect to the client terminal of the user for whom the session has been established. A communication device characterized by having a presence management means for notifying presence information.

<figref num="1">It is a principle explanatory drawing of this invention.</figref><figref num="2">It is a figure which shows the system configuration example of 1st Embodiment.</figref><figref num="3">It is a figure which shows the hardware configuration of the server used in this embodiment.</figref><figref num="4">It is a block diagram which shows the function of a server and a client.</figref><figref num="5">It is a figure explaining the outline of operation of a communication system.</figref><figref num="6">It is a figure which shows the operation screen of the application control UI of 1st Embodiment.</figref><figref num="7">It is a figure which shows the user profile table.</figref><figref num="8">It is a figure which shows the processing sequence of the registration phase of a user profile.</figref><figref num="9">It is a figure which shows the presence table.</figref><figref num="10">It is a figure which shows the processing sequence of the presence collection / notification phase of a communication medium (an example of VoIP).</figref><figref num="11">It is a figure which shows the processing sequence of presence collection / notification of an application.</figref><figref num="12">It is a figure which shows the processing sequence of the collaboration addition phase of an IP phone.</figref><figref num="13">It is a figure which shows the processing sequence of the collaboration addition phase at the time of file transmission.</figref><figref num="14">It is a block diagram which shows the system of the 2nd Embodiment.</figref><figref num="15">It is a figure which shows the user profile table of the 2nd Embodiment.</figref><figref num="16">It is a figure which shows the preference table.</figref><figref num="17">It is a flowchart explaining the processing sequence of the collaboration addition phase of the 2nd Embodiment.</figref><figref num="18">It is a block diagram which shows the system of the 3rd Embodiment.</figref><figref num="19">It is a figure which shows the application data profile table.</figref><figref num="20">It is a flowchart explaining the processing sequence of the collaboration addition phase of 3rd Embodiment.</figref><figref num="21">It is a flowchart explaining the processing sequence of the collaboration addition phase of 3rd Embodiment.</figref><figref num="22">It is a block diagram which shows the system of 5th Embodiment.</figref><figref num="23">It is a figure which shows the operation screen of the application control UI of the 5th Embodiment.</figref>

Code description

1, 1a Client terminal 2 Server 3 Profile management means 3a Unique information 4 App control means 5 Collecting means 5a Presence information 6 Presence management means 7, 7a Information management means 8, 8a App control UI 21, 22, 23, 23a Communication means 60 , 65 Communication media 100 Server 110 Application control 120 Presence management 130 Presence DB 140 Profile management 150, 150a Profile DB 160, 250 Interface 170 Preferences 180 Preferences DB 190 File format conversion 191 File provider 200 , 201 Client 210 Application 220 App Control UI 230 Local App Information Management Unit 240 Profile Operation UI 260 Preferences Operation UI 300 SIP Server 400 IM Server 40, 500, 500a, 500b, 500c Communication System