KR102076138B1 - Apparatus for managing smart log file and method for the same - Google Patents

Abstract

The smart log file management apparatus includes a memory and a processor electrically connected to the memory, and the processor detects whether a file is updated through the user terminal, generates a system log message including a file storage time, and sends the system log message to the user terminal. A user log message for updating the file is generated, and a smart log message is generated based on the system log message and the user log message and associated with the file.

Description

Apparatus and method for managing smart log files {APPARATUS FOR MANAGING SMART LOG FILE AND METHOD FOR THE SAME}

The present invention relates to a log file management technology, and more particularly, to an apparatus and method for smart log file management that can efficiently manage and intuitively notify a user's file update and improve user convenience.

The file management program may be implemented as an application that stores and manages files of users in a user account space of the server, and may provide a function of uploading or downloading a file requested by the user. As the number of users using file management programs increases, various file management applications are being developed to support efficient file sharing and management among various users.

Korean Laid-Open Patent Publication No. 10-2004-0025445 (2004.03.24) relates to a system and method for managing a file sharing, retrieval, and access rights of a shared file on a per-share basis through a web browser. (Web Browser) is installed, a plurality of terminals for requesting the search of the shared file by inputting a search word or for transmitting and receiving the shared file, collecting index information from each of the terminals accessing the shared file, and each terminal A web server for transmitting the search results for the search term transmitted from the web server to the corresponding terminal as a HTML document and a member information database storing personal information of a user registered as a member in the web server and the web server collected from the respective terminals. Contains a database server that contains an index information database where one index information is stored and updated The.

Korean Patent No. 10-0295725 (2001.05.02) relates to a copy management method of a shared data file, and (a) for each copy (205, 420) of the shared data file, Maintaining a record 540, and (b) retrieving a maintenance record 550 maintained for at least a portion of said copy of said shared data file through a connection to said mobile communications network 460; (C) merging (560) the retrieved records to create a change sequence, and (d) applying a predefined rule (580) to the change sequence to resolve conflicts in the change sequence. And (e) changing at least one copy (205, 420) of the shared file based on the change sequence in which the conflict was resolved.

Korean Patent Publication No. 10-2004-0025445 (2004.03.24) Korean Patent Registration No. 10-0295725 (2001.05.02)

An embodiment of the present invention is to provide a smart log file management apparatus and method that can efficiently manage and update the user's file updates and improve the user convenience.

An embodiment of the present invention is to provide an apparatus and method for managing a smart log file that facilitates sharing of update contents to be transmitted between file sharers through a user response in a file update process.

Among the embodiments, the smart log file management apparatus includes a memory and a processor electrically connected to the memory, the processor detects whether the file is updated through the user terminal to generate a system log message including the file storage time; And generating a user log message for updating the file to the user terminal, and generating a smart log message based on the system log message and the user log message and associating with the file.

The processor may include the user identifier authenticated during the login process of the user terminal in the system log message.

The processor may generate the presence or absence of a feedback request of another user according to the update of the file as the first partial message of the user log message.

The processor may notify the other user of the update of the file immediately when the feedback request is made or when the login of the other user is performed.

The processor may generate whether or not the file is renewed by the other user after the notification in response to the first partial message.

The processor may copy the current file reflecting the update of the file as a checkpoint file as the second partial message of the user log message.

The processor may generate a user memo indicating an update intention of the corresponding user as a third partial message of the user log message.

When updating of the file is completed, the processor may automatically suggest the user memo based on contents changed in the existing file.

The processor may generate a file badge per user according to the update of the file as the fourth partial message of the user log message.

The processor may update the user-independent file modification history by detecting modification of the file by any user terminal.

The processor may generate the file badge for each user based on the file modification history and the file access time for each user.

The processor may generate a smart log message further comprising a correlation analysis result generated through the correlation analysis between the system log message, the user log message and the corresponding log messages.

The processor may calculate and include statistical information regarding at least one of a total number of modifications associated with the file, a total number of feedback requests, a total number of feedback request responses, and a number of smart log message provision times, and include the same in the smart log message.

The processor may determine whether to provide at least a portion of the smart log message by analyzing the smart log message when an access of the file is requested by an arbitrary user terminal.

The processor may notify the user terminal of the number of modifications occurring after a specific number of modifications have been detected since the last access date of the user requesting access to the file, and may recommend checking the smart log message before opening the file. .

