KR101204317B1 - Peer to peer network system and method for providing publish/subscribe service using the same - Google Patents

Abstract

A P2P network system and a method for providing a post / subscribe service using the same are provided. The disclosed P2P network system includes at least one node (subscriber node) operating as a subscriber generating a subscription including a plurality of attributes; And two or more nodes (publisher / subscriber nodes) that act as publishers or act as subscribers that generate events corresponding to some of the plurality of attributes. Subscriber nodes are grouped into a plurality of publisher groups consisting of at least one publisher / subscriber node, wherein the plurality of publisher groups are any one of the at least one subscriber node and the at least two publisher / subscriber nodes through mutual communication. Collect events that satisfy conditions (attribute conditions) for a plurality of attributes included in the subscription generated in the sub-group, and any one publisher group of the plurality of publisher groups transmits the collected events to the arbitrary nodes. .

Description

P2P network system and publishing / subscription service providing method using the same {PEER TO PEER NETWORK SYSTEM AND METHOD FOR PROVIDING PUBLISH / SUBSCRIBE SERVICE USING THE SAME}

Embodiments of the present invention relate to a method for providing a publish / subscription service through a plurality of peer nodes, and a peer to peer network system capable of providing a publish / subscribe service.

Conventional networking technology for providing a subscription / subscription service Rendezvous according to the method of storing the subscription (Subscription) occurred on the Subscriber side and the transmission method of Events occurred on the Publisher side (Rendezvous) It is largely classified into a method and a filter method.

In the conventional rendezvous type publishing / subscribing service, each subscriber's subscription registration and publisher's event transmission are performed by one subject (node). In the case of a conventional filter publishing / subscribing service, nodes constituting the system distribute and store subscriptions, and form a tree topology among the nodes using the inclusion relationship between the subscriptions. The event has been sent.

However, the above-described networking technology for providing a filter-based publishing / subscribing service considers only an environment in which all the publishers generate an event including all the plurality of properties included in the subscription, so that the publishers have some properties. There was a problem that cannot be applied to a distributed event generation environment that generates bays.

In order to solve the problems of the prior art as described above, the present invention proposes a P2P network system that can provide a post / subscription service in a distributed event generation environment, and a method for providing a post / subscription service using the same.

Other objects of the present invention may be derived by those skilled in the art through the following examples.

According to a preferred embodiment of the present invention to achieve the above object, in a peer-to-peer (P2P) network system including a plurality of nodes, a subscription including a plurality of attributes (Subscription) At least one node (subscriber node) that acts as a subscriber (subscriber) that generates; And two or more nodes (publisher / subscriber nodes) that act as publishers or act as subscribers that generate events corresponding to some of the plurality of attributes. Subscriber nodes are grouped into a plurality of publisher groups consisting of at least one publisher / subscriber node, wherein the plurality of publisher groups are any one of the at least one subscriber node and the at least two publisher / subscriber nodes through mutual communication. Collect events that satisfy conditions (attribute conditions) for a plurality of attributes included in the subscription, and any one publisher group of the plurality of publisher groups transmits the collected events to the arbitrary nodes. Provided is a P2P network system capable of providing a post / subscribe service.

The plurality of publisher / subscriber nodes may be grouped into the plurality of publisher groups according to whether the generated attributes are the same.

The at least one subscriber node and the two or more publisher / subscriber nodes are connected according to a topology to form a subscriber overlay network, and the one publisher group is any one node included in the subscriber overlay network. The aggregated event may be transmitted to the random node, and the aggregated event may be transmitted from the one node to the arbitrary node through a connection according to the predetermined topology.

Each of the plurality of publisher groups includes one head publisher / subscriber node and at least one member publisher / subscriber node, and communication between the plurality of publisher groups is each included in the plurality of publisher groups. Corresponds to communication between subscriber nodes (plural head publisher / subscriber nodes).

The plurality of publisher / subscriber nodes are grouped into the plurality of publisher groups according to whether the generated attributes are the same, and each of the plurality of head publisher / subscriber nodes is included in a plurality of subscriptions generated at the arbitrary node. A routing table may be generated and stored using attribute conditions for the attribute, and the mutual communication may be performed using the routing table.

The routing table includes first routing information and the head for selecting a next head publisher / subscriber node to forward the internal event when the head publisher / subscriber node receives an event (internal event) from the member publisher / subscriber node. When the publisher / subscriber node receives an event (external event) from another head publisher / subscriber node, it may include second routing information for selecting the next head publisher / subscriber node to aggregate and deliver the external event and the internal event. Can be.

The first routing information includes condition information including attribute conditions for some attributes occurring in a publisher group including a corresponding head publisher / subscriber node among a plurality of attributes included in a subscription occurring in the arbitrary node; Head publisher / subscriber node information is included, and the next head publisher / subscriber node information includes some attributes occurring in a publisher group to which the corresponding head publisher group belongs among a plurality of attributes included in the subscription occurring at the arbitrary node. Information on the head publisher / subscriber node included in each of the k publisher groups that generate events for other k (integer or greater) attributes may be included.

The head publisher / subscriber node that has received the internal event stores the internal event when the internal event satisfies the condition information, and any one of information of the head publisher / subscriber node included in the k publisher groups, respectively. The internal event may be transmitted to the head publisher / subscriber node corresponding to the any one information by using the information.

