KR100439185B1 - Method for loading programs in the active network model and hybrid active network node - Google Patents

Abstract

Disclosed are a mixed active network model and a packet processing method in an active network model.

According to the present invention, active packets are classified into 'sigAflow' packets, 'Aflow' packets, and 'non-Aflow' packets according to whether packet processing is accelerated and whether packet delivery is persistent. A hybrid active node model for processing That is, the active network technology according to the present invention can provide a flexible network environment by allowing the active node to dynamically load and expand a service necessary for executing an active packet and program codes for implementing the same into the active node on the network. Frequently required service and program codes are pre-installed in the active node and can be processed at high speed when the active packet arrives at the active node.

Description

METHOD FOR LOADING PROGRAMS IN THE ACTIVE NETWORK MODEL AND HYBRID ACTIVE NETWORK NODE}

The present invention relates to an active networking technology, and more particularly, to a hybrid active network model and a packet processing method in an active network model suitable for dynamically loading and processing resources required for active packet execution in an active node.

Two methods can be applied to the active node to execute the active packet transmitted along the network.

One of them involves residing necessary services and program codes in a node in advance. When a packet including a program identifier and data desired to be executed arrives, a program corresponding to the program identifier is loaded into the node and processed together with the data. It is called.

However, this method is applicable only to a program that already exists in the node, there is a problem that it is not easy to add a new program.

The other method is to load a program and data in a packet without storing the program in the node, and to process the program and data included in the packet in the node's own execution environment.

Such a method may cause a problem that packet transmission efficiency may be deteriorated, since a traffic problem on a network, a retransmission problem when a packet is lost, and the like may occur, particularly when a program to be delivered is large.

In order for an active node to execute an active packet transmitted along a network, it is necessary to load a node with necessary services and program codes for implementing the active packet. A frequently used program is loaded into the node in advance, and a packet requesting the corresponding program is loaded on the node. When delivered, it needs to process the packet quickly.

In addition, infrequently used programs need to be loaded and loaded from a code server or other active node only when required by the packet, thereby reducing the load on the node so that unnecessary or less frequently used programs and services are not dependent on the node.

SUMMARY OF THE INVENTION The present invention has been made in view of the above-mentioned necessity, and is classified into an 'Aflow' packet, a 'non-Aflow' packet, and a 'sigAflow' packet according to whether the packet delivery period is persistent in terms of speeding up the packet processing and real time. A hybrid active network model and a method for processing a packet in an active network model that dynamically load resources required for packet execution to an active node to realize a high packet processing speed, a small amount of node-dependent resources, and a flexible network environment. The purpose is to provide.

According to an embodiment of the present invention for achieving the above object, in the mixed active network model, the active packet received from the network device is distributed, and the packet classified as the active packet is used for demux key matching. A node operating system block classified into a corresponding flow packet and allocating, controlling, and returning arbitrary node resources; It provides a mixed active network model characterized in that it comprises a execution environment block for detecting the type value of the packet header of the active packet provided from the node operating system block, and classifies the received packet into the corresponding flow packet according to the detected type value .

According to another exemplary embodiment of the present invention, a network classifier includes a packet classifier, a node operating system block including a flow classifier, and an execution environment block for detecting a type field of an active packet header. In a packet processing method in an active network model that receives a packet transmitted to an active node through a packet, if any packet is received by the packet classifier, the protocol field of the received packet header is set to a value indicating that the packet is an active packet. Judging; If the protocol field of the received packet header is set to a value indicating that the packet is an active packet, the packet classifier classifies the received packet into an active packet and provides the packet to the flow classifier; Determining, by the flow classifier, whether the demux key field of the packet matches, and classifying the packet as an 'Aflow' packet if the demux key field matches; If the demux key field does not match, providing a packet to the execution environment block to detect the type field of the packet header; Classifying the packet as a 'sigAflow' packet when the type value of the packet header detected in the execution environment block is '0'; And classifying the packet into a 'non-Aflow' packet when the type value of the packet header detected in the execution environment block is '2'.

1 is a configuration diagram of a mixed active network according to the present invention;

2 is a flowchart of a packet classification process in an active network model according to an embodiment of the present invention;

FIG. 3 is a flow classification result of FIG. 2 for explaining a processing process when classifying a 'sigAflow' packet; FIG.

FIG. 4 is a flow classification result of FIG. 2 for explaining a process of classifying an 'Aflow' packet; FIG.

FIG. 5 is a flow classification result of FIG. 2 illustrating a processing process when classifying a non-Aflow packet. FIG.

<Description of the code | symbol about the principal part of drawing>

11: packet classifier

12: flow sorter

13: active packet generator

14: flow manager

15: channel manager

21: execution environment controller

22: sensor loader

23: node state manager

24: sensor processor

100: node operating system block

200: execution environment block

300: active application block

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