Among the embodiments, the smart log file management method is performed in a smart log file management apparatus including a memory and a processor electrically connected to the memory, the smart log file management method is (a) whether or not to update the file through the user terminal Generating a system log message including a file storage time by detecting a message; (b) generating a user log message relating to an update of the file to the user terminal; and (c) the system log message and the user log message. Generating a smart log message based on the message and associating it with the file.

Among the embodiments, the recording medium stores a smart log file management method performed in a smart log file management device including a memory and a processor electrically connected to the memory and computer-executable, the recording medium is (a) a user terminal A function of generating a system log message including a file storage time by detecting whether a file is updated through a file, (b) generating a user log message of updating the file to the user terminal, and (c) the system log And generating a smart log message based on the message and the user log message and associating it with the file.

The disclosed technique can have the following effects. However, since a specific embodiment does not mean to include all of the following effects or only the following effects, it should not be understood that the scope of the disclosed technology is limited by this.

The smart log file management apparatus and method according to an embodiment of the present invention can efficiently manage and update the file update of a user, thereby improving user convenience.

The apparatus and method for managing a smart log file according to an embodiment of the present invention can support sharing of update contents to be transmitted among file sharers through a user's response during a file update process.

1 is a view for explaining a smart log file management system according to an embodiment of the present invention.
FIG. 2 is a block diagram illustrating an apparatus for managing a smart log file in FIG. 1.
3 is a block diagram illustrating functional elements of a processor in FIG. 2.
4 is a flow chart illustrating a smart log file management procedure performed by the processor in FIG.
5 to 6 are diagrams illustrating an embodiment for describing a process of providing a smart log message by interworking with a user terminal by the smart log file management apparatus of FIG. 1.

Description of the present invention is only an embodiment for structural or functional description, the scope of the present invention should not be construed as limited by the embodiments described in the text. That is, since the embodiments may be variously modified and may have various forms, the scope of the present invention should be understood to include equivalents for realizing the technical idea. In addition, the objects or effects presented in the present invention does not mean that a specific embodiment should include all or only such effects, the scope of the present invention should not be understood as being limited thereby.

On the other hand, the meaning of the terms described in the present application should be understood as follows.

Terms such as "first" and "second" are intended to distinguish one component from another component, and the scope of rights should not be limited by these terms. For example, the first component may be referred to as a second component, and similarly, the second component may also be referred to as a first component.

When a component is referred to as being "connected" to another component, it should be understood that there may be other components in between, although it may be directly connected to the other component. On the other hand, when a component is referred to as being "directly connected" to another component, it should be understood that there is no other component in between. On the other hand, other expressions describing the relationship between the components, such as "between" and "immediately between" or "neighboring to" and "directly neighboring", should be interpreted as well.

Singular expressions should be understood to include plural expressions unless the context clearly indicates otherwise, and terms such as "comprise" or "have" refer to a feature, number, step, operation, component, part, or portion thereof that is implemented. It is to be understood that the combination is intended to be present and does not exclude in advance the possibility of the presence or addition of one or more other features or numbers, steps, actions, components, parts or combinations thereof.

In each step, an identification code (e.g., a, b, c, etc.) is used for convenience of description, and the identification code does not describe the order of the steps, and each step is clearly contextual. Unless stated otherwise, they may occur out of the order noted. That is, each step may occur in the same order as specified, may be performed substantially simultaneously, or may be performed in the reverse order.

The present invention can be embodied as computer readable code on a computer readable recording medium, and the computer readable recording medium includes all kinds of recording devices in which data can be read by a computer system. . Examples of computer-readable recording media include ROM, RAM, CD-ROM, magnetic tape, floppy disk, optical data storage device, and the like. The computer readable recording medium can also be distributed over network coupled computer systems so that the computer readable code is stored and executed in a distributed fashion.

All terms used herein have the same meaning as commonly understood by one of ordinary skill in the art unless otherwise defined. The terms defined in the commonly used dictionary should be interpreted to coincide with the meanings in the context of the related art, and should not be interpreted as having ideal or excessively formal meanings unless clearly defined in the present application.

1 is a view for explaining a smart log file management system according to an embodiment of the present invention.

Referring to FIG. 1, the smart log file management system 100 includes a smart log file management device 110 and a user terminal 120.

