WO2016177030A1 - Method, device and system for establishing link of sdn network device - Google Patents

Abstract

Disclosed are a method, device and system for establishing a link of an SDN network device and addressing the problem in the related art in which an SDN device is difficult to have a connection with a traditional non-SDN device. The method comprises: acquiring, by an SDN switch according to a received DCN topology discovery packet, topology information of a network directly connected thereto, and determining a DCN network route according to the DCN topology discovery packet or an interior gateway protocol (IGP) routing protocol, wherein the DCN topology discovery packet is compatible with a topology discovery packet utilized by a non-SDN switch; and transmitting, by the SDN switch via the DCN network route, the network topology information to a network management device and a controller respectively.

Description

SDN network equipment building chain method, device and system Technical field

The present invention relates to the field of communications technologies, and in particular, to a SDN network device chain building method, device and system.

Background technique

With the development of software technology, more and more versatility in the device can be realized by means of software, thereby generating compatibility problems between the traditional device and the device supporting the software development. Take PTN (Packet Transport Network) and SPTN (SDN-PTN, software-defined packet transport network) as an example.

PTN is a multi-service transport technology with packet switching as the core. PTN complies with the IP development trend of telecommunication services, and satisfies the bearer requirements of 2G/3G/LTE mobile backhaul and large customers. In the telecom PTN network, the DCN (Data Communication Network) provides a special in-band channel for the management network element to meet the EMS (Element Management System) network management system to remotely monitor and concentrate the intranet elements. Management needs.

For the development of Internet-centric applications, PTN technology has the driving force for further evolution. The introduction of SDN-PTN technology has promoted the introduction of SDN (Software Defined Network) technology in PTN networks. Different from PTN, SPTN introduces the feature of SDN control and forwarding separation, abstracting the centralized control plane (Controller, controller) and forwarding plane (Switch, logical switch).

At present, with the gradual commercialization of SDN, there are also automatic deployment solutions for various switches. However, for commercial telecommunication networks, commercialization of SDN switches has just started. Most of the related PTN networks are still traditional PTN switches, and large-scale in the short term. Upgrade or replacement is hard to predict. Due to the difference between SPDN and PTN architecture, SPDN is difficult to interface with the traditional PTN DCN.

Summary of the invention

The technical problem to be solved by the present invention is to provide a method, a device and a system for establishing an SDN network device, which are used to solve the problem that the SDN network device in the related art is difficult to interface with a conventional non-SDN network device.

In one aspect, the embodiment of the present invention provides a method for establishing an SDN network device, including: the software-defined network SDN switch obtains the directly connected network topology information according to the received data communication network DCN topology discovery packet, and according to the DCN topology described above. Discovery packets or IGP (Interior Gateway Protocol) routing protocol to determine the DCN network And the above-mentioned DCN topology discovery packet is compatible with the topology discovery message used by the non-SDN switch; the SDN switch sends the network topology information to the network management device and the controller respectively through the DCN network route.

Optionally, the foregoing SDN switch includes a software defined network packet transmission network SPTN switch.

Optionally, the foregoing SPTN switch is an SPTN-hub switch; determining, according to the DCN topology discovery message or the internal gateway protocol IGP routing protocol, the DCN network route, according to the foregoing DCN topology discovery packet, determining a device type of the neighbor node; In the case that the device type of the neighboring node is the SPTN-user-side device SPTN-CPE switch, the route to the neighboring node is generated according to the DCN topology discovery message; the device type of the neighbor node is SPTN-hub SPTN-hub In the case of a switch or PTN switch, the route to the above neighbor nodes is generated using the IGP routing protocol.

Optionally, the foregoing SPTN switch is an SPTN-CPE switch; determining the DCN network route according to the foregoing DCN topology discovery message or the internal gateway protocol IGP routing protocol includes: determining, according to the DCN topology discovery packet, a device type of the neighbor node; If the device type of the neighboring node is an SPTN-hub switch, the default route to the neighboring node is generated according to the DCN topology discovery packet.

On the other hand, the embodiment of the present invention provides a method for establishing a SDN network device, including: the network management device receives network topology information from the SDN switch; and the network management device establishes a network management data connection with the SDN switch according to the network topology information.

Optionally, after the network management device receives the network topology information from the SDN switch, the method further includes: the network management device synchronizing the network topology information to the controller.

On the other hand, the embodiment of the present invention further provides a method for establishing an SDN network device, including: the controller receives network topology information from the SDN switch; and the controller determines, according to the network topology information, whether the newly added network element supports the SDN; In the case that the above-mentioned newly added network element supports SDN, a control channel is established with the above SDN switch.

Optionally, the method further includes: the controller receiving the network topology information synchronization message from the network management device.

On the other hand, the embodiment of the present invention further provides an SDN switch, including: an obtaining and determining unit, configured to obtain the directly connected network topology information according to the received DCN topology discovery packet, and discover the packet according to the DCN topology. Or the IGP routing protocol determines the DCN network route, wherein the DCN topology discovery message is compatible with the topology discovery message used by the non-SDN switch; and the sending unit is configured to send the network topology to the network management device and the controller respectively by using the DCN network route. information.

Optionally, the foregoing SDN switch includes an SPTN switch.

Optionally, the foregoing SPTN switch is an SPTN-hub switch; the foregoing acquiring and determining unit is specifically configured to: determine, according to the DCN topology discovery packet, a device type of the neighbor node; where the device type of the neighbor node is an SPTN-user side device In the case of the SPTN-CPE switch, the message is generated according to the DCN topology discovery message to the neighbor node. Routing; in the case where the device type of the neighbor node is an SPTN-hub SPTN-hub switch or a PTN switch, the route to the neighbor node is generated using the IGP routing protocol.

