Information processing device and information processing system

Abstract

The present invention provides an information processing device and an information processing system that can execute processing on a document even if the user who uses the document does not execute the processing on the document in the device used for authentication. An information processing device having a processor that, when the authentication of a user designated as a document user succeeds, does not permit the document to be processed by the device itself, but permits the command for the user to execute the processing on the document to be given to a processing device different from the device itself.

Description

Technical Field

[0001] The invention relates to an information processing device and an information processing system. Background Art

[0002] There is known a system that transmits an electronic document to a device at a transmission destination and enables a user of the device at the transmission destination to utilize the document.

[0003] The content authentication system described in Patent Document 1 includes a creator terminal used by a content creator and a user terminal used by a content user. The creator terminal has a fingerprint verification code database storing fingerprint verification codes of users who set content usage rights. When creating content, the content creator includes the fingerprint verification codes of users who are given the content usage rights and the user indicating the usage rights given to each user in the subtitle of the content. When creating content, it is possible to set usage rights corresponding to each user for multiple users.

[0004] Patent Document 1: Japanese Patent Application Publication No. 2006-243868

[0005] However, if the user who uses the document processes the document in the device used for authentication, the security of the document may be reduced. For example, if there are many people around the device used for authentication, there is a possibility that the content of the document will be leaked to others if the document is processed in the device used for authentication. Summary of the invention

[0006] An object of the present invention is to provide a system that enables a user who uses a document to execute a process on the document even if the user does not execute the process on the document in a device used for authentication.

[0007] The invention involved in Scheme 1 is an information processing device, which has a processor. When the authentication of a user designated as a document user is successful, the processor does not allow the document to be processed by its own device, but allows the command of the user to process the document to be given to a processing device different from its own device.

[0008] The invention described in Scheme 2 is characterized in that, in the information processing device described in Scheme 1, the processor further receives user information representing the user of the document and the device using the document, and when the group of the own device and the user using the own device and the group of the user and the device using the device represented by the received user information match, even if the authentication of the user is successful, the document is not allowed to be processed by the own device, but a command for the user to process the document is allowed to be given to the processing device.

[0009] The invention described in claim 3 is characterized in that, in the information processing device described in claim 1 or 2, the processor further transmits information indicating that the user is authenticated to the processing device when the user is authenticated.

[0010] The invention described in Scheme 4 is characterized in that, in the information processing device described in any one of Schemes 1 to 3, the processor further does not receive the document, but receives user authentication information urging the user to authorize the command to perform processing on the document to be given to the processing device.

[0011] The invention described in claim 5 is characterized in that, in the information processing device described in any one of claims 1 to 4, the processor prohibits browsing and editing of the document in its own device.

[0012] The invention described in Scheme 6 is characterized in that, in the information processing device described in any one of Schemes 1 to 5, when the authentication of the user is successful, the processor does not allow the document to be processed by its own device, but allows the user's command to print the document to be given to the processing device.

[0013] The invention described in Scheme 7 is an information processing system, which includes a sending end device, a sending destination device and a processing device, the sending end device has a first processor, the first processor specifies the sending destination user of the document and sends the document to the processing device, the sending destination device has a second processor, when the authentication of the user designated as the sending destination of the document is successful, the second processor does not allow the document to be processed by the sending destination device, but allows the command of the user to process the document to be given to the processing device.

[0014] The invention described in Scheme 8 is characterized in that, in the information processing system described in Scheme 7, the first processor sends the document and the sending destination information representing the sending destination user and the sending destination device of the document to the processing device, and the second processor receives the sending destination information. When the own device, i.e., the sending destination device, matches the group of the user using the own device, i.e., the sending destination device, and the group of the sending destination user and the sending destination device represented by the received sending destination information, even if the authentication of the user is successful, the document is not allowed to be processed by the own device, i.e., the sending destination device, but a command for the user to process the document is allowed to be given to the processing device.

[0015] The invention described in Scheme 9 is characterized in that, in the information processing system described in Scheme 7 or 8, the processing device has a third processor, and when the third processor processes the document through the processing device in accordance with the user's command, the processed information indicating that the document is processed by the processing device is associated with the document and sent to the management device that manages the processing device.

[0016] The invention described in Scheme 10 is characterized in that, in the information processing system described in Scheme 9, the third processor further associates new identification information with the document to create a new document different from the document when the document is processed by the processing device in accordance with the user's command.

[0017] The invention described in Scheme 11 is characterized in that, in the information processing system described in Scheme 7 or 8, the processing device has a third processor, the third processor creates a protected document by performing a processing for protection on the document, the second processor does not allow the sending device to perform processing on the protected document when the authentication of the user is successful, but allows the command for the user to print the protected document to be given to the processing device, and the third processor further creates a new protected document by performing a processing for protection on the new document when the original created by printing the protected document is read by a reading device to create a new document.

[0018] The invention described in claim 12 is characterized in that, in the information processing system described in claim 11, when there is a difference between the document and the new document, the third processor creates the new protected document by performing a processing for protecting the new document.

[0019] Effects of the Invention

[0020] According to the first and seventh aspects of the present invention, it is possible to provide a system that can execute processing on a document even if the user who uses the document does not execute the processing on the document in the device used for authentication.

[0021] According to the second and eighth aspects of the present invention, it is possible to prevent a command to execute a process on a document from being given to a device other than the utilization device indicated by the user information.

[0022] According to the third aspect of the present invention, it is possible to notify the processing device that the user who has given the command to execute the process on the document has been authenticated.

[0023] According to the fourth and fifth aspects of the present invention, it is possible to prevent the user from leaking the contents of the document from the device used for authentication and to execute processing on the document.

[0024] According to the sixth aspect of the present invention, it is possible to print a document while preventing the contents of the document from being leaked from a device used for user authentication.

[0025] According to the ninth aspect of the present invention, it is possible to manage whether a process has been performed on a document.

[0026] According to the tenth aspect of the present invention, it is possible to distinguish and manage documents that have not yet been processed and documents that have been processed.

[0027] According to the eleventh and twelfth aspects of the present invention, a new document created by reading a manuscript and a document used for creating the manuscript can be managed separately. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] Embodiments of the present invention will be described in detail with reference to the following drawings.

[0029] Figure 1 is a diagram showing an example of the structure of a document management system;

[0030] Figure 2 It is a diagram showing an example of the hardware configuration of each of a creation terminal, a processing device, and a utilization terminal;

[0031] Figure 3 is a diagram illustrating the data content of metadata;

[0032] Figure 4 is a diagram illustrating the content of data managed by the user ID server;

[0033] Figure 5 is a diagram illustrating the content of data managed by the DID server;

[0034] Figure 6 is a diagram illustrating the content of data managed by the processing device management server;

[0035] Figure 7 is a diagram illustrating the structure of a processing device and the data contents of the processing device;

[0036] Figure 8 This is a diagram showing an example of a system configuration in which a management system within an organization is provided.

[0037] Explanation of symbols

[0038] 100-local system, 102-create terminal, 104-use terminal, 110-processing device, 150-management system within the organization, 152-local user ID server, 154-local DID server, 156-local metadata server, 200-management system, 210-user ID server, 220-DID server, 230-metadata server, 240-processing device management server. DETAILED DESCRIPTION

[0039] exist Figure 1 The schematic structure of one embodiment of an information processing system, namely a document management system, is shown in FIG. Figure 1 The document management system shown is the same system as the document management system proposed by the applicant (for example, the systems exemplified in Japanese Patent Application Publication Nos. 2018-156409, 2018-156410, 2018-156411, and 2018-156383).