The smart log file management apparatus 110 corresponds to a computing device that can be connected to at least one user terminal 120 through a network. In an embodiment, the smart log file management apparatus 110 may manage at least one member group in which a user associated with the user terminal 120 is included as a member. In an embodiment, the smart log file management apparatus 110 may be connected to the user terminal 120 through a smart log file agent installed in the user terminal 120, where the smart log file agent is the user terminal 120. If installed in the user terminal 120, the user terminal 120 and the smart log file management device 110 may be implemented as a software that can interoperate with each other.

The user terminal 120 may correspond to a computing device that may be connected to the smart log file management apparatus 110 through a network. For example, the user terminal 120 may correspond to a user terminal implemented as a desktop, a laptop, a tablet PC, or a smartphone. . In one embodiment, the first user terminal 120a may correspond to a mobile terminal, and may be connected to the smart log file management apparatus 110 through cellular communication or Wi-Fi communication. In another embodiment, the second user terminal 120b may correspond to a desktop and may be connected to the smart log file management apparatus 110 through the Internet.

FIG. 2 is a block diagram illustrating an apparatus for managing a smart log file in FIG. 1.

Referring to FIG. 2, the smart log file management apparatus 110 may include a processor 210, a memory 220, a user input / output unit 230, and a network input / output unit 240.

The processor 210 may execute the smart log file management procedure shown in FIG. 4, and may manage the memory 220 that is read or written in this process, and between the volatile memory and the nonvolatile memory in the memory 220. You can schedule synchronization times. The processor 210 may control the overall operation of the smart log file management apparatus 110, and is electrically connected to the memory 220, the user input / output unit 230, and the network input / output unit 240 to exchange data flow therebetween. Can be controlled. The processor 210 may be implemented as a central processing unit (CPU) of the smart log file management device 110.

The memory 220 may include a secondary memory device which is implemented as a nonvolatile memory such as a solid state disk (SSD) or a hard disk drive (HDD), and is used to store the entire data necessary for the smart log file management device 110. And a main memory device implemented with volatile memory such as random access memory (RAM). As such, the memory 220 may be implemented as volatile and nonvolatile memory, and if implemented as nonvolatile memory, the memory 220 may be connected through a hyperlink.

The user input / output unit 230 includes an environment for receiving user input and an environment for outputting specific information to the user, and includes, for example, a mouse, a trackball, a touch pad, a graphic tablet, a scanner, a touch screen, a keyboard, or a pointing. It may include an input device including an adapter such as a device and an output device including an adapter such as a monitor or a touch screen. In one embodiment, the user input / output unit 230 may correspond to a computing device connected through a remote connection, in which case, the smart log file management device 110 may be performed as a server.

The network input / output unit 240 may include an environment for connecting to the user terminal 120 through a network and may include, for example, an adapter for local area network (LAN) communication.

3 is a block diagram illustrating functional elements of a processor in FIG. 2.

Referring to FIG. 3, the processor 210 may include a system log message generator 310, a user log message generator 320, a smart log message generator 330, and a controller 340.

The system log message generator 310 detects whether a file is updated through the user terminal 120 and generates a system log message including a file storage time. Here, the file may include a general user file such as a document file or a multimedia file transmitted from the user terminal 120. In one embodiment, the system log message generating unit 310 includes a file storage time when the modification of a specific file in the folder is detected by the user terminal 120 participating in the folder as a folder participant, the file update type, The system log message may further include at least one of user information and user group information. In one embodiment, the file storage time may include at least one of a generation time, a last modified time and a last access time.

The system log message generating unit 310 may include the user identifier authenticated during the login process of the user terminal 10 in the system log message, and in one embodiment, the user ID from the user information associated with the corresponding user terminal 120. Alternatively, you can get the username and include it in the system log message.

The system log message generator 310 may include a user group identifier associated with the user terminal 10 in the system log message, and in one embodiment, a user group in which a user associated with the corresponding user terminal 120 participates as a member. You can get the ID or user group name and include it in the system log message.

The user log message generating unit 320 generates a user log message regarding the update of the file to the user terminal 120. In one embodiment, the user log message generation unit 320 may generate a user log message composed of a plurality of partial messages for indicating at least one of feedback about the update of the file, the user update intention, and the contents of the update. have.

The user log message generator 320 may generate the presence or absence of a feedback request of another user according to the update of the corresponding file as the first partial message of the user log message. In one embodiment, the user log message generation unit 320 generates the presence or absence of a feedback request to determine whether to feed back the file update to another user based on feedback request information received during the file update process and input by the user. can do. For example, the user log message generation unit 320 may request a feedback as a first partial message of the user log message if a feedback request check button provided as a user interface is checked by a user during a file update process. Can be generated.

