WO2013082983A1

WO2013082983A1 - Method and apparatus for data transmission between openflow network domains

Info

Publication number: WO2013082983A1
Application number: PCT/CN2012/084021
Authority: WO
Inventors: 胡永生
Original assignee: 中兴通讯股份有限公司
Priority date: 2011-12-08
Filing date: 2012-11-02
Publication date: 2013-06-13
Also published as: CN103166876A; CN103166876B

Abstract

The present invention provides a method and an apparatus for data transmission between OpenFlow network domains, wherein the method comprises: the controller of the local network domain obtains global network information, wherein the global network information is the information needed for the data switching between the local network domain and neighbor network domains; for the data packets whose destination addresses are not in the local network domain, the controller of the local network domain controls, according to the global network information, the switch of the local network domain to forward the data packets to the neighbor network domains. Using the technical solution provided by the present invention, the effect that the data switching between different OpenFlow network domains can be realized is achieved.

Description

TECHNICAL FIELD The present invention relates to the field of communications, and in particular to a method and an apparatus for transmitting data between OpenFlow network domains. BACKGROUND OF THE INVENTION The Stanford University in the United States proposed the OpenFlow protocol in 2008. The protocol uses a forwarding/control separation architecture. The external control plane entity uses the OpenFlow protocol to control the forwarding plane device to implement various forwarding logics. The main function of the forwarding plane device is to control according to OpenFlow. The flow table sent by the device performs controlled forwarding, and its behavior is standardized: Receive a message, take out the L2/L3/L4 related field value of its header, and use it as a key to find the flow table, matching After an entry is made, the packet field is transformed according to the instruction set in the content of the entry, and then forwarded to a logical or physical port according to the indication. This protocol further evolved to become the basis of Software Defined Network (SDN) technology, which can implement various complex network applications by software programming on the control plane, and the forwarding plane device does not need any change, because the control plane adopts Universal server + general-purpose operating system, and can be implemented using a common software programming tool or a scripting language such as Python, which makes the support of the new network protocol very simple, and the new technology deployment cycle is greatly shortened. A basic OpenFlow network consists of two main control entities: the network controller (Controller) and the switch (OpenFlow Switch). Typically, a centralized network controller is deployed in the network responsible for the management domain control of all OpenFlow switches throughout the network domain. However, a single centralized controller can become a bottleneck for network scale. For example, the delay of establishing a flow of a switch far away from the controller increases, the throughput of a single controller processing the exchange path request is limited, and the end-to-end path bandwidth is limited. Poor controllability, etc. To this end, the academic community proposes a distributed network controller solution, but these solutions generally deploy multiple controllers on the network, and implement common management and control of multiple network controllers with consistent status through event message synchronization or storage sharing. OpenFlow network. However, in an actual network deployment, an OpenFlow network is generally deployed in an area. OpenFlow networks in multiple areas are interconnected through a limited number of links, but different OpenFlow network domains do not interfere with each other, that is, a network in a region. The controller is only responsible for data exchange within the local domain, and cannot exchange data between the local network domain and other network domains. That is, in the related art, there is no data exchange solution for different OpenFlow network domains. In view of the above problems in the related art, an effective solution has not yet been proposed. SUMMARY OF THE INVENTION In the related art, a technical problem of a solution for data exchange between different OpenFlow network domains has not been proposed. The present invention provides a method and an apparatus for transmitting data between OpenFlow network domains to solve at least the above technical problem. According to an aspect of the present invention, a method for transmitting data between OpenFlow network domains is provided, including: a controller of a local network domain acquires global network information, where the global network information is the local network domain and a neighboring network. Information required for data exchange between domains; for data packets whose destination address is not in the local network domain, the controller of the local network domain controls the switch of the local network domain according to the global network information The data message is sent to the neighboring network domain. Preferably, the global network information includes: link state information between the local network domain and the neighboring network domain, and network information of other network domains except the local network domain. Preferably, the foregoing link state information is obtained by: the controller of the local network domain instructing the switch of the local network domain to forward the first link probe message to the phase via a switch of the neighboring network domain a controller of the local domain; the controller of the local network domain receives the first link probe message forwarded by a controller from the neighboring domain to obtain the link state information. Preferably, the foregoing link state information is obtained by: receiving, by the controller of the local network domain, a second link detection message reported by the switch of the local network domain, where the second link detection message is from The switch of the neighboring network domain; the controller of the local network domain acquires the link state information according to the received second link probe message. Preferably, the network information of the other network domain is obtained by: acquiring, by the controller of the local network domain, network information of the other network domain from a controller of the neighboring network domain. Preferably, the network information of the other network domain includes: terminal device address information and/or address information prefix and/or network domain identifier information of the neighboring network domain, and the neighboring network domain and the other network domain. Link status information between. Preferably, the global network information further includes: link path information between the local network domain and the destination network domain indicated by the destination address. According to another aspect of the present invention, an apparatus for transmitting data between OpenFlow network domains is provided, which is located in a local network domain, and includes: an obtaining module, configured to acquire global network information, where the global network information is the local network Information required for data exchange between the domain and the neighboring network domain; a control module, configured to control a data packet whose destination address is not in the local network domain, and control the switch of the local network domain according to the global network information The data message is sent to the neighboring network domain. Preferably, the global network information includes: link state information between the local network domain and the neighboring network domain, and network information of other network domains except the local network domain. Preferably, the obtaining module includes: a sending unit, configured to instruct the switch of the local network domain to forward the first link probe message to the controller of the neighboring domain via the switch of the neighboring network domain; a receiving unit, configured to receive the first link detection message that is forwarded by a controller from the neighboring domain, where the first acquiring unit is configured to acquire the link state information according to the first link detection message. Preferably, the obtaining module includes: a second receiving unit, configured to receive a second link probe message reported by the switch of the local network domain, where the second link probe message is from the neighboring network domain And a second acquiring unit, configured to acquire the link state information according to the received second link probe message. Preferably, the acquiring module is configured to acquire network information of the other network domain from a controller of the neighboring network domain. According to the present invention, the controller of the local network domain controls the switch of the local network domain to send the data packet whose destination address is not in the local domain to the adjacent network domain according to the global network information, and solves the related art. The technical problem of the solution for data exchange between different OpenFlow network domains can achieve the effect of data exchange between different OpenFlow network domains. BRIEF DESCRIPTION OF THE DRAWINGS The accompanying drawings, which are set to illustrate,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, 1 is a flowchart of a method for transmitting data between OpenFlow network domains according to an embodiment of the present invention; FIG. 2 is a structural block diagram of a data transmission device between OpenFlow network domains according to an embodiment of the present invention; Schematic diagram of a data exchange network architecture between network domains according to an embodiment of the present invention; 4 is a schematic diagram of a process for actively detecting a link of a neighboring network domain in a local network domain according to an embodiment of the present invention; FIG. 5 is a schematic diagram of a process of exchanging data packets in a source network domain according to an embodiment of the present invention; FIG. 7 is a schematic flowchart of a method for a controller to establish a global network information database according to an embodiment of the present invention. FIG. BEST MODE FOR CARRYING OUT THE INVENTION Hereinafter, the present invention will be described in detail with reference to the accompanying drawings. It should be noted that the embodiments in the present application and the features in the embodiments may be combined with each other without conflict. FIG. 1 is a flowchart of a method for transmitting data between OpenFlow network domains according to an embodiment of the present invention. As shown in FIG. 1 , the method includes: Step S102: A controller of a local network domain acquires global network information, where the global network information is required for data exchange between the local network domain and a neighboring network domain. Information; In a specific implementation, a global network information database may be established in the controller of the local network domain to store the global network information. Step S104: For a data packet whose destination address is not in the local network domain, the controller of the local network domain controls, according to the global network information, a switch of the local network domain to send the data packet to the Adjacent network domain. Through the foregoing processing steps, the controller of the local network domain can control the switch of the local network domain to send the data packet whose destination address is not in the local domain to the adjacent network domain, according to the obtained global network information, thus implementing different OpenFlow networks. Data exchange between domains. In a specific application, before the step S104, the controller of the local network domain can determine whether the data packet needs to be exchanged across the network domain, for example, according to the data packet, for the data packet reported by the switch in the local domain. The destination address is used to determine whether a cross-network domain exchange is required. When the destination address is a local network domain, the controller of the local network domain sends a flow table directly to the local domain switch to establish a switching path. Data packet, according to the path selection policy, the controller of the local network domain selects an edge switch as an egress switch, and controls the data packet to be forwarded to the adjacent network domain. In a preferred embodiment of the present invention, the global network information may include the following information: link state information between a local network domain and a neighboring network domain, and network information of other network domains except the local network domain. . In fact, a new networking method based on the OpenFlow network can be implemented by using the processing steps in the step S102, the step S104, and the global network information. For example, the following networking method can be implemented:

The OpenFlow network is composed of at least one network domain, and at least one network link exists between the adjacent network domains; the network domain is composed of a controller and at least one switch; the controller of the network domain is responsible for the switch device in the domain. Management, and exchange path control of data packets within the domain; controllers of the network domain collect link state information with neighboring network domains, and exchange controllers of other network domains with controllers of the neighboring domains Network information, establishing a global network information database; the controller of the network domain controls the local domain switch to send the data packet to the domain and the phase according to the global network information database information for the data packet whose destination address is not in the local domain. On the link of the neighbor's connection. In a preferred implementation of the present invention, the foregoing link state information may be obtained by means of active detection or passive detection. The specific process of active detection is as follows: The controller of the local network domain indicates the local network domain. The switch forwards the first link probe message to the controller of the neighboring domain via the switch of the neighboring network domain; the controller of the local network domain receives the forwarder from the controller of the neighboring domain The first link probe message is obtained to obtain the link state information. In short, the controller of the local network domain instructs the switch of the network domain to send a network connection probe message on all ports, if the controller of the neighboring domain receives the report reported by the switch of the neighboring domain. The network connection probe message, the controller of the neighboring domain forwards the network connection probe message to a controller of the network domain. The specific process of the passive detection is as follows: the controller of the local network domain receives the second link detection message reported by the switch of the local network domain, where the second link detection message is from the phase a switch of the neighboring network domain; the controller of the local network domain acquires the link state information according to the received second link probe message. In short, the controller of the local network domain receives the network connection probe message sent by the neighboring domain switch reported by the switch of the local network domain, and collects the network domain according to the network connection probe message. Link state information of the neighboring domain. As described above, the network information of the other network domain may be obtained by: performing, by the controller of the local network domain, data exchange with the neighboring network domain to obtain network information of the foregoing other network domain, that is, from the foregoing The network information of the other network domain is obtained from a controller of a neighboring network domain. The network information of the other network domain includes: terminal device address information and/or address information prefix and/or network domain identifier information of the neighboring network domain, and between the neighboring network domain and the other network domain. Link status information. In a specific implementation of the embodiment of the present invention, the foregoing global network information further includes: link path information between the local network domain and the destination network domain indicated by the destination address, and may include, for example, the following path information: The intermediate network domain between the domain (local network domain) and the destination network domain, and/or the link path between adjacent network domains on the path, and so on. In this embodiment, a data transmission device between the OpenFlow network domains is also provided. The device is located in the local network domain, and is used to implement the foregoing embodiments and preferred embodiments. The module is described in the device. As used hereinafter, the term "module" may implement a combination of software and/or hardware of a predetermined function. Although the apparatus described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware, is also possible and conceivable. 2 is a structural block diagram of an apparatus for transmitting data between OpenFlow network domains according to an embodiment of the present invention. As shown in FIG. 2, the device includes: an obtaining module 20, configured to acquire global network information, where the global network information is information required for data exchange between the local network domain and a neighboring network domain; The module 22 is coupled to the obtaining module 20, configured to: for the data packet whose destination address is not in the local network domain, control, by the global network information, the switch of the local network domain to send the data packet to the phase Neighbor network domain. Preferably, the global network information includes: link state information between the local network domain and the neighboring network domain, and network information of other network domains except the local network domain. Preferably, the obtaining module 20 may include the following unit, configured to obtain the foregoing link state information in an active detection manner: a sending unit, configured to: indicate, by the switch of the local network domain, that the first link detection message is sent by using the neighboring link The switch of the network domain is forwarded to the controller of the neighboring domain; the first receiving unit is coupled to the sending unit, configured to receive the first link probe message forwarded by the controller of the neighboring domain; The acquiring unit is coupled to the first receiving unit, configured to acquire the link state information according to the first link detection message. Preferably, the obtaining module 20 may further include: a unit for acquiring the link state information in a passive detection manner: a second receiving unit, configured to receive a second link detection message reported by the switch of the local network domain, where The second link detection message is sent from the switch of the neighboring network domain; the second acquisition unit is coupled to the second receiving unit, and configured to acquire the chain according to the received second link detection message. Road status information. Preferably, the obtaining module 20 is configured to acquire network information of the other network domain from a controller of the neighboring network domain. In order to better understand the above embodiments and preferred embodiments, the following detailed description will be made in conjunction with the specific examples and related drawings. The basic idea of the following embodiments is that, in a plurality of isolated OpenFlow network domains, a controller of each network domain interacts with controllers of other network domains to detect network link information between adjacent domains, and Exchange information with other network domain controllers to collect global network information. For the forwarding of data packets, when the destination address of the data packet is the domain terminal, the network controller directly sends a flow table to the local domain switch to establish a switching path. When the destination address of the data packet is another network domain terminal, The network controller controls the local network switch to send the data packet to the link connecting the local domain and the adjacent domain according to the global network information database information of the domain. Embodiment 1 As described in the above embodiment, a new OpenFlow network networking method can be implemented based on the data transmission method between OpenFlow network domains described in the foregoing embodiments. As shown in FIG. 3, the networking includes: a network domain A, a network domain B, and a network domain. Taking network domain A as an example, OpenFlow network domain A is composed of controller A and at least one switch 301, and hosts or terminals 302 in the network are connected to OpenFlow network domain B and network domain C through switch 301. The adjacent OpenFlow network domains are connected by at least one link, and the multiple OpenFlow network domains form an interconnected OpenFlow network. In this embodiment, the controller A of the OpenFlow network domain A is only responsible for the management and control of the switch 301 in the local domain. The controllers A of the plurality of OpenFlow network domains A form a control plane network 303, and exchange network topology information to construct a local global network information base. When the data packet is exchanged, the controllers of the network domain control the data packets sent by the switch in the local domain according to the destination address of the data packet, or forward the data packet to the switch in the local domain or On the terminal, or forward the data packet to the switch in the adjacent domain. The behavior of the switches in the respective OpenFlow network domains is the same as that of the OpenFlow switch in the related art, that is, data forwarding is performed only according to the flow table sent by the controller of the network domain. FIG. 4 is a schematic diagram of a flow of a link detection process of a neighboring network domain by a controller of a local network domain according to an embodiment of the present invention. The following is an example of the process of data exchange between network domain A and network domain B. When the switch joins the OpenFlow network domain, the controller instructs the switch to send a link probe message on all ports, and when the switch adjacent to the switch receives the link probe message, the link probe message is reported to The controller of the network domain to which it belongs. For switches adjacent to other network domains, the link probe message is connected by the switch of the adjacent domain. And receiving, and being reported to the controller of the adjacent domain, the controller of the adjacent domain needs to forward the link detection message to the controller of the network domain that initiates the network detection through the control plane network, and complete the network detection process. . The specific steps are as follows: Step S402: The new switch AS1 joins the network domain A, and establishes a connection with the controller A to perform related operations such as security verification, basic information reporting, and switch configuration. In step S404, the controller A instructs the switch AS1 to perform a network detection process. The controller A periodically sends an instruction to the switch AS1 to instruct the switch AS1 to send the specified network probe message on the designated port. Step S406: The network probe message is sent to the port connected to the switch BS1 of the network domain B by the switch AS1. Here, the processing flow of the network probe message sent by the AS1 to the port connected to the other switches in the network domain A is omitted, because the technology of the present invention cannot be used; in step S408, the switch BS1 receives the network probe message and further reports it through the OpenFlow protocol. Controller B of network domain B; Step S410, controller B receives the network probe message reported by the switch BS1, and determines that the network probe message is from the network domain A, and is forwarded to the controller A of the network domain A through the control plane network; Here, the controller B of the network domain B learns the control of the network domain A. The mode of the device A is solved in the control plane network. For example, when the network domain A requests to join other interconnected OpenFlow networks, the controller of the network domain A downloads the controller information configuration file of other network domains, and the network domain A The controller information is reported to the controller of the other network domain. In step S412, the controller A receives the network probe message forwarded by the controller B, and the network probe message sent in step 202 is used to collect the switch BS1 of the network domain B. The link status between the port of switch AS1 and network domain A. Step S414-Step S422, the controller B periodically instructs the switch BS1 to initiate a network detection process. Similar to the steps S404-S414, the link detection message initiated by the switch BS1 is reported to the controller A through the switch AS1, and the controller A further controls. The face network forwards back to the controller controller B to collect the link state between the switch AS1 of the network domain A and the port of the switch BS1 of the network domain B. Here, the link detection message is a Link Layer Discovery Protocol (LLDP) message, or a Link Management Protocol (LMP) message, or other link can be implemented. The protocol message of the probe can be determined according to the specific network environment. In addition, network link detection between OpenFlow network domains can also be passive. When the switch joins the OpenFlow network domain, the controller instructs the switch to send a link probe message on all ports, and when the switch of the neighboring domain receives the link probe message, the controller of the adjacent domain according to the neighbor The link probe message content reported by the switch of the domain can determine the inter-domain link state, that is, through the steps S404-S408, the controller B of the network domain B can collect the switch of the switch AS1 and the network domain B of the network domain A. The link state between the ports of the BS1; in step S414-S418, the controller A of the network domain A can collect the link state between the switch BS1 of the network domain B and the port of the switch AS1 of the network domain A. . Embodiment 2 In the source network domain, for a data packet whose destination address is another network domain, the controller controls the local domain switch to forward the data packet to the adjacent network domain, and more specifically, to the adjacent network domain. On the switch port. As shown in FIG. 5, the specific steps are as follows: Step S502: The host AH1 in the source network domain A sends a data packet to the network, and the destination address is a network domain.

