KR102116460B1 - Sdn controller for managing flow mobility by service and method for managing flow mobility by service using the same - Google Patents

Abstract

A method of managing flow mobility for each service of an SDN controller according to an aspect of the present invention includes: receiving, by the SDN controller, a router access request message of a mobile node transmitted through a first AP; Assigning a different prefix for each flow for each flow based on information on the service type of the flow included in the router access request message by the mobile node; Matching the assigned prefix information with the mobile node information and AP information connected to the mobile node and storing the information in the BCE; And setting a path for each flow based on the information on the service type of the flow and transmitting the flow of the mobile node to the destination node according to the set path. At this time, the router access request message identifies information about the service type of the flow recorded by the mobile node, the first type for which session maintenance is unnecessary, the second type for which session maintenance of the flow is required, or the third type for which the IP of the flow is fixed. The information is recorded, and the step of establishing a route resets the anchor of the mobile node when the service type corresponds to the second type when the handover of the mobile node occurs, and the service type is the first type or the third If it is the type, the optimal path is recalculated.

Description

SDN controller that manages flow mobility for each service and mobility management method using the same {SDN CONTROLLER FOR MANAGING FLOW MOBILITY BY SERVICE AND METHOD FOR MANAGING FLOW MOBILITY BY SERVICE USING THE SAME}

The present invention relates to a method and apparatus for managing mobility of a flow according to a service type of a flow used by a mobile node in an SDN network environment.

Recently, as the transmission speed of data communication has evolved through 5G networks, various services have been added. Due to this, the number of services used by the terminal is diversified, and the number of terminals used in the network is also increasing. The user wants to receive a seamless service, but when the terminal moves to another AP (Access Point), when performing handover, it is difficult to provide a continuous service because a temporary disconnection occurs. In the case of a real-time streaming service in 5G, the service disconnection phenomenon causes inconvenience to the user, and thus requires differentiated mobility management for each service.

In order to continuously provide a real-time streaming service, it is necessary to be able to maintain a session even when the terminal moves. The existing mobility management technique manages mobility for each user terminal and fixes a node of the path as an anchor during handover. This increases the packet delivery cost and the handover delay because the packet path cannot always be the optimal path.

In order to solve these problems, a technique for dynamically setting anchors has been proposed. It is known that there is an advantage of reducing the packet delay cost and the handover delay by dynamically setting the anchor. However, in a 5G network environment, when each terminal uses several services together, signaling cost and handover delay are generated according to the number of flows.

In order to solve these problems, recent studies suggest a method of managing mobility for each flow, but the technique of selecting an anchor according to the type of individual service is unknown.

Republic of Korea Patent Publication No. 2014-0088379 (Name of the invention: a method for supporting the mobility of a mobile station in a wireless communication system)

One embodiment of the present invention is to solve the above-described problems of the prior art, to distinguish the flow used in the mobile node according to the service type, the mobility of the terminal according to the method of setting the anchor for the flow that requires real-time service It is intended to provide an SDN controller capable of managing and a mobility management method using the same.

However, the technical problem to be achieved by the present embodiment is not limited to the technical problem as described above, and other technical problems may exist.

As a technical means for achieving the above-described technical problem, a method for managing mobility of a flow for each service of a Software-Defined Networking (SDN) controller according to an aspect of the present invention is a method in which the SDN controller is transmitted through a first AP Receiving a router solicitation message from the node; Assigning, by the mobile node, a different prefix for each service type for each flow based on information on the service type of the flow included in the router access request message; Matching the assigned prefix information with the mobile node information and the AP information connected to the mobile node and storing it in a binding cache entry (BCE); And setting a path for each flow based on the information on the service type of the flow and transmitting the flow of the mobile node to the destination node according to the set path. At this time, the router access request message is classified as a first type that does not require session maintenance, a second type that requires session maintenance of the flow, or a third type where the IP of the flow is fixed as information about the service type of the flow recorded by the mobile node. The information to be recorded is recorded. In addition, the step of establishing the route resets the anchor of the mobile node when the service type corresponds to the second type when the handover of the mobile node occurs, and the service type is assigned to the first type and the third type. Recalculate the optimal path, if applicable.

