KR20120090897A - System and method for managing wide usable document, mobile device for performing management of wide usable document - Google Patents

Abstract

PURPOSE: A universal document management system, a method thereof, and a mobile device performing the same are provided to increase the convenience of a user by connecting a converted universal document file through a URL(Uniform Resource Locator). CONSTITUTION: A first client transmits a document file. A conversion server(200) receives the document file and converts the document file into a universal document file. The conversion server generates link information on a web about the universal document file. A second client accesses the universal document file through the link information. The document file is a binary document file. The universal document file is a readable form on a web browser. The link information is distributed through a mobile communication network.

Description

Universal document management system, universal document management method, and mobile device for performing the same {SYSTEM AND METHOD FOR MANAGING WIDE USABLE DOCUMENT, MOBILE DEVICE FOR PERFORMING MANAGEMENT OF WIDE USABLE DOCUMENT}

The present invention relates to a general-purpose document management system, a general-purpose document management method, and a mobile device for performing the same. More particularly, the general-purpose document management system enables reading documents of various formats without installing a separate application program. A general document management method and a mobile device performing the same.

Recently, various mobile devices such as smartphones, PDAs, PMPs, MP3 players, tablet PCs, laptop computers, netbooks, etc. have gained popularity, and documents in various formats that were only available on desktop PCs can be viewed on mobile devices. It became.

Among document files containing certain information, binary document formats such as Korean (HWP) files, MS Word (DOC, DOCX) files, MS Excel (XLS, XLSX), PDF files, etc. In this case, since the text viewer provided by the platform cannot be read, a separate application that can read the file is required.

Domestic Patent Publication No. 2011-0081099 Domestic Patent Publication No. 2010-0071733

For example, if you send a schedule for a meeting from your smartphone as a text message, attach the meeting-related document file together and send it as a message, e.g. mail or text message (SMS, MMS, etc.) To view a file, you can view it only if a viewer is installed that can view the document file format.

In addition, a lot of information is also sent and received on social network services (SNS), such as Twitter (Twitter) and Facebook (Facebook), which provides a download address or a predetermined document directly through a URL link You can also provide a link to view.

In this case, if the viewer is not installed, you will need to pay a separate fee to install the viewer and view it, or download the message from another device with a viewer, such as a desktop or laptop PC, and view it. Inconvenience is caused.

The present invention has been conceived based on the above points, and the problem to be solved by the present invention is a general document management system, a general document management method and a mobile device for performing the same to view all document formats without installing a separate application Is to provide.

Another object of the present invention is to provide a general document management system, a general document management method, and a mobile device for performing the same, which can freely view a predetermined document file regardless of the device receiving the message.

The objects of the present invention are not limited to the above-mentioned objects, and other objects that are not mentioned will be clearly understood by those skilled in the art from the following description.

To solve this problem, the general-purpose document management system according to an embodiment of the present invention includes a client for transmitting a document file, the document file received from the client, and then converted into an HTML document and storing the HTML document. And a conversion server for generating and providing a URL which is stored location information, wherein the document file is in a binary document format.

According to another embodiment of the present invention, a general-purpose document management system includes a first client for transmitting a document file, and after receiving the document file, converting the document file into a universal document file, and converting link information on the web to the universal document file. Includes a conversion server to create.

A general-purpose document management system according to another embodiment of the present invention includes a first client for transmitting a document file, and after receiving the document file, converting the document file into a universal document file, and link information on the web to the universal document file. And a message relay service server configured to relay message transmission and reception between the first client and another client, wherein the first client attaches the document file to a message to be transmitted to the other client. The message relay service server transmits the document file to the conversion server to receive the link information, and adds the link information to a message to be transmitted to the other client.

A general-purpose document management method according to an embodiment of the present invention comprises the steps of: receiving a document file, converting the document file into a general document file, generating link information which is a location on the web where the universal document file is stored; And transmitting the link information.

According to another aspect of the present invention, there is provided a method of managing a general document, the method comprising: receiving link information which is location information on a general document file corresponding to a document file, generating a message including the link information, and receiving the message. Transmitting.

A mobile device according to an embodiment of the present invention, a message management module for managing a message transmitted and received, an attachment file management module for managing a document file attached to the message managed by the message management module, transmitting the message It includes a communication module for performing communication with the outside.