[0040] The document management system of this embodiment provides an environment in which electronic documents can be used safely, and aims to reduce the risk of document information leakage. Here, a document is content data that can be circulated as a unit (for example, a file), and there is no particular limitation on the type of data. For example, the concept of a document includes text data, document data created by word processing software, spreadsheet data created by spreadsheet software, CAD (Computer Aided Design) data, image data, dynamic image data, audio data, multimedia data, page data displayed by a web browser, and various data created / edited / viewed on other PCs and becoming print objects.

[0041] The document management system includes a plurality of local systems 100 and a management system 200 for managing these local systems (particularly, managing a processing system described later). The management system 200 can communicate with each local system 100 via a wide area network 10 such as the Internet.

[0042] The local system 100 includes one or more creation terminals 102, one or more use terminals 104, and a processing device 110 connected to a local network 108. The local network 108 is set in a private network (for example, configured as a LAN) within an organization such as an enterprise, and is protected from the wide area network 10 by a firewall or the like. Basically, one processing device 110 is set in the local system 100. When the private network within the organization is a large-scale network, each network segment constituting the private network may be set as a local system 100, and one processing device 110 may be set in each of these local systems 100. For example, a network segment in an office of each department of a certain company becomes a local system 100 of each department, and one processing device 110 is set in the segment. In this example, a local system 100 with a processing device 110 as the core is formed for each company or each department of each company, and is managed by a management system 200 in which each of these processing devices 110 is located in the center.

[0043] The creation terminal 102 is a terminal for creating documents, for example, a desktop or notebook personal computer, a workstation, a tablet terminal, a smart phone, a multifunction machine, a scanner, a fax machine, and a digital camera. Applications for creating and editing documents are installed in the creation terminal 102. In addition, software for requesting the document management system to transmit the created document is installed in the creation terminal 102. As a form of the software, it is conceivable to install it as a device driver that exchanges information with the processing device 110 described later or install it based on a Web application. The creation terminal 102 is equivalent to an example of a sending end device.

[0044] As an example, the processing device 110 performs a protection process of converting a document created by the creation terminal 102 into a protected document (hereinafter also referred to as an "eDoc file") in a manner used in a secure environment provided by the document management system of this embodiment. The protection process is also referred to as a process of encoding an original document into an eDoc file, and in this sense, the processing device 110 is an encoder. In this protection process, the document is converted into data in a special format designed for the system of this embodiment, and encrypted in a manner that can be decoded only by a user designated as the destination of the document. Either the format conversion or the encryption may be performed first.

[0045] The above-mentioned protection processing is only an example of the processing performed by the processing device 110, and the processing device 110 may also perform processing other than the protection processing on the original document created by the creation terminal 102. That is, the protected document is an example of a processed document generated by the processing device 110 performing processing on the original document, and the protection processing is only an example of the processing. For example, the processing device 110 may generate a document whose format is converted by performing a format conversion processing on the original document without performing an encryption processing, or may generate an encrypted document by performing an encryption processing on the original document without performing a format conversion processing. The document generated in this way is also equivalent to an example of a processed document generated by the processing based on the processing device 110. As an example, the following describes an example of generating an eDoc file through the protection processing and using the eDoc file, but the file used in this embodiment is not limited to the eDoc file, and may also be a document other than the eDoc file generated by performing processing other than the protection processing. As described later, for example, the eDoc file is a document that becomes a printing object, but a document other than the eDoc file generated by performing processing other than the protection processing may also become a printing object.

[0046] The processing device 110 may also perform processing such as printing on the protected document. For example, if a user issues a command to print a protected document using the terminal 104, the processing device 110 prints the protected document to be printed according to the printing command. In addition, processing such as printing may also be performed by a device other than the processing device 110.

[0047] Furthermore, the processing device 110 creates metadata of the protected document and registers the created metadata in the upper system, that is, the management system 200. The metadata includes bibliographic items of the protected document, information of the transmission destination, and key information for decrypting the encryption of the protected document at each transmission destination, etc. The metadata includes a plurality of items, and data addition / editing / updating is performed by the corresponding device or user according to the function provided by the service.

[0048] For example, a user who has executed a command to register a document in the document management system specifies some of these items, and the other items are created by the processing device 110. Alternatively, the management system 200 or the terminal 104 may set values ​​for some items in the metadata.

[0049] As an example, the processing device 110 may send the generated protected document (eDoc file) to the user terminal 104 of the transmission destination specified by the user. When a document other than the eDoc file is generated by performing a process other than the protection process, the document may be sent to the user terminal 104. Instead of sending the protected document to the user terminal 104 of the transmission destination, the processing device 110 may send information prompting the user to authenticate the user for granting a command to execute a process such as printing on the protected document to the user terminal 104 of the transmission destination.

[0050] The protected document, i.e., the eDoc file, is a file that is an original document converted into a special format and encrypted, and is also called the body of the eDoc. In order to print the eDoc file, corresponding metadata is required. The eDoc file and metadata are complete and constitute a complete protected document that can be printed. Thus, hereinafter, the set of the eDoc file and the corresponding metadata is referred to as "eDoc".

[0051] The processing device 110 may also have a built-in function of a wireless LAN access point. In this case, the user terminal 104 can communicate with the processing device 110 via the wireless LAN.

[0052] As an example, the terminal 104 is a terminal used to give a command to execute a process such as printing on a protected document (eDoc file). In the present embodiment, the terminal 104 is not allowed to execute a process such as printing, reading or editing on a protected document, and these processes or operations for processing are prohibited. The "reading" mentioned here means that the protected document is used in a manner corresponding to the information content represented by the document. For example, when the protected document has a file such as word processing data or a drawing as information content, reading means that the user reads or watches the file displayed by the terminal 104. And, when the information content represented by the protected document is audio, reading means that the user listens to the audio played by the terminal 104. In addition, the name of the protected document, etc. can also be displayed in the terminal 104. The terminal 104 is equivalent to an example of an information processing device or a sending device. In addition, when a document other than an eDoc file is generated by performing a process other than a protection process, the terminal 104 is used to give a command to execute a process such as printing on the document.

[0053] In addition, in this embodiment, as an example, an authentication device 130 carried by a user is used as a tool for authenticating a user who uses the document management system of this embodiment. The authentication device 130 is a device such as an IC card that has built-in identification information inherent to the user carrying the device and performs data processing for user authentication in response to a request from an external device. The authentication device 130 may also be a mobile terminal such as a smart phone that has built-in functions similar to those of such an IC card for personal authentication. The utilization terminal 104 or the creation terminal 102 has a function of communicating with the authentication device 130 using a wireless communication protocol such as NFC (Near Field Communication). The utilization terminal 104 or the creation terminal 102 exchanges information for user authentication with the authentication device 130 according to a prescribed protocol, and authenticates the user carrying the authentication device 130. Alternatively, the following method may be used, that is, the actual user authentication is performed by the server side of the document management system of this embodiment such as the processing device 110 or the management system 200, and the utilization terminal 104 or the creation terminal 102 mediates the data transmission between the server side and the authentication device 130. Furthermore, the function of the authentication device 130 built into the terminal 104 or the creation terminal 102 may also be utilized.

[0054] The management system 200 manages the processing devices 110 in each local system 100. Furthermore, the management system 200 manages metadata of protected documents generated by each of the processing devices 110, and provides the metadata to the use terminal 104 upon request. The management system 200 is composed of one computer or a plurality of computers that can communicate with each other, and has the functions of a user ID server 210, a DID server 220, a metadata server 230, and a processing device management server 240.

[0055] The user ID server 210 is a server for managing information of each user using the document management system. There are two levels of users using the document management system. One is the contractor who has signed a contract with the operator of this system for the use of the document management system, and the other is the general user who actually uses the system and performs document registration under the contract. For example, assuming that a company is the contractor, a processing device 110 is set in the local network 108 of the company, and the employees of the company often use the document management system as general users via the processing device 110. The user ID server 210 maintains and manages information about each of the contractor and the general user.