In another embodiment, when the file is updated, the user log message generator 320 may immediately provide a feedback confirmation message asking the user terminal 120 whether to update the file update to another user after completion of the update. (E.g., provide a pop-up message with [Do you want to feed other folder participants about file updates]), and based on the feedback confirmation response message received as a user response to the feedback confirmation message (e.g., In response to selecting [Yes] in the pop-up message, it may be determined whether to include the feedback request in the first partial message of the user log message.

According to an embodiment, the user log message generator 320 may set at least one folder participant specified in the process of confirming the user's intention regarding the feedback and participate in the corresponding folder as a feedback target, and thus, the first log of the user log message. Can be included in partial messages.

If there is a feedback request, the user log message generator 320 may notify the corresponding other user of the update of the file immediately or when the login of the corresponding other user is performed. In one embodiment, the user log message generation unit 320 and each of the at least one folder participant included in the feedback request as a feedback target when the feedback request for the update of the file is confirmed through the first partial message of the user log message; The associated user terminal 120 may provide a file update notification message summarizing the main contents of the user log message regarding the file update.

The user log message generating unit 320 may generate whether or not the corresponding file is re-updated by the corresponding other user after the notification as a response message of the first partial message. According to an embodiment, the user log message generator 320 may receive a file update notification response when a file update notification response message including whether to renew the file as a response by the corresponding user to the file update notification message is received. Based on the message, whether or not to update the file may be generated and included in the first part message of the user log message.

The user log message generator 320 may copy the current file reflecting the update of the corresponding file as the second partial message of the user log message as a checkpoint file. The user log message generating unit 320 may copy the file at the present time as a checkpoint file so that the file at the present time may be checked later or restored. For example, when the modification of the first file is detected, the user log message generating unit 320 may copy the first file at the time of the modified time. Replicate to the first checkpoint file and include it in the second partial message of the user log message.If modification of the first file is detected again later, the first file of the modified point is copied to the second checkpoint file again. The second part of the log message may be included in the message.

In one embodiment, when the modification of the file is detected for the first time, the user log message generator 320 may duplicate the original file as an original checkpoint file and generate a file at the time of file update as a checkpoint file. The user log message generator 320 may accumulate and manage the checkpoint file as the second partial message of the user log message whenever modification of the file is detected. For example, a checkpoint file can be managed up to one month) or a specific number (for example, 100 times).

The user log message generation unit 320 may generate a user memo indicating the update intention of the corresponding user as the third partial message of the user log message. In one embodiment, the user log message generation unit 320 may generate a user memo based on user update intention information received in the file update process and input by the user, for example, a user in the file update process. When user update intention information (eg, [detail subject change and comeback correction]) input by a user is received through a user memo generation field provided as an interface, the user part may be included as a user memo in the third part message of the user log message. have.

When the update of the file is completed, the user log message generator 320 may automatically suggest a user memo based on the changed contents of the existing file. In one embodiment, when the file update is completed, the user log message generator 320 may compare and analyze the first checkpoint file previously generated from the previous update (or original) and the second checkpoint file generated at the corresponding update point. The electronic device may detect at least one of changed content content, a change type, and a corrected amount in the second checkpoint file compared to the first checkpoint file, and generate a recommended user memo based on the detected information to the user terminal 120. After providing, you can decide whether to save the recommended user memo as a user memo according to the approval by the user.

For example, the user log message generating unit 320 modifies the [tumble meeting] to [strategic meeting] by two bytes and adds the following strategies by comparing the checkpoint file with the previous analysis. ] Can be added to the user terminal 120 by detecting the addition of 150 bytes of [corrected correction, add description] as a recommended user memo, and provides the generated user recommendation memo to the user terminal 120 Suggest a use of the recommended user note (for example, visualize “Would you like to record [Comb Fix, Add Comment] as the user update intent of this fix”), and respond to the suggestion from the user terminal 120 As a user approval, the recommended user memo may be added as a user memo to the third part message of the user log message.

The user log message generator 320 may generate a file badge per user according to the update of the file as the fourth partial message of the user log message. Here, the file badge for each user may include information indicating whether the file update is confirmed for each user.