The second routing information includes first condition information including attribute conditions for some attributes occurring in a publisher group including a corresponding head publisher / subscriber node among a plurality of attributes included in a subscription generated in the arbitrary node. And attribute conditions for k (an integer of 1 or more) attributes other than some attributes occurring in the publisher group to which the head publisher group belongs, among a plurality of attributes included in the subscription occurring in the arbitrary node. k second condition information and k next head publisher / subscriber node information corresponding to the k second condition information, respectively, and include i (1 or more k or less) The next head publisher / subscriber node information includes the i th attribute of the publisher group that generates the events for the k attributes. It may include information about the head of the publisher / subscriber node included in each group, except for the publisher Publishers Group generated the event.

The head publisher / subscriber node receiving the internal event stores the internal event when the internal event satisfies the condition information, and the head publisher / subscriber node receiving the external event stores the internal event, When the external event satisfies at least one second condition information of the k second condition information, the head publisher / subscriber included in at least one next head publisher information respectively corresponding to the at least one second condition information. The external event and the internal event may be collected and transmitted to the head publisher / subscriber node corresponding to the any one information using any one of the node information.

Further, according to another embodiment of the present invention, an event corresponding to at least one node (subscriber node) operating as a subscriber generating a subscription including a plurality of attributes and an attribute of some of the plurality of attributes is generated. A method for providing a publish / subscribe service using a P2P network system including at least one node (publisher / subscriber node) which operates as a publisher or is operated as the subscriber and is grouped into a plurality of publisher groups, the at least one subscriber node and Generating a subscription at any of the two or more publisher / subscriber nodes; Collecting, by the plurality of publisher groups, an event that satisfies a condition (attribute condition) for a plurality of attributes included in a subscription generated at the arbitrary node through communication with each other; And a publisher group of any of the plurality of publisher groups transmits the collected events to the arbitrary nodes. The method of providing a publish / subscribe service using a P2P network system is disclosed.

According to the present invention, it is possible to easily provide a post / subscribe service even in a distributed event generation environment.

1 is a diagram illustrating a schematic configuration of a P2P network system capable of providing a post / subscribe service according to an embodiment of the present invention.
2 is a diagram illustrating a procedure performed when a new publisher / subscriber node joins as a publisher group.
3 is a diagram for describing an operation of generating a routing table by a head publisher / subscriber node.
4 is a diagram for describing an operation of generating a routing table by a plurality of head publisher / subscriber nodes.
FIG. 5 is a diagram for describing an operation of collecting events by a plurality of head publisher / subscriber nodes using the routing table generated in FIG. 4.
6 is a flowchart illustrating the overall flow of a method of providing a post / subscribe service using a P2P network system according to an embodiment of the present invention.

While the invention is susceptible to various modifications and alternative forms, specific embodiments thereof are shown by way of example in the drawings and will herein be described in detail. It should be understood, however, that the invention is not intended to be limited to the particular embodiments, but includes all modifications, equivalents, and alternatives falling within the spirit and scope of the invention. Like reference numerals are used for like elements in describing each drawing.

Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings.

1 is a diagram illustrating a schematic configuration of a P2P network system capable of providing a post / subscribe service according to an embodiment of the present invention.

Referring to FIG. 1, a P2P network system 100 (hereinafter, referred to as a “P2P network system”) capable of providing a publish / subscribe service according to an embodiment of the present invention includes a plurality of nodes 111 and 121. do. In more detail, the P2P network system 100 includes at least one first node 111 and two or more second nodes 121.

At least one first node 111 operates as a subscriber that generates a subscription including a plurality of attributes. In addition, the two or more second nodes 121 operate as a publisher that generates an event for a specific property or as a subscriber described above. That is, each of the two or more second nodes 121 may generate a subscription (operate as a subscriber) or generate an event (operate as a publisher) according to a situation. Hereinafter, for convenience of description, the first node 111 will be referred to as a "subscriber node" and the second node 121 will be referred to as a "publisher / subscriber node".

Such at least one subscriber node 111 and two or more publisher / subscriber nodes 121 are connected according to a predetermined topology as shown in FIG. 1 to form a subscriber overlay network 110. In addition, the two or more publisher / subscriber nodes 121 may be grouped into a plurality of publisher groups composed of at least one publisher / subscriber node 121 to form a publisher overlay network 120.

According to an embodiment of the present invention, the plurality of publisher / subscriber nodes 121 may be grouped into a plurality of publisher groups according to whether the attributes of events occurring in the corresponding publisher / subscriber node 121 are the same. That is, the publisher / subscriber node 121 only generates an event for some of the plurality of attributes included in the subscription (for example, one attribute). According to one embodiment of the present invention, the publisher group Attributes of the generated event may be formed by grouping the same publisher / subscriber nodes 121.

The plurality of publisher groups thus formed are subscriptions that occur at any of the nodes (i.e., at least one subscriber node and at least two publisher / subscriber nodes) forming subscriber overlay network 110 through mutual communication. An event that satisfies a condition (attribute condition) for a plurality of attributes included in is collected, and the collected event is transmitted to the arbitrary node.

That is, as mentioned above, the publisher / subscriber node 121 generates an event only for some of the plurality of attributes included in the subscription, and the event generated by the publisher / subscriber node 121 for each publisher group. Since the attributes are different, a plurality of publisher groups may collect events of different attributes occurring in each publication group to generate an event set that satisfies a plurality of attributes included in the subscription occurring at the arbitrary node. It is then sent to the random node. At this time, the aggregated event is transmitted to the arbitrary node by any one publisher group of a plurality of publisher groups.