Prior to the description, the core technical gist of the present invention is to classify active packets according to the speed of packet processing and the persistence of packet forwarding, and dynamically load the resources necessary to execute the packets to the active node to process the packets. From this technical idea, it is possible to easily achieve the object of the present invention.

1 is a configuration diagram of a mixed active node according to the present invention, and may be broadly divided into a node operating system block 100, an execution environment block 200, and an active application block 300.

Here, the node operating system block 100 includes a packet classifier 11, a flow classifier 12, an active packet generator 13, a flow manager 14, and a channel manager 15. A performance environment controller 21, a sensor loader 22, a node state manager 23, a sensor processor 24, respectively.

The node operating system block 100 performs a function of allocating, controlling, and returning node resources required by the execution environment block 200.

In addition, the node operating system block 100 distributes the active packet received from the network device to the execution environment block 200 and performs a function of transferring the result data from the execution environment block 200 to the third node.

As shown in FIG. 1, the node operating system block 100 includes a packet classifier 11, a flow classifier 12, and the like, and the packet classifier 11 converts a received packet into an active packet or a general IP packet. The flow classifier 12 classifies a packet classified as an active packet in the packet classifier 11 into a corresponding flow packet according to whether or not a demox key is matched as described later. This packet classification and flow classification process will be described in more detail in the flowchart of FIG. 2.

On the other hand, the execution environment block 200 is a virtual machine (virtual machine), after processing the active packet from the node operating system block 100 through the execution code, and as a result the data to the active application block 300 or node operating system Perform the function of passing to block 100. That is, the execution environment block 200 detects the type value of the packet header of the active packet provided from the node operating system block 100 and classifies the received packet into the corresponding flow packet according to the detected type value.

Hereinafter, the packet classification process in the active network model according to the preferred embodiment of the present invention will be described in detail with reference to the flowchart of FIG. 2.

First, if any packet is received by the packet classifier 11 (S200), the packet classifier 11 proceeds to step S202 to determine whether the received packet is classified as an active packet according to the presence or absence of an 'ANEP' header in the packet. In this case, it is determined whether to classify as a general IP packet.

That is, if the protocol field of the IP packet header is not set to a value indicating that it is an active packet, the packet classifier 11 proceeds to step S204 to consider the packet as a general IP packet, and the protocol field of the IP packet header is active. If it is set to a value indicating that a packet, the packet classifier 11 proceeds to step S206 to regard the packet as an active packet.

Thereafter, in step S208, the packet classified as the active packet is provided to the flow classifier 12 to perform a flow classification process and proceed to step S210.

In step S210, the flow classifier 12 selects an execution environment or a flow to which the corresponding active packet should be delivered by referring to a demux key field of the corresponding packet.

That is, the flow classifier 12 determines whether the demux key field matches in step S210, and if the demux key field matches, classifies the packet into an 'Aflow' packet after proceeding to step S212. If the demux key field does not match, the flow proceeds to step S214.

From step S214, the processes are performed in the execution environment block 200.

In step S214, the execution environment block 200 detects a type field of the active packet header, and proceeds to step S216 to perform a determination process accordingly.

As a result of the determination in step S216, if the type value of the detected active packet header is '0', the process proceeds to step S218 and classifies the packet as a 'sigAflow' packet.

If the type value of the detected active packet header is '2' (S220), the execution environment block 200 proceeds to step S222 and classifies the packet as a 'non-Aflow' packet.

FIG. 3 is a flow classification result of FIG. 2 illustrating a processing process when classifying a 'sigAflow' packet.

First, a 'sigAflow' packet is a packet used to deliver information necessary for generating and terminating a flow for an 'Aflow' packet and information necessary for loading a sensor. Therefore, the 'sigAflow' packet basically specifies a request to create / terminate a flow for the 'Aflow' packet, and includes information necessary to distinguish the 'Aflow' packet and address information where the code of the 'Aflow' packet is located. do.

A 'sigAflow' packet can reduce the number and cost of code requests by optionally including the common active code that other nodes may need in the data portion of the packet for efficient code loading.

When the 'sigAflow' packet for generating the flow reaches the execution environment block 200 through the node operating system block 100, the execution environment controller 21 in the execution environment block 200 generates a single packet for the corresponding 'Aflow' packet. Create a flow and request the necessary resources to the node operating system block 100.

At this time, the flow generation for the 'Aflow' packet should be performed at all intermediate nodes from the source node to the destination node of the 'Aflow' packet. When the 'sigAflow' packet for ending the flow arrives, the flow is terminated and the allocated resources are allocated. Release it.

FIG. 4 is a diagram illustrating a processing process when classifying an 'Aflow' packet as the flow classification result of FIG. 2 described above.

First, an 'Aflow' packet is a packet generated by the active application block 300 in terms of maintaining correlation with time, resource allocation, data sharing, and the like.

