KR20090099874A - System and method for file distribution using messenger - Google Patents

Abstract

PURPOSE: A file distribution system using a messenger and a method thereof including a file distribution unit are provided to distribute the file stably and efficiently by using an internet messenger system capable of communicating with the other user. CONSTITUTION: A data distribution method is as follows. It confirms whether the data is existed as clients(101,103,105,107) connecting to a server. The server determines the distribution form for distributing at the client who it connects data to a server data to be distributed at the client who confirmation result data of the first step connects to a server exist. The server transmits the client whose the distribution form determined in the second step connects the included distribution command to the server.

Description

File Distribution System using Messenger and its method {SYSTEM AND METHOD FOR FILE DISTRIBUTION USING MESSENGER}

The present invention relates to file distribution, and more particularly, to a file distribution system and a method using a messenger.

Korean Patent Publication No. 10-2006-0072422 published on June 28, 2006 as a related art for file distribution [Name: Peer-to-peer distribution method in the network area for efficient automatic distribution and installation of a specific program. And its production method and software asset and patch management system.

The prior art divides a plurality of client systems connected to the network into a predetermined number of groups, assuming a broadcasting environment, for example, a LAN environment, which is broadcastable. To distribute and install certain programs to the remaining clients of the group.

According to the related art, it is possible to distribute network traffic concentrated on a server in which the predetermined program is stored and to secure stability of an automatic program installation service provided by the server.

However, since the conventional technology is a technology that can be applied only to a broadcastable environment (LAN), it cannot be applied to a client universally connected to the Internet.

Accordingly, there is a need for a technique capable of reliably distributing and distributing files even for a client universally connected to the Internet, overcoming the limitations of the prior art.

Accordingly, the present invention has been made to meet the above demands, and provides a file distribution system and method for efficiently and reliably distributing files using an Internet messenger system capable of communicating with other users regardless of location. The purpose is to provide.

Those skilled in the art to which the present invention pertains can easily recognize other objects and advantages of the present invention from the drawings, the detailed description of the invention, and the claims.

In order to achieve the above object, the present invention provides a data distribution method for distributing data to a plurality of clients connected to a server, the method comprising: checking whether data to be distributed to clients connected to the server exists; step; A distribution method for distributing the data to a client accessing the server when the data to be distributed to the client accessing the server exists as a result of the checking of the first step; A first method of distributing the data from a server, a second method of distributing the data from another client in a messenger buddy relationship with a client connected to the server, or a method of distributing the data from another client in the buddy relationship with the server Including at least one of three ways; And a third step of transmitting, by the server, a distribution command including a distribution method determined in the second step, to a client accessing the server.

In order to achieve the above object, the present invention provides a data distribution system for distributing data to a client, comprising: data distributing means for storing data to be distributed to the client; Messenger service means for managing information of another client having a messenger buddy relationship with the client and performing a messenger service; Distribution information management means for managing history information of data distributed to the client; Distribution method for distributing to the client The distribution method includes a first method of distributing the data from the data distributing means and a second method of distributing the data from another client having a messenger buddy relationship with the client; Distribution method determining means for determining one or more of third ways to distribute the data from other clients in the buddy relationship; And command transmitting means for transmitting a distribution command including the determined distribution method to the client.

In addition, to achieve the above object, the present invention provides a client system for accessing the data distribution system, comprising: command receiving means for receiving a distribution command transmitted from the data distribution system; Data receiving means for receiving the data from the data distributing means or distributing the data from another client having a messenger buddy relationship with the client system according to a distributing method included in the received distributing command; And data management means for storing and managing data distributed by the data receiving means.

The present invention also provides a data distribution method for distributing data, comprising: a first step of checking whether or not there is data to be distributed to a client connected to a server; A second step of confirming whether the data to be distributed exists in another client having a messenger buddy relationship when there is data to be distributed to a client accessing the server as a result of the checking of the first step; Distribution method for distributing the data when the data exists in the other client, The distribution method is a first method of distributing the data from the server, from the other client having a messenger buddy relationship with the client connected to the server And at least one of a second manner of distributing the data or a third manner of distributing the data from the server and other clients in the buddy relationship.

According to the present invention, if an Internet connection is available, a file can be distributed among messenger clients using a messenger system that can communicate with other users regardless of location, thereby distributing resources necessary for the file distribution and making the file efficient and stable. Distributed distribution.

The following merely illustrates the principles of the invention. Therefore, those skilled in the art, although not explicitly described or illustrated herein, can embody the principles of the present invention and invent various devices that fall within the spirit and scope of the present invention. In addition, all conditional terms and embodiments listed herein are in principle clearly intended to be understood only for the purpose of understanding the concept of the invention and are not to be limited to the specifically listed embodiments and states. do. In addition, it is to be understood that all detailed descriptions, including the principles, aspects, and embodiments of the present invention, as well as listing specific embodiments, are intended to include structural and functional equivalents of these matters. In addition, these equivalents should be understood to include not only equivalents now known, but also equivalents to be developed in the future, that is, all devices invented to perform the same function regardless of structure.

 The above objects, features and advantages will become more apparent from the following detailed description taken in conjunction with the accompanying drawings. First of all, in adding reference numerals to the components of each drawing, it should be noted that the same components have the same number as much as possible even if displayed on different drawings. In addition, in describing the present invention, when it is determined that the detailed description of the related known technology may unnecessarily obscure the subject matter of the present invention, the detailed description thereof will be omitted. Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings.

Internet Messenger (Instant Messenger) service mentioned in the present specification, unlike the e-mail has been used in the current communication service using the Internet with the advantage that the real-time message can be transmitted. The current messenger service provides not only text transmission but also various functions such as URL transmission, group chat, file transmission, and additional information such as stocks, traffic, weather, games, wired / wireless interworking services, voice chat, and video chat. Additional service functions are integrated and provided. Therefore, messenger service is expected to develop further based on interworking between different types of real-time communication, various additional functions, etc., which are differentiated from e-mail, which is the most powerful communication means in daily life and corporate activities. The messenger service allows the sending and receiving clients to exchange messages in real time. The messenger service network consists of a messenger server and a plurality of messenger clients. The messenger client exchanges messages with the messenger server. Each messenger client may have a buddy relationship with another messenger client, and the messenger server manages the buddy information.

According to the present invention, for some of the messenger clients connected to the file distribution system via the Internet while the file for distribution is stored in the file distribution server including the messenger server function, the file is directly transmitted from the file distribution system. The remaining messenger client connected to the file distribution system is distributed from a messenger client that has already received and stored the file as a messenger client having a buddy relationship with the messenger client.

According to the present invention, it is possible to reduce the load of the file distribution system by allowing the file to be distributed, for example, in a P2P manner among messenger clients. In addition, when a P2P file distribution is difficult between messenger clients, such as when the local network to which the messenger client belongs is protected by a firewall, file distribution between messenger clients is possible through a file relay means included in the file distribution server. P2P communication is a one-to-one communication between clients that does not depend on the server. It is a form that all participants become suppliers and consumers by directly connecting and retrieving clients from the existing server and client concept or supplier and consumer concept. The P2P network structure has a long history of being adopted as a core technology since the early version of the Internet Protocol Request for Comments (RFC) enacted on April 7, 1969. A peer-to-peer network, or peer-to-peer network, is a network that depends on the computation and bandwidth capabilities of the clients that make up the network, rather than focusing on relatively few servers. File sharing via P2P communication is very common. P2P communication method, such as Napster in the US and Sori Sea in Korea, has a centralized list of contents related to the content and provides client-to-client access and sharing, or overseas KaZaA, Limewire, and domestic Like Guru Guru, the central server does not have content information, but provides tools for access and sharing between individuals, and the distributed processing of the server is applied to the P2P network so that some downloaded files are shared again with other clients. Many configurations.

Here, when the file is distributed from a buddy, the file may be divided and distributed from a plurality of buddies storing the file. The split-distributed files are combined at the receiving client. When a file is divided and distributed, a load of a buddy that stores the file, that is, a messenger client, may be reduced, and a messenger client that divides and distributes the file may be offline, even if the buddy is offline. By re-requesting only the necessary portion of the file can be distributed efficiently. The divided distribution amount may be determined according to, for example, a transmission speed between a buddy distributing the file and a messenger client distributing the file. In this case, by setting a large amount of distribution for a bird with a high transmission speed, the transmission time can be reduced and the network environment can be efficiently used.

The file distributed to the messenger client may be stored in the messenger client for a predetermined period of time for distribution, for example, until the distribution expiration date of the file.

Meanwhile, the file distributed to the messenger client may be installed or patched in the messenger client.

In addition, a hash algorithm such as message-digest algorithm 5 (MD5) or secure hash algorithm (SHA) may be applied to ensure the integrity of the file. MD5 is a cryptographic hash function that provides a 128-bit hash. Designated as RFC 1321, it is used to check the integrity of many programs and files. SHA functions are a collection of cryptographic hash functions associated with each other. These functions were first designed by the US National Security Agency (NSA) in 1993 and have been set as US national standards. The first function in the SHA family of functions is officially called SHA, but it is also called SHA-0 to distinguish it from later designed functions. Later, SHA-1, a variant of SHA-0, was released, followed by four more variants: SHA-224, SHA-256, SHA-384, and SHA-512. These are collectively referred to as SHA-2. SHA-1 is the most common of the SHA functions.

1 is a schematic diagram illustrating a file distribution system according to an embodiment of the present invention. As shown in FIG. 1, a file distribution system according to an exemplary embodiment of the present invention includes a plurality of messenger clients 101 to 107 that can be connected to a file distribution server 109 through the Internet. Here, it is assumed that the plurality of messenger clients 101 to 107 are registered as buddies with each other.

The file distribution server 109 includes a messenger session means 111, a file distribution means 113, and a file relay means 115. Although FIG. 1 illustrates that the messenger session means 111, the file distribution means 113, and the file relay means 115 are all included in the file distribution server 109, they may be physically located at different locations.

The file relay means 115 performs a file relay function between messenger clients that is performed in a typical messenger system. According to the present invention, when it is difficult to distribute a P2P file between messenger clients 101 to 107, such as when the local network to which the messenger client belongs is protected by a firewall, the file may be distributed between messenger clients through the file relay means 115. Do it.

The file distributing means 113 includes a file storage unit for storing a file to be distributed to the messenger clients 101 to 107 according to the present invention. The file stored in the file distribution means 113 may be, for example, an installation file or a patch file of a program for a specific service. The patch file may include patch application data for performing file patching and patch data required for file patching. A patch application is an application that independently executes a file patch, such as installing a new program or copying patch data to a specific directory. As described above, a file stored in the file distribution means 113 may be applied with a hash algorithm such as MD5, SHA, etc. to ensure integrity. Therefore, the file distributing means 113 may mount a hash encryption unit for generating a file hash by encrypting the stored file according to a predetermined hash algorithm.

The messenger session means 111 mounts a messenger service unit to manage information of other messenger clients 103 to 107 which are buddies of the messenger client 1 101, and performs a normal messenger session server function. Thus, for example, the messenger client 1 (101) exchanges messages with other messenger clients (103 to 107) authenticated and connected through the messenger service unit of the messenger session means (111) and registered as a buddy of the messenger client 1 (101). The file may be exchanged through the file relay means 115.

According to an embodiment of the present invention, the messenger session means 111 may distribute, for example, a file to be distributed to the connected messenger client 1 101 through the file distributing means 113 or the buddy 103 to the 107) to decide whether to distribute. Therefore, the messenger session means 111 may have a determining unit that determines the distribution method. Meanwhile, according to another exemplary embodiment of the present invention, the determination unit may be mounted in each of the messenger clients 101 to 107. The determination of the distribution method is performed when the messenger client 1 (101) connects to the messenger session means 111 and is included in a file distribution command transmitted to the messenger client 1 (101) according to an embodiment of the present invention. The file distribution command is transmitted to the messenger clients 101 to 107 by a command transmitter mounted on the messenger session means 111. On the other hand, according to another embodiment of the present invention, the messenger clients 101 to 107 do not need to receive the file distribution command because the decision unit performing the determination is mounted in each of the messenger clients 101 to 107. In this case, the command transmitter is unnecessary.