A more detailed example according to embodiments of the present invention will be described later in the embodiment section with reference to the drawings.

According to the present invention, after converting a predetermined document file, especially a document in binary form that cannot be viewed with a basic text viewer, into a general document file such as an HTML document file that can be basically viewed on all mobile devices, the corresponding general document file. Since the message is transmitted and received only by referring to the stored URL location, there is no need to install an application for a separate reading on the recipient side.

In addition, the once converted universal document file can be referred to repeatedly with only the URL location information, and the document creator can repeatedly transmit only the URL information to a plurality of others without transmitting a large document itself. The amount of data to be moved can be significantly reduced.

In addition, since the converted general-purpose document file can be accessed at any time on the Internet through a URL, user convenience is greatly increased.

The effects according to the present invention are not limited by the contents exemplified above, and more various effects are included in the present specification.

1 is a block diagram schematically illustrating a general document management system according to an embodiment of the present invention.
FIG. 2 is a flowchart showing an operation procedure of the general document management system of FIG. 1.
3 is a block diagram schematically illustrating a general-purpose document management system according to another embodiment of the present invention.
4 is a diagram illustrating a link information distribution and redistribution process of the general document management system of FIG. 3.
FIG. 5 is a diagram illustrating a process in which link information generated by the general document management system of FIG. 3 is limitedly disclosed on a social network service.
6 is a block diagram schematically showing a general document management system according to another embodiment of the present invention.
7 is a block diagram schematically illustrating a configuration of a client device according to embodiments of the present invention.

Advantages and features of the present invention and methods for achieving them will be apparent with reference to the embodiments described below in detail with the accompanying drawings. However, the present invention is not limited to the embodiments disclosed below, but will be implemented in various forms, and only the present embodiments are intended to complete the disclosure of the present invention, and the general knowledge in the art to which the present invention pertains. It is provided to fully convey the scope of the invention to those skilled in the art, and the present invention is defined only by the scope of the claims.

DETAILED DESCRIPTION Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings. &Quot; and / or "include each and every combination of one or more of the mentioned items. ≪ RTI ID = 0.0 >

Although the first, second, etc. are used to describe various components, it goes without saying that these components are not limited by these terms. These terms are used only to distinguish one component from another. Therefore, it goes without saying that the first component mentioned below may be the second component within the technical scope of the present invention.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. In the present specification, the singular form includes plural forms unless otherwise specified in the specification. As used herein, "comprises" and / or "comprising" does not exclude the presence or addition of one or more other components in addition to the mentioned components.

Unless otherwise defined, all terms (including technical and scientific terms) used in the present specification may be used in a sense that can be commonly understood by those skilled in the art. Also, commonly used predefined terms are not ideally or excessively interpreted unless explicitly defined otherwise.

Hereinafter, a general document management system according to an embodiment of the present invention will be described with reference to FIGS. 1 to 2.

1 and 2, the general document management system according to the present embodiment may include a client 100 and a conversion server 200, and in addition, the client mobile device 300 and the second mobile. Device 400, third mobile device 500, and the like.

The client 100 holds an original document file before conversion, for example, a DOC file, a HWP file, an XLS file, a PDF file, a PPT file, and the like, which are binary document files. The client 100 transmits to the conversion server 200 to convert the original document file retained (S110).

The conversion server 200 receiving the original document file converts the original document file into an HTML document (S120). The conversion server 200 loads a binary document file, extracts tag information and text information, and recombines the HTML document to generate a converted HTML document.

The converted HTML document may be stored in the conversion server 200 itself or stored in a separate document storage server or document storage database, and may be referred to by an URL that is an independent and identifiable Internet address (S130). In other words, when the URL is accessed from outside, the converted HTML document can be viewed.

In the present embodiment, a case where the URL of the converted HTML document is http://aaa.bb is described.

When the conversion server 200 completes the document conversion and URL generation, and transmits the URL information to the client 100 again (S140).

Upon receiving the URL information, the client 100 may directly transmit the URL information to another user, or copy the URL information to a mobile device based on another platform, and then send a message with the URL information from the mobile device to the other user. There is (S150).

