[go: up one dir, main page]

WO2013152496A1 - 接收信息的方法、发送信息的方法及装置 - Google Patents

接收信息的方法、发送信息的方法及装置 Download PDF

Info

Publication number
WO2013152496A1
WO2013152496A1 PCT/CN2012/073937 CN2012073937W WO2013152496A1 WO 2013152496 A1 WO2013152496 A1 WO 2013152496A1 CN 2012073937 W CN2012073937 W CN 2012073937W WO 2013152496 A1 WO2013152496 A1 WO 2013152496A1
Authority
WO
WIPO (PCT)
Prior art keywords
plane device
information
forwarding path
network
packet forwarding
Prior art date
Application number
PCT/CN2012/073937
Other languages
English (en)
French (fr)
Inventor
夏寅贲
董雯霞
朱明明
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to PCT/CN2012/073937 priority Critical patent/WO2013152496A1/zh
Priority to CN201280000301.3A priority patent/CN103493439B/zh
Priority to EP12873946.3A priority patent/EP2824875B1/en
Priority to JP2015503727A priority patent/JP5978384B2/ja
Publication of WO2013152496A1 publication Critical patent/WO2013152496A1/zh
Priority to US14/488,956 priority patent/US9749215B2/en

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4604—LAN interconnection over a backbone network, e.g. Internet, Frame Relay
    • H04L12/462—LAN interconnection over a bridge based backbone
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0695—Management of faults, events, alarms or notifications the faulty arrangement being the maintenance, administration or management system
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/12—Discovery or management of network topologies
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/34—Signalling channels for network management communication
    • H04L41/342—Signalling channels for network management communication between virtual entities, e.g. orchestrators, SDN or NFV entities
    • 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/02—Topology update or discovery
    • 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/02—Topology update or discovery
    • H04L45/028—Dynamic adaptation of the update intervals, e.g. event-triggered updates
    • 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

