Patent ID: 12235804

DETAILED DESCRIPTION

Hereinafter, example embodiments of the present disclosure will be described with reference to the attached drawings. Advantages and features of the present disclosure and methods of accomplishing the same may be understood more readily by reference to the following detailed description of example embodiments and the accompanying drawings. The present disclosure may, however, be embodied in many different forms and should not be construed as being limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete and will fully convey the concept of the disclosure to those skilled in the art, and the present disclosure will be defined by the appended claims and their equivalents.

In describing the present disclosure, when it is determined that the detailed description of the related well-known configuration or function may obscure the gist of the present disclosure, the detailed description thereof will be omitted.

Hereinafter, embodiments of the present disclosure will be described with reference to the attached drawings:

FIG.1is a configuration diagram of a document sharing system100according to an embodiment of the present disclosure.

Referring toFIG.1, the document sharing system100according to this embodiment may include a document management server110, a sharing management server120, a keyword management server130, and a token management server140.

The document management unit110may receive a document sharing request from the user10and provide a page list of the document. Here, the user10is a document sharing requester, and may be a document creator or a document owner.

According to one embodiment, the document may be an electronic document in a PDF file format. If the document is not in a PDF file format, it may be converted into a PDF file format by a PDF converter included in a backend system (not shown) of the document sharing system100.

According to an embodiment, the document management unit110may receive a sharing request for a sharing request page from the user10. Here, the sharing request page refers to a page that is selected and requested to be shared by the user10from the page list of the document provided by the document management unit110. In this case, the sharing request page may be a plurality of pages.

The sharing management unit120may receive a sharing target page and a request for designating a sharing target from the user10. Here, the sharing target page may refer to a page determined as a page to be shared among sharing request pages by a document sharing requester. In addition, the user10may be a sharing requester who requests to designate a sharing target page and a sharing target. Alternatively, the user10may be another user designated as a document sharing target by a document sharing requester, to whom the document is to be shared.

According to an embodiment, the sharing management unit120may register a token corresponding to the sharing target page generated by the token management unit140and may store the sharing target page. In addition, a sharing target token registration result for a sharing target may be provided to the document sharing requester.

The keyword management unit130may receive a keyword check request for the sharing request page of the document management unit110, perform keyword check of the sharing request page, and transmit the keyword check result to the document management unit110. Here, various conventional keyword extraction algorithms may be used as the keyword checking method.

According to one embodiment, the keyword may be any one of one or more words registered in advance.

According to one embodiment, the keyword may be any one of one or more words stored and managed in a file indexing format in a database of a backend system (not shown) of the document sharing system100.

According to an embodiment, the keyword may be one or more words including important company information included in the document, such as compliance information, key technical terms, or confidential information included in the document.

The token management unit140may generate a token corresponding to the keyword by receiving a token generation request from the keyword management unit130when a keyword is extracted as a result of the keyword check for the sharing request page of the keyword management unit130.

According to one embodiment, the token may be an authentication token generated by the token management server140and stored in the token management server140.

For example, the token may be an authentication token for granting access permission to a website or application based on an open standard protocol for authentication such as Open Authorization.

According to an embodiment, the sharing request page may be locked by the document management unit110according to a lock processing method based on attributes of keywords using the token generated by the token management unit140.

According to an embodiment, the lock processing method according to the attribute of the keyword may be any one of a method of hiding the sharing request page when the first keyword is included in the sharing request page, a method of displaying the entire sharing request page as locked when the second keyword is included in the sharing request page, and a method of displaying only a region as locked where the third keyword of the sharing request page is displayed when the third keyword is included in the sharing request page.

Here, the attributes of the keywords may be attributes classified according to importance of main technical information or compliance information. For example, if the first keyword, which has the highest importance among the key technical information keyword data stored in the database of the document sharing system100, is included in the sharing request page, the sharing request page may be hidden, and if the third keyword, which has the lowest important, is included in the sharing request page, only a region may be displayed as locked where the third keyword of the sharing request page is displayed.

According to one embodiment, attributes of keywords may be attributes classified according to a predefined grouping method of keyword data.

According to the above-described embodiments, a document may be shared by each page unit of the document, and security issues regarding a document may be prevented in advance through keyword extraction of company internal key information and compliance information.

In addition, according to the above-described embodiments, an effect of improving storage management of unnecessary edited documents is provided through the permission management of a document by page unit without generating additional documents.

In addition, according to the above-described embodiments, an effect of automatically locking a document by the system according to importance is provided. In addition, by changing the lock processing method of the sharing request page according to the attribute of the keyword, the user may easily identify the importance of the contents included in the document to be shared.

According to an embodiment, when a plurality of keywords are included in the sharing request page, a lock processing method may be determined according to a predefined priority order. An embodiment of a lock processing method according to priority will be described later with reference toFIG.7.

