KR101001755B1 - Policy Creation Method for Differentiated Services - Google Patents

Abstract

The present invention relates to a method of defining each component constituting the differentiated service data path as a rule and combining the rules to create a policy.

To this end, the present invention provides a method for generating a policy in a policy controller for a differentiated service that changes data paths according to types of services, each component constituting a data path of the differentiated service, a parameter corresponding to each component. Type of, preparing a combination rule between each component; Displaying each component and a combination rule between the components on a screen according to a policy generation request from an operator; Receiving an input of each parameter by displaying a parameter input window corresponding to the corresponding element on the screen when a certain element is selected from the operator; And generating a data path connecting the selected components in order according to a registration request from the operator as a policy of a corresponding service, wherein each component includes a classifier, metering, and action. (Action), algorithmic drop (Algorithmic Drop), Queue (Queue), the combination rule, the classifier (C), the metering (M) and the action (A) behind the respective components can be connected but After the algorithmic drop (D) and the queue (Q) is characterized in that the same component as its own can not be connected.

Policy Management, QoS, Differentiation Service, Data Path, Policy Management Tool, Policy Decision Point

Description

How to create a policy for differentiated services {Method of framing policy for a differentiated services}             

1 is a view showing the components constituting the data path of the differentiation service,

2 is a functional block diagram illustrating a policy management QoS framework;

3 is a diagram illustrating an example of a policy applied to a differentiated service;

4 is a flowchart illustrating an operation of generating a policy by the policy console according to the present invention.

[Description of Reference Numerals]

210: Policy console 220: Policy management tool

230: Policy Store 240: Policy Decision Point

250: mens

The present invention relates to a method for creating a policy for a differentiated service, and more particularly, to a method for creating a policy by defining each component constituting the differentiated service data path as a rule and combining the corresponding rules.

As the Internet develops, users' demand for the quality of Internet services is increasing. In particular, as multimedia services become more popular, services that require real-time processing and require high bandwidth are becoming more diverse, and types thereof are also increasing. In addition, different quality of service (QoS) is required according to various users and Internet service types. In general, since the Internet supports best effort without considering service quality for each service type, the Internet cannot support differentiation of services by service type for each user.

The IETF, the Internet standardization organization, is conducting standardization on providing services in consideration of QoS according to various users and types of Internet services. One of the standardization models is DiffServ (Differed Services) model. This differentiated service (DiffServ) refers to a service that makes it possible to apply various services with scalability in a large network by discriminating the service by a set of packet flows of a real-time application service. This differentiated service provides different quality of service for each set with a flow set as a unit, makes all complex traffic control functions only at the edge of the network, and performs only very simple packet forwarding function internally. (ISP) has the scalability to be applicable to the large Internet network to which the network is connected.

The components of the data path of the differentiated service are classified as Classifier, Metering, Action, Algorithmic Drop, and Queue, as set out in the Standard (RFC3289). It consists of five components.

The data path of this differentiation service may begin or end with any component as shown in FIG. 1. Any component can be connected after the classifier (C), metering (M), or action (A) components, but before and after the algorithmic drop (D) and cue (Q) components, It cannot be connected. That is, one of the components of type A may be connected to the classifier (C), metering (M), and action (A) components, and one of the components of type C may be connected to the algorithmic drop (D) component. One of the components of type B may be connected to the queue (Q) component.

Type A includes all the components, and depending on the components, it is in the form of an infinite loop that is connected to types A, B, and C again. Type B may be connected after the queue (Q) component, and may include other components except for the queue (Q) component, and type A or C may be connected after the type B. Type C may be connected after the algorithmic drop (D) component, and may include other components except the algorithmic drop (D) component, which may be connected with type A or B.

As described above, the data path of the differentiated service may theoretically have an infinite number of cases, and therefore, a user interface for generating a policy that accurately reflects these characteristics is difficult and complicated to implement. It is also necessary to constantly modify the program, even if it can be implemented.                         