According to an embodiment of the present invention, the one publisher group transmits an aggregated event to any one node included in the subscriber overlay network 110, and the aggregated event is connected through a connection according to the predetermined topology. It can be transmitted from any one node to any node. That is, any one publisher group may transmit the aggregated events assuming the subscriber overlay network 110 as one subscriber.

The structure of the P2P network system 100 is a hierarchical structure for collecting events and determining and filtering their validity before transmitting the collected events to subscribers. That is, the publisher overlay network 120 distributes and collects events from each publisher, and determines whether the generated events are in accordance with the subscription, and the matching events are combined with the previously collected events for the centralized event. It is transmitted to the subscriber overlay network 110 in the form.

On the other hand, the subscriber overlay network 110 can be applied to the existing publishing / subscription service network. This is because the subscriber overlay network 110 simply recognizes the publisher overlay network 120 as one publisher and receives the event (the aggregated events) without having to know the publisher overlay network 120. Since both the subscriber overlay network 110 and the publisher overlay network 120 configure the overlay network based on the subscription, the subscriber overlay network 110 and the publisher overlay network 120 have such dual structure. You need to be aware and register subscriptions with each overlay network simultaneously.

Hereinafter, with reference to FIGS. 2 and 3, a concept in which a plurality of publisher / subscriber nodes are grouped to form a publisher group (that is, a concept of forming a network within a publisher group that generates an event for the same property) and a plurality of publisher groups This concept of forming a network for communication between each other (concept of forming an overlay network between groups of publishers) will be described in more detail.

1. Formation of publisher groups

As mentioned above, by default, the publisher / subscriber node 121 having the same attribute of the occurrence event is grouped into one publisher group, and additionally, the publisher / subscriber node 121 that is identically included in a specific area includes one publisher group. Can be grouped as: Here, the "area" may be defined by various criteria such as a physical location area or a logical service area.

For example, when a plurality of nodes 111 and 121 constituting the P2P network system 100 are used for a sensor monitoring service, a space where the plurality of nodes 111 and 121 are located is a plurality of areas having a predetermined size. In this case, at least one publisher / subscriber node 121 included in the same area (physical location area) and generating an event having the same property may form one publisher group.

 In another example, in the above example, when some nodes sense temperature, and some other nodes sense humidity, they are included in the same service area (temperature sensing service or humidity sensing service) and generate an event of the same attribute. At least one publisher / subscriber node 121 may form one publisher group.

According to an embodiment of the present invention, each of the plurality of publisher groups formed as described above may include one head publisher / subscriber node and at least one member publisher / subscriber node.

The head publisher / subscriber node receives and stores events from within the publisher group from member publisher / subscriber nodes within the group, and maintains a network with the head publisher / subscriber nodes of other publisher groups outside the publisher group. When the validation of the event is completed (that is, when all events for the attributes included in the specification are collected) while communicating between publisher groups to collect the event, the collected event is sent to the subscriber overlay network 110. It serves to convey. That is, when the head publisher / subscriber node is included in the publisher group, the communication between the plurality of publisher groups may correspond to the communication between the head publisher / subscriber nodes included in each of the plurality of publisher groups.

Such head publisher / subscriber node may be selected according to various criteria. In one example, to prevent frequent replacement of the head publisher / subscriber node, the publisher / subscriber node with the largest amount of remaining power may be selected as the head publisher / subscriber node. As another example, the publisher / subscriber node having the highest frequency of events may be selected as the head publisher / subscriber node to prevent the number of event transmissions in the publisher group.

At this time, according to an embodiment of the present invention, nodes in each publisher group may be connected to a member publisher / subscriber node based on a star topology based on a head publisher / subscriber node. That is, the member publisher / subscriber node may not be connected to other publisher / subscriber nodes except for the head publisher / subscriber node. This is to ensure that all events that occur within the publisher group are sent externally through the head publisher / subscriber node.

Meanwhile, after the formation of the publisher group is completed, a new publisher / subscriber node may participate as a publisher group. FIG. 2 is a view for explaining a procedure performed when a new publisher / subscriber node participates as a publisher group.

As shown in FIG. 2, in the publisher overlay network 120 included in the P2P network system 100 according to an embodiment of the present invention, a bootstrap server 122 exists in the same manner as a conventional P2P network system. Bootstrap server 122 provides information about the plurality of publisher groups and information about entry points for accessing the publisher group (ie, information about publisher / subscriber nodes 121a through 121d in the publisher group). At this time, the entry point need not be the head publisher / subscriber node 121a. This is because all publisher / subscriber nodes 121a through 121d in the publisher group are aware of the head publisher / subscriber node 121a, so if a new publisher / subscriber node 123 wants to join a publisher group, any publisher / subscriber This is because the information about the head publisher / subscriber node 121a can be transmitted even if the node becomes the entry point.

The procedure in the case where the new publisher / subscriber node 123 intends to participate in the publisher group will be described in more detail as follows.

First, Bootstrap server 122 transmits the group join message to the entry point of the publisher group described above. When the publisher / subscriber node of the entry point that receives this is not the head publisher / subscriber node 121a, the publisher / subscriber node 123 responds to the information of the head publisher / subscriber node 121a, so that the new publisher / subscriber node 123 receives the head. The publisher / subscriber node 121a can be recognized.