Optionally, the SPTN switch is an SPTN-CPE switch; the foregoing obtaining and determining unit is specifically configured to: determine, according to the DCN topology discovery packet, a device type of the neighbor node; where the device type of the neighbor node is an SPTN-hub switch In this case, a default route to the neighbor node is generated according to the DCN topology discovery message.

In another aspect, the embodiment of the present invention further provides a network management device, including: a network management unit, configured to receive network topology information from an SDN switch; and a network management unit, configured to establish network management data with the SDN switch according to the network topology information. connection.

Optionally, the device further includes a network management synchronization unit, configured to synchronize the network topology information to the controller after receiving the network topology information from the SDN switch.

In another aspect, the embodiment of the present invention further provides a controller, including: a controller receiving unit, configured to receive network topology information from an SDN switch; and a controller determining unit configured to determine a new network element according to the network topology information. Whether the SDN is supported; the controller establishing unit is configured to establish a control channel with the SDN switch in the case that the newly added network element supports the SDN.

Optionally, the controller receiving unit is further configured to receive a network topology information synchronization message from the network management device.

Correspondingly, the embodiment of the present invention further provides a network system, including any switch, network management device, and controller provided by the embodiment of the present invention.

The SDN network device construction method, the switch, the network management device, the controller, and the network system provided by the embodiment of the present invention, the SDN switch can obtain the directly connected network topology information according to the received DCN topology discovery packet, and according to the DCN The topology discovery packet or the IGP routing protocol determines the DCN network route. In this way, the SDN switch can discover the network topology changes around it, calculate the corresponding route, and then notify the network management device and the controller of the network topology change. The network topology change is completed. The DCN topology discovery packet is compatible with the topology discovery packet used by the non-SDN switch. In the above process, the SDN switch and the non-SDN switch can recognize each other and discover topology changes and change based on these topologies. Establishing connections to each other effectively ensures network compatibility.

DRAWINGS

FIG. 1 is a flowchart of a method for establishing an SDN network device according to an embodiment of the present invention;

2 is another flowchart of a method for establishing an SDN network device according to an embodiment of the present invention;

FIG. 3 is still another flowchart of a method for establishing an SDN network device according to an embodiment of the present invention;

4 is a detailed flowchart of a method for establishing an SDN network device according to an embodiment of the present invention;

FIG. 5 is another detailed flowchart of a method for establishing an SDN network device according to an embodiment of the present invention;

6 is a schematic diagram of a network connection of an SDN network device according to an embodiment of the present invention;

FIG. 7 is a schematic structural diagram of a switch according to an embodiment of the present invention;

FIG. 8 is a schematic structural diagram of a network management device according to an embodiment of the present invention;

FIG. 9 is a schematic structural diagram of a controller according to an embodiment of the present invention.

detailed description

The invention will be described in detail below with reference to the accompanying drawings. It is understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

The embodiment of the present invention provides a simple and reliable SDN network device chain building method, which is compatible with the non-SDN network environment of the current telecommunication operator, and has high efficiency and high reliability. The SDN network device construction method provided by the embodiment of the present invention includes three main parties: an SDN switch, an openflow controller, and an EMS network management. The SDN network device chain building method provided by the embodiment of the present invention is described in detail below from the perspective of the three executive entities.

As shown in FIG. 1 , an embodiment of the present invention provides a method for establishing an SDN network device, including:

S11: The SDN switch obtains the directly connected network topology information according to the received DCN topology discovery packet, and determines the DCN network route according to the DCN topology discovery packet or the IGP routing protocol, where the DCN topology discovery packet is used by the non-SDN switch. Topology discovery message compatibility;

S12: The SDN switch sends network topology information to the network management device and the controller through the DCN network route.

The method for establishing an SDN network device according to the embodiment of the present invention, the SDN switch can obtain the directly connected network topology information according to the received DCN topology discovery message, and determine the DCN network route according to the DCN topology discovery message or the IGP routing protocol. In this way, the SDN switch can discover the network topology changes around it, calculate the corresponding route, and then notify the network management device and the controller of the network topology change, so as to complete the deployment of the new network topology change, due to the DCN topology discovery packet. It is compatible with the topology discovery packets used by non-SDN switches. In the above process, the SDN switch and the non-SDN switch can recognize each other, discover topology changes, and establish connections with each other based on these topology changes, thus effectively ensuring network compatibility.

Specifically, after the SDN switch is powered on, the SDN switch is initialized, generates a management IP address of the switch according to a certain rule, and obtains information such as the device identifier, the device MAC, and the device type from the device, and obtains the Openflow protocol port resource information of the switch, and On the NNI (Network Node Interface) port, the corresponding VLAN (Virtual Local Area Network) sub-interface of the DCN channel is created. By default, the dedicated VLAN reserved by the DCN channel is used. The interface type is a point-to-point interface. . The interface IP address is directly used to lease the DCN management IP address. Convert the configuration to the Openflow flow table and deliver the openflow forwarding table. Then, the route is calculated according to the default routing protocol, and the corresponding route is converted into a corresponding flow entry and configured to the forwarding chip.

After the configuration is complete, the SDN switch sends a specific DCN topology discovery packet to the SDN protocol port. The packet is the Layer 2 (data link layer) packet of the protocol and does not depend on the IP route. To be compatible with the PTN device on the live network, the packet should be compatible with the topology packet format of the original PTN device, including the device type, device MAC address, and device IP address.

It should be noted that the SDN switch refers to all switches that support SDN, such as a software-defined network packet transmission network SPTN switch. A non-SDN switch refers to a switch that does not support SDN, such as a conventional PTN switch.