Definitions

  • the present invention relates to network technologies, and in particular, to a method of receiving information, a method and apparatus for transmitting information.
  • Background Art With the development of network technologies, a network architecture of control and forwarding classification has emerged, such as OpenFlow.
  • the network architecture of the control and forwarding separate network architecture includes two types of network devices, namely a forwarding plane device and a control plane device.
  • the forwarding plane device processes the received packet according to the flow table, and the control plane device controls the forwarding device through the control channel.
  • control and forwarding separation in the network architecture in which control and forwarding are separated means that the forwarding plane device is separated from the control plane device.
  • the forwarding surface device transfers some or all of the functions of the control plane to the control plane device.
  • the forwarding plane device has the ability to communicate with the control plane device.
  • the forwarding surface device is capable of communicating with the control plane device via the control channel.
  • Embodiments of the present invention provide a method for receiving information, a method for transmitting information, and a device, which can solve the problem that when a control plane device cannot perform jurisdiction on a forwarding plane device, the forwarding plane device needs to actively acquire information for calculating a packet forwarding path. technical problem.
  • an embodiment of the present invention provides a method for receiving information, including:
  • the forwarding plane device When the control plane device is capable of governing the forwarding plane device, the forwarding plane device receives information sent by the control plane device for calculating a packet forwarding path, and the forwarding plane device and the control plane device are located in control and forwarding A network of separate network architectures.
  • an embodiment of the present invention provides a method for sending information, including: When the control plane device is capable of governing the forwarding plane device, the control plane device transmits information for calculating a packet forwarding path to the forwarding plane device, the forwarding plane device and the control plane device being located in control and forwarding separation Network architecture network.
  • an embodiment of the present invention provides an apparatus for receiving information, including a triggering unit and a receiving unit, where the triggering unit is configured to trigger the receiving unit to receive when the control plane device can administer the forwarding plane device.
  • the receiving unit is configured to receive the information used to calculate a packet forwarding path, where the forwarding plane device and the control plane device are located in a network that controls a separate network architecture.
  • an embodiment of the present invention provides an apparatus for transmitting information, including a triggering unit and a sending unit: the triggering unit is configured to trigger the sending unit to be triggered when the control plane device can perform jurisdiction on the forwarding plane device.
  • Transmitting plane means transmitting information for calculating a packet forwarding path;
  • the sending unit is configured to send the information used to calculate a packet forwarding path, where the forwarding plane device and the control plane device are located in a network of a network architecture that separates and forwards the control.
  • the control plane device when the control plane device is capable of governing the forwarding plane device, information for calculating the packet forwarding path is transmitted to the forwarding plane device. Therefore, with the technical solution provided by the embodiment of the present invention, the forwarding plane device does not need to actively acquire information for calculating the packet forwarding path before calculating the packet forwarding path based on the information used to calculate the packet forwarding path.
  • FIG. 1 is a flowchart of a method for receiving information according to an embodiment of the present invention
  • FIG. 2 is a flowchart of a method for sending information according to an embodiment of the present invention
  • FIG. 3 is a schematic structural diagram of an apparatus for receiving information according to an embodiment of the present invention.
  • FIG. 4 is a schematic structural diagram of an apparatus for transmitting information according to an embodiment of the present invention.
  • the technical solutions in the embodiments of the present invention are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present invention. It is obvious that the described embodiments are some embodiments of the present invention, but not all embodiments. . Base All other embodiments obtained by those skilled in the art without creative efforts are within the scope of the present invention.
  • Embodiments of the present invention relate to a network architecture that separates control from forwarding.
  • the "control and forwarding separation" in the network architecture separated from control and forwarding means that the forwarding plane device is separated from the control plane device.
  • the forwarding surface device transfers some or all of the functions of the control plane to the control plane device.
  • the forwarding plane device has the ability to communicate with the control plane device.
  • the forwarding surface device is capable of communicating with the control plane device via the control channel.
  • the control plane device is a device that conforms to a network architecture in which control and forwarding are separated.
  • the forwarding plane device of the present invention is a device that conforms to the network architecture of control and forwarding classification.
  • the forwarding plane device processes the received packet according to the flow table.
  • the control surface device controls the forwarding surface device through the control channel.
  • the forwarding plane device when forwarding a packet, can forward the Layer 2 packet or forward the Layer 3 packet.
  • OSI model Open Systems Interconnection model
  • the forwarding plane device When the forwarding plane device is specifically implemented, it may be a switch or a router.
  • the forwarding plane device may be an OpenFlow Switch (OpenFlow Switch).
  • OpenFlow Switch For an OpenFlow switch, refer to the Open Networking Foundation (ONF) of the Standard Setting Organization (SSO). ) Released OpenFlow Switch Specification 1.0 (OpenFlow Switch Specification 1.0).
  • control plane device When the control plane device is specifically implemented, it may be an OpenFlow Controller.
  • OpenFlow Controller For open flow controllers, please refer to the OpenFlow Switch Specification Version 1.0 released by ONF.
  • control channel When the control channel is implemented, it may be a secure channel for the OpenFlow switch to interact with the OpenFlow controller.
  • the forwarding plane device can have two forwarding modes, one is a stream forwarding mode, and the other is a packet forwarding mode.
  • Flow forwarding means that the forwarding plane device forwards the packet according to the flow table.
  • the number of fields used to determine whether a packet matches the entry of the flow table in one entry of the flow table is two or more.
  • the number of fields in an entry of the flow table used to determine whether the packet matches the entry of the flow table may be five.
  • the five fields can be the source Internet Protocol (IP) address, the destination IP address, the source port (Port), the destination port, and the protocol.
  • IP Internet Protocol
  • Port source port
  • the protocol is used to determine whether the packet matches the entry of the flow table.
  • the field may be in the field of the Data Link layer of the OSI model or in the field of the IP layer of the OSI model.
  • Packet forwarding means that the forwarding plane device forwards the packet according to the packet forwarding table. Used in an entry in the packet forwarding table The number of fields that determine whether the packet matches the entry of the packet forwarding table is one.
  • the field in the packet forwarding table used to determine whether the packet matches the entry of the flow table may be a destination IP address or a destination media access control (MAC) protocol address.
  • MAC media access control
  • the packet forwarding table can be a MAC table or a routing table.
  • the OpenFlow switch can generate a MAC table according to the source MAC protocol address in the received message and the interface for receiving the message. After the MAC table is generated, the OpenFlow switch can forward packets according to the MAC table.
  • FIG. 1 is a flowchart of a method for receiving information according to an embodiment of the present invention. Referring to Figure 1, the method includes:
  • the forwarding plane device receives information sent by the control plane device for calculating a packet forwarding path, where the forwarding plane device and the control plane device are located in a control A network with a separate network architecture for forwarding.
  • control surface device is capable of governing the transfer surface device means that the control surface device can communicate with the transfer surface device through the control channel.
  • the control plane device when the control plane device is capable of governing the forwarding plane device, information for calculating the packet forwarding path is transmitted to the forwarding plane device. Therefore, with the technical solution provided by the embodiment of the present invention, the forwarding plane device does not need to actively acquire information for calculating the packet forwarding path before calculating the packet forwarding path based on the information used to calculate the packet forwarding path.
  • the forwarding plane device may calculate the packet forwarding path according to the information used to calculate the packet forwarding path.
  • the forwarding plane device can calculate the packet forwarding path according to the Spanning Tree Protocol (STP).
  • STP Spanning Tree Protocol
  • the forwarding plane device can also be based on the intermediate system to the intermediate system (Intermediate System to
  • the Intermediate System, IS-IS protocol calculates the packet forwarding path.
  • the algorithm used to calculate the forwarding path may be a Bellman-Ford algorithm, a Dijkstra algorithm, a Floyd-Warshall algorithm, or a Johnson algorithm.
  • the packet forwarding path may be represented by the following information: an identifier of the root bridge, an identifier of the root interface, and an identifier of the specified interface.
  • the algorithm used to calculate the forwarding path may be a Shortest Path First (SPF) algorithm.
  • SPF Shortest Path First
  • Receiving, by the forwarding plane device, the information used by the control plane device to calculate a packet forwarding path includes: the forwarding plane device receiving the information used to calculate a packet forwarding path, where the information used to calculate a packet forwarding path Obtained by:
  • the control plane device obtains topology information of the network
  • the control plane device generates the information for calculating a packet forwarding path based on topology information of the network.
  • the topology information of the network includes which interface of any two network elements in the network with any direct connection relationship and which interface of another network element is connected to another network element.
  • the control plane device obtains topology information of the network by running an extended Link Layer Discovery Protocol (LLDP).
  • LLDP extended Link Layer Discovery Protocol
  • the OpenFlow controller establishes a transport control protocol with the managed OpenFlow switch (Transfer)
  • the OpenFlow controller After the connection, the OpenFlow controller knows the interface that the managed OpenFlow switch has. The OpenFlow controller sends the extended LLDP message to the managed OpenFlow switch.
  • the extended LLDP message carries the identity of the managed OpenFlow switch and the identity of the interface of the managed OpenFlow switch.
  • the OpenFlow controller sends multiple extended LLDP messages to the governed OpenFlow switch.
  • the plurality of extended LLDP messages are in one-to-one correspondence with the plurality of interfaces.
  • Each extended LLDP message of the multiple extended LLDP messages carries an interface identifier of the corresponding interface.
  • the managed OpenFlow switch After receiving the extended LLDP message, the managed OpenFlow switch forwards the extended LLDP message corresponding to the interface to the neighbor OpenFlow switch through the interface of the managed OpenFlow switch.
  • the neighboring OpenFlow switch receives the extended LLDP message, the identifier of the neighbor OpenFlow switch is added to the extended LLDP message to generate a new extended LLDP message.
  • the neighbor OpenFlow switch sends the new extended LLDP message to the OpenFlow controller through the control channel.
  • the OpenFlow controller can obtain, according to the new extended LLDP message, which interface the OpenFlow switch connects with the neighbor OpenFlow switch.
  • the OpenFlow controller can further obtain which interface the neighbor OpenFlow switch connects with the neighbor OpenFlow switch of the neighbor OpenFlow switch.
  • the OpenFlow controller can obtain topology information of the network under its jurisdiction.
  • the information used to calculate the packet forwarding path includes an identifier of the root bridge.
  • the identity of the root bridge can be obtained by running STP.
  • the value of the MAC address of the root bridge is smaller than other OpenFlow switches that are under the jurisdiction of the same OpenFlow controller.
  • the value of the MAC protocol address is smaller than other OpenFlow switches that are under the jurisdiction of the same OpenFlow controller.
  • the OpenFlow controller can obtain the identity of the root bridge by running STP.
  • the OpenFlow switch can obtain the link cost by running STP.
  • the OpenFlow switch can obtain the identifier of the root interface, the identifier of the non-root non-designated interface, and the identifier of the specified interface by running STP according to the identifier of the root bridge and the cost of the link.
  • the information used to calculate the packet forwarding path may further include a Root Path Cost.
  • the OpenFlow switch After the OpenFlow switch establishes a TCP connection with the OpenFlow controller, the OpenFlow switch sends the bandwidth of each interface of the OpenFlow switch to the OpenFlow controller through the OpenFlow protocol.
  • OpenFlow protocol see the OpenFlow Switch Specification Version 1.0 released by ONF.
  • the OpenFlow controller can get the interface overhead based on the bandwidth of the interface.
  • the OpenFlow switch is directly connected to the neighbor OpenFlow switch through the first interface of the OpenFlow switch.
  • the bandwidth of the first interface is equal to the overhead of the direct link of the OpenFlow switch to the neighbor OpenFlow switch.
  • the OpenFlow controller can calculate the cost of multiple links separately, thus obtaining multiple root path costs.
  • the overhead of the link from the open flow switch to the root bridge is the root path cost.
  • the OpenFlow controller can obtain the identity of the root bridge by running STP.
  • the OpenFlow switch can obtain the identity of the root interface, the identifier of the specified interface, and the identifier of the non-root non-designated interface.
  • the OpenFlow network can determine which interface or interfaces of the OpenFlow switches having multiple interfaces have a loop according to the root bridge and the topology information of the network.
  • the OpenFlow network can determine which interface or interfaces are root interfaces or non-root non-designated interfaces based on the overhead of the link from the root bridge to the OpenFlow switch.
  • Receiving, by the forwarding plane device, the information used by the control plane device to calculate a packet forwarding path includes: the forwarding plane device receiving the information used to calculate a packet forwarding path, where the information used to calculate a packet forwarding path Obtained by: The control plane device obtains topology information of the network, and the topology information of the network is the information used to calculate a packet forwarding path.
  • control plane device can obtain topology information of the network by using extended LLDP.
  • extended LLDP extended LLDP
  • the information for calculating a packet forwarding path includes a link state database (Link State Database,
  • the information for calculating the forwarding path may be stored in the forwarding plane device.
  • the forwarding plane device calculates a forwarding path based on the information used to calculate the forwarding path.
  • control plane device cannot administer the forwarding plane device.
  • the control plane device may be faulty, or the link between the control plane device and the forwarding plane device may be faulty.
  • FIG. 2 is a flowchart of a method for transmitting information according to an embodiment of the present invention. Referring to Figure 2, the method includes:
  • control plane device When the control plane device is capable of governing the forwarding plane device, the control plane device sends information for calculating a packet forwarding path to the forwarding plane device, where the forwarding plane device and the control plane device are located in a control and A network that forwards separate network architectures.
  • control surface device is capable of governing the transfer surface device means that the control surface device can communicate with the transfer surface device through the control channel.
  • the control plane device when the control plane device is capable of governing the forwarding plane device, information for calculating the packet forwarding path is transmitted to the forwarding plane device. Therefore, with the technical solution provided by the embodiment of the present invention, the forwarding plane device does not need to actively acquire information for calculating the packet forwarding path before calculating the packet forwarding path based on the information used to calculate the packet forwarding path.
  • the forwarding plane device may calculate the packet forwarding path according to the information used to calculate the packet forwarding path.
  • the forwarding plane device can calculate the packet forwarding path according to the STP.
  • the forwarding plane device can also calculate the packet forwarding path according to the IS-IS protocol.
  • the algorithm used to calculate the forwarding path may be a Bellman-Ford algorithm, a Dijkstra algorithm, a Floyd-Warshall algorithm, or a Johnson algorithm.
  • the packet forwarding path may be represented by the following information: an identifier of the root bridge, an identifier of the root interface, and an identifier of the designated interface.
  • the algorithm used to calculate the forwarding path may be the SPF algorithm.
  • the method includes:
  • the control plane device obtains topology information of the network
  • the control plane device generates the information for calculating a packet forwarding path based on topology information of the network.
  • the topology information of the network includes which interface of any two network elements in the network with any direct connection relationship and which interface of another network element is connected to another network element.
  • the control plane device obtains topology information of the network by running extended LLDP.
  • the OpenFlow controller can know the interface that the managed OpenFlow switch has.
  • the OpenFlow controller sends the extended LLDP message to the managed OpenFlow switch.
  • the extended LLDP message carries the identity of the managed OpenFlow switch and the identity of the interface of the managed OpenFlow switch.
  • the OpenFlow controller sends multiple extended LLDP messages to the governed OpenFlow switch.
  • the plurality of extended LLDP messages are in one-to-one correspondence with the plurality of interfaces.
  • Each extended LLDP message of the multiple extended LLDP messages carries an interface identifier of the corresponding interface.
  • the managed OpenFlow switch After receiving the extended LLDP message, the managed OpenFlow switch forwards the extended LLDP message corresponding to the interface to the neighbor OpenFlow switch through the interface of the managed OpenFlow switch.
  • the neighboring OpenFlow switch receives the extended LLDP message, the identifier of the neighbor OpenFlow switch is added to the extended LLDP message to generate a new extended LLDP message.
  • the neighbor OpenFlow switch sends the new extended LLDP message to the OpenFlow controller through the control channel.
  • the OpenFlow controller can obtain, according to the new extended LLDP message, which interface the OpenFlow switch connects with the neighbor OpenFlow switch.
  • the OpenFlow controller can further obtain which interface the neighbor OpenFlow switch connects with the neighbor OpenFlow switch of the neighbor OpenFlow switch.
  • the OpenFlow controller can obtain topology information of the network under its jurisdiction.
  • the information used to calculate the packet forwarding path includes an identifier of the root bridge.
  • the identity of the root bridge can be obtained by running STP. It can be understood by those skilled in the art that in the scenario where the priority of the OpenFlow switch is equal, the value of the MAC protocol address of the root bridge is smaller than the value of the MAC protocol address of other OpenFlow switches governed by the same OpenFlow controller.
  • the OpenFlow controller can obtain the identity of the root bridge by running STP.
  • the OpenFlow switch can obtain the link cost by running STP.
  • the OpenFlow switch can obtain the identifier of the root interface, the identifier of the non-root non-designated interface, and the identifier of the specified interface by running STP according to the identifier of the root bridge and the cost of the link.
  • the information used to calculate the packet forwarding path may also include a root path cost.
  • the OpenFlow switch After the OpenFlow switch establishes a TCP connection with the OpenFlow controller, the OpenFlow switch sends the bandwidth of each interface of the OpenFlow switch to the OpenFlow controller through the OpenFlow protocol.
  • OpenFlow protocol see the OpenFlow Switch Specification Version 1.0 released by ONF.
  • the OpenFlow controller can get the interface overhead based on the bandwidth of the interface.
  • the OpenFlow switch is directly connected to the neighbor OpenFlow switch through the first interface of the OpenFlow switch.
  • the bandwidth of the first interface is equal to the overhead of the direct link of the OpenFlow switch to the neighbor OpenFlow switch.
  • the OpenFlow controller can calculate the cost of multiple links separately, thus obtaining multiple root path costs.
  • the overhead of the link from the open flow switch to the root bridge is the root path cost.
  • the OpenFlow controller can obtain the identity of the root bridge by running STP.
  • the OpenFlow switch can obtain the identity of the root interface, the identifier of the specified interface, and the identifier of the non-root non-designated interface.
  • the OpenFlow network can determine which interface or interfaces of the OpenFlow switches having multiple interfaces have a loop according to the root bridge and the topology information of the network.
  • the OpenFlow network can determine which interface or interfaces are root interfaces or non-root non-designated interfaces based on the overhead of the link from the root bridge to the OpenFlow switch.
  • the method includes:
  • the control plane device obtains topology information of the network, and the topology information of the network is the information used to calculate a packet forwarding path.
  • control plane device can obtain topology information of the network by using extended LLDP.
  • extended LLDP extended LLDP
  • the information used to calculate the packet forwarding path includes an LSDB.
  • the forwarding plane device calculates a forwarding path based on the information used to calculate the forwarding path.
  • control plane device cannot administer the forwarding plane device.
  • the control plane device may be faulty, or the link between the control plane device and the forwarding plane device may be faulty.
  • FIG. 3 is a schematic structural diagram of an apparatus for receiving information according to an embodiment of the present invention.
  • the apparatus shown in Fig. 3 can be realized by the method shown in Fig. 1.
  • the device is a forwarding surface device.
  • the device includes a trigger unit 301 and a receiving unit 302;
  • the triggering unit 301 is configured to trigger, when the control plane device can administer the forwarding plane device, the receiving unit 302 to receive information used by the control plane device to calculate a packet forwarding path.
  • the receiving unit 302 is configured to receive the information used to calculate a packet forwarding path, where the forwarding plane device and the control plane device are located in a network that controls a separate network architecture.
  • control surface device is capable of governing the transfer surface device means that the control surface device can communicate with the transfer surface device through the control channel.
  • the control plane device when the control plane device is capable of governing the forwarding plane device, information for calculating the packet forwarding path is transmitted to the forwarding plane device. Therefore, with the technical solution provided by the embodiment of the present invention, the forwarding plane device does not need to actively acquire information for calculating the packet forwarding path before calculating the packet forwarding path based on the information used to calculate the packet forwarding path.
  • the apparatus may further include a calculating unit configured to calculate a packet forwarding path according to the information used by the receiving unit 302 to calculate a packet forwarding path.
  • the forwarding plane device can calculate the packet forwarding path according to the STP.
  • the forwarding plane device can also calculate the packet forwarding path according to the IS-IS protocol.
  • the OpenFlow switch calculates a forwarding path according to STP
  • the calculation for calculating the forwarding path The method can be a Bellman-Ford algorithm, a Dijkstra algorithm, a Floyd-Warshall algorithm, or a Johnson algorithm.
  • the forwarding plane device calculates the packet forwarding path according to the STP
  • the packet forwarding path may be represented by the following information: an identifier of the root bridge, an identifier of the root interface, and an identifier of the designated interface.
  • the algorithm used to calculate the forwarding path may be the SPF algorithm.
  • the receiving unit 302 is configured to receive the information used to calculate a packet forwarding path, where the information used to calculate a packet forwarding path is obtained by:
  • the control plane device obtains topology information of the network
  • the control plane device generates the information for calculating a packet forwarding path based on topology information of the network.
  • the topology information of the network includes which interface of any two network elements in the network with any direct connection relationship and which interface of another network element is connected to another network element.
  • the control plane device obtains topology information of the network by running extended LLDP.
  • the OpenFlow controller can know the interface that the managed OpenFlow switch has.
  • the OpenFlow controller sends the extended LLDP message to the managed OpenFlow switch.
  • the extended LLDP message carries the identity of the managed OpenFlow switch and the identity of the interface of the managed OpenFlow switch.
  • the OpenFlow controller sends multiple extended LLDP messages to the governed OpenFlow switch.
  • the plurality of extended LLDP messages are in one-to-one correspondence with the plurality of interfaces.
  • Each extended LLDP message of the multiple extended LLDP messages carries an interface identifier of the corresponding interface.
  • the managed OpenFlow switch After receiving the extended LLDP message, the managed OpenFlow switch forwards the extended LLDP message corresponding to the interface to the neighbor OpenFlow switch through the interface of the managed OpenFlow switch.
  • the neighboring OpenFlow switch receives the extended LLDP message, the identifier of the neighbor OpenFlow switch is added to the extended LLDP message to generate a new extended LLDP message.
  • the neighbor OpenFlow switch sends the new extended LLDP message to the OpenFlow controller through the control channel.
  • the OpenFlow controller can obtain, according to the new extended LLDP message, which interface the OpenFlow switch connects with the neighbor OpenFlow switch.
  • the OpenFlow controller can further obtain which interface the neighbor OpenFlow switch connects with the neighbor OpenFlow switch of the neighbor OpenFlow switch.
  • the OpenFlow controller can obtain topology information of the network under its jurisdiction.
  • the information used to calculate the packet forwarding path includes an identifier of the root bridge.
  • the identity of the root bridge can be obtained by running STP.
  • the value of the MAC address of the root bridge is smaller than the value of the MAC protocol address of other OpenFlow switches under the same OpenFlow controller.
  • the OpenFlow controller can obtain the identity of the root bridge by running STP.
  • the OpenFlow switch can obtain the link cost by running STP.
  • the OpenFlow switch can obtain the identifier of the root interface, the identifier of the non-root non-designated interface, and the identifier of the specified interface by running STP according to the identifier of the root bridge and the cost of the link.
  • the information used to calculate the packet forwarding path may also include a root path cost.
  • the OpenFlow switch After the OpenFlow switch establishes a TCP connection with the OpenFlow controller, the OpenFlow switch sends the bandwidth of each interface of the OpenFlow switch to the OpenFlow controller through the OpenFlow protocol.
  • OpenFlow protocol see the OpenFlow Switch Specification Version 1.0 released by ONF.
  • the OpenFlow controller can get the interface overhead based on the bandwidth of the interface.
  • the OpenFlow switch is directly connected to the neighbor OpenFlow switch through the first interface of the OpenFlow switch.
  • the bandwidth of the first interface is equal to the overhead of the direct link of the OpenFlow switch to the neighbor OpenFlow switch.
  • the OpenFlow controller can calculate the cost of multiple links separately, thus obtaining multiple root path costs.
  • the overhead of the link from the open flow switch to the root bridge is the root path cost.
  • the OpenFlow controller can obtain the identity of the root bridge by running STP.
  • the OpenFlow switch can obtain the identity of the root interface, the identifier of the specified interface, and the identifier of the non-root non-designated interface.
  • the OpenFlow network can determine which interface or interfaces of the OpenFlow switches having multiple interfaces have a loop according to the root bridge and the topology information of the network.
  • the OpenFlow network can determine which interface or interfaces are root interfaces or non-root non-designated interfaces based on the overhead of the link from the root bridge to the OpenFlow switch.
  • the process of determining whether the interface of the OpenFlow switch is a root interface, a designated interface, or a non-root non-designated interface belongs to a process of calculating a packet forwarding path.
  • the receiving unit 302 is configured to receive the information used to calculate a packet forwarding path, where the information used to calculate a packet forwarding path is obtained by:
  • the control plane device obtains topology information of the network, and the topology information of the network is the information used to calculate a packet forwarding path.
  • control plane device can obtain topology information of the network by using extended LLDP.
  • extended LLDP extended LLDP
  • the information used to calculate the packet forwarding path includes an LSDB.
  • the apparatus may include a storage unit for storing the information for calculating a forwarding path.
  • the calculating unit is configured to calculate a forwarding path according to the information used to calculate the forwarding path when the control plane device is unable to perform the jurisdiction on the forwarding plane device.
  • control plane device cannot administer the forwarding plane device.
  • the control plane device may be faulty, or the link between the control plane device and the forwarding plane device may be faulty.
  • FIG. 4 is a schematic structural diagram of an apparatus for transmitting information according to an embodiment of the present invention.
  • the apparatus shown in Fig. 4 can be realized by the method shown in Fig. 2.
  • the device is a control surface device.
  • the apparatus includes a trigger unit 401 and a transmitting unit 402:
  • the triggering unit 401 is configured to trigger the sending unit 402 to send information for calculating a packet forwarding path to the forwarding plane device when the control plane device can administer the forwarding plane device;
  • the sending unit 402 is configured to send the information used to calculate a packet forwarding path, where the forwarding plane device and the control plane device are located in a network that controls a separate network architecture.
  • control surface device is capable of governing the transfer surface device means that the control surface device can communicate with the transfer surface device through the control channel.
  • the control plane device when the control plane device is capable of governing the forwarding plane device, information for calculating the packet forwarding path is transmitted to the forwarding plane device. Therefore, with the technical solution provided by the embodiment of the present invention, the forwarding plane device does not need to actively acquire information for calculating the packet forwarding path before calculating the packet forwarding path based on the information used to calculate the packet forwarding path.
  • the forwarding plane device may calculate the packet forwarding path according to the information used to calculate the packet forwarding path. For example, the forwarding plane device can calculate the packet forwarding path according to the STP. The forwarding plane device can also calculate the packet forwarding path according to the IS-IS protocol.
  • the algorithm used to calculate the forwarding path may be a Bellman-Ford algorithm, a Dijkstra algorithm, a Floyd-Warshall algorithm, or a Johnson algorithm.
  • the packet forwarding path may be represented by the following information: an identifier of the root bridge, an identifier of the root interface, and an identifier of the specified interface.
  • the algorithm used to calculate the forwarding path may be the SPF algorithm.
  • the device may further include:
  • a first generating unit configured to: before the sending unit 402 sends the information used to calculate a packet forwarding path, obtain topology information of the network; generate, according to topology information of the network, the used to calculate a packet forwarding path. information.
  • the topology information of the network includes which interface of any two network elements in the network with any direct connection relationship and which interface of another network element is connected to another network element.
  • the control plane device obtains topology information of the network by running extended LLDP.
  • the OpenFlow controller can know the interface that the managed OpenFlow switch has.
  • the OpenFlow controller sends the extended LLDP message to the managed OpenFlow switch.
  • the extended LLDP message carries the identity of the managed OpenFlow switch and the identity of the interface of the managed OpenFlow switch.
  • the OpenFlow controller sends multiple extended LLDP messages to the governed OpenFlow switch.
  • the plurality of extended LLDP messages are in one-to-one correspondence with the plurality of interfaces.
  • Each extended LLDP message of the multiple extended LLDP messages carries an interface identifier of the corresponding interface.
  • the managed OpenFlow switch After receiving the extended LLDP message, the managed OpenFlow switch forwards the extended LLDP message corresponding to the interface to the neighbor OpenFlow switch through the interface of the managed OpenFlow switch.
  • the neighboring OpenFlow switch receives the extended LLDP message, the identifier of the neighbor OpenFlow switch is added to the extended LLDP message to generate a new extended LLDP message.
  • the neighbor OpenFlow switch sends the new extended LLDP message to the OpenFlow controller through the control channel.
  • the OpenFlow controller can obtain, according to the new extended LLDP message, which interface the OpenFlow switch connects with the neighbor OpenFlow switch.
  • the OpenFlow controller can further obtain which of the neighbor OpenFlow switches passes.
  • the interface is connected to the neighbor OpenFlow switch of the neighbor OpenFlow switch.
  • the OpenFlow controller can obtain topology information of the network under its jurisdiction.
  • the information used to calculate the packet forwarding path includes an identifier of the root bridge.
  • the identity of the root bridge can be obtained by running STP.
  • the value of the MAC address of the root bridge is smaller than the value of the MAC protocol address of other OpenFlow switches under the same OpenFlow controller.
  • the OpenFlow controller can obtain the identity of the root bridge by running STP.
  • the OpenFlow switch can obtain the link cost by running STP.
  • the OpenFlow switch can obtain the identifier of the root interface, the identifier of the non-root non-designated interface, and the identifier of the specified interface by running STP according to the identifier of the root bridge and the cost of the link.
  • the information used to calculate the packet forwarding path may also include a root path cost.
  • the OpenFlow switch After the OpenFlow switch establishes a TCP connection with the OpenFlow controller, the OpenFlow switch sends the bandwidth of each interface of the OpenFlow switch to the OpenFlow controller through the OpenFlow protocol.
  • OpenFlow protocol see the OpenFlow Switch Specification Version 1.0 released by ONF.
  • the OpenFlow controller can get the interface overhead based on the bandwidth of the interface.
  • the OpenFlow switch is directly connected to the neighbor OpenFlow switch through the first interface of the OpenFlow switch.
  • the bandwidth of the first interface is equal to the overhead of the direct link of the OpenFlow switch to the neighbor OpenFlow switch.
  • the OpenFlow controller can calculate the cost of multiple links separately, thus obtaining multiple root path costs.
  • the overhead of the link from the open flow switch to the root bridge is the root path cost.
  • the OpenFlow controller can obtain the identity of the root bridge by running STP.
  • the OpenFlow switch can obtain the identity of the root interface, the identifier of the specified interface, and the identifier of the non-root non-designated interface.
  • the OpenFlow network can determine which is based on the overhead of the link from the root bridge to the OpenFlow switch. Which interfaces are root interfaces or non-root non-designated interfaces.
  • a second generating unit configured to obtain, by the sending unit 402, the topology information of the network before sending the information used for calculating a packet forwarding path, where the topology information of the network is the information used to calculate a packet forwarding path .
  • control plane device can obtain topology information of the network by using extended LLDP.
  • extended LLDP extended LLDP
  • the information used to calculate the packet forwarding path includes an LSDB.
  • the forwarding plane device calculates a forwarding path based on the information used to calculate the forwarding path.
  • control plane device cannot administer the forwarding plane device.
  • the control plane device may be faulty, or the link between the control plane device and the forwarding plane device may be faulty.
  • the disclosed systems, devices, and methods may be implemented in other ways.
  • the device embodiments described above are only schematic.
  • the division of the unit may be only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined. Either can be integrated into another system, or some features can be ignored, or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units.
  • the present embodiment can be implemented by selecting some or all of the units according to actual needs. The purpose of the program.
  • each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the functions, if implemented in the form of software functional units and sold or used as separate products, may be stored in a computer readable storage medium.
  • the technical solution of the present invention which is essential or contributes to the prior art, or a part of the technical solution, may be embodied in the form of a software product, which is stored in a storage medium, including
  • the instructions are used to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present invention.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read only memory (abbreviated as ROM in English, a full name of Read-Only Memory in English), a random access memory (abbreviated as RAM in English, a full name called Random Access Memory in English), and a disk. Or a variety of media such as optical discs that can store program code.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

一种接收信息的方法、发送信息的方法及装置。所述接收信息的方法包括：当控制面装置能够对转发面装置进行管辖时，转发面装置接收控制面装置发送的用于计算包转发路径的信息，转发面装置和控制面装置位于控制与转发分离的网络架构的网络。通过本发明实施例提供的技术方案，转发面装置基于用于计算包转发路径的信息计算包转发路径前不需要主动获取用于计算包转发路径的信息。

Description

接收信息的方法、 发送信息的方法及装置
技术领域 本发明涉及网络技术， 特别涉及接收信息的方法、 发送信息的方法及装置。 背景技术 随着网络技术的发展， 出现了控制与转发分类的网络架构， 例如开放流 (OpenFlow)。
控制与转发分离的网络架构的网络中包含两种类型的网络设备，即转发面装置以 及控制面装置。其中， 转发面装置根据流表对收到的报文进行处理， 控制面装置通过 控制通道对转发面装置进行管辖。
控制与转发分离的网络架构中的 "控制与转发分离"是指转发面装置与控制面装 置分离。其中， 转发面装置将控制面的部分或者全部功能转移到控制面装置。转发面 装置具备与控制面装置进行通信的能力。转发面装置能够通过控制通道与控制面装置 通信。
当控制面装置发生故障， 或者控制面装置与转发面装置之间的链路发生故障时， 控制面装置不能对转发面装置进行管辖。 当控制面装置不能对转发面装置进行管辖 时，转发面装置需要主动获取用于计算包转发路径的信息。这使得转发面装置基于用 于计算包转发路径的信息计算包转发路径前需要主动获取用于计算包转发路径的信 息。 发明内容 本发明实施例提供了接收信息的方法、发送信息的方法及装置， 能够解决当控制 面装置不能对转发面装置进行管辖时，转发面装置需要主动获取用于计算包转发路径 的信息的技术问题。
一方面， 本发明实施例提供了一种接收信息的方法， 包括：
当控制面装置能够对转发面装置进行管辖时，所述转发面装置接收所述控制面装 置发送的用于计算包转发路径的信息，所述转发面装置和所述控制面装置位于控制与 转发分离的网络架构的网络。
另一方面， 本发明实施例提供了一种发送信息的方法， 包括： 当控制面装置能够对转发面装置进行管辖时，所述控制面装置向所述转发面装置 发送用于计算包转发路径的信息，所述转发面装置和所述控制面装置位于控制与转发 分离的网络架构的网络。
又一方面，本发明实施例提供了一种接收信息的装置，包括触发单元和接收单元; 所述触发单元，用于当控制面装置能够对转发面装置进行管辖时，触发所述接收 单元接收所述控制面装置发送的用于计算包转发路径的信息；
所述接收单元，用于接收所述用于计算包转发路径的信息，所述转发面装置和所 述控制面装置位于控制与转发分离的网络架构的网络。
再一方面，本发明实施例提供了一种发送信息的装置，包括触发单元和发送单元: 所述触发单元，用于当控制面装置能够对转发面装置进行管辖时，触发所述发送 单元向所述转发面装置发送用于计算包转发路径的信息；
所述发送单元，用于发送所述用于计算包转发路径的信息，所述转发面装置和所 述控制面装置位于控制与转发分离的网络架构的网络。
从上述技术方案可以看出， 控制面装置能够对转发面装置进行管辖时， 将用于计 算包转发路径的信息发送至转发面装置。 因此， 通过本发明实施例提供的技术方案， 转发面装置基于用于计算包转发路径的信息计算包转发路径前不需要主动获取用于 计算包转发路径的信息。 附图说明
为了更清楚地说明本发明实施例或现有技术中的技术方案，下面将对实施例或现 有技术描述中所需要使用的附图作简单地介绍， 显而易见地， 下面描述中的附图仅仅 是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动性的前 提下， 还可以根据这些附图获得其他的附图。
图 1为本发明实施例提供的接收信息的方法的流程图；
图 2为本发明实施例提供的发送信息的方法的流程图；
图 3为本发明实施例提供的接收信息的装置的结构示意图；
图 4为本发明实施例提供的发送信息的装置的结构示意图。 具体实施方式 下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完 整地描述， 显然， 所描述的实施例是本发明一部分实施例， 而不是全部的实施例。 基 于本发明中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所 有其他实施例， 都属于本发明保护的范围。
本发明实施例涉及到控制与转发分离的网络架构。控制与转发分离的网络架构中 的 "控制与转发分离"是指转发面装置与控制面装置分离。 其中， 转发面装置将控制 面的部分或者全部功能转移到控制面装置。转发面装置具备与控制面装置进行通信的 能力。 转发面装置能够通过控制通道与控制面装置通信。
本发明涉及的控制面装置为符合控制与转发分离的网络架构的装置。本发明涉及 的转发面装置为符合控制与转发分类的网络架构的装置。其中，转发面装置根据流表 对收到的报文进行处理。 控制面装置通过控制通道对转发面装置进行控制。
举例来说， 转发面装置对报文进行转发时， 可以对二层的报文进行转发， 也可以 对三层的报文进行转发。 关于二层与三层， 具体请参考开放系统互连模型 （Open Systems Interconnection model， OSI model )。
转发面装置具体实现时， 可以是交换机或者路由器。
在转发面装置是交换机的场景下， 转发面装置具体可以是开放流交换机 ( OpenFlow Switch )„ 关于开放流交换机， 请参考标准制定组织 （Standard Setting Organization, SSO)开放网络基础（Open Networking Foundation, ONF)发布的《开 放流交换机规范》 版本 1.0 (OpenFlow Switch Specification 1.0)。
控制面装置具体实现时， 可以是开放流控制器（OpenFlow Controller )。关于开放 流控制器， 请参考 ONF发布的 《开放流交换机规范》 版本 1.0。
控制通道具体实现时，可以是开放流交换机与开放流控制器进行交互的安全通道
( Secure Channel 关于安全通道， 具体请参考 O F发布的 《开放流交换机规范》 版本 1.0。
转发面装置可以具有两种转发模式， 一种是流转发模式， 另一种是包转发模式。 流转发是指转发面装置根据流表对报文进行转发。流表的一个表项中用于判断报 文是否与流表的表项匹配的字段的个数为 2个或者 2个以上。举例来说，流表的一个 表项中用于判断报文是否与流表的表项匹配的字段的个数可以是 5个。 5个字段可以 分别是源网际协议 （Internet Protocol, IP) 地址、 目的 IP地址、 源端口 （Port)、 目 的端口以及协议（Protocol 举例来说， 用于判断报文是否与流表的表项匹配的字段 可以是处于 OSI model的数据链路 （Data Link) 层的字段， 也可以是处于 OSI model 的 IP层的字段。
包转发是指转发面装置根据包转发表对报文进行转发。包转发表的一个表项中用 于判断报文是否与包转发表的表项匹配的字段的个数为 1个。举例来说，包转发表的 表项中用于判断报文是否与流表的表项匹配的字段可以目的 IP地址， 也可以是目的 媒体访问控制 （Media Access Control, MAC) 协议地址。 本领域的技术人员可以理 解， 包转发表可以是 MAC表， 也可以是路由表。
本领域的技术人员可以理解， 开放流交换机可以根据接收到的报文中的源 MAC 协议地址以及用于接收报文的接口生成 MAC表。 MAC表生成后， 开放流交换机可 以根据 MAC表进行包转发。
图 1为本发明一个实施例提供的接收信息的方法的流程图。 参见图 1， 所述方法 包括：
101、 当控制面装置能够对转发面装置进行管辖时， 所述转发面装置接收所述控 制面装置发送的用于计算包转发路径的信息，所述转发面装置和所述控制面装置位于 控制与转发分离的网络架构的网络。
控制面装置能够对转发面装置进行管辖是指控制面装置能够通过控制通道与转 发面装置进行通信。
从上述技术方案可以看出，控制面装置能够对转发面装置进行管辖时，将用于计 算包转发路径的信息发送至转发面装置。 因此， 通过本发明实施例提供的技术方案， 转发面装置基于用于计算包转发路径的信息计算包转发路径前不需要主动获取用于 计算包转发路径的信息。
可选的，
转发面装置接收到所述用于计算包转发路径的信息后，可以根据所述用于计算包 转发路径的信息计算包转发路径。
举例来说， 转发面装置可以根据生成树协议 （Spanning Tree Protocol, STP) 计 算包转发路径。 转发面装置也可以根据中间系统到中间系统 （Intermediate System to
Intermediate System, IS-IS) 协议计算包转发路径。
举例来说， 当开放流交换机根据 STP计算转发路径时， 用于计算转发路径的算 法可以是 Bellman-Ford算法、 Dijkstra算法、 Floyd- Warshall算法或者 Johnson算法。 当转发面装置根据 STP计算包转发路径时， 所述包转发路径可以用如下信息表示： 根桥的标识、 根接口的标识以及指定接口的标识。
举例来说， 当开放流交换机根据 IS-IS协议计算转发路径时， 用于计算转发路径 的算法可以是最短路径优先 （Shortest Path First, SPF) 算法。
可选的， 所述转发面装置接收所述控制面装置发送的用于计算包转发路径的信息包括： 所述转发面装置接收所述用于计算包转发路径的信息，所述用于计算包转发路径 的信息通过如下途径获得：
所述控制面装置获得所述网络的拓扑信息；
所述控制面装置基于所述网络的拓扑信息生成所述用于计算包转发路径的信息。 网络的拓扑信息包括网络中任意两个具有直连关系的网元中的一个网元通过哪 个接口及另一个网元的哪个接口连接到另一个网元。举例来说，所述控制面装置通过 运行扩展的链路层发现协议（Link Layer Discovery Protocol, LLDP)获得所述网络的 拓扑信息。
举例来说， 开放流控制器与被管辖的开放流交换机建立传输控制协议 （Transfer
Control Protocol, TCP) 连接后， 开放流控制器能够知道被管辖的开放流交换机具有 的接口。开放流控制器向被管辖的开放流交换机发送扩展的 LLDP消息。扩展的 LLDP 消息中携带被管辖的开放流交换机的标识以及被管辖的开放流交换机的接口的标识。
当被管辖的开放流交换机具有多个接口时，开放流控制器向被管辖的开放流交换 机发送多个扩展的 LLDP消息。多个扩展的 LLDP消息与上述多个接口是一一对应的。 所述多个扩展的 LLDP消息中每个扩展的 LLDP消息中携带了对应接口的接口标识。 被管辖的开放流交换机收到扩展的 LLDP 消息后， 通过被管辖的开放流交换机的接 口，将与接口对应的扩展的 LLDP消息转发至邻居开放流交换机。邻居开放流交换机 收到扩展的 LLDP消息后，在扩展的 LLDP消息中添加所述邻居开放流交换机的标识， 从而生成新的扩展的 LLDP消息。所述邻居开放流交换机通过控制通道将所述新的扩 展的 LLDP消息发送到开放流控制器。
通过上述机制，开放流控制器能够根据所述新的扩展的 LLDP消息得到所述开放 流交换机通过哪个接口和所述邻居开放流交换机进行连接。
基于同样的机制，开放流控制器能够进一步得到所述邻居开放流交换机通过哪个 接口和所述邻居开放流交换机的邻居开放流交换机进行连接。
通过重复上述操作， 开放流控制器能够得到所管辖的网络的拓扑信息。
可选的，
所述用于计算包转发路径的信息包括根桥的标识。
举例来说， 开放流控制器得到所管辖的网络的拓扑信息后， 通过运行 STP可以 得到根桥的标识。本领域的技术人员可以理解，在开放流交换机的优先级相等的场景 下， 根桥的 MAC协议地址的数值小于受同一开放流控制器管辖的其他开放流交换机 的 MAC协议地址的数值。
举例来说， 开放流控制器得到所管辖的网络的拓扑信息后可以通过运行 STP得 到根桥的标识。所述开放流交换机接收到所述开放流控制器发送的根桥的标识后，可 以通过运行 STP得到链路的开销 （Cost)。 所述开放流交换机可以根据根桥的标识以 及链路的开销， 通过运行 STP得到根接口的标识、 非根非指定接口的标识以及指定 接口的标识。
可选的，
所述用于计算包转发路径的信息还可以包括根路径开销 （Root Path Cost)。
举例来说，
开放流交换机与开放流控制器建立 TCP连接后，开放流交换机通过 OpenFlow协 议将开放流交换机的每个接口的带宽发送至开放流控制器。 关于 OpenFlow协议， 请 参见 ONF发布的《开放流交换机规范》版本 1.0。 开放流控制器能够根据接口的带宽 得到接口的开销。开放流交换机通过开放流交换机的第一接口与邻居开放流交换机直 连。 第一接口的带宽等于开放流交换机至邻居开放流交换机的直连链路的开销。
当开放流交换机与根桥没有直连关系，并且开放流交换机与根桥之间存在多条链 路时， 开放流控制器可以分别计算多条链路的开销， 从而得到多个根路径开销。 开放 流交换机到根桥的链路的开销为根路径开销。
举例来说， 开放流控制器得到所管辖的网络的拓扑信息后可以通过运行 STP得 到根桥的标识。开放流交换机接收到开放流控制器发送的根桥的标识以及根路径开销 后， 可以通过运行 STP得到根接口的标识、 指定接口的标识以及非根非指定接口的 标识。
本领域的技术人员可以理解， 开放流网络运行 STP后， 能够根据根桥以及网络 的拓扑信息确定具有多个接口的开放流交换机中的哪个或者哪些接口是否存在环路。 当存在环路时，开放流网络能够根据从根桥到开放流交换机的链路的开销确定哪个或 者哪些接口为根接口或者非根非指定接口。
本领域的技术人员可以理解，确定开放流交换机的接口是否为根接口、指定接口 或者非根非指定接口的过程属于计算包转发路径的过程。
可选的，
所述转发面装置接收所述控制面装置发送的用于计算包转发路径的信息包括： 所述转发面装置接收所述用于计算包转发路径的信息，所述用于计算包转发路径 的信息通过如下途径获得： 所述控制面装置获得所述网络的拓扑信息，所述网络的拓扑信息为所述用于计算 包转发路径的信息。
举例来说， 所述控制面装置可以通过扩展的 LLDP获得所述网络的拓扑信息。 可选的，
所述用于计算包转发路径的信息包括链路状态数据库 （Link State Database,
LSDB)0
可选的，
所述用于计算转发路径的信息可以存储在所述转发面装置。
可选的，
当所述控制面装置不能对所述转发面装置进行管辖时，所述转发面装置根据所述 用于计算转发路径的信息计算转发路径。
举例来说，所述控制面装置不能对所述转发面装置进行管辖可以是所述控制面装 置发生故障， 也可以是所述控制面装置与所述转发面装置之间的链路发送故障。
图 2为本发明一个实施例提供的发送信息的方法的流程图。 参见图 2， 所述方法 包括：
201、 当控制面装置能够对转发面装置进行管辖时， 所述控制面装置向所述转发 面装置发送用于计算包转发路径的信息，所述转发面装置和所述控制面装置位于控制 与转发分离的网络架构的网络。
控制面装置能够对转发面装置进行管辖是指控制面装置能够通过控制通道与转 发面装置进行通信。
从上述技术方案可以看出，控制面装置能够对转发面装置进行管辖时，将用于计 算包转发路径的信息发送至转发面装置。 因此， 通过本发明实施例提供的技术方案， 转发面装置基于用于计算包转发路径的信息计算包转发路径前不需要主动获取用于 计算包转发路径的信息。
可选的，
转发面装置接收到所述用于计算包转发路径的信息后，可以根据所述用于计算包 转发路径的信息计算包转发路径。
举例来说， 转发面装置可以根据 STP计算包转发路径。 转发面装置也可以根据 IS-IS协议计算包转发路径。
举例来说， 当开放流交换机根据 STP计算转发路径时， 用于计算转发路径的算 法可以是 Bellman-Ford算法、 Dijkstra算法、 Floyd- Warshall算法或者 Johnson算法。 当转发面装置根据 STP计算包转发路径时， 所述包转发路径可以用如下信息表示： 根桥的标识、 根接口的标识以及指定接口的标识。
举例来说， 当开放流交换机根据 IS-IS协议计算转发路径时， 用于计算转发路径 的算法可以是 SPF算法。
可选的，
所述控制面装置向所述转发面装置发送用于计算包转发路径的信息之前，所述方 法包括：
所述控制面装置获得所述网络的拓扑信息；
所述控制面装置基于所述网络的拓扑信息生成所述用于计算包转发路径的信息。 网络的拓扑信息包括网络中任意两个具有直连关系的网元中的一个网元通过哪 个接口及另一个网元的哪个接口连接到另一个网元。举例来说，所述控制面装置通过 运行扩展的 LLDP获得所述网络的拓扑信息。
举例来说， 开放流控制器与被管辖的开放流交换机建立 TCP连接后， 开放流控 制器能够知道被管辖的开放流交换机具有的接口。开放流控制器向被管辖的开放流交 换机发送扩展的 LLDP消息。扩展的 LLDP消息中携带被管辖的开放流交换机的标识 以及被管辖的开放流交换机的接口的标识。
当被管辖的开放流交换机具有多个接口时，开放流控制器向被管辖的开放流交换 机发送多个扩展的 LLDP消息。多个扩展的 LLDP消息与上述多个接口是一一对应的。 所述多个扩展的 LLDP消息中每个扩展的 LLDP消息中携带了对应接口的接口标识。 被管辖的开放流交换机收到扩展的 LLDP 消息后， 通过被管辖的开放流交换机的接 口，将与接口对应的扩展的 LLDP消息转发至邻居开放流交换机。邻居开放流交换机 收到扩展的 LLDP消息后，在扩展的 LLDP消息中添加所述邻居开放流交换机的标识， 从而生成新的扩展的 LLDP消息。所述邻居开放流交换机通过控制通道将所述新的扩 展的 LLDP消息发送到开放流控制器。
通过上述机制，开放流控制器能够根据所述新的扩展的 LLDP消息得到所述开放 流交换机通过哪个接口和所述邻居开放流交换机进行连接。
基于同样的机制，开放流控制器能够进一步得到所述邻居开放流交换机通过哪个 接口和所述邻居开放流交换机的邻居开放流交换机进行连接。
通过重复上述操作， 开放流控制器能够得到所管辖的网络的拓扑信息。
可选的，
所述用于计算包转发路径的信息包括根桥的标识。 举例来说， 开放流控制器得到所管辖的网络的拓扑信息后， 通过运行 STP可以 得到根桥的标识。本领域的技术人员可以理解，在开放流交换机的优先级相等的场景 下， 根桥的 MAC协议地址的数值小于受同一开放流控制器管辖的其他开放流交换机 的 MAC协议地址的数值。
举例来说， 开放流控制器得到所管辖的网络的拓扑信息后可以通过运行 STP得 到根桥的标识。所述开放流交换机接收到所述开放流控制器发送的根桥的标识后，可 以通过运行 STP得到链路的开销。 所述开放流交换机可以根据根桥的标识以及链路 的开销， 通过运行 STP得到根接口的标识、 非根非指定接口的标识以及指定接口的 标识。
可选的，
所述用于计算包转发路径的信息还可以包括根路径开销。
举例来说，
开放流交换机与开放流控制器建立 TCP连接后，开放流交换机通过 OpenFlow协 议将开放流交换机的每个接口的带宽发送至开放流控制器。 关于 OpenFlow协议， 请 参见 ONF发布的《开放流交换机规范》版本 1.0。 开放流控制器能够根据接口的带宽 得到接口的开销。开放流交换机通过开放流交换机的第一接口与邻居开放流交换机直 连。 第一接口的带宽等于开放流交换机至邻居开放流交换机的直连链路的开销。
当开放流交换机与根桥没有直连关系，并且开放流交换机与根桥之间存在多条链 路时， 开放流控制器可以分别计算多条链路的开销， 从而得到多个根路径开销。 开放 流交换机到根桥的链路的开销为根路径开销。
举例来说， 开放流控制器得到所管辖的网络的拓扑信息后可以通过运行 STP得 到根桥的标识。开放流交换机接收到开放流控制器发送的根桥的标识以及根路径开销 后， 可以通过运行 STP得到根接口的标识、 指定接口的标识以及非根非指定接口的 标识。
本领域的技术人员可以理解， 开放流网络运行 STP后， 能够根据根桥以及网络 的拓扑信息确定具有多个接口的开放流交换机中的哪个或者哪些接口是否存在环路。 当存在环路时，开放流网络能够根据从根桥到开放流交换机的链路的开销确定哪个或 者哪些接口为根接口或者非根非指定接口。
本领域的技术人员可以理解，确定开放流交换机的接口是否为根接口、指定接口 或者非根非指定接口的过程属于计算包转发路径的过程。
可选的， 所述控制面装置向所述转发面装置发送用于计算包转发路径的信息之前，所述方 法包括：
所述控制面装置获得所述网络的拓扑信息，所述网络的拓扑信息为所述用于计算 包转发路径的信息。
举例来说， 所述控制面装置可以通过扩展的 LLDP获得所述网络的拓扑信息。 可选的
所述用于计算包转发路径的信息包括 LSDB。
可选的，
当所述控制面装置不能对所述转发面装置进行管辖时，所述转发面装置根据所述 用于计算转发路径的信息计算转发路径。
举例来说，所述控制面装置不能对所述转发面装置进行管辖可以是所述控制面装 置发生故障， 也可以是所述控制面装置与所述转发面装置之间的链路发送故障。
图 3为本发明一个实施例提供的接收信息的装置的结构示意图。图 3所示的装置 可以通过图 1所示的方法实现。 所述装置为转发面装置。 参见图 3， 所述装置包括触 发单元 301和接收单元 302;
所述触发单元 301， 用于当控制面装置能够对转发面装置进行管辖时， 触发所述 接收单元 302接收所述控制面装置发送的用于计算包转发路径的信息；
所述接收单元 302， 用于接收所述用于计算包转发路径的信息， 所述转发面装置 和所述控制面装置位于控制与转发分离的网络架构的网络。
控制面装置能够对转发面装置进行管辖是指控制面装置能够通过控制通道与转 发面装置进行通信。
从上述技术方案可以看出，控制面装置能够对转发面装置进行管辖时，将用于计 算包转发路径的信息发送至转发面装置。 因此， 通过本发明实施例提供的技术方案， 转发面装置基于用于计算包转发路径的信息计算包转发路径前不需要主动获取用于 计算包转发路径的信息。
可选的，
所述装置还可以包括计算单元，用于根据所述接收单元 302接收的所述用于计算 包转发路径的信息计算包转发路径。
举例来说， 转发面装置可以根据 STP计算包转发路径。 转发面装置也可以根据 IS-IS协议计算包转发路径。
举例来说， 当开放流交换机根据 STP计算转发路径时， 用于计算转发路径的算 法可以是 Bellman-Ford算法、 Dijkstra算法、 Floyd- Warshall算法或者 Johnson算法。 当转发面装置根据 STP计算包转发路径时， 所述包转发路径可以用如下信息表示： 根桥的标识、 根接口的标识以及指定接口的标识。
举例来说， 当开放流交换机根据 IS-IS协议计算转发路径时， 用于计算转发路径 的算法可以是 SPF算法。
可选的，
所述接收单元 302用于接收所述用于计算包转发路径的信息，所述用于计算包转 发路径的信息通过如下途径获得：
所述控制面装置获得所述网络的拓扑信息；
所述控制面装置基于所述网络的拓扑信息生成所述用于计算包转发路径的信息。 网络的拓扑信息包括网络中任意两个具有直连关系的网元中的一个网元通过哪 个接口及另一个网元的哪个接口连接到另一个网元。举例来说，所述控制面装置通过 运行扩展的 LLDP获得所述网络的拓扑信息。
举例来说， 开放流控制器与被管辖的开放流交换机建立 TCP连接后， 开放流控 制器能够知道被管辖的开放流交换机具有的接口。开放流控制器向被管辖的开放流交 换机发送扩展的 LLDP消息。扩展的 LLDP消息中携带被管辖的开放流交换机的标识 以及被管辖的开放流交换机的接口的标识。
当被管辖的开放流交换机具有多个接口时，开放流控制器向被管辖的开放流交换 机发送多个扩展的 LLDP消息。多个扩展的 LLDP消息与上述多个接口是一一对应的。 所述多个扩展的 LLDP消息中每个扩展的 LLDP消息中携带了对应接口的接口标识。 被管辖的开放流交换机收到扩展的 LLDP 消息后， 通过被管辖的开放流交换机的接 口，将与接口对应的扩展的 LLDP消息转发至邻居开放流交换机。邻居开放流交换机 收到扩展的 LLDP消息后，在扩展的 LLDP消息中添加所述邻居开放流交换机的标识， 从而生成新的扩展的 LLDP消息。所述邻居开放流交换机通过控制通道将所述新的扩 展的 LLDP消息发送到开放流控制器。
通过上述机制，开放流控制器能够根据所述新的扩展的 LLDP消息得到所述开放 流交换机通过哪个接口和所述邻居开放流交换机进行连接。
基于同样的机制，开放流控制器能够进一步得到所述邻居开放流交换机通过哪个 接口和所述邻居开放流交换机的邻居开放流交换机进行连接。
通过重复上述操作， 开放流控制器能够得到所管辖的网络的拓扑信息。
可选的， 所述用于计算包转发路径的信息包括根桥的标识。
举例来说， 开放流控制器得到所管辖的网络的拓扑信息后， 通过运行 STP可以 得到根桥的标识。本领域的技术人员可以理解，在开放流交换机的优先级相等的场景 下， 根桥的 MAC协议地址的数值小于受同一开放流控制器管辖的其他开放流交换机 的 MAC协议地址的数值。
举例来说， 开放流控制器得到所管辖的网络的拓扑信息后可以通过运行 STP得 到根桥的标识。所述开放流交换机接收到所述开放流控制器发送的根桥的标识后，可 以通过运行 STP得到链路的开销。 所述开放流交换机可以根据根桥的标识以及链路 的开销， 通过运行 STP得到根接口的标识、 非根非指定接口的标识以及指定接口的 标识。
可选的，
所述用于计算包转发路径的信息还可以包括根路径开销。
举例来说，
开放流交换机与开放流控制器建立 TCP连接后，开放流交换机通过 OpenFlow协 议将开放流交换机的每个接口的带宽发送至开放流控制器。 关于 OpenFlow协议， 请 参见 ONF发布的《开放流交换机规范》版本 1.0。 开放流控制器能够根据接口的带宽 得到接口的开销。开放流交换机通过开放流交换机的第一接口与邻居开放流交换机直 连。 第一接口的带宽等于开放流交换机至邻居开放流交换机的直连链路的开销。
当开放流交换机与根桥没有直连关系，并且开放流交换机与根桥之间存在多条链 路时， 开放流控制器可以分别计算多条链路的开销， 从而得到多个根路径开销。 开放 流交换机到根桥的链路的开销为根路径开销。
举例来说， 开放流控制器得到所管辖的网络的拓扑信息后可以通过运行 STP得 到根桥的标识。开放流交换机接收到开放流控制器发送的根桥的标识以及根路径开销 后， 可以通过运行 STP得到根接口的标识、 指定接口的标识以及非根非指定接口的 标识。
本领域的技术人员可以理解， 开放流网络运行 STP后， 能够根据根桥以及网络 的拓扑信息确定具有多个接口的开放流交换机中的哪个或者哪些接口是否存在环路。 当存在环路时，开放流网络能够根据从根桥到开放流交换机的链路的开销确定哪个或 者哪些接口为根接口或者非根非指定接口。
本领域的技术人员可以理解，确定开放流交换机的接口是否为根接口、指定接口 或者非根非指定接口的过程属于计算包转发路径的过程。 可选的，
所述接收单元 302用于接收所述用于计算包转发路径的信息，所述用于计算包转 发路径的信息通过如下途径获得：
所述控制面装置获得所述网络的拓扑信息，所述网络的拓扑信息为所述用于计算 包转发路径的信息。
举例来说， 所述控制面装置可以通过扩展的 LLDP获得所述网络的拓扑信息。 可选的，
所述用于计算包转发路径的信息包括 LSDB。
可选的，
所述装置可以包括存储单元， 用于存储所述用于计算转发路径的信息。
可选的，
所述计算单元用于当所述控制面装置不能对所述转发面装置进行管辖时，根据所 述用于计算转发路径的信息计算转发路径。
举例来说，所述控制面装置不能对所述转发面装置进行管辖可以是所述控制面装 置发生故障， 也可以是所述控制面装置与所述转发面装置之间的链路发送故障。
图 4为本发明一个实施例提供的发送信息的装置的结构示意图。图 4所示的装置 可以通过图 2所示的方法实现。 所述装置为控制面装置。 参见图 4， 所述装置包括触 发单元 401和发送单元 402:
所述触发单元 401， 用于当控制面装置能够对转发面装置进行管辖时， 触发所述 发送单元 402向所述转发面装置发送用于计算包转发路径的信息；
所述发送单元 402， 用于发送所述用于计算包转发路径的信息， 所述转发面装置 和所述控制面装置位于控制与转发分离的网络架构的网络。
控制面装置能够对转发面装置进行管辖是指控制面装置能够通过控制通道与转 发面装置进行通信。
从上述技术方案可以看出，控制面装置能够对转发面装置进行管辖时，将用于计 算包转发路径的信息发送至转发面装置。 因此， 通过本发明实施例提供的技术方案， 转发面装置基于用于计算包转发路径的信息计算包转发路径前不需要主动获取用于 计算包转发路径的信息。
可选的，
转发面装置接收到所述用于计算包转发路径的信息后，可以根据所述用于计算包 转发路径的信息计算包转发路径。 举例来说， 转发面装置可以根据 STP计算包转发路径。 转发面装置也可以根据 IS-IS协议计算包转发路径。
举例来说， 当开放流交换机根据 STP计算转发路径时， 用于计算转发路径的算 法可以是 Bellman-Ford算法、 Dijkstra算法、 Floyd- Warshall算法或者 Johnson算法。 当转发面装置根据 STP计算包转发路径时， 所述包转发路径可以用如下信息表示： 根桥的标识、 根接口的标识以及指定接口的标识。
举例来说， 当开放流交换机根据 IS-IS协议计算转发路径时， 用于计算转发路径 的算法可以是 SPF算法。
可选的，
所述装置还可以包括：
第一生成单元， 用于所述发送单元 402 发送所述用于计算包转发路径的信息之 前， 获得所述网络的拓扑信息； 基于所述网络的拓扑信息生成所述用于计算包转发路 径的信息。
网络的拓扑信息包括网络中任意两个具有直连关系的网元中的一个网元通过哪 个接口及另一个网元的哪个接口连接到另一个网元。举例来说，所述控制面装置通过 运行扩展的 LLDP获得所述网络的拓扑信息。
举例来说， 开放流控制器与被管辖的开放流交换机建立 TCP连接后， 开放流控 制器能够知道被管辖的开放流交换机具有的接口。开放流控制器向被管辖的开放流交 换机发送扩展的 LLDP消息。扩展的 LLDP消息中携带被管辖的开放流交换机的标识 以及被管辖的开放流交换机的接口的标识。
当被管辖的开放流交换机具有多个接口时，开放流控制器向被管辖的开放流交换 机发送多个扩展的 LLDP消息。多个扩展的 LLDP消息与上述多个接口是一一对应的。 所述多个扩展的 LLDP消息中每个扩展的 LLDP消息中携带了对应接口的接口标识。 被管辖的开放流交换机收到扩展的 LLDP 消息后， 通过被管辖的开放流交换机的接 口，将与接口对应的扩展的 LLDP消息转发至邻居开放流交换机。邻居开放流交换机 收到扩展的 LLDP消息后，在扩展的 LLDP消息中添加所述邻居开放流交换机的标识， 从而生成新的扩展的 LLDP消息。所述邻居开放流交换机通过控制通道将所述新的扩 展的 LLDP消息发送到开放流控制器。
通过上述机制，开放流控制器能够根据所述新的扩展的 LLDP消息得到所述开放 流交换机通过哪个接口和所述邻居开放流交换机进行连接。
基于同样的机制，开放流控制器能够进一步得到所述邻居开放流交换机通过哪个 接口和所述邻居开放流交换机的邻居开放流交换机进行连接。
通过重复上述操作， 开放流控制器能够得到所管辖的网络的拓扑信息。
可选的，
所述用于计算包转发路径的信息包括根桥的标识。
举例来说， 开放流控制器得到所管辖的网络的拓扑信息后， 通过运行 STP可以 得到根桥的标识。本领域的技术人员可以理解，在开放流交换机的优先级相等的场景 下， 根桥的 MAC协议地址的数值小于受同一开放流控制器管辖的其他开放流交换机 的 MAC协议地址的数值。
举例来说， 开放流控制器得到所管辖的网络的拓扑信息后可以通过运行 STP得 到根桥的标识。所述开放流交换机接收到所述开放流控制器发送的根桥的标识后，可 以通过运行 STP得到链路的开销。 所述开放流交换机可以根据根桥的标识以及链路 的开销， 通过运行 STP得到根接口的标识、 非根非指定接口的标识以及指定接口的 标识。
可选的，
所述用于计算包转发路径的信息还可以包括根路径开销。
举例来说，
开放流交换机与开放流控制器建立 TCP连接后，开放流交换机通过 OpenFlow协 议将开放流交换机的每个接口的带宽发送至开放流控制器。 关于 OpenFlow协议， 请 参见 ONF发布的《开放流交换机规范》版本 1.0。 开放流控制器能够根据接口的带宽 得到接口的开销。开放流交换机通过开放流交换机的第一接口与邻居开放流交换机直 连。 第一接口的带宽等于开放流交换机至邻居开放流交换机的直连链路的开销。
当开放流交换机与根桥没有直连关系，并且开放流交换机与根桥之间存在多条链 路时， 开放流控制器可以分别计算多条链路的开销， 从而得到多个根路径开销。 开放 流交换机到根桥的链路的开销为根路径开销。
举例来说， 开放流控制器得到所管辖的网络的拓扑信息后可以通过运行 STP得 到根桥的标识。开放流交换机接收到开放流控制器发送的根桥的标识以及根路径开销 后， 可以通过运行 STP得到根接口的标识、 指定接口的标识以及非根非指定接口的 标识。
本领域的技术人员可以理解， 开放流网络运行 STP后， 能够根据根桥以及网络 的拓扑信息确定具有多个接口的开放流交换机中的哪个或者哪些接口是否存在环路。 当存在环路时，开放流网络能够根据从根桥到开放流交换机的链路的开销确定哪个或 者哪些接口为根接口或者非根非指定接口。
本领域的技术人员可以理解，确定开放流交换机的接口是否为根接口、指定接口 或者非根非指定接口的过程属于计算包转发路径的过程。
可选的，
第二生成单元， 用于所述发送单元 402 发送所述用于计算包转发路径的信息之 前， 获得所述网络的拓扑信息，所述网络的拓扑信息为所述用于计算包转发路径的信 息。
举例来说， 所述控制面装置可以通过扩展的 LLDP获得所述网络的拓扑信息。 可选的
所述用于计算包转发路径的信息包括 LSDB。
可选的，
当所述控制面装置不能对所述转发面装置进行管辖时，所述转发面装置根据所述 用于计算转发路径的信息计算转发路径。
举例来说，所述控制面装置不能对所述转发面装置进行管辖可以是所述控制面装 置发生故障， 也可以是所述控制面装置与所述转发面装置之间的链路发送故障。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单 元及算法步骤， 能够以电子硬件、 或者计算机软件和电子硬件的结合来实现。这些功 能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专 业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实 现不应认为超出本发明的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、 装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中， 应该理解到， 所揭露的系统、 装置和方法， 可 以通过其它的方式实现。 例如， 以上所描述的装置实施例仅仅是示意性的， 例如， 所 述单元的划分， 可以仅仅为一种逻辑功能划分， 实际实现时可以有另外的划分方式， 例如多个单元或组件可以结合或者可以集成到另一个系统， 或一些特征可以忽略， 或 不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过 一些接口， 装置或单元的间接耦合或通信连接， 可以是电性， 机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显 示的部件可以是或者也可以不是物理单元， 即可以位于一个地方， 或者也可以分布到 多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例 方案的目的。
另外，在本发明各个实施例中的各功能单元可以集成在一个处理单元中， 也可以 是各个单元单独物理存在， 也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以 存储在一个计算机可读取存储介质中。基于这样的理解，本发明的技术方案本质上或 者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现 出来， 该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机 设备（可以是个人计算机， 服务器， 或者网络设备等）执行本发明各个实施例所述方 法的全部或部分步骤。 而前述的存储介质包括： U盘、 移动硬盘、 只读存储器（英文 缩写为 ROM,英文全称为 Read-Only Memory ) 随机存取存储器（英文缩写为 RAM, 英文全称为 Random Access Memory )、 磁碟或者光盘等各种可以存储程序代码的介 质。
以上所述， 仅为本发明的具体实施方式， 但本发明的保护范围并不局限于此， 任 何熟悉本技术领域的技术人员在本发明揭露的技术范围内， 可轻易想到变化或替换， 都应涵盖在本发明的保护范围之内。因此，本发明的保护范围应所述以权利要求的保 护范围为准。