Thereafter, the new publisher / subscriber node 123 exchanges a metric which is a selection criterion of the head with the head publisher / subscriber node 121a corresponding to the received information to determine whether to replace the head. If the existing head publisher / subscriber node 121a is more suitable as a head, the new publisher / subscriber node 123 stores the head information and then completes the subscription procedure. Conversely, if the new publisher / subscriber node 123 is more suitable as a head, then the existing head publisher / subscriber node 121a is assigned to the new publisher / subscriber node 123 to all member publisher / subscriber nodes 122b through 121d. Information about the new head has been selected and the event reception status up to this point is notified to the new publisher / subscriber node 123, and the role is changed as a member publisher / subscriber.

2. A group of publishers form a network for mutual communication

According to an embodiment of the present invention, the overlay network between the publisher groups formed by the connection between the head publisher / subscriber nodes may follow a PHT configuration of the DHT (Distributed Hash Table). That is, the plurality of head publisher / subscriber nodes may configure the DHT-based overlay network using a plurality of attributes in subscriptions occurring at any node in the subscriber overlay network.

In this case, according to an embodiment of the present invention, each of the plurality of head publisher / subscriber nodes uses conditions (attribute conditions) for the plurality of attributes included in the subscription occurring at any node included in the subscriber overlay network. By creating and storing a routing table, and communicating with each other using the stored routing table.

3 is a diagram for describing an operation of generating a routing table by a head publisher / subscriber node.

As shown in FIG. 3, when a subscription including a plurality of attributes occurs at any of the nodes, the subscription is sequentially delivered to the plurality of head publisher / subscriber nodes 121a in the order of the attributes. Each of the plurality of head publisher / subscriber nodes generates and stores a routing table using attribute conditions for the plurality of attributes included in the subscription.

According to one embodiment of the invention, the routing table is configured to: i) select the next head publisher / subscriber node to forward an internal event when the head publisher / subscriber node receives an event (internal event) from a member publisher / subscriber node. First routing information and ii) a second for selecting the next head publisher / subscriber node to aggregate and forward external and internal events when the head publisher / subscriber node receives an event (external event) from the head publisher / subscriber node; Routing information may be included.

More specifically, first, the first routing information for the delivery of internal events includes some attributes that occur in the publisher group including the head publisher / subscriber node among the plurality of attributes included in the subscription occurring in the arbitrary node. Condition information including an attribute condition for and next head publisher / subscriber node information, and the next head publisher / subscriber node information included in the first routing information includes a plurality of subscriptions included in the subscription occurring at the arbitrary node. The properties of the head publisher / subscriber node included in each of the k publisher groups that fire events for k (which is an integer of 1 or more) other than some of the properties that occur in the publisher group to which the head publisher group belongs can be included. have.

That is, the head publisher / subscriber node stores the attribute conditions for the attributes in the same subscription as the attribute information of the events occurring in the publisher group to which the corresponding head publisher / subscriber node belongs, and generates the event for the remaining attributes in the subscription. The first routing information may be generated by setting the head publisher / subscriber nodes of another publisher group as candidate next head publisher / subscriber nodes to transmit the corresponding internal event. This is to determine a common next hop when an event satisfies a plurality of subscriptions in a case where the order of event occurrence in each publisher group occurs regardless of the order of attributes defined in the subscription.

In this case, the head publisher / subscriber node receiving the internal event stores the internal event when the internal event satisfies the condition information in the first routing information, and the information of the head publisher / subscriber node included in each of the k publisher groups. The internal event may be transmitted to the head publisher / subscriber node corresponding to the any one information by using any one of the information.

Next, the second routing information for the delivery of the external event includes attributes of some attributes occurring in the publisher group including the corresponding head publisher / subscriber node among a plurality of attributes included in the subscription occurring in the arbitrary node. K (at least one integer) attributes other than some attributes occurring in the publisher group to which the head publisher group belongs, among the plurality of attributes included in the subscription generated by the arbitrary node. K second condition information each including an attribute condition for an attribute, and k next head publisher / subscriber node information respectively corresponding to k second condition information, and k next head publishers included in the second routing information. The i next (integer of 1 or greater k) of the subscriber node information, the event for k attributes is included in the next head publisher / subscriber node information. The information on the head publisher / subscriber node included in each publisher group except for the publisher group that generates an event for the i-th property among the publisher groups that generate a may be included.

That is, the head publisher / subscriber node stores the attribute conditions for the attributes in the same subscription as the first attribute information as attributes of the event occurring in the publisher group to which the head publisher / subscriber node belongs, and the remaining attributes (k) in the subscription. Store the attribute condition for the second attribute as k second condition information, and the event for the remaining attributes (k-1) in the subscription except for the i-th attribute among the k attributes and the attributes of the event occurring in the publisher group to which they belong. The second routing information may be generated by setting the head publisher / subscriber node included in the publisher group that generates a to the i th next head publisher / subscriber.

In this case, the head publisher / subscriber node that receives the external event stores the internal event, and when the external event satisfies at least one second condition information among k second condition information, at least one second condition information. And aggregate external and internal events into the head publisher / subscriber node corresponding to any one of the information by using any one of the head publisher / subscriber node information included in at least one next head publisher information corresponding to Can transmit