Optionally, the SPTN switch can be divided into an SPTN-Hub switch and an SPTN-CPE switch according to the provided functions. SPTN-Hub is a convergence node of the SPTN network. When the project is connected to the current metropolitan area PTN network, it needs to support multiple network topologies such as ring network, star, and mesh. SPTN-CPE belongs to the customer access side of the SPTN service. It is connected to the current metropolitan PTN network through the SPTN-Hub node. The network role is simple and the SPTN-CPE is not directly connected. Both SPTN-Hub and SPTN-CPE switches can perform DCN processing. The DCN processing of the two switches is also different depending on the differences in the device network roles.

Optionally, in an embodiment of the present invention, the SPTN switch is an SPTN-hub switch. In step S11, determining the DCN network route according to the DCN topology discovery message or the internal gateway protocol IGP routing protocol may specifically include:

Determining the device type of the neighbor node according to the DCN topology discovery packet;

If the device type of the neighboring node is an SPTN-CPE switch, the route to the neighboring node is generated according to the DCN topology discovery packet.

In the case where the device type of the neighbor node is an SPTN-hub switch or a PTN switch, the route to the neighbor node is generated using the IGP routing protocol.

That is, when an SPTN-hub switch receives a DCN topology discovery packet from another network element, it can determine whether the directly connected neighbor node is an SPTN-CPE switch according to the device type information in the packet. When the neighboring node is an SPTN-CPE switch, the device generates a destination for the directly connected SPTN-CPE device based on the IP address, MAC address, and outgoing interface of the SPTN-CPE switch. Connect the route entry and redistribute the direct route to the IGP routing protocol. When the neighbor node is also an SPTN-hub switch, the route to the neighbor node is generated using the IGP routing protocol.

Optionally, in step S12, after the SPTN-hub switch processes the packet, if the topology neighbor transmission change is found, and the network management channel is established, the information about the topology change of the network element is reported to the EMS network management; if the switch has been controlled If the channel is set up, the information about the topology change of the NE is encapsulated into the packet_in packet of the openflow protocol and reported to the controller. If the channel between the device and the EMS or the controller is not established, the neighbor information is directly encapsulated. Message.

Optionally, in another embodiment of the present invention, the SPTN switch is an SPTN-CPE switch; in step S11, Determining the DCN network route according to the DCN topology discovery message or the IGP routing protocol includes:

Determining the device type of the neighbor node according to the DCN topology discovery packet;

In the case that the device type of the neighbor node is an SPTN-hub switch, a default route to the neighbor node is generated according to the DCN topology discovery message.

Optionally, the SPTN-CPE switch maintains a neighbor information table locally, and periodically sends a topology discovery packet to all SDN protocol ports. The format of the packet is consistent with the format of the packet sent by the SPTN-hub. After receiving the DCN topology packet from the directly connected neighbor, the SPTN-CPE switch needs to update the local topology neighbor information table and check whether it is from the SPTN-Hub switch according to the NE information in the topology packet. If the topology information packet is from the SPTN-Hub switch, it is advertised to the DCN routing unit; if the topology information packet is from the non-SPTN-Hub switch, the routing entry is not generated.

The SPTN-CPE switch directly generates a default route entry with the destination IP address of 0.0.0.0 based on the information such as the IP address of the SPTN-Hub, the MAC address of the device, and the interface that the local end receives the topology packet. The address of the next hop is the IP address of the SPTN-Hub. The destination MAC address of the packet is the MAC address of the SPTN-Hub. The outgoing interface is the interface that the switch receives the packet. If there is a connection between the SPTN-CPE and two or more SPTN-Hubs, select one of the paths to generate a route and deliver the corresponding flow table entry, and the other one serves as the backup path. When the primary path is invalid, the original routing entry is deleted and the new entry is delivered.

Correspondingly, as shown in FIG. 2, an embodiment of the present invention further provides a SDN network device chain building method, including:

S21. The network management device receives network topology information from the SDN switch.

S22: The network management device establishes a network management data connection with the SDN switch according to the network topology information.

The method for establishing an SDN network device according to the embodiment of the present invention, the network management device receives the network topology information from the SDN switch, and establishes a network management data connection with the SDN switch according to the network topology information. In this way, whether the non-SDN network element or the SDN network element changes, the network management device can learn the corresponding network topology changes, and establish a connection with each other based on these topology changes, thereby effectively ensuring network compatibility.

After receiving the change of the NE topology information reported by the SDN switch, the network management device can obtain the IP address of the SDN switch, initiate a network connection data connection request with the switch, and create a virtual network element on the client interface of the network management system.

Optionally, after the network management device receives the network topology information from the SDN switch, the method may further include: the network management device synchronizes the network topology information to the controller. Since the non-SDN switch does not separate the forwarding plane from the control plane, the operation of the non-SDN device is not notified to the controller. In order to control the operation of the non-SDN device, the EMS network management needs to change the topology information. Synchronize through the data communication interface between the network management and the controller.

Correspondingly, as shown in FIG. 3, an embodiment of the present invention further provides a method for establishing a SDN network device, including:

S31. The controller receives network topology information from the SDN switch.

S32. The controller determines, according to the network topology information, whether the newly added network element supports the SDN.

S33. When the newly added network element supports SDN, establish a control channel with the SDN switch.

The SDN network device construction method provided by the embodiment of the present invention, the controller can receive the network topology information from the SDN switch, and determine whether the newly added network element supports the SDN according to the network topology information, and if the newly added network element supports the SDN, The SDN switch establishes a channel, thereby enabling the controller to implement control of the network device.