The determination may be performed according to various policies.

In one embodiment of the determination may be determined according to the distribution policy according to the access rate. That is, a messenger client having a predetermined ratio (for example, 10%) among the messenger clients that are currently connected to receive the file through the file distribution means 113, and the messenger client having the remaining ratio (90% in the above example) is a buddy. It can be determined to distribute the file through. The distribution policy according to the access ratio increases the ratio of the messenger client receiving the file through the file distribution means 113, but the transmission load of the file distribution means 113 increases, but there is an advantage that the file distribution can be performed quickly. . On the other hand, in order to maximize the advantages of distributed distribution, that is, file distribution through the buddy, the number of clients distributed from the file distribution means 113 should be reduced, and the number of clients receiving files distributed through the buddy should be increased.

As another embodiment of the determination, it may be determined according to a distribution policy according to the number of buddies of the messenger client. In other words, for a messenger client having a predetermined number (for example, 10 or more), the file is distributed through the file distribution means 113, and for a messenger client having a buddy having a predetermined number (for example, 10) of the buddy. Can be determined to distribute files. In the initial stage of file distribution (a predetermined period from when the file is first distributed), if a file having a large number of buddies can be preferentially distributed from the file distribution unit 113, the file is distributed through a buddy. The probability of that increases.

As another embodiment of the determination, the file is distributed through a buddy to a client having a large number of currently connected buddies, and the file is distributed through a file distribution means 113 to a client having a small number of buddies currently connected. Can be determined to be distributed.