[0056] The DID server 220 manages the identification information (ID) of the protected document, namely the DID (document ID). The device that actually assigns the DID to the protected document is the processing device 110 that created the protected document, but the DID server 220 assigns the DID issuance authority and issuance framework (issued quantity) to the processing device 110. Under the issuance authority and issuance framework, the processing device 110 receives and records the report of the actually issued DID. In this way, the DID server 220 suppresses the generation of improper DIDs and can detect documents with improper DIDs.

[0057] The metadata server 230 stores and manages metadata of the protected document (eDoc file) generated by the processing device 110. When a user requests metadata of the protected document via the use terminal 104, the metadata server 230 provides the metadata to the use terminal 104 as long as the user is a legitimate user. The fact that the user who requests metadata is a "legitimate user" for the metadata server 230 means that the combination of the user and the use terminal 104 used by the user when making the request matches the combination of the destination user and the use terminal 104 of the destination indicated by the destination information (details will be described later) in the metadata stored by the metadata server 230 in association with the DID of the eDoc file (which is included in the request).

[0058] The processing device management server 240 is a server that manages the status of each processing device 110 .

[0059] Below, reference Figure 2 The hardware structures of the creation terminal 102, the processing device 110 and the utilization terminal 104 are described respectively. Figure 2 An example of their hardware configuration is shown in FIG.

[0060] The creation terminal 102 includes, for example, a communication device 102a, a UI 102b, a memory 102c, and a processor 102d.

[0061] The communication device 102a is a communication interface (eg, a network interface) having a communication chip or the like, and has a function of sending data to other devices or systems and a function of receiving data sent from other devices or systems.

[0062] UI102b is a user interface and includes at least one of a display device and an operating device. The display device is a liquid crystal display or an EL display, etc. The operating device is a keyboard or an input key or an operating panel, etc. UI102b can also be a UI such as a touch panel that has both a display device and an operating device.

[0063] The memory 102c is a device that constitutes one or more storage areas for storing data, and is, for example, a hard disk drive, various memories (such as RAM, DRAM, or ROM), and other storage devices (such as optical disks), or a combination thereof.

[0064] The processor 102d is configured to control the operation of each unit of the creation terminal 102. The processor 102d may include a memory. The functions of the creation terminal 102 are implemented by the processor 102d. The processor 102d corresponds to an example of the first processor.

[0065] The processing device 110 , for example, includes a communication device 110 a , a UI 110 b , a memory 110 c , and a processor 110 d .

[0066] The communication device 110a is a communication interface (eg, a network interface) having a communication chip or the like, and has a function of sending data to other devices or systems and a function of receiving data sent from other devices or systems.

[0067] UI110b is a user interface and includes at least one of a display device and an operating device. The display device is a liquid crystal display or an EL display, etc. The operating device is a keyboard or an input key or an operating panel, etc. UI110b can also be a UI such as a touch panel that has both a display device and an operating device.

[0068] The memory 110c is a device constituting one or more storage areas for storing data, and is, for example, a hard disk drive, various memories (eg, RAM, DRAM, ROM, etc.), other storage devices (eg, optical disks, etc.), or a combination thereof.

[0069] The processor 110d is configured to control the operation of each unit of the processing device 110. The processor 110d may include a memory. The functions of the processing device 110 are implemented by the processor 110d. The processor 110d corresponds to an example of a third processor.

[0070] The terminal 104 includes, for example, a communication device 104a, a UI 104b, a memory 104c, and a processor 104d.

[0071] The communication device 104a is a communication interface (eg, a network interface) having a communication chip or the like, and has a function of sending data to other devices or systems and a function of receiving data sent from other devices or systems.

[0072] UI104b is a user interface and includes at least one of a display device and an operating device. The display device is a liquid crystal display or an EL display, etc. The operating device is a keyboard or an input key or an operating panel, etc. UI104b can also be a UI such as a touch panel that has both a display device and an operating device.

[0073] The memory 104c is a device that constitutes one or more storage areas for storing data, and is, for example, a hard disk drive, various memories (eg, RAM, DRAM, ROM, etc.), and other storage devices (eg, optical disks, etc.), or a combination thereof.

[0074] The processor 104d is configured to control the operation of each unit of the use terminal 104. The processor 104d may include a memory. The functions of the use terminal 104 are implemented by the processor 104d. The processor 104d corresponds to an example of a second processor.

[0075] Next, refer to Figure 3 An example of the data content of the metadata 300 of the eDoc will be described.

[0076] Among the items included in the metadata 300, first, "DID" is a document ID assigned by the processing device 110 that generated the eDoc, and "Document Name" is a name or title of the eDoc.

[0077] The “transmitter ID” is the user ID of the person who transmitted the eDoc, that is, the person who registered the document from the creation terminal 102 to the processing device 110 and transmitted the document via the processing device 110 (hereinafter referred to as the “transmitter”).

[0078] "Encoding date and time" is the date and time when the eDoc was created by encoding (i.e., protecting) the document from the creation terminal 102. "Processing device ID" is the identification information of the processing device that executed the protection process. "Encryption information" is information related to the encryption when the eDoc was generated, and includes the name of the encryption software used for encryption, the version of the encryption software, and key information indicating the key for decrypting (decoding) the encryption. The key information is, for example, information in which the key for decryption is encrypted with the public key of each transmission user. "Keyword information" is a list of keywords extracted from the eDoc (or original data). This keyword information is used, for example, when searching for an eDoc.

[0079] The "transmission destination information" is information indicating the user and the terminal 104 designated by the transmitter as the transmission destination of the eDoc. Figure 3 In the example of , the destination information includes the user ID of the user and the ID (identification information) of the terminal 104 to be used by the user for each user of the destination. When multiple terminals 104 are specified, the combination of the user ID of the user and the IDs of the multiple terminals 104 is included in the destination information. The destination information is an example of user information or source information.

[0080] Furthermore, as another example, when a method is adopted in which a transmission destination user can instruct the eDoc to be processed even when using any of the user terminals 104 designated as transmission destinations, the transmission destination information includes a transmission destination user ID list and a transmission destination user terminal 104 ID list. For example, as candidates for the transmission destination user terminal 104, a department's shared terminal or a terminal installed in a department's office or conference room is sometimes assumed. Although it is not determined which user in the organization uses a shared terminal or a terminal installed in an office, etc. (this is also a type of shared terminal), the transmitter at least knows what type of terminal it is and also knows that it is unlikely to be taken out of the organization at will, so it is qualified as a transmission destination for confidential documents. In this way, when using an eDoc in a shared terminal whose characteristics are well known, the transmission destination user can also consider a method of using any of the user terminals 104 designated as transmission destinations.

[0081] "Access right information" is information indicating the usage rights of the eDoc granted by the transmitter to the user at the transmitting location. In the present embodiment, the user at the transmitting location is permitted to print the eDoc file, but is not permitted to use the eDoc file in the terminal 104. More specifically, the user at the transmitting location is permitted to instruct the printing of the eDoc file in the terminal 104 at the transmitting location, but is not permitted to use the eDoc file as electronic data, such as for browsing or editing, in the terminal 104. Access right information is information indicating the usage rights of such content. That is, the usage rights granted to the user at the transmitting location are for printing the eDoc file, and are not granted for browsing or editing the eDoc file in the terminal 104. Access right information is information indicating that the usage rights granted to the user at the transmitting location include printing of the eDoc file, but do not include browsing or editing, etc. in the terminal 104.