Optionally, the control channel of the controller to the switch may include an openflow channel and an of-config channel. Optionally, the method may further include: the controller receiving a network topology information synchronization message from the network management device. Since the non-SDN device does not separate the forwarding plane from the control plane, its operation will not notify the controller. In order to control the operation of the non-SDN device, the controller can receive the synchronization message of the EMS network management.

The following describes the construction of the SDN network device provided by the present invention in detail by using specific embodiments.

As shown in FIG. 4, in an embodiment of the present invention, the process of establishing a link between an SPTN-Hub type switch and a network management device and a controller may include the following steps:

Step 101: After the switch is powered on, initialize the operating environment of the DCN, and read the network element information of the switch from the device ROM. The network element information includes: the MAC address of the network element, the device type, and the software version information, according to the uniqueness of the switch. Calculate the management address of the switch. The MAC address of the NE can be used as the unique identifier of the switch. It is set when the switch is shipped from the factory.

Step 102: Generate a default flow entry, match the DCN topology discovery packet, and output the action to the local. The matching field of the DCN topology packet may be a special multicast MAC address field of the DCN topology packet, a preset DCN VLAN field, an Ethernet type field, or a combination of the foregoing three fields.

Step 103: Configure the DCN route and start the IGP route instance of the DCN. In actual application, to distinguish the forwarding entry of the DCN from the forwarding entry of the service, a DCN-specific VRF can be created.

Step 104: Receive the SDN protocol port advertisement on the NNI side of the device, and create a default VLAN sub-interface as the data channel of the DCN on the port, and adapt the corresponding route configuration to the corresponding openflow flow entry to write the openflow forwarding on the switch. Module. In actual engineering applications, the default VLAN value must be the same as the VLAN value used by the live network DCN.

Step 105: According to the corresponding configuration, the DCN routing table is calculated through the standard IGP routing protocol negotiation, and the calculated DCN routing table is adapted to the openflow flow entry and then written to the openflow forwarding module.

Step 106: Acquire the SDN protocol port information, and send the topology discovery packet to all the SDN protocol ports, where the packet contains the identification information of the local network element. On the SPTN-Hub switch, the packet format should be compatible with the DCN topology discovery packet format of the PTN running PTN on the live network. The SPTN-Hub switch connected to the PTN network can be recognized by the relevant PTN.

Step 107: After receiving the topology discovery packet sent by the directly connected neighbor, the SPTN-hub switch extracts the device type of the peer device, the management IP address of the device, the MAC address of the device, and the port that receives the packet locally, and caches the packet. Go to the local neighbor NE information table.

Step 108: Check whether the neighbor information table changes. If the new SPTN-CPE switch is directly connected to the neighbor, the neighbor is actively generated with a direct route: the destination IP address is the DCN management IP address of the neighbor, and the mask is 255.255. .255.255, the outbound interface of the route is the interface that receives the information about the network element information recorded in the neighbor information table, and the generated route is forwarded to the openflow forwarding module, and the direct route is forwarded. It is re-advertised to the IGP routing instance, so that all SPTN-Hubs can learn the routing entries of the SPTN-CPE through the IGP route.

If the SPTN-hub does not receive the topology discovery packet sent by the CPE, the SPTN-hub considers that the neighbor is offline, deletes the generated direct route entry, and cancels the re-release of the route in the IGP. .

Step 109: Detect whether the neighbor NE information table changes. If the change occurs, continue to check whether a control connection has been established with the controller or the EMS network management. If the communication connection with the EMS is established, the changed NE information is sent to the NMS through the NMS. If the communication with the NMS is established, the changed NE information is encapsulated as the packet_in packet of the openflow. Give the controller.

Step 110: When the EMS network management receives the network topology information reported by the switch that has established the network management monitoring channel, the EMS network creates the virtual information on the EMS according to the newly discovered IP address, network element type, and network element identifier of the network element. The network element and the underlying communication connection of the TCP/IP are established with the newly deployed switch through the IP address, and the network management protocol (such as SNMP, NETCONT, Qx, etc.) is used to establish the monitoring channel of the network element management.

Step 111: The EMS network management synchronizes the newly uploaded SPTN network element information to the controller through the communication interface between the EMS and the controller, so that the PTN

Step 112: The controller receives the information advertisement from the EMS network management system or receives the packet-in packet carrying the network element discovery information reported by the monitored SPTN-Hub switch, and detects the newly powered SPTN-Hub or SPTN- Management IP address and device type of the CPE switch. The controller verifies the type of the switch. If the switch type does not belong to the SPTN switch that supports the SDN feature, it will not be processed. If the newly-powered switch is an SPTN switch and does not establish a connection with the controller, the controller initiates a link establishment request with the SPTN switch, and establishes an openflow secure channel and an of-config channel on the basis of TCP/IP.

The SDN network device is provided in this embodiment. The automatic deployment process of the SPTN switch is compatible with the traditional PTN switch, which effectively implements the automatic deployment of the network element when the SPTN network is connected to the relevant network.

As shown in FIG. 5, in another embodiment of the present invention, the process of establishing a link between the SPTN-CPE switch and the controller and the EMS network management may include:

Step 201: After the switch is powered on, initialize the operating environment of the DCN, and read the network element of the switch from the device ROM. Information, network element information should include: network element IP, network element MAC address, device type and software version information;

Step 202: Receive the SDN protocol port advertisement on the NNI side of the device, and create a default VLAN sub-interface as the data channel of the DCN on the port, and adapt the corresponding configuration to the corresponding openflow flow entry to write the openflow forwarding module on the switch. . In actual engineering applications, the default VLAN value must be the same as the VLAN value used by the live network DCN.

