WO2012096131A1 - ネットワークシステム、及び経路制御方法 - Google Patents
ネットワークシステム、及び経路制御方法 Download PDFInfo
- Publication number
- WO2012096131A1 WO2012096131A1 PCT/JP2011/080325 JP2011080325W WO2012096131A1 WO 2012096131 A1 WO2012096131 A1 WO 2012096131A1 JP 2011080325 W JP2011080325 W JP 2011080325W WO 2012096131 A1 WO2012096131 A1 WO 2012096131A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- terminal
- switch
- destination
- entry
- controller
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/38—Flow based routing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L49/00—Packet switching elements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/302—Route determination based on requested QoS
- H04L45/306—Route determination based on the nature of the carried application
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/52—Multiprotocol routers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/64—Routing or path finding of packets in data switching networks using an overlay routing layer
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/74—Address processing for routing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L49/00—Packet switching elements
- H04L49/70—Virtual switches
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/72—Routing based on the source address
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
- H04L47/2483—Traffic characterised by specific attributes, e.g. priority or QoS involving identification of individual flows
Definitions
- the present invention relates to a network system, and more particularly to a route control method for a network system.
- a method of controlling switches, terminals, etc. (user plane) from an external controller (control plane) is called a CU (C: control plane / U: user plane) separated architecture.
- a network having a configuration based on such a CU separation type architecture is referred to as a CU separation type network.
- the OpenFlow network is only an example.
- a controller such as OFC (OpenFlow Controller) controls the behavior of a switch by operating a flow table of the switch such as OFS (OpenFlow Switch).
- OFC OpenFlow Controller
- OFS OpenFlow Switch
- the flow table is a table in which entries (entries) defining predetermined processing contents (actions) to be performed on packets (communication data) that meet predetermined matching conditions (rules) are registered.
- the packet may be read as a frame.
- a packet group (packet series) that conforms to the rule is called a flow.
- the rules of the flow are: destination address (DA: Destination Address), source address (SA), destination port (DP: Destination Port), source port included in the header area (field) of each protocol layer of the packet It is defined by various combinations using any or all of (SP: Source Port) and can be distinguished.
- DA Destination Address
- SA source address
- DP Destination Port
- source port included in the header area (field) of each protocol layer of the packet It is defined by various combinations using any or all of (SP: Source Port) and can be distinguished.
- SP Source Port
- the above address includes a MAC address (Media Access Control Address) and an IP address (Internet Protocol Address).
- IP address Internet Protocol Address
- the flow action is usually a packet transfer to a predetermined transfer destination.
- packet discard is usually specified as the flow action.
- a switch In an OpenFlow network, normally, when a switch receives a packet that does not have a corresponding entry, the switch sends an inquiry (entry request) about the packet to the controller. Normally, the switch transfers the packet to the controller as an inquiry about the packet.
- the controller In the OpenFlow network, the controller is usually connected to a switch under management through a secure channel connection.
- the controller receives an inquiry about a packet from a switch under management, the controller calculates a route (path) of the packet group (flow) and, based on the route, stores the packet group ( The entry “transfers the flow) to a predetermined transfer destination” is registered.
- the controller transmits a control message for registering the entry to the flow table to the switch.
- the controller calculates a route (path) of a predetermined packet group (flow) “in advance” (before data communication starts), and registers an entry in the flow table of the switch.
- the “Proactive type” here refers to “advance entry registration” that the controller voluntarily performs.
- the controller calculates the route of the packet group (flow) when receiving an inquiry about the 1st packet (new packet with no corresponding entry) from the switch, and enters the entry in the flow table of the switch. sign up. That is, the “Reactive type” here refers to “real-time entry registration” performed by the controller in response to an inquiry from the switch during actual data communication.
- the “Reactive type” that registers an entry related to the received packet when the controller receives an inquiry about the 1st packet from the switch is the center.
- the “Proactive type” is suitable for reducing the processing frequency of the flow table and solving the performance problem.
- the Proactive type is preferable in order to be able to process even when a large amount of 1st packets arrive at the controller.
- the number of entries is considered to be enormous when the complete proactive type is used, it may be possible to avoid the restriction on the number of entries by making a part of the reactive type.
- the flow can be defined before the start of communication, so that it is considered possible to avoid the problem of mass flow due to viruses such as Nimda, unauthorized access due to unknown packets, and the like.
- the network system includes a plurality of switches and a controller.
- Each of the plurality of switches performs an operation according to the action defined in the entry for the received packet that conforms to the rule of the entry registered in its own flow table.
- the controller uses a unique identifier for the route calculated according to the physical topology of the network formed by a plurality of switches as a rule, and communicates an entry using an output from a predetermined output port as an action. Register with each switch before it begins.
- each of the plurality of switches performs an operation according to the action defined in the entry for a received packet that conforms to the entry rule registered in its own flow table.
- an entry having a rule as an identifier unique to a route calculated according to the physical topology of a network formed by a plurality of switches and an action from an output from a predetermined output port is set between the plurality of switches.
- the program according to the present invention is a program for causing a computer to execute the operation of the controller in the above path control method.
- the program according to the present invention can be stored in a storage device or a storage medium.
- the present invention is directed to a CU separation type network.
- an OpenFlow network that is one of CU separation type networks will be described as an example. However, actually, it is not limited to the OpenFlow network.
- the controller 20 associates the switch ID (64 bits) of each switch with the uniquely defined node ID (16 bits) on a one-to-one basis before communication is started.
- the number of bits is only an example. That is, the controller 20 assigns a node ID to each switch. Further, the controller 20 calculates a path between the edge switches that can be connected to the terminal, and stores in the flow table of each core switch (Core) that is a relay switch on the path “at least in the destination information area of the received packet” If a predetermined node ID is described in part, a Core entry (relay entry) indicating that the received packet is transferred (from a predetermined output port) to the next-stage switch is registered.
- the core switch determines whether transfer is possible using the node ID described in the destination information area of the received packet as a match condition (rule).
- the controller 20 may designate other information described in the destination information area of the received packet as a match condition (rule).
- the controller 20 “transfers the received packet (from a predetermined output port) to the next-stage switch” (regardless of the node ID) in each flow table of the core switch (Core). It is also possible to register a Core entry to that effect. In this case, the core switch (Core) unconditionally transfers the received packet to the next-stage switch.
- the controller 20 displays in the edge switch flow table that “at least a part of the destination packet destination information area includes the node ID of the edge switch and the user ID of the subordinate terminal”. If it is described, an Egress entry (output entry) indicating that the destination information of the received packet is returned to the terminal and the received packet is transferred to the terminal is registered.
- the user ID of the subordinate terminal is set as the match condition (rule) because there may be a plurality of subordinate terminals.
- the match condition since the combination of the node ID of the edge switch and the user ID of the terminal is used as a match condition (rule), it is possible to use a user ID that is duplicated between edge switches. However, duplicate user IDs cannot be used for each terminal under the same edge switch.
- the controller 20 sets the flow table of the input side edge switch (Ingress) as follows: “When receiving a predetermined packet, the destination information is used as a search key, and at least a part of the destination information area of the received packet An Ingress entry (input entry) is registered in which the node ID of the output side edge switch (Egress) and the user ID of the destination terminal are entered and transferred to the next-stage switch.
- the above-mentioned “predetermined packet” may be read as “a packet that meets a predetermined match condition (rule)”.
- the Ingress entry since the input side edge switch (Ingress) first identifies the flow, the Ingress entry is defined with a packet matching rule similar to that of a normal open flow and the above-described action for the matched packet. Become.
- the controller 20 determines a terminal (destination candidate terminal) to be a predetermined packet transfer destination in advance before communication is started. Then, before the communication is started, the controller 20 stores in the flow table of the edge switch that can be the input-side edge switch, “When a predetermined packet is received, the destination information is used as a search key, and the destination of the received packet is An Ingress entry indicating that the node ID of the edge switch to which the destination candidate terminal is connected and the user ID of the destination candidate terminal are described in at least a part of the information area and transferred to the next switch. sign up. In this embodiment, this case will be described.
- the controller 20 when the controller 20 receives an inquiry about the received packet from the input side edge switch that has received the packet from the transmission source terminal, the path of the received packet group (flow) Based on this route, the flow table of the input side edge switch indicates that “when a predetermined packet is received, the destination information is used as a search key and at least a part of the destination information area of the received packet. Then, an Ingress entry indicating that the node ID of the edge switch to which the destination candidate terminal is connected and the user ID of the destination candidate terminal are described and transferred to the next switch is registered. This case will be described in the second embodiment.
- the controller 20 defines a redundancy ID for each path. Since each of the next-stage switches exists on the respective route, each of the next-stage switches is associated with a redundancy ID. If the redundant ID (with a predetermined node ID) is described in at least a part of the destination information area of the received packet in the flow table of the core switch (Core), the controller 20 designates the received packet as the redundant ID. To the next-stage switch corresponding to “.” Is registered.
- the controller 20 uses the flow table of the input side edge switch to indicate that “when the predetermined packet is received, the destination information is used as a search key, and the output side edge is included in at least a part of the destination information area of the received packet.
- An Ingress entry is registered to the effect that “the node ID of the switch, the redundant ID, and the user ID of the destination terminal are described and transferred to the next-stage switch”.
- the redundant ID may be a part of the node ID of the output edge switch. For example, several bits (bits) at the beginning or end of the node ID area may be used as the redundant ID area.
- VM virtual machines
- a processor for executing the above, a memory for storing the program and various data, and a communication interface for connecting to a network.
- a CPU Central Processing Unit
- a microprocessor a microcontroller
- IC Integrated Circuit
- semiconductor storage devices such as RAM (Random Access Memory), ROM (Read Only Memory), EEPROM (Electrically Erasable and Programmable Read Only Memory), and HDD Memory (SDHidK)
- RAM Random Access Memory
- ROM Read Only Memory
- EEPROM Electrical Erasable and Programmable Read Only Memory
- HDD Memory HDD Memory
- An auxiliary storage device such as State Drive
- a removable disk such as a DVD (Digital Versatile Disk)
- a storage medium such as an SD memory card (Secure Digital memory card), or the like is conceivable.
- processor and the memory may be integrated.
- a single chip such as a microcomputer has been developed. Therefore, a case where a one-chip microcomputer mounted on an electronic device or the like includes a processor and a memory can be considered.
- Examples of the above communication interfaces include semiconductor integrated circuits such as boards (motherboards, I / O boards) and chips that support network communication, network adapters such as NIC (Network Interface Card), similar expansion cards, antennas, etc. Communication ports such as communication devices and connection ports (connectors) are conceivable.
- networks include the Internet, LAN (Local Area Network), wireless LAN (Wireless LAN), WAN (Wide Area Network), backbone (Backbone), cable TV (CATV) line, fixed telephone network, mobile phone network, WiMAX (IEEE 802.16a), 3G (3rd Generation), dedicated line (lease line), IrDA (Infrared Data Association), Bluetooth (registered trademark), serial communication line, data bus, and the like are conceivable.
- the controller 20 detects the physical topology of the network by LLDP (Link Layer Discovery Protocol).
- LLDP is a protocol for periodically collecting neighboring device information by transmitting and receiving control frames.
- Inward config is setting information for communication with the inside of the network.
- Outward configuration is setting information for communication with the outside of the network.
- PortStat port status information
- the controller 20 recognizes a port having an inward and explicit setting as an “inward port” (Inside Port). Further, the controller 20 recognizes a port having an outward setting and an explicit setting in the port status information as an “outward port” (Outside Port).
- the controller 20 transmits an LLDP control frame to an inward port and a port (such as an unconfigured port) that is not explicitly set to be outward. Then, the controller 20 detects the physical topology of the network from the response to the LLDP control frame, and creates topology information.
- the node ID may be associated with only a switch (edge switch) having an outward port.
- DPID: # 1 to # 6 is shown as the switch ID. In practice, “DPID: # 1 to # 6” can be used as the node ID as it is.
- the node ID includes a sub node ID and a redundant ID.
- the sub node ID is a substantial body of the node ID for specifying the switch.
- the sub-node ID may be identification information that can specify a switch alone.
- the sub node ID may be combined with the redundant ID to form a node ID for uniquely specifying the switch.
- the redundant ID is identification information for specifying a route.
- the redundancy ID may be stored in another area as long as the relationship with the node ID is maintained and the redundancy ID can be specified.
- the controller 20 calculates a route between the switches (edge switches) in which the outward ports exist, and stores in the flow table of the core switch (Core) on the route “at least a part of the destination information area of the received packet. If a predetermined node ID (the node ID of the edge switch in which the outward port exists) is described, a Core entry is registered indicating that the received packet is transferred to the next-stage switch on the route. That is, the core switch determines whether transfer is possible using the node ID described in the destination information area of the received packet as a match condition (rule). Of course, in addition to the node ID, the controller 20 may also specify other information (VTNID, user ID, etc.) described in the destination information area of the received packet as a match condition (rule).
- the controller 20 “transfers the received packet (from a predetermined output port) to the next-stage switch” (regardless of the node ID) in each flow table of the core switch (Core). It is also possible to register a Core entry to that effect. In this case, the core switch (Core) unconditionally transfers the received packet to the next-stage switch. Whether or not the received packet can be transferred is determined by the input side edge switch (Ingress) or the output side edge switch (Egress).
- the controller 20 calculates a route between all the switches having the outward ports, and registers the Core entry in the flow table of the core switch (Core) on the route as described above.
- the entry includes data storage areas such as “Port”, “DA” (Destination Address), “SA” (Source Address), “OPPort” (Output Port), and “Mod” (Modify).
- Data storage areas such as “Port”, “DA” (Destination Address), “SA” (Source Address), “OPPort” (Output Port), and “Mod” (Modify).
- Port is a storage area for information indicating the input port of the received packet.
- DA is a storage area for destination information of a received packet.
- SA is a storage area for transmission source information of a received packet.
- OPort is a storage area for information indicating the output port of the received packet.
- Mode is an information storage area that defines a process to be performed on a received packet.
- ID group stored in “DA” is information such as “node ID”, “VTNID”, and “user ID”.
- the “node ID” is a storage area of identification information for specifying a switch (a node in which an outward port exists) to be an output side edge switch.
- VTNID is a storage area of identification information of a VN (Virtual Network) to which a packet group (flow) passing through a path between switches in which an outward port exists, such as VTN (Virtual Tenant Network).
- VTNID Virtual Network
- User ID is identification information of a user ID for specifying a destination terminal (a terminal connected / connectable to a switch having an outward port). The association between the terminal and the user ID is performed in “station detection” described below.
- the controller 20 performs station detection by using an ARP (Address Resolution Protocol) control frame transmitted by the terminal for address resolution.
- ARP Address Resolution Protocol
- control frame is only an example.
- a control frame such as DHCP (Dynamic Host Configuration Protocol) may be used.
- DHCP Dynamic Host Configuration Protocol
- control frame is not limited.
- terminal 30-1 is “terminal A” and the terminal 30-2 is “terminal B”.
- ARP_Req ARP request (Request)
- the MAC address of terminal B is not known, but only the IP address of terminal B is used. Is known, terminal A broadcasts ARP_Req (ARP request) for resolving the address of terminal B.
- the edge switch 10-1 to which the terminal A is connected transfers ARP_Req (ARP request) to the controller 20 through a secure channel connection.
- ARP_Req ARP request
- the controller 20 operates as an ARP proxy.
- the controller 20 When the controller 20 receives the ARP_Req (ARP request) from the edge switch 10-1 to which the terminal A is connected, the controller 20 acquires the MAC address (and IP address) of the terminal A from the transmission source information of the ARP_Req (ARP request).
- a user ID is assigned to terminal A. That is, the MAC address (and IP address) of terminal A is associated with the user ID.
- the controller 20 indicates in the flow table of the edge switch 10-1 to which the terminal A is connected that “the user ID of the terminal A under its control (with the node ID of the edge switch) in at least a part of the destination information area of the received packet”. If it is described, an Egress entry indicating that the destination information of the received packet is returned to the MAC address of the terminal A and the received packet is transferred to the MAC address of the terminal A is registered.
- ARP_Req (ARP request) is broadcasted to each of... At this time, the transmission source MAC address of ARP_Req (ARP request) is the MAC address of terminal A.
- the edge switch 10-6 to which the terminal B is connected transfers the ARP_Req (ARP request) transmitted by broadcast to the terminal B.
- terminal B is described as a destination terminal, but the same processing as described above is performed for an edge switch to which another destination terminal is connected.
- terminal B transmits ARP_Rep (ARP reply) to terminal A as a response to ARP_Req (ARP request).
- the edge switch 10-6 to which the terminal B is connected transfers ARP_Rep (ARP reply) to the controller 20 through a secure channel connection.
- ARP_Rep ARP reply
- the controller 20 operates as an ARP proxy.
- the controller 20 When receiving the ARP_Rep (ARP reply) from the edge switch 10-6 to which the terminal B is connected, the controller 20 acquires the MAC address (and IP address) of the terminal B from the transmission source information of the ARP_Rep (ARP reply).
- a user ID is assigned to terminal B. That is, the MAC address (and IP address) of terminal B is associated with the user ID.
- the controller 20 indicates in the flow table of the edge switch 10-6 to which the terminal B is connected that “the user ID of the terminal B under its control is included in at least a part of the destination information area of the received packet (with the node ID of the edge switch). If it is described, an Egress entry indicating that the destination information of the received packet is returned to the MAC address of the terminal B and the received packet is transferred to the MAC address of the terminal B is registered.
- the controller 20 determines that communication between the terminal A and the terminal B is possible, and “receives a packet addressed to the terminal B” in the flow table of the edge switch 10-1 to which the terminal A is connected.
- the ID group node ID of the edge switch to which the terminal B is connected, the VTNID of the flow, and the user ID of the terminal B
- This entry registration method is “Proactive type” (a method of registering Ingress entries in advance).
- the controller 20 transfers the ARP_Rep (ARP reply) to the terminal A. Therefore, the controller 20 transmits the ARP_Rep to the edge switch 10-1 to which the terminal A is connected through the secure channel connection. (ARP reply) is transmitted. At this time, the transmission source MAC address of ARP_Rep (ARP reply) is the MAC address of terminal B.
- the edge switch 10-1 to which the terminal A is connected transfers the ARP_Rep (ARP reply) received from the controller 20 to the terminal A.
- Terminal A acquires the MAC address of terminal B from ARP_Rep (ARP reply) received as a response to ARP_Req (ARP request).
- the terminal A describes the MAC address (and IP address) of the destination terminal B in the packet destination information area, and transmits the packet addressed to the terminal B.
- the edge switch 10-1 to which the terminal A is connected receives the packet addressed to the terminal B at the input port 1, the edge switch 10-1 checks whether an entry matching the received packet is registered in its own flow table.
- the edge switch 10-1 to which the terminal A is connected has, in its own flow table, “When a packet addressed to the terminal B is received, at least a part of the destination information area of the received packet includes an ID group (the terminal B Since an Ingress entry is registered indicating that the node ID of the connected edge switch 10-6, the VTNID of the flow, and the user ID of the terminal B are described and transferred to the next-stage switch, it is received.
- the ID group is described in at least a part of the destination information area of the packet and transferred to the next-stage switch.
- the edge switch 10-1 changes the MAC address of the terminal B described in the destination information of the received packet to the ID group (overwrites the ID group in the destination information), and the changed packet (hereinafter referred to as ID) Packet) is transferred to the output port 2 and transferred from the output port 2 to the next-stage switch 10-2.
- the edge switch 10-2 When the edge switch 10-2 receives the ID packet at the input port 3, it checks whether an entry that matches the ID packet is registered in its own flow table.
- the edge switch 10-2 reads “if the node ID of the edge switch 10-6 is described in at least a part of the destination information area of the received packet in its own flow table (the predetermined output port). Since the “Core entry” indicating “transfer to the next-stage switch” is registered, the ID packet is transferred to the output port 4 and transferred from the output port 4 to the next-stage switch 10-3. Note that the edge switch 10-2 determines which of the output port 4 and the output port 5 is transferred based on the value of “OPort” of the Core entry.
- the edge switch 10-2 searches for the corresponding Core entry using the value of the redundant ID as a search key.
- the edge switch 10-3 When the edge switch 10-3 receives the ID packet at the input port 10, it confirms whether an entry that matches the ID packet is registered in its own flow table.
- the edge switch 10-3 reads “if the node ID of the edge switch 10-6 is described in at least a part of the destination information area of the received packet in its own flow table (the predetermined output port). Since the “Core entry” indicating “transfer to the next-stage switch” is registered, the ID packet is transferred to the output port 12 and transferred from the output port 12 to the next-stage switch 10-6.
- the edge switch 10-6 When the edge switch 10-6 receives the ID packet at the input port 13, the edge switch 10-6 checks whether an entry that matches the ID packet is registered in its own flow table.
- the edge switch 10-6 to which the terminal B is connected has, in its own flow table, the user of the terminal B under the control of “at least part of the destination information area of the received packet (with the node ID of the edge switch 10-6)” If the ID is described, since the Egress entry of “return destination information of the received packet to the MAC address of the terminal B and transfer the received packet to the MAC address of the terminal B” is registered, The ID group described in the destination information area of the ID packet is changed to the MAC address of terminal B (overwrites the MAC address of terminal B in the destination information), and the changed packet (original received packet) ) To the output port 14 and from the output port 14 to the terminal B.
- the “MAC address area” is described as an example of the destination information area.
- the “IP address area” may actually be used. That is, it may be a “destination address area”.
- the controller 20 registers an Ingress entry as a response when receiving an inquiry about a received packet from a switch under management via a secure channel connection.
- the terminal A describes the MAC address (and IP address) of the destination terminal B in the packet destination information area, and transmits the packet addressed to the terminal B.
- the edge switch 10-1 to which the terminal A is connected receives the packet addressed to the terminal B, the edge switch 10-1 checks whether an entry that matches the packet is registered in its own flow table. At this time, since the entry (Ingress entry) that matches the packet is not registered in the edge switch 10-1 to which the terminal A is connected, the edge switch 10-1 to which the terminal A is connected The packet addressed to the terminal B is forwarded to the controller 20 by (Secure Channel) connection.
- the controller 20 acquires the MAC address (and IP address) of the terminal B from the destination information of the packet addressed to the terminal B, and from the topology information and station information held by itself, the user ID of the terminal B and the terminal B
- the node ID of the connected edge switch 10-6 is specified.
- the controller 20 indicates that “when a packet addressed to the terminal B is received, at least a part of the destination information area of the received packet includes an ID group (terminal B Ingress entry indicating that the node ID of the edge switch to which is connected, the VTNID of the flow concerned, and the user ID of the terminal B) are transferred to the next-stage switch is registered.
- This entry registration method is a “Reactive type” (a method of registering an Ingress entry when the first packet arrives).
- a switch corresponding to the first embodiment and a switch corresponding to the second embodiment may be mixed. Further, when there are a plurality of VTNs, the embodiment may be made different for each VTN.
- [Appendix 1: System configuration] A plurality of switches each performing an operation in accordance with the action defined in the entry for a received packet that conforms to the rules of the entry registered in its own flow table; Communication between a plurality of switches starts with an entry having a rule as an identifier unique to a route calculated according to the physical topology of the network formed by the plurality of switches, and an output from a predetermined output port as an action. And a controller that registers with each of the switches before the network system.
- the network system is A port information collection unit that inputs inward and outward setting information to each switch and collects port information of each switch when topology detection before the start of communication; Based on the port information of each switch, the inward port and the outward port are specified, the switch specifying unit for specifying the edge switch and the core switch, A control frame sending unit that sends a control frame for collecting neighboring switch information to an inward port and a port that is not explicitly set as an outward direction; From a response to the control frame, a topology information creation unit that detects the physical topology of the network and creates topology information; A node ID assignment processing unit for associating each switch with a node ID as the unique identifier; If the path between the switches where the outgoing ports exist is calculated and the node ID of the edge switch is described in the destination information area of the received packet in the flow table of the core switch, the received packet is sent to the next switch.
- a network system comprising: a relay entry
- the network system according to attachment 2, wherein The controller is At the time of station detection before the start of communication, based on an ARP request from the transmission source terminal, a transmission source terminal identification unit that identifies destination information of the transmission source terminal; A transmission source user ID allocation processing unit that associates a user ID as the unique identifier with the transmission source terminal; When the node ID of the edge switch and the user ID of the source terminal are described in the destination information area of the received packet in the flow table of the edge switch to which the source terminal is connected, the destination of the received packet A network system further comprising: a transmission source terminal side output entry registration unit that registers destination information of the transmission source terminal in an information area and registers an output entry indicating that the received packet is transferred to the transmission source terminal .
- the controller is A destination terminal specifying unit for specifying destination information of the destination terminal based on an ARP response from the destination terminal when detecting a station before starting communication;
- a destination user ID assignment processing unit that associates a user ID as the unique identifier with the destination terminal;
- the node ID of the edge switch and the user ID of the destination terminal are described in the destination information area of the received packet in the flow table of the edge switch to which the destination terminal is connected, the destination information of the received packet
- a network system further comprising: a destination terminal-side output entry registration unit that registers destination information of the destination terminal in an area and registers an output entry for transferring the received packet to the destination terminal.
- the network system according to attachment 4, wherein The controller is A communication availability determination unit that determines that communication between the transmission source terminal and the destination terminal is possible based on an ARP response from the destination terminal during station detection before the start of communication; When a packet addressed to the destination terminal is received in the flow table of the edge switch to which the source terminal is connected, the edge switch of the edge switch to which the destination terminal is connected is at least part of the destination information area of the received packet.
- a network system further comprising: a transmission source terminal side entry entry registration unit for registering an entry for entry indicating that a node ID and a user ID of the destination terminal are transferred to a next-stage switch.
- the network system according to attachment 4, wherein The controller is A communication availability determination unit that determines that communication between the transmission source terminal and the destination terminal is possible based on a packet inquiry from an edge switch to which the transmission source terminal is connected when communication is started. When, When a packet addressed to the destination terminal is received in the flow table of the edge switch to which the source terminal is connected, the edge switch of the edge switch to which the destination terminal is connected is at least part of the destination information area of the received packet.
- a network system further comprising: a transmission source terminal side entry entry registration unit for registering an entry for entry indicating that a node ID and a user ID of the destination terminal are transferred to a next-stage switch.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
Description
オープンフローネットワークでは、OFC(OpenFlow Controller)等のコントローラが、OFS(OpenFlow Switch)等のスイッチのフローテーブルを操作することによりスイッチの挙動を制御する。
以下に、本発明の第1実施形態について添付図面を参照して説明する。
図1に示すように、本発明に係るネットワークシステムは、スイッチ10(10-i、i=1~n:nはスイッチ台数)と、コントローラ20を含む。
スイッチ10(10-i、i=1~n)は、内部にフローテーブルを持ち、コントローラ20からフローテーブルに登録されたエントリに従って、パケットを転送する。
コントローラ20は、トポロジ(topology:ネットワークの接続形態)検知を行い、ネットワークを構成するスイッチ10(10-i、i=1~n)を検知し、フロー毎の経路(パス)を計算する。これにより、コントローラ20は、ネットワークを構成する全てのスイッチの識別情報(スイッチID、MACアドレス等)、及び各スイッチの接続形態を認識し、各スイッチの次段のスイッチを特定する。
なお、コントローラ20が入力側エッジスイッチのフローテーブルにエントリを登録するタイミングとしては、「通信が開始される前」(事前登録)と、「実際の通信時」(リアルタイム登録)の2つが考えられる。
更に、各スイッチの次段のスイッチが複数存在する場合(経路が複数の場合)、コントローラ20は、経路毎に冗長IDを定義する。次段のスイッチの各々はそれぞれの経路上に存在するため、次段のスイッチの各々と冗長IDとが対応付けられる。コントローラ20は、コアスイッチ(Core)のフローテーブルに、「受信パケットの宛先情報の領域の少なくとも一部に(所定のノードIDと)冗長IDが記載されていれば、当該受信パケットを当該冗長IDに対応する次段のスイッチに転送する」という旨のCoreエントリを登録する。また、コントローラ20は、入力側エッジスイッチのフローテーブルに、「所定のパケットを受信した際、宛先情報を検索のキーとして使用し、受信パケットの宛先情報の領域の少なくとも一部に、出力側エッジスイッチのノードIDと、冗長IDと、宛先となる端末のユーザIDとを記載して次段のスイッチに転送する」という旨のIngressエントリを登録する。冗長IDは、出力側エッジスイッチのノードIDの一部でも良い。例えば、ノードIDの領域の先頭又は末尾の数ビット(bit)を、冗長IDの領域として使用しても良い。
スイッチ10(10-i、i=1~n)の例として、ネットワークスイッチ(network switch)、ルータ(router)、プロキシ(proxy)、ゲートウェイ(gateway)、ファイアウォール(firewall)、ロードバランサ(load balancer:負荷分散装置)、帯域制御装置(packet shaper)、セキュリティ監視制御装置(SCADA:Supervisory Control And Data Acquisition)、ゲートキーパー(gatekeeper)、基地局(base station)、アクセスポイント(AP:Access Point)、通信衛星(CS:Communication Satellite)、或いは、複数の通信ポートを有する計算機等が考えられる。また、スイッチ10(10-i、i=1~n)は、物理マシン上に構築された仮想スイッチでも良い。
図2を参照して、トポロジ検知の際の処理について説明する。
以下に、エントリの構成例について説明する。
エントリは、「Port」、「DA」(Destination Address)、「SA」(Source Address)、「OPort」(Output Port)、「Mod」(Modify)等のデータ格納領域を含む。
図3、図4を参照して、ステーション検知の際の処理について説明する。
図3に示すように、端末Aから端末Bに対して通信する際に、端末BのMACアドレスがわからず、端末BのIPアドレスだけがわかっている場合、端末Aは、端末Bのアドレスを解決するためのARP_Req(ARPリクエスト)をブロードキャストで送信する。
図4に示すように、端末Bは、ARP_Req(ARPリクエスト)に対する応答として、端末A宛にARP_Rep(ARPリプライ)を送信する。
図5を参照して、エントリ登録完了後のスイッチ間でのIPパケット等の通信の際の処理について説明する。
以下に、本発明の第2実施形態について説明する。
本実施形態では、ステーション検知の際ではなく、スイッチ間でのIPパケット等の通信を開始した際に、入力側エッジスイッチのフローテーブルに「Ingressエントリ」を登録する事例について説明する。
図6を参照して、データ通信開始時のパケットの問い合わせの際の処理について説明する。
なお、上記の各実施形態は、組み合わせて実施することも可能である。例えば、本発明に係るネットワークシステムにおいて、第1実施形態に対応するスイッチと、第2実施形態に対応するスイッチが混在していても良い。また、複数のVTNが存在する場合、VTN毎に実施形態を別々にしても良い。
上記の実施形態の一部又は全部は、以下の付記のように記載することも可能である。但し、実際には、以下の記載例に限定されない。
それぞれが、自身のフローテーブルに登録されたエントリのルールに適合する受信パケットに対し、前記エントリに定義されたアクションに従った動作を行う複数のスイッチと、
前記複数のスイッチによって形成されるネットワークの物理トポロジに応じて計算された経路に固有の識別子をルールとし、所定の出力ポートからの出力をアクションとしたエントリを、複数のスイッチ間において通信が開始される前に、前記各スイッチに登録するコントローラと
を含む
ネットワークシステム。
付記1に記載のネットワークシステムであって、
前記コントローラは、
通信開始前のトポロジ検知の際、前記各スイッチに内向き及び外向きの設定情報を投入し、前記各スイッチのポート情報を収集するポート情報収集部と、
前記各スイッチのポート情報を基に、内向きポートと外向きポートとを特定し、エッジスイッチとコアスイッチとを特定するスイッチ特定部と、
内向きポート、及び外向きと明示的な設定のないポートに対して、隣接スイッチ情報を収集するための制御フレームを送信する制御フレーム送出部と、
前記制御フレームに対する応答から、ネットワークの物理トポロジを検知し、トポロジ情報を作成するトポロジ情報作成部と、
前記各スイッチに、前記固有の識別子としてノードIDを対応付けるノードID割り当て処理部と、
外向きポートが存在するスイッチ間の経路を計算し、コアスイッチのフローテーブルに、受信パケットの宛先情報の領域にエッジスイッチのノードIDが記載されている場合は次段のスイッチに当該受信パケットを転送する旨の中継用エントリを登録する中継用エントリ登録部と
を具備する
ネットワークシステム。
付記2に記載のネットワークシステムであって、
前記コントローラは、
通信開始前のステーション検知の際、送信元端末からのARP要求を基に、前記送信元端末の宛先情報を特定する送信元端末特定部と、
前記送信元端末に、前記固有の識別子としてユーザIDを対応付ける送信元ユーザID割り当て処理部と、
前記送信元端末が接続されたエッジスイッチのフローテーブルに、受信パケットの宛先情報の領域に当該エッジスイッチのノードID及び前記送信元端末のユーザIDが記載されている場合は、当該受信パケットの宛先情報の領域に前記送信元端末の宛先情報を記載し、前記送信元端末に当該受信パケットを転送する旨の出力用エントリを登録する送信元端末側出力用エントリ登録部と
を更に具備する
ネットワークシステム。
付記3に記載のネットワークシステムであって、
前記コントローラは、
通信開始前のステーション検知の際、宛先端末からのARP応答を基に、前記宛先端末の宛先情報を特定する宛先端末特定部と、
前記宛先端末に、前記固有の識別子としてユーザIDを対応付ける宛先ユーザID割り当て処理部と、
前記宛先端末が接続されたエッジスイッチのフローテーブルに、受信パケットの宛先情報の領域に当該エッジスイッチのノードID及び前記宛先端末のユーザIDが記載されている場合は、当該受信パケットの宛先情報の領域に前記宛先端末の宛先情報を記載し、前記宛先端末に当該受信パケットを転送する旨の出力用エントリを登録する宛先端末側出力用エントリ登録部と
を更に具備する
ネットワークシステム。
付記4に記載のネットワークシステムであって、
前記コントローラは、
通信開始前のステーション検知の際、前記宛先端末からのARP応答を基に、前記送信元端末と前記宛先端末との間の通信が可能であると判断する通信可否判断部と、
前記送信元端末が接続されたエッジスイッチのフローテーブルに、前記宛先端末宛のパケットを受信した場合、当該受信パケットの宛先情報の領域の少なくとも一部に、前記宛先端末が接続されたエッジスイッチのノードID及び前記宛先端末のユーザIDを記載して次段のスイッチに転送する旨の入力用エントリを登録する送信元端末側入力用エントリ登録部と
を更に具備する
ネットワークシステム。
付記4に記載のネットワークシステムであって、
前記コントローラは、
通信が開始された際、前記送信元端末が接続されたエッジスイッチからのパケットの問い合わせを基に、前記送信元端末と前記宛先端末との間の通信が可能であると判断する通信可否判断部と、
前記送信元端末が接続されたエッジスイッチのフローテーブルに、前記宛先端末宛のパケットを受信した場合、当該受信パケットの宛先情報の領域の少なくとも一部に、前記宛先端末が接続されたエッジスイッチのノードIDと前記宛先端末のユーザIDを記載して次段のスイッチに転送する旨の入力用エントリを登録する送信元端末側入力用エントリ登録部と
を更に具備する
ネットワークシステム。
Claims (12)
- 各々が、自身のフローテーブルに登録されたエントリのルールに適合する受信パケットに対し、前記エントリに定義されたアクションに従った動作を行う複数のスイッチと、
前記複数のスイッチによって形成されるネットワークの物理トポロジに応じて計算された経路に固有の識別子をルールとし、所定の出力ポートからの出力をアクションとしたエントリを、複数のスイッチ間において通信が開始される前に、前記各スイッチに登録するコントローラと
を含む
ネットワークシステム。 - 請求項1に記載のネットワークシステムであって、
前記コントローラは、
通信開始前のトポロジ検知の際、ネットワークの物理トポロジを検知し、前記各スイッチをエッジスイッチとコアスイッチとに分類する手段と、
前記エッジスイッチの各々に固有の識別子を割り当てる手段と、
エッジスイッチ間の経路を計算し、コアスイッチのフローテーブルに、受信パケットの宛先情報の領域に所定のエッジスイッチの識別子が記載されている場合は次段のスイッチに当該受信パケットを転送する旨の中継用エントリを登録する手段と
を具備する
ネットワークシステム。 - 請求項2に記載のネットワークシステムであって、
前記コントローラは、
通信開始前のステーション検知の際、前記送信元端末の宛先情報を特定する手段と、
前記送信元端末に、固有の識別子を割り当てる手段と、
前記送信元端末が接続されたエッジスイッチのフローテーブルに、受信パケットの宛先情報の領域に当該エッジスイッチの識別子及び前記送信元端末の識別子が記載されている場合は、当該受信パケットの宛先情報の領域に前記送信元端末の宛先情報を記載し、前記送信元端末に当該受信パケットを転送する旨の出力用エントリを登録する手段と
を更に具備する
ネットワークシステム。 - 請求項3に記載のネットワークシステムであって、
前記コントローラは、
通信開始前のステーション検知の際、前記宛先端末の宛先情報を特定する手段と、
前記宛先端末に、前記固有の識別子として識別子を割り当てる手段と、
前記宛先端末が接続されたエッジスイッチのフローテーブルに、受信パケットの宛先情報の領域に当該エッジスイッチの識別子及び前記宛先端末の識別子が記載されている場合は、当該受信パケットの宛先情報の領域に前記宛先端末の宛先情報を記載し、前記宛先端末に当該受信パケットを転送する旨の出力用エントリを登録する手段と
を更に具備する
ネットワークシステム。 - 請求項4に記載のネットワークシステムであって、
前記コントローラは、
前記送信元端末と前記宛先端末との間の通信が可能であるか確認する手段と、
前記送信元端末と前記宛先端末との間の通信が可能であると判断した場合、前記送信元端末が接続されたエッジスイッチのフローテーブルに、前記宛先端末宛のパケットを受信した場合、当該受信パケットの宛先情報の領域の少なくとも一部に、前記宛先端末が接続されたエッジスイッチの識別子及び前記宛先端末の識別子を記載して次段のスイッチに転送する旨の入力用エントリを登録する手段と
を更に具備する
ネットワークシステム。 - 請求項1乃至5のいずれか一項に記載のネットワークシステムで使用されるコントローラ。
- 複数のスイッチの各々において、自身のフローテーブルに登録されたエントリのルールに適合する受信パケットに対し、前記エントリに定義されたアクションに従った動作を行うことと、
コントローラにおいて、前記複数のスイッチによって形成されるネットワークの物理トポロジに応じて計算された経路に固有の識別子をルールとし、所定の出力ポートからの出力をアクションとしたエントリを、複数のスイッチ間において通信が開始される前に、前記各スイッチに登録することと
を含む
経路制御方法。 - 請求項7に記載の経路制御方法であって、
前記コントローラにおいて、
通信開始前のトポロジ検知の際、ネットワークの物理トポロジを検知し、前記各スイッチをエッジスイッチとコアスイッチとに分類することと、
前記エッジスイッチの各々に固有の識別子を割り当てることと、
エッジスイッチ間の経路を計算し、コアスイッチのフローテーブルに、受信パケットの宛先情報の領域に所定のエッジスイッチの識別子が記載されている場合は次段のスイッチに当該受信パケットを転送する旨の中継用エントリを登録することと
を更に含む
経路制御方法。 - 請求項8に記載の経路制御方法であって、
前記コントローラにおいて、
通信開始前のステーション検知の際、前記送信元端末の宛先情報を特定することと、
前記送信元端末に、固有の識別子を割り当てることと、
前記送信元端末が接続されたエッジスイッチのフローテーブルに、受信パケットの宛先情報の領域に当該エッジスイッチの識別子及び前記送信元端末の識別子が記載されている場合は、当該受信パケットの宛先情報の領域に前記送信元端末の宛先情報を記載し、前記送信元端末に当該受信パケットを転送する旨の出力用エントリを登録することと
を更に含む
経路制御方法。 - 請求項9に記載の経路制御方法であって、
前記コントローラにおいて、
通信開始前のステーション検知の際、前記宛先端末の宛先情報を特定することと、
前記宛先端末に、前記固有の識別子として識別子を割り当てることと、
前記宛先端末が接続されたエッジスイッチのフローテーブルに、受信パケットの宛先情報の領域に当該エッジスイッチの識別子及び前記宛先端末の識別子が記載されている場合は、当該受信パケットの宛先情報の領域に前記宛先端末の宛先情報を記載し、前記宛先端末に当該受信パケットを転送する旨の出力用エントリを登録することと
を更に含む
経路制御方法。 - 請求項10に記載の経路制御方法であって、
前記コントローラにおいて、
前記送信元端末と前記宛先端末との間の通信が可能であるか確認することと、
前記送信元端末と前記宛先端末との間の通信が可能であると判断した場合、前記送信元端末が接続されたエッジスイッチのフローテーブルに、前記宛先端末宛のパケットを受信した場合、当該受信パケットの宛先情報の領域の少なくとも一部に、前記宛先端末が接続されたエッジスイッチの識別子及び前記宛先端末の識別子を記載して次段のスイッチに転送する旨の入力用エントリを登録することと
を更に含む
経路制御方法。 - 請求項7乃至11のいずれか一項に記載の経路制御方法におけるコントローラの動作を計算機に実行させるためのプログラムを格納した記憶媒体。
Priority Applications (12)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201180064890.7A CN103329488B (zh) | 2011-01-13 | 2011-12-27 | 网络系统和路由控制方法 |
US13/995,921 US9787580B2 (en) | 2011-01-13 | 2011-12-27 | Network system and routing method |
KR1020157010902A KR101624474B1 (ko) | 2011-01-13 | 2011-12-27 | 네트워크 시스템 및 경로 제어 방법 |
EP18200176.8A EP3461077A1 (en) | 2011-01-13 | 2011-12-27 | Network system and routing method |
ES11855288T ES2706416T3 (es) | 2011-01-13 | 2011-12-27 | Sistema de red y método de enrutamiento |
JP2012552660A JP5585664B2 (ja) | 2011-01-13 | 2011-12-27 | ネットワークシステム、及び経路制御方法 |
KR1020137018242A KR101574167B1 (ko) | 2011-01-13 | 2011-12-27 | 네트워크 시스템 및 경로 제어 방법 |
KR1020167003508A KR20160021309A (ko) | 2011-01-13 | 2011-12-27 | 네트워크 시스템 및 경로 제어 방법 |
EP11855288.4A EP2665229B1 (en) | 2011-01-13 | 2011-12-27 | Network system and routing method |
RU2013132519/08A RU2576473C2 (ru) | 2011-01-13 | 2011-12-27 | Сетевая система и способ маршрутизации |
US15/724,384 US10819625B2 (en) | 2011-01-13 | 2017-10-04 | Network system and routing method |
US17/066,777 US11552885B2 (en) | 2011-01-13 | 2020-10-09 | Network system and routing method |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2011005137 | 2011-01-13 | ||
JP2011-005137 | 2011-01-31 |
Related Child Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/995,921 A-371-Of-International US9787580B2 (en) | 2011-01-13 | 2011-12-27 | Network system and routing method |
US15/724,384 Continuation US10819625B2 (en) | 2011-01-13 | 2017-10-04 | Network system and routing method |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2012096131A1 true WO2012096131A1 (ja) | 2012-07-19 |
Family
ID=46507042
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2011/080325 WO2012096131A1 (ja) | 2011-01-13 | 2011-12-27 | ネットワークシステム、及び経路制御方法 |
Country Status (9)
Country | Link |
---|---|
US (3) | US9787580B2 (ja) |
EP (2) | EP2665229B1 (ja) |
JP (3) | JP5585664B2 (ja) |
KR (3) | KR101624474B1 (ja) |
CN (2) | CN105262683B (ja) |
ES (1) | ES2706416T3 (ja) |
RU (1) | RU2576473C2 (ja) |
TW (1) | TWI489821B (ja) |
WO (1) | WO2012096131A1 (ja) |
Cited By (16)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102938794A (zh) * | 2012-11-14 | 2013-02-20 | 华为技术有限公司 | 地址解析协议arp消息转发方法、交换机和控制器 |
CN103179046A (zh) * | 2013-04-15 | 2013-06-26 | 昆山天元昌电子有限公司 | 基于openflow的数据中心流量控制方法及系统 |
CN103346922A (zh) * | 2013-07-26 | 2013-10-09 | 电子科技大学 | 基于sdn的确定网络状态的控制器及其确定方法 |
WO2014084216A1 (ja) * | 2012-11-27 | 2014-06-05 | 日本電気株式会社 | 制御装置、通信システム、通信方法及びプログラム |
CN104243319A (zh) * | 2013-06-06 | 2014-12-24 | 杭州华三通信技术有限公司 | 一种邻居发现的方法及装置 |
CN104348727A (zh) * | 2013-08-05 | 2015-02-11 | 杭州华三通信技术有限公司 | OpenFlow网络中的流表表项处理方法及设备 |
JP2015053610A (ja) * | 2013-09-06 | 2015-03-19 | エヌ・ティ・ティ・コミュニケーションズ株式会社 | 接続制御装置、中継装置、接続制御方法、及びプログラム |
WO2015075862A1 (ja) * | 2013-11-20 | 2015-05-28 | 日本電気株式会社 | ネットワーク制御装置、ネットワーク制御方法およびプログラム |
WO2015118811A1 (ja) * | 2014-02-10 | 2015-08-13 | 日本電気株式会社 | 通信システム、パケット転送装置、パケット転送方法およびパケット転送用プログラム |
EP3031179A4 (en) * | 2013-08-07 | 2016-08-03 | Ibm | SWITCH CLUSTER WITH LAYER 3-DISTRIBUTED ROUTER FUNCTIONALITY |
JP2017175522A (ja) * | 2016-03-25 | 2017-09-28 | 日本電気株式会社 | ネットワークシステム、制御装置、方法およびプログラム |
JP2017536761A (ja) * | 2014-12-17 | 2017-12-07 | 華為技術有限公司Huawei Technologies Co.,Ltd. | ソフトウェア定義型ネットワーキングにおけるデータ転送方法、装置、およびシステム |
US10063420B2 (en) | 2013-11-26 | 2018-08-28 | Nec Corporation | Network control apparatus, network system, network control method, and program |
US10305777B2 (en) | 2014-06-30 | 2019-05-28 | Huawei Technologies Co., Ltd. | Flow entry configuration method, apparatus, and system |
US10498669B2 (en) | 2013-08-20 | 2019-12-03 | Nec Corporation | Communication system, switch, controller, ancillary data management apparatus, data forwarding method, and program |
JP2021504983A (ja) * | 2017-11-28 | 2021-02-15 | ホアウェイ・テクノロジーズ・カンパニー・リミテッド | メッセージ転送方法、制御プレーンゲートウェイおよびユーザプレーンゲートウェイ |
Families Citing this family (34)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN103905577A (zh) * | 2012-12-28 | 2014-07-02 | 中兴通讯股份有限公司 | 一种地址解析协议报文的处理方法和系统 |
US8929356B2 (en) * | 2013-02-05 | 2015-01-06 | Anue Systems, Inc. | Mobile user identification and tracking for load balancing in packet processing systems |
US9210074B2 (en) | 2013-05-03 | 2015-12-08 | Alcatel Lucent | Low-cost flow matching in software defined networks without TCAMs |
EP3028401A1 (en) * | 2013-08-01 | 2016-06-08 | Hewlett-Packard Development Company, L.P. | Address resolution rewriting |
CN103458479A (zh) * | 2013-09-17 | 2013-12-18 | 清华大学 | Wsn中基于内容的路由表的数据路由方法及系统 |
US20150098475A1 (en) * | 2013-10-09 | 2015-04-09 | International Business Machines Corporation | Host table management in software defined network (sdn) switch clusters having layer-3 distributed router functionality |
TWI513260B (zh) * | 2013-12-13 | 2015-12-11 | Inventec Corp | 路由控制方法與裝置 |
CN104954281B (zh) * | 2014-03-31 | 2018-08-03 | 中国移动通信集团公司 | 通信方法、系统、资源池管理系统、交换机和控制装置 |
CN105531967B (zh) | 2014-04-21 | 2020-06-16 | 华为技术有限公司 | 一种报文传输方法、设备及通信系统 |
CN105409169B (zh) * | 2014-05-30 | 2019-01-18 | 华为技术有限公司 | 一种多路径转发规则的构造方法、装置及系统 |
JP6395867B2 (ja) * | 2014-06-03 | 2018-09-26 | 華為技術有限公司Huawei Technologies Co.,Ltd. | OpenFlow通信方法及びシステム、制御部、並びにサービスゲートウェイ |
US9774502B2 (en) * | 2014-06-25 | 2017-09-26 | Ciena Corporation | Systems and methods for combined software defined networking and distributed network control |
US9813301B2 (en) * | 2014-08-20 | 2017-11-07 | Nec Corporation | Optimization framework for multi-tenant data centers |
US9876712B2 (en) * | 2014-09-05 | 2018-01-23 | Kt Corporation | Method and device for processing address resolution protocol in software-defined networking environment |
BR112017012218A2 (pt) * | 2014-12-09 | 2017-12-26 | Huawei Tech Co Ltd | método e aparelho para processamento de tabela de fluxo adaptativo |
JP2016116024A (ja) * | 2014-12-12 | 2016-06-23 | 日立金属株式会社 | タグ変換装置 |
CN104639438A (zh) * | 2015-01-05 | 2015-05-20 | 北京交通大学 | 一种OpenFlow网络中数据流的新标识和控制方法 |
JP2016181819A (ja) * | 2015-03-24 | 2016-10-13 | 富士通株式会社 | ネットワークの制御装置及び制御方法、並びに、ネットワークスイッチ |
JP6525256B2 (ja) * | 2015-05-29 | 2019-06-05 | Necプラットフォームズ株式会社 | 仮想ネットワークシステムおよび仮想ネットワーク経路設定方法 |
KR101674177B1 (ko) | 2015-07-07 | 2016-11-09 | 주식회사 케이티 | 멀티노드간 이더넷 가상연결서비스를 제공하는 트랜스포트 sdn 컨트롤러 및 멀티노드간 이더넷 가상연결서비스 제공 방법 |
CN106411746A (zh) * | 2015-08-03 | 2017-02-15 | 上海宽带技术及应用工程研究中心 | 基于Vlan的SDN网络数据传输系统及方法 |
US10003537B2 (en) | 2015-10-01 | 2018-06-19 | Keysight Technologies Singapore (Holding) Pte Ltd | Egress port overload protection for network packet forwarding systems |
JP6701779B2 (ja) * | 2016-02-15 | 2020-05-27 | 株式会社リコー | 通信システム |
KR101870146B1 (ko) * | 2016-10-12 | 2018-06-25 | 아토리서치(주) | 리프-스파인 구조의 소프트웨어 정의 네트워킹에서 목적지 기반 패킷 전송 제어 방법 및 장치 |
KR102342734B1 (ko) * | 2017-04-04 | 2021-12-23 | 삼성전자주식회사 | Sdn 제어 장치 및 이의 데이터 패킷의 전송 룰 설정 방법 |
CN112039772B (zh) * | 2017-06-29 | 2024-04-09 | 华为技术有限公司 | 一种传输路径的确定方法及节点 |
KR102001487B1 (ko) * | 2017-11-22 | 2019-07-17 | 아토리서치(주) | 소프트웨어 정의 네트워킹 제어 방법 및 이를 수행하는 컴퓨팅 장치 |
PL3531622T3 (pl) * | 2018-02-23 | 2020-06-29 | Akademia Górniczo-Hutnicza im. Stanisława Staszica w Krakowie | Sposób obsługi przepływu pakietów w programowalnej sieci komputerowej SDN, produkt programu komputerowego oraz programowalna sieć komputerowa SDN |
CN110460456B (zh) * | 2018-05-08 | 2020-10-20 | 大唐移动通信设备有限公司 | 一种管理信息库mib同步生成网络拓扑的方法及装置 |
CN110838979B (zh) * | 2018-08-17 | 2022-02-08 | 中国电信股份有限公司 | 流量转发控制方法、装置、系统和计算机可读存储介质 |
JP2019092233A (ja) * | 2019-03-26 | 2019-06-13 | Necプラットフォームズ株式会社 | 仮想ネットワークシステムおよび仮想ネットワーク経路設定方法 |
KR102207290B1 (ko) * | 2019-04-12 | 2021-01-25 | 아토리서치(주) | 소프트웨어 정의 네트워크에서 vlan을 지원하는 방법 |
CN112887741A (zh) * | 2021-01-08 | 2021-06-01 | 武汉球之道科技有限公司 | 一种篮球比赛进球视频无线分享系统 |
CN115134299A (zh) * | 2021-03-25 | 2022-09-30 | 华为技术有限公司 | 通信方法及装置 |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2008187686A (ja) * | 2007-01-31 | 2008-08-14 | Nippon Telegr & Teleph Corp <Ntt> | トンネル通信システム、制御装置およびトンネル通信装置 |
JP2009077219A (ja) * | 2007-09-21 | 2009-04-09 | Nec Corp | ネットワークシステム、ネットワーク管理装置、通信装置、パス設定方法及びプログラム |
WO2010110235A1 (ja) * | 2009-03-26 | 2010-09-30 | 日本電気株式会社 | 経路設定サーバ、経路設定方法、及び経路設定プログラム |
JP2011005137A (ja) | 2009-06-29 | 2011-01-13 | Kyoraku Sangyo Kk | 遊技機、認証方法、プログラム |
Family Cites Families (44)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1104687C (zh) | 1996-01-31 | 2003-04-02 | 伊普思龙网络公司 | 传输网络中在包路由选择和包交换之间动态转换的改进方法及设备 |
US6876654B1 (en) * | 1998-04-10 | 2005-04-05 | Intel Corporation | Method and apparatus for multiprotocol switching and routing |
US6526052B1 (en) * | 1998-12-23 | 2003-02-25 | Enterasys Networks, Inc. | Virtual local area networks having rules of precedence |
US7200144B2 (en) * | 2001-10-18 | 2007-04-03 | Qlogic, Corp. | Router and methods using network addresses for virtualization |
US20030156541A1 (en) * | 2002-02-21 | 2003-08-21 | Zheng Haihong | Method and system for reserving resources on an MPLS path |
US8050180B2 (en) | 2003-10-31 | 2011-11-01 | Brocade Communications Systems, Inc. | Network path tracing method |
JP3760167B2 (ja) * | 2004-02-25 | 2006-03-29 | 株式会社日立製作所 | 通信制御装置、通信ネットワークおよびパケット転送制御情報の更新方法 |
JP4332079B2 (ja) * | 2004-07-01 | 2009-09-16 | 株式会社日立製作所 | モジュール型パケット通信ノード装置 |
JP4598462B2 (ja) * | 2004-09-16 | 2010-12-15 | 富士通株式会社 | L2−vpnサービスを提供するプロバイダ網、及びエッジルータ |
US7801125B2 (en) | 2004-10-22 | 2010-09-21 | Cisco Technology, Inc. | Forwarding table reduction and multipath network forwarding |
WO2006049235A1 (ja) * | 2004-11-04 | 2006-05-11 | Matsushita Electric Industrial Co., Ltd. | マルチインタフェース通信装置、端末、および経路切替方法 |
US7827402B2 (en) * | 2004-12-01 | 2010-11-02 | Cisco Technology, Inc. | Method and apparatus for ingress filtering using security group information |
JP4680866B2 (ja) * | 2006-10-31 | 2011-05-11 | 株式会社日立製作所 | ゲートウェイ負荷分散機能を備えたパケット転送装置 |
JP4680942B2 (ja) * | 2007-01-18 | 2011-05-11 | 株式会社日立製作所 | パケット転送装置 |
US20080189769A1 (en) * | 2007-02-01 | 2008-08-07 | Martin Casado | Secure network switching infrastructure |
US20090063438A1 (en) | 2007-08-28 | 2009-03-05 | Iamg, Llc | Regulatory compliance data scraping and processing platform |
EP2582092A3 (en) * | 2007-09-26 | 2013-06-12 | Nicira, Inc. | Network operating system for managing and securing networks |
GB2458154B (en) * | 2008-03-07 | 2012-06-27 | Hewlett Packard Development Co | Routing across a virtual network |
US8146147B2 (en) * | 2008-03-27 | 2012-03-27 | Juniper Networks, Inc. | Combined firewalls |
EP2296788B1 (fr) | 2008-05-16 | 2012-02-29 | Eurecat S.A. | Procede de sulfuration ou presulfuration de particules solides d'un catalyseur ou d'un adsorbant |
JP5242301B2 (ja) * | 2008-09-01 | 2013-07-24 | 株式会社東芝 | メッセージを転送する装置、出力方法および出力プログラム |
US8761152B2 (en) * | 2008-10-14 | 2014-06-24 | William Marsh Rice University | Method and system for scalable ethernet |
JP2010193019A (ja) * | 2009-02-16 | 2010-09-02 | Panasonic Corp | 通信装置及び通信装置の遠隔起動方法 |
WO2010103909A1 (ja) * | 2009-03-09 | 2010-09-16 | 日本電気株式会社 | OpenFlow通信システムおよびOpenFlow通信方法 |
CA3081255C (en) * | 2009-04-01 | 2023-08-22 | Nicira, Inc. | Method and apparatus for implementing and managing virtual switches |
US9497039B2 (en) * | 2009-05-28 | 2016-11-15 | Microsoft Technology Licensing, Llc | Agile data center network architecture |
US9210065B2 (en) * | 2009-06-22 | 2015-12-08 | Alcatel Lucent | Providing cloud-based services using dynamic network virtualization |
US9014184B2 (en) * | 2009-09-24 | 2015-04-21 | Nec Corporation | System and method for identifying communication between virtual servers |
WO2011037105A1 (ja) * | 2009-09-25 | 2011-03-31 | 日本電気株式会社 | コンテンツベーススイッチシステム、及びコンテンツベーススイッチ方法 |
US8369333B2 (en) * | 2009-10-21 | 2013-02-05 | Alcatel Lucent | Method and apparatus for transparent cloud computing with a virtualized network infrastructure |
JP5392137B2 (ja) * | 2010-02-17 | 2014-01-22 | 富士通株式会社 | 通信処理のためのプログラム、コンピュータ及び方法 |
US8571040B2 (en) * | 2010-03-01 | 2013-10-29 | Deutsche Telekom Ag | Apparatus, method, manufacture, and system for providing network services from building blocks |
US8817629B2 (en) * | 2010-03-16 | 2014-08-26 | Deutsche Telekom Ag | Method for routing-assisted traffic monitoring |
US8504718B2 (en) * | 2010-04-28 | 2013-08-06 | Futurewei Technologies, Inc. | System and method for a context layer switch |
US8503307B2 (en) * | 2010-05-10 | 2013-08-06 | Hewlett-Packard Development Company, L.P. | Distributing decision making in a centralized flow routing system |
US8989187B2 (en) * | 2010-06-04 | 2015-03-24 | Coraid, Inc. | Method and system of scaling a cloud computing network |
US8897134B2 (en) * | 2010-06-25 | 2014-11-25 | Telefonaktiebolaget L M Ericsson (Publ) | Notifying a controller of a change to a packet forwarding configuration of a network element over a communication channel |
US8958292B2 (en) * | 2010-07-06 | 2015-02-17 | Nicira, Inc. | Network control apparatus and method with port security controls |
US9680750B2 (en) * | 2010-07-06 | 2017-06-13 | Nicira, Inc. | Use of tunnels to hide network addresses |
CN101917492B (zh) * | 2010-08-06 | 2013-06-05 | 北京乾唐视联网络科技有限公司 | 一种新型网的通信方法及系统 |
US20120099591A1 (en) * | 2010-10-26 | 2012-04-26 | Dell Products, Lp | System and Method for Scalable Flow Aware Network Architecture for Openflow Based Network Virtualization |
US20130188489A1 (en) * | 2010-10-28 | 2013-07-25 | Shihomi Sato | Network system and communication traffic controlling method |
US9001827B2 (en) * | 2010-12-17 | 2015-04-07 | Big Switch Networks, Inc. | Methods for configuring network switches |
US8559335B2 (en) * | 2011-01-07 | 2013-10-15 | Jeda Networks, Inc. | Methods for creating virtual links between fibre channel over ethernet nodes for converged network adapters |
-
2011
- 2011-12-27 EP EP11855288.4A patent/EP2665229B1/en active Active
- 2011-12-27 CN CN201510578941.8A patent/CN105262683B/zh active Active
- 2011-12-27 CN CN201180064890.7A patent/CN103329488B/zh active Active
- 2011-12-27 KR KR1020157010902A patent/KR101624474B1/ko active IP Right Grant
- 2011-12-27 EP EP18200176.8A patent/EP3461077A1/en active Pending
- 2011-12-27 US US13/995,921 patent/US9787580B2/en active Active
- 2011-12-27 KR KR1020137018242A patent/KR101574167B1/ko active IP Right Grant
- 2011-12-27 JP JP2012552660A patent/JP5585664B2/ja active Active
- 2011-12-27 KR KR1020167003508A patent/KR20160021309A/ko not_active Application Discontinuation
- 2011-12-27 RU RU2013132519/08A patent/RU2576473C2/ru active
- 2011-12-27 ES ES11855288T patent/ES2706416T3/es active Active
- 2011-12-27 WO PCT/JP2011/080325 patent/WO2012096131A1/ja active Application Filing
-
2012
- 2012-01-05 TW TW101100466A patent/TWI489821B/zh active
-
2014
- 2014-04-28 JP JP2014092790A patent/JP5594551B2/ja active Active
- 2014-04-28 JP JP2014092791A patent/JP5594552B2/ja active Active
-
2017
- 2017-10-04 US US15/724,384 patent/US10819625B2/en active Active
-
2020
- 2020-10-09 US US17/066,777 patent/US11552885B2/en active Active
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2008187686A (ja) * | 2007-01-31 | 2008-08-14 | Nippon Telegr & Teleph Corp <Ntt> | トンネル通信システム、制御装置およびトンネル通信装置 |
JP2009077219A (ja) * | 2007-09-21 | 2009-04-09 | Nec Corp | ネットワークシステム、ネットワーク管理装置、通信装置、パス設定方法及びプログラム |
WO2010110235A1 (ja) * | 2009-03-26 | 2010-09-30 | 日本電気株式会社 | 経路設定サーバ、経路設定方法、及び経路設定プログラム |
JP2011005137A (ja) | 2009-06-29 | 2011-01-13 | Kyoraku Sangyo Kk | 遊技機、認証方法、プログラム |
Non-Patent Citations (2)
Title |
---|
OPENFLOW SWITCH SPECIFICATION VERSION 1.0.0, 31 December 2009 (2009-12-31) |
See also references of EP2665229A4 |
Cited By (31)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102938794A (zh) * | 2012-11-14 | 2013-02-20 | 华为技术有限公司 | 地址解析协议arp消息转发方法、交换机和控制器 |
US10523629B2 (en) | 2012-11-27 | 2019-12-31 | Nec Corporation | Control apparatus, communication system, communication method, and program |
WO2014084216A1 (ja) * | 2012-11-27 | 2014-06-05 | 日本電気株式会社 | 制御装置、通信システム、通信方法及びプログラム |
JP6024761B2 (ja) * | 2012-11-27 | 2016-11-16 | 日本電気株式会社 | 制御装置、通信システム、通信方法及びプログラム |
US10044671B2 (en) | 2012-11-27 | 2018-08-07 | Nec Corporation | Control apparatus, communication system, communication method, and program |
CN103179046A (zh) * | 2013-04-15 | 2013-06-26 | 昆山天元昌电子有限公司 | 基于openflow的数据中心流量控制方法及系统 |
CN103179046B (zh) * | 2013-04-15 | 2016-03-30 | 昆山天元昌电子有限公司 | 基于openflow的数据中心流量控制方法及系统 |
CN104243319B (zh) * | 2013-06-06 | 2018-01-09 | 新华三技术有限公司 | 一种邻居发现的方法及装置 |
CN104243319A (zh) * | 2013-06-06 | 2014-12-24 | 杭州华三通信技术有限公司 | 一种邻居发现的方法及装置 |
CN103346922B (zh) * | 2013-07-26 | 2016-08-10 | 电子科技大学 | 基于sdn的确定网络状态的控制器及其确定方法 |
CN103346922A (zh) * | 2013-07-26 | 2013-10-09 | 电子科技大学 | 基于sdn的确定网络状态的控制器及其确定方法 |
WO2015018293A1 (en) * | 2013-08-05 | 2015-02-12 | Hangzhou H3C Technologies Co., Ltd. | Flow table entry in software defined networking |
CN104348727A (zh) * | 2013-08-05 | 2015-02-11 | 杭州华三通信技术有限公司 | OpenFlow网络中的流表表项处理方法及设备 |
US9426060B2 (en) | 2013-08-07 | 2016-08-23 | International Business Machines Corporation | Software defined network (SDN) switch clusters having layer-3 distributed router functionality |
EP3031179A4 (en) * | 2013-08-07 | 2016-08-03 | Ibm | SWITCH CLUSTER WITH LAYER 3-DISTRIBUTED ROUTER FUNCTIONALITY |
US10182005B2 (en) | 2013-08-07 | 2019-01-15 | International Business Machines Corporation | Software defined network (SDN) switch clusters having layer-3 distributed router functionality |
US10498669B2 (en) | 2013-08-20 | 2019-12-03 | Nec Corporation | Communication system, switch, controller, ancillary data management apparatus, data forwarding method, and program |
JP2015053610A (ja) * | 2013-09-06 | 2015-03-19 | エヌ・ティ・ティ・コミュニケーションズ株式会社 | 接続制御装置、中継装置、接続制御方法、及びプログラム |
CN105745878A (zh) * | 2013-11-20 | 2016-07-06 | 日本电气株式会社 | 网络控制设备、网络控制方法以及程序 |
JPWO2015075862A1 (ja) * | 2013-11-20 | 2017-03-16 | 日本電気株式会社 | ネットワーク制御装置、ネットワーク制御方法およびプログラム |
US10021015B2 (en) | 2013-11-20 | 2018-07-10 | Nec Corporation | Network control device, network control method, and storage medium |
WO2015075862A1 (ja) * | 2013-11-20 | 2015-05-28 | 日本電気株式会社 | ネットワーク制御装置、ネットワーク制御方法およびプログラム |
US10063420B2 (en) | 2013-11-26 | 2018-08-28 | Nec Corporation | Network control apparatus, network system, network control method, and program |
WO2015118811A1 (ja) * | 2014-02-10 | 2015-08-13 | 日本電気株式会社 | 通信システム、パケット転送装置、パケット転送方法およびパケット転送用プログラム |
US10305777B2 (en) | 2014-06-30 | 2019-05-28 | Huawei Technologies Co., Ltd. | Flow entry configuration method, apparatus, and system |
US10659342B2 (en) | 2014-06-30 | 2020-05-19 | Huawei Technologies Co., Ltd. | Flow entry configuration method, apparatus, and system |
US10263889B2 (en) | 2014-12-17 | 2019-04-16 | Huawei Technologies Co., Ltd. | Data forwarding method, device, and system in software-defined networking |
JP2017536761A (ja) * | 2014-12-17 | 2017-12-07 | 華為技術有限公司Huawei Technologies Co.,Ltd. | ソフトウェア定義型ネットワーキングにおけるデータ転送方法、装置、およびシステム |
JP2017175522A (ja) * | 2016-03-25 | 2017-09-28 | 日本電気株式会社 | ネットワークシステム、制御装置、方法およびプログラム |
JP2021504983A (ja) * | 2017-11-28 | 2021-02-15 | ホアウェイ・テクノロジーズ・カンパニー・リミテッド | メッセージ転送方法、制御プレーンゲートウェイおよびユーザプレーンゲートウェイ |
JP7065034B2 (ja) | 2017-11-28 | 2022-05-11 | ホアウェイ・テクノロジーズ・カンパニー・リミテッド | メッセージ転送方法、制御プレーンゲートウェイおよびユーザプレーンゲートウェイ |
Also Published As
Publication number | Publication date |
---|---|
TWI489821B (zh) | 2015-06-21 |
JP5594552B2 (ja) | 2014-09-24 |
US10819625B2 (en) | 2020-10-27 |
CN105262683A (zh) | 2016-01-20 |
US20130279371A1 (en) | 2013-10-24 |
JP5594551B2 (ja) | 2014-09-24 |
KR101624474B1 (ko) | 2016-05-26 |
US9787580B2 (en) | 2017-10-10 |
EP2665229A4 (en) | 2016-12-07 |
EP3461077A1 (en) | 2019-03-27 |
RU2576473C2 (ru) | 2016-03-10 |
CN103329488B (zh) | 2016-05-04 |
CN105262683B (zh) | 2021-03-30 |
US20210029027A1 (en) | 2021-01-28 |
KR20160021309A (ko) | 2016-02-24 |
JP2014168286A (ja) | 2014-09-11 |
EP2665229B1 (en) | 2018-10-17 |
JPWO2012096131A1 (ja) | 2014-06-09 |
US11552885B2 (en) | 2023-01-10 |
KR101574167B1 (ko) | 2015-12-03 |
CN103329488A (zh) | 2013-09-25 |
JP2014168285A (ja) | 2014-09-11 |
JP5585664B2 (ja) | 2014-09-10 |
KR20150054006A (ko) | 2015-05-19 |
ES2706416T3 (es) | 2019-03-28 |
TW201246843A (en) | 2012-11-16 |
RU2013132519A (ru) | 2015-02-20 |
US20180041429A1 (en) | 2018-02-08 |
EP2665229A1 (en) | 2013-11-20 |
KR20130121921A (ko) | 2013-11-06 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
JP5594551B2 (ja) | ネットワークシステム、及び経路制御方法 | |
JP5610247B2 (ja) | ネットワークシステム、及びポリシー経路設定方法 | |
RU2583745C2 (ru) | Сетевая система, коммутатор и способ обнаружения подсоединенного терминала | |
US9548933B2 (en) | Network system, switch, and methods of network configuration | |
KR101579014B1 (ko) | 부하 저감 시스템, 및 부하 저감 방법 | |
JP5682846B2 (ja) | ネットワークシステム、パケット処理方法、及び記憶媒体 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
WWE | Wipo information: entry into national phase |
Ref document number: 201180064890.7 Country of ref document: CN |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 11855288 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 2012552660 Country of ref document: JP Kind code of ref document: A |
|
WWE | Wipo information: entry into national phase |
Ref document number: 13995921 Country of ref document: US |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2011855288 Country of ref document: EP |
|
ENP | Entry into the national phase |
Ref document number: 20137018242 Country of ref document: KR Kind code of ref document: A |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
ENP | Entry into the national phase |
Ref document number: 2013132519 Country of ref document: RU Kind code of ref document: A |