In order to apply the policy for differentiated services to network devices, the policy should be created according to the complex Management Information Base (MIB) structure as described in the standard (RFC3289) above, and appropriate values should be set according to each policy. However, as described above, the data path of the differentiated service is not limited by the number and order of its components, and the number of data paths that can be theoretically implemented is infinite. Therefore, it is necessary to develop a method for easily generating a data path conforming to a policy. Do.

An object of the present invention proposed to meet the needs of the prior art described above, when creating a policy for differentiation service in the policy management QoS framework, each component of the data path is defined as a rule and the corresponding rules are combined. It is to provide a method for creating a policy.

The present invention for achieving the above object, in the policy generation method in the policy controller for the differentiation service to change the data path for each type of service, each component constituting the data path of the differentiation service, each configuration Preparing a type of parameter corresponding to the element and a combination rule between the respective elements; Displaying each component and a combination rule between the components on a screen according to a policy generation request from an operator; Receiving an input of each parameter by displaying a parameter input window corresponding to the corresponding element on the screen when a certain element is selected from the operator; And generating a data path connecting the selected components in order according to a registration request from the operator as a policy of a corresponding service, wherein each component includes a classifier, metering, and action. (Action), algorithmic drop (Algorithmic Drop), Queue (Queue), the combination rule, the classifier (C), the metering (M) and the action (A) behind the respective components can be connected but After the algorithmic drop (D) and the queue (Q) is characterized in that the same component as its own can not be connected.

delete

Hereinafter, with reference to the accompanying drawings will be described in more detail "policy generation method for differentiation service" according to an embodiment of the present invention.

2 is a functional block diagram illustrating a policy management QoS framework. This includes a policy console 210, a policy management tool 220, a policy repository 230, and a policy decision point 240. The policy console 210 receives data for policy generation from the user and delivers the data to the policy management tool 220. The policy management tool 220 receives the user's command, interprets and verifies the policy rule, stores the appropriate policy in the policy store 230, and monitors the topology and state information of the network 250 to monitor the network topology and state information. Store in the policy store 230. The policy repository 230 stores policy, network topology, and state information. The policy decision point 240 executes a user command received from the policy management tool 220. The policy vertex 240 searches a policy of the policy repository 230 and converts the policy into a device-dependent form according to the components of the network 250. Provide to each policy enforcement point. This policy enforcement point refers to each router that constitutes the network.

The policy console 210 provides a user interface for a user to create a policy. Each data path component of a differentiation service that a user can use in a policy is defined as a rule for forming a policy, and the user By associating them in the required order, the policy of differentiation service can be easily and easily created.

3 illustrates an example of a policy applied to a differentiated service. The policy illustrated in FIG. 3 includes a classifier C, a classifier C, a metering M, an action A, an action A, an algorithmic drop D, and a queue Q. The input data is output via a data path consisting of the above-described components C → C → M → A → A → D → Q. According to the present invention, each data path component described above is defined as a rule, and a user can easily create a necessary policy by selecting a rule according to each component and inputting information necessary for the rule. That is, in order to create a policy composed of the above-described data paths, the user may use a classifier rule (CR), a classifier rule (CR), a metering rule (MR), an action rule (AR), an action rule (AR), and an algorithmic drop rule. (DR) and the queue rule (QR) are selected sequentially, and necessary information may be input. The created policy is verified by the policy management tool and executed at any policy enforcement point.                     

4 is a flowchart illustrating an operation of generating a policy by the policy console according to the present invention.

First, the policy console defines and stores five components constituting the differentiated service data path as rules (S401). If there is a policy generation request from the operator (S402), the main screen for policy generation is displayed (S403). The main screen for creating a policy displays a policy type, a policy name, a creation rule for configuring a policy, and provides an environment for an operator to select a component rule to create.

In the main screen, the operator sequentially selects the component rules constituting the policy he wants to create and inputs parameter values necessary for the corresponding component rule to create the corresponding component rule.