More specifically, the user log message generator 320 may generate a user-independent file modification history including modification information performed for each user (for example, a folder user participating in the folder) with respect to the file according to the file update. It can create and manage, and create a user-specific file badge based on the file modification history. For example, if the user [Cho Jae-ho] has modified the file A in the folder, it affects all the folder users participating in the folder, so that the user-specific file badge for the file A can be updated independently of the user.

The user log message generating unit 320 may accumulate file modification dates in the file modification history during a specific interval from the present or a specific number of file modifications in the process of updating the file modification history. The user log message generator 320 may manage a time stamp including a creation date, a modification date, and an access date as a user's time displacement parameter with respect to the corresponding file, and reflect it as a file modification date in the file modification history. For example, the file badge management unit 330 may sequentially manage file modification dates a, b, c, and d sequentially generated in the file modification history by multiple users of the file, as shown in Table 1 below. And can reflect file modifications that occurred in the past year or three months from the current time point or up to 100 times.

[Table 1]

According to an embodiment, the user log message generator 320 may determine the specific number based on Equation 1 below, and accumulate file modification dates according to the determined specific number of file modifications in the file modification history. have. For example, _assuming that m _av1 and m _av2 are detected as 2.6 and 1.4 and n ₀ is set to 50, the user log message generator 320 calculates n as 93 according to Equation 1 below. The calculated n may be determined as a specific number for accumulating file modification dates.

[Equation 1]

는 내부의 값에 대해 정수로 반올림 연산을 수행하는 연산을 의미한다.Here, m _av1 represents the number of modifications that occurred on an average per day during the first recent specific interval (eg, during the last week) for the file, and m _av2 represents the most recent second specific interval in the file ( For example, the number of corrections generated on a daily average for the last three months) is shown, wherein the second specific section means a time section longer than the first specific section. Here, n ₀ represents a reference cumulative number (eg, 100) and can be set by a user or a designer,

Is an operation that performs rounding operation to an internal value.

When the file update is completed, the user log message generation unit 320 may update the file badge for each user by tracking the file access time and the file modification history of the corresponding file for each user. For example, the user log message generation unit 320 may check the file modification date of each user of the file from the file modification history of Table 1 regarding the file, and access the file last for each user. Based on a date and time, file modifications generated in the meantime may be counted to generate a file badge for each user as shown in Table 2 below. For example, user A's file badge is updated to 0 because user A last modified the file, and user B's file badge is updated to 1 since 1 modification has occurred since user B's last access date. The file badge of user C may be updated to 2 since two modifications have occurred since the user C's last access date.

[Table 2]

The user log message generation unit 320 may detect the reading of the file by the user terminal 120 and update the file badge related to the corresponding file of the corresponding user. Following the above example, the user terminal associated with the user C ( 120) If the corresponding file of the file badge 2 is opened or downloaded, the user C file badge of the user-specific file badge of the file may be updated from 2 to 0.

The smart log message generator 330 generates a smart log message based on the system log message and the user log message and associates it with the corresponding file. The smart log message generator 330 may generate a smart log message including a system log message and a user log message, and in one embodiment, the correlation analysis generated through the correlation analysis between the corresponding system log message and the user log message. You can create a smart log message that further contains the results. For example, the smart log message generating unit 330 may set the feedback if there is a feedback setting [recommend feedback request] among the group setting information set associated with the group ID of the corresponding user in the system log message during the generation of the smart log message. The first partial message [Feedback requested] and the corresponding feedback setting information of the user log message associated with may be included in the smart log message.

The smart log message generator 330 may calculate and include statistical information about at least one of the total number of modifications associated with the corresponding file, the total number of feedback requests, the total number of feedback request responses, and the number of times the smart log message is provided and included in the smart log message. have.

In one embodiment, as shown in Table 3 below, the smart log message generator 330 may generate a smart log message based on the system log message and the user log message and associate it with the corresponding file. For example, the smart log message generating unit 330 may include (a) file storage time, file update type, user information and user group information in the system log message, (b) feedback request in the user log message, checkpoint File, user update intent and file badge for each user, (c) user setting information and group setting information, and (4) statistics on total modifications, total feedback requests, total feedback request responses, and smart log message provisions. You can generate smart log messages as a basis.

[Table 3]

The smart log message generator 330 may determine whether to provide at least some of the corresponding smart log messages by analyzing the smart log messages of the file when the user is requested to access the file. For example, the smart log message generation unit 330 analyzes the smart log message and receives the last access of the user even when there is no access request for the smart log message associated with the file by the user. If more than a certain number of modifications have been detected since the date (for example, three times), we recommend that you either provide the file with the smart log message or notify the number of modifications and check the smart log message first before opening the file. The smart log message confirmation recommendation message may be provided to the user terminal 120.

