KR101679224B1 - Network system based on sdn capable traffice distribution - Google Patents

Abstract

The present invention relates to a network system based on SDN (Software Defined Network) and capable of selectively distributing traffic to guarantee service quality, and the network system can efficiently use the network for each service, The satisfaction of the user experience can be increased.

Description

[0001] NETWORK SYSTEM BASED ON SDN CAPABLE TRAFFICE DISTRIBUTION [0002]

The present invention relates to a network system based on SDN (Software Defined Network) and capable of selectively distributing traffic to guarantee service quality, and the network system can efficiently use the network for each service, The satisfaction of the user experience can be increased.

In order to distribute the traffic to the selected 2 or more networks, the IP of the device may be based. In this case, since the classification is performed based on the IP of the device, the approximate network status . In the case of users receiving various services through mobile, it is difficult to obtain the effect of traffic distribution. In case of real-time service such as VoIP, quality assurance becomes a very important factor. Therefore, these factors must be considered in order to obtain the effect of actual traffic distribution.

1. OpenFlow Switch Specification version 1.4.0 (Wire Protocol 0x05), October 14, 2013 [https://www.opennetworking.org/images/stories/downloads/sdn-resources/onf-specifications/openflow/openflow-spec- v1.4.0.pdf] 2. Software-Defined Networking: The New Norm for Netwrks, ONF White Paper, April 13, 2012 [https://www.opennetworking.org/images/stories/downloads/sdn-resources/white-papers/wp-sdn- newnorm.pdf] 3. ETSI GS NFV 002 v1.1.1 (2013-10) [http://www.etsi.org/deliver/etsi_gs/NFV/001_099/002/01.01.01_60/gs_NFV002v010101p.pdf]

It is an object of the present invention to provide a network system capable of distributing traffic that can guarantee quality by service using SDN. The present invention also provides a service chaining method capable of minimizing the size of a table required for service chaining. In addition, the service chain rule is applied and managed to each service chain list (NF list: NFv list), rather than applying the service chain rule for each individual user, so that the service chaining rule functions more easily and efficiently.

A network system according to the present invention includes: a wireless access network connected to a mobile terminal; A core network based on SDN (Software Defined Network) for transmitting traffic of the radio access network to one of first and second networks; And a control unit for receiving traffic from the core network, extracting service information including at least a service type from the received traffic information, and transmitting, based on traffic distribution data including the extracted service information, Based controller for traffic control to transmit the traffic to either one of the first network and the second network.

In addition, the extracted service information may include a QoS policy. In addition, the controller receives traffic statistical information between the core network and the first and second networks from the core network, and the traffic distribution data may further include the received traffic statistical information.

The wireless access network transmits terminal information including a user IP and a TEID of the connected mobile terminal to the controller when the mobile terminal accesses the terminal, and the controller transmits the terminal information received from the wireless access network to the controller And the traffic distribution data may include the transmitted terminal information. In addition, when the mobile access terminal terminates the wireless access network, the controller transmits information of the terminated mobile terminal to the controller. When the controller receives the terminated terminal information, the controller transmits the terminated terminal information to the terminal information DB Can be deleted.

The controller deletes the associated entry from the entry DB if there is an entry related to the revoked mobile terminal and transmits a message to the core network to delete the entry related to the revoked mobile terminal from the entry table of the core network. Lt; / RTI >

Also, the first network may be a mobile network, the second network may be an IP network, and the core network may have a function of removing or changing GTP headers of traffic, or adding GTP headers to the traffic. The service type may be extracted based on at least one of an external destination IP address of the GTP header of the traffic and a destination IP address of the mobile terminal packet. In addition, when the core network receives an instruction to transmit traffic of the mobile terminal from the controller to the second network, the core network removes the GTP header of the mobile terminal traffic and transmits the removed mobile terminal traffic to the second Network. The core network may transmit a second network traffic to which the GTP header is added to the wireless access network by adding a GTP header to the second network traffic when traffic is received from the second network.

The addition of the GTP header may include adding an entry corresponding to the flow information of the second network traffic of the entry table of the core network in the core network by executing an instruction and receiving the second network traffic from the core network And an addition in the core network by an instruction message indicating that the controller adds the GTP header from the information of the second network traffic to the core network.

According to the present invention, traffic classification and quality assurance can be performed for each service, thereby improving the user's satisfaction. High efficiency per service can be used in the network, which can increase resource utilization of the entire network. In addition, by monitoring the traffic, it is possible to monitor the usage pattern of the traffic, the possibility of interworking with the big data, and the connection with the billing system.

1 is a block diagram of an SDN network system according to an embodiment of the present invention;
2 is a block diagram of a controller of the network system of FIG. 1;
FIG. 3 is a block diagram of a switch of the network system of FIG. 1,
4 is an operation table showing a field table of a flow entry and an operation type according to a flow entry,
5 shows the field table of the group and meter tables,
6 is a block diagram of a mobile network system according to an embodiment of the present invention.
7 is a block diagram of a controller according to another embodiment of the present invention, and Fig.
8 to 10 are signal flow diagrams in the mobile network system of Fig.

Hereinafter, the present invention will be described in more detail with reference to the drawings.

The terms first, second, etc. may be used to describe various components, but the components should not be limited by the terms. The terms are used only for the purpose of distinguishing one component from another. For example, without departing from the scope of the present invention, the first component may be referred to as a second component, and similarly, the second component may also be referred to as a first component. And / or < / RTI > includes any combination of a plurality of related listed items or any of a plurality of related listed items.

It is to be understood that when an element is referred to as being "connected" or "connected" to another element, it may be directly connected or connected to the other element, . On the other hand, when an element is referred to as being "directly connected" or "directly connected" to another element, it should be understood that there are no other elements in between. Also, the fact that the first component and the second component on the network are connected or connected means that data can be exchanged between the first component and the second component by wire or wirelessly.

In addition, suffixes "module" and " part "for the components used in the following description are given merely for convenience of description, and do not give special significance or role in themselves. Accordingly, the terms "module" and "part" may be used interchangeably.

When such components are implemented in practical applications, two or more components may be combined into one component, or one component may be divided into two or more components as necessary. The same or similar elements are given the same throughout the drawings, and the detailed description of the elements having the same reference numerals can be omitted and replaced with the description of the above-described elements.

FIG. 1 is a block diagram of an SDN network system according to an embodiment of the present invention. FIG. 2 is a block diagram of a controller of the network system of FIG. 1. FIG. 3 is a block diagram of a switch of a network system of FIG. 4 is an operation table showing a field table of a flow entry and an operation type according to a flow entry, and Fig. 5 is a field table of a group and a meter table.

Referring to FIG. 1, an SDN network system according to an embodiment of the present invention may include a controller 10, a plurality of switches 20, and a plurality of network devices 30.

The network device 30 may include a user terminal device for exchanging data or information, or a physical device or a virtual device for performing a specific function. From a hardware standpoint, the network device 30 may be a PC, a client terminal, a server, a workstation, a supercomputer, a mobile communication terminal, a smart phone, a smart pad, or the like. The network device 30 may also be a virtual machine (VM) created on a physical device.

The network device 30 may be referred to as a network function that performs functions on various networks. Network features include anti-DDoS, intrusion detection / blocking (IDS / IPS), integrated security services, virtual private network services, anti-virus, anti-spam, security services, access management services, firewalls, load balancing, . ≪ / RTI > These network functions can be virtualized.

There is a network function virtualization (NFV) defined in a white paper on NFV issued by the European Telecommunications Standards Institute (ETSI) (see non-patent reference 3) as a virtualized network function. The network function (NF) may be used herein in combination with network function virtualization (NFV). NFV provides necessary network functions by dynamically generating necessary L4-7 service connection for each tenant, and provides firewall, IPS and DPI functions necessary for policy-based DDoS attacks quickly through a series of service chaining . NFVs can also easily turn on and off firewalls or IDS / IPS and provision them automatically. NFV can also reduce the need for overprovisioning.

A controller 10 is a kind of command computer that controls the SDN system and can perform various complex functions such as routing, policy declaration, and security check. The controller 10 can define the flow of packets occurring in the plurality of switches 20 in the lower layer. The controller 10 may calculate a path (data path) to be flowed by referring to a network topology or the like with respect to a flow allowed in the network policy, and then set an entry of the flow on a switch on the path. The controller 10 may communicate with the switch 20 using a specific protocol, e.g., an open flow protocol. The communication channel between the controller 10 and the switch 20 can be encrypted by SSL.

2, the controller 10 may include a switch communication unit 110, a control unit 100, and a storage unit 190, which communicate with the switch 20.

The storage unit 190 may store a program for processing and controlling the control unit 100. [ The storage unit 190 may perform a function for temporarily storing input or output data (packet, message, etc.). The storage unit 190 may include an entry database (DB) 191 for storing flow entries.

The controller 100 may control the overall operation of the controller 10 by controlling the operations of the respective units. The control unit 100 may include a topology management module 120, a path calculation module 125, an entry management module 135, and a message management module 130. Each module may be configured in hardware in the control unit 100 and may be configured in software separate from the control unit 100. [

The topology management module 120 can construct and manage network topology information based on the connection relationship of the switches 20 collected through the switch communication unit 110. [ The network topology information may include a topology between the switches and a network device topology connected to each switch.

The path calculation module 125 can obtain the data path of the packet received through the switch communication unit 110 and the action column to be executed by the switch on the data path based on the network topology information established in the topology management module 120 .

The entry management module 135 registers the entry in the entry DB 191 as an entry such as a flow table, a group table, and a meter table based on the result calculated by the route calculation module 125, a policy such as QoS, . The entry management module 135 may proactively register an entry in each table in the switch 20 and react to an addition or update request of an entry from the switch 20. [ The entry management module 135 may change or delete entries in the entry DB 191 as needed or in accordance with an entry disappearance message of the switch 10. [

The message management module 130 may interpret a message received through the switch communication unit 110 or may generate a controller-switch message to be transmitted to the switch through the switch communication unit 110, which will be described later. The status change message, which is one of the controller-switch messages, may be generated based on the entry according to the entry management module 135 or the entry stored in the entry DB 191. [

The switch 20 may be a physical switch or a virtual switch supporting an open flow protocol. The switch 20 can process the received packet and relay the flow between the network devices 30. [ To this end, the switch 20 may comprise a single flow table or a multiple flow table for pipeline processing as described in non-patent document 1. [

The flow table may include a flow entry defining rules for how to handle the flow of network device 30. [

A flow may refer to a packet flow of a particular path according to a series of packets sharing a value of at least one header field from a single switch or a combination of multiple flow entries of multiple switches. The open-flow network can perform path control, fault recovery, load balancing and optimization on a flow-by-flow basis.

The switch 20 can be divided into a core switch between an ingress and egress edge switch and an edge switch between a flow according to the combination of multiple switches.

3, the switch 20 includes a port portion 205 for communicating with other switches and / or network devices, a controller communication portion 210 for communicating with the controller 10, a switch control portion 200, and a storage portion 290).

The port unit 205 may include a plurality of pairs of ports that are flown out from a switch or a network device. A pair of ports can be implemented as one port.

The storage unit 290 may store a program for processing and controlling the switch control unit 210. [ The storage unit 290 may perform a function for temporarily storing input or output data (packets, messages, etc.). The storage unit 290 may include a table 291 such as a flow table, a group table, and a meter table. Entries in the table 230 or table may be added, modified, or deleted by the controller 10. The table entry can be destroyed by itself.

The flow table can be composed of multiple flow tables to handle the pipeline of open flows. 4, a flow entry of a flow table includes match fields describing conditions (matching rules) to match a packet, a priority, counters to be updated when there are packets to be matched, An instruction that is a set of various actions that occurs when there is a packet matched to a flow entry, timeouts that describe the time to be discarded in the switch, and an opaque type that is selected by the controller. Can be used to filter flow statistics, flow changes, and flow deletions, and can include tuples such as cookies that are not used in packet processing. An instruction may change pipeline processing such as forwarding a packet to another flow table. The instructions may also include a collection of actions to add an action to an action set, or a list of actions to apply directly to a packet. An action is an operation that modifies a packet, such as sending a packet to a specific port or decreasing the TTL field. The action may be part of an instruction set associated with the flow entry or belonging to an action bucket associated with the group entry. An action set is an aggregated set of actions indicated in each table. An action set can be performed when no table is matched. 5 illustrates various packet processing by a flow entry.

A pipeline is a sequence of packets between a packet and a flow table. When a packet is input to the switch 20, the switch 20 searches for a flow entry matching the packet in the order of higher priority of the first flow table. When the matching is performed, the instruction of the entry is executed. An instruction may be an apply-action that is immediately matched, a command to clear or add / modify an action set, a write-action, a write-metadata command, And a goto-table that moves packets along with metadata to a table. If there is no flow entry matched with the packet, the packet may be dropped according to the table setting, or the packet may be sent to the controller 10 in a packet-in message.

The group table may include group entries. The group table may be indicated by a flow entry to suggest additional forwarding methods. Referring to FIG. 6, the group entry of the group table may include the following fields. A group identifier for identifying a group entry, a group type for specifying a rule for performing a select or all action buckets defined in the group entry, a counter for a flow entry , And action buckets, which are a set of actions associated with the parameters defined for the group.

The meter table is made up of meter entries and defines per-flow meters. The flow meter-party can allow open flows to be applied to various QoS operations. A meter is a kind of switch element that can measure and control the rate of packets. Referring to FIG. 7, a meter table includes a meter identifier identifying the meter, a rate specified in the band and meter bands indicating how the packet is to be operated, And counters fields that are updated when they become available. Meter bands include a band type indicating how the packet is to be processed, a rate used to select the meter band by the meter, counters that are updated when the packets are processed by the meter band, ), And a type specific argument, which is a bad type with optional arguments.

The switch control unit 210 can control the overall operation of the switch 200 by controlling the operations of the respective units. The control unit 210 may include a table management module 240 that manages the table 291, a flow search module 220, a flow processing module 230, and a packet processing module 235. Each module may be configured in hardware in the control unit 110 and may be configured in software separate from the control unit 110. [

The table management module 240 may add the entry received from the controller 10 to the appropriate table through the controller communication unit 210 or periodically remove the time-out entry.

The flow search module 220 may extract flow information from the received packet as user traffic. The flow information includes identification information of an ingress port as a packet inflow port of the edge switch, identification information of an incoming port of the switch of the switch, packet header information (IP address of the source and destination, MAC address, port, And VLAN information, etc.), metadata, and the like. The metadata may be optionally added in the previous table or may be data added in another switch. The flow search module 220 can search the table 291 for a flow entry for a received packet by referring to the extracted flow information. The flow search module 220 may request the flow processing module 260 to process the received packet according to the retrieved flow entry, if a flow entry is found. If the flow entry search fails, the flow search module 220 may transmit the minimum data of the received packet or the received packet to the controller 100 through the controller communication unit 210.

The flow processing module 230 may process an action, such as outputting a packet to a specific port or multiple ports, dropping it, or modifying a specific header field, in accordance with the procedure described in the entry retrieved from the flow search module 220 have.

The flow processing module 230 may execute an action set to execute a pipeline process of a flow entry, execute an instruction to change an action, or execute a set of actions when it is no longer possible to go to the next table in a multi-flow table.

The packet processing module 235 can actually output the processed packet by the flow processing module 230 to one or more ports of the port unit 205 specified by the flow processing module 230. [

Although not shown in FIG. 1, the SDN network system may further include an orchestrator for creating, changing, and deleting virtual network devices, virtual switches, and the like. When an orchestrator creates a virtual network device, the orchestrator generates a virtual network device such as a network device, such as identification information of a switch to be connected to the virtual network, port identification information connected to the switch, MAC address, IP address, tenant identification information, To the controller (10).

The controller 10 and the switch 20 exchange various information, which is called an open flow protocol message. Such an open flow message may be of a type such as a controller-to-switch message, an asynchronous message, and a symmetric message. Each message may have a transaction identifier (transaction id; xid) in the header that identifies the entry.

The controller-switch message is a message generated by the controller 10 and transmitted to the switch 20, which is mainly used for managing or checking the state of the switch 20. [ The controller-switch message may be generated by the controller 100 of the controller 10, and in particular by the message management module 130.

The controller-switch message includes features inquiring about the capabilities of the switch, configuration for inquiring and setting the settings of the configuration parameters of the switch 20, flow / group / meter of the open flow table, A modify state message for adding / deleting / modifying entries, a packet-out message for transmitting a packet received from the switch through a packet-in message to a specific port on the switch, and the like . The state change message includes a modify flow table message, a modify flow entry message, a modify group entry message, a prot modification message, and a meter entry change message. Message (meter modification message).

The asynchronous message is a message generated by the switch 20, and is used to update the state of the switch, the network event, and the like in the controller 10. The asynchronous message may be generated by the control unit 200 of the switch 20, in particular by the flow search module 220.

Asynchronous messages include packet-in messages, flow-removed messages, and error messages. The packet-in message is used by the switch 20 to send a packet to the controller 10 to receive control of the packet. The packet-in message includes all or part of the received packet, or a copy thereof, sent from the open flow switch 20 to the controller 10 to request the data path when the switch 20 receives an unknown packet Message. A packet-in message is used even when the action of the entry associated with the incoming packet is determined to be sent to the controller. The deleted flow-removed message is used to forward the flow entry information to the controller 10 to be deleted from the flow table. This message occurs when the controller 10 requests the switch 20 to delete the corresponding flow entry or in a flow expiry process by a flow timeout.

The symmetric message is generated in both the controller 10 and the switch 20, and is transmitted even when there is no request from the other party. A hello used to initiate the connection between the controller and the switch, an echo to confirm that there is no abnormality in the connection between the controller and the switch, and an error message used by the controller or switch to inform the other side of the problem an error message, and the like. The error message is mostly used in the switch to indicate a failure in response to a request initiated by the controller.

FIG. 6 is a block diagram of a mobile network system according to an embodiment of the present invention. FIG. 7 is a block diagram of a controller according to another embodiment of the present invention. FIGS. 8 to 10 are diagrams Fig. Please refer to Figs. 1 to 5.

Referring to FIG. 6, the mobile network system may include a mobile terminal 30, a wireless access network, a core network based on a SDN (Software Defined Network), and an SDN-based controller 10. Reference is made to Figs. 1 to 5 for a detailed description of the same or similar components.

The mobile terminal 30 may correspond to the network device of Fig. However, in terms of a mobile communication network, the mobile terminal 30 is preferably a mobile communication terminal or a smart phone, a PC, a notebook, or a smart pad equipped with a mobile communication module or a wireless communication module.

The radio access network may be the base station 40 itself or may further include other base stations and / or network elements such as base station controllers, radio network controllers, relay nodes, and the like. The base station 40 may be configured to transmit and receive wireless signals within a specific area referred to as a cell. The cell may be subdivided into a plurality of cell sectors.

The mobile network system may be a multiple access system and may employ one or more channel approaches such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and the like. For example, the base station 40 and the mobile terminal 30 in the wireless access network may use a wireless technology such as Universal Mobile Telecommunications System (UMTS) terrestrial radio access (UTRA) to establish a wireless interface using wideband CDMA (WCDMA) Can be implemented. WCDMA may include communications protocols such as High Speed Packet Access (HSPA) or Evolved HSPA (HSPA +). The HSPA may include high speed downlink packet access (HSDPA) or high speed uplink packet access (HSUPA). In another embodiment, the base station 40 and the mobile terminal 30 may use an evolutionary UMTS terrestrial radio access (E-UTRA) system that establishes a wireless interface using Long Term Evolution (LTE) and / or LTE- ). ≪ / RTI >

In other embodiments, the base station 40 and the mobile terminal 30 may communicate with each other using IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, (GSM), Enhanced Data Rates for GSM Evolution (EDGE), GSM EDGE (GERAN), and the like. .

The base station 40 may be a wireless router, a home Node B, a home eNode B, or an access point and may use any suitable wireless access network that enables wireless connectivity in a local area such as a business premises, home, automobile, campus, have. In one embodiment, the base station 40 and the mobile terminal 30 may implement a wireless technology such as IEEE 802.11 to establish a wireless local area network (WLAN). In another embodiment, the base station 40 and the mobile terminal 30 may implement a wireless technology such as IEEE 802.15 to establish a wireless personal communication network (WPAN). In another embodiment, the base station 40 and the mobile terminal 30 establish a picocell or femtocell using a cellular based wireless access network (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, can do.

The base station 40 may mount an SDN agent. The base station 40 can communicate with the controller 10 or the open flow switch 20 of the core network in the open flow protocol. The base station 40 may have the functions or components of the switches of Figs. 1 and 3, or may have additional functions or elements.

The base station 40 may transmit the terminal information to the controller 10 when the mobile terminal 30 accesses or detaches the wireless access network. The terminal information may include a user IP address, and a tunnel ID (TEID).

The wireless access network communicates with a core network and the core network provides voice over data, applications, and / or voice over internet protocol (VoIP) services to one or more mobile terminals 30 Lt; / RTI > may be any type of network configured. For example, the core network can provide call control, billing services, mobile location-based services, prepaid calling, internet access, image distribution, and can perform advanced security functions such as user authentication. Although not shown in FIG. 6, the radio access network can directly or indirectly communicate with another radio access network using the same radio access network or another radio access network as the radio access network or the core network. For example, in addition to being connected to a wireless access network using E-UTRA wireless technology, the core network may also communicate with other wireless access networks (not shown) using GSM wireless technology.

The core network may function as a gateway for the mobile terminal 30 to connect to the PSTN, the Internet and other networks. The PSTN may include a circuit switched telephone network providing a plain old telephone service (POTS). Other networks may include wired or wireless communication networks owned or operated by other service providers. Other networks may include other core networks connected to other radio access networks.

In this embodiment, the core network may include an open flow switch 20 that satisfies the SDN-based open flow protocol. For details of the open flow switch 20, refer to FIG. 1 or FIG. It is assumed that the network connected to the core network is a mobile network and an IP network.

When the wireless access network uses an LTE system including an Evolved Universal Terrestrial Radio Access Network (EUTRAN), the open flow switch 20 can be switched between the serving gateway S-GW and the packet data network PDN gateway P- Or at least some of the functions of each gateway. The open flow switch 20 may be composed of two switches, serving gateway and PDN gateway functions. The base station 40 may be named eNode B (eNB) in the LTE system. Hereinafter, it is assumed that the wireless access network uses the LTE system. The switch 20 and the base station can transmit and receive packets through the GTP tunnel.

The port portion 205 of the open flow switch 20 may include a radio access network (base station 40), a mobile network, and a plurality of ports for transmitting and receiving packets with the IP network.

The controller 10 communicates with the SDN-based or SDN agent-mounted component and can control the component. In this embodiment, the controller 10 can communicate with the base station 40 of the radio access network and the open flow switch 20 of the core network in an open flow protocol. Although the communication between the base station 40 and the controller 10 is directly shown, it is not limited thereto. For example, the base station 40 and the controller 10 can communicate via the open flow switch 20. Referring to FIG. 7, the controller 10 may include a communication unit 110, a control unit 100, and a storage unit 190. The controller 10 according to the present embodiment may have or additionally have the functions or components of the controllers of Figs. The detailed description of the related functions or elements will be replaced with the contents of FIG. 1 and FIG.

The controller 100 of the controller 10 constructs topology information of a plurality of radio access networks, a plurality of core networks, and a plurality of mobile terminals, calculates a data path of a packet based on the constructed network topology information, It is possible to control the packet to move along the calculated data path to the radio access network or the core network on the path.

The communication unit 110 of the controller 10 can transmit and receive a packet to and from the base station 40 and the open flow switch 20 through a channel according to the open flow protocol.

The storage unit 190 of the controller 10 may include an entry DB 191, a terminal information DB 193, a service information DB 195, and a monitoring DB 197.

The control unit 100 can store and manage the terminal information received from the base station 40 through the terminal information DB 193 as a DB. The control unit 100 can store and manage service information such as policies such as the types of services such as web, game, FTP, and VoIP, and QoS for each service through the service information DB 195. The service type can be extracted using a destination IP address of a mobile terminal packet or an external destination address of a GTP header. A QoS policy may be designated to favor a mobile network in the case of a service in which real-time property is important, such as VoIP, and an IP network in the case of a non-real-time bandwidth-sensitive service such as FTP. The control unit 100 can store and manage the information of the flow table for each service of the mobile terminal 30 in the DB through the entry DB 191. [ The control unit 100 stores statistical information of traffic flowing in and out of the mobile network connected to the open flow switch 20 monitored by the switch 20 and the IP network port through the monitoring DB 197 And traffic statistics information can be easily linked with a user-specific billing system.

8-10, when the mobile terminal 30 is connected to the base station 40 (S410), the base station 40 can transmit the terminal information to the controller 10 (S415). The terminal information may be transmitted from the base station 40 to the controller 10 via the open flow switch 20. [ The terminal information may include a user IP address and a tunnel ID (TEID).

The controller 10 can update or update the terminal information DB 193 using terminal information received from the base station 40 (S420).

After transmitting the packet generated by the mobile terminal 30 to the base station 40, the base station 40 constructs the GTP header, adds the GTP header to the received user packet, and transmits the packet to the open flow switch 20 through the GTP tunnel (S425). The GTP header may include at least an S1 GTP header among the S1 GTP header and the S5 GTP header. The GTP header may include an external source and a destination IP address. The base station 40 may set the external destination IP address of the GTP header to be the same as the destination IP address of the mobile terminal packet or set the IP address of the open flow switch 20.

The open flow switch 20 can extract the flow information of the GTP packet added with the GTP header received from the base station 40 and search the flow table for a flow entry matching the flow information. If there is no flow entry matching the search result, the open flow switch 20 may encapsulate the GTP-packet into a packet-in message and send it to the controller 10 (S430).

The controller 10 can extract service information such as a service type and a QoS policy from the GTP-packet included in the received packet-in message. The controller 10 can extract the service type using at least one of the user IP address of the GTP-packet, the external IP address of the GTP header, and the destination IP address of the mobile terminal packet. The controller 10 uses at least one of service information including the extracted service type, QoS policy of the corresponding service, terminal information or user information associated with the corresponding GTP-packet, and traffic statistics information of the monitoring DB 197 The network to which the GTP-packet is to be transmitted may be determined (S435). The terminal information or the user information can be extracted through the tunnel ID. Such traffic distribution can be performed for each type of service, thereby dynamically ensuring the quality of each service and improving the user experience.

When the controller 10 makes the traffic distribution decision, it can update the entry DB 191 so that the traffic is transmitted to the determined network. The controller 10 may transmit a packet-out message to the open flow switch 20 so that the open flow switch 20 transmits the traffic to the determined network based on the updated entry DB (S440). In addition, a flow change message (flow-mode msg.) May be transmitted so that the flow table of the open flow switch 20 is changed (S440).

The open flow switch 20 may transmit the GTP-packet to either the mobile or the IP network based on the packet-out message or the flow table.

If the GTP-packet is directed to the mobile network, the open flow switch 20 may transmit the GTP-packet to the mobile network and receive response traffic (downstream packet) corresponding to the service request from the mobile network ). The open flow switch 20 can transmit the received response traffic to the mobile terminal 30 (S450). The open flow switch 20 does not need to decapsulate (remove) the GTP header, thereby improving the processing speed and reducing resource consumption such as operation processing or memory.

When the GTP-packet is designated to be directed to the IP network, the open flow switch 20 removes the GTP header of the corresponding traffic (S460), and transmits the GTP header-removed mobile terminal packet to the IP network (S465). The open flow switch 20 may receive acknowledgment (ACK) or response traffic (downlink packet) for the service request traffic of the mobile terminal from the IP network (S470). Upon receiving the downlink packet, the open flow switch 20 constructs a GTP header, adds a GTP header to the received downlink packet (S475), and transmits the GTP-down packet to which the GTP header is added to the base station 40 (S480).

When the mobile terminal 30 disconnects from the base station 40 in step S510, the base station 40 may transmit the terminal information of the mobile terminal 30 to the controller 10 in step S515.

Upon receipt of the release terminal information, the controller 10 can search the entry DB 191 for an entry associated with the terminal information. If there is an associated entry, the controller 10 may delete the entry in the entry DB 191. The controller 10 may transmit a flow change message (flow-Mod msg.) To the open flow switch 20 so that the corresponding entry is deleted from the flow table of the open flow switch 20 (S525). The controller 10 can delete the corresponding terminal information from the terminal information DB 193 (S530).

The present invention can be implemented in hardware or software. The present invention can also be embodied as computer readable code on a computer readable recording medium. A computer-readable recording medium includes all kinds of recording apparatuses in which data that can be read by a computer system is stored. Examples of the computer-readable recording medium include a ROM, a RAM, a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, and the like, and may be implemented in the form of a carrier wave (for example, transmission via the Internet) . The computer readable recording medium may also be distributed over a networked computer system so that computer readable code can be stored and executed in a distributed manner. And functional programs, codes, and code segments for implementing the present invention can be easily inferred by programmers skilled in the art to which the present invention pertains.

Embodiments of the present invention may include a carrier wave having electronically readable control signals, which may be operated with a programmable computer system in which one of the methods described herein is implemented. Embodiments of the present invention may be implemented as a computer program product having program code, wherein the program code is operated to execute one of the methods when the computer program is run on a computer. The program code may be stored on, for example, a machine readable carrier. One embodiment of the invention may be a computer program having program code for executing one of the methods described herein when the computer program is run on a computer. The present invention may include a computer, or programmable logic device, for performing one of the methods described above. A programmable logic device (e.g., a field programmable gate array, a complementary metal oxide semiconductor based logic circuit) may be used to perform some or all of the functions described above.

While the present invention has been particularly shown and described with reference to exemplary embodiments thereof, it is to be understood that the invention is not limited to the disclosed exemplary embodiments, but, on the contrary, It will be understood by those skilled in the art that various changes and modifications may be made by those skilled in the art without departing from the spirit and scope of the present invention.

10: controller 20: SDN switch
30: mobile terminal 40: base station
100: control unit 110: switch communication unit
190: storage unit 200:
205: port unit 210: controller communication unit
290:

Claims (11)

A wireless access network connected to a mobile terminal;
A core network based on SDN (Software Defined Network) for transmitting traffic of the radio access network to one of first and second networks; And
The method comprising the steps of: receiving traffic from the core network, extracting service information including at least a service type from information of the received traffic, determining, based on traffic distribution data including the extracted service information, And an SDN-based controller for traffic control to transmit the traffic to either the first network or the second network,
The first network is a mobile network, the second network is an IP network,
The core network has a function of removing or changing the GTP header of the traffic or adding a GTP header to the traffic,
Wherein the core network removes the GTP header of the mobile terminal traffic and transmits the removed mobile terminal traffic to the second network when the controller is instructed to transmit traffic of the mobile terminal to the second network Lt; / RTI &
The GTP header addition may include:
An addition by an instruction execution of an entry corresponding to the flow information of the second network traffic of the entry table of the core network in the core network,
Which is one of the additions in the core network by an instruction message instructing the core network to add the GTP header from the information of the second network traffic, system. The method according to claim 1,
Wherein the extracted service information comprises a QoS policy. The method according to claim 1,
Wherein the controller receives traffic statistical information between the core network and the first and second networks from the core network,
And the traffic distribution data further includes the received traffic statistical information. The method according to claim 1,
Wherein the wireless access network transmits terminal information including a user IP and a TEID of the connected mobile terminal to the controller when the mobile terminal accesses the terminal,
The controller establishes a terminal information DB using the terminal information received from the radio access network,
And the traffic distribution data includes the transmitted terminal information. 5. The method of claim 4,
Wherein the wireless access network transmits information of the released mobile terminal to the controller when the mobile terminal terminates,
And the controller deletes the revoked terminal information from the terminal information DB upon receiving the revoked terminal information. 6. The method of claim 5,
The controller deletes the associated entry from the entry DB when there is an entry related to the revoked mobile terminal and transmits a message to the core network to delete an entry related to the revoked mobile terminal from the entry table of the core network , Network system. delete The method according to claim 1,
Wherein the service type is extracted based on at least one of an external destination IP address of a GTP header of the traffic and a destination IP address of a mobile terminal packet. delete The method according to claim 1,
Wherein the core network adds a GTP header to the second network traffic when traffic is received from the second network, and transmits the second network traffic to which the GTP header is added to the wireless access network. delete

Images