[0082] The "offline validity period" is information indicating the length of the validity period of the metadata. That is, even when the user terminal 104 is in a state where the management system 200 cannot be accessed (offline state), there is metadata cached for the eDoc, and as long as it is within the "offline validity period" from the date and time when the metadata is obtained, it is permitted to use the user terminal 104 to command the execution of processing such as printing on the eDoc. On the other hand, when the offline validity period of the metadata cached for the eDoc has expired in the offline state, it is not permitted to use the user terminal 104 to command the execution of processing such as printing on the eDoc. In addition, when the user commands the execution of processing such as printing on the eDoc while the user terminal 104 can access the management system 200 (i.e., online state), the latest metadata of the eDoc is obtained from the management system 200 (especially the metadata server 230) and used.

[0083] The "original data information" is information indicating whether the original data before eDoc generation (encoding) has been saved, and if saved, information indicating the storage location of the original data (for example, URL: Uniform Resource Locator). The original data here is, for example, a document transmitted from the creation terminal 102 to the processing device 110 (before protection processing is performed) or application data that becomes the original data of the document (for example, when the document is page description language data, data of a word processing software before conversion into the data) or both.

[0084] The "document acquisition date and time" is the date and time when the file of the text data of the eDoc (i.e., the eDoc file) was acquired by the terminal 104. The "metadata acquisition date and time" is the date and time when the latest metadata currently cached for the eDoc was acquired from the management system 200 by the terminal 104. The document acquisition date and time and the metadata acquisition date and time are not included in the metadata retained in the management system 200, but are added in order to manage the metadata acquired from the management system 200 by the terminal 104 in the device itself.

[0085] And, in Figure 3 Among the metadata items shown, the DID, encoding date and time, processing device ID, encryption information, and keyword information are information generated by the processing device 110. In addition, the document name, transmitter ID, transmission destination information, access permission information, offline validity period, and original data information are derived from the document or attribute data transmitted from the creation terminal 102 to the processing device 110.

[0086] Next, data contents of information managed by the servers 210 to 250 of the management system 200 are exemplified.

[0087] First, refer to Figure 4 An example of the data content managed by the user ID server 210 will be described. In the user ID server 210, contractor data 212 of each contractor and user data 214 of each general user are registered.

