KR102732591B1 - Content centralization system and method for attaching content in the content centralization system - Google Patents

Abstract

Disclosed are a content centralization system capable of attaching content using a link file to reduce excessive traffic generation and control the propagation status of a specific version of content, and a content attachment method in the content centralization system. The content centralization system according to one aspect includes a central server which creates a user's folder to store and manage content; and a user terminal including an agent which displays the user's folder on a local screen and is connected to a virtual file system driver, wherein the agent includes a server synchronization unit which synchronizes the user's folder of the central server and displays it on a local screen; an event receiving unit which receives an attachment request event for specific content in the user's folder displayed on the local screen from a predetermined process through the virtual file system driver; and a link file generating unit which transmits an attachment request for the specific content to the central server and receives a response thereto, and generates a link file for the specific content based on the received response and transmits it to the predetermined process through the virtual file system driver.

Description

Content centralization system and method for attaching content in the content centralization system

The present invention relates to a content centralization system and a content attachment method in the content centralization system, and more specifically, to a content centralization system capable of attaching content using an attachment link file, and a content attachment method in the content centralization system.

A content centralization system, also known as an Enterprise Content Management (ECM) system, is a system for centrally integrating and managing various types of content, such as general documents and multimedia materials, within a company. A content centralization system implements content centralization by storing all content within a company on a central server and prohibiting storage on local disks such as users' computer hard disks and removable storage media. Through content centralization, all content created and modified by users within a company can be controlled. Therefore, external leakage or illegal use can be prevented, and the risk of content omission or loss can be reduced even when users leave the company or move to a different department.

Even if content is centralized within a company, there are cases where content is attached to in-house systems such as groupware/ERP via messenger or email, or content is directly uploaded to a website and attached. In this case, users access the central server, download content stored on the central server, and then send the downloaded content to other users by attaching it to a messenger or email, or upload it to a website and attach it. However, excessive traffic occurs in downloading/transmitting/uploading content, and since content is directly attached, it is impossible to control incorrect content attachment, which can cause security issues.

The present invention has been proposed to solve the above-described problems, and relates to a content centralization system capable of attaching content using a link file so as to reduce excessive traffic generation and control the propagation status of a specific version of content, and a content attachment method in the content centralization system.

A content centralization system according to one aspect comprises: a central server which creates a user's folder to store and manage content; and a user terminal which includes an agent which displays the user's folder on a local screen and is connected to a virtual file system driver, wherein the agent comprises: a server synchronization unit which synchronizes the user's folder of the central server and displays it on a local screen; an event receiving unit which receives an attachment request event for specific content in the user's folder displayed on the local screen from a predetermined process through the virtual file system driver; and a link file generating unit which transmits an attachment request for the specific content to the central server and receives a response thereto, and generates a link file for the specific content based on the received response and transmits it to the predetermined process through the virtual file system driver.

The above agent further includes a policy verification unit that verifies whether the attachment request event conforms to a policy, and the link file generation unit can generate the link file if the attachment request event conforms to a policy.

The above policy may include at least one of process information and URL address that can utilize the link file.

The central server, upon receiving the attachment request, can copy the original file of the specific content stored in the original storage area and store it as an attachment content in the attachment file storage area, and transmit the response including the file storage path of the attachment content to the link file generation unit.

The above link file creation unit can create the link file by including creator information including the user's information, the address of the central server, and the creation time; file information including the file storage path; and verification information based on the creator information and the file information.

The central server can receive information about the link file from the link file creation unit and record a creation log based on the file name of the link file in the log storage area based on the information about the link file.

The above agent further includes a link file processing unit that transmits the link file to the user's folder of the central server when the link file is stored in the user's folder displayed on the local screen, and the central server can convert the link file stored in the user's folder into attachment content stored in the attachment file storage area based on the file storage path included in the link file.

The central server may, after the conversion, record a conversion log based on the file name of the link file in the log storage area.

The central server may perform the conversion only when viewing is set to ON, based on the viewing ON/OFF setting information for the attached content set by the user, and delete the link file saved in the user's folder when viewing is set to OFF.

In another aspect, a method for attaching content in a content centralization system including a central server for creating a user's folder to store and manage content; and a user terminal including an agent connected to a virtual file system driver and displaying the user's folder on a local screen, the method includes: a step in which the agent synchronizes the user's folder of the central server and displays it on a local screen; a step in which the agent receives an attachment request event for specific content in the user's folder displayed on the local screen from a predetermined process through the virtual file system driver; a step in which the agent transmits an attachment request for the specific content to the central server and receives a response thereto, and creates a link file for the specific content based on the received response; and a step in which the agent transmits the link file to the predetermined process through the virtual file system driver.