As another embodiment of the determination, it may be determined to distribute the file through a buddy for a predetermined period from a time when the file is first distributed, and to distribute the file through the file distribution unit 113 after the predetermined period.

Although some embodiments of the crystal according to the present invention have been introduced in the present specification, the present invention is not limited to only some of the embodiments, and various embodiments related to the crystal may exist, having ordinary skill in the art. It is obvious to him. Therefore, it is to be understood that the present invention is not limited to the examples of such crystals.

On the other hand, when a file is distributed through a buddy as a premise of the determination, the buddy must be previously distributed and stored in the file through the file distribution unit 113 or another buddy. Therefore, when the messenger session means 111 is connected, before the determination, the messenger session means 111 checks whether the buddy of the messenger client has previously distributed the file via the file distribution means 113 or another buddy.

In addition, according to an embodiment of the present invention, the messenger session means 111 manages information necessary for distribution of the file stored in the file distribution means 113 to the messenger clients 101 to 107 according to the present invention. Therefore, the messenger session means 111 may mount a distribution information management unit that manages information necessary for distribution of a file. The information necessary for the distribution of the file may include, for example, file identification information (file name and file size), file hashing, distribution period, distribution history (the time at which the distribution command was sent to the messenger client, and the deployment instruction to the buddy of the messenger client). Time of transmission, distribution method included in the distribution command) and access information (address information of a file stored in the file distribution unit 113). Among the information necessary for the distribution of the file, file identification information, file hashing, distribution period, and access information are included in the file distribution command transmitted to the messenger client 1 (101) described above. Accordingly, the messenger clients 101 to 107 may access the file distribution means 113 or the buddy storing the file based on the information necessary for the distribution of the file, and receive the file.