[0088] The contractor data 212 includes a contractor ID, contract content information, and a user list. The contractor ID is identification information of a contractor (e.g., an organization or a department within an organization) that has signed a contract with the operator of the document management system. The user list is a list of user IDs of general users (e.g., members of the contractor's organization) that use the document management system in accordance with the contractor's contract.

[0089] The general user data 214 includes the user ID, password, user ID key information, public key certificate, established processing device ID, established terminal list and affiliation information of the general user. The user ID key information is the authentication information of the user used by the authentication device 130 of the user. The public key certificate is a digital certificate that proves the public key of the user. The established processing device ID is the ID of the processing device 110 logged in by the user. Usually, the user logs in to the processing device 110 placed in the office building to which he belongs, and the processing device 110 becomes the established processing device for the user. The established terminal list is a list of the IDs of one or more terminals mainly used by the user. The terminals included in the list become candidates for the terminals to which the user transmits eDoc. The affiliation information is information that determines the organization or department to which the user belongs, such as the contractor ID of the organization or department.

[0090] Next, refer to Figure 5 , illustrating an example of data content managed by the DID server 220.

[0091] like Figure 5 As shown, the DID server 220 stores information on each item of the issuance framework, the granting processing device, the key granting date and time, the key expiration date and time, and the issued DID list for each issuance authority key issued to the processing device 110.

[0092] The issuance authority key is key information (e.g., a randomly generated string) that the DID server 220 grants to the processing device 110 to prove the issuance authority of the DID. The processing device 110 includes the issuance authority key granted by the DID server 220 in the self-issued DID to prove that the DID was issued under the legitimate issuance authority.

[0093] The issuance framework is the upper limit of the number of DID issuances (the upper limit of the number of documents that can be assigned a DID) that is assigned to the processing device 110 together with the issuance authority key. If a pair of issuance authority keys and issuance frameworks are assigned from the DID server 220, the processing device 110 can assign a unique DID to each of the eDocs up to the upper limit indicated by the issuance framework.

[0094] The assigning location processing device indicates the ID of the assigning location processing device 110 of the issuing location of the issuing authority key (and issuing framework). The key assigning date and time is the date and time when the issuing authority key is assigned to the processing device 110. The key expiration date and time is the date and time when the issuing authority key is used up by the assigning location processing device 110. That is, it is the date and time when the processing device 110 ends assigning DIDs to the upper limit number of eDocs represented by the issuing framework assigned together with the issuing authority key. In addition, when a structure is adopted in which the processing device 110 requests the next issuing authority key and issuing framework from the DID server 220 after using up the issuing framework, instead of explicitly recording the key expiration date and time of a certain issuing authority key (referred to as the first key), the key assigning date and time of the issuing authority key assigned by the processing device 110 after the issuing authority key may be used as the key expiration date and time of the first key. The issued DID list is a list of DIDs issued by the assigning location processing device 110 using the issuing authority key and their issuing year, month and date. Each time a DID is issued using the issuance authority key, the processing device 110 at the granting location notifies the DID server 220 of the DID, and the DID server 220 adds the notified DID and its issuance date to the issued DID list corresponding to the issuance authority key included in the DID.

[0095] The metadata server 230 stores metadata of each eDoc transmitted from each processing device 110. The data content of the stored metadata is Figure 3 The contents of the examples are the same. However, Figure 3 Among the metadata items shown as examples, the metadata server 230 does not manage items (document acquisition date and time, metadata acquisition date and time, etc.) that are used only in the terminal 104 .

[0096] Next, refer to Figure 6 The data managed by the processing device management server 240 will be described. The processing device management server 240 stores the status history 242 of the processing device 110 for each processing device 110 to be managed. The status history includes information on the status 244 of the processing device 110 at the time of creation and each update (creation / update date and time) in association with the ID of the processing device 110.

[0097] The status 244 at each time point includes the installation location, contractor ID, administrator name, administrator contact information, logged-in user list, software information 246, hardware information 248, disk free capacity, and security certificate information. The installation location is information indicating the installation location of the processing device 110, for example, including information such as the address, building name, and floor number. The contractor ID is the ID of the contractor who is using the processing device 110. The administrator name is the name of the administrator of the processing device 110. The administrator is a user who manages the processing device 110 in the department where the processing device 110 is installed. The administrator contact information is information on the administrator's contact information (for example, an email address). The logged-in user list is a list of user IDs of users who have logged into the processing device 110 (in other words, users who regard the processing device 110 as a "predetermined processing device").

[0098] The software information 246 includes the name of the encoding software, the version of the encoding software, the name of the encryption software, the version of the encryption software, and the names and versions of other software installed in the processing device 110. Here, the encoding software is software that converts (encodes) a document input from the creation terminal 102 into a dedicated format for the document management system. The encryption software is software that encrypts a document (e.g., a document converted into a dedicated format).

[0099] The hardware information 248 includes items such as encoding circuit information, encoding circuit FW version, and the manufacturer name of the processing device 110. The encoding circuit information is information indicating the model of the hardware circuit used for encoding processing. The encoding circuit FW version is the version of the firmware (FW) of the encoding circuit.

[0100] The disk free capacity refers to the free capacity of a secondary storage device such as a hard disk or a solid state disk of the processing device 110 at that point in time.

[0101] The security certificate information is information that identifies each security certificate installed in the processing device 110 at that point in time (for example, information such as the subject identifier, issuer identifier, and issue date of the certificate).

[0102] Furthermore, although the illustration is omitted to avoid complexity, status 244 includes the types of fonts installed in processing device 110 (a list of font names), an address for network communication (e.g., an IP address), a device ID of a mounted secondary storage device (such as a hard disk drive), information indicating the customized contents for connecting processing device 110 to a processing backbone system of an organization where the processing device 110 is installed, and the installation date and time of an encryption key (used for communication path encryption or signing, etc.) used by processing device 110.

[0103] Next, refer to Figure 7The following describes a database group held by the processing device 110. As shown in the figure, the processing device 110 includes a management information storage unit 112, a user DB 114, and a document DB 116.

[0104] Management information 112a is stored in the management information storage unit 112. The management information 112a includes items such as host device address information, security certificates, encryption keys, encoding software names, encoding software versions, encryption software names and encryption software versions. The host device address information is information about the communication addresses (for example, IP addresses, URLs, etc.) of the host devices that manage the processing device 110. The management system 200 and the servers 210 to 240 therein or the management system 150 within the organization described later and the servers 152 to 156 therein are examples of host devices. The security certificate is a digital certificate used when the processing device 110 communicates securely with other devices on the network based on a public key infrastructure. The processing device 110 maintains security certificates for each host device with which it frequently communicates. In addition, the security certificates of each user who creates the terminal 102 or uses the terminal 104 may also be maintained. The encryption key is an encryption key of the processing device 110 used for the purpose of encryption or decoding when the processing device 110 communicates with other devices on the network, or generating a digital signature based on the processing device 110 (or similar certification information), and is, for example, a pair of a secret key and a public key assigned to the processing device 110 in a public key infrastructure. The encoding software and the encryption software are software installed in the processing device 110 for performing user encoding (conversion to a dedicated format) and encryption, respectively.

[0105] The user DB 114 stores user information 114a of each user who has logged into the processing device 110 (in other words, a user who regards the processing device 110 as a "predetermined processing device"). The user information 114a of each logged-in user includes items such as a user ID, a password, user ID key information, a public key certificate, and a list of predetermined terminals. These items are described in detail in the description of the data held by the user ID server 210 (see Figure 4 ) was explained.

[0106] The document DB 116 stores the eDoc file generated by the processing device 110 and metadata corresponding to the eDoc file. The eDoc file and metadata contain information about the DID, so a corresponding association can be established. In addition, the original data before encoding the eDoc (data received from the creation terminal 102) can also be associated with the DID of the eDoc and registered in the document DB 116.

[0107] The creation terminal 102 and the use terminal 104 store the user's authentication information (user ID, password, etc.), the ID of a predetermined processing device, the address information of a predetermined processing device, the address information of a host device (for example, the management system 200 or the management system 150 within the organization described later), the security certificate of the processing device or the host device, and the encryption key used for communication path encryption, etc., according to each user who uses the terminal.

[0108] <System Processing Flow>

[0109] When the processing device 110 is installed on the local network 108, the maintenance personnel who perform maintenance of the processing device 110 register the information of the users who use the processing device 110 and the information of the creation terminals 102 or the use terminals 104 that may be used by these users to the processing device 110. The registered user information is also transmitted and registered to the upper device, that is, the user ID server 210 (or the local user ID server 152 described later). In addition, when the number of users who use the processing device 110 increases or decreases after the installation, the maintenance personnel performs the work of newly registering the information of the added users to the processing device 110 or deleting the information of the decreased users. Such addition or deletion is also notified to the upper device such as the user ID server 210, and the information retained by the upper device is updated accordingly. In addition, the maintenance personnel installs software for processing the registration and transmission of the request document to the processing device 110 on each of these creation terminals 102 (for example, it is set to a state where the device driver of the processing device 110 is used). Furthermore, the maintenance personnel registers information (for example, device name, communication address, wireless access setting) and the like for communicating with the processing device 110 in each utilization terminal 104 .

[0110] Hereinafter, the flow of processing by the document management system according to the present embodiment will be described.

[0111] (0) The DID server 220 grants the right to issue DID (document ID) and the accompanying issuance framework (number of documents) to the processing device 110 in the local system 100 in advance. The right to issue DID is not unlimited, but is limited by the issuance framework of the management system 200. In other words, as long as the number of documents is up to the number indicated by the issuance framework granted by the management system 200, the processing device 110 can grant DID according to the issuance right granted at the same time. If the issuance framework is used up, the processing device 110 receives a new issuance right and issuance framework from the management system 200.

[0112] (1) When a document is to be registered in the document management system of this embodiment (i.e., to be transmitted), the user instructs the creation terminal 102 to register the document (e.g., by commanding "Login" on the menu of the application). The creation terminal 102, which has received the command, requests user authentication. The authentication can be performed by inputting a user ID and a password, or by the user placing the authentication device 130 close to the card reader of the creation terminal 102. The user authentication can be performed by the creation terminal 102 or by the processing device 110, which is the registration point of the document. Then, the user selects a document to be registered in the document management system from the documents stored in the creation terminal 102 and instructs the registration.

[0113] When receiving a document registration command from the user, the creation terminal 102 (more specifically, a registration processing program installed in the creation terminal 102) receives input of an item (e.g., a document delivery destination) that the user needs to specify in the attribute data of the document. Here, the designation of a combination of the user and the use terminal 104 may be received as the delivery destination. In this case, when the combination of the user and the use terminal 104 used by the user matches the combination designated as the delivery destination, the user is allowed to instruct to execute processing such as printing on the document.

[0114] (2) The creation terminal 102 sends attribute data that combines attribute items such as the destination input by the user and other attribute items (e.g., information of the registrant, creation date and time, etc.) generated by the creation terminal 102 itself, together with the data of the document, to the processing device 110. The attribute data includes access permission information indicating that the user of the destination is granted the use permission to print the eDoc file but is not granted the use permission to view or edit the eDoc file in the user's terminal 104. In addition, the creation terminal 102 may also have a driver that converts documents of various formats created by various applications into a unified format that can be used on the side of the terminal 104. For example, in the case of data representing a static document image such as word processing data, electronic spreadsheet, and CAD data, the driver converts the data into a document expressed in a page description language in the same manner as a printer driver. And, for example, when the original data is audio data, the driver converts the audio data into data (document) in a specific audio data format corresponding to the document management system (especially the terminal 104) of this embodiment.

[0115] (3) The processing device 110 receives the document of the registration target transmitted from the creation terminal 102 .

[0116] (4) The processing device 110 generates a protected document (eDoc file) by performing protection processing on the document of the login object received from the creation terminal 102. In this generation, the eDoc file is generated by encoding the received document into a dedicated format of the document management system of this embodiment, and encrypting the encoded data using the generated encryption key. The order of encoding and encryption can be interchanged. In addition, the processing device 110 assigns a unique DID to the eDoc file. The DID includes information that proves that it is based on the issuance authority received from the management system 200 (for example, the issuance authority key) and information that proves that it is assigned by the processing device 110 itself (for example, the issuance certification key). The generated DID is incorporated into the eDoc file (for example, as an item of the attribute of the file).

[0117] Furthermore, the processing device 110 generates metadata corresponding to the generated eDoc file. The metadata includes the attribute data received from the creation terminal 102 together with the document and the values ​​of the attribute items (e.g., DID, the ID of the processing device itself, encoding date and time, encryption key information) generated by the processing device 110 itself. The attribute data includes access permission information, so the metadata includes access permission information. The encryption key information included in the metadata is information indicating the key used to decrypt the eDoc file. When a shared key method is used in encryption, the encryption key information is information indicating the shared key. However, if the shared key itself is included in the metadata in plain text format, there is a concern that it may be abused due to eavesdropping or monitoring, so the key encrypted by using the public key of the user at the transmission site is included in the metadata as encryption key information.

[0118] Furthermore, the processing device 110 stores the generated eDoc file and metadata in a built-in database.

[0119] (5) The processing device 110 sends the previously generated DID to the DID server 220. The DID server 220 stores the DID sent from the processing device 110. Furthermore, the processing device 110 sends the generated metadata to the metadata server 230 and registers it. The metadata server 230 stores the received metadata.

[0120] (6) The processing device 110 transmits the generated eDoc file to the user terminal 104 designated as the transmission destination. The transmission may be push-based, pull-based, or both (for example, push-based when the eDoc is created, and the user terminal 104 that is not in operation and does not receive the file receives the file in pull-based mode). The transmission is performed via the local network 108 within the local system 100. For example, the processing device 110 sends a transmission preparation completion notification regarding the generated eDoc to the user terminal 104 designated as the transmission destination. The notification includes information on the previously generated DID and the document name of the eDoc.

[0121] (7) The eDoc file transmitted from the processing device 110 is received by the terminal 104 .

[0122] (8) The eDoc file received by the user terminal 104 cannot be processed by the user terminal 104. For example, the eDoc file cannot be viewed, edited, or printed by the user terminal 104. For example, the name of the eDoc file is displayed on the user terminal 104, but the content of the eDoc file is not displayed on the user terminal 104. In other words, the eDoc file cannot be opened in the user terminal 104. In this way, the user terminal 104 prohibits the viewing and editing of the eDoc file in its own device.

[0123] As another example, the processing device 110 may transmit information for prompting the user at the transmission destination to grant a command to print the eDoc file to the user terminal 104 designated as the transmission destination, instead of transmitting the generated eDoc file to the user terminal 104 designated as the transmission destination. For example, the processing device 110 transmits information indicating that an eDoc file that can be printed according to the command of the user at the transmission destination has been generated to the user terminal 104. Furthermore, the processing device 110 may transmit the name, title, DID, etc. of the generated eDoc file to the user terminal 104. The user terminal 104 receives and displays this information. For example, the name of the eDoc file that can be printed according to the command of the user at the transmission destination is displayed on the user terminal 104.

[0124] When the user wants to use the terminal 104 to instruct the eDoc file to be printed or processed, the user places his authentication device 130 close to the card reader of the terminal 104 to receive user authentication, and then instructs the eDoc file to be printed or processed. For example, the terminal 104 displays a list screen, which displays a list of eDoc files transmitted to its own device. The list screen displays, for example, the names of the eDoc files. The user specifies the eDoc file to be processed on the list screen and instructs the execution of the processing. The terminal 104 that has received the execution command accesses the management system 200 and requests the metadata of the eDoc file. The request includes the DID of the eDoc file.

[0125] (9) The metadata server 230 transmits the latest metadata of the eDoc file requested by the user terminal 104 to the user terminal 104 .

[0126] (10) When the requested metadata is received from the management system 200, the terminal 104 determines whether the destination information included in the metadata includes a combination of the terminal 104 and the user currently using the terminal 104 (i.e., the user authenticated by the authentication device 130). When the destination information includes the combination, the authentication of the user of the eDoc file is successful. In this case, the user uses the terminal 104 and is permitted to use the eDoc file according to the access rights indicated by the access rights information included in the metadata. As described above, the access rights information is information indicating that the user of the destination is granted the access rights to print the eDoc file but is not granted the access rights to browse or edit the eDoc file in the terminal 104. Therefore, the user has the right to use the terminal 104 to issue a command to print the eDoc file, but does not have the right to browse or edit the eDoc file. The terminal 104 sends the command information indicating the command to print the eDoc file and the information indicating the successful authentication of the user to the processing device 110. When user authentication succeeds, the user is allowed to issue a command to print the eDoc file to a processing device 110 different from the use terminal 104. The information indicating that user authentication succeeds is information indicating that the user who is using the use terminal 104 is allowed to issue a command to print the eDoc file to a processing device 110 different from the use terminal 104. The command information includes the DID of the eDoc file to be processed such as printing. The access right information indicates that the user at the transmission destination does not have the authority to read or edit the eDoc file, so even if the user authentication succeeds, the content of the eDoc file is not displayed on the use terminal 104, and the user cannot read or edit the content of the eDoc file in the use terminal 104. When the transmission destination information does not include this combination, the user does not have the authority to use the use terminal 104 to issue a command to print the eDoc file, so the use terminal 104 does not send the command information and the information indicating that the user authentication succeeds to the processing device 110, and displays an error message indicating that the user does not have the authority to execute the command.

[0127] (11) If command information and information indicating successful user authentication are received from the user terminal 104, the processing device 110 performs processing on the eDoc file having the DID included in the command information. For example, the processing device 110 uses the encryption key information included in the metadata to decode and print the eDoc file. The processing device 110 may also send the eDoc file to a printing device other than the processing device 110 to cause the printing device to print the eDoc file. For example, the processing device 110 may send the eDoc file to a printing device that is located closest to the user terminal 104, or may send the eDoc file to a pre-set printing device. Furthermore, when the printing of the eDoc file is completed, the processing device 110 may also send information indicating the completion of printing of the eDoc file to the user terminal 104 that issued the command for the printing. In this case, information indicating the completion of printing of the eDoc file is displayed on the user terminal 104.

[0128] When the eDoc file has been sent to the user terminal 104, the user terminal 104 may send the command information, the information indicating that the user authentication is successful, and the eDoc file to the processing device 110. In this case, the processing device 110 prints the eDoc file. When the eDoc file has not been sent to the user terminal 104, the processing device 110 prints the eDoc file that has the DID of the eDoc file to be printed and is stored in the processing device 110. Even when the eDoc file has been sent to the user terminal 104, the processing device 110 may print the eDoc file stored in the processing device 110.

[0129] In addition, when the user who has successfully authenticated specifies the processing device 110 for printing, the command information and the information indicating that the user authentication is successful are sent to the specified processing device 110. When the eDoc file is stored in the processing device 110, the processing device 110 prints the eDoc file. When the eDoc file is not stored in the processing device 110, the processing device 110 obtains the eDoc file from the processing device 110 storing the eDoc file and prints it. When the eDoc file has been transmitted to the utilization terminal 104, the eDoc file can also be sent from the utilization terminal 104 to the processing device 110 for printing, and the processing device 110 prints the eDoc file.

[0130] (12) When the processing device 110 performs a process such as printing on the eDoc file, the processing device 110 associates the processed information indicating that the eDoc file is processed by the processing device 110 with the eDoc file and transmits the processed information to the DID server 220. Specifically, the processing device 110 associates the DID of the eDoc file on which the process such as printing is performed with the processed information and transmits the information to the DID server 220. The DID server 220 associates the DID with the processed information and stores and manages the information. Thus, the eDoc file having the DID is managed to be printed.

[0131] Figure 1 The document management system described in the document management system has a hierarchical structure of two levels, namely, the processing device 110 group and the management system 200. However, it is also possible to set the system to have three or more levels by inserting a new management system level. Figure 8 A three-level system is illustrated in FIG.

[0132] exist Figure 8 In the example shown, a plurality of local systems 100 exist in an intra-organization network, which is a private network of an organization such as a company. In addition, an intra-organization management system 150 is provided in the intra-organization network. The intra-organization management system 150 manages processes within the organization or information required for the processes in the document management system. That is, the management system 200 is operated by a service provider of the document management system and manages information or processes related to a plurality of organizations using the document management system, whereas the intra-organization management system 150 manages the part of the information or processes related to the organization under the management of the management system 200.

[0133] The in-organization management system 150 includes a local user ID server 152 , a local DID server 154 , and a local metadata server 156 .

[0134] The local user ID server 152 manages the information of users who log in to the document management system among the members of the organization. The information of each user maintained by the local user ID server 152 is Figure 4The information of the general user maintained by the user ID server 210 described in . If a user who uses the processing device 110 (i.e., a user who regards the processing device 110 as a "predetermined processing device") logs in to the processing device 110, the processing device 110 transmits the information of the logged-in user to the local user ID server 152 in the organization. The local user ID server 152 stores the received user information and transmits it to the user ID server 210 of the central management system 200 via the wide area network 10. The user ID server 210 stores the received user information. In addition, when the information of the user logged in to the processing device 110 is changed, the administrator or the like changes the information of the user to the processing device 110. The processing device 110 sends the information of the changed content of the user information (for example, including the user ID, the name of the item of the changed information item, and the changed value of the item) to the local user ID server 152, and the local user ID server 152 changes the information of the user stored by itself according to the received changed content. Furthermore, the local user ID server 152 transmits the received information of the changed content to the central user ID server 210, and the user ID server 210 changes the information of the user maintained by itself according to the transmitted information.

[0135] The local DID server 154 receives and stores the DIDs issued by the processing devices 110 in each local system 100 belonging to the organization's intra-organization network. Figure 5 The local DID server 154 transmits the DID information received from the processing device 110 to the central DID server 220, and the DID server 220 stores the information. The local DID server 154 is granted the DID issuance authority and issuance framework from the central DID server 220, and within the scope of the issuance framework, the local DID server 154 grants the DID issuance authority and issuance framework to each processing device 110 under management according to the issuance authority.

[0136] The local metadata server 156 receives and stores metadata of eDoc generated by the processing device 110 in each local system 100 belonging to the intra-organization network of the organization. The information stored in the local metadata server 156 is the same as the information stored in the metadata server 230. In addition, the local metadata server 156 transmits the metadata received from the processing device 110 to the central metadata server 230, and the metadata server 230 stores the metadata.

[0137] exist Figure 8In the document management system described in , the user cannot browse the contents of the eDoc file in the terminal 104 , but when the user authentication succeeds in the terminal 104 , the user is allowed to give a command to the processing device 110 to execute processing such as printing on the eDoc file.

[0138] In the above embodiment, a document created by the creation terminal 102 is printed, but an eDoc stored in the processing device 110 may be printed. The flow of this process will be described in detail below.

[0139] First, when the user wants to use the terminal 104 to instruct the eDoc file to be processed, such as printing, the user places his authentication device 130 close to the card reader of the terminal 104 to receive user authentication, and then instructs the eDoc file to be processed. For example, the terminal 104 displays a list screen, which displays a list of eDoc files stored in the processing device 110. The list screen displays, for example, the name of the eDoc file. The user specifies the eDoc file to be processed on the list screen and instructs the execution of the processing. Figure 1 In the system described in , the user terminal 104 that has received the execution command accesses the management system 200 and requests the metadata of the eDoc. The request includes the DID of the eDoc. Figure 8 In the system described in , the terminal 104 is used to access the management system 150 within the organization and request the metadata of the eDoc.

[0140] exist Figure 1 In the described system, the metadata server 230 transmits the latest metadata of the eDoc requested by the user terminal 104 to the user terminal 104. Figure 8 In the system described in , the local metadata server 156 sends the latest metadata of the requested eDoc to the user terminal 104 .

[0141] If the requested metadata is received from the metadata server 230 or the local metadata server 156, the terminal 104 determines whether the transmission source information contained in the metadata includes the combination of the terminal 104 and the user currently using the terminal 104 (i.e., the user authenticated by the authentication device 130).

[0142] When the transmission information includes the combination, the authentication of the user of the eDoc file is successful, and the terminal 104 sends the command information and the information indicating the successful user authentication to the processing device 110. The command information includes the DID of the eDoc file to be processed such as printing. Even if the user authentication is successful, the content of the eDoc file will not be displayed on the terminal 104, and the user cannot read the content of the eDoc file on the terminal 104. When the transmission information does not include the combination, the user does not have the authority to use the terminal 104 command to execute the eDoc file such as printing, so the terminal 104 does not send the command information and the information indicating the successful user authentication to the processing device 110, and displays an error message indicating that the user does not have the authority to execute the command.

[0143] When receiving the command information and the information indicating successful user authentication from the user terminal 104, the processing device 110 identifies the eDoc file having the DID included in the information from the eDoc file group stored in the processing device 110, and performs processing such as printing on the eDoc file. For example, the processing device 110 uses the encryption key information included in the metadata to decrypt the eDoc file and print it.

[0144] Furthermore, the processing device 110 generates a new DID for the determined eDoc file and assigns the new DID to the eDoc file, thereby generating a new eDoc file. Furthermore, the processing device 110 generates new metadata including the new DID. The content of the new eDoc file is the same as that of the determined eDoc file, but the DID and metadata are different.

[0145] exist Figure 1 In the system described in , the processing device 110 sends the generated new DID to the DID server 220, and sends the generated new metadata to the metadata server 230. Figure 8 In the system described in , the processing device 110 sends the new DID to the local DID server 154 and sends the new metadata to the local metadata server 156.

[0146] And, in Figure 1 In the system described in , the processing device 110 associates the processed information indicating that the eDoc file has been processed by the processing device 110, such as printing, with the previously generated new DID and sends the information to the DID server 220. The DID server 220 associates the new DID with the processed information and stores and manages them. Figure 8In the described system, the processing device 110 associates the new DID with the processed information and sends the information to the local DID server 154. The local DID server 154 associates the new DID with the processed information and stores and manages the information.

[0147] When the sender of the document is different from the user of the document (i.e., the user who uses the terminal 104 to instruct the execution of a process such as printing), the processing device 110 inquires the sender of the identified eDoc file whether to permit the execution of a process such as printing, and when the permission is obtained from the creator, the processing such as printing can be executed on the eDoc file. For example, the processing device 110 identifies the sender based on the sender ID included in the metadata of the eDoc file, and sends information indicating the inquiry to the creation terminal 102 used by the identified sender. When the sender is permitted to execute the process such as printing using the creation terminal 102 itself, the information indicating the permission is sent from the creation terminal 102 to the processing device 110. If the information indicating the permission is received, the processing device 110 executes the process such as printing on the eDoc file. When the sender is prohibited from executing the process such as printing using the creation terminal 102 itself, the information indicating the prohibition is sent from the creation terminal 102 to the processing device 110. If the information indicating the prohibition is received, the processing device 110 does not execute the process such as printing on the eDoc file. Furthermore, when the processing device 110 does not receive information indicating approval from the creation terminal 102 within a predetermined time after the information indicating the inquiry is transmitted to the creation terminal 102 , the processing device 110 may not execute processing such as printing on the eDoc file.

[0148] In the document management system according to the present embodiment described above, the user who uses the eDoc file does not process the eDoc file in the user terminal 104 used for authentication, so the possibility of the contents of the eDoc file being leaked to others in the user terminal 104 is reduced compared to the case where the eDoc file is processed in the user terminal 104. Furthermore, although the eDoc file is not processed in the user terminal 104, the eDoc file can be processed in the processing device 110 or other devices.

[0149] <Processing of generating a new eDoc by reading a document>

[0150] Next, the process of generating a new eDoc by reading a document will be described.

[0151] For example, the eDoc file is printed on paper. The printing may be performed by the processing device 110 or by other printing devices. Furthermore, as described in the above embodiment, the printing may be performed according to a command from a user who has successfully authenticated the user in the terminal 104, but the present invention is not limited to this example, and the printing may also be performed according to a printing command from another terminal or another user. That is, the printing here is not limited to the above embodiment, and any method or device may be used.

[0152] Hereinafter, for convenience of explanation, the paper on which the eDoc file is printed is referred to as "manuscript A." That is, the manuscript A is created by printing the eDoc file. The manuscript A is, for example, a paper document.

[0153] The contents of the eDoc file are printed on manuscript A. In addition, additional information is printed on manuscript A. The additional information includes, for example, the DID of the printed eDoc file, identification information of the device that performed the printing (for example, the processing device ID of the processing device 110 that performed the printing), the user ID of the user who ordered the printing, the user ID of the user who actually performed the printing, information indicating the date and time of the printing, and other information (for example, graphics such as watermarks, etc.). The additional information may be coded and the code (for example, a barcode or a two-dimensional code) may be printed.

[0154] Next, a new document (e.g., scanned data generated by scanning with a scanner, etc.) is generated by reading the original A with a reading device such as a scanner or a camera. The reading device may or may not be provided in the processing device 110. Hereinafter, for the sake of convenience, the new document generated by reading the original A is referred to as "document B".

[0155] In addition to the contents of the printed original eDoc file, additional information added when printing the eDoc file is displayed in Document B. Furthermore, when characters, symbols, graphics, etc. are written in Original A, information indicating the written characters, etc. is also displayed in Document B.

[0156] The processing device 110 sends the document B generated by reading the original A to the DID server 220 or the local DID server 154 .

[0157] Next, by applying character recognition processing such as OCR (Optical Character Recognition) processing to the document B, the DID of the printed original eDoc file is determined from the document B. Since the additional information appears in the document B, the DID is determined from the additional information. Furthermore, when a code such as a barcode or a two-dimensional code appears on the document B, the DID can also be read from the code. The character recognition processing can be performed by the management system 200, or by the management system 150 within the organization, or by other devices or systems.

[0158] Next, the content of the eDoc file having the determined DID and stored in the processing device 110 is compared with the content of the document B generated by reading. For example, the DID server 220 or the local DID server 154 obtains the eDoc file having the determined DID from the processing device 110, and compares the content of the obtained eDoc file with the content of the document B. At this time, the DID server 220 or the local DID server 154 decodes the obtained eDoc file, and compares the content of the document generated by the decoding with the content of the document B.

[0159] When there is a difference in the content, the DID server 220 or the local DID server 154 instructs the processing device 110 to assign a new DID to document B and encode (i.e., encrypt) document B. When there is no difference in the content, the DID server 220 or the local DID server 154 does not execute the command to the processing device 110.

[0160] The DID server 220 or the local DID server 154 can instruct to assign a new DID and execute encoding when the difference in the content is less than a preset threshold, and not execute the command when the difference in the content is greater than the threshold. When the difference is greater than the threshold, there is a possibility that the original document A is forged to generate document B, so in this case, a new DID is not assigned to document B.

[0161] Furthermore, when the original eDoc file is printed, additional information such as a watermark that is not included in the content of the eDoc file is printed on paper, so the additional information also appears in the document B generated by reading the original A generated by the printing. Since the additional information such as the watermark is pre-set information, the DID server 220 or the local DID server 154 removes the additional information such as the watermark from the document B, and compares the content of the document B with the content of the printed original eDoc file without the additional information. In this way, the documents can be compared with each other in a state without the additional information.

[0162] For example, when characters, symbols, graphics, etc. are written in document A, the written characters, etc. also appear in document B, so there is a difference between the content of document B and the content of the printed original eDoc file.

[0163] When receiving a command to assign a new DID and execute encoding from the DID server 220 or the local DID server 154, the processing device 110 encodes the document B and encrypts the encoded data, thereby generating a new eDoc file (hereinafter referred to as "eDoc file B"). In addition, the processing device 110 generates a new DID and assigns the new DID to the eDoc file B. In addition, the processing device 110 generates new metadata including the new DID.

[0164] The processing device 110 sends the DID of the eDoc file B to the DID server 220 or the local DID server 154, and sends the metadata of the eDoc file B to the metadata server 230 or the local metadata server 156. For example, the DID server 220 or the local DID server 154 associates and manages the DID of the eDoc file B with the DID determined by the character recognition process (that is, the DID of the original eDoc file printed). In this way, the new eDoc file B generated by reading the original document is associated and managed with the original eDoc file printed. In this way, for example, the association between the new eDoc file B and the original eDoc file (for example, whether there is tampering, etc.) can be confirmed.

[0165] Furthermore, the processing device 110 may include data indicating the difference between the content of the original eDoc file printed and the content of the eDoc file B (i.e., the content of document B) in the metadata of the eDoc file B. The data indicating the difference is data from which additional information added due to the difference in printing is removed. For example, when information such as characters is written in the original document A, the information written in the eDoc file B is displayed, but the information written in the original eDoc file printed is not displayed, so the data indicating the difference is data indicating information such as characters written in the original document A.

[0166] In the above-mentioned embodiments, the processor refers to a processor in a broad sense, including a general-purpose processor (for example, CPU: Central Processing Unit, etc.), a special-purpose processor (for example, GPU: Graphics Processing Unit, ASIC: Application Specific Integrated Circuit, FPGA: Field Programmable Gate Array, programmable logic device, etc.). In addition, the actions of the processor in the above-mentioned embodiments can be performed by one processor or by a plurality of processors in physically separate locations. In addition, the order of the actions of the processor is not limited to the order described in the above-mentioned embodiments, and can also be changed appropriately.

[0167] The above-mentioned embodiments of the present invention are provided for the purpose of illustration and explanation. In addition, the embodiments of the present invention do not fully and exhaustively include the present invention, and do not limit the present invention to the disclosed methods. Obviously, various modifications and changes are self-evident to the technical personnel in the field to which the present invention belongs. The present embodiment is selected and described in order to most easily understand the principles of the present invention and its application. Thus, other technical personnel in the technical field can understand the present invention by using various modified examples of optimization for the determination of the assumed various embodiments. The scope of the present invention is defined by the above claims and their equivalents.

Claims

1. An information processing device comprising a processor, The processor receives user information representing a document user and a device using the document, and when the group of the device itself and the user using the device matches the group of the user represented by the received user information and the device using the device, it is determined that the user's authentication is successful, and the user is not allowed to perform processing on the document through the device itself, but a command for the user to perform the processing on the document is allowed to be assigned to a processing device different from the device itself.

2. The information processing device according to claim 1, characterized in that The processor further sends information indicating that the user is authenticated to the processing device different from the own device when the user is authenticated.

3. The information processing device according to any one of claims 1 to 2, characterized in that: The processor further receives information for urging the user to perform user authentication without receiving the document, so as to permit the command to execute the process on the document to be given to the processing device different from the own device.

4. The information processing device according to any one of claims 1 to 2, characterized in that: The processor prohibits reading and editing of the document in its own device.

5. The information processing device according to any one of claims 1 to 2, characterized in that: When the authentication of the user succeeds, the processor does not permit the processing to be performed on the document by the own device, but permits the user's command to print the document to be given to the processing device different from the own device.

6. An information processing system comprising a transmitting device, a receiving device and a processing device, The transmitting end device comprises a first processor, The first processor specifies a destination user of the document and sends the document and destination information indicating the destination user and the destination device of the document to the processing device. The sending device has a second processor, The second processor receives the sending destination information, and when its own device, i.e., the sending destination device, matches the group of the user using its own device, i.e., the sending destination device, and the group of the sending destination user and the sending destination device represented by the received sending destination information, it determines that the authentication of the user is successful, and does not allow the user to perform processing on the document through the sending destination device, but allows the command for the user to perform the processing on the document to be given to the processing device.

7. The information processing system according to claim 6, characterized in that: The processing device comprises a third processor, When the processing device executes the processing on the document according to the user's command, the third processor associates the processed information indicating that the document is processed by the processing device with the document and transmits the processed information to the management device that manages the processing device.

8. The information processing system according to claim 7, characterized in that: The third processor further associates new identification information with the document to create a new document different from the document when the processing device executes the processing on the document in accordance with the user's command.

9. The information processing system according to claim 6, characterized in that: The processing device comprises a third processor, The third processor creates a protected document by performing a protection process on the document. When the authentication of the user succeeds, the second processor does not permit the transmission device to process the protected document, but permits the user to issue a command to print the protected document to the processing device. The third processor further creates a new protected document by performing a protection process on a new document when a manuscript created by printing the protected document is read by a reading device to create a new document.

10. The information processing system according to claim 9, characterized in that: When there is a difference between the document and the new document, the third processor creates the new protected document by performing a protection process on the new document.

Images