Hereinafter, an operation of generating a routing table by a plurality of head publisher / subscriber nodes and an operation of collecting events based on the routing table will be described in detail with reference to FIGS. 4 and 5.

4 is a diagram for describing an operation of generating a routing table by a plurality of head publisher / subscriber nodes. Referring to FIG. 4, an operation of generating a routing table by each head publisher / subscriber node is as follows.

First, a subscription (S1) containing attribute A (attribute condition: 1 <A <4), attribute B (attribute condition: 1 <B <4), and attribute C (attribute condition: 2 <C <5) When the head publisher / subscriber node A of publisher group A, which raises an event for attribute A, receives, the head publisher / subscriber node A receives the attribute condition (1 <A <4) for the attribute A (Rx Event from local), and then add head publisher / subscriber node B and head publisher / subscriber node C belonging to publisher group B and publisher group C, each of which causes property B and property C, except for property A, respectively, to the next head publisher / Set as a subscriber node (Next) to generate the first routing information (411).

The head publisher / subscriber node A stores the attribute condition (1 <A <4) for the attribute A as the first condition information (Local Received event state), and the attributes of the attributes B and C, which are the remaining attributes except for the attribute A, are stored. Conditions 1 <B <4 and 2 <C <5 are stored as second condition information Rx Event from HP, respectively. Thereafter, the head publisher / subscriber node replaces the head publisher / subscriber node C, which generates attribute C other than attributes A and B, with a condition for attribute A (1 <A <4) and a condition for attribute B (1 Set to the next head publisher / subscriber node (Next) when <B <4) is satisfied, and the condition for attribute A is the head publisher / subscriber node B, which generates attribute B, except attributes A and C. Set to the next head publisher / subscriber node when (1 <A <4) and the condition (2 <C <5) for attribute C are satisfied. Accordingly, the second routing information 412 is generated.

The head publisher / subscriber node A, which has generated a routing table 410 containing the first routing information 411 and the second routing information 412, is the publisher group B that generates an event for attribute B, which is the next attribute of attribute A. The subscription S1 is sent to the head publisher / subscriber node B of the.

Next, the head publisher / subscriber node B receiving the subscription S1 has a routing table including the first routing information 421 and the second routing information 422 in the same manner as the head publisher / subscriber node A. 420, and transmits the subscription S1 to the head publisher / subscriber node C of the publisher group C that generates an event for the next attribute, attribute C.

Subsequently, the head publisher / subscriber node C receiving the subscription S1 receives the first routing information 431 and the second routing information 432 in the same manner as the head publisher / subscriber node A and the head publisher / subscriber node B. Generate a routing table 430 including the &lt; RTI ID = 0.0 &gt; Accordingly, generation of the first routing information 411, 421, and 431 and the second routing information 412, 422, and 432 for the subscription S1 is completed.

Subsequently, subscription S2 including attribute A (attribute condition: 3 <A <8), attribute C (attribute condition: 1 <C <4), and attribute D (attribute condition: 1 <D <3). Is received by the head publisher / subscriber node A, the head publisher / subscriber node A, the head publisher / subscriber node C, and the head publisher / subscriber node D perform the same operations as described above, so that the first routing information 411, 431, 441) and second routing information 412, 432, 442 are generated / updated to update / create the routing table 410, 430, 440.

Accordingly, the generation of the routing tables 410, 420, 430, 440 at the head publisher / subscriber node A to the head publisher / subscriber node D is completed.

FIG. 5 is a diagram for describing an operation of collecting events by a plurality of head publisher / subscriber nodes using the routing table generated in FIG. 4.

Hereinafter, assuming that an event for attribute C, an event for attribute B, and an event for attribute A occur sequentially, an operation of collecting events by a plurality of head publisher / subscriber nodes will be described in detail.

First, if any member publisher / subscriber node included in publisher group C has an event (C = 3) (i.e., an internal event) on attribute C, then head publisher / subscriber node C will receive an event (C = 3). Is received, and it is determined whether the event (C = 3) satisfies the condition information (Rx Event form local) included in the first routing information 431 of the routing table 430.

Referring to FIG. 5, since the event (C = 3) satisfies both condition information (2 <C <5, 1 <C <4), the head publisher / subscriber node C stores the event (C = 3). After that, one of the head publisher / subscriber node A, the head publisher / subscriber node B, and the head publisher / subscriber node C is selected as the next head publisher / subscriber node to transmit an event (C = 3). .

As an example, the head publisher / subscriber node C selects the head next publisher / subscriber node A, which is the common next head publisher / subscriber node for the two condition information, as the next head publisher / subscriber node, to reduce the number of transmissions of the entire event. It is possible to send an event (C = 3) (hereinafter, assume that event (C = 3) is sent to head publisher / subscriber node A).

In this case, in order to prevent the event from being repeatedly transmitted indefinitely, the head publisher / subscriber node C transmitting the internal event may transmit its ID (ID) together with the event (C = 3).

Subsequently, the head publisher / subscriber node A, which received an event (C = 3) from the head publisher / subscriber node C (ie, received an external event), determines whether an event (internal event) for attribute A is stored. do. In this case, since no event for attribute A is stored, the head publisher / subscriber node A discards the received event (C = 3).