Step 203: Generate a default flow entry, and set a matching field according to the feature of the topology discovery packet, and the action is output to the local;

In the step 204, the DCN topology discovery packet is sent out through the SDN protocol port at a fixed interval, and the packet carries the information such as the network element management address, the network element MAC, and the device type of the network element, and is automatically discovered by the DCN of the current network PTN. The message remains compatible;

Step 205: When the auto-discovery message of the directly connected neighbor is received, the neighboring network element information is cached to the local neighbor information table, and the basic elements include: the local receiving interface, the management IP address of the neighbor, the neighbor device type, and the device MAC of the neighbor;

Step 206: Detect whether there is a change in the content of the neighbor information table. If a new SPTN-hub switch is accessed, the neighbor information entry is notified to the DCN routing unit. After receiving the notification of the update of the neighbor information entry, a default route entry with the destination address of 0.0.0.0 is generated, and the next hop address is the management address in the neighbor information entry. The outgoing interface of the packet is the local address of the neighbor information entry. End the interface and adapt the route entry to the openflow entry to the openflow forwarding module.

In actual engineering, in step 206, the SPTN-CPE switch may be connected to two (or more) SPTN-hub switches through dual-homing access. At this time, multiple default route entries with different next hop addresses and different outgoing interfaces are generated. Only one of the entries needs to be selected, and other routing entries are used as alternate forwarding paths. When the DCN detects that the current forwarding entry is abnormal, it uses the backed up routing table.

The detection means can pass the link state detection and the maximum timeout period. Link state detection, that is, detecting the physical link status between the SPTN-CPE and the SPTN-hub. If the current connection routing entry corresponds to the DOWN connection, if there is a backup routing entry, it should be switched immediately. Maximum timeout detection: Set a maximum timeout period. If the TCP/IP communication connection cannot be established with the controller and the NMS during this interval, the current channel is considered unavailable. If there is a backup path, switch to backup. The forwarding path.

Figure 6 shows a typical networking scenario when an SPTN switch is connected to a traditional PTN network. The switches connect to each other through an in-band port. The PTN/SPTN access gateway is a traditional PTN A switch. Directly connected to the openflow controller and EMS network management.

With reference to FIG. 6, we further illustrate an application example of the SDN network device chain building method described in the present application:

As shown in Figure 6, the SPTN-Hub switch and the traditional PTN switch use OSPF (Open Shortest Path First) as the IGP routing protocol for interworking between NNI devices. The network management system uses the network configuration protocol NETCONF to manage the device; the SDN controller is the openflow controller, and the controller and the switch use the openflow protocol. The channel and the of-config protocol channel are all based on the TCP/IP data channel provided by the DCN.

The PTN switch A is a traditional PTN device (not supporting SDN). It is directly connected to the EMS and the controller. The network management system has established a TCP/IP-based channel with the switch A. The controller does not directly manage the PTN A device, but can ping the A. The Ethernet direct connection address is 192.168.2.1. The channel between the EMS network management system and the controller has been deployed.

Now, the SPTN network is newly established on the downstream of the PTN switch A. The network consists of SPTN-Hub switches B to C and SPTN-CPE switches D to E.

After the SPTN switch is powered on, the switches B to E respectively generate the openflow flow entry automatically discovered by the DCN network element. The matching field of the flow entry is the preset multicast MAC+DCN VLAN+ network element automatic discovery used by the NE discovery packet. The Ethernet type of the message, the action is set to be sent to the local, that is, it needs to be sent to the CPU for processing.

The switch B to E automatically obtain the NE information of the local switch, and calculate the management IP address of the local network element according to the unique identifier of the network element. The same IP calculation method as PTN A, the IP generated by B to E is also generated. The first byte of the address is the same, assuming 10.1.1.2 to 10.1.1.5, respectively, and the IP is configured on the loopback interface.

The SPTN-hub switch B to C automatically creates an exclusive OSPF route instance of the DCN. The OSPF router ID is the management address of the DCN.

When the SPTN-hub switch B-C receives the information about the openflow protocol port information on the switch, it creates a point-to-point vlan sub-interface for all the openflow protocol ports on the NNI. The VLAN value defaults to 4094. The DCN port data is delivered to the flow table of the openflow.

The SPTN-hub switch B to C configures the default IP address for each DCN VLAN sub-interface. The address is directly used to lease the DCN management address, that is, ip unnumbered. The same default OSPF protocol configuration is enabled on the DCN VLAN sub-interface for DCN interworking between SPTN-hub to SPTN-hub or SPTN-Hub to PTN. After the configuration is complete, the corresponding flow entry is configured to the openflow forwarding module to match the OSPF packets on the DCN port. The action is sent to the local device for processing.

Through protocol packet exchange of the DCN OSPF routing instance, switches A, B, and C learn the IGP routes between them.

Table 1 DCN forwarding table on SPTN-Hub switch B

Purpose ip	Jump ip	Outgoing interface
10.1.1.1/32	10.1.1.1	B1.4094
10.1.1.2/32	10.1.1.2	Local loopback
10.1.1.3/32	10.1.1.3	B2.4094
192.168.1.0/24	10.1.1.1	B1.4094
192.168.2.0/24	10.1.1.1	B1.4094

Table 2 DCN routing forwarding table on SPTN-Hub switch C

Purpose ip	Jump ip	Outgoing interface
10.1.1.1/32	10.1.1.1	C1.4094
10.1.1.2/32	10.1.1.1	C2.4094
10.1.1.3/32	10.1.1.3	Local loopback
192.168.1.0/24	10.1.1.1	C1.4094
192.168.2.0/24	10.1.1.1	C1.4094