The method further includes, after the step of receiving the attachment request event, a step of the agent determining whether the attachment request event conforms to a policy, and the step of generating the link file can generate the link file if the attachment request event conforms to a policy.

The above policy may include at least one of process information and URL address that can utilize the link file.

The step of generating the above link file may include receiving, from the central server, the response including the file storage path of the attached content, where the agent copies the original file of the specific content stored in the original storage area and stores it as attached content in the attachment file storage area, in response to the attachment request.

The step of generating the above link file may generate the link file including: creator information including the user's information, the address of the central server, and the creation time; file information including the file storage path; and verification information based on the creator information and the file information.

The method may further include a step in which the central server receives information of the link file from the agent and records a generation log based on the file name of the link file in a log storage area based on the information of the link file.

The method may further include a step of the agent transmitting the link file to the user's folder of the central server when the link file is stored in the user's folder displayed on the local screen; and a step of the central server converting the link file stored in the user's folder into attachment content stored in the attachment file storage area based on the file storage path included in the link file.

The above method may further include a step in which the central server records a conversion log based on the file name of the link file in a log storage area after the conversion.

The step of converting the above-mentioned link file into an attachment content stored in the above-mentioned attachment file storage area may be performed by the central server, with reference to the viewing ON/OFF setting information for the attached content set by the user, performing the conversion only when viewing ON is set, and deleting the link file stored in the user's folder when viewing OFF is set.

The present invention can significantly reduce traffic generation compared to conventional content attachment methods in a content centralization environment. A representative method of attaching and transmitting large-capacity content is to attach using a link URL. For example, when transmitting a 1GB file, the present invention can reduce traffic generation by 1/1000 compared to conventional methods using link URLs.

The present invention can prevent security issues such as external leakage of important information by centrally controlling content attachment by attaching content using a link file, and can track the propagation status of a specific version of content in real time. That is, the present invention can provide a denial prevention effect of content leakage, etc. by permanently storing content attached by a user at a specific point in time in a separate attachment file storage area, so that the content attached by the user at a specific point in time can be confirmed later when the user attaches and transmits it to another user.

FIG. 1 is a diagram illustrating a content centralization system according to one embodiment of the present invention.
FIG. 2 is a diagram showing a drive screen mounted by an agent according to one embodiment of the present invention.
Figure 3 is a diagram schematically showing the configuration of the central server and user terminal of Figure 2.
FIG. 4 is a diagram illustrating a content attachment log record according to one embodiment of the present invention.
FIG. 5 is a diagram schematically showing the configuration of an agent according to one embodiment of the present invention.
Figure 6 is a flowchart explaining a method of transmitting content via a messenger in the content centralization system of Figure 1.
Figure 7 is a flowchart explaining a method of receiving content via a messenger in the content centralization system of Figure 1.

Hereinafter, the embodiments disclosed in this specification will be described in detail with reference to the attached drawings. Regardless of the drawing symbols, identical or similar components will be given the same reference numerals and redundant descriptions thereof will be omitted. The suffix "part" used for components in the following description is assigned or used interchangeably only for the convenience of writing the specification, and does not in itself have a distinct meaning or role. In addition, when describing the embodiments disclosed in this specification, if it is determined that a specific description of a related known technology may obscure the gist of the embodiments disclosed in this specification, the detailed description thereof will be omitted. In addition, the attached drawings are only intended to facilitate easy understanding of the embodiments disclosed in this specification, and the technical ideas disclosed in this specification are not limited by the attached drawings, and should be understood to include all modifications, equivalents, and substitutes included in the spirit and technical scope of the present invention.

Singular expressions include plural expressions unless the context clearly indicates otherwise. In this application, the terms "comprises" or "have" are intended to specify the presence of a feature, number, step, operation, component, part or combination thereof described in the specification, but should be understood to not preclude the possibility of the presence or addition of one or more other features, numbers, steps, operations, components, parts or combinations thereof.

In implementing the present invention, components may be described in detail for convenience of explanation, but these components may be implemented in one device or module, or one component may be implemented by being divided into multiple devices or modules.

FIG. 1 is a diagram illustrating a content centralization system according to one embodiment of the present invention. Referring to FIG. 1, the content centralization system according to the present embodiment includes a central server (110), a user terminal (120), an attachment intermediary means (130), and a communication network (140) connecting them. Here, the communication network (140) means a connection structure in which information can be exchanged between each communication node, and may be implemented as a wired network such as a Local Area Network (LAN), a Wide Area Network (WAN), or a Value Added Network (VAN), or any type of wireless network such as a mobile radio communication network, a satellite communication network, Bluetooth, Wibro (Wireless Broadband Internet), HSDPA (High Speed Downlink Packet Access), or a combination thereof.