The smart log message generating unit 330 may manage the smart log message in a corresponding folder or through a separate root.

In one embodiment, the smart log message generator 330 may store the smart log message as a user file in the folder. In one embodiment, the smart log message generating unit 330 may store the smart log message as a read-only attribute, and may update the smart log message according to the detection of the file update, the user terminal 120 When access to a smart log message is requested, the smart log message can be viewed as read-only.

In another embodiment, the smart log message generator 330 stores the smart log message as a log file in a specific area of the file system, and associates the smart log message with the corresponding file through a smart log file database (not shown). The relationship may be managed, and when the access request for the smart log message is received from the user terminal 120 through the corresponding file, the smart log message may be read-only. The smart log message generator 330 may modify the smart log file database based on the request of the user terminal 120 to reset the association between them.

When the movement of the file is detected, the smart log message generating unit 330 may move the smart log message associated with the file to the folder of the moving target or modify the smart log file database to reset the association.

When the smart log message generation unit 330 receives a request for providing a detailed file change from the user terminal 120 in the process of providing the smart log message, the smart log message generator 330 analyzes the change of the user log message in the corresponding smart log message. Can be provided. For example, the smart log message generator 330 associates the first checkpoint file before the modification and the second checkpoint file after the modification with respect to the modification based on the corresponding smart log message to provide a visual contrast of the changes. You can do that.

When the user terminal 120 logs in, the smart log message generating unit 330 temporarily suspends the smart log summary information on the file update detected since the last access date of the user among all the files to which the user has access to the file. Can provide. For example, when the user terminal 120 associated with user A logs in, the smart log message generation unit 330 may include a file name, a file name of files modified since the last login among the files in all folders accessible by user A, By providing a summary list of smart logs including folder names, modification types, and modifiers, users can identify changes at once.

The controller 340 may control the overall operation of the processor 210 and control data flow between the system log message generator 310, the user log message generator 320, and the smart log message generator 330. Can be.

In one embodiment, the control unit 340 may receive an access request for a specific folder from the user terminal 120, and determine whether to allow the access by checking the access rights of the corresponding file of the user. . The controller 340 may check the access right of the folder by acquiring user information associated with the user terminal 120, and may allow the corresponding access only when the access right of the corresponding folder of the corresponding user is confirmed. The controller 340 may determine an access right of the folder through the user invitation by the folder creator when the folder is created.

When the user terminal 120 is allowed to access the folder, the controller 340 provides the user terminal 120 with a file badge for each user of each of the at least one file in the folder so that the user terminal 120 relates to the corresponding folder. In the process of displaying a file list, the user may display a file badge for each user on at least one file in the corresponding folder.

The control unit 340 cumulatively calculates the file badge of the user regarding the files in the folder and the subfolders in the substructure based on the user's file badge and file modification history for each file in the folder. Can be reflected in the badge cumulative count.

The controller 340 may detect statistical information of the smart log message associated with all files in the folder and the substructure and reflect the statistical information in the cumulative statistics count in the folder. For example, the controller 340 may be configured to provide at least one of a total number of modifications, a total number of feedback requests, a total number of feedback request responses, and a number of smart log messages provided in a file list. The cumulative statistics can be reflected and reflected in the cumulative statistics count of the folder.

The controller 340 may arrange the corresponding folder or file based on the user's file badge and the smart log message according to a request of the user terminal 120. For example, the control unit 340 according to the request of the user terminal 120, the files in the folder in the order in which the user's file medium is large (in the order of the number of unconfirmed file update), the total number of modifications For example, the total feedback request number may be arranged in ascending order, or the total feedback request response number may be arranged in order.

4 is a flow chart illustrating a smart log file management procedure performed by the processor in FIG.

In FIG. 4, the system log message generating unit 310 detects whether a file is updated through the user terminal 120 and generates a system log message including a file storage time (step S410). The user log message generation unit 320 generates a user log message regarding the update of the file to the user terminal 120 (step S420). The smart log message generator 330 generates a smart log message based on the system log message and the user log message and associates it with the corresponding file (step S430).

5 to 6 are diagrams illustrating an embodiment for explaining a process of providing a smart log message by interworking with a user terminal by the smart log file management apparatus of FIG. 1.