The host BH1 of B; Step S504, the switch AS2 connected to the host AH1 receives the data packet, and queries the local flow table without a hit entry; here, according to the flow forwarding rule of the OpenFlow protocol, if the host AH1 and the host BH1 are already After the communication is performed, a valid flow table entry may exist on the switch AS2. In this case, the switch AS2 can directly forward the data packet according to the flow table. Step S506: According to the OpenFlow protocol rule, the data packet cannot be forwarded according to the local flow table. The switch AS2 reports the packet to the controller A of the local domain through the OpenFlow message. In step S508, the controller A queries the local global network information database according to the information reported by the switch AS2, and identifies the destination address of the data packet in the network domain. B, and further selecting the switch AS1 to forward to the adjacent network domain according to the configured switching path rule; here, the controller A queries the result according to the local global network information database, and the configured switching path rule, or directly routes the data packet to Destination network domain, or route data packets to an intermediate network domain Transit; In step S510, the controller A sends a forwarding flow table to the switch AS2, indicating that the current flow is forwarded to the switch AS1 on the switch AS2. In step S512, the controller A sends a forwarding flow table to the switch AS1, indicating that the current flow is in the switch. The AS1 forwards the port to the network domain B. In step S514, the switch AS2 forwards the data packet to the switch AS1 according to the instruction in the flow table entry sent by the controller A. In step S516, the switch AS1 is based on The local flow table entry forwards the data packet to the port interconnected with the network domain B. In the destination network domain, when the switch receives the data packet from the other network domain, the controller controls the local domain switch to forward the data packet to the network host or terminal of the local domain for the data packet whose destination address is the local domain. As shown in FIG. 6, the specific steps are as follows: Step S602: The switch BS1 connected to the source network domain receives a data packet; Step S604, the switch BS1 queries the local flow table miss entry; here, according to the OpenFlow protocol The routing rule is as follows: If the switch BS1 receives the data packet belonging to the current flow, the switch AS1 may have a valid flow table entry, and the switch BS1 directly forwards the data packet according to the flow table; Step S606, according to The OpenFlow protocol rule, for the data packet that cannot be forwarded according to the local flow table, the switch BS1 reports the packet to the controller B of the local domain through the OpenFlow message; in step S608, the controller B identifies the datagram according to the information reported by the switch BS1. The destination address of the text is located in the local area, and the switch BS2 is further forwarded to the host BH1 according to the configured switching path rule. Here, the controller B determines the destination address of the data packet to be located in another network according to the local global network information database query result. Domain, or route data packets directly to the destination network domain, or The message is routed to an intermediate network domain for forwarding. In step S610, the controller B sends a forwarding flow table to the switch BS1, indicating that the current flow is forwarded to the switch BS2 on the switch BS1. Step S612, the controller B goes to the switch BS2. Sending a forwarding flow table, indicating that the current flow is forwarded on the switch BS2 to the port connected to the host BH1; In step S614, the switch BS1 forwards the data packet to the switch BS2 according to the instruction in the flow table entry sent by the controller B. Step S616, the switch BS2 forwards the data packet to the host BH1 according to the local flow table entry. Connected to the port. Embodiment 3 FIG. 7 is a schematic flowchart of a method for a controller to establish a global network information database according to an embodiment of the present invention. In this embodiment, when the OpenFlow network domain joins the interconnected OpenFlow network, the controller needs to establish a global network information database: The controller of an OpenFlow network domain needs to determine the destination address of the data packet or the data stream, and the required global network information includes , the terminal address information belonging to each network domain, or specific address information such as a MAC address and/or an IP address, or an address prefix. The controller of an OpenFlow network domain determines the data path of the data packet or the data stream. The required global network information includes the intermediate network domain between the source network domain and the destination network domain, and the adjacent network on the path. What are the link paths between domains? When an OpenFlow network domain is added to the interconnected OpenFlow network, the method for the controller to establish the global network information database is described as follows: Step S702, an OpenFlow network domain applies to join an interconnected OpenFlow network; Step S704, the controller of the OpenFlow network domain collects The network topology information in the domain, including the identity of the switch, the port configuration and status, the link status between the switches, and the learning of the terminal MAC address in the local domain (for the implementation of the Layer 3 routing network, the IP address of the learning terminal is also required); Step S706, the controller of the OpenFlow network domain exchanges global network topology information with the controller of the other network domain, including the network domain identifier, the host/terminal information, and the link state information between the network domains, etc.; Step S708, The controller of the OpenFlow network domain indicates that the switch in the local domain performs inter-domain topology detection, and collects link state information between the local domain and the neighbor network domain. Here, the inter-domain topology detection and the intra-domain topology detection in step S704. Synchronous, involving inter-domain network detection Embodiment described above with reference to a flow. Step S710: The controller of the OpenFlow network domain establishes a local global network information database according to the collected related information. Specifically, the inter-domain topology information can be further simplified by network planning in a specific implementation. For example, the domain ID of an OpenFlow network domain X is pre-configured to be 01, and the intra-domain switch ID prefix is 01. The intra-domain host/terminal The MAC address prefix is 0A~12, and the IP address prefix of the host/terminal in the domain is 10.12.* or 30.10.*. The format of the global network information database finally established by the controller of the OpenFlow network domain is as shown in Table 1:

Table 1 shows the format of the global network information data stored by the controller.

The technical solution provided by the foregoing embodiment can solve the problem of data exchange between different OpenFlow network domains. According to the above technical solution provided by the foregoing embodiment, the controllers of the different OpenFlow network domains form network information between the control plane network interaction network domains, and the controller of the OpenFlow network domain is only responsible for the management and control of the switches in the domain. Easy to manage independent OpenFlow networks to communicate with each other. In another embodiment, software is also provided for performing the technical solutions described in the above embodiments and preferred embodiments. In another embodiment, a storage medium is provided, the software being stored, including but not limited to: an optical disk, a floppy disk, a hard disk, a rewritable memory, and the like. Obviously, those skilled in the art should understand that the above modules or steps of the embodiments of the present invention can be implemented by a general computing device, which can be concentrated on a single computing device or distributed in multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device, such that they may be stored in the storage device by the computing device and, in some cases, may be different from The steps shown or described are performed sequentially, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated into a single integrated circuit module. Thus, embodiments of the invention are not limited to any specific combination of hardware and software. The above is only the preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes can be made to the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and scope of the present invention are intended to be included within the scope of the present invention.

Claims

Claim

A method for transmitting data between OpenFlow network domains, including:

The controller of the local network domain obtains global network information, where the global network information is information required for data exchange between the local network domain and the neighboring network domain;

