JP3594229B2 - Document file sharing system, collaboration server, document file transfer method, and storage medium - Google Patents

Description

[0001]
TECHNICAL FIELD OF THE INVENTION
The present invention relates to a system or the like in which a plurality of clients are connected via a communication network, and more particularly to a collaboration system or the like that executes a collaboration by sharing a local file in one of the clients.
[0002]
[Prior art]
In recent years, a computer system that supports information exchange (collaboration) among multiple users has been developed with the aim of building a new system for transmitting and sharing information such as qualitative knowledge and know-how that could not be handled as a system until now. The introduction is progressing rapidly. If a system that supports this collaboration is realized by constructing an intranet, for example, images and graphs are added to the core data (product information, customer data, sales performance, etc.) conventionally stored as text, which makes it more useful. It can be shared as information. In addition, by expanding to an extranet, for example, joint product development, research and development, and project management with related companies can be performed more smoothly, and processes can be streamlined by sharing information with vendors and suppliers. It becomes possible. In addition, if the circle of information exchange is extended to the Internet, for example, in response to an inquiry from a distant customer, a sales representative can output the product information that the customer inquired on the customer's browser and add an explanation as appropriate. In addition, it is possible to receive orders on the spot, and is expected to contribute to the promotion of mobile offices and telecommuting.
[0003]
Here, as an application for executing these collaborations, a web collaboration (WebCollaboration), which is a product of the applicant (IBM Corporation), mainly for sharing HTML on a web server (WebServer), or a local image file. There is IBM's WebCollaboration SnapShot Sharing, whose primary use is sharing. Also, Microsoft's NetMeeting, whose main use is to share applications on various PCs, and the Lotus Freelance Team Screen Show, whose main use is to synchronize and view screen shows on multiple PCs ( Freedom Team Screen Show) and the like. For example, when using Web Collaboration, which is an application of IBM Corporation, at a customer consultation center or the like, the contents (contents of information) posted on the IBM Corporation homepage and the like are shared with a Customer (Customer), thereby allowing the customer (Customer) to share with the customer. It is possible to deepen mutual understanding with an agent (Agent) supported by a call center or the like, and it is possible to achieve smooth communication. As a patent publication, Japanese Patent Application Laid-Open No. 9-258948 discloses a system that detects a change in the display of an application program and reflects the operation on each other.
[0004]
[Problems to be solved by the invention]
However, according to, for example, the HTML sharing function in Corepoint (IBM trademark) WebCollaboration, it is possible to share the HTML of the world between browsers, but to share the contents of a document file that has not been posted on a web server. Can not. In addition, although the PDF (Portable Document Format) file on the web server is displayed, since the browser is displayed using the plug-in (Plug-in), enlargement and scrolling of the PDF file itself are synchronized. Can not do it.
For example, there is no problem if an agent wants to collaborate with a customer using materials, but only collaborates with materials posted on the Internet homepage. Often become. In such cases, it is impractical to post the material on the web server in advance, and on the other hand, agents generally do not have the authority to rewrite the content of the web server, resulting in immediate collaboration Cannot be performed.
[0005]
Further, existing applications do not assume that the contents of a local document file are shared. For example, even if you have a function to send a bitmap from one sharing terminal to a web server, all of these will make the document file a bitmap and send it to the web server, so the data volume will be enormous. Excessive load on the network is inevitable. Further, when converting a document file or the like over a plurality of pages into a bitmap, much trouble is required. In the freelance team screen show, it is assumed that document files will be shared.However, this is a tool for synchronizing and displaying multiple freelance documents on the intranet. Sharing is not possible.
Further, Japanese Patent Application Laid-Open No. 9-258948 mentions only sharing of window display changes, and cannot solve the above problem at all.
[0006]
The present invention has been made to solve such a problem, and an object of the present invention is to efficiently share a document file stored in one PC between users who collaborate.
Another object is to enable efficient collaboration by a caching function in both a collaboration server and a client.
Yet another object is to allow the shared file to be stored in the same document format as the original.
[0007]
[Means for Solving the Problems]
For this purpose, a feature of the present invention is that the content of a document file such as PDF can be transmitted and shared from one terminal without passing through a web server.
That is, the present invention provides a collaboration between clients connected via a communication network. Document file sharing system for sharing document files used in Windows Establishes a session between the first client and the second client executing the collaboration And maintain information on established sessions From a session establishing means to be established and a first client having a session established by the session establishing means. Upon receiving the content of the document file used by the first client, the session establishment means recognizes that the transfer destination of the content of the document file is the second client, and recognizes the content of the document file. File transfer means for transferring to the second client.
[0008]
Further, the system further comprises file transfer request means for requesting file transfer from the second client to the first client, wherein the file transfer means transfers the document file based on a request from the file transfer request means. This is preferable in that a smooth collaboration can be performed based on a local document file, which is greatly different from the related art in which a URL indicating only a place is transferred.
Further, if the apparatus further comprises file information transmitting means for transmitting the file information of the document file held by the first client to the second client, it becomes possible to transfer only the contents of the necessary document file, Is excellent in that time can be saved. It is preferable that the file information of the document file include the file name, size, date, and the like, in order to determine the file identity.
Further, in addition to these configurations, if a configuration is provided in which a collaboration means for synchronizing open document files between clients having a session is established, a page can be moved and scrolled by a viewer on any client. Sending the event to the other, such as when an enlargement / reduction button is pressed, is preferable in that the viewing areas can be synchronized.
[0009]
As a form of the collaboration system according to the present invention, the first client and the second client connected to a communication network such as the Internet may each be provided with a session establishing means to perform file transfer. is there. It is also possible to provide a mediation collaboration server in addition to the first client and the second client, and to perform a file cache and transfer in addition to the session establishment.
Further, it goes without saying that the type and format of the document file are not particularly selected, and the document file is not limited to the "document" in a narrow sense. If the document file format is PDF (Portable Document Format), which is a file format for displaying documents developed by Adobe Systems in the United States, this PDF is general-purpose and the file is compressed. This is preferable as the document file format of the present system because it becomes lighter.
Further, here, the term "collaboration" means that an action generated in one client is transmitted to the other client, and the other client obtains the same result by generating the action.
[0010]
On the other hand, when the present invention is grasped from the mediating collaboration server, the collaboration server of the present invention establishes a session with the first client and the second client connected via the communication network. And maintain information on established sessions A session manager that receives the contents of the document file opened by the first client from the first client, and receives the contents of the received document file. Confirms with the session manager that the sending destination of the document is the second client, and recognizes the contents of the document file. It is characterized by including a controller for sending to the second client, and is applicable to sharing a document file on a PC through a firewall, for example.
[0011]
The controller receives the document file information of the document file opened by the first client, transfers the received document file information to the second client, and transfers the document file sent from the second client. Receiving the request, and transferring the contents of the document file opened by the first client to the second client based on the received transfer request. For example, the same file is transmitted to the second client. When cached, there is no need to perform file transfer, and sharing preparation can be performed efficiently. For example, efficient collaboration by a caching function can be performed by both the client and the collaboration server.
[0012]
A cache for storing the content of the document file; and a cache manager for checking whether or not the content of the corresponding document file is stored in the cache based on the received document file information. If the contents of the corresponding document file are stored in the cache, the contents of the document file are read from the cache and transferred to the second client. This is excellent in that the processing can be omitted. In particular, the present invention is characterized in that the shared file can be stored in the same document format as the original, and it is possible to cache the collaboration server as a cache location in addition to each client.
[0013]
On the other hand, the present invention relates to a method of transferring a document file between a plurality of clients executing a collaboration, wherein a step of specifying a document file to be shared based on a specification by a user, and a step of specifying file information of the specified document file Notifying, receiving a file transfer request in the document file, and transferring the content of the document file based on the received file transfer request, without passing through a web server. For example, a PDF file can be transmitted from one terminal and shared. By converting the file into PDF, the load on the network is reduced, and the enlargement and scrolling of the PDF file, which were not possible with a browser plug-in, can be synchronized.
[0014]
Also, the document file transfer method of the present invention, a session establishing step of establishing a session between a customer and an agent connected via a communication network, Storing information of the established session in a predetermined storage device; A file transfer requesting step for requesting a file transfer of a document file for the purpose of sharing the document file from a customer who has established the session; A transfer destination determining step of determining to the customer a transfer destination of the requested document file by referring to the stored session information; Transferring a requested document file to the customer.
Further, if the file transfer step is characterized in that the contents of the document file transferred from the agent are transferred to the customer, for example, between the agent at the customer contact of the company and the client as the customer, It is possible to share materials that are not listed above, and to achieve good communication.
Further, a file information notifying step of notifying the file information of the document file to be shared from the agent is further included, so that, for example, when the same file is already cached on the client side, efficient processing is possible. This is preferable because sharing of a document file can be realized.
[0015]
The present invention also provides a storage medium storing a program to be executed by a computer, the program comprising: a session establishment process for establishing a session between a plurality of clients connected to a network; A storage process of storing information of the session established by the session establishment process in a predetermined storage device; A receiving process of receiving the content of the document file from one client in which the session was established by the session establishing process; A transfer destination determining process of determining the transfer destination of the content of the document file received by the receiving process to the other client in which the session has been established with one client by referring to the session information stored in the storing process; Based on the result of the transfer destination determination process, The computer is characterized in that the computer executes a transfer process of transferring the content of the document file received by the reception process to the other client having a session established with one client.
[0016]
According to the present invention, in a storage medium storing a program to be executed by a computer, the program includes a process of specifying a document file to be shared with another client based on a specification by a user; It is characterized by causing a computer to execute a process of notifying information, a process of recognizing a file transfer request in the document file, and a process of transferring content of the document file based on the recognized file transfer request. The type of the storage medium is not limited to a specific type. For example, a storage medium such as a CD-ROM or the like which can be installed, or a storage medium such as a hard disk provided in a computer is applicable.
[0017]
On the other hand, when grasped as a program transmission device, the present invention provides a computer with a process of specifying a document file to be shared with another client based on a user's specification and a process of notifying the computer of file information of the specified document file. Storage means for storing a program for executing a process of recognizing a file transfer request in a document file, and a process of transferring the content of the document file based on the recognized file transfer request, and reading the program from the storage means. The transmission device for transmitting the program is characterized in that the present invention is applied to a case where the program is downloaded from a server or the like storing the program to a PC or the like on which the program is to be executed. Becomes possible.
[0018]
BEST MODE FOR CARRYING OUT THE INVENTION
Hereinafter, the present invention will be described in detail based on embodiments shown in the accompanying drawings.
FIG. 1 is a functional block diagram for explaining the overall configuration of the collaboration system according to the present embodiment. In FIG. 1, reference numeral 10 denotes a first client as an agent, for example, a support person in charge of a customer call center. Reference numeral 11 denotes a second client as a customer, for example, a customer who makes an inquiry to a customer call center. The first client 10 and the second client 11 have similar functions, and can collaborate with each other. Reference numeral 20 denotes a collaboration server that establishes a session between the first client 10 and the second client 11 via the Internet 30 and outputs a file transfer request and the like. Further, reference numeral 31 denotes a Web server connected to the Internet 30, which is not a characteristic component in the present embodiment. However, the conventional document file via the Web can also be used. For example, the first document file can be used for sharing from the Web server 31 using a URL.
[0019]
The first client 10 and the second client 11 in FIG. 1 display a PDF cache 14 that stores a document file typified by a PDF (Portable Document Format) developed by Adobe Systems, a document file, and “Start sharing”. The user can perform a user action such as pressing the "" button, and the PDF cache 15 reads and writes to the PDF cache 14, and changes the state of the PDF viewer 15 such as displaying and scrolling a specified file. Further, a PDF control 13 for executing various controls such as transferring a user action from the PDF viewer 15 to the collaboration server 20 is provided. Here, in the present embodiment, the PDF viewer 15 is formed as a PDF file viewer using, for example, Adobe Systems' Acrobat Core API, and includes, for example, a sharing start button, page movement, scrolling, enlargement / Buttons with functions such as reduction have been created. In addition, a Web browser 17 and a Web browser control 16 for controlling event monitoring and status change of the Web browser 17 are provided so that the URL is shared with other clients. If the URL is not cached, the HTML is dropped from the Web server 31. In addition, it is configured to be able to execute functions such as web collaboration that has been performed conventionally.
[0020]
Further, the collaboration server 20 according to the present embodiment, based on a connection request from the first client 10 as an agent or the second client 11 as a customer, establishes a pair with a session manager 21 that establishes these sessions. And a session DB (database) 22 for storing the Further, a PDF cache 24 for caching document files such as PDF, and a PDF cache manager 23 for controlling transfer of PDF files are provided. The PDF cache 24 can store the shared file in the same format as the original. Upon receiving a file transfer request, the PDF cache manager 23 checks whether or not the same file is stored in the PDF cache 24 based on the file name, size, date, and the like. Is configured to issue a file transfer request to a client having a PDF file, and to transfer the file if cached. Also, a Web cache 26 and a cache manager 25 for controlling the Web cache 26 are provided. According to the URL cache information received from one of them, it is selected whether to request a file transfer from the Web server 31 or to transfer the file from the Web cache 26. It is configured to be able to execute the web collaboration function from. The collaboration server 20 functions so that a session can be established across a firewall (fire wall), and it is possible to execute a collaboration between the first client 10 and the second client 11 across a firewall. It becomes possible.
[0021]
Next, the flow of each process in the present embodiment will be described in detail.
FIG. 2 is a flowchart showing the flow of processing up to session establishment in the present embodiment as viewed from the collaboration server 20. The flow of this processing will be described with reference to FIGS. 2 and 1. First, the session manager 21 determines whether or not there is a connection request from any client (block 102). If there is no connection request, the process returns to the start of block 101, and it is determined again whether there is a connection request. If there is a connection request from the client, it is determined whether the client is an agent or a customer (block 103). If the agent is the agent (for example, the first client 10), the agent is added to the agent list of the session DB 22 and the agent (for example, the first client 10) is notified of the successful logon (block 104). Wait for connection request from customer.
[0022]
On the other hand, if it is determined in block 103 that the client is a customer (for example, the second client 11), it is determined whether an agent is already logged on (block 105). If the agent is logged on, a pair with any agent (for example, the first client 10) is created, and the customer (for example, the second client 11) is notified of the successful logon and the session establishment (block 106). Thereafter, the corresponding agent (for example, the first client 10) is notified of the session establishment (block 107), and the session establishment is completed (block 108).
On the other hand, if it is determined in block 105 that the agent has not logged on yet, the customer (for example, the second client 11) is notified of the logon failure, that is, the agent is absent (block 109). Returning to the start, it is determined again whether there is a connection request.
[0023]
Next, the flow of processing from the establishment of a session to the start of sharing of a document file such as PDF, which is the most characteristic part of the present embodiment, will be described in detail with reference to FIGS. In FIG. 3, the flow is shown separately for the user action in the first client 10 as the agent and the processing in the PDF control 13 on the agent side, the collaboration server 20, and the PDF control 13 in the second client 11 as the customer. Although an example is shown in which an agent shares a document file with a customer, it is possible to actually share the document file from either.
[0024]
First, the PDF viewer 15 on the agent side (the first client 10) opens a local PDF file from the “Open” menu of “File” (block 111). In response, the PDF control 13 displays the specified file (block 112). Using the displayed file, the user on the agent side presses a “share start” button provided in the PDF viewer 15 to request sharing start (block 113). Upon receiving this request, the PDF control 13 on the agent side turns on an indicator indicating that preparation is being made, for example, a red lamp, and notifies the collaboration server 20 of file information (block 114). Upon receiving this notification, the collaboration server 20 checks the file transfer destination with the session manager 21 and transfers the file information to the customer side (second client 11) (block 115). The PDF control 13 on the customer side determines whether the same file is cached in the PDF cache 24 by judging from the file name, size, date and the like in the transferred file information (block 116). If the same file is not cached on the client side, the PDF control 13 outputs a file transfer request to the collaboration server 20 (block 117).
[0025]
Next, the collaboration server 20 that has received the file transfer request from the customer side (second client 11) judges whether the same file is cached in the PDF cache 24 based on the file name, size, date, and session information. A check is made (block 118). If not cached, a file transfer is requested to the agent side (first client 10) (block 119). The PDF control 13 on the agent side (the first client 10) receiving the request transfers the requested file to the collaboration server 20 (block 120). Upon receiving the file transfer, the collaboration server 20 checks the transfer destination with the session manager 21 and transfers the file to the customer side (block 121). If it is determined in block 118 that the same file has been cached, the file is read from the PDF cache 24 and transferred to the customer without requesting the agent to transfer the file (block). 121). As described above, when the data is already cached, the file transfer from the agent side can be omitted, and the sharing of the PDF can be achieved in a short time.
[0026]
Next, the PDF control 13 on the customer side (the second client 11) receives the file from the collaboration server 20 (block 122), and then displays the file on the PDF viewer 15 and, at the same time, prepares for sharing such as a blue lamp. Is displayed to notify the collaboration server 20 that the preparation for sharing is completed (block 123). Similarly, when the cache has been cached in the above-described block 116, an indicator indicating that the preparation for sharing is OK is displayed to notify that the preparation for sharing is completed. If the data is cached by the determination in block 116, the transfer request processing from block 117 to block 122 can be omitted, and a series of processing time up to PDF sharing can be greatly reduced. Next, the collaboration server 20 having received the notification in block 123 confirms the transfer destination to the session manager 21 and notifies the PDF control 13 on the agent side (first client 10) of a message (block 124). Upon receiving this notification, the agent-side PDF control 13 turns on the sharing preparation OK indicator, for example, a blue lamp, and a series of processes up to the start of PDF sharing is completed. As described above, in the present embodiment, a transfer request can be issued to the client, and a local file can be transferred and sharing can be started. Unlike the prior art, it is possible to immediately collaborate using a free document file. As described above, it is naturally possible to share from the customer side (the second client 11) to the agent side (the first client 10). Collaboration can be immediately executed based on the document file. Here, the term “collaboration” refers to transmitting an action that has occurred in one client to the other client and causing the same to obtain a similar result.
[0027]
Next, the synchronization of actions performed after sharing of PDF is started will be described with reference to FIG. First, FIG. 4 is a block diagram for describing a configuration for synchronizing actions according to the present embodiment. The PDF control 13 of the first client 10 and the second client 11 is provided with an event monitoring unit 41 that monitors various events such as pressing a button on a screen, scrolling, and executing drawing. In response to the information from the event monitoring unit 41, necessary items are selected by the event control unit 42. That is, the event control unit 42 determines whether the generated event is an event to be synchronized or an event not to be synchronized, for example, in the case of the cursor synchronization mode, for example, in synchronization with the movement of the cursor. The data conversion unit 43 converts the event to be synchronized determined by the event control unit 42 into collaboration data. The converted data is transmitted from the data transmission unit 44 to the collaboration server 20.
On the other hand, when an action occurs in the client that has started sharing, collaboration data is transmitted from the collaboration server 20. The data receiving unit 45 receives the collaboration data, and the event information conversion unit 46 converts the collaboration data into event information. The event operation unit 47 receives the output from the event information conversion unit 46 and executes an action item on the PDF viewer 15.
[0028]
Next, a flow when an attempt is made to display the next page, which is one example of the action synchronization, will be described with reference to FIGS.
First, an event of clicking a “next page” button as a user action occurs in the PDF viewer 15 on the agent side (first client 10) (block 131). In response to this event, the PDF control 13 on the agent side turns on the indicator of preparation for sharing, for example, such as a red lamp, displays the next page on the PDF viewer 15, and notifies the collaboration server 20 of the fact. (Block 132). Upon receiving the notification, the collaboration server 20 checks the transfer destination with the session manager 21 and notifies the message to the customer side (second client 11) (block 133). Upon receiving the notification, the PDF control 13 on the customer side displays the next page on the PDF viewer 15 and notifies the collaboration server 20 of a page transition completion message (block 134). Upon receiving the notification, the collaboration server 20 checks the transfer destination with the session manager 21 and notifies the agent of the message (block 135). Upon receiving this notification, the agent-side PDF control 13 turns on the sharing preparation OK indicator, for example, a blue lamp, and the series of processes for displaying the next page ends.
[0029]
As described above, the display of the next page has been described as an example of the action synchronization, but the collaboration in the present embodiment is not limited to the display of the next page. For example, it can be synchronized with actions such as drawing a line from A to B, changing the color of the line, changing the window size, and scrolling. In such a case, it is possible to respond by changing the message sent to the collaboration server in FIG. 5 to the action content such as execution of drawing. Here, in the present embodiment, the burden on the network is reduced by converting the file into PDF. However, as an example of synchronizing actions, enlargement of a PDF file, which was impossible with a browser plug-in up to now, Scrolling can also be synchronized. In addition, a function of saving the PDF on the transferred side can be added.
Further, in addition to these basic functions, the viewer can be configured to be created by MDI (Multiple Document Interface) which is an interface technology provided by Microsoft Corporation. With such a configuration, it is possible to synchronize a plurality of PDF files.
Note that FIG. 5 shows a case where the next page is displayed on the agent side (first client 10), but a case where the next page is displayed on the customer side (second client 11). Can be realized by a similar flow.
[0030]
In the present embodiment, the collaboration server 20 has been described as a mediation of the collaboration of the client. It is also possible to omit the collaboration server 20, for example, by directly connecting to the IP address. More specifically, each PC creates a PDF file viewer using, for example, the Acrobat Core API, and creates buttons having functions such as page movement, scrolling, and enlargement / reduction. As a communication function, for example, a session control, which is a function for establishing a WebCollaboration session, is added to the viewer. The method of establishing a session by the session control is performed in the same manner as in the ChatWindow class, and provides methods such as synchronized and isSyncronized, and synchronizes using the methods. In the present embodiment, since the control classes (WebWindow, IEWebBrowser) for IE and Netscape are not used, it is not necessary to create a control class for each browser as in the case of chat. Next, a function of performing FTP (File Transfer Protocol) between PCs having a session is added. That is, when a PDF file is opened by a viewer on any PC to which a session is set, the PDF file is transferred to the other PC and displayed. In the present embodiment, only a specific page of the PDF file can be transferred using the Acrobat Core API, so that only the page desired to be disclosed to the other party can be disclosed. Next, as a collaboration function, open files are synchronized between PCs having a session. Specifically, when a page movement, scrolling, or enlargement / reduction button is pressed by a viewer on any of the PCs, by sending the event to the other, the viewing areas can be synchronized with each other.
[0031]
As described above, in the present embodiment, the information exchange (collaboration) between the first client 10 and the second client 11 has been described. However, the number of clients executing the collaboration is increased, and three or more clients are executed. It is also possible to share local files with. For example, when one of the applications is applied to a distance learning system, an exchange lesson or a distance lecture is performed between a teacher and one student, and between the teacher and many students. If the present embodiment is applied to such an application, there is no need to post materials on a web server in advance. For example, a PDF file for a lecture created by a teacher can be sent to students. It is possible to immediately share the PDF file created by the student, and it is possible to smoothly share the PDF file created by the student. Collaboration can be performed.
[0032]
When installing a program for executing each function in the present embodiment, a program for executing each process is stored in a storage medium such as a CD-ROM, and these storage mediums are stored in a computer such as a PC. (Connected) reading means. That is, the first client 10, the second client 11, and the collaboration server 20 may be configured to install and execute a program using a storage medium such as a CD-ROM. Alternatively, the program may be configured to be downloaded to each client via the Internet or the like without using such a storage medium. In such a case, a program transmission device such as a PC having a storage unit storing a program for executing each of the above-described processes transmits the program to each client or the like via the Internet or the like using the program transmission unit of the PC or the like. It is configured as follows. In particular, when the present embodiment is applied to an application in which the client is located at a remote location, it becomes possible to provide each client with the functions of the present embodiment by a method of downloading a program, A highly convenient collaboration system can be formed over a wide range.
[0033]
【The invention's effect】
As described above, according to the present invention, a document file can be transmitted and shared from one terminal without passing through a web server, so that a quick and highly convenient collaboration can be provided. it can.
[Brief description of the drawings]
FIG. 1 is a functional block diagram for describing an overall configuration of a collaboration system according to the present embodiment.
FIG. 2 is a flowchart showing a flow of processing up to session establishment in the present embodiment.
FIG. 3 is a flowchart showing a flow of processing up to the start of sharing of a document file in the present embodiment.
FIG. 4 is a block diagram for describing a configuration for synchronizing actions according to the present embodiment.
FIG. 5 is a flowchart showing a processing flow when an attempt is made to display the next page.
[Explanation of symbols]
10 first client (agent), 11 second client (customer), 13 PDF control, 14 PDF cache, 15 PDF viewer, 16 web browser control, 17 web browser, 20 collaboration server, 21 ... Session Manager, 22 ... Session DB, 23 ... PDF Cache Manager, 24 ... PDF Cache, 25 ... Cache Manager, 26 ... Web Cache, 30 ... Internet, 31 ... Web Server, 41 ... Event Monitoring Unit, 42 ... Event Control Unit 43, a data conversion unit, 44, a data transmission unit, 45, a data reception unit, 46, an event information conversion unit, 47, an event operation unit

