JP4937070B2 - Document data management method, document data creation method, server, and computer program - Google Patents

Description

  The present invention relates to a method for managing and creating document data such as a form file, a server and a computer program therefor.

  In recent years, awareness of information security has increased, and leakage of private data has become a problem. In particular, in a network system, data stored in a server used by being connected from a plurality of computers is read or written by a large number of users, so that it is easy to leak and it is difficult to detect the leak.

  On the other hand, Patent Document 1 discloses a file protection method that prevents an operating system from accessing a file to be protected.

  According to this method, a protected area that is inaccessible from the operating system is created in a storage device such as a hard disk. By protecting a file to be protected from a non-protected area accessible from the operating system to a protected area, the file is protected from unauthorized processing such as data leakage and falsification.

  Also, Patent Document 2 discloses a confidential document management method that enables access to a confidential document only via a proxy file that represents the confidential document.

  According to this method, a proxy file that can be directly accessed by the user and has no content is generated, and a confidential document is accessed via the generated proxy file. Further, by authenticating the user when accessing the confidential document, access to the confidential document by an unauthorized user is prevented.

  On the other hand, in a business system composed of a plurality of computers, a system using a WWW (world wide web) technology such as a web browser and a web server (hereinafter referred to as a web system) has been spreading.

  In the Web system, various processes can be performed by accessing a Web server using a Web browser as a client. Since the Web browser is installed in many personal computers as a standard feature, it is easy to introduce and saves time and effort for updating the software on the client side.

  FIG. 9 is a diagram showing a configuration of a conventional Web system 70.

  The Web system 70 includes a server 71 and a personal computer 72. The server 71 is a server having a Web server function, and performs processing in response to a request from the personal computer 72. The personal computer 72 requests the server 71 as a client for processing via the installed Web browser. A plurality of personal computers 72 may be provided.

  As an example, the flow of processing when printing a form representing data and logs stored in the server 71 in a predetermined format will be described below.