The central server (110) is a server that stores and manages various contents such as general documents and multimedia data within the company in a storage unit (e.g., a database). The central server (110) manages contents generated during the performance of work within the company systematically and consistently based on predefined management criteria and classification systems, performs security processing on contents (e.g., encryption after document storage), manages history/version of contents (e.g., creation/editing date/time, creator/editor information, etc.), manages collaboration between users, manages content search, and manages user profiles/authority, etc. In addition, the central server (110) may provide tools such as a document writer so that users can access and create contents such as writing documents.

The central server (110) manages content propagation through content attachment. Here, content attachment may include content transmission and reception between users within the company, or external export by users within the company. In the present embodiment, content attachment may be divided into attachment through direct transmission and reception of content files, or attachment using link files. The central server (110) may set and manage policies for these two attachment methods. The policy includes process information that can attach content using link files, and URL address information that can attach content using link files for specific processes. In the latter example, in the case of the Edge browser, only the www.naver.com address can attach content using link files. Processes or URL addresses that do not correspond to this policy are attached through direct transmission and reception of content files, not link files, or are blocked from attachment.

When a user sends content to another user using a link file, the central server (110) copies the original file of the content from the original storage area of the storage unit and stores it as attached content in the attachment file storage area, and when the user receiving the link file saves the link file in a designated folder, the central server (110) converts the link file into attached content that is copied and stored in the attachment file storage area. At this time, the central server (110) stores and manages a log of content attachment. The log record includes a creation log and a conversion log based on the link file name. This will be described in detail below.

The user terminal (120) is a terminal used by users within the company, and is, for example, a computing device such as a tablet PC, a laptop, a personal computer, or a smart phone. The user terminal (120) connects to the central server (110) via a communication network (140), synchronizes a list of contents stored in the central server (110) and the storage of the central server (110), displays them locally, and performs content creation, editing, reading, content collaboration, etc. on the central server (110).

The user terminal (120) includes an agent (121) for communicating with the central server (110). The agent (121) is installed together with a virtual file system driver in the user terminal (120), and is mounted in a specific drive form (e.g., I:W) and connected to the virtual file system driver. At this time, the virtual file system driver is installed in the kernel mode of the user terminal (120) and processes a file attachment request event of another process for a specific drive mounted by the agent (121).

The agent (121) can log in to the central server (110) using the ID/PW input by the user at the time of operation, and after the login is completed, the user's folder structure set in the central server (110) can be synchronized and displayed on the screen of the user terminal (120). FIG. 2 is a drawing showing a drive screen (e.g., InnoEcm (I:)) mounted by the agent (121) according to one embodiment of the present invention, and the agent (121) synchronizes the user's folders set in the central server (110), i.e., personal folders/backup folders/department folders, and displays them on the screen of the user terminal (120). When the user selects a specific folder on the user terminal (120), the agent (121) synchronizes the contents list in the selected folder with the central server (110) and displays them.

In one embodiment, the agent (121) may display the user's folder structure set in the central server (110) and the list of contents within the folder on the local screen of the user terminal (120) as a logical block such as a name space, without locally mounting the user's folder set in the central server (110) in the form of a drive. The name space refers to the amount of non-volatile memory formatted as logical blocks. Alternatively, the agent (121) may display the user's folder structure set in the central server (110) and the list of contents within the folder on the local screen of the user terminal (120) through a separate interface. Hereinafter, an example in which the user's folder is mounted in the form of a drive on the user terminal (120) will be described as a main embodiment.

The agent (121) processes the attachment of content stored in the central server (110) according to the user's input. Attachment of content includes transmission and reception through attachment mediation means (130), for example, a bulletin board/e-mail of a messenger server (131) or a web server (132) referring to FIG. 1. The agent (121) can attach and propagate content by attaching a link file that can identify the content rather than directly attaching the content selected by the user according to a policy received from the central server (110). This will be described in detail below.

FIG. 3 is a schematic diagram illustrating the configuration of the central server and the user terminal of FIG. 2. The central server (110) and the user terminal (120) may include a memory, a memory controller, one or more processors (CPUs), a peripheral interface, an input/output (I/O) subsystem, a camera, a display device, an input device, and a communication module. The memory may include a high-speed random access memory, and may also include one or more magnetic disk storage devices, nonvolatile memory such as a flash memory device, or other nonvolatile semiconductor memory devices. Access to the memory by other components such as the processor and the peripheral interface may be controlled by the memory controller. The components of the central server (110) and the user terminal (120) illustrated in FIG. 3 may be implemented as a program, stored in a memory, and executed by a processor, or may be implemented and operated by a combination of hardware and software.