Meanwhile, according to another embodiment of the present invention, the distribution information manager may be mounted on each of the messenger clients 101 to 107. In this case, since the messenger clients 101 to 107 do not need to receive the file distribution command, in this case, file identification information, file destruction, distribution period and access information among the information necessary for the distribution of the file are previously described. It is not included in the file distribution command transmitted to the messenger client 1 101 described above, but is included in the distribution file notification information transmitted from the messenger session means 111 to the messenger client 1 101. Accordingly, the messenger clients 101 to 107 may access the file distribution means 113 or the buddy storing the file based on the information necessary for the distribution of the file, and receive the file.

Each of the messenger clients 101 to 107 connects to the messenger session means 111 and then, based on the information necessary for distributing a file included in the file distribution command received from the messenger session means 111 via the command receiving unit, The file is received and stored from any one of the file distribution means 113, the buddy and the file relay means 115. Accordingly, the messenger clients 101 to 107 include a file receiving unit that receives a file from the file distribution unit 113 via the Internet, a P2P transmission / reception unit that receives an entire file or a divided file from a buddy in a P2P manner, and a file relay unit 115. A file relay transceiver for receiving an entire file or a divided file through a messenger network, a file combining unit for combining the divided received files, and a file hash received from the messenger session means 111 according to a hash algorithm applied to the received file. A hash decryption unit for decoding the received file with a key is mounted, and since such a configuration is a technique known to a person skilled in the art, detailed description thereof will be omitted. The files distributed to the messenger clients 101 to 107 may be stored and managed in the messenger client during the distribution period included in the information necessary for distributing the files. The storage management of the file is performed by the file manager mounted on the messenger clients 101 to 107. In addition, the messenger clients 101 to 107 are equipped with a messenger client service unit that performs a native messenger service.

2 is a flowchart illustrating a file distribution process according to an embodiment of the present invention, which is a flowchart illustrating a process of a messenger client receiving a file from a file distribution unit.

As shown in Fig. 2, when the messenger client 1 (101) accesses and authenticates the messenger session means 111 through the messenger client service unit (S201), the distribution information manager of the messenger session means 111 should be distributed at present. It is checked whether a file to be present exists (S203). The existence of the distribution file may be checked by setting a distribution period of the file, for example. That is, the distribution information management unit mounted on the messenger session means 111 checks whether the distribution period of the file stored in the file distribution means 113 expires based on the distribution period information which is information necessary for the distribution of the file. You can check the existence of the distribution file. If the distribution file does not exist, the messenger session means 111 provides a normal messenger service through the messenger service unit (S215).

As a result of the determination in step S203, when the distribution file exists, the distribution information management unit of the messenger session means 111 checks whether or not the distribution file has been distributed to the messenger client 1 101 to which it is currently connected (S205). ). That is, the distribution information management unit mounted on the messenger session terminal 111 includes distribution history information included in information necessary for distributing a file (the time when the distribution command is transmitted to the messenger client, and the distribution method included in the distribution command). ), It is checked whether the distribution file has been distributed to the messenger client 1 (101). If the distribution file has been distributed to the messenger client 1 (101), the messenger session means 111 provides a normal messenger service through the messenger service unit (S215).

As a result of the determination in step S205, when the distribution file has not been distributed to the messenger client 1 (101), the determining unit of the messenger session means 111 selects a distribution system for distributing the distribution file to the messenger client 1 (101). Determine (S207). That is, the decision unit included in the messenger session means 111 determines the distribution method according to the above-described various policies.

In this process, the determining unit transmits distribution history information included in the information necessary for distributing the file (for example, the time when the distribution command is transmitted to the buddies 103 to 107 of the messenger client 1 101, the distribution). Based on the distribution method included in the command], it is checked whether the buddies 103 to 107 of the messenger client 1 101 have previously distributed the file through the file distribution means 113 or another buddy.

As a result of the check, when the buddies 103 to 107 of the messenger client 1 101 have not previously distributed the file through the file distribution means 113 or another buddy (i.e., the messenger client 1 101 and the buddy) When all of 103 to 107 have not been distributed the distribution file], the determination unit determines distribution through the file distribution means 113 as a distribution method to the messenger client 1 (101).

On the other hand, if the buddy 103 to 107 of the messenger client 1 101 has previously distributed the file through the file distribution means 113 or another buddy (that is, the messenger client 1 101). At least one of the buddies 103 to 107 of the distribution file is distributed to the messenger client 1 101 through the file distribution means 113 in accordance with various policies as described above. One of the distribution and the distribution through the buddies 103 to 107 are determined.

Next, the command transmitter mounted on the messenger session means 111 transmits a distribution command including information necessary for the distribution of the file to the messenger client 1 101 based on the file distribution method determined in step S207 ( S209). FIG. 2 shows an example in which the determination unit decides to distribute the distribution file through the file distribution means 113 as a distribution method to the messenger client 1 (101). Therefore, the distribution command transmitted in step S209 includes a command to receive the distribution file through the file distribution means 113.