According to an embodiment, the compliance system20requests the keyword management unit130to check keywords for documents stored in the document management unit110of the document sharing system100, and automatically locks the document. In this case, documents stored in the document sharing system100are automatically locked by the compliance system20, thereby providing an effect of increasing the security level of the document sharing system100.

The document sharing system100described above may be implemented with one or more computing devices having a processor. For example, each component such as the document management unit110may be implemented as one computing device, or a plurality of components or the document sharing system100may be implemented as one computing device. A computing device may refer to any device having a computing function, and an example of such a device may be referred toFIG.12.

Next, a method of sharing a document by each page according to another embodiment of the present disclosure will be described with reference toFIGS.2to9. The method of sharing a document by each page according to the present embodiment may be performed by one or more computing devices. For example, in the document sharing method by each page according to the present embodiment, all operations may be performed by one computing device, or some operations may be performed by another computing device. Hereinafter, it will be described on the assumption that the method described below is performed by the document sharing system100illustrated inFIG.1. Therefore, in the following description, if the description of the subject of performing some operations is omitted, it would be understood that they are performed by the document sharing system100.

FIG.2is a flowchart of a method of sharing a document by each page according to another embodiment of the present disclosure.

In step S100, a document sharing request of the document sharing requester is received by the document sharing system100. In this case, the document may be a document stored in the document sharing system100or a document uploaded by a document sharing requester.

In step S200, the document sharing system100may receive a document sharing request from a document sharing requestor (S100) and provide a page list of a document requested for sharing to the document sharing requester.

In step S300, a sharing request for a sharing request page may be received. Here, the sharing request page may be a page requested for sharing by the document sharing requester selecting a page to request sharing from a page list of a sharing requested document provided to the document sharing requester.

In step S400, a sharing request for a sharing request page of a document is received (S300), and the keyword check for the sharing request page may be automatically performed. Here, the keyword may be any one of one or more words registered in advance.

FIG.3is a detailed flowchart illustrating an embodiment of a method for checking a keyword of a sharing request page described with reference toFIG.2. Referring toFIG.3, it is determined whether the number of keywords in the sharing request page is equal to or greater than a reference value (S410a). If the number of keywords is less than the reference value, the keyword check result for the sharing request page is provided without any other indication (S430a). If the number of keywords included in the sharing request page is equal to or greater than the reference value, a warning indication may be added to the sharing request page (S420a), and keyword check results may be provided (S430a).

Here, the keyword check result may be the number of keywords included in the sharing request page, the number of keywords grouped and distinguished based on the attribute of the keyword, or a sharing request page and a list of sharing request pages, for which a warning indication is displayed on the sharing request page.

According to the above-described embodiment, when the sharing request page includes keywords equal to or greater than the reference value, it is treated as a document of high importance, and thus, an effect, in which a sharing requestor may easily identify it and finally determine whether to share the document, is provided.

Referring back toFIG.2, in step S500, a token may be generated for the keyword extracted from the sharing request page according to the keyword check result, and the locking process may be performed on the sharing request page using the generated token.

According to an embodiment, the document sharing system100may store a token generated for a keyword extracted from the sharing request page in the document sharing system100.

Referring toFIGS.4to7, various embodiments of a lock processing method based on keyword attributes included in the sharing request page in step S500ofFIG.2will be described.

FIG.4is a flowchart illustrating a keyword lock processing method according to an embodiment of the present disclosure. Referring toFIG.4, when a keyword check is performed on the sharing request page (S400) and the first keyword is included in the sharing request page as a result of the keyword check (S510a), a first token for the first keyword is generated, and the sharing request page may be hidden using the first token (S520a). In this case, the entire sharing request page within the document is hidden and invisible.

According to an embodiment, a keyword check result, and a keyword-locked sharing request page, and a list of keyword-locked sharing request pages may be provided to a sharing requester. In this case, the sharing requester may refer to the provided keyword check result and the list of locked sharing requested pages, etc., and finally determine the sharing target page later.

FIG.5is a flowchart illustrating a keyword lock processing method according to an embodiment of the present disclosure. Referring toFIG.5, when a keyword check is performed on the sharing request page (S400), and the second keyword is included in the sharing request page as a result of the keyword check (S510b), a second token for the second keyword is generated. And, the sharing request page may be displayed as locked using the second token (S520b). In this case, the entire sharing request page within the document is displayed as locked.

FIG.6is a flowchart illustrating a keyword lock processing method according to an embodiment of the present disclosure. Referring toFIG.6, a keyword check is performed on the sharing request page (S400), and if the third keyword is included in the sharing request page as a result of the keyword check (S510c), a third token for the third keyword is generated, the third keyword display region of the sharing request page may be displayed as locked using the third token (S520c). In this case, the rest of the region except for the third keyword display region of the corresponding sharing request page is displayed as opened to public.