At this time, the TCP/IP route between the EMS and the controller and the SPTN is available but not yet connected. However, the EMS and the controller are not aware of the newly created SPTN switch. The switch cannot sense the existing controller and the EMS.

After the switch is powered on, the switch automatically sends the NE auto-discovery packet to the protocol port of the openflow. The packet contains the IP address, MAC address, and device type of the NE.

The PTN switch A can resolve the auto-discovery packets sent by the SPTN switch and discover the newly-powered SPTN-hub switches B and C. The neighbor information table is shown in Table 3:

Table 3 Neighbor information table on PTN switch A

	SPTN-hub B	SPTN-hub C
Local interface	A1	A2
Remote IP address	10.1.1.2	10.1.1.3
Remote device type	SPTN-hub	SPTN-hub
Remote NE MAC address	00d0d0010102	00d0d0010103

The PTN switch A has established a monitoring channel with the EMS network management system. Therefore, the PTN A directly reports the NE information of the new SPTN-A and SPTN-B switches to the EMS network management.

Based on the packet, the EMS network management senses the key information of the newly added SPTN-Hub A and B in the network. The EMS establishes a TCP/IP communication link with SPTN-Hub A (IP address 10.1.1.2) and SPTN-Hub B (IP address 10.1.1.3) through the TCP/IP protocol. On the basis of the TCP/IP connection, the network management and the switch negotiate the network management protocol (NETCONF) to establish a NETCONF session. At this point, SPTN-Hub switches B and C can be managed normally by the EMS.

When the EMS network management senses that the newly added SPTN-Hub B and C are online, the EMS will synchronize the information to the controller through the data channel between the controller and the controller.

After parsing the packet, the controller parses the newly-recognized NE type. If the advertised device type is PTN, the controller does not process it. The controller finds that the new online NE type is SPTN-Hub, and checks whether the TCP/IP link with the target switch has been established. At this point, both SPTN A and SPTN B are new grid elements. The controller establishes TCP with SPTN-Hub A (IP address 10.1.1.2) and SPTN-Hub B (IP address 10.1.1.3) through TCP/IP protocol. /IP communication link. On the basis of the TCP/IP connection, the controller performs openflow negotiation with switches B and C and establishes an openflow secure channel.

At this point, the SPTN-Hub switches B, C and EMS network management, and the in-band DCN channel of the controller are all open.

After receiving the automatic discovery message of the DCN network element from the SPTN-Hub switch, the SPTN-CPE switches D and E respectively update the local neighbor information table. The status of the neighbor information table on switches D and E is shown in Table 4 and Table 5:

Table 4 Neighbor information table on SPTN-CPE switch D

	SPTN-CPE B
Local interface	D1
Remote IP address	10.1.1.2
Remote device type	SPTN-hub
Remote NE MAC address	00d0d0010102

Table 5 Neighbor information table on SPTN-CPE switch E

	SPTN-CPE C
Local interface	E1
Remote IP address	10.1.1.3
Remote device type	SPTN-hub
Remote NE MAC address	00d0d0010103

The type of the neighboring switch B that is directly connected to the switch D is the SPTN-Hub. Therefore, the DCN processing module in the switch D actively generates a default routing entry as shown in Table 6 and adapts it to the openflow flow entry. The configuration of the openflow forwarding module is delivered:

Table 6 DCN routing forwarding table on SPTN-CPE switch D

Purpose ip	Jump ip	Outgoing interface
0.0.0.0/0	10.1.1.2	D1.4094

Similar to the scenario of switch D, switch E also generates a default routing entry as shown in Table 7 according to the neighbor entry of the directly connected SPTN-Hub switch C, and is configured to be an openflow flow entry. Forwarding module:

Table 7 DCN routing forwarding table on SPTN-CPE switch E

Purpose ip	Jump ip	Outgoing interface
0.0.0.0/0	10.1.1.3	E1.4094

For the SPTN-Hub switches B and C, the neighbor information discovery packet from the SPTN-CPE switch is received at this time. The SPTN-CPE information is added to the neighbor information table entries.

Switch B checks that the newly added neighbor switch D is an SPTN-CPE switch. Therefore, a direct-connected routing entry is generated based on the information and is configured as an openflow forwarding entry.

Table 8 New DCN Route Forwarding Table on Switch B

Purpose ip	Jump ip	Outgoing interface
10.1.1.4/32	10.1.1.4	B3.4094

Switch B also imports the direct route information into the DCN OSPF routing instance through route redistribution, so that both PTN A and SPTN-Hub C can learn the route to SPTN-CPE D.

Because the switch B has established a communication connection with the controller and the EMS network management, the switch B directly sends the NE information of the switch D to the controller or the EMS network management device through the packet-in packet or the NETCONF packet.

After receiving the packet-in packet from the SPTN-Hub B, the controller parses the information of the switch D carried in the packet data, and initiates a secure channel based on the TCP/IP-based openflow protocol with the switch D.

After receiving the NE information notification from the SPTN-Hub B, the EMS network management resolves the information of the switch D carried in the packet data, and initiates the establishment of a TCP/IP-based NETCONF network management channel with the switch D.

The process of processing SPTN-CPE switch E on switch C is similar to that on switch B. Add the direct route entry shown in Table 9 based on the neighbor NE information table.

Table 9 New DCN Route Forwarding Table on Switch C

Purpose ip	Jump ip	Outgoing interface
10.1.1.5/32	10.1.1.5	C3.4094

Switch C re-advertises the direct routing entry to the DCN OSPF routing instance, so that both PTN A and SPTN-Hub B can learn the route to SPTN-CPE E.