Claims (10)

A document file sharing system for sharing a document file used in collaboration between clients connected via a communication network,
Session establishment means for establishing a session between the first client and the second client executing the collaboration, and holding information on the established session;
When a specific page of the document file used by the first client is received from the first client with which the session has been established by the session establishing means, the transfer destination of the specific page of the document file is the second client. A file transfer unit for recognizing the document file by confirming it with the session establishment unit and transferring a specific page of the document file to the second client. File transfer requesting means for requesting file transfer from the second client to the first client,
2. The document file sharing system according to claim 1, wherein the file transfer unit transfers the document file based on a request from the file transfer request unit. 3. The document file sharing system according to claim 2, further comprising file information sending means for sending file information of the document file held by said first client to said second client. A session manager that establishes a session with the first client and the second client connected via the communication network and holds information on the established session;
A specific page of the document file opened by the first client is received from the first client, and the session manager is informed that the destination of the received specific page of the document file is the second client. A collaboration server comprising: a controller that recognizes the document file by checking and sends a specific page of the document file to the second client. The controller receives document file information of a document file opened by the first client, transfers the received document file information to the second client, and sends a document transmitted from the second client. 5. The method according to claim 4, further comprising: receiving a file transfer request, and transferring a specific page of the document file opened by the first client to the second client based on the received transfer request. Collaboration server described. A cache for storing specific pages of the document file,
A cache manager that checks whether a specific page of the corresponding document file is stored in the cache based on the received document file information,
By the cache manager, when a particular page of a corresponding document file is stored in the cache, characterized in that from the cache reads a specific page of the document file to transfer to the second client The collaboration server according to claim 5, wherein A session establishing step of establishing a session between a customer and an agent connected via a communication network;
Storing information of the established session in a predetermined storage device;
A file transfer requesting step for requesting transfer of a specific page of the document file for the purpose of sharing the document file from the customer with which the session has been established;
A transfer destination determining step of determining the transfer destination of the requested document file to the customer by referring to the stored information of the session;
Transferring a specified page of the requested document file to the customer. 8. The document file transfer method according to claim 7, wherein in the file transfer step, a specific page of the document file transferred from the agent is transferred to the customer. 8. The document file transfer method according to claim 7, further comprising a file information notifying step of notifying the file information of the document file to be shared from the agent. In a storage medium storing a program to be executed by a computer,
The program is
A session establishment process for establishing a session between a plurality of clients connected to the network;
A storage process of storing information of the session established by the session establishment process in a predetermined storage device;
A receiving process of receiving a specific page of the document file from one of the clients whose session has been established by the session establishing process;
By referring to the information of the session stored by the storage processing, a transfer destination of a specific page of the document file received by the reception processing is determined to the other client in which a session is established with the one client. Destination determination processing to be performed,
And causing the computer to execute a transfer process of transferring a specific page of the document file received by the reception process to the other client based on a result of the determination by the transfer destination determination process. .

Images