Thereafter, if an event (B = 2) (i.e., an internal event) on attribute B occurs at any member publisher / subscriber node included in publisher group B, the head publisher / subscriber node B will receive an event (B = 2 ), And determines whether the event (B = 2) satisfies the condition information included in the first routing information 421 of the routing table 420.

Referring to Fig. 5, since event B = 2 satisfies condition information 1 <B <4, head publisher / subscriber node B stores head event B / subscriber node A and after storing event B = 2. The head publisher / subscriber node of one of the head publisher / subscriber nodes C is selected as the next head publisher / subscriber node, and an event (B = 2) is transmitted (hereinafter, the event (B = 2) to the head publisher / subscriber node C). Is assumed to be sent). In this case, the head publisher / subscriber node B may transmit its ID together with the event (B = 2).

Subsequently, the head publisher / subscriber node C, which received an event (B = 2) from the head publisher / subscriber node B (ie, received an external event), determines whether an event (internal event) for attribute C is stored. do.

At this time, as described above, since the event (C = 3) for the attribute C is stored, the head publisher / subscriber node C has the second condition information (Rx Event from HP) satisfied by the event (B = 2). Determine if it exists.

Referring to FIG. 5, there is second condition information 1 <B <4 satisfied by the event B = 2, and the stored event C = 3 has second condition information 1 <B <4. Satisfies the first condition information (Local received event state) 2 <C <5 for attribute C corresponding to < RTI ID = 0.0 &gt; C, &lt; / RTI &gt; Is collected and transmitted to the head publisher / subscriber node A, which is the next head publisher / subscriber node corresponding to the second condition information (1 <B <4) (in this case, the ID of the head publisher / subscriber node B is also transmitted together). Can be).

Next, the head publisher / subscriber node A, having received the aggregated events (B = 2, C = 3) from the head publisher / subscriber node B (that is, the external event), receives the event (internal event) for attribute A. Determine if is stored.

In this case, since the event for attribute A is still not stored, the head publisher / subscriber node A discards the received events (B = 2, C = 3).

Subsequently, if any member publisher / subscriber node included in publisher group A has an event (A = 4) (i.e., an internal event) on attribute A, then head publisher / subscriber node A generates an event (A = 4). ), And determines whether the event A = 4 satisfies the condition information included in the first routing information 411 of the routing table 410.

Referring to Fig. 5, since event A = 4 satisfies both condition information 1 <A <5, 3 <A <8, the head publisher / subscriber node A stores the event A = 4. And then selects the head publisher / subscriber node of any one of head publisher / subscriber node B, head publisher / subscriber node C, and head publisher / subscriber node D as the next head publisher / subscriber node (preferably the common head node Selects subscriber node C) and transmits an event (A = 4) (assuming that event (A = 4) is transmitted to head publisher / subscriber node C). In this case, the ID of the head publisher / subscriber node A may be transmitted together.

Subsequently, head publisher / subscriber node C, which has received an event (A = 4) from head publisher / subscriber node A (that is, receives an external event), checks whether an event (internal event) for attribute C is stored and It is determined whether there is the second condition information satisfied by the event A = 4 (external event).

At this time, as described above, the event (C = 3) for the attribute C is stored, and the second condition information (1 <A <5, 3 <A <8) satisfied by the event (A = 4) is stored. Exists and the stored event (C = 3) is the first condition information (2 <C <5, 1 <C <) for the attribute C corresponding to the second condition information (1 <A <5, 3 <A <8). 4), the head publisher / subscriber node C collects the external event (A = 4) and the internal event (C = 3) to collect the second condition information (1 <) with the ID of the head publisher / subscriber node A). To Head Publisher / Subscriber Node B or Head Publisher / Subscriber Node D, which is the next Head Publisher / Subscriber Node corresponding to A <5, 3 <A <8). A = 4, C = 3) is assumed to be sent).

Next, the head publisher / subscriber node B that received the aggregated events (A = 4, C = 3) from the head publisher / subscriber node C (that is, the external event) receives an event (internal event) for attribute B. Is stored, and whether the second condition information (Rx Event from HP) satisfied by the events A = 4 and C = 3 (external event) exists.

At this time, as described above, the event (B = 2) for the attribute B is stored, and the second condition information (1 <A <5, 2 <C) satisfied by the events A = 4 and C = 3. <5) exists, and the stored event (B = 2) includes first condition information (1 <B <4) for attribute B corresponding to second condition information (1 <A <5, 2 <C <5). Therefore, the head publisher / subscriber node B aggregates the external events (A = 4, C = 3) and the internal events (B = 2) and together with the IDs of the head publisher / subscriber node A events (A = 4). , B = 2, C = 3), head publisher / subscriber node A or head publisher / subscriber node C, which is the next head publisher / subscriber node corresponding to the second condition information (1 <A <5, 2 <C <5) To send. In this case, the head publisher / subscriber node B has received the event (A = 4, C = 3) via the attributes contained in the received external event (A = 4, C = 3) and the head publisher / subscriber node A and the head. As you can see that it has been via publisher / subscriber node C, head publisher / subscriber node B is responsible for the event (A = 4, B = 2, C = 3) aggregated to head publisher / subscriber node A that originally sent the event. send.

Finally, the head publisher / subscriber node A, who received the aggregated events (A = 4, B = 2, C = 3), receives all attributes (A) included in the subscription (S1) through its ID sent together. It is confirmed that the events related to B, C) have been collected, and the collected events (A = 4, B = 2, C = 3) are transmitted to the arbitrary node that generated the subscription S1.