Claims

权 利 要 求
1、 一种接收信息的方法， 其特征在于， 包括：
当控制面装置能够对转发面装置进行管辖时，所述转发面装置接收所述控制 面装置发送的用于计算包转发路径的信息，所述转发面装置和所述控制面装置位 于控制与转发分离的网络架构的网络。
2、 根据权利要求 1所述方法， 其特征在于， 所述转发面装置接收所述控制 面装置发送的用于计算包转发路径的信息包括：
所述转发面装置接收所述用于计算包转发路径的信息，所述用于计算包转发 路径的信息通过如下途径获得：
所述控制面装置获得所述网络的拓扑信息；
所述控制面装置基于所述网络的拓扑信息生成所述用于计算包转发路径的 信息。
3、 根据权利要求 2所述方法， 其特征在于， 所述用于计算包转发路径的信 息包括根桥的标识。
4、 根据权利要求 1所述方法， 其特征在于， 所述转发面装置接收所述控制 面装置发送的用于计算包转发路径的信息包括：
所述转发面装置接收所述用于计算包转发路径的信息，所述用于计算包转发 路径的信息通过如下途径获得：
所述控制面装置获得所述网络的拓扑信息，所述网络的拓扑信息为所述用于 计算包转发路径的信息。
5、 根据权利要求 4所述方法， 其特征在于， 所述用于计算包转发路径的信 息包括链路状态数据库。
6、 一种发送信息的方法， 其特征在于， 包括：
当控制面装置能够对转发面装置进行管辖时，所述控制面装置向所述转发面 装置发送用于计算包转发路径的信息，所述转发面装置和所述控制面装置位于控 制与转发分离的网络架构的网络。
7、 根据权利要求 6所述方法， 其特征在于， 所述控制面装置向所述转发面 装置发送用于计算包转发路径的信息之前， 所述方法包括：
所述控制面装置获得所述网络的拓扑信息；
所述控制面装置基于所述网络的拓扑信息生成所述用于计算包转发路径的 信息。
8、 根据权利要求 7所述方法， 其特征在于， 所述用于计算包转发路径的信 息包括根桥的标识。
9、 根据权利要求 6所述方法， 其特征在于， 所述控制面装置向所述转发面 装置发送用于计算包转发路径的信息之前， 所述方法包括：
所述控制面装置获得所述网络的拓扑信息，所述网络的拓扑信息为所述用于 计算包转发路径的信息。
10、根据权利要求 9所述方法， 其特征在于， 所述用于计算包转发路径的信 息包括链路状态数据库。
11、 一种接收信息的装置， 其特征在于， 包括触发单元和接收单元； 所述触发单元， 用于当控制面装置能够对转发面装置进行管辖时， 触发所述 接收单元接收所述控制面装置发送的用于计算包转发路径的信息；
所述接收单元， 用于接收所述用于计算包转发路径的信息， 所述转发面装置 和所述控制面装置位于控制与转发分离的网络架构的网络。
12、 一种发送信息的装置， 其特征在于， 包括触发单元和发送单元： 所述触发单元， 用于当控制面装置能够对转发面装置进行管辖时， 触发所述 发送单元向所述转发面装置发送用于计算包转发路径的信息；
所述发送单元， 用于发送所述用于计算包转发路径的信息， 所述转发面装置 和所述控制面装置位于控制与转发分离的网络架构的网络。
13、 根据权利要求 12所述装置， 其特征在于， 包括：
第一生成单元， 用于所述发送单元发送所述用于计算包转发路径的信息之 前， 获得所述网络的拓扑信息； 基于所述网络的拓扑信息生成所述用于计算包转 发路径的信息。
14、 根据权利要求 12所述装置， 其特征在于， 包括：
第二生成单元， 用于所述发送单元发送所述用于计算包转发路径的信息之 前， 获得所述网络的拓扑信息， 所述网络的拓扑信息为所述用于计算包转发路径 的信息。
PCT/CN2012/073937 2012-04-12 2012-04-12 接收信息的方法、发送信息的方法及装置 WO2013152496A1 (zh)