In the example shown in FIG. 1, a message including URL information may be directly transmitted from the client device 100 of the user to the third mobile device 500, which is another device, and the URL information may be copied from the client 100. Then, the other mobile device 300 of the user may transmit a message including the URL information to the third mobile device 400 which is another device. The form of the message is not limited, and the URL information may be distributed in all manners such as an email, a short message (SMS), a multimedia message (MMS), and a messenger chat. In addition, the message may include all types of information uploaded on the SNS. For example, the URL information can be attached to a Mention or Direct Message posted on Twitter's Timeline and distributed to other users. Other forms of SNS, such as Me2Day, Cyworld, and LinkedIn, can send URL information, which is the address of an HTML document, to others.

The second and third mobile devices 400 and 500 that have received the message including the URL information may view the converted HTML document at any time by clicking the URL (S160). That is, the HTML document can be referred to by the URL. Since the HTML-type document can be accessed and viewed by all web browsers without any application on most existing mobile devices, the URL of the received message can be clicked. You can browse the HTML converted document page or redistribute the URL information by copying it.

In addition, since the receiver side only adds an additional amount of data corresponding to the length of the URL, the packet burden of the receiver can be reduced, and when necessary, the converted HTML document can be inquired anytime and anywhere. In the present embodiment, when the URL is http://aaa.bb , it is possible to receive HTML document information only with data of about tens of bytes. In particular, the URL information generated by the conversion server 200 may be converted into a short URL, thereby reducing the amount of data and increasing reference convenience.

Hereinafter, another embodiment of the present invention will be described with reference to FIGS. 3 to 5. FIG. 3 is a block diagram schematically illustrating a general document management system according to another embodiment of the present invention. FIG. 4 is a view illustrating a link information distribution and redistribution process of the general document management system of FIG. 3. FIG. 3 is a diagram for explaining a process of restricting disclosure of link information generated by the general-purpose document management system on a social network service.

According to another exemplary embodiment of the present invention, a general document management system includes a first client 100 for transmitting a document file, and after receiving the document file, converting the document file into a universal document file, and converting the document file into a universal document file. It includes a conversion server 200 for generating link information.

Unlike the above embodiment, the document converted by the conversion server 200 is not limited to the HTML document file, other types of documents that can be viewed universally is possible. For example, the universal document file may be a file type that is commonly supported on all platforms, and the general document file may be basically viewable even without an extension module installed on all kinds of web browsers. For example, the document file transmitted to the conversion server 200 may be converted into an HTML 5 file format, which is a next-generation web standard adopted by the web consortium (W3C) that is compatible with HTML and makes a web standard, in addition to the HTML file format.

In addition, the document file converted by the conversion server 200 does not necessarily need to be converted into the same document file, and may be converted into an image file including all information existing in the document file as necessary. For example, it may be converted into a JPEG or BMP file format, which is an image file format basically supported on an OS or a web browser. This conversion process may be performed by capturing the document file of the user as it is, or may be performed by a conversion process such as rendering. The general document file in the form of the converted image may be viewed with a basic image viewer installed on the user's platform.

The conversion server 200 may include a database or file server for storing the converted universal document file or generate a universal document file generated by being connected to the outside.

As described above, the converted universal document file may be referred to through the web protocol from the outside by predetermined link information. The client 100, which has transmitted the document file to the conversion server 200, may receive link information, which is an address on the web, that may access the general document file that has been converted.

For example, the link information may be a shortcut URL such as http: //ccc.dd that replaces the original URL address in a short form as shown in the example, but is not limited thereto. It may also be in the form of an address.

The client 100 distributes the received link information through a predetermined network. For example, the link information may be distributed through a mobile communication network or a wireless internet network. In other words, through a mobile communication network (2G, 3G, 4G) or a wired or wireless Internet network, to send a text message (SMS, MMS) containing the link information http: //ccc.dd to other clients, In the case of a messaging application that provides a separate message transmission service, for example, a message including link information is transmitted through an application such as kakao talk, my people, Whatsapp, or electronically. It can also be sent in the form of e-mail.

As such, other clients may access and view the general document file through the link information. In particular, since a general document file is in the form of a URL that can be accessed by a web browser, all document files can be distributed and viewed without installing a separate application with a single click.

Referring to FIG. 4, the transmitted link information may be redistributed to another user or another node. That is, once a general purpose document file is generated, it can be continuously referenced as long as the link information linking the general purpose document file is not lost, and can be accessed through various roots on the web.