When the policy console generates a classifier rule generation request from the operator (S404), the policy console displays a classifier rule generation screen (S405). The classifier rule creation screen displays the rule type, rule name, and required parameter input window (source IP address, destination IP address, source port, destination port, DSCP (DiffServ Code Point, etc.)). When the operator inputs a parameter for classifier rule generation and requests a rule registration (S406), the policy console stores the classifier rule and displays it on the main screen (S407). If a policy generation completion request is input (S408), the policy generation process is terminated, and if there is another rule generation request, the process returns to step S404.

 If a metering rule generation request is input from the operator (S409), the policy console displays a metering rule generation screen (S410). The metering rule creation screen displays the rule type, rule name, and the required parameter input window (metering algorithm, token bucket rate, burst size, time interval, etc.). When the operator inputs a parameter for generating a metering rule and requests a rule registration (S411), the policy console stores the metering rule and displays it on the main screen (S412). If the policy generation completion request is inputted to step S408, the policy generation process is terminated, and if there is another rule generation request, the process returns to step S404.

When the action rule generation request is input from the operator (S413), the policy console displays the action rule generation screen (S414). The action rule creation screen displays the rule type, rule name, and the required parameter input window (DSCP, action count, etc.). When the operator inputs a parameter for generating an action rule and requests a rule registration (S415), the policy console stores the action rule and displays it on the main screen (S416). If the policy generation completion request is inputted to step S408, the policy generation process is terminated, and if there is another rule generation request, the process returns to step S404.

If an algorithmic drop rule generation request is input from an operator (S417), the policy console displays an algorithmic drop rule generation screen (S418). The Create Algorithmic Drop Rule screen displays the rule type, rule name, and required parameter inputs (Algorithmic Drop Type, Queue Depth, Drop Minimum Threshold, Drop Maximum Threshold, Maximum Disposability, Drop Weight, Drop Sampling Rate, etc.). Is displayed. When the operator inputs a parameter for generating an algorithmic drop rule and makes a rule registration request (S419), the policy console stores the algorithmic drop rule and displays it on the main screen (S420). If the policy generation completion request is inputted to step S408, the policy generation process is terminated, and if there is another rule generation request, the process returns to step S404.

If a queue rule creation request is input from the operator (S421), the policy console displays a queue rule creation screen (S422). This queue rule creation screen displays the rule type, rule name, and necessary parameter input window (scheduling method, scheduling priority, fixed minimum rate, fixed maximum rate, minimum rate threshold, etc.). When the operator inputs a parameter for creating a queue rule and requests a rule registration (S423), the policy console stores the queue rule and displays it on the main screen (S424). If the policy generation completion request is inputted to step S408, the policy generation process is terminated, and if there is another rule generation request, the process returns to step S404.

When the policy creation process of the policy console is finished, the policy management tool interprets the newly created policy consisting of the component rules and verifies that it is a suitable policy. Appropriate policies are stored in the policy store and applied to policy enforcement points by commands from the policy management tool. At this time, the policy decision point converts each policy into a form suitable for the device to which the policy is applied and delivers it to the application device.

While the invention has been described above based on the preferred embodiments thereof, these embodiments are intended to illustrate rather than limit the invention. It will be apparent to those skilled in the art that various changes, modifications, or adjustments to the above embodiments can be made without departing from the spirit of the invention. Therefore, the protection scope of the present invention will be limited only by the appended claims, and should be construed as including all such changes, modifications or adjustments.

As described above, according to the present invention, since the QoS policy for the differentiated service can be easily and simply implemented in the policy-based framework, there is an advantage of accommodating the service needs of various users.

Claims (3)

In the policy generation method in the policy controller for the differentiated service that changes the data path for each type of service, Preparing each component constituting a data path of the differentiating service, types of parameters corresponding to each component, and a combination rule between the components; Displaying each component and a combination rule between the components on a screen according to a policy generation request from an operator; Receiving an input of each parameter by displaying a parameter input window corresponding to the corresponding element on the screen when a certain element is selected from the operator; And Generating a data path connecting the selected components in order according to a registration request from the operator as a policy of a corresponding service; Each of the above components, Classifier, Metering, Action, Algorithmic Drop, Queue, The combination rule is, The components may be connected to the classifier C, the metering M, and the action A, but the same components may be connected to the rear of the algorithmic drop D and the cue Q. Policy generation method for a differentiated service, characterized in that there is no. delete delete

Images