Accordingly, events for all of the plurality of attributes included in the subscription S1 are collected through the publisher overlay network and delivered to the node that generated the subscription S1.

6 is a flowchart illustrating the overall flow of a method of providing a publish / subscribe service using a P2P network system 100 according to an embodiment of the present invention. Hereinafter, a process performed for each step will be described.

First, in step S610, a subscription is generated at any node of at least one subscriber node and at least two publisher / subscriber nodes. The generated subscription includes a plurality of attributes.

Next, in step S620, a plurality of publisher groups collect events that satisfy conditions (attribute conditions) for a plurality of attributes included in subscriptions generated at the arbitrary nodes through communication with each other.

According to an embodiment of the present invention, the communication between the plurality of publisher groups may correspond to the communication between the head publisher / subscriber nodes included in each of the publisher groups.

Finally, in step S630, an event in which any one publisher group of a plurality of publisher groups is collected is transmitted to the arbitrary node.

According to an embodiment of the present invention, step S630 may be performed by generating a routing table by using a plurality of head publisher / subscriber nodes using attribute conditions for a plurality of attributes included in a subscription occurring at the arbitrary node. And storing. In this case, in step S630, the plurality of head publisher / subscriber nodes may communicate with each other using the generated routing table.

In this case, according to one embodiment of the present invention, the routing table is for selecting the next head publisher / subscriber node to forward the received internal event to when the head publisher / subscriber node receives an internal event from the member publisher / subscriber node. First routing information and second routing information for selecting the next head publisher / subscriber node to aggregate and forward received external and internal events when the head publisher / subscriber node receives an external event from another head publisher / subscriber node; It may include.

So far, embodiments of the method for providing a post / subscribe service using the P2P network system according to the present invention have been described, and the configuration of the P2P network system 100 described with reference to FIG. 1 may be applied to the present embodiment as it is. Do. Hereinafter, a detailed description will be omitted.

In addition, embodiments of the present invention may be implemented in the form of program instructions that can be executed through various computer means and recorded on a computer readable medium. The computer readable medium may include program instructions, data files, data structures, etc. alone or in combination. The program instructions recorded on the medium may be those specially designed and constructed for the present invention or may be available to those skilled in the art of computer software. Examples of computer-readable media include magnetic media such as hard disks, floppy disks, and magnetic tape; optical media such as CD-ROMs and DVDs; magnetic media such as floppy disks; Examples of program instructions, such as magneto-optical and ROM, RAM, flash memory and the like, can be executed by a computer using an interpreter or the like, as well as machine code, Includes a high-level language code. The hardware device described above may be configured to operate as one or more software modules to perform the operations of one embodiment of the present invention, and vice versa.

As described above, the present invention has been described with reference to particular embodiments, such as specific elements, and limited embodiments and drawings. However, it should be understood that the present invention is not limited to the above- Various modifications and variations may be made thereto by those skilled in the art to which the present invention pertains. Accordingly, the spirit of the present invention should not be construed as being limited to the embodiments described, and all of the equivalents or equivalents of the claims, as well as the following claims, belong to the scope of the present invention .

100: P2P network system 110: subscriber overlay network
111: subscriber node 120: publisher overlay network
121: Publisher / subscriber node 121a: Head publisher / subscriber node
121b, 121c, 121d: Member publisher / subscriber nodes
122: Bootstrap Server 123: New Publisher / Subscriber Node
410, 420, 430, 440: routing table
411, 421, 431, and 441: first routing information
412, 422, 432, 442: second routing information

Claims (15)