For a data packet whose destination address is not in the local network domain, the controller of the local network domain controls, according to the global network information, a switch of the local network domain to send the data packet to the neighboring network. area.

2. The method according to claim 1, wherein the global network information comprises:

Link state information between the local network domain and the neighboring network domain, and network information of other network domains except the local network domain.

3. The method according to claim 2, wherein the link state information is obtained by: the controller of the local network domain instructing a switch of the local network domain to send a first link probe message via the a switch of a neighboring network domain forwards to a controller of the neighboring domain;

The controller of the local network domain receives the first link probe message forwarded by a controller from the neighboring domain to obtain the link state information.

The method according to claim 2, wherein the link state information is obtained by: receiving, by a controller of the local network domain, a second link probe message reported by a switch of the local network domain, where And the second link detection message is obtained from the switch of the neighboring network domain; the controller of the local network domain acquires the link state information according to the received second link detection message.

The method according to claim 2, wherein the network information of the other network domain is obtained by: obtaining, by the controller of the local network domain, the other network from a controller of the neighboring network domain Domain network information.

The method of claim 2, wherein the network information of the other network domain comprises:

Terminal device address information and/or address information prefix and/or network domain identification information of the neighboring network domain, and link state information between the neighboring network domain and the other network domain.

The method according to any one of claims 1 to 6, wherein the global network information further comprises: link path information between the local network domain and a destination network domain indicated by the destination address.

8. An apparatus for transmitting data between OpenFlow network domains, located in a local network domain, where the apparatus includes:

An acquiring module, configured to obtain global network information, where the global network information is information required for data exchange between the local network domain and a neighboring network domain;

The control module is configured to control, by the switch of the local network domain, the data packet sent by the local network domain to the neighboring network domain according to the data packet whose destination address is not in the local network domain.

9. The device according to claim 8, wherein the global network information comprises:

Link state information between the local network domain and the neighboring network domain and network information of other network domains except the local network domain.

The device according to claim 9, wherein the obtaining module comprises:

a sending unit, configured to instruct the switch of the local network domain to forward the first link probe message to the controller of the neighboring domain via a switch of the neighboring network domain;

a first receiving unit, configured to receive the first link probe message forwarded by a controller from the neighboring domain;

a first acquiring unit, configured to acquire the link state information according to the first link detection message.

The device according to claim 9, wherein the obtaining module comprises:

a second receiving unit, configured to receive a second link detection message reported by the switch of the local network domain, where the second link detection message is from a switch of the neighboring network domain;

And a second acquiring unit, configured to acquire the link state information according to the received second link probe message.

The device according to claim 9, wherein the acquiring module is configured to acquire network information of the other network domain from a controller of the neighboring network domain.