Priority Applications (5)

Application Number Priority Date Filing Date Title
PCT/CN2012/073937 WO2013152496A1 (zh) 2012-04-12 2012-04-12 接收信息的方法、发送信息的方法及装置
CN201280000301.3A CN103493439B (zh) 2012-04-12 2012-04-12 接收信息的方法、发送信息的方法及装置
EP12873946.3A EP2824875B1 (en) 2012-04-12 2012-04-12 Information receiving and sending methods and apparatuses
JP2015503727A JP5978384B2 (ja) 2012-04-12 2012-04-12 情報を受信するための方法、情報を送信するための方法及びそれらの装置
US14/488,956 US9749215B2 (en) 2012-04-12 2014-09-17 Method for receiving information, method for sending information, and apparatus for the same

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2012/073937 WO2013152496A1 (zh) 2012-04-12 2012-04-12 接收信息的方法、发送信息的方法及装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US14/488,956 Continuation US9749215B2 (en) 2012-04-12 2014-09-17 Method for receiving information, method for sending information, and apparatus for the same

Publications (1)

Publication Number Publication Date
WO2013152496A1 true WO2013152496A1 (zh) 2013-10-17

Family

ID=49327010

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2012/073937 WO2013152496A1 (zh) 2012-04-12 2012-04-12 接收信息的方法、发送信息的方法及装置