In a peer-to-peer network system including a plurality of nodes,
At least one node (subscriber node) that acts as a subscriber to generate a subscription including a plurality of attributes; And
At least two nodes (publisher / subscriber nodes) acting as publishers or acting as subscribers to generate an event corresponding to some of the plurality of attributes,
The two or more publisher / subscriber nodes are grouped into a plurality of publisher groups consisting of at least one publisher / subscriber node,
The plurality of publisher groups may satisfy conditions (attribute conditions) for a plurality of attributes included in a subscription occurring at any one of the at least one subscriber node and the at least two publisher / subscriber nodes through mutual communication. And a publisher group of any one of the plurality of publisher groups transmits the collected events to the arbitrary nodes. The method of claim 1,
And the at least two publisher / subscriber nodes are grouped into the plurality of publisher groups according to whether the generated attributes are the same. The method of claim 1,
The at least one subscriber node and the two or more publisher / subscriber nodes are connected according to a topology to form a subscriber overlay network, and the one publisher group is any one node included in the subscriber overlay network. Send the aggregated event to
The aggregated event is a P2P network system capable of providing a publish / subscribe service, characterized in that transmitted from any one node to the arbitrary node through a connection according to the predetermined topology. The method of claim 1,
Each of the plurality of publisher groups includes one head publisher / subscriber node and at least one member publisher / subscriber node, and communication between the plurality of publisher groups is each included in the plurality of publisher groups. A P2P network system capable of providing a publish / subscribe service, which corresponds to communication between subscriber nodes (a plurality of head publisher / subscriber nodes). Claim 5 was abandoned upon payment of a set-up fee. 5. The method of claim 4,
The two or more publisher / subscriber nodes are grouped into the plurality of publisher groups according to whether the occurring attributes are the same,
Each of the plurality of head publisher / subscriber nodes generates and stores a routing table using attribute conditions for a plurality of attributes included in a subscription generated by the arbitrary node, and communicates with each other using the routing table. P2P network system capable of providing a publish / subscribe service, characterized in that performed. Claim 6 has been abandoned due to the setting registration fee. The method of claim 5,
The routing table is
First routing information for selecting a next head publisher / subscriber node to forward the internal event to when the head publisher / subscriber node receives an event (internal event) from the member publisher / subscriber node;
If the head publisher / subscriber node receives an event (external event) from another head publisher / subscriber node, second routing information for selecting the next head publisher / subscriber node to aggregate and deliver the external event and the internal event;
P2P network system capable of providing a post / subscription service comprising a. Claim 7 was abandoned upon payment of a set-up fee. The method according to claim 6,
The first routing information includes condition information including attribute conditions for some attributes occurring in a publisher group including a corresponding head publisher / subscriber node among a plurality of attributes included in a subscription occurring in the arbitrary node; Head publisher / subscriber node information,
The next head publisher / subscriber node information includes k (an integer of 1 or more) attributes other than some attributes occurring in the publisher group to which the head publisher group belongs among the plurality of attributes included in the subscription generated at the arbitrary node. A P2P network system capable of providing a publish / subscribe service, characterized in that information of a head publisher / subscriber node included in k publisher groups generating an event for each is included. Claim 8 was abandoned when the registration fee was paid. The method of claim 7, wherein
The head publisher / subscriber node that has received the internal event stores the internal event when the internal event satisfies the condition information, and any one of information of the head publisher / subscriber node included in the k publisher groups, respectively. The P2P network system capable of providing a publish / subscribe service, characterized in that for transmitting the internal event to the head publisher / subscriber node corresponding to any one of the information using the information. Claim 9 has been abandoned due to the setting registration fee. The method according to claim 6,
The second routing information includes first condition information including attribute conditions for some attributes occurring in a publisher group including a corresponding head publisher / subscriber node among a plurality of attributes included in a subscription generated in the arbitrary node. And attribute conditions for k (an integer of 1 or more) attributes other than some attributes occurring in the publisher group to which the head publisher group belongs, among a plurality of attributes included in the subscription occurring in the arbitrary node. k second condition information, and k next head publisher / subscriber node information corresponding to the k second condition information, respectively;
In the k next head publisher / subscriber node information, i (an integer of 1 or more and less than k) generates an event for the i-th attribute among the publisher groups that generate an event for the k attributes. A P2P network system capable of providing a publish / subscribe service, characterized in that the information includes the head publisher / subscriber node included in each publisher group except the publisher group. Claim 10 has been abandoned due to the setting registration fee. 10. The method of claim 9,
The head publisher / subscriber node receiving the internal event stores the internal event when the internal event satisfies the condition information.
The head publisher / subscriber node receiving the external event has the internal event stored therein, and the external event satisfies at least one second condition information of the k second condition information. The external event and the internal event to the head publisher / subscriber node corresponding to the one information by using any one of the head publisher / subscriber node information included in at least one next head publisher information corresponding to the condition information. P2P network system capable of providing a post / subscription service, characterized in that the aggregated event. At least one node (subscriber node) that acts as a subscriber generating a subscription that includes a plurality of attributes and a publisher that generates an event corresponding to an attribute of some of the plurality of attributes or as a subscriber and operates as a subscriber A method of providing a publish / subscribe service using a P2P network system including at least two nodes (publisher / subscriber nodes) grouped into a publisher group of,
Generating a subscription at any of the at least one subscriber node and the at least two publisher / subscriber nodes;
Collecting, by the plurality of publisher groups, an event that satisfies a condition (attribute condition) for a plurality of attributes included in a subscription generated at the arbitrary node through communication with each other; And
Any one publisher group of the plurality of publisher groups sends the aggregated event to the arbitrary node;
Method of providing a post / subscription service using a P2P network system comprising a. The method of claim 11,
The at least two publisher / subscriber nodes are grouped into the plurality of publisher groups according to whether the generated attributes are the same. The method of claim 11,
Each of the plurality of publisher groups includes one head publisher / subscriber node and at least one member publisher / subscriber node, and communication between the plurality of publisher groups is each included in the plurality of publisher groups. A method of providing a publish / subscribe service using a P2P network system, which corresponds to communication between subscriber nodes (a plurality of head publisher / subscriber nodes). The method of claim 13,
The two or more publisher / subscriber nodes are grouped into the plurality of publisher groups according to whether the occurring attributes are the same,
Aggregating the event
Wherein each of the plurality of head publisher / subscriber nodes generates and stores a routing table using attribute conditions for a plurality of attributes included in a subscription occurring at the arbitrary node, and using the routing table. Method of providing a publish / subscribe service using a P2P network system, characterized in that to perform communication with each other. Claim 15 is abandoned in the setting registration fee payment. 15. The method of claim 14,
The routing table is
First routing information for selecting a next head publisher / subscriber node to forward the internal event to when the head publisher / subscriber node receives an event (internal event) from the member publisher / subscriber node;
If the head publisher / subscriber node receives an event (external event) from another head publisher / subscriber node, second routing information for selecting the next head publisher / subscriber node to aggregate and deliver the external event and the internal event;
Method of providing a post / subscription service using a P2P network system comprising a.

Images