Because the switch C has established a communication connection with the controller and the EMS network management, the switch B directly sends the NE information of the switch D to the controller or the EMS network management device through the packet-in packet or the NETCONF packet.

After receiving the packet-in packet from the SPTN-Hub C, the controller parses the information of the switch D carried in the packet data, and initiates a secure channel based on the TCP/IP-based openflow protocol with the switch E.

After receiving the information about the NE information from the SPTN-Hub C, the EMS network management resolves the information of the switch D carried in the packet data, and initiates the establishment of a TCP/IP-based NETCONF network management channel with the switch E.

At this point, the automatic deployment of the SPTN network is completed, and both the controller and the EMS can manage and control the SPTN switch through the in-band DCN channel.

Correspondingly, as shown in FIG. 7, an embodiment of the present invention further provides an SDN switch 7, including:

The obtaining and determining unit 71 is configured to obtain the directly connected network topology information according to the received DCN topology discovery message, and determine the DCN network route according to the DCN topology discovery message or the IGP routing protocol, where the DCN topology discovery message and The topology discovery packets used by non-SDN switches are compatible;

The sending unit 72 is configured to send network topology information to the network management device and the controller respectively through the DCN network routing.

The SDN switch 7 provided by the embodiment of the present invention can obtain the directly connected network topology information according to the received DCN topology discovery message, and determine the DCN network route according to the DCN topology discovery message or the IGP routing protocol. In this way, the SDN switch 7 can discover the network topology changes around itself, calculate the corresponding route, and then notify the network management device and the controller of the change of the network topology by the sending unit 72, so as to complete the deployment of the new network topology change. The DCN topology discovery packet is compatible with the topology discovery packet used by the non-SDN switch. In the above process, the SDN switch and the non-SDN switch can recognize each other, discover topology changes, and establish connections with each other based on these topology changes. Network compatibility.

It should be noted that the SDN switch refers to all switches that support SDN, such as a software-defined network packet transmission network SPTN switch. A non-SDN switch refers to a switch that does not support SDN, such as a conventional PTN switch. Among them, the SPTN switch can be further divided into an SPTN-hub type switch and an SPTN-CPE type switch.

Optionally, for the switch of the SPTN-hub type, the obtaining and determining unit 71 may be specifically configured to:

Determining the device type of the neighbor node according to the DCN topology discovery packet;

If the device type of the neighboring node is an SPTN-user-side device SPTN-CPE switch, the route to the neighboring node is generated according to the DCN topology discovery packet.

In the case where the device type of the neighbor node is an SPTN-hub SPTN-hub switch or a PTN switch, the route to the neighbor node is generated using the IGP routing protocol.

For the switch of the SPTN-CPE type, the obtaining and determining unit 71 is specifically configured as:

Determining the device type of the neighbor node according to the DCN topology discovery packet;

In the case that the device type of the neighbor node is an SPTN-hub switch, a default route to the neighbor node is generated according to the DCN topology discovery message.

Correspondingly, as shown in FIG. 8, the embodiment of the present invention further provides a network management device 8, which includes:

The network management receiving unit 81 is configured to receive network topology information from the SDN switch;

The network management unit 82 is configured to establish a network management data connection with the SDN switch according to the network topology information.

The network management device 8 provided by the embodiment of the present invention can receive the network topology information from the SDN switch, and the network management unit 82 establishes a network management data connection with the SDN switch according to the network topology information. In this way, whether the SDN network element or the non-SDN network element changes, the network management device can learn the corresponding network topology change, and base. Establishing network connections for these topology changes effectively ensures network compatibility.

Optionally, the gateway device 8 may further include a network management synchronization unit configured to synchronize the network topology information to the controller after receiving the network topology information from the SDN switch.

Correspondingly, as shown in FIG. 9, the embodiment of the present invention further provides a controller 9, which includes:

The controller receiving unit 91 is configured to receive network topology information from the SDN switch;

The controller determining unit 92 is configured to determine, according to the network topology information, whether the newly added network element supports the SDN;

The controller establishing unit 93 is configured to establish a control channel with the SDN switch if the newly added network element supports the SDN.

The controller 9 provided by the embodiment of the present invention, the controller receiving unit 91 can receive network topology information from the SDN switch, and the controller determining unit 92 can determine, according to the network topology information, whether the newly added network element supports the SDN, in the new In the case that the enhanced network element supports SDN, the controller establishing unit 93 can establish a channel with the SDN switch, thereby enabling the controller to implement control of the network device.

Optionally, the controller receiving unit 91 is further configured to receive a network topology information synchronization message from the network management device.

Correspondingly, the embodiment of the present invention further provides a network system, including any one of the switches, the network management device, and the controller provided by the foregoing embodiments, so that the corresponding beneficial technical effects can also be achieved, and the foregoing has been described in detail. I will not repeat them here.

It should be noted that each of the above modules may be implemented by software or hardware. For the latter, the foregoing may be implemented by, but not limited to, the foregoing modules are all located in the same processor; or, the modules are located in multiple In the processor.

Embodiments of the present invention also provide a storage medium. Optionally, in the embodiment, the foregoing storage medium may be configured to store program code for performing the following steps:

S1, the software-defined network SDN switch obtains the directly connected network topology information according to the received data communication network DCN topology discovery message, and determines the DCN network route according to the DCN topology discovery message or the internal gateway protocol IGP routing protocol, where DCN The topology discovery packet is compatible with the topology discovery packet used by the non-SDN switch.

S2. The SDN switch sends network topology information to the network management device and the controller through the DCN network route.

Optionally, in this embodiment, the foregoing storage medium may include, but not limited to, a USB flash drive, a Read-Only Memory (ROM), a Random Access Memory (RAM), a mobile hard disk, and a magnetic memory. A variety of media that can store program code, such as a disc or a disc.