Country Status (5)

Country Link
US (1) US9749215B2 (zh)
EP (1) EP2824875B1 (zh)
JP (1) JP5978384B2 (zh)
CN (1) CN103493439B (zh)
WO (1) WO2013152496A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2015195479A (ja) * 2014-03-31 2015-11-05 株式会社エヌ・ティ・ティ・データ ネットワーク制御装置、ネットワーク制御方法、及びプログラム
JP2017501639A (ja) * 2013-12-31 2017-01-12 華為技術有限公司Ｈｕａｗｅｉ Ｔｅｃｈｎｏｌｏｇｉｅｓ Ｃｏ．，Ｌｔｄ． パケット処理方法およびデバイス

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105556906A (zh) * 2014-05-30 2016-05-04 华为技术有限公司 一种网络地址转换方法及装置
WO2017054181A1 (zh) 2015-09-30 2017-04-06 华为技术有限公司 业务流处理策略的处理方法、装置和系统
US11791342B2 (en) 2021-11-17 2023-10-17 International Business Machines Corporation Varactor integrated with complementary metal-oxide semiconductor devices

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102164094A (zh) * 2011-05-30 2011-08-24 北京星网锐捷网络技术有限公司 多链路流量重分配的方法和装置
US20110261723A1 (en) * 2009-10-06 2011-10-27 Nec Corporation Network system, controller, method and program
CN102301663A (zh) * 2011-07-06 2011-12-28 华为技术有限公司 一种报文处理方法及相关设备
US20120020220A1 (en) * 2010-01-04 2012-01-26 Nec Corporation Network system, controller, and network control method
CN102349268A (zh) * 2009-03-09 2012-02-08 日本电气株式会社 OpenFlow通信系统和OpenFlow通信方法

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6130875A (en) * 1997-10-29 2000-10-10 Lucent Technologies Inc. Hybrid centralized/distributed precomputation of network signal paths
US20080189769A1 (en) * 2007-02-01 2008-08-07 Martin Casado Secure network switching infrastructure
EP2383942A1 (en) 2008-12-25 2011-11-02 Hitachi, Ltd. Communication system and communication controller
US8867507B2 (en) * 2009-05-14 2014-10-21 Avaya Inc. Split-plane wireless network architecture
US8873398B2 (en) * 2011-05-23 2014-10-28 Telefonaktiebolaget L M Ericsson (Publ) Implementing EPC in a cloud computer with openflow data plane
US8804490B2 (en) * 2011-07-29 2014-08-12 Telefonaktiebolaget L M Ericsson (Publ) Controller placement for fast failover in the split architecture
US9185027B2 (en) * 2011-07-29 2015-11-10 Telefonaktiebolaget L M Ericsson (Publ) Method and apparatus for resilient routing of control traffic in a split-architecture system
US8811212B2 (en) * 2012-02-22 2014-08-19 Telefonaktiebolaget L M Ericsson (Publ) Controller placement for fast failover in the split architecture

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102349268A (zh) * 2009-03-09 2012-02-08 日本电气株式会社 OpenFlow通信系统和OpenFlow通信方法
US20110261723A1 (en) * 2009-10-06 2011-10-27 Nec Corporation Network system, controller, method and program
US20120020220A1 (en) * 2010-01-04 2012-01-26 Nec Corporation Network system, controller, and network control method
CN102164094A (zh) * 2011-05-30 2011-08-24 北京星网锐捷网络技术有限公司 多链路流量重分配的方法和装置
CN102301663A (zh) * 2011-07-06 2011-12-28 华为技术有限公司 一种报文处理方法及相关设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP2824875A4 *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2017501639A (ja) * 2013-12-31 2017-01-12 華為技術有限公司Ｈｕａｗｅｉ Ｔｅｃｈｎｏｌｏｇｉｅｓ Ｃｏ．，Ｌｔｄ． パケット処理方法およびデバイス
US10200284B2 (en) 2013-12-31 2019-02-05 Huawei Technologies Co., Ltd Packet processing method and device
JP2015195479A (ja) * 2014-03-31 2015-11-05 株式会社エヌ・ティ・ティ・データ ネットワーク制御装置、ネットワーク制御方法、及びプログラム