In order to maintain such correlation, state information on the processing and execution result of these packets should be maintained at an intermediate active node from the source node to the destination node of the active application block 300. In other words, the intermediate active node must create a flow for the corresponding 'Aflow' packet and keep it continuously until the 'Aflow' ends.

To this end, a 'sigAflow' packet as described above with reference to FIG. 3 is used.

Since the packets belonging to 'Aflow' are delivered after the flow is generated at the intermediate nodes from the source to the destination through the 'sigAflow' packet, the node receiving the packet belonging to the 'Aflow' is quickly transmitted through the packet classifier 11. Classifies and processes them using the pre-generated flow, thus enabling fast packet processing.

In addition, since the 'sigAflow' packet provides information for demux key and code loading of the packet, only the required version and type fields exist in the 'Aflow' packet header.

Thus, 'Aflow' packets are suitable for real-time applications that require fast packet processing and quality of service (QoS) guarantees.

An 'Aflow' packet is delivered to an input channel of a preset flow to a node through a packet classification process. The packet is processed using a resource of a predetermined flow, and delivers the execution result to the node's own active application block 300 or the next active node.

FIG. 5 is a diagram illustrating a processing process when classifying a non-Aflow packet as a flow classification result of FIG. 2.

First, a 'non-Aflow' packet is a packet that is transmitted and processed independently of other active packets generated by the same active application. Therefore, since there is no need for the active node to maintain their interrelationships, the node does not need to continue specific flows for 'non-Aflow' packets, and also forwards these packets to specific flows in the packet classifier 11. You don't have to.

Therefore, the 'non-Aflow' packet is suitable for active applications in which the path of the packet is not constant and the delivery period of the packet is not continuous.

The 'non-Aflow' packet is delivered to the execution environment block 200 through a packet classification process through the packet classifier 12. Like the 'Aflow' packet, the 'non-Aflow' packet requires active code execution, but because there is no preset resource, the execution environment generates a temporary flow and terminates the flow immediately after processing the corresponding 'non-Aflow' packet. Let's do it.

That is, the present invention classifies the packets transmitted to the active node through the network into the active packet and the general IP packet, and then distributes the classified active packet to the corresponding execution environment in the active node. By considering the two cases of 'Aflow' and 'non-Aflow' packets according to whether the packet delivery period is persistent, and the case of additional 'sigAflow' packets for the case where packet delivery should be maintained continuously In other words, the active node dynamically loads the resources needed to execute the active packet.

As mentioned above, although this invention was concretely demonstrated based on the Example, this invention is not limited to this Example, Of course, various changes are possible within the range which does not deviate from the summary.

As described above, according to the present invention, a network service and a program that is continuously and frequently required are pre-installed in an active node, so that when a packet actually requesting a service arrives at the active node, the packet can be processed at high speed. It works. In addition, by dynamically loading and expanding services and program codes that are not continuously used on the active node on the network, it is possible to construct a network environment that can pursue the lightweighting of the active node and the flexibility of the network environment.

Claims (6)

In the mixed active network model, Node operating system block that distributes active packets received from network devices, classifies packets classified as active packets into corresponding flow packets according to the presence or absence of demux key matching, and allocates, controls, and returns arbitrary node resources. and; And an execution environment block for detecting a type value of a packet header of an active packet provided from the node operating system block, and classifying a received packet into a corresponding flow packet according to the detected type value. The method of claim 1, The classified flow packet is, Hybrid active network model, characterized in that any one of the 'Aflow' packet, 'sigAflow' packet, 'non-Aflow' packet. An active network model including a node classifier block including a packet classifier and a flow classifier, and an execution environment block for detecting a type field of an active packet header, and receiving a packet transmitted to an active node through a network. In the packet processing method in If an arbitrary packet is received by the packet classifier, determining whether a protocol field of the received packet header is set to a value indicating that the packet is an active packet; If the protocol field of the received packet header is set to a value indicating that the packet is an active packet, the packet classifier classifies the received packet into an active packet and provides the packet to the flow classifier; Determining, by the flow classifier, whether the demux key field of the packet matches, and classifying the packet as an 'Aflow' packet when the demux key field matches; If the demux key field does not match, providing the packet to the execution environment block to detect a type field of the packet header; Classifying the packet as a 'sigAflow' packet when a type value of a packet header detected in the execution environment block is '0'; And classifying the packet as a 'non-Aflow' packet when the type value of the packet header detected in the execution environment block is '2'. The method of claim 3, wherein The 'Aflow' packet is, A packet processing method in an active network model, characterized in that high-speed packet processing is possible while maintaining correlation with time, resource allocation, and data sharing. The method of claim 3, wherein The 'sigAflow' packet is, The packet processing method of the active network model, characterized in that the packet used to deliver the information necessary for generating and terminating the flow for the 'Aflow' packet and the sensor loading information. The method of claim 3, wherein The 'non-Aflow' packet is a packet which is transmitted and processed independently, and is applied to an active application in which the path of the packet is not constant and the delivery period of the packet is not continuous.