More specifically, FIG. 5 is a process of receiving a request for modifying a file input by a user through the file modification interface 500 of the smart log file agent in which the user terminal 120 is installed and transmitting the received request to the smart log file management apparatus 120. 6 illustrates a process in which the user terminal 120 visualizes a folder, a file list, and a smart log message provided from the smart log file management apparatus 120 through the shared folder interface 700.

In FIG. 5, when the access to a specific file is received from the user terminal 120, the smart log file management apparatus 110 may check the file access authority of the corresponding user and provide the specific file to the user terminal 120. The user terminal 120 may provide a file modification interface 500 to receive modification information about the corresponding file input by the user through the file modification interface 500.

The user terminal 120 includes a setting regarding whether to request feedback from another user regarding the file modification, a feedback request target setting, and an update intention input setting through the smart log setting menu 510 of the file modification interface 500. Smart log setting information may be received, and modifications of the corresponding file may be received through the file modification menu 520. When the user terminal 120 finally receives a file modification request including the smart log setting information and the modification contents created by the user, the user terminal 120 may transmit the request to the smart log file management apparatus 110 to request modification of the corresponding file.

When the file modification request is received through the user terminal 120, the smart log file management apparatus 110 may update the corresponding file, and the smart log setting information in the file modification request received during the update process of the corresponding file and The modifications can be analyzed to generate system log messages, user log messages, and smart log messages based on them. For example, the smart log file management device 110 generates a system log message including the corresponding file storage time [2017.12.02 18:07:42] and the corresponding user ID [Cho Jae-ho], as shown in FIG. Based on the smart log configuration information, feedback request information for [update request to all folder participants] is generated as the first partial message of the user log message, and a checkpoint file reflecting the update of the file is generated. Create a partial message, create a user memo [Modify detailed content by modifying overall contents] as a third partial message based on the smart log setting information, and generate a user-specific file badge according to the file update as a fourth partial message Thus, a smart log message can be generated based on the system and user log messages.

The smart log file management apparatus 110 may notify the update of the corresponding file when the user terminal 120 associated with the corresponding folder participant logs in according to the feedback request setting, and if the corresponding user terminal 120 responds to the notification. If the file has been modified with a message, it can be reflected in the response message for the first partial message that the modification was performed in response to the notification.

In FIG. 6A, the user terminal 120 may attempt to access a specific folder in a corresponding folder list according to a user selection, and if the access is allowed, a file list of the corresponding folder from the smart log file management apparatus 110, Information regarding a file badge and a smart log message for each user may be received and displayed through the shared folder interface 600.

The user terminal 120 may visualize a list of accessible folders of the corresponding user through the folder window 610, and calculate a file badge accumulation count calculated for each folder provided from the smart log file management apparatus 110. Symbol 612 may be used to indicate this. For example, in FIG. 6A, in the case of the '4. Productivity' folder which is the currently selected folder, the file badge accumulation count for all the files in the folder may be displayed as 6. FIG.

The user terminal 120 may visualize a file list received from the smart log file management apparatus 110 and metadata for each file through the file window 620. The user terminal 120 may display a file badge of the corresponding user for each file through the file badge symbol 622 of the file window 620. For example, [4. For each of the [Functional Filter Quality], [Filter Quality Acquisition], and [Filter Strategy Interview] files in the Improved Productivity] folder, the file badge symbol 622 is used to determine the File badges can be marked as [3], [0] and [0], and among them, in the case of file badge [3] of [Functional Filter Quality], the user [Jeong Ho] opened or downloaded the file last. A total of three modifications have been made by another user since receipt. In the case of a sub-folder in a folder, the user terminal 120 may display a file badge accumulation count for all files in the corresponding sub-folder substructure through the file badge symbol 622.

The user terminal 120 may display an access link for accessing the smart log message associated with each file through the smart log link symbol 624, and the cumulative statistical count of the corresponding folder is displayed through the cumulative statistical count symbol 626. Number of files in the folder and its substructure (total number of files: 11), sum of the number of modifications made to all of those files (total number of modifications: 13), and files at the current time, counted by all of those files Media sum (pile accumulation: 6) can be visualized. When the modification of the specific file is completed, the user terminal 120 may receive a user-specific file badge of each file updated according to the modification from the smart log file management apparatus 110 and update the file through the file window 620.