In addition, a software-defined networking (SDN) controller that manages flow mobility for each service according to another embodiment of the present invention executes a memory in which a program for managing flow mobility for each service is stored and a program stored in the memory And a processor for receiving a Router Solicitation message of a mobile node transmitted through the first AP by execution of the program, and included in the Router Access Request message by the mobile node. Based on the information on the service type of the flow, a different prefix is assigned for each service type for each flow, and the assigned prefix information is matched with the mobile node information and AP information connected to the mobile node. Stored in a binding cache entry (BCE), a path is set for each flow based on information on a service type of the flow, and the flow of the mobile node is transmitted to a destination node according to the set path. At this time, the router access request message identifies information about the service type of the flow recorded by the mobile node, the first type for which session maintenance is unnecessary, the second type for which session maintenance of the flow is required, or the third type for which the IP of the flow is fixed. In the process of setting information and setting the path, when the handover of the mobile node occurs, the anchor of the mobile node is reset when the service type corresponds to the second type, and the service type is the first type and the first If the type is 3, the optimal route is recalculated.

According to any one of the above-described problem solving means of the present invention, it is possible to distinguish a plurality of flows serviced to each user terminal according to the type of service and to manage the mobility of the flows according to the service type. In particular, an anchor point can be dynamically set for a flow that needs to provide a real-time service, thereby minimizing an active link, thereby increasing network resource use efficiency and reducing handover delay.

1 is a view showing the configuration of an SDN controller according to an embodiment of the present invention.
2 is a flowchart illustrating a mobile node management method of an SDN controller according to an embodiment of the present invention.
3 is a flowchart illustrating a process in which a mobile node is registered according to an embodiment of the present invention.
4 is a flowchart illustrating a handover process of a mobile node according to an embodiment of the present invention.
5 is a view for explaining an anchor setting process according to an embodiment of the present invention.
6 is a diagram illustrating experimental data of a method of managing flow mobility for each service of an SDN controller according to an embodiment of the present invention.

Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings so that those skilled in the art to which the present invention pertains may easily practice. However, the present invention can be implemented in many different forms and is not limited to the embodiments described herein. In order to clearly describe the present invention, parts not related to the description are omitted in the drawings, and like reference numerals are given to similar parts throughout the specification. Also, with reference to the drawings, even in the case of a configuration indicated by the same name, the drawing number may vary depending on the drawing, and the drawing number is for convenience of description only, and the concept, feature, and function of each configuration are indicated by the corresponding drawing number. Or, the effect is not to be interpreted limitedly.

Throughout the specification, when a part is "connected" to another part, this includes not only "directly connected" but also "electrically connected" with another element in between. . Also, when a part is said to “include” a certain component, it means that the component may further include other components, not exclude other components, unless otherwise stated. It should be understood that features or numbers, steps, actions, components, parts or combinations thereof are not excluded in advance.

In the present specification, the term “unit” or “module” includes a unit realized by hardware or software, and a unit realized by both, and one unit is realized by using two or more hardware. It may be, or two or more units may be realized by one hardware.

1 is a view showing the configuration of an SDN controller according to an embodiment of the present invention.

First, the SDN controller is connected to OpenFlow-enabled switches and APs.

The SDN controller can manage the network more flexibly by distinguishing the service type of the flow used by the mobile node by interworking with the on-demand module application. The on-demand module application includes a management module, a routing module, and a binding cache entry (BCE) module.

First, when the mobile node accesses the SDN domain, the management module detects the connection of the mobile node (MN) and determines the mobile content. At this time, the management module detects the connection of the mobile node by using a router access request (RS) message, and when the mobile node is detected, transmits a message to the corresponding module according to mobility, and then advertises the router (Router Advertisement, RA) ) Message to inform the mobile node. The routing module selects a route according to information on a flow type using switch information located in a current route between a mobile node and a destination node. The BCE module stores the information of the mobile node and distinguishes the flow used in the mobile node.