For example, the first node 1010 that first generated the general document file may generate http: //ccc.dd , which is link information, and then distribute it to the second node 1020. Upon receiving the link information, the second node 1020 can access the general document file by using the link information, and the link information is again in the form of a message, an e-mail, and the like. May be redistributed). Although not shown, the third node 1030 and the fourth node 1040 may also redistribute link information to each connected node.

In the example shown in FIG. 4, a node may mean a device capable of connecting to a network, a user controlling a device, or a separate server / client connected to each other.

Referring to FIG. 5, link information may be distributed through a social network service. For example, the first user 2010 has a predetermined acquaintance with the second user 2020 to the sixth user 2060, and the first user 2010 converts the binary document file to the conversion server 200. Http: //hhh.ii , which is predetermined link information, can be generated.

A general social network service can establish a friendship between users, and defines a relationship with a direct friend as a first acquaintance (L1), a user who has a direct relationship with a user who has a direct relationship, that is, a step The relationship with the user who has acquaintances may be defined as the second acquaintance relation L2, and the relationship with the user who has acquaintances with the acquaintance two steps may be defined as the third acquaintance relation L3.

The first user 2010 may arbitrarily set an acquaintance of the user who can access the link information published by the first user 2010 to limit the user who can access the link information http: //hhh.ii .

For example, when the first user 2010 posts the link information to the social network service, and only the user with the first acquaintance L1 is configured to view the link information, the second to sixth users may access the link information. Only the user can access the link information.

In addition, when the first user 2010 is configured to view the link information to a user having a second acquaintance relationship L2, the second to ninth users may access the link information.

In this way, by restricting disclosure of link information for accessing a predetermined general document file according to intimacy between users on a predetermined social network service, only a desired user can be allowed to view a document generated by the user.

The method of limiting the link information may be to prevent access of the posting itself of the first user in which the link information is described, but is not limited thereto. The posting information of the first user may be accessed, but the corresponding link information may be limited. An authentication procedure may be granted to the user so that only a user authorized by the first user may pass the authentication process.

Hereinafter, another embodiment of the present invention will be described with reference to FIG. 6. 6 is a block diagram schematically showing a general document management system according to another embodiment of the present invention.

According to another embodiment of the present invention, a general-purpose document management system includes a first client 100 for transmitting a document file, and after receiving the document file, converting the document file into a universal document file, and converting the document file into a general document file. Including a conversion server 200 for generating link information of the first client 100, and further comprises a message relay service server 600 for relaying messages between the client 400, the first client 100 attaches the document file to a message to be transmitted to the other client 400 and transmits the document file to the message relay service server 600, and the message relay service server 600 transmits the document file to the conversion server 200. ) To receive the link information, and add the link information to a message to be transmitted to the other client 400 to transmit the link information.

The general document management system according to the present embodiment further includes a message relay service server 600 between the client 100 and the conversion server 200. That is, the client 100 does not directly transmit the document file to be converted to the conversion server 200, but the client 100 transmits a message to the other client 400 to the message relay service server 600. However, it may be transmitted in the form of attaching the document file to be transmitted to the other client (400).

In this case, the client 100 may select whether to convert the document file attached to the message while transmitting the message. When the document file is to be converted into a general document file, the selection information about the document file is transmitted to the message relay service server 600, and the message relay service server 600 transmits the document file to the conversion server 200. A general document file and link information thereof can be generated. The generated link information is transmitted to the message relay service server 600 again, and the message relay service server 600 receiving the received link information is added to the message transmitted by the client 100 to the other client 400. Send to. The other client may access the document file that the client 100 intends to transmit using the link information included in the received message.

When the client 100 transmits a message and wants to transmit the original document file to another client 400 without converting the document file attached to the message, the message relay service server 600 includes such selection information in the message. ), The message relay service server 600 may transfer the original message and the original document file to other clients 400 as they are.

In some embodiments, when the client 100 sends a message and a document file together to the message relay service server 600, the client 100 may be configured to automatically generate a general document file even if the client 100 does not select it.

The message relay service server 600 may be a message server of a mobile carrier for relaying transmitted and received messages, may be a message server (KakaoTalk server, etc.) of the third-party messaging application described above, and may be a mail server transmitting mail. In addition, it may be an SNS server that provides a social network service, but is not limited thereto. The server relaying all kinds of messages may correspond to the message relay service server 600.