In FIG. 6B, when an access request for a smart log message regarding a specific file is received through the smart log link symbol 624 of the file window 620, the user terminal 120 transmits the access request to the smart log file management apparatus 110. The smart log file management device 110 may receive a smart log message associated with the corresponding file from the smart log file management device 110 by transmitting the same, and visualize the smart log message through the smart log window 630.

The user terminal 120 responds to a modifier (Cho Jae-ho), a modification date, a modification type (creation, modification), and a feedback request in the smart log message through the file modification basic information providing field 632 of the smart log window 630. A notification message regarding whether the file is modified may be provided, and when a plurality of updates are generated for the same file, a notification message about each of the updates may be sequentially arranged in a time series.

The user terminal 120 may visualize the first checkpoint file (file before modification) that is replicated before the file modification through the file modification column 634 of the smart log window 630, and the file display column after modification ( 636 may visualize the second checkpoint file (file before modification) reflecting the file modification. The user terminal 120 may visually display the modified portion according to the corresponding modification by overlapping the modified portion contrast marker 638 at a relative position of the modified portion in the second checkpoint file relative to the first checkpoint file.

When the user terminal 120 selects another one of the plurality of file modification basic information provision fields 632 by the user, the user terminal 120 displays the checkpoint files related to the selected modification before the file modification column 634 and the after modification file indication column ( 636) allows for new visualizations.

Although described above with reference to a preferred embodiment of the present application, those skilled in the art various modifications of the present application without departing from the spirit and scope of the invention described in the claims below And can be changed.

100: smart log file management system
110: smart log file management device
120: user terminal
210: processor 220: memory
230: user input and output unit 240: network input and output unit
310: system log message generation unit
320: user log message generation unit
330: smart log message generating unit
340: control unit

Claims (17)

A memory and a processor electrically connected to the memory,
The processor is
Detects whether the file is updated through the user terminal to generate a system log message including the file storage time,
Generating a user log message regarding the update of the file to the user terminal;
Generate a smart log message based on the system log message and the user log message and associate it with the file,
The user log message includes a presence or absence of a request for feedback on the update of the file, a checkpoint file that duplicates the file after the update is reflected, an update intention of the user's update to the file, and another user to update the file. Smart log file management apparatus comprising at least one of a file badge per user indicating whether the identification of the (file badge per user).
The system of claim 1, wherein the processor is
Smart log file management device, characterized in that to include in the system log message the user identifier authenticated during the login process of the user terminal.
The system of claim 1, wherein the processor is
And generating the feedback request of another user according to the update of the file as the first partial message of the user log message.
4. The processor of claim 3, wherein the processor is
And when the feedback request is made, notifying the other user of the update of the file immediately or when the login of the other user is performed.
The method of claim 4, wherein the processor
And generating the renewal of the file by the other user after the notification as a response message of the first partial message.
The system of claim 1, wherein the processor is
And a current file reflecting the update of the file as the second partial message of the user log message as the checkpoint file .
The system of claim 1, wherein the processor is
And a user memo indicating the update intention of the corresponding user as a third partial message of the user log message.
8. The processor of claim 7, wherein the processor is
Smart log file management device, characterized in that to automatically suggest the user memo based on the contents changed in the existing file when the update of the file is completed.
The system of claim 1, wherein the processor is
And a file badge per user according to the update of the file as a fourth partial message of the user log message.
The system of claim 9, wherein the processor is
Smart log file management apparatus, characterized in that for updating the user-independent file modification history by detecting the modification of the file by any user terminal.
The method of claim 10, wherein the processor is
Smart log file management apparatus for generating the file badge for each user based on the file modification history and the file access time for each user.
The system of claim 1, wherein the processor is
Smart log file management apparatus, characterized in that for generating a smart log message further comprises a result of the correlation analysis generated through the correlation analysis between the system log message, the user log message and the corresponding log messages.
The system of claim 1, wherein the processor is
Smart log file management apparatus, characterized in that for calculating the statistical information relating to at least one of the total number of modifications associated with the file, the total number of feedback request, the total number of feedback request response, and the number of smart log message provided and included in the smart log message .
The system of claim 1, wherein the processor is
The smart log file management apparatus, characterized in that if the user access to the file is requested by any user terminal to analyze whether or not to provide at least a portion of the smart log message associated with the smart log message.
15. The system of claim 14, wherein said processor is
If a modification occurs more than a certain number of times since the last access date of the user requesting access to the file, the user terminal is informed of the number of modifications and the smart log message is recommended before opening of the file. Log file management device.
delete delete

Images