The SDN controller 100 includes a communication module 110, a memory 120, a processor 130, and a database 140.

In detail, the communication module 110 provides a communication interface necessary to provide a transmission / reception signal between the SDN controller 100 and a user terminal, that is, a mobile node, in the form of packet data. Furthermore, the communication module 110 may perform a role of receiving a data request from the mobile node and transmitting data in response thereto.

Here, the communication module 110 may be a device including hardware and software necessary for transmitting and receiving a signal such as a control signal or a data signal through a wired or wireless connection with another network device.

In the memory 120, a program for performing a method in which the SDN controller manages flow mobility for each service is recorded. In addition, it performs a function of temporarily or permanently storing data processed by the processor 130. Here, the memory 120 may include volatile storage media or non-volatile storage media, but the scope of the present invention is not limited thereto.

The processor 130 controls the entire process in which the SDN controller provides a method of managing flow mobility for each service. Here, the processor 130 processes all kinds of devices capable of processing data, such as a processor. It can contain. Here, a 'processor' may mean a data processing device embedded in hardware having physically structured circuits, for example, to perform functions represented by codes or instructions included in a program. As an example of such a data processing device embedded in hardware, a microprocessor, a central processing unit (CPU), a processor core, a multiprocessor, and an application-specific integrated ASIC circuit, a field programmable gate array (FPGA), or the like, but the scope of the present invention is not limited thereto.

The database 140 stores data accumulated while the SDN controller manages flow mobility for each service.

For example, the database 140 may store a mobile node identifier, an identifier of an AP to which the mobile node is connected, information on a service type of each flow, and the like.

In one embodiment of the present invention, the flow is largely divided into three types, a first type that is a non-persistent service that does not require session maintenance of a flow, a real-time service that requires session maintenance of a flow and requires mobility. -lasting) is classified into the second type, and the third type of a fixed type in which the IP address should always be kept valid. The management module may allocate a first prefix for flows of the first and third types, and a second prefix for flows of the second type that cannot tolerate delays and require session continuity.

2 is a flowchart illustrating a mobile node management method of an SDN controller according to an embodiment of the present invention.

First, the SDN controller receives a router access request (RS) message of a mobile node delivered through the first AP operated by the SDN (S210).

In the RS message, as the information about the service type of the flow recorded by the mobile node, information identifying the first type that does not require session maintenance, the second type that requires session maintenance of the flow, or the third type in which the IP of the flow is fixed. On the other hand, in the general RS message, the code field is defined as '0000' in the form of a byte, but the message according to an embodiment of the present invention is changed by defining information about the flow type in the code field. For example, in the code field of the RS message, the first type is defined as Flow1 = 0001, the second type is Flow2 = 0002, and the third type is Flow3 = 0003, and the mobile node records information about the flow type.

Next, the SDN controller allocates a prefix to each flow based on information on the service type of the flow included in the RS message (S220). At this time, the SDN controller allocates a first prefix for the first type and the third type of flow, and a second prefix for the second type of flow.

Next, the SDN controller stores the prefix information allocated through step S220 in the BCE for each flow (S230). At this time, the identifier of the mobile node, the information of the AP connected to the mobile node and the prefix information of the flow are matched and stored. Then, the SDN controller transmits an RA message confirming that information on the flow type is registered to the mobile node through the first AP. At this time, the RA message is transmitted by defining the information about the flow type in the code field in the same way as the RS message.

Next, the SDN controller sets a path for each flow based on information on the service type of the flow (S240). The flow to which the second prefix is assigned is when the service type corresponds to the second type, and resets the anchor of the mobile node. In addition, the flow to which the first prefix is assigned is performed when the service type corresponds to the first type or the third type and recalculates the optimal route.

Next, the SDN controller transmits the flow transmitted from the mobile node to the destination node according to the path set in the previous step (S250).