According to the above-described embodiments, when sharing of a page of a document is requested, an effect of automatically locking a sharing request page including a keyword is provided. In addition, by changing the lock processing method of the sharing request page according to the attribute of the keyword, the user may easily identify the importance of the contents included in the document to be shared.

FIG.7is a flowchart illustrating a keyword lock processing method when a plurality of keywords exist in a sharing request page according to an embodiment of the present disclosure ofFIG.2. Referring toFIG.7, it is determined whether the first keyword is included in the sharing request page (S510d). If the first keyword is included, the sharing request page may be hidden (S540d). If the first keyword is not included in the sharing request page, it is determined whether the second keyword is included in the sharing request page (S520d). If the second keyword is included, the sharing request page is displayed as locked (S550d). If the second keyword is not included, it is determined whether the third keyword is included in the sharing request page (S530d). If the third keyword is included, only the third keyword display region of the sharing request page is displayed as locked (S560d). If the third keyword is not included, the entire sharing request page is displayed as opened to public (S570d).

Here, the first to third keywords may be words determined according to a grouping method of keyword data registered in advance based on keyword attributes. For example, the first keyword may be information of high importance, the second keyword may be information of medium importance, and the third keyword may be information of low importance. In this case, according to the priority order, the sharing request page including the first keyword is hidden regardless of whether the second keyword and the third keyword are included.

According to the above-described embodiment, when there are a plurality of keywords in a sharing request page, an effect of automatically determining a lock processing method according to a predetermined priority based on attributes of the keywords is provided.

Referring back toFIG.2, in step S600, the sharing target page is shared with the sharing target.

Hereinafter, with reference toFIGS.8and9, an embodiment of a method for sharing a sharing target page with a sharing target in step S600ofFIG.2will be described.

FIG.8is a flowchart illustrating a method for sharing a sharing target page according to an embodiment of the present disclosure. Referring toFIG.8, a sharing requester determines a sharing target page among sharing request pages based on a keyword check result and a list of locked sharing request pages, and the document sharing system100may receive the sharing request of the determined sharing target page from the document sharing requester (S610).

According to an embodiment, the document sharing requester may designate a sharing target for each sharing target page and request the document sharing system100for a sharing target page for each sharing target.

According to the above-described embodiment, a document sharing requester designates a sharing target and shares for each target page, thereby simplifying a work process and sharing some pages of a document without additional document editing.

The document sharing system100may receive a sharing request for a sharing target page from a document sharing requester and register a token generated for a keyword included in the sharing target page as a sharing target token (S620). In this case, the tokens generated for keywords included in the sharing target page are tokens generated for keywords extracted as a result of keyword check on the sharing request page, and it may be some of the tokens stored in the document sharing system100.

According to an embodiment, the sharing target token may be a token registered as a sharing target token for a sharing target by mapping a token generated with respect to a keyword included in the determined sharing target page to each designated sharing target.

After that, the document sharing system100may refer to the sharing target token and transmit data for viewing the sharing target page to the terminal of the sharing target (S630). Here, the data for viewing the sharing target page may be, for example, PDF format data.

FIG.9is a flowchart illustrating in detail the operation of the method for transmitting data for viewing a sharing target page to a terminal of a sharing target described with reference toFIG.8.

Referring toFIG.9, first, an inquiry request for a sharing target page is received from a sharing target (S631). At this time, it is determined whether the locking process is performed on the sharing target page, which is requested to inquiry by the sharing target (S632). If the locking process is not performed, the sharing target may view the sharing target page (S635). If the locking process is performed, it is determined whether a sharing target token for the corresponding sharing target page is registered with the sharing target (S633). If the sharing target token is not registered, the document sharing system100may display the corresponding sharing target page in a locked state to the sharing target (S636). When the sharing target token is registered, the locking process of the sharing target page is released (S634), and the sharing target may view the sharing target page (S635).

For example, if a sharing target page is locked only in the keyword region, and if a sharing target token is not registered with the sharing target, the sharing target may view the contents of the sharing target page except for the keyword region.

For example, if the sharing target page is in a hidden state and the sharing target token is not registered with the sharing target, the sharing target page may be displayed in a locked state to the sharing target.

FIGS.10and11are signal flow diagrams for describing a method for sharing a document by each page according to an embodiment of the present disclosure operating in the document sharing system100described with reference toFIG.1.

FIG.10is a signal flow diagram illustrating an automatic keyword lock processing method according to a document sharing request according to an embodiment of the present disclosure.

Referring toFIG.10, a document sharing request is transmitted to a document management unit by a user (S11). The document management unit may receive a user's document sharing request (S11) and provide a page list to the user (S12). In this case, each page may be displayed together with the page list. Here, the user may be a document sharing requester.