For example, the specific examples in this embodiment may refer to the examples described in the foregoing embodiments and the optional embodiments, and details are not described herein again.

It will be apparent to those skilled in the art that the various modules or steps of the present invention described above can be implemented by a general-purpose computing device that can be centralized on a single computing device or distributed across a network of 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 order herein. The steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated as a single integrated circuit module. Thus, the invention is not limited to any specific combination of hardware and software.

The above description 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.

Industrial applicability

In the embodiment of the present invention, the SDN switch can obtain the directly connected network topology information according to the received DCN topology discovery message, and determine the DCN network route according to the DCN topology discovery message or the IGP routing protocol, so that the SDN switch can The network topology is changed and the corresponding route is calculated. Then, the network topology is notified to the network management device and the controller to complete the deployment of the new network topology. The DCN topology discovery packet is used by the non-SDN switch. The topology discovery packet is compatible. In the above process, the SDN switch and the non-SDN switch can recognize each other, discover topology changes, and establish connections with each other based on these topology changes, thus effectively ensuring network compatibility.

Claims (17)

1. A method for building a chain of SDN network equipment, comprising:

   The software-defined network SDN switch obtains the directly connected network topology information according to the received data communication network DCN topology discovery message, and determines the DCN network route according to the DCN topology discovery message or the internal gateway protocol IGP routing protocol, where The DCN topology discovery packet is compatible with the topology discovery packet used by the non-SDN switch.

   The SDN switch sends the network topology information to the network management device and the controller respectively through the DCN network route.
2. The method of claim 1 wherein said SDN switch comprises a software defined network packet transport network SPTN switch.
3. The method of claim 2, wherein the SPTN switch is an SPTN-hub switch;

   Determining the DCN network route according to the DCN topology discovery message or the internal gateway protocol IGP routing protocol includes:

   Determining a device type of the neighbor node according to the DCN topology discovery packet;

   In the case that the device type of the neighboring node is an SPTN-user-side device SPTN-CPE switch, a route to the neighboring node is generated according to the DCN topology discovery message;

   In the case where the device type of the neighbor node is an SPTN-hub SPTN-hub switch or a PTN switch, a route to the neighbor node is generated using an IGP routing protocol.
4. The method of claim 2, wherein the SPTN switch is an SPTN-CPE switch;

   Determining the DCN network route according to the DCN topology discovery message or the internal gateway protocol IGP routing protocol includes:

   Determining a device type of the neighbor node according to the DCN topology discovery packet;

   In the case that the device type of the neighbor node is an SPTN-hub switch, a default route to the neighbor node is generated according to the DCN topology discovery message.
5. A method for building a chain of SDN network equipment, comprising:

   The network management device receives network topology information from the SDN switch;

   The network management device establishes a network management data connection with the SDN switch according to the network topology information.
6. The method of claim 5, wherein after the network management device receives the network topology information from the SDN switch, the method further includes:

   The network management device synchronizes the network topology information to the controller.
7. A method for building a chain of SDN network equipment, comprising:

   The controller receives network topology information from the SDN switch;

   Determining, according to the network topology information, whether the newly added network element supports the SDN;

   In the case that the newly added network element supports SDN, a control channel is established with the SDN switch.
8. The method of claim 7 further comprising:

   The controller receives a network topology information synchronization message from the network management device.
9. An SDN switch that includes:

   The acquiring and determining unit is configured to obtain the directly connected network topology information according to the received DCN topology discovery message, and determine the DCN network route according to the DCN topology discovery message or the IGP routing protocol, where the DCN topology is found. The packet is compatible with the topology discovery packet used by the non-SND switch.

   And sending, by the sending unit, the network topology information to the network management device and the controller by using the DCN network route.
10. The switch of claim 9 wherein said SDN switch comprises an SPTN switch.
11. The switch according to claim 10, wherein the SPTN switch is an SPTN-hub switch;

    The obtaining and determining unit is specifically configured to:

    Determining a device type of the neighbor node according to the DCN topology discovery packet;

    In the case that the device type of the neighboring node is an SPTN-user-side device SPTN-CPE switch, a route to the neighboring node is generated according to the DCN topology discovery message;

    In the case where the device type of the neighbor node is an SPTN-hub SPTN-hub switch or a PTN switch, a route to the neighbor node is generated using an IGP routing protocol.
12. The switch according to claim 10, wherein the SPTN switch is an SPTN-CPE switch;

    The obtaining and determining unit is specifically configured to:

    Determining a device type of the neighbor node according to the DCN topology discovery packet;

    In the case that the device type of the neighbor node is an SPTN-hub switch, a default route to the neighbor node is generated according to the DCN topology discovery message.
13. A network management device, including:

    The network management receiving unit is configured to receive network topology information from the SDN switch;

    The network management unit is configured to establish a network management data connection with the SDN switch according to the network topology information.
14. The apparatus of claim 13, further comprising a network management synchronization unit configured to synchronize the network topology information to the controller after receiving network topology information from the SDN switch.
15. A controller comprising:

    a controller receiving unit configured to receive network topology information from the SDN switch;

    a controller determining unit, configured to determine, according to the network topology information, whether the newly added network element supports the SDN;

    The controller establishing unit is configured to establish a control channel with the SDN switch if the newly added network element supports the SDN.
16. The controller according to claim 15, wherein

    The controller receiving unit is further configured to receive a network topology information synchronization message from the network management device.
17. A network system comprising the switch of any one of claims 9-12, the network management device of claim 13 or 14, and the controller of claim 15 or 16.

Images