3 is a flowchart illustrating a process of registering a mobile node according to an embodiment of the present invention, and FIG. 4 is a flowchart illustrating a handover process of a mobile node according to an embodiment of the present invention.

Referring to FIG. 3, an RS message transmitted from a mobile node (MN) to an AP includes information on a service type of each flow.

The management module of the SDN controller detects the connection of the mobile node through the RS message, and assigns a prefix based on the information on the service type of the flow included in the RS message. For example, a streaming video may be used while using a messenger function in a mobile node. In this case, the flow type for the messenger function may be a first type that does not require session maintenance, and the flow type for a streaming video may be a second type that requires session maintenance.

The BCE module stores the host identifier (HostID), the AP identifier (AP ID), the prefix (Prefix1, Prefix2), and information about the service type of the flow (Flow1, Flow2, Flow3) in the BCE.

The management module generates an RA message confirming that the information on the service type of the flow is registered in the SDN controller and transmits it to the mobile node.

The path setting module sets the path of each flow according to the service type of the flow, but resets the anchor of the mobile node when the service type of the flow corresponds to the second type when the handover of the mobile node occurs, and the service type of the flow is removed. The optimal path is recalculated if the type 1 or type 3 is applicable.

The SDN controller transmits the flow transmitted from the mobile node to the destination node according to the path set in the routing module.

Referring to FIG. 4, when the SDN controller receives an RS message transmitted from the mobile node through the second AP, a prefix is assigned to each flow based on information on a service type of the flow included in the RS message. The subsequent procedure is the same as that described in FIG. 3 above. In particular, when a handover occurs, the anchor is reset when the service type of the flow corresponds to the second type.

5 is a view for explaining an anchor setting process according to an embodiment of the present invention.

In the present invention, whether to reset the anchor is determined according to the service type of the flow. That is, when a real-time service is required, in order to maintain the session, the switch located at the closest distance from the location where the mobile node is moved among the switches included in the existing path set between the mobile node and the destination node is reset to an anchor.

FIG. 6 is a diagram illustrating experimental data of a method of managing flow mobility for each service of an SDN controller according to an embodiment of the present invention.

In the case of a typical mobile node, considering 2016 statistical data that video traffic occupies 60% of the total mobile data traffic, it is assumed that half of the flows activated on the mobile device are real-time service types. As a result of performing the experiment under these assumptions, it can be confirmed that the handover delay in the case of applying the present invention has been reduced by 50% compared to the prior art, and the real-time service can be processed faster than the mobility of the existing SDN-based environment. there was.

The method of managing flow mobility for each service of the SDN controller according to the embodiment of the present invention described above may be implemented in the form of a recording medium including instructions executable by a computer, such as a program module executed by a computer. Can be. Such recording media include computer readable media, which can be any available media that can be accessed by a computer and includes both volatile and nonvolatile media, removable and non-removable media. In addition, computer readable media includes computer storage media, which are volatile and nonvolatile implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. , Removable and non-removable media.

The above description of the present invention is for illustration only, and a person who is investigating ordinary knowledge in the technical field to which the present invention pertains can understand that it can be easily modified to other specific forms without changing the technical spirit or essential features of the present invention. will be. Therefore, it should be understood that the embodiments described above are illustrative in all respects and not restrictive. For example, each component described as a single type may be implemented in a distributed manner, and similarly, components described as distributed may be implemented in a combined form.

Further, although the methods and systems of the present invention have been described in connection with specific embodiments, some or all of their components or operations may be implemented using a computer system having a general purpose hardware architecture.

The scope of the present invention is indicated by the following claims rather than the detailed description, and all changes or modifications derived from the meaning and scope of the claims and their equivalent concepts should be interpreted to be included in the scope of the present invention. .

100: SDN controller 110: communication module
120: memory 130: processor

Claims (8)