Due to this configuration, the message relay service server 600 can reduce the load on the network in the process of receiving and sending a message to which the document file is attached, and the link information generated once will be referred to later. This can reduce unnecessary network traffic and greatly speed up access to documents.

Hereinafter, referring to FIG. 7, a configuration of a client 100 device constituting a general document management system according to embodiments of the present invention will be described. 7 is a block diagram schematically illustrating a configuration of a client device according to embodiments of the present invention.

The client 100 may include a communication module 110 and / or a network connection module 120 to transmit or receive communication or data with the outside, and the communication module 110 and / or the network connection module 120 may be a control module. 130 is controlled.

In addition to the communication module 110 and / or the network connection module 120, the control module 130 is connected to the message management module 140, the attachment file management module 150, and the link management module 160. Manage attachments, link information, and more.

The user may create a predetermined message to be transmitted to another user through the message management module 140, and select the document file to be transmitted to the other user by the attachment file management module 150. The attachment file management module 150 may perform a file upload function.

When the message file attached to the document file is generated and transmitted to the control module 130, the control module 130 transfers the message to the communication module 110 or the network connection module 120.

In this process, the control module 130 may perform a process of encoding or compressing the message and / or document file for transmission on the network.

The message to which the document file is attached is transmitted to another user via the mobile communication network through the conversion server 200 by the communication module 110 or through the wired or wireless network by the network connection module 120. It can be delivered to other users via.

After the conversion server 200 converts the document file into a general document file such as an HTML document file, link information for referencing the general document file can be generated and added to the message and transmitted to another user. The link information may be delivered to the client 100 that sent the message.

The transmitted link information is managed by the link management module 160, and the process of attaching the attached file by adding only the link information later when sending the message again from the client 100 may be omitted.

Although the embodiments of the present invention have been described with reference to the accompanying drawings, the present invention is not limited to the above embodiments, and may be manufactured in various forms within the scope of the present invention, and the present invention Those skilled in the art will understand that it can be implemented in other specific forms without changing the technical spirit or essential features of the present invention, the embodiments described above are exemplary in all respects and limited It is not limited to form.

100: client
200: conversion server
300: client mobile device
400: second client
500: third client
600: message relay service server

Claims (21)

A first client for transmitting a document file; And
And a conversion server for receiving the document file and converting the document file into a general document file and generating link information on the web for the general document file. The method of claim 1,
And a second client for accessing and viewing the universal document file via the link information. The method of claim 1,
The document file is a general document management system, which is a binary document file. The method of claim 1,
The general purpose document file is a general-purpose document management system in a form that can be viewed on a web browser. The method of claim 4, wherein
The general purpose document file is an HTML document file. The method of claim 1,
And the link information is in the form of a shortcut URL. The method of claim 1,
And the first client receives the link information. The method of claim 1,
The link information is distributed over a mobile communication network or a wireless Internet network, universal document management system. The method of claim 1,
Wherein the link information is distributed via a message transfer service. The method of claim 1,
The link information is distributed via a social network service. The method of claim 1,
And a message relay service server configured to relay message transmission and reception between the first client and another client. The method of claim 11,
And the first client attaches the document file to a message to be transmitted to the other client and transmits the document file to the message relay service server. The method of claim 12,
The message relay service server transmits the document file to the conversion server to receive the link information.
And add the link information to a message to be transmitted to the other client. Receiving a document file;
Converting the document file into a general purpose document file;
Generating link information which is a location on the web where the universal document file is stored; And
And transmitting the link information. The method of claim 14,
And said document file is a binary document file. The method of claim 14,
The general purpose document file is a form that can be viewed on a web browser. Receiving link information which is location information on a general purpose document file corresponding to the document file;
Generating a message including the link information; And
Sending the message. 18. The method of claim 17,
Distributing the link information on a social network service. A message management module managing a message to be transmitted and received;
An attachment file management module for managing a document file attached to the message;
A mobile device comprising a communication module for performing communication with the outside to transmit the message. 20. The method of claim 19,
Further comprising a network connection module for connecting to a wired or wireless network,
The message is transmitted via the network connection module. 20. The method of claim 19,
The mobile device of claim 1, further comprising a link management module configured to manage link information of a general document file corresponding to the document file.

Images