The central server (110) includes a storage unit (111), a content management unit (112), a content attachment management unit (113), and a policy management unit (114).

The storage unit (111) may be a database, a network attached storage (NAS), etc., and may be divided into an original storage area, an attachment file storage area, and a log storage area, as illustrated in FIG. 3. The original file of the content is stored in the original storage area, and the attached file storage area stores the attached content copied from the original file of the content. In the log storage area, a log for content attachment is recorded.

FIG. 4 is a diagram illustrating a content attachment log record according to one embodiment of the present invention. Referring to FIG. 4, the content attachment log record includes, based on the link file name, a creation log of a link file, and a log (i.e., a conversion log) for receiving content using the link file. The creation log includes a creation time, a creator name, and an attachment parameter (e.g., a process name, URL information). The conversion log includes a conversion time, a converter name, and a conversion file name.

The content management unit (112) stores and manages content created and edited by each user, or content created/edited through collaboration between users. The content management unit (112) stores and manages the original files of such content in the original storage area of the storage unit (111). The content management unit (112) can create a folder structure for each user and classify and store the user's content within each folder.

The content attachment management unit (113) manages the attachment of content. When a request for attachment of specific content is received from a user's agent (121), the content attachment management unit (113) copies the original file of the specific content from the original storage area of the storage unit (111) and stores it as attached content in the attachment file storage area of the storage unit (111) and sends a response back to the agent (121). The response includes the file storage path of the attached content copied and stored in the attachment file storage area.

When the content attachment management unit (113) receives link file information for the copied and saved attached content from the agent (121) of the user attaching the content, it records a creation log in the log storage area of the storage unit (111). That is, the content attachment management unit (113) records the link file name and records the creation log of the link file based on the link file name.

The link file is not the attached content itself, but rather includes information that can identify and access the attached content, including creator information, file information, and verification information. Here, the creator information includes the creation time of the link file, the last modification time of the content, creator information (e.g., ID), the address of the central server (110), and the file storage path of the original file that is the basis of the attached content, and the file information includes the file storage path of the attached content copied from the original file, and the verification information is hash information of the creator information and the file information. The verification information is used to verify the integrity of the link file.

In this way, since the link file is composed only of information for identifying and accessing the attached content, not the attached content itself, its size is very small compared to the actual size of the attached content. For example, regardless of the size of the attached content, the link file is only about 1KB. Therefore, compared to directly attaching a large-sized attached content, the attached content can be transmitted using only the link file, which can significantly reduce traffic. In addition, since the link file is created for the attached content copied from the original file, not the original file of the attached content, even if the original file is later modified by the user, the link file is not affected at all, and the content status at the time of attachment can be maintained as is.

In one embodiment, the content attachment management unit (113) may receive ON/OFF setting information for viewing attached content from the agent (121) of the user attaching the content and record it in the log storage area. That is, the ON/OFF setting information for viewing may be recorded based on the link file name. ON/OFF for viewing indicates whether or not viewing of content is possible using the link file.

