Intergrated wire and wireless network packet broker and method for matching deep packet of the same

Abstract

The present invention relates to a network packet broker device including a deep packet matching module which controls a GTP correlation module to match a GTP control plane packet and a GTP user plane packet and a deep packet matching method thereof. Packet information in a deep stage at a switch level is extracted to match flows of the GTP control plane packet and the GTP user plane packet and a correlation may be assigned to forward the GTP control plane packet and the GTP user plane packet to the same egress port.

1 . A network packet broker device, comprising:
 a plurality of openflow edge switches connected to a plurality legacy networks which is radio access networks or wired access networks;   a software defined network (SDN) controller which acquires information of the plurality of openflow edge switches belonging to a switch group;   a legacy router container which treats a switch group including at least some of the plurality of switches as a virtual router to generate routing information for a packet ingressed to any one switch of the switch group; and   a network application module including modules which perform a function of manipulating a packet and controlling a flow in accordance with a request, through the controller,   wherein the legacy router container maps a plurality of network heads connected to the plurality of openflow switches which generates legacy routing information for a flow processing inquiry message of the controller based on information of at least one virtual router with information of an external network which is directly coupled to the virtual router, the network application module includes a GTP correlation module interworking to forward a GTP-C packet and a GTP-U packet of the flow packet to the same egress port, the network application module includes a deep packet matching module which extracts, modifies, removes, or inserts a GTP header or a VxLAN header of the flow packet, the GTP correlation module includes a GTP session tracking module, a GTP user plane forwarding module, and a storage, and the deep packet matching module controls the GTP correlation module to match the GTP control plane packet and the GTP user plane packet.   
     
     
         2 . The network packet broker device of  claim 1 , wherein the GTP correlation module includes:
 a storage which stores a subscriber table storing a subscriber IMSI and a GTP session table storing subscriber session information;   a GTP user plane forwarding module which receives a GTP user plane packet from a port unit of the switch to forward the GTP user plane packet to a predetermined port unit of the switch and searching for GTPU TEID of the GTP user plane packetin the storage to connect the egress port of the GTP user plane packet to the storage to be stored; and   a GTP control plane forwarding module which receives a GTP control plane packet from the port unit of the switch to forward the GTP control plane packet received from a port unit of the switch same as the searched egress port by searching for the egress port of the GTP user plane packet connected to a GTPU TEID of the GTP control plane packet in the storage.   
     
     
         3 . The network packet broker device of  claim 2 , further comprising:
 a processor,   wherein the storage of the GTP correlation module is located in the processor.   
     
     
         4 . The network packet broker device of  claim 2 , wherein the storage of the GTP correlation module includes an IMSI table, an MME context table, and an SGW context table, a subscriber table of the storage of the GTP correlation module is an IMSI table, a GTP session table of the storage of the GTP correlation module includes an MME context table and an SGW context table, and the GTP session table of the storage of the GTP correlation module further includes a correlation table which stores a correlation of the IMSI table, the MME context table, and the SGW context table. 
     
     
         5 . The network packet broker device of  claim 4 , wherein the correlation table of the storage of the GTP correlation module includes a first correlation table, a second correlation table, a third correlation table, and a fourth correlation table. 
     
     
         6 . A deep packet matching method of a network packet broker device, wherein the network packet broker device includes:
 a plurality of openflow edge switches connected to a plurality legacy networks which is radio access networks or wired access networks;   a software defined network (SDN) controller which acquires information of the plurality of openflow edge switches belonging to a switch group;   a legacy router container which treats a switch group including at least some of the plurality of switches as a virtual router to generate routing information for a packet ingressed to any one switch of the switch group; and   a network application module including modules which perform a function of manipulating a packet and controlling a flow in accordance with a request, through the controller,   wherein the legacy router container maps a plurality of network heads connected to the plurality of openflow switches which generates legacy routing information for a flow processing inquiry message of the controller based on information of at least one virtual router with information of an external network which is directly coupled to the virtual router, the network application module includes a GTP correlation module interworking to forward a GTP-C packet and a GTP-U packet of the flow packet to the same egress port, the network application module includes a deep packet matching module which extracts, modifies, removes, or inserts a GTP header or a VxLAN header of the flow packet, the GTP correlation module includes a GTP session tracking module, a GTP user plane forwarding module, and a storage, and the deep packet matching module controls the GTP correlation module to match the GTP control plane packet and the GTP user plane packet.   
     
     
         7 . The deep packet matching method of  claim 6 , comprising:
 a step of receiving a packet from an ingress port unit of a switch, by a deep packet matching module;   an ingress packet parsing step of extracting deep packet information from an input packet, by a packet parsing module of the switch;   an ingress packet pipeline step of processing a packet with acquired information, by the deep packet matching module;   a step of distinguishing a type of packet from information of the acquired packet, by the deep packet matching module;   a GTP control plane packet processing step of acquiring an egress port unit or an egress port group which sends a packet by querying a flow matching the packet to the GTP control plane egress table, by a GTP session tracking module when the distinguished type of packet is a GTP control plane packet; and   an egress packet pipeline step of processing the packet by querying the flow matching the packet to the GTP user plane egress table by a GTP user plane forwarding module when the distinguished type of packet is a GTP user plane packet.   
     
     
         8 . The deep packet matching method of  claim 7 , wherein the ingress packet parsing step includes:
 an ingress port parsing step of extracting ingress port information from an ingress packet by a packet parsing module;   an Ethernet protocol parsing step of extracting Ethernet protocol information from the ingress packet by the packet parsing module;   a VLAN parsing step of extracting VLAN information from the ingress packet when the extracted Ethernet protocol information is VLAN, by the packet parsing module;   an IPv4 parsing step of extracting IPv4 information from the ingress packet when the extracted Ethernet protocol information is IPv4, by the packet parsing module;   a TCP parsing step of extracting TCP information from the ingress packet when the type of the extracted IPv4 protocol is a TCP, by the packet parsing module;   an IMCP parsing step of extracting IMCP information from the ingress packet when the type of the extracted IPv4 protocol is a IMCP, by the packet parsing module;   an SCTP parsing step of extracting SCTP information from the ingress packet when the type of the extracted IPv4 protocol is an SCTP, by the packet parsing module;   an UDP parsing step of extracting UDP protocol number information from the ingress packet by the packet parsing module;   a VxLAN parsing step of extracting VxLAN information from the ingress packet when the extracted UDP protocol number is VxLAN, by the packet parsing module;   a GTP parsing step of extracting GTP information from the ingress packet when the extracted UDP protocol number is GTP, by the packet parsing module;   an Inner Ether parsing step of extracting Inner Ether information from the ingress packet by the packet parsing module;   an Inner IPv4 parsing step of extracting Inner IPv4 information from the ingress packet by the packet parsing module; and   an Inner TCP/UDP parsing step of extracting inner TCP and inner UDP information from the ingress packet by the packet parsing module.   
     
     
         9 . The deep packet matching method of  claim 7 , wherein the ingress pipeline step includes:
 an ingress port mapping step of converting an ingress physical port to a logic port used for a match action table, by the deep packet matching module;   a GTP filter applying step of storing processing of a packet corresponding to GTP information extracted from the ingress packet in an egress port match action table, by the deep packet matching module; and   an Inner IPv4 filter applying step of storing processing of a packet corresponding to Inner IPv4 information extracted from the ingress packet in an egress port match action table, when there is Inner IPv4 information extracted from the ingress packet, by the deep packet matching module.   
     
     
         10 . The deep packet matching method of  claim 7 , wherein the egress packet parsing step includes:
 an ingress port filter number parsing step of extracting an ingress port filter number from an egress packet, by the deep packet matching module;   an ingress port filter matching step of querying the ingress port filter number extracted from the egress packet to a policy manager module, by the deep packet matching module;   a step of extracting the matched ingress port action from the policy manager module when there is a matched ingress port filter number;   a GTP filter number parsing step of extracting a GTP filter number from the egress packet, by the deep packet matching module;   an GTP filter matching step of querying a GTP filter number extracted from the egress packet to a policy manager module, by the deep packet matching module;   a step of extracting the matched GTP action from the policy manager module when there is a matched GTP filter number;   an Inner IPv4 parsing step of extracting Inner IPv4 information from the egress packet, by the deep packet matching module;   an Inner IPv4 matching step of querying Inner IPv4 information extracted from the egress packet to the policy manager module, by the deep packet matching module;   a step of extracting the matched Inner IPv4 action from the policy manager module when there is a matched Inner IPv4 information; and   an action list generating step of storing all the pairs of the egress packet and extracted action lists in a GTP user plane egress port match action table, by the deep packet matching module   
     
     
         11 . The deep packet matching method of  claim 6 , further comprising:
 a GTP user plane forwarding step of receiving a GTP user plane packet from a port unit of the switch to forward the GTP user plane packet to a predetermined port unit of the switch and searching for GTPU TEID of the GTP user plane packet in the storage to connect the egress port of the GTP user plane packet to the storage to be stored; and   a GTP control plane forwarding step of receiving a GTP control plane packet from the port unit of the switch to forward the GTP control plane packet received from a port unit of the switch same as the searched egress port by searching for the egress port of the GTP user plane packet connected to a GTPU TEID of the GTP control plane packet in the storage.   
     
     
         12 . The deep packet matching method of  claim 11 , wherein the storage of the GTP correlation module includes an IMSI table, an MME context table, and an SGW context table, a subscriber table of the storage of the GTP correlation module is an IMSI table, a GTP session table of the storage of the GTP correlation module includes an MME context table and an SGW context table, and the GTP session table of the storage of the GTP correlation module further includes a correlation table which stores a correlation of the IMSI table, the MME context table, and the SGW context table. 
     
     
         13 . The deep packet matching method of  claim 12 , wherein the correlation table of the storage of the GTP correlation module includes a first correlation table, a second correlation table, a third correlation table, and a fourth correlation table. 
     
     
         14 . The deep packet matching method of  claim 13 , further comprising:
 a step of generating a record with an MME IP address as a key and a bearer ID set including an MME IP, a bearer ID, and a sequence and an MME S11 TEID as values in an MME context table, by the GTP correlation module;   a step of generating a record with an SGW IP address as a key in the SGW context table, by the GTP correlation module;   a step of updating SGW S11 TEID and SGW S1U TEID by searching for a record with the SGW IP address as a key, in the SGW context table, by the GTP correlation module;   a step of generating a record with MME S11 TEID as a key and with IMSI context and SGW S11 TEID context as values, in the first correlation table, by the GTP correlation module;   a step of generating a record with SGW S11 TEID as a key and with MME S11 context as a value, in the second correlation table, by the GTP correlation module;   generating a record with SGW S11 TEID as a key and with SGW S11 TEID context as a value, in the third correlation table, by the GTP correlation module;   a step of generating a record with eNB TEID and eNB IP as keys and with SGW S1U TEID context as a value, in the fourth correlation table, by the GTP correlation module;   a step of updating a bearer ID set including an MME IP, a bearer ID, and a sequence of a record with an MME IP address as a key and an eNB S1U TEID value in the MME context table, by the GTP correlation module; and   a step of generating a record with an IMSI as a key and with a bearer ID set including an MME IP, a bearer ID, and a sequence as a value, in the IMSI table, by the GTP correlation module.