In the method of managing the mobility of the flow for each service of the SDN (Software-Defined Networking) controller,
Receiving, by the SDN controller, a Router Solicitation message of a mobile node delivered through a first AP;
Assigning, by the mobile node, a different prefix for each service type for each flow based on information on the service type of the flow included in the router access request message;
Matching the assigned prefix information with the mobile node information and AP information connected to the mobile node and storing the information in a binding cache entry (BCE);
Establishing a path for each flow based on information on the service type of the flow, and
And transmitting a flow of the mobile node to a destination node according to the established path,
The router access request message is information about the service type of the flow recorded by the mobile node, and information identifying the first type that does not require session maintenance, the second type that requires session maintenance of the flow, or the third type where the IP of the flow is fixed. Is recorded,
The step of setting the path resets the anchor of the mobile node when the service type corresponds to the second type when the handover of the mobile node occurs, and the service type corresponds to the first type or the third type If the path is to recalculate the method of managing the mobility of the flow for each service of the SDN controller. According to claim 1,
Receiving a router access request message of a mobile node delivered through a second AP operated by the SDN controller according to the movement of the mobile node;
Assigning a different prefix for each flow for each flow based on information on the service type of the flow included in the router access request message by the mobile node;
Matching the assigned prefix information to the mobile node information and AP information connected to the mobile node and storing the information in the BCE;
Establishing a path for each flow based on information on the service type of the flow, and
And transmitting a flow of the mobile node to a destination node according to the established path,
The step of establishing the route resets the anchor of the mobile node when the service type corresponds to the second type when the handover of the mobile node occurs, and the service type corresponds to the first type or the third type If the path is to recalculate how to manage the mobility of the flow for each service of the SDN controller. According to claim 1,
And transmitting a router advertisement message indicating that information on the service type of the flow is registered to the mobile node through the first AP. According to claim 1,
The step of establishing the route is based on the flow of each service of the SDN controller that resets the switch located at the closest distance from the position where the mobile node moves among the switches included in the existing route set between the mobile node and the destination node to the anchor. How to manage mobility. In the SDN (Software-Defined Networking) controller for managing the mobility of the flow for each service,
Memory for storing programs for managing flow mobility for each service and
And a processor for executing the program stored in the memory,
The processor receives, by the execution of the program, a Router Solicitation message of a mobile node transmitted through the first AP, and the service type of the flow included in the router access request message by the mobile node. A different prefix is assigned for each service type for each flow based on the information on the flow, and the assigned prefix information is matched with the mobile node information and AP information connected to the mobile node to bind the BCE (Binding cache entry) ), And set a path for each flow based on information on the service type of the flow, and transmit the flow of the mobile node to the destination node according to the set path,
The router access request message is information about the service type of the flow recorded by the mobile node, which identifies the first type that does not require session maintenance, the second type that requires session maintenance of the flow, or the third type where the IP of the flow is fixed. Is recorded,
In the process of establishing the route, when the handover of the mobile node occurs, the anchor of the mobile node is reset when the service type corresponds to the second type, and the service type corresponds to the first type or the third type. SDN controller which is to recalculate the case. The method of claim 5,
The processor receives the router access request message of the mobile node delivered through the second AP operated by the SDN controller according to the movement of the mobile node, and the service of the flow included in the router access request message by the mobile node Based on the information on the type, a different prefix is assigned for each service type for each flow, the assigned prefix information is matched with the mobile node information and AP information connected to the mobile node, and stored in the BCE. Set a path for each flow based on information on the service type of the flow, and transmit the flow of the mobile node to the destination node according to the set path,
In the process of establishing the route, when the handover of the mobile node occurs, the anchor of the mobile node is reset when the service type corresponds to the second type, and the service type corresponds to the first type or the third type. SDN controller which is to recalculate the case. The method of claim 5,
The processor is an SDN controller that transmits a Router Advertisement message indicating that information on a service type of a flow is registered to the mobile node through the first AP. The method of claim 5,
In the process of establishing a route, the SDN controller resets a switch located at a distance closest to a position moved by the mobile node among switches included in an existing route set between the mobile node and a destination node.

Images