When the distribution command is transmitted in step S209, the distribution information management unit mounted on the messenger session means 111 is necessary information for distributing the file, and the distribution history of the distribution file (for example, the messenger client 1 101). The time at which the distribution command in step S209 was transmitted, the distribution method included in the distribution command] is updated (S211). On the basis of the distribution history updated in step S211, the distribution file can be prevented from being distributed to the messenger client 1 (101) connected to the messenger session means 111 later.

Next, the messenger client 1 (101), which has received the distribution command transmitted by step S209 through the command receiving unit, is access information (file distribution means 113) as information necessary for the distribution of the file included in the distribution command. Based on the address information of the file stored in the [SAP], the file distribution unit 113 is connected to the file distribution unit 113 to distribute the distribution file (S213).

The messenger client 1 101 that has received the distribution file in step S213 hashes, decodes, distributes, and stores the distribution file through the hash decoding unit, or performs a messenger service through the messenger client service unit as necessary (S215). If there is an error in the integrity of the distribution file during the hash decoding process by the hash decoding unit, the file distribution unit 113 receives the distribution file having no integrity error. In this case, there is an error in the integrity of the file when the file itself is changed due to a predetermined reason, for example, a virus, a file change operation, or the like.

3 is a flowchart illustrating a file distribution process according to an embodiment of the present invention, and a flowchart illustrating a process of receiving a file from messenger client 1 (101) in which messenger client 2 (103) is a buddy. In the embodiment shown in Fig. 3, steps S201 to S211 of Fig. 2 are performed between the messenger client 2 103 and the messenger session means 111. Figs.

For example, the distribution information manager of the messenger session means 111 checks whether a file to be distributed to the messenger client 2 103 currently connected exists or not (S203).

As a result of the determination in step S203, in the case where the distribution file exists, the distribution information management unit mounted on the messenger session means 111 transmits distribution history information included in the information necessary for the distribution of the file (in this case, sends a distribution command to the messenger client). One hour, based on the distribution method included in the distribution command), it is checked whether the distribution file has been distributed to the messenger client 2 (103) (S205).

As a result of the determination in step S205, when the distribution file has not been distributed to the messenger client 2 103, the determining unit included in the messenger session means 111 distributes the distribution file to the messenger client 2 103 for distribution. The method is determined according to various policies as described above (S207).

In step S207, the determining unit transmits distribution history information (for example, time for transmitting a distribution command to the buddies 101, 105, and 107 of the messenger client 2 103) included in the information necessary for the distribution of the file, Check whether the buddies 101, 105, and 107 of the messenger client 2 103 have previously distributed the file through the file distribution means 113 or another buddy based on the distribution method included in the distribution command. .

As a result of the checking, since the buddy of messenger client 2 103, that is, the messenger client 1 101, has previously distributed the file through the file distribution means 113 or another buddy, the determining unit is a messenger client 2 103. ), The distribution through the file distribution means 113 and the distribution through the buddy (101, 105, 107) in accordance with various policies as described above.

Next, the command transmitting unit mounted on the messenger session means 111 transmits a distribution command including information necessary for the distribution of the file to the messenger client 2 103 based on the file distribution method determined in step S207 ( S209). 3 shows an example in which the determination unit decides to distribute a distribution file through a buddy as a distribution method to the messenger client 2 (103). Therefore, the distribution command transmitted in step S209 includes a command to receive the distribution file through a buddy.

Next, the messenger client 2 (103) receiving the distribution command transmitted by step S209 through the command receiving unit stores the distribution file confirmed from the distribution command to the buddies 101, 105, and 107 through the file management unit. Inquire (S301). The inquiry may be performed, for example, at an interval of one hour until receiving a response from the buddies 101, 105, and 107.

If the file management unit of the messenger client 1 (101) storing the distribution file among the buddies (101, 105, 107) receiving the inquiry sent in step S301 transmits a response to the messenger client 2 (103) (S303). The messenger client 2 103 receives the distribution file from the messenger client 1 101 in a P2P manner or a file relay manner of a messenger service through a P2P transceiver or a file relay transceiver (S305).

The messenger client 2 103 that has received the distribution file in step S305 hashes, decodes, distributes, and stores the distribution file through the hash decoding unit, or performs a messenger service through the messenger client service unit as necessary (S307). If there is an error in the integrity of the distribution file during the hash decoding process by the hash decoding unit, the distribution file is received again. If there is an error in the integrity of the file distributed from one buddy, the distributed file is received again from another buddy.

4 is a flowchart illustrating a file distribution process according to an exemplary embodiment of the present invention, in which a messenger client 3 105 receives a file from a plurality of buddy messenger client 1 101 and messenger client 2 103. It is a flowchart explaining. In the embodiment shown in Fig. 4, steps S201 to S211 of Fig. 2 are performed between the messenger client 3 105 and the messenger session means 111. Figs.

For example, the distribution information manager of the messenger session means 111 checks whether or not a file to be distributed to the messenger client 3 105 currently connected exists (S203).