The personal computer 72 requests the server 71 to create a form file that is data used for printing (step # 81). The server 71 creates a form file based on the request from the personal computer 72 (step # 82). When the form file is created, the server 71 sends a URL (uniform resource locator) indicating the location where the created form file is stored to the personal computer 72 (step # 83). The personal computer 72 downloads the form file based on the received URL (step # 84). The personal computer 72 performs printing using a printer or the like based on the downloaded form file.
JP 2004-220400 A JP 2006-260176 A

  However, the conventional Web system has the following problems.

  That is, in the conventional Web system, the created form file is stored on the server in the form printing process or the like. For this reason, when the Web system is used by a plurality of personal computers, the created form file can be accessed from a personal computer different from the personal computer that requested the creation of the form file. . Therefore, data may be leaked to an unrelated third party who uses the personal computer.

  When the file protection method disclosed in Patent Document 1 is used in a conventional Web system, it operates as follows.

  When the client personal computer requests the server to create a form file used for printing, the server creates the form file and stores it in a storage device such as a hard disk of the server itself. At this time, the created form file is moved from the non-protected area to the protected area so that the form file cannot be accessed via the server operating system.

  However, in the file protection method disclosed in Patent Document 1, if the user is authenticated as an authorized user by the input user ID and password, a list of files stored in the protection area is displayed.

  Similarly, when the confidential document management method disclosed in Patent Document 2 is used in a conventional Web system, if the user is authenticated as a legitimate user, the confidential document information is displayed.

  Therefore, when a malicious third party steals the user ID and password, the file can be accessed and the contents of the file may be leaked.

  In view of these points, the present invention aims to appropriately protect private data in a Web system.

  A document data management method that achieves the above object is a document data management method for managing document data requested by a user at a server, wherein a session between a terminal device operated by the user and the server is started. A first step of assigning a session ID for identifying the session to the terminal device; and a second step of receiving a document data management request and the session ID assigned to the terminal device from the terminal device. A third step of storing the document data in a second server protected by a firewall in association with the session ID received together with the management request for the document data based on the received management request; From the terminal device, stored in the second server and the session ID assigned to the terminal device. A fourth step of receiving the download request for the document data, the session ID associated with the document data, and the session ID received together with the download request for the document data match And a fifth step of reading out the document data from the second server and transmitting it to the terminal device.

  According to the document data management method of this aspect, since the document data is stored in the second server protected by the firewall, access to the document data can be restricted.

  A document data creation method for achieving the above object is a document data creation method for creating document data based on a user's request in a server, and starts a session between a terminal device operated by the user and the server. In this case, a first step of assigning a session ID for identifying the session to the terminal device, and the session ID assigned to the terminal device and the document data creation request are received from the terminal device. A second step, a third step of creating the document data based on the received creation request, and the created document data in association with the session ID received together with the document data creation request, A fourth step to be stored in the second server protected by the terminal device, and the terminal device A fifth step of receiving the session ID assigned to the document server and the download request for the document data stored in the second server; the session ID associated with the document data; and the document data And a sixth step of reading out the document data from the second server and transmitting the same to the terminal device when the session ID received together with the download request is matched.

  According to the document data creation method of this aspect, the document data created in the server is stored in the second server protected by the firewall, so that access to the created document data can be restricted.

  In a preferred aspect, in the document data creation method, in the fourth step, the created document data is stored in association with a unique file ID for each of the document data, and is associated with the created document data. And the file ID associated with the document data requesting download is received from the terminal device in the fifth step, In the sixth step, when the file ID associated with the document data matches the file ID received together with the download request related to the document data, the document is received from the second server. Data is read and transmitted to the terminal device.

  According to the document data creation method of this aspect, when the same user requests creation of a plurality of document data using the same terminal device, the created document data can be distinguished.

In a preferred embodiment, in the sixth step, the document data creation method transmits the binary file that is the document data read from the second server and the file name of the binary file to the terminal device.

  According to this form of document data creation method, when the document data stored in the second server is downloaded, the server does not have to store the document data.

  In a preferred aspect, the document data creation method stores the session ID as valid with a time limit even after the session ends, and starts the session between the terminal device and the server. When the session ID received from the session ID storage device matches the session ID stored in the session ID storage means, the session ID received from the terminal device is assigned to the terminal device as the session ID of the session in the first step. .

  According to the document data creation method of this form, the same session ID can be continuously used when the session is once ended and the session is resumed.

  The document data refers to form files, form data, and other data that can be printed as documents.

  According to the present invention, it is possible to appropriately protect private data in a Web system.

  FIG. 1 is a diagram illustrating an overall configuration of a Web system 1 according to an embodiment of the present invention, FIG. 2 is a diagram illustrating a functional configuration of a Web server 2, and FIG. 3 is a functional configuration of an intermediate file management server 4. It is a figure to do.

  The Web system 1 is an ASP (Application Service Provider) system in which each organization uses one Web server in common, instead of installing and using one Web server at each organization where the Web system is introduced. It takes the form called. The Web server is installed and used in, for example, an IDC (internet data center) provider.

  As shown in FIG. 1, the Web system 1 includes a Web server 2, a firewall 3, an intermediate file management server 4, a DB server 5, and a plurality of personal computers 8 (81a, 81b, ..., 82a, 82b, ..., 83a, 83b,...), A printer 9, a communication line 10, and a plurality of routers RT. The personal computer 8 and the Web server 2 can be connected to each other via the router RT and the communication line 10. The Web server 2 and the intermediate file management server 4 can be connected to each other via the firewall 3. The Web server 2 and the DB server 5 can be connected to each other via the firewall 3.

  In the Web system 1, a personal computer 8 as a client requests various processes to the Web server 2 via a Web browser, and the Web server 2 cooperates with the intermediate file management server 4 and the DB server 5 to perform the requested processes. Is a network system.

  The Web server 2 has a function of a Web server that accumulates information such as HTML (hypertext markup language) documents and images and transmits the information in response to a client request via the Web browser. In addition, by executing a program in response to a client request, a function for transmitting various processing results to the client, a function for creating various files such as a form file in cooperation with the DB server 5, a form file, etc. It has a function to download.

  For example, when the user operates the personal computer 8 as a client and inputs data to the Web system 1, the input data is stored in the DB server 5. Next, when the user requests the Web system 1 to print a form, a form file is created based on the data stored in the DB server 5 and the created form file is downloaded to the personal computer 8. The printer 9 performs printing processing. The Web server 2 mediates these processes.

  The Web server 2 has a RAM (random access memory) and a CPU, and the above-described program is read into the RAM as necessary, and the program is executed by the CPU.

  The firewall 3 is a firewall for preventing unauthorized access from the outside.

  A firewall captures all communication requests from inside and outside and arbitrarily passes or prohibits them, thereby allowing only necessary communication and ensuring security. For example, these controls are performed using a port number, an IP address, or a communication direction of communication to be passed through the firewall 3.

  Examples of the firewall include a dedicated device, a server or router equipped with the function, and a software product. Any of these may be used in the present embodiment.

  In the Web system 1 of this embodiment, the firewall 3 is set so that only the Web server 2 can access the intermediate file management server 4 and the DB server 5. Therefore, the personal computer 8 cannot access the intermediate file management server 4 or the DB server 5. In order to use the file or data of the intermediate file management server 4 or the DB server 5 from the personal computer 8, the personal computer 8 must access the Web server 2 to intervene processing in the Web server 2. In other words, since the firewall 3 exists, the personal computer 8 cannot directly access the intermediate file management server 4 or the DB server 5 but performs indirect access.

  The intermediate file management server 4 stores a file created by the Web server 2, a file sent from the personal computer 8 or the like in a memory such as a hard disk. The stored file is managed using the intermediate file management database FM (see FIG. 3).

  The DB server 5 stores various data and logs used in the Web system 1. These data or logs are updated and read in response to a request from the Web server 2.

  The personal computer 8 is a client of the Web system 1 and has a Web browser. Based on the input by the user, various processes are requested to the Web server 2 via the Web browser.

  The personal computer 8 is installed in each of a plurality of organizations such as companies and organizations. The personal computer 8 installed in each organization is connected to a network of different segments for each organization divided by the router RT.

  The printer 9 performs printing processing using paper in response to a request from the personal computer 8.

  The communication line 10 is a communication line in which security for connecting the network of each organization and the Web server 2 is secured, and a dedicated line, a VPN (virtual private network), an Internet VPN, or the like is used. In addition, the Internet can be used as the communication line 10.

  When the Web system 1 takes the form of an ASP system, in the conventional Web system, a form file used for printing is stored in the Web server, and the form file can be accessed from other unrelated organizations. It becomes a state.

  On the other hand, in the present embodiment, the form file created by the Web system 1 is stored in the intermediate file management server 4. Hereinafter, what kind of processing each part of the Web server 2 and the intermediate file management server 4 performs to realize this will be described in detail.

  In FIG. 2, a login receiving unit 201 receives a login request from the personal computer 8 to the Web system 1. The login may be performed by inputting a user ID (user identifier UI) and a password, or may be a method using an IC (integrated circuit) card.

  The session ID assigning unit 202 transmits a session identifier SI that is a session ID to the personal computer 8 used by the user who is authenticated by the login. This starts a session.

  Note that the session refers to a period from when the personal computer 8 or the like logs in to the Web server 2 until the user logs out, or processing or communication during that period. That is, a session can be said to be a logical connection relationship provided for exchanging data between computers. In order to exchange data between the two, it is necessary to first establish a session between them, and when the data exchange is completed, the session ends. The Web server 2 terminates the session when the logged-in personal computer 8 voluntarily logs out or when there is no data exchange with the logged-in personal computer 8 for a predetermined time. When a user tries to exchange data with the Web server 2 after the session ends, it is usually necessary to perform authentication again and log in. In the present embodiment, an individual session ID storage unit 203 that stores a session ID (session identifier) as valid even after the session ends is provided. Details will be described later.

  The session ID is for holding a state in which the user is authenticated by login as one session. When the user logs in, the session ID issued by the Web server is transmitted to the client. The transmitted session ID is stored as an information file called “cookie” in a hard disk of a personal computer as a client. The stored session ID is automatically transmitted to the Web server every time communication is performed from the Web browser to the Web server while the user is logged in. The Web server recognizes the communication by the authenticated user by receiving the session ID. Further, when the user logs out, the stored session ID is deleted.

  Therefore, once the user logs in, it is not necessary to perform authentication every time communication is performed until the user logs out, that is, for one session.

  The session ID is used after being encoded by a method such as Base64, for example. Further, by increasing the number of digits (number of bits), it becomes difficult for a third party to decipher and the security can be improved.

  In this embodiment, when the session identifier SI is given to the personal computer 8, in addition to the above-described general session ID issuance session ID SI, a session identifier SI managed uniquely by the Web system 1 is also used. .

  The individual session ID storage unit 203 stores a session identifier SI and a validity period (validity period) YK related to a predetermined user.

  The session identifier SI is deleted from the personal computer 8 used by the user once the user logs out. Therefore, when only the session identifier SI obtained by issuing a general session ID is used in the Web system 1, the operation is as follows. That is, when a process requiring a long time is requested from the Web server 2 and the user logs out from the Web system 1 to engage in other tasks, a new session identifier SI is given when logging in again. End up. For this reason, as it is, the Web server 2 cannot recognize that it is the user who requested the process.

  Therefore, for a predetermined user, the session identifier SI and the necessary expiration date or validity period are stored in the individual session ID storage unit 203 in advance. For example, for a specific user, the session identifier SI for which the session has ended is registered in the individual session ID storage unit 203 with the specific period or the like as the effective period until the next day only on the current day. When the validity period expires, the registration is deleted.

  When a login request is received by the login receiving unit 201, the session ID providing unit 202 refers to the individual session ID storage unit 203 and determines whether or not the user is a predetermined user related to the stored session identifier SI. If the user is a predetermined user, the session identifier SI is read from the individual session ID storage unit 203 and transmitted to the personal computer 8. Otherwise, a new session identifier SI is issued and transmitted to the personal computer 8.

  The file creation request accepting unit 204 accepts a request for creating a form file used for printing from the personal computer 8.

  The file creation unit 205 creates a form file DF based on the request received by the file creation request reception unit 204.

  The file storage request unit 206 requests the intermediate file management server 4 to store the session identifier SI transmitted from the personal computer 8 together with the request for creating the form file and the created form file DF. .

  In FIG. 3, the file storage request reception unit 401 of the intermediate file management server 4 receives a request from the file storage request unit 206 of the Web server 2.

  The file storage unit 402 stores the form file DF created by the file storage request unit 206, the form file DF uploaded from the personal computer 8, and the like.

  The intermediate file management database FM issues a unique file identifier (file ID) FI to the stored form file DF, the session identifier SI related to the request to create the form file DF, the issued file identifier FI, The file path FS indicating the location where the form file DF is stored is recorded in association with each other and managed. In the intermediate file management database FM, a download file name ND that is a file name used in the personal computer 8 is recorded correspondingly.

  The file ID notification unit 403 notifies the Web server 2 of the file identifier FI issued for the form file DF.

  Returning to FIG. 2, the URL notification unit 207 of the Web server 2 notifies the personal computer 8 of a URL indicating the program that performs processing for downloading the form file DF, including the issued file identifier FI as a parameter.

  The personal computer 8 requests the Web server 2 to download the form file DF based on the notified URL.

  The download request receiving unit 208 receives a request for downloading the form file DF from the personal computer 8.

  The file read request unit 209 requests the intermediate file management server 4 to read the form file DF based on the session identifier SI and the file identifier FI transmitted from the personal computer 8 together with the download request.

  In FIG. 3, a file read request receiving unit 404 of the intermediate file management server 4 receives a request from the file read request unit 209 of the Web server 2.

  The file reading unit 405 refers to the intermediate file management database FM based on the session identifier SI and the file identifier FI transmitted from the personal computer 8, and acquires the file path FS of the form file DF. The form file DF is read from the file storage unit 402 based on the acquired file path FS.

  Returning to FIG. 2, the file transmission unit 210 of the Web server 2 transmits the read form file DF to the personal computer 8.

  The personal computer 8 prints on the paper using the printer 9 based on the received form file DF.

  4 is a diagram showing an example of processing when creating a file in the Web system 1, FIG. 5 is a diagram showing an example of a form printing screen PS displayed on the front surface of the personal computer 8, and FIG. FIG. 7 is a diagram illustrating an example of a form PD.

  Next, the flow of processing when the user instructs the Web system 1 to print a form will be described with a specific example.

  In FIG. 4, a session identifier SIA “EEEEFFFFGGGGHHHH” is stored in the personal computer 8 used by a user who has already logged in to the Web system 1. This session identifier SIA “EEEEFFFFGGGGHHHH” has the same content as the session identifier SIA1 stored in the individual session ID storage unit 203 of the Web server 2 by the prior setting.

  When the user clicks the “print” button BT on the form print screen PS as shown in FIG. 5, a request to create a form file used for printing is transmitted from the personal computer 8 to the Web server 2 (step # 11). .

  Based on the request, the Web server 2 creates a form file DFA whose file name NDA is “aaa.doc” (step # 12).

  The Web server 2 requests the intermediate file management server 4 to store the created form file DFA (# 13). At this time, the intermediate file management server 4 stores the file as an intermediate file that is temporarily stored, and the file name is “5678.tmp”. The file path FSA in the intermediate file management server 4 is “D: \ temp \ 5678.tmp”.

  When the Web server 2 makes a request for processing to the intermediate file management server 4, a program executed on the Web server 2 is stored in the intermediate file management server 4 using RPC (remote procedure call). You may make it call the subroutine currently made directly. For example, a subroutine for performing processing for storing data in a hard disk or the like in the intermediate file management server 4 may be called. According to this method, the form file created by the Web server 2 can be directly stored in the intermediate file server 4 without being stored in the Web server 2.

  The intermediate file management database FM issues a file identifier FIC “1000000002”. The session identifier SIA “EEEEFFFFGGGGHHHH” received from the personal computer 8, the issued file identifier FI “1000000002”, the file path FSA “D: \ temp \ 5678.tmp”, and the file name used by the personal computer 8 when downloaded The download file name NDA “aaa.doc” is recorded in the intermediate file management database FM in association with each other (step # 14). In this way, the intermediate file management database FM is updated.

  The Web server 2 transmits to the personal computer 8 a form file acquisition URL “http: //websvr/file.aspx? Fileid = 1000000002”, which is a URL used when the personal computer 8 acquires the form file DFA. The form file acquisition URL includes a file identifier FIA “1000000002”.

  Next, the flow of processing when the personal computer 8 downloads a form file used for form printing from the Web server 2 will be described with a specific example.

  The personal computer 8 transmits a form file acquisition URL “http: //websvr/file.aspx? Fileid = 1000000002” and requests the Web server 2 to download the form file (step # 21). At this time, the session identifier SIA “EEEEFFFFGGGGHHHH” stored in the personal computer 8 is also transmitted to the Web server 2 at the same time.

  For session identifier SIA “EEEEFFFFGGGGHHHH”, session identifier SIA1 “EEEEFFFFGGGGHHHH” having the same content is stored in individual session ID storage section 203. Therefore, even when the user logs out after the request for creating the form file, if the user logs in again within the validity period of the session identifier SIA, the same session identifier SIA as that at the time of requesting the creation of the form file is given. The session identifier SIA is used as a new session identifier SI.

  The Web server 2 requests the intermediate file management server 4 to read out the form file DFA based on the session identifier SIA “EEEEFFFFGGGGHHHH” and the file identifier FIA “1000000002” transmitted from the personal computer 8 (step # 22). .

  The intermediate file management server 4 refers to the intermediate file management database FM and uses the session identifier SIA “EEEEFFFFGGGGHHHH” and the file identifier FIA “1000000002” as keys, and the corresponding file path FSA “D: \ temp \ 5678.tmp”. And download file name NDA “aaa.doc” is extracted. The form file DFA is read based on the extracted file path FSA “D: \ temp \ 5678.tmp”.

  The Web server 2 acquires the read form file DFA in real time as binary data, and transmits it to the personal computer 8 together with the download file name “aaa.doc” (step # 23). Note that the downloaded form file DFA and the data for managing the form file DFA may be deleted from the file storage unit 402 and the intermediate file management database FM at an appropriate timing.

  The personal computer 8 stores the received form file DFA as a file name “aaa.doc” and prints it on a sheet using the printer 9 based on the form file. As shown in FIG. 7, a form PD is output.

FIG. 8 is a diagram showing an example of processing at the time of file upload of the Web system 1. In the Web system 1, an image file of an image read by a scanner and a form file processed by the personal computer 8 are uploaded from the personal computer 8. be able to. The uploaded form file can be stored and managed in the intermediate file management server 4 as in the case of creating a form file in the Web system 1.

  Next, the flow of processing when the personal computer 8 uploads an existing form file to the Web server 2 will be described with a specific example.

  The personal computer 8 transmits the form file DFB “bbb.doc” to the Web server 2 (step # 21). At this time, the session identifier SIA “EEEEFFFFGGGGHHHH” stored in the personal computer 8 is also transmitted to the Web server 2 at the same time.

  The intermediate file management server 4 includes, as empty file information, a session identifier SIA “EEEEFFFFGGGGHHHH”, a file identifier FIA “1000000002”, a file path FSB “D: \ temp \ 8765.tmp”, and a download file name NDB “bbb. doc "are recorded in the intermediate file management database FM in association with each other. At this time, an empty file is stored in the file storage unit 402 (step # 32).

  The intermediate file management server 4 opens the stored empty file, and gives a file handle to the Web server 2 by using the RPC a plurality of times (step # 33).

  The Web server 2 writes the contents of the form file DFB with the file name NDB “bbb.doc” as a stream to the empty file stored in the intermediate file management server 4, thereby storing the form file DFB in the file storage unit. 402 (# 34).

  The form file DFB uploaded to the Web server 2 in the Web system 1 is the same as the form file DF created in the Web system 1, and only the personal computer 8 that stores the session identifier SIA associated with the intermediate file management database FM. Can be downloaded.

  If the uploaded form file DFB is to be shared by a plurality of users, it may be moved from the intermediate file management server 4 to the DB server 5.

  Note that the functions of both the intermediate file management server 4 and the DB server 5 may be realized by a single server.

  The file stored in the intermediate file management server 4 may be other than a form file.

  According to the present embodiment, since the file created by the Web server is stored in the intermediate file management server 4 accessible only by the Web server, it is possible to prevent data leakage to a person unrelated to the file.

  In addition, the session identifier SI, the file identifier FI, the file path PS, the Web server 2, the intermediate file management server 4, the configuration of the whole or each part of the Web system 1, the processing content, the processing order, and the like are appropriately determined in accordance with the spirit of the present invention. Can be changed.

1 is a diagram illustrating an overall configuration of a Web system according to the present invention. It is a figure explaining the functional structure of a Web server. It is a figure explaining the functional structure of an intermediate file management server. It is a figure which shows the example of the process at the time of the file creation of a Web system. It is a figure which shows the example of a form printing screen. It is a figure which shows the example of the process at the time of the file download of a Web system. It is a figure which shows the example of a form. It is a figure which shows the example of the process at the time of the file upload of a Web system. It is a figure which shows the structure of the conventional Web system.

Explanation of symbols

1 Web system 2 Web server (server)
3 Firewall 4 Intermediate file management server (second server)
8 Personal computer (terminal equipment)
202 Session ID Assignment Unit 203 Individual Session ID Storage Unit 205 File Creation Unit 206 File Storage Request Unit 207 URL Notification Unit 402 File Storage Unit 405 File Reading Unit FM Intermediate File Management Database DF Form File (Document Data)
FI file identifier (file ID)
SI session identifier (session ID)

Claims (8)

A document data management method for managing document data requested by a user on a server,
A first step of giving a session ID for identifying the session to the terminal device when starting a session between the terminal device operated by the user and the server;
A second step of receiving a document data management request and the session ID assigned to the terminal device from the terminal device;
A third step of storing the document data in a second server protected by a firewall in association with the session ID received together with the document data management request, based on the received management request;
A fourth step of receiving, from the terminal device, the session ID assigned to the terminal device and the download request for the document data stored in the second server;
When the session ID associated with the document data matches the session ID received together with the download request related to the document data, the document data is read from the second server and the terminal device A fifth step of sending to
A document data management method characterized by comprising: A document data creation method for creating document data on a server based on a user request,
A first step of giving a session ID for identifying the session to the terminal device when starting a session between the terminal device operated by the user and the server;
A second step of receiving, from the terminal device, the session ID assigned to the terminal device and the creation request for the document data;
A third step of creating the document data based on the received creation request;
A fourth step of storing the created document data in a second server protected by a firewall in association with the session ID received together with the document data creation request;
A fifth step of receiving, from the terminal device, the session ID assigned to the terminal device and the download request for the document data stored in the second server;
When the session ID associated with the document data matches the session ID received together with the download request related to the document data, the document data is read from the second server and the terminal device A sixth step of sending to
A document data creating method characterized by comprising: In the fourth step, the created document data is stored in association with a unique file ID for each document data, and the file ID associated with the created document data is stored in the creation of the document data. Send to the terminal device for the request,
In the fifth step, the file ID associated with the document data requesting download is received from the terminal device;
In the sixth step, when the file ID associated with the document data matches the file ID received together with the download request related to the document data, the document is received from the second server. Read the data and send it to the terminal device,
The document data creation method according to claim 2, wherein: The said 6th step WHEREIN: The binary file which is the said document data read from the said 2nd server, and the file name of the said binary file are transmitted to the said terminal device, The Claim 2 or Claim characterized by the above-mentioned. 3. Document data creation method described in 3. The session ID is stored as valid with a time limit even after the session ends, and the session ID received from the terminal device is stored in the session ID storage when starting a session between the terminal device and the server. When the session ID matches the session ID stored in the means, in the first step, the session ID received from the terminal device is assigned to the terminal device as the session ID of the session.
The document data creation method according to any one of claims 2 to 4. A server that manages document data requested by users,
Means for giving the terminal device a session ID for identifying the session when starting a session between the terminal device operated by the user and the server;
Means for receiving, from the terminal device, a document data management request and the session ID assigned to the terminal device;
Means for storing the document data in a second server protected by a firewall in association with the session ID received together with the document data management request based on the received management request;
Means for receiving, from the terminal device, the session ID assigned to the terminal device and the download request for the document data stored in the second server;
When the session ID associated with the document data matches the session ID received together with the download request related to the document data, the document data is read from the second server and the terminal device Means for sending to
The server characterized by having. Session ID storage means for storing the session ID as valid even after the session ends,
The session received from the terminal device when the session ID received from the terminal device matches the session ID stored in the session ID storage means when starting a session between the terminal device and the server. ID is given to the terminal device as the session ID of the session,
The server according to claim 6. A computer program for realizing by a computer a server for managing document data requested by a user,
When the computer program is executed by the computer,
Means for giving a session ID for identifying the session to the terminal device when starting a session between the terminal device operated by the user and the computer;
Means for receiving, from the terminal device, a document data management request and the session ID assigned to the terminal device;
Means for storing the document data in a second server protected by a firewall in association with the session ID received together with the document data management request based on the received management request;
Means for receiving, from the terminal device, the session ID assigned to the terminal device and the download request for the document data stored in the second server;
When the session ID associated with the document data matches the session ID received together with the download request related to the document data, the document data is read from the second server and the terminal device Means for sending to
A computer program for realizing the above by the computer.

Images