When a user who has received a link file of an attached content saves the link file in a folder of a drive mounted by the agent (121), the content attachment management unit (113) receives the link file for the attached content from the agent (121) and stores it in the original storage area of the storage unit (111) (i.e., the user's folder synchronized within the server), searches for the attached content in the attachment file storage area of the storage unit (111) based on the information of the link file, and converts the link file stored in the original storage area into attached content. Accordingly, the agent (121) of the user who receives the attached content synchronizes the attached content stored in the original storage area of the storage unit (111) and displays it on the user terminal (120), and the user can view, edit, etc. the attached content.

The content attachment management unit (113) converts a link file stored in the original storage area into an attachment content, and then records a conversion log in the log storage area of the storage unit (111). The content attachment management unit (113) searches for a log record based on the link file name in the log storage area and adds a conversion log. The conversion log includes the conversion time, converter name, and changed file name.

In one embodiment, the content attachment management unit (113) refers to the ON/OFF setting information for viewing in the log storage area of the storage unit (111) based on the information of the link file received from the agent (121) of the user who received the link file of the attached content, and only when viewing ON is set, searches for the attached content in the attachment file storage area and converts the link file stored in the original storage area, and when viewing OFF, does not convert the link file and maintains it as is or deletes it to block viewing of the attached content.

The policy management unit (114) sets and manages a policy for content attachment using a link file. Here, the policy includes process information that can attach content using a link file, and URL address information that can attach content to a specific process. Processes or URL addresses that do not correspond to this policy are directly attached to content files, not link files, and are transmitted and received, or content attachment is blocked. The policy management unit (114) transmits the policy to the agent (121) of the user terminal (120).

The user terminal (120) includes an operating system. The operating system is software that controls hardware, manages computer resources, assists in the execution of application programs, and acts as an intermediary between the user and the hardware. The operation mode in this operating system is divided into the operation of the user mode and the operation of the kernel mode for the convenience and stability of the user interface.

In user mode, users perform general tasks for using the computer environment (e.g., working on documents, using the Internet, searching for files, attaching files, etc.), and it provides an environment where various services or applications can request the system area that manages hardware resources. In user mode, users cannot directly use hardware, and can request the kernel mode to perform the actions they want to perform through an interface such as an API provided by the operating system.

Referring to FIG. 3, applications such as an agent (121), a messenger (122), and a web browser (123) are installed in the user mode, and when the agent (121) is installed, a virtual file system driver (124) for the agent (121) is also installed in the kernel mode. When the agent (121) is installed, the agent (121) is mounted in a specific drive format (e.g., I:W) in the user terminal (120) and connected to the virtual file system driver. Applications such as a messenger (122) and a web browser (123) in the user mode in the user terminal (120) access the drive mounted by the agent (121) through the virtual file system driver (124).

Figure 5 is a diagram showing a schematic configuration of an agent according to one embodiment of the present invention. Referring to Figure 5, the agent (121) includes a server synchronization unit (510), an event receiving unit (520), a policy verification unit (530), a link file generation unit (540), and a link file processing unit (550).

The server synchronization unit (510) communicates with the central server (110) via the communication network (140) to synchronize the user's folder in the central server (110) with the folder of the drive mounted by the agent (121). For example, when the user creates a new folder in the drive mounted by the agent (121), the same folder is also created in the central server (110), and when a file is saved in the folder of the central server (110), the same file is also displayed in the user terminal (120). At this time, the actual file is saved in the central server (110) and the actual file is not saved in the user terminal (120).

The event receiving unit (520) can receive an attachment request event for content stored in the mounted drive through the virtual file system driver (124). For example, when a user sends content to another user through a messenger (122), or when a user connects to Naver by operating a web browser (123) and then sends content by attaching it to Naver Mail, or when a user uploads content by attaching it to a specific bulletin board, the event receiving unit (520) receives an attachment request event from the virtual file system driver (124).

The policy verification unit (530) verifies whether the received attachment request event complies with the policy. The policy verification unit (530) verifies whether the application program that sent the attachment request event, i.e., the process, is a process set in the policy, or whether the URL address of the process that requested the attachment request event is a URL address set in the policy.

The link file creation unit (540) creates a link file according to the policy verification result of the policy verification unit (530). If the received attachment request event conforms to the policy, the link file creation unit (540) transmits an attachment request for the content requested for attachment to the central server (110) and receives a response thereto. The response includes the file storage path of the content requested for attachment, i.e., the attachment content copied from the original file.

The link file creation unit (540) creates a link file including creator information, file information, and verification information. Here, the creator information includes the creation time of the link file, the last modification time of the content, creator information (e.g., ID), the address of the central server (110), and the file storage path of the original file that is the basis of the attached content, the file information includes the file storage path of the attached content copied from the original file, and the verification information is hash information of the creator information and the file information.

Preferably, the link file creation unit (540) creates the link file by making the file name and extension of the link file the same as the file name and extension of the attached content. Therefore, when viewed by a user, the link file has the same file name and extension as the attached content, and the only difference is the capacity. The link file has a capacity of approximately 1 KB.

The link file creation unit (540) transmits the generated link file to the process that transmitted the attachment request event through the virtual file system driver (124). Therefore, for example, a messenger (122) transmits the link file to the other party, and a web mail site of a web browser (123) attaches the link file as an attachment file to an email. In addition, the link file creation unit (540) transmits information on the generated link file to the central server (110). Therefore, the central server (110) records a link file creation log based on the file name of the link file.

The link file processing unit (550) transmits the link file to the central server (110) when the link file is stored in the drive mounted by the agent (121). Accordingly, the central server (110) stores the received link file in a folder within the server synchronized with the local folder of the user terminal (120) where the link file is stored, and then converts the link file stored in the folder within the server into attached content copied and stored in the attachment file storage area. Accordingly, the capacity of the link file within the local folder of the user terminal (120) synchronized with the folder within the server is converted into the capacity of the attached content and displayed. As a result, the transmission of the content is completed, and the user can view and edit the attached content within the local folder.

In one embodiment, the link file processing unit (550) extracts verification information from the link file, performs a hash operation on the remaining information except for the verification information of the link file, and verifies whether the extracted verification information is the same as the value calculated by the hash operation. If they are not the same, the link file is determined to have been damaged during transmission and reception, and the link file processing unit (550) deletes the link file stored in the drive, and converts the link file into attached content only if they are the same.

In addition, in one embodiment, the link file processing unit (550) may, before transmitting the link file to the central server (110), transmit information about the link file to the central server (110) to inquire whether the file can be viewed, and if a response indicating that the file cannot be viewed is received from the central server (110), the link file stored in the drive may be deleted, and when a response indicating that the file can be viewed is received, the link file may be transmitted to the central server (110).

Fig. 6 is a flowchart illustrating a method of transmitting content via a messenger in the content centralization system of Fig. 1. This embodiment is an example of transmitting content from user terminal #1 to user terminal #2.

Referring to FIG. 6, in step S601, a user at user terminal #1 (120) drives a messenger (122) and selects content to be transmitted to user terminal #2 (120) from a drive mounted by agent (121). Accordingly, in step S602, an attachment request event is transmitted from messenger (122) to agent (121) via virtual file system driver (124).

In step S603, the agent (121) checks whether the received attachment request event complies with the policy. If it does not comply with the policy, for example, if the attachment request event is received from a process that is not set in the policy, in steps S604 and S605, the agent (121) requests and receives the original file of the content for which attachment is requested from the central server (110). Then, in step S606, the agent (121) transfers the received original file to the messenger (122) through the virtual file system driver (124). Accordingly, the messenger (122) transmits the original file to the user terminal #2 (120). In another embodiment, if it does not comply with the policy, the agent (121) may block the attachment itself.

Meanwhile, if the result of verification in step S603 shows that the received attachment request event complies with the policy, in step S607, the agent (121) transmits an attachment request for content corresponding to the attachment request event to the central server (110).

In step S608, the central server (110) copies the original file of the content for which attachment has been requested from the original storage area of the storage unit (111) and stores it as attachment content in the attachment file storage area, and in step S609, the central server (110) transmits a response to the agent (121). Here, the response includes the file storage path of the attachment content.

In step S610, the agent (121) creates a link file for the attached content. Preferably, the agent (121) creates a link file including creator information, file information, and verification information. Here, the creator information includes the creation time of the link file, the last modification time of the content, creator information (e.g., ID), the address of the central server (110), and the file storage path of the original file that is the basis of the attached content, the file information includes the file storage path of the attached content copied from the original file, and the verification information is hash information of the creator information and the file information. Preferably, the agent (121) creates the link file by making the file name and extension of the link file the same as the file name and extension of the attached content.

In step S611, the agent (121) transmits the generated link file to the process that transmitted the attachment request event through the virtual file system driver (124). Therefore, in step S612, the messenger (122) transmits the link file, not the attachment content itself, to the user terminal #2 (12).

In addition, in step S613, the agent (121) transmits information on the generated link file to the central server (110). Therefore, in step S614, the central server (110) records a generation log of the link file in the log storage area of the storage unit (111) based on the file name of the link file. The generation log includes the generation time, the creator name, and attached parameters (e.g., process name, URL information).

In one embodiment, the agent (121) may transmit viewing ON/OFF setting information for attached content received from a user to the central server (110). In this case, the central server (110) records the viewing ON/OFF setting information in a record based on the link file name in the log storage area of the storage unit (111).

FIG. 7 is a flowchart explaining a method of receiving content via a messenger in the content centralization system of FIG. 1. This is an example of creating a link file at user terminal #1 and transmitting it to user terminal #2, and processing the link file at user terminal #2 according to the method explained with reference to FIG. 6.

Referring to FIG. 7, in step S701, the messenger (122) of the user terminal #2 (120) receives a link file from the messenger (122) of the user terminal #1 (120). The user moves the received link file into a drive mounted by the agent (121).

In step S702, the agent (121) performs integrity verification of the link file moved into the mounted drive. That is, the agent (121) extracts verification information from the link file, performs a hash operation on the remaining information excluding the verification information of the link file, and verifies whether the extracted verification information is identical to the value calculated.

If they are not identical, i.e., if the integrity verification fails, in step S703, the agent (121) determines that the link file has been damaged during transmission and reception and deletes the link file stored in the drive.

On the other hand, if the integrity verification is successful, in step S704, the agent (121) transmits the link file to the central server (110). In step S705, the central server (110) stores the received link file in a folder within the server synchronized with the local folder of the user terminal (120), and converts the link file stored in the folder within the server into attached content copied and stored in the attachment file storage area.

In step S706, the central server (110) transmits a conversion completion response to the agent (121), and in step S707, the central server (110) records a conversion log of the link file in the log storage area of the storage unit (110). The conversion log includes the conversion time, converter name, and conversion file name.

In step S708, the agent (121) converts the capacity of the link file in the local folder of the user terminal (120) synchronized to the folder in the server into the capacity of the attached content and displays it. As a result, the content transfer from the user terminal #1 to the user terminal #2 is completed, and the user of the user terminal #2 can view and edit the attached content in the local folder.

Meanwhile, in step S704, before transmitting the link file to the central server (110), the agent (121) transmits information on the link file to the central server (110) to inquire whether it can be viewed, and if a response that it cannot be viewed is received from the central server (110), the agent can delete the link file stored in the drive, and when a response that it can be viewed is received, the agent can transmit the link file to the central server (110).

According to the above embodiment, traffic can be significantly reduced compared to conventional content attachment methods. A representative method of attaching large-capacity content is a method of attachment using a link URL. There is a significant difference in traffic between content attachment using a link URL and content attachment using a link file according to the present invention.

For example, if a first user transmits a 1GB file stored in a central server (110) to 10 other users using a conventional link URL, the first user must transmit the link URL to the 10 other users, and each of the 10 users must access the central server (110) using the link URL, download the 1GB file, and then upload the 1GB file to their own folder in the central server (110). In other words, 1GB x 10 downloads + 1GB x 10 uploads = 20GB of traffic is generated (the transmission traffic of the link URL is ignored).

On the other hand, when the first user transmits a 1 GB file stored in the central server (110) to 10 other users using a link file according to the present invention, the first user creates a 1 KB link file and transmits it to the 10 other users, and each of the 10 users only needs to store the 1 KB link file in the local drive of their user terminal and upload it to their own folder in the central server (110). The central server (110) automatically converts the link file into the 1 GB file that the first user requested to be attached. Therefore, in the present invention, a traffic of 1 KB x 10 transmissions + 1 KB x 10 uploads = 0.02 GB is generated.

Compared to attaching content using a conventional link URL, the present invention can reduce traffic generation by 1/1000.

In addition, the present invention can centrally control content attachment by attaching content using a link file, thereby preventing security issues such as external leakage of important information, and can track the status of content attachment in real time.

In addition, the present invention permanently stores content attached by a user at a specific point in time in a separate attachment file storage area, thereby enabling the user to confirm content attached and transmitted to another user at a specific point in time at a later time, thereby providing an effect of preventing denial of content leakage, etc.

While this specification includes many features, such features should not be construed as limiting the scope of the invention or the claims. Furthermore, features described in separate embodiments herein may be combined and implemented in a single embodiment. Conversely, various features described in a single embodiment herein may be implemented in multiple embodiments individually or in suitable combinations.

Although the operations are illustrated in the drawings in a particular order, it should not be understood that such operations are to be performed in the particular order illustrated, or in a series of sequential orders, or that all of the illustrated operations are to be performed to achieve a desired result. Multitasking and parallel processing may be advantageous in certain circumstances. Furthermore, it should be understood that the distinction between the various system components in the embodiments described above does not require such distinction in all embodiments. The program components and systems described above may generally be implemented as a package in a single software product or in multiple software products.

The method of the present invention as described above can be implemented as a program and stored in a computer-readable form on a recording medium (CD-ROM, RAM, ROM, floppy disk, hard disk, magneto-optical disk, etc.). Since this process can be easily performed by a person having ordinary skill in the art to which the present invention belongs, it will not be described in detail any further.

The present invention described above is not limited to the above-described embodiments and the attached drawings, since various substitutions, modifications, and changes can be made without departing from the technical spirit of the present invention by a person having ordinary skill in the art to which the present invention pertains.

110: Central Server 111: Storage
112: Content Management Department 113: Content Attachment Management Department
114: Policy Management Department 120: User Terminal
121: Agent 122: Messenger
123 : Web Browser 124 : Virtual File System Driver
130: Attachment Parameter Means 131: Messenger Server
132: Web Server 510: Server Synchronization Unit
520: Event receiving unit 530: Policy verification unit
540: Link file creation section 550: Link file processing section

Claims (19)

In a content centralization system,
A central server that creates user folders to store and manage content; and
Includes a user terminal that displays the user's folder on the local screen and includes an agent that connects to a virtual file system driver,
The above agent,
A server synchronization unit that synchronizes the user's folder of the central server and displays it on the local screen;
An event receiving unit that receives an attachment request event for a specific content in the user's folder displayed on the local screen from a predetermined process through the virtual file system driver; and
A link file generation unit is included that transmits an attachment request for the specific content to the central server, receives a response thereto, generates a link file for the specific content based on the received response, and transmits it to the predetermined process through the virtual file system driver.
The above central server,
Upon receiving the above attachment request, the original file of the specific content stored in the original storage area is copied and stored as the attached content in the attachment file storage area, and the response including the file storage path of the attached content is transmitted to the link file creation unit.
The above agent,
If the link file is saved in the user's folder displayed on the local screen, the system further includes a link file processing unit that transmits the link file to the user's folder of the central server.
The above central server,
A content centralization system that converts link files stored in the user's folder into attachment contents stored in the attachment file storage area based on the file storage path included in the link file. In the first paragraph,
The above agent,
Further comprising a policy verification section for checking whether the above attachment request event complies with the policy;
The above link file generation part,
A content centralization system characterized in that the link file is generated when the above attachment request event conforms to the policy. In the second paragraph,
The above policy is,
A content centralization system characterized by including at least one of process information and URL addresses that can utilize a link file. delete In the first paragraph,
The above link file generation part,
Creator information including the user's information, the address of the central server, and the creation time;
File information including the above file storage path; and
A content centralization system characterized by generating the link file, including verification information based on the creator information and the file information. In paragraph 5,
The above central server,
A content centralization system characterized by receiving information on the link file from the link file creation unit and recording a creation log based on the file name of the link file in a log storage area based on the information on the link file. delete In the first paragraph,
The above central server,
A content centralization system characterized in that, after the above conversion, a conversion log is recorded in a log storage area based on the file name of the link file. In the first paragraph,
The above central server,
A content centralization system characterized in that the conversion is performed only when viewing is set to ON, and the link file stored in the user's folder is deleted when viewing is set to OFF, with reference to the viewing ON/OFF setting information for the attached content set by the user. A method for attaching content in a content centralization system, comprising: a central server for creating a user's folder to store and manage content; and a user terminal including an agent that displays the user's folder on a local screen and is connected to a virtual file system driver;
The step of the above agent synchronizing the user's folder of the central server and displaying it on the local screen;
The above agent receives an attachment request event for specific content in the user's folder displayed on the local screen from a predetermined process through the virtual file system driver;
The step of the agent transmitting an attachment request for the specific content to the central server, receiving a response thereto, and creating a link file for the specific content based on the received response; and
The above agent comprises a step of transmitting the link file to the predetermined process through the virtual file system driver,
The steps to create the above link file are:
The agent, in response to the attachment request, receives the response including the file storage path of the attached content from the central server, which copies the original file of the specific content stored in the original storage area and stores it as attached content in the attachment file storage area,
The above method,
The step of the agent transmitting the link file to the user's folder of the central server when the link file is stored in the user's folder displayed on the local screen; and
A method further comprising a step of the central server converting a link file stored in the user's folder into an attachment content stored in the attachment file storage area based on the file storage path included in the link file. In Article 10,
After receiving the above attachment request event,
The above agent further comprises a step of checking whether the attachment request event conforms to a policy,
The steps to create the above link file are:
A method characterized in that the link file is generated when the above attachment request event conforms to a policy. In Article 11,
The above policy is,
A method characterized by including at least one of process information and a URL address that can utilize a link file. delete In Article 10,
The steps to create the above link file are:
A method characterized by generating the link file including: creator information including the user's information, the address of the central server, and the creation time; file information including the file storage path; and verification information based on the creator information and the file information. In Article 14,
A method characterized in that the central server further includes a step of receiving information of the link file from the agent and recording a generation log based on the file name of the link file in a log storage area based on the information of the link file. delete In Article 10,
A method characterized in that the central server further includes a step of recording a conversion log based on the file name of the link file in a log storage area after the conversion. In Article 10,
The step of converting the above link file into attachment content stored in the above attachment file storage area is:
A method characterized in that the central server performs the conversion only when viewing is set to ON, referring to the viewing ON/OFF setting information for the attached content set by the user, and deletes the link file stored in the user's folder when viewing is set to OFF. A computer program stored on a computer-readable recording medium that executes the method according to any one of Articles 10 to 12, 14, 15, 17, and 18 through a computer system.