As a result of the determination in step S203, in the case where the distribution file exists, the distribution information management unit mounted on the messenger session means 111 transmits distribution history information included in the information necessary for the distribution of the file (in this case, sends a distribution command to the messenger client). One hour, based on the distribution method included in the distribution command), it is checked whether the distribution file has been distributed to the messenger client 3 105 (S205).

As a result of the determination in step S205, when the distribution file has not been distributed to the messenger client 3 105, the determining unit included in the messenger session means 111 distributes the distribution file to the messenger client 3 105. The method is determined according to various policies as described above (S207).

In step S207, the determination unit transmits the distribution history information included in the information necessary for the distribution of the file (for example, the time to send the distribution command to the buddy 101, 103, 107 of the messenger client 3 105, Check whether the buddy 101, 103, 107 of the messenger client 3 105 has previously distributed the file through the file distribution means 113 or another buddy based on the distribution method included in the distribution command. .

As a result of the checking, since the messenger client 1 101 and the messenger client 2 103 which are buddies of the messenger client 3 105 have previously distributed the file through the file distribution means 113 or another buddy, the determination unit As the distribution method to the messenger client 3 105, one of the distribution through the file distribution means 113 and the distribution through the buddies 101, 103, and 107 is determined according to various policies as described above.

Next, the command transmitting unit mounted on the messenger session means 111 transmits a distribution command including information necessary for the distribution of the file to the messenger client 3 105 based on the file distribution method determined in step S207 ( S209). 4 shows an example in which the determination unit decides to distribute a distribution file through a buddy as a distribution method to the messenger client 3 (105). Therefore, the distribution command transmitted in step S209 includes a command to receive the distribution file through a buddy.

Next, the messenger client 3 105 that receives the distribution command transmitted by step S209 through the command receiving unit stores the distribution file identified from the distribution command to the buddies 101, 103, and 107 via the file management unit. Inquire (S401). The inquiry may be performed, for example, at an interval of 1 hour until a response is received from the buddies 101, 103, and 107.

Among the buddies 101, 103, and 107 receiving the inquiry sent in step S401, the file management unit of the messenger client 1 101 and messenger client 2 103 that stores the distribution file is sent to the messenger client 3 105. When the response is transmitted (S403), the messenger client 3 105 distributes the message from the messenger client 1 101 and the messenger client 2 103 in a P2P method or a file relay method of a messenger service through a P2P transceiver or a file relay transceiver. The file is distributed (S405). Here, the distribution file may be divided and distributed from a plurality of buddies that store distribution files, that is, messenger client 1 101 and messenger client 2 103. The divided and distributed files are combined in the file combination unit of the messenger client 3 (105). When the file is divided and distributed, the buddy that stores the file, that is, the messenger client 1 (101) and the messenger client 2 (103), may reduce the transmission load, and enter the messenger client 3 (105) that divides and distributes the file. In this case, when the messenger client 1 (101) and the messenger client (103) go offline, the client requests only the necessary portion of the file when the messenger client (101) and the messenger client (103) are connected online. The file can be distributed efficiently. The divided distribution amount may be determined according to, for example, a transmission speed between the messenger client 1 (101) and the messenger client 2 (103) for distributing the file and the messenger client 3 (105) for distributing the file. In this case, by setting a large amount of distribution for a bird with a high transmission speed, the transmission time can be reduced and the network environment can be efficiently used.

The messenger client 3 105 having distributed the distribution file in step S405 hashes and decrypts the distribution file through the hash decoding unit to patch, install, or store the messenger service through the messenger client service unit as necessary (S407). If there is an error in the integrity of the distribution file during the hash decoding process by the hash decoding unit, the distribution file is received again. If there is an error in the integrity of the file distributed from one buddy, the distributed file is received again from another buddy.

On the other hand, throughout the present specification, the file distribution server 109 may operate as a buddy of the client receiving the file. For example, in the embodiment shown in Fig. 4, the file distribution server 109 also acts as a buddy of the messenger client 3 105, and together with the messenger client 1 101 and messenger client 2 103, messenger client 3 ( 105) to distribute the file.

5 is a flowchart illustrating a file distribution process according to another exemplary embodiment of the present invention, and illustrating a process of a messenger client receiving a file from a file distribution unit.

As shown in Fig. 5, when the messenger client 1 (101) accesses and authenticates the messenger session means 111 through the messenger client service unit (S501), the distribution information manager of the messenger session means 111 should be distributed at present. Check whether a file to be present exists (S503). The existence of a distribution file can be checked, for example, by setting the distribution period of the file. That is, the distribution information management unit mounted on the messenger session means 111 checks whether the distribution period of the file stored in the file distribution means 113 expires based on the distribution period information which is information necessary for the distribution of the file. You can check the existence of the distribution file. If the distribution file does not exist, the messenger session means 111 provides a normal messenger service through the messenger service unit (S519).

As a result of the determination in step S503, when the distribution file exists, the distribution information management unit of the messenger session means 111 transmits the distribution file notification information to the messenger client 1 101 (S505). As described above, among the information necessary for the distribution of the file, file identification information, file hashing, distribution period, and access information are included in the distribution file notification information.

The distribution information manager of the messenger client 1 (101) receiving the distribution file notification information checks whether the distribution file has been distributed to the messenger client 1 (101) to which the distribution file is currently connected (S507). That is, the distribution information management unit mounted on the messenger client 1 (101) includes distribution history information included in the information necessary for distributing the file (the time when the distribution command is transmitted to the messenger client, the distribution method included in the distribution command). Based on this, it is checked whether the distribution file has been distributed to the messenger client 1 (101). If the distribution file has been distributed to the messenger client 1 (101), the messenger session means 111 provides a normal messenger service through the messenger service unit (S519).

As a result of the determination in step S507, when the distribution file has not been distributed to the messenger client 1 101, the determining unit of the messenger client 1 101 determines a distribution system for distributing the distribution file to the messenger client 1 101. FIG. Determine (S509).

Here, in the case of the embodiment of FIG. 5, the distribution scheme may be determined more simply than in the case of the embodiment of FIGS. 2 to 4. That is, as described above, the file distribution server 109 can operate as a buddy of the client to which the file is distributed (in the embodiment of FIG. 5, the messenger client 1 101), the file distribution server 109 and the buddy. The files may be determined to be distributed from 103, 105, and 107, or the files may be determined to be distributed from buddies 103, 105, and 107.

If the distribution method is determined in step S509, the distribution information management unit mounted on the messenger client 1 101 updates the distribution history of the distribution file as information necessary for distribution of the file (S511). Based on the distribution history updated in step S511, the distribution file can be prevented from being distributed to the messenger client 1 (101) connected to the messenger session means 111 later.

Next, the messenger client 1 101 queries the file distribution server 109 and the buddies 103, 105, and 107 via the file management unit whether they are storing the distribution file identified from the distribution command (S513). The query may be performed, for example, at an interval of 1 hour until a response is received from the file distribution server 109 and the buddies 103, 105, and 107.

The file management unit and the file distribution server 109 of the messenger client 2 103 which stores the distribution file among the file distribution server 109 and the buddies 103, 105, and 107 that have received the inquiry transmitted in step S513. Sends a response to the messenger client 1 (101) (S515), the messenger client 1 (101) from the messenger client 2 (103) in the P2P method or the file relay method of the messenger service through the P2P transceiver or file relay transceiver; Distribution files are distributed (S517). Here, when the file is also distributed from the file distribution server 109, the file is distributed through the file receiving unit based on the access information (address information of the file stored in the file distribution unit 113) as information necessary for the distribution of the file. The distribution file is distributed by accessing the means 113.

In the case of the plurality of buddies that store the distribution file, that is, the embodiment shown in FIG. 5, the distribution file may be divided and distributed from the file distribution server 109 and the messenger client 2 103. The divided and distributed files are combined in the file combination unit of the messenger client 1 (101). The divided distribution amount may be determined according to, for example, a transmission speed between the file distribution server 109 distributing the file and the messenger client 2 103 and the messenger client 1 101 distributing the file. In this case, by setting a large amount of distribution for a bird with a high transmission speed, the transmission time can be reduced and the network environment can be efficiently used.

The messenger client 1 (101) having received the distribution file in step S517 may hash, decode, distribute, and store the distribution file through the hash decoding unit, or perform a messenger service through the messenger client service unit as necessary (S519). If there is an error in the integrity of the distribution file during the hash decoding process by the hash decoding unit, the distribution file is received again. If there is an error in the integrity of the file distributed from one buddy, the distributed file is received again from another buddy.

The method of the present invention as described above may be implemented as a program and stored in a computer-readable recording medium (CD-ROM, RAM, ROM, floppy disk, hard disk, magneto-optical disk, etc.).

The present invention described above is not limited to the above-described embodiments and the accompanying drawings, and various substitutions, modifications, and changes are possible in the technical field of the present invention without departing from the technical spirit of the present invention. It will be clear to those of ordinary knowledge.

1 is a schematic diagram illustrating a file distribution system according to an embodiment of the present invention;

FIG. 2 is a flowchart illustrating a file distribution process according to an embodiment of the present invention, illustrating a process of a messenger client receiving a file from a file distribution unit; FIG.

3 is a flowchart illustrating a file distribution process according to an embodiment of the present invention, illustrating a process of receiving a file from messenger client 1 in which messenger client 2 is a buddy;

4 is a flowchart illustrating a file distribution process according to an embodiment of the present invention, and a flow chart illustrating a process of receiving a file from a messenger client 1 and a messenger client 2 in which a messenger client 3 is a plurality of buddies;

5 is a flowchart illustrating a file distribution process according to another exemplary embodiment of the present invention, and illustrating a process of a messenger client receiving a file from a file distribution unit.

<Explanation of symbols for the main parts of the drawings>

101 to 107: messenger client

109: File Distribution Server

111: Messenger session means

113: Means of file distribution

115: file relay means

Claims (20)

In the data distribution method of distributing data to a plurality of clients connected to the server, A first step of checking whether there is data to be distributed to a client accessing the server; A distribution method for distributing the data to a client accessing the server when the data to be distributed to the client accessing the server exists as a result of the checking of the first step; A first method of distributing the data from a server, a second method of distributing the data from another client in a messenger buddy relationship with a client connected to the server, or a method of distributing the data from another client in the buddy relationship with the server Including at least one of three ways; And The third step of transmitting, by the server, a distribution command including a distribution method determined in the second step to a client accessing the server; Data distribution method comprising a. The method of claim 1, The first step to confirm The client sends information about the files previously distributed to the server or the server sends information about the files that the server should currently distribute. Data distribution method comprising a. The method of claim 1, The first step is Determining whether there is data to be distributed based on any one or more of distribution period information of the data, the distribution history information, and time information when a distribution command is transmitted to a client accessing the server; How data is distributed. The method of claim 1, The second step is A fourth step of checking whether the data has been distributed to another client in the buddy relationship; A fifth step of determining, as the distribution method, the first method when the file has never been distributed to another client having a buddy relationship as a result of the checking of the fifth step; And A sixth step of determining one of the first method, the second method, and the third method according to a policy as the distribution method when the file has been distributed to another client having the buddy relationship as a result of the checking in the fifth step; Data distribution method comprising a. The method of claim 4, wherein The policy is Distributing the data from the server to a client having a predetermined ratio or more than a predetermined number of clients connected to the server, or distributing the data from another client having a messenger buddy relationship to the remaining clients. Data distribution methods. The method of claim 1, The client accessing the server distributes the data from the server or from another client having a messenger buddy relationship with the client connected to the server according to the distribution method included in the distribution command transmitted by the third step. Receive seventh step Data distribution method further comprising. The method of claim 6, The seventh step Receiving the data from another client in the messenger buddy relationship by any one of a P2P scheme, a messenger file relay scheme, or a hybrid scheme combining P2P and relay schemes. How data is distributed. The method of claim 7, wherein The seventh step Receive distribution of data to be distributed at a predetermined rate from each of a plurality of clients in the messenger buddy relationship How data is distributed. The method of claim 1, The data is encrypted How data is distributed. The method of claim 1, When the distribution method determined in the second step is the second method or the third method The accessing client receives the data from the second client after checking whether the data to be distributed is transmitted to one or more second clients that are currently connected to the buddy relationship. Data distribution method further comprising. In a data distribution system that distributes data to clients, Data distribution means for storing data to be distributed to the client; Messenger service means for managing information of another client having a messenger buddy relationship with the client and performing a messenger service; Distribution information management means for managing history information of data distributed to the client; Distribution method for distributing to the client The distribution method includes a first method of distributing the data from the data distributing means and a second method of distributing the data from another client having a messenger buddy relationship with the client; Distribution method determining means for determining one or more of third ways to distribute the data from other clients in the buddy relationship; And Command transmitting means for transmitting a distribution command including the determined distribution method to the client Data distribution system comprising a. The method of claim 11, The distribution information management means Determining whether there is data to be distributed to the client based on any one or more of distribution period information of the data, distribution history information of the data, and time information of a distribution command transmitted to a client accessing the server; Data distribution system. The method of claim 11, The distribution information management means checks whether the data has been distributed to other clients in the buddy relationship when the distribution information management means has never been distributed to the client connected to the server. If the file has never been distributed to another client in the buddy relationship, the distribution method determining means determines the distribution method by distributing the data from the data distribution means. When the file has been distributed to another client in the buddy relationship, the distribution method determining means determines one of the first method, the second method, and the third method according to a policy as the distribution method. Data distribution system. The method of claim 13, The policy is Distributing the data from the data distributing means to clients currently connected to the server with a predetermined ratio of clients or a number of other clients in a messenger buddy relationship, and distributing the data from other clients in a messenger buddy relationship to the remaining clients. doing Data distribution system. In the client system for accessing the data distribution system of claim 11, Command receiving means for receiving a distribution command sent from the data distribution system; Data receiving means for receiving the data from the data distributing means or distributing the data from another client having a messenger buddy relationship with the client system in accordance with a distribution method included in the received distribution command; And Data management means for storing and managing data distributed by the data receiving means Client system comprising a. The method of claim 15, The data receiving means From another client in the messenger buddy relationship Receiving the data by any one of a P2P method, a messenger file relay method, or a hybrid method in which P2P and relay methods are mixed. Client system. The method of claim 16 The data receiving means Receive distribution of data to be distributed at a predetermined rate from each of a plurality of clients in the messenger buddy relationship Client system. The method of claim 17, Data combination unit for combining the divided and distributed data Client system further comprising. The method of claim 15, The data management means Which one of a plurality of other clients in the messenger buddy relationship is storing the data Client system. In the data distribution method for distributing data, A first step of checking whether there is data to be distributed to a client connected to the server; A second step of confirming whether the data to be distributed exists in another client having a messenger buddy relationship when there is data to be distributed to a client accessing the server as a result of the checking of the first step; Distribution method for distributing the data when the data exists in the other client, The distribution method is a first method of distributing the data from the server, from the other client having a messenger buddy relationship with the client connected to the server A third step of determining one or more of a second way of distributing data or a third way of distributing the data from the server and other clients in the buddy relationship; Data distribution method comprising a.

Images