The user may refer to the provided page list, select a page to request sharing, and then transmit a page sharing request to the document management unit (S13). The document management unit may transmit a keyword check request for the sharing request page to the keyword management unit (S14). The keyword management unit may perform keyword check on the sharing request page and transmit the keyword check result to the document management unit (S16). At this time, the document management unit may provide the keyword check result to the user (not shown).

After performing the keyword check, the keyword management unit may request the token management unit to generate a token for the corresponding keyword (S17). After receiving the token generation request, the token management unit may generate a token for a keyword (S18). At this time, the token management unit may store the generated token in the token management unit.

After the token is generated, the token management unit may request keyword locking process using the generated token to the document management unit (S19), and the document management unit may perform keyword locking process for a sharing request page, from which keywords are extracted, according to a lock processing method based on keyword attributes.

FIG.11is a signal flow diagram illustrating a method of registering a sharing target token for a sharing target according to an embodiment of the present disclosure.

First, the document sharing requester may refer to the keyword check result and the list of locked sharing request pages to determine the sharing target page, and then transmit a sharing target page and a request for designating a sharing target to the sharing management unit (S21).

The sharing management unit may request a token corresponding to the keyword included in the sharing target page from the token management unit (S22). The token management unit may generate a token corresponding to the sharing target page and transmit it to the sharing management unit (S23). In this case, the token to be transmitted may be a token generated in advance according to a keyword check result and stored in the token management unit.

The sharing management unit that has received the token may register the sharing target token for the sharing target page with respect to the sharing target. According to an embodiment, the sharing management unit may store the corresponding sharing target page, in which the sharing target token is registered, in the sharing management unit (S24).

After registering the sharing target token and storing the sharing target page, the sharing management unit may transmit the sharing target token registration result to the document sharing requester (S25).

Thereafter, the sharing target page stored in the sharing management unit may be viewed by the sharing target according to the above-described process.

According to the above-described embodiments, using a secure authentication token managed by the token management unit140of the document sharing system100, documents may be shared without additional document creation, thereby providing an effect of simplifying work processes.

FIG.12is a hardware configuration diagram of an exemplary computing device capable of implementing document sharing system100according to some embodiments of the present disclosure. As shown inFIG.12, the computing device1000may comprise one or more processors1100, a system bus1600, a communication interface1200, a memory for loading a computer program1500executed by the processor1100, and a storage1300for storing the computer program1500.

The processor1100controls the overall operation of each component of the computing device1000. The processor1100may perform an operation for at least one application or program for executing a method/operation according to various embodiments of the present disclosure.

The memory1400stores various data, commands and/or information. The memory1400may load one or more computer programs1500from storage1300to execute methods/operations according to various embodiments of the present disclosure.

The storage1300may non-temporarily store one or more computer programs1500.

The computer program1500may include one or more instructions, in which methods/operations according to various embodiments of the present disclosure may be implemented. When the computer program1500is loaded into the memory1400, the processor1100may execute the one or more instructions to perform methods/operations according to various embodiments of the present disclosure.

The computer program1500includes, for example, instructions for receiving a sharing request for a sharing request page of a document and automatically performing a keyword check for the sharing request page, an instruction for generating a token for a keyword extracted from the sharing request page as a result of the keyword check and performing a locking process for the sharing request page using the token, and an instruction for determining a sharing target page among the sharing request pages and designating a sharing target to share the sharing target page. In this case, the document sharing system100according to an embodiment of the present disclosure may be implemented through the computing device1000.

So far, a variety of embodiments of the present disclosure and the effects according to embodiments thereof have been mentioned with reference toFIGS.1to12. The effects according to the technical idea of the present disclosure are not limited to the forementioned effects, and other unmentioned effects may be clearly understood by those skilled in the art from the description of the specification.

The technical features of the present disclosure described so far may be embodied as computer readable codes on a computer readable medium. The computer readable medium may be, for example, a removable recording medium (CD, DVD, Blu-ray disc, USB storage device, removable hard disk) or a fixed recording medium (ROM, RAM, computer equipped hard disk). The computer program recorded on the computer readable medium may be transmitted to other computing device via a network such as internet and installed in the other computing device, thereby being used in the other computing device.

Although operations are shown in a specific order in the drawings, it should not be understood that desired results may be obtained when the operations must be performed in the specific order or sequential order or when all of the operations must be performed. In certain situations, multitasking and parallel processing may be advantageous. According to the above-described embodiments, it should not be understood that the separation of various configurations is necessarily required, and it should be understood that the described program components and systems may generally be integrated together into a single software product or be packaged into multiple software products.

In concluding the detailed description, those skilled in the art will appreciate that many variations and modifications may be made to the example embodiments without substantially departing from the principles of the present disclosure. Therefore, the disclosed example embodiments of the disclosure are used in a generic and descriptive sense only and not for purposes of limitation.