Also Published As

Publication number Publication date
JP2015514374A (ja) 2015-05-18
EP2824875B1 (en) 2017-08-02
EP2824875A1 (en) 2015-01-14
US20150036542A1 (en) 2015-02-05
US9749215B2 (en) 2017-08-29
CN103493439B (zh) 2016-03-02
CN103493439A (zh) 2014-01-01
EP2824875A4 (en) 2015-03-18
JP5978384B2 (ja) 2016-08-24

Similar Documents

Publication Publication Date Title
JP5590263B2 (ja) 情報システム、制御装置、仮想ネットワークの提供方法およびプログラム
CN103391250B (zh) 静态trill路由方法和系统
US10237179B2 (en) Systems and methods of inter data center out-bound traffic management
JP5488979B2 (ja) コンピュータシステム、コントローラ、スイッチ、及び通信方法
US9515927B2 (en) System and method for layer 3 proxy routing
WO2015000362A1 (zh) 一种业务节点配置方法、业务节点池注册器及系统
WO2014047784A1 (zh) 报文转发路径确定方法及网络设备、控制设备
JP2013510459A (ja) 分離的なパス計算アルゴリズム
TW201134151A (en) RSVP-TE graceful restart under fast re-route conditions
CN102511151A (zh) 一种路由器、虚拟集群路由器系统及建立方法
CN105340230A (zh) 虚拟机架拓扑管理
CN107306215B (zh) 一种数据处理方法、系统及节点
JP2018535616A (ja) ソフトウェア定義ネットワークのエントリ生成およびパケット転送
WO2015081551A1 (zh) 一种网络中实现报文路由的方法、设备和系统
WO2013152496A1 (zh) 接收信息的方法、发送信息的方法及装置
WO2014075216A1 (zh) 一种虚拟集群建立的方法及网络设备
JP2008042665A (ja) ネットワーク仮想化装置及びネットワーク仮想化プログラム
CN107566292B (zh) 报文转发方法及装置
WO2014205792A1 (zh) 一种建立光旁路的方法、装置和系统
WO2012103708A1 (zh) 媒体访问控制mac地址保护方法和交换机
WO2014173235A1 (zh) 转发路径的生成方法、控制器和系统
CN111885630A (zh) 数据传输方法及通信装置
WO2012078523A1 (en) Systems and methods for pseudo-link creation
WO2012171382A1 (zh) 一种环回检测方法及系统
WO2015074258A1 (zh) 一种控制业务数据在虚拟网络中转发的方法、装置及系统

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 12873946

Country of ref document: EP

Kind code of ref document: A1

REEP Request for entry into the european phase

Ref document number: 2012873946

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2012873946

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2015503727

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE