[go: up one dir, main page]

WO2016177030A1 - Sdn网络设备建链方法、设备和系统 - Google Patents

Sdn网络设备建链方法、设备和系统 Download PDF

Info

Publication number
WO2016177030A1
WO2016177030A1 PCT/CN2016/074414 CN2016074414W WO2016177030A1 WO 2016177030 A1 WO2016177030 A1 WO 2016177030A1 CN 2016074414 W CN2016074414 W CN 2016074414W WO 2016177030 A1 WO2016177030 A1 WO 2016177030A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
switch
sptn
dcn
sdn
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2016/074414
Other languages
English (en)
French (fr)
Inventor
陈磊
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
ZTE Corp
Original Assignee
ZTE Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by ZTE Corp filed Critical ZTE Corp
Publication of WO2016177030A1 publication Critical patent/WO2016177030A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/34—Signalling channels for network management communication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/40—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using virtualisation of network functions or resources, e.g. SDN or NFV entities

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a SDN network device chain building method, device and system.
  • PTN Packet Transport Network
  • SPTN software-defined packet transport network
  • 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.
  • the DCN Data Communication Network
  • the EMS Element Management System
  • SDN-PTN Software Defined Network
  • SPTN introduces the feature of SDN control and forwarding separation, abstracting the centralized control plane (Controller, controller) and forwarding plane (Switch, logical switch).
  • 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.
  • 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.
  • IGP Interior Gateway Protocol
  • the foregoing SDN switch includes a software defined network packet transmission network SPTN switch.
  • 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.
  • 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.
  • 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.
  • the method further includes: the network management device synchronizing the network topology information to the controller.
  • 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.
  • the method further includes: the controller receiving the network topology information synchronization message from the network management device.
  • 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.
  • 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.
  • the foregoing SDN switch includes an SPTN switch.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the controller receiving unit is further configured to receive a network topology information synchronization message from the network management device.
  • 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 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.
  • 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.
  • 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.
  • FIG. 1 is a flowchart of a method for establishing an SDN network device according to an embodiment of the present invention
  • FIG. 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
  • FIG. 5 is another detailed flowchart of a method for establishing an SDN network device according to an embodiment of the present invention.
  • FIG. 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.
  • 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.
  • an embodiment of the present invention provides a method for establishing an SDN network device, including:
  • 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;
  • the SDN switch sends network topology information to the network management device and the controller through the DCN network route.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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 may specifically include:
  • the route to the neighboring node is generated according to the DCN topology discovery packet.
  • the route to the neighbor node is generated using the IGP routing protocol.
  • an SPTN-hub switch 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.
  • the neighboring node is an SPTN-CPE switch
  • the device 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.
  • the neighbor node is also an SPTN-hub switch, the route to the neighbor node is generated using the IGP routing protocol.
  • 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.
  • 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:
  • a default route to the neighbor node is generated according to the DCN topology discovery message.
  • 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.
  • the SPTN-CPE switch 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.
  • an embodiment of the present invention further provides a SDN network device chain building method, including:
  • 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.
  • 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.
  • the network management device 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.
  • 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.
  • an embodiment of the present invention further provides a method for establishing a SDN network device, including:
  • the controller receives network topology information from the SDN switch.
  • the controller determines, according to the network topology information, whether the newly added network element supports the SDN.
  • 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.
  • control channel of the controller to the switch may include an openflow channel and an of-config channel.
  • 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 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.
  • 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.
  • 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.
  • 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.
  • the SPTN-hub 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.
  • the network management protocol such as SNMP, NETCONT, Qx, etc.
  • 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.
  • 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.
  • 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. .
  • 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;
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the SPTN-hub switch B-C 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.
  • 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.
  • switches A, B, and C learn the IGP routes between them.
  • the TCP/IP route between the EMS and the controller and the SPTN is available but not yet connected.
  • the EMS and the controller are not aware of the newly created SPTN switch. The switch cannot sense the existing controller and the EMS.
  • the switch 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:
  • 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.
  • 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.
  • the network management and the switch negotiate the network management protocol (NETCONF) to establish a NETCONF session.
  • NETCONF network management protocol
  • SPTN-Hub switches B and C can be managed normally by the EMS.
  • the EMS network management 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.
  • 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.
  • IP address 10.1.1.2 IP address 10.1.1.2
  • SPTN-Hub B IP address 10.1.1.3
  • the SPTN-Hub switches B, C and EMS network management, and the in-band DCN channel of the controller are all open.
  • the SPTN-CPE 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:
  • 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:
  • switch E 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 :
  • 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.
  • 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.
  • the switch B 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.
  • the controller 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.
  • the EMS network management 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.
  • 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.
  • 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.
  • the controller 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.
  • the EMS network management 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.
  • both the controller and the EMS can manage and control the SPTN switch through the in-band DCN channel.
  • 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.
  • 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.
  • the SPTN switch can be further divided into an SPTN-hub type switch and an SPTN-CPE type switch.
  • the obtaining and determining unit 71 may be specifically configured to:
  • the route to the neighboring node is generated according to the DCN topology discovery packet.
  • the route to the neighbor node is generated using the IGP routing protocol.
  • the obtaining and determining unit 71 is specifically configured as:
  • a default route to the neighbor node is generated according to the DCN topology discovery message.
  • 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.
  • 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.
  • 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.
  • 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.
  • controller receiving unit 91 is further configured to receive a network topology information synchronization message from the network management device.
  • 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.
  • each of the above modules may be implemented by software or hardware.
  • 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.
  • the foregoing storage medium may be configured to store program code for performing the following steps:
  • 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.
  • the SDN switch sends network topology information to the network management device and the controller through the DCN network route.
  • 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.
  • ROM Read-Only Memory
  • RAM Random Access Memory
  • a mobile hard disk e.g., a hard disk
  • magnetic memory e.g., a hard disk
  • 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.
  • the invention is not limited to any specific combination of hardware and software.
  • 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.
  • 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.

Landscapes

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

Abstract

本发明公开一种SDN网络设备建链方法、设备和系统，用以解决相关技术中SDN设备难以与传统的非SDN设备对接的问题。该方法包括：SDN交换机根据接收到的DCN拓扑发现报文获取自身直连的网络拓扑信息，并根据DCN拓扑发现报文或内部网关协议IGP路由协议确定DCN网络路由，其中，DCN拓扑发现报文与非SDN交换机使用的拓扑发现报文兼容；SDN交换机通过DCN网络路由分别向网管设备和控制器发送所述网络拓扑信息。

Description

SDN网络设备建链方法、设备和系统 技术领域
本发明涉及通讯技术领域，特别是涉及一种SDN网络设备建链方法、设备和系统。
背景技术
随着软件技术的发展，设备中的越来越多功能都可以通过软件的方式来实现，由此产生了传统设备与支持软件开发的设备之间的兼容性问题。以PTN(Packet Transport Network，分组传送网)和SPTN(SDN-PTN，软件定义的分组传送网)为例。
PTN是以分组交换为内核的多业务传送技术。PTN顺应了电信业务的IP化发展趋势，满足了2G/3G/LTE移动回传和大客户等业务的承载需求。电信PTN网络中，DCN(Data Communication Network，数据通信网)为管理网元提供了一条特殊的带内通道，满足EMS(Element Management System，网元管理系统)网管对域内网元进行远程监控和集中管理的需求。
面向互联网应用为中心的业务发展需求，PTN技术有进一步演进的驱动力，SDN-PTN技术的提出，推动了SDN(Software Defined Network,软件定义网络)技术在PTN网络的引入。与PTN不同，SPTN引入了SDN控制与转发分离的特性，抽象出集中的控制平面(Controller，控制器)和转发平面(Switch,逻辑交换机)。
目前随着SDN逐渐趋于商用，也出现了多种交换机的自动部署方案，但是对于目前商用电信网络，SDN交换机商用刚刚起步，相关PTN网络大部分还是传统的PTN交换机，且短期内大规模的升级或者替换难以预计。由于SPDN与PTN体系结构的差异，SPDN难以与传统PTN的DCN对接。
发明内容
本发明要解决的技术问题是提供一种SDN网络设备建链方法、设备和系统，用以解决相关技术中SDN网络设备难以与传统非SDN网络设备对接的问题。
一方面，本发明实施例提供一种SDN网络设备建链方法，包括：软件定义网络SDN交换机根据接收到的数据通信网络DCN拓扑发现报文获取自身直连的网络拓扑信息，并根据上述DCN拓扑发现报文或IGP(Interior Gateway Protocol，内部网关协议)路由协议确定DCN网 络路由，其中，上述DCN拓扑发现报文与非SDN交换机使用的拓扑发现报文兼容；上述SDN交换机通过上述DCN网络路由分别向网管设备和控制器发送上述网络拓扑信息。
可选的，上述SDN交换机包括软件定义网络分组传输网SPTN交换机。
可选的，上述SPTN交换机为SPTN-hub交换机；上述根据上述DCN拓扑发现报文或内部网关协议IGP路由协议确定DCN网络路由包括：根据上述DCN拓扑发现报文，确定邻居节点的设备类型；在上述邻居节点的设备类型为SPTN-用户侧设备SPTN-CPE交换机的情况下，根据上述DCN拓扑发现报文生成通往上述邻居节点的路由；在上述邻居节点的设备类型为SPTN-集线器SPTN-hub交换机或PTN交换机的情况下，使用IGP路由协议生成通往上述邻居节点的路由。
可选的，上述SPTN交换机为SPTN-CPE交换机；上述根据上述DCN拓扑发现报文或内部网关协议IGP路由协议确定DCN网络路由包括：根据上述DCN拓扑发现报文，确定邻居节点的设备类型；在上述邻居节点的设备类型为SPTN-hub交换机的情况下，根据上述DCN拓扑发现报文生成通往上述邻居节点的默认路由。
另一方面，本发明实施例提供还一种SDN网络设备建链方法，包括：网管设备接收来自SDN交换机的网络拓扑信息；上述网管设备根据上述网络拓扑信息与上述SDN交换机建立网管数据连接。
可选的，上述网管设备接收来自SDN交换机的网络拓扑信息之后，上述方法还包括：上述网管设备将上述网络拓扑信息同步到控制器。
另一方面，本发明实施例还提供一种SDN网络设备建链方法，包括：控制器接收来自SDN交换机的网络拓扑信息；上述控制器根据上述网络拓扑信息确定新增网元是否支持SDN；在上述新增网元支持SDN的情况下，与上述SDN交换机建立控制通道。
可选的，上述方法还包括：上述控制器接收来自网管设备的网络拓扑信息同步消息。
另一方面，本发明实施例还提供一种SDN交换机，包括：获取和确定单元，设置为根据接收到的DCN拓扑发现报文获取自身直连的网络拓扑信息，并根据上述DCN拓扑发现报文或IGP路由协议确定DCN网络路由，其中，上述DCN拓扑发现报文与非SDN交换机使用的拓扑发现报文兼容；发送单元，设置为通过上述DCN网络路由分别向网管设备和控制器发送上述网络拓扑信息。
可选的，上述SDN交换机包括SPTN交换机。
可选的，上述SPTN交换机为SPTN-hub交换机；上述获取和确定单元具体设置为：根据上述DCN拓扑发现报文，确定邻居节点的设备类型；在上述邻居节点的设备类型为SPTN-用户侧设备SPTN-CPE交换机的情况下，根据上述DCN拓扑发现报文生成通往上述邻居节点 的路由；在上述邻居节点的设备类型为SPTN-集线器SPTN-hub交换机或PTN交换机的情况下，使用IGP路由协议生成通往上述邻居节点的路由。
可选的，上述SPTN交换机为SPTN-CPE交换机；上述获取和确定单元具体设置为：根据上述DCN拓扑发现报文，确定邻居节点的设备类型；在上述邻居节点的设备类型为SPTN-hub交换机的情况下，根据上述DCN拓扑发现报文生成通往上述邻居节点的默认路由。
另一方面，本发明实施例还提供一种网管设备，包括：网管接收单元，设置为接收来自SDN交换机的网络拓扑信息；网管建立单元，设置为根据上述网络拓扑信息与上述SDN交换机建立网管数据连接。
可选的，上述设备还包括网管同步单元，设置为在接收来自SDN交换机的网络拓扑信息之后，将上述网络拓扑信息同步到控制器。
另一方面，本发明实施例还提供一种控制器，包括：控制器接收单元，设置为接收来自SDN交换机的网络拓扑信息；控制器确定单元，设置为根据上述网络拓扑信息确定新增网元是否支持SDN；控制器建立单元，设置为在上述新增网元支持SDN的情况下，与上述SDN交换机建立控制通道。
可选的，上述控制器接收单元还设置为接收来自网管设备的网络拓扑信息同步消息。
相应的，本发明实施例还提供一种网络系统，包括本发明实施例提供的任一种交换机，网管设备，以及控制器。
本发明实施例提供的SDN网络设备建链方法、交换机、网管设备、控制器及网络系统，SDN交换机能够根据接收到的DCN拓扑发现报文获取自身直连的网络拓扑信息，并根据所述DCN拓扑发现报文或IGP路由协议确定DCN网络路由，这样，SDN交换机就能够发现自身周围的网络拓扑变化、计算出相应的路由，然后将网络拓扑的变化通知给网管设备和控制器，以便对新的网络拓扑变化完成部署，由于DCN拓扑发现报文与非SDN交换机使用的拓扑发现报文兼容，在上述过程中，SDN交换机与非SDN交换机能够相互识别，相互发现拓扑变化，并基于这些拓扑变化彼此建立连接，有效保证了网络兼容性。
附图说明
图1是本发明实施例提供的SDN网络设备建链方法的一种流程图；
图2是本发明实施例提供的SDN网络设备建链方法的另一种流程图；
图3是本发明实施例提供的SDN网络设备建链方法的又一种流程图；
图4是本发明实施例提供的SDN网络设备建链方法的一种详细流程图；
图5是本发明实施例提供的SDN网络设备建链方法的另一种详细流程图；
图6是本发明实施例中SDN网络设备的一种网络连接示意图；
图7是本发明实施例提供的交换机的一种结构示意图；
图8是本发明实施例提供的网管设备的一种结构示意图；
图9是本发明实施例提供的控制器的一种结构示意图。
具体实施方式
以下结合附图对本发明进行详细说明。应当理解，此处所描述的具体实施例仅仅用以解释本发明，并不限定本发明。
本发明实施例面向SDN的特点，提供一种简单可靠的SDN网络设备建链方法，能够兼容当前电信运营商的非SDN网络环境，且效率高、可靠性强。本发明实施例提供的SDN网络设备建链方法包括的执行主体包括三方：SDN交换机、openflow控制器和EMS网管。下面分别从这三个执行主体的角度对本发明实施例提供的SDN网络设备建链方法进行详细说明。
如图1所示，本发明实施例提供一种SDN网络设备建链方法，包括：
S11，SDN交换机根据接收到的DCN拓扑发现报文获取自身直连的网络拓扑信息，并根据DCN拓扑发现报文或IGP路由协议确定DCN网络路由，其中，DCN拓扑发现报文与非SDN交换机使用的拓扑发现报文兼容；
S12，SDN交换机通过DCN网络路由分别向网管设备和控制器发送网络拓扑信息。
本发明实施例提供的SDN网络设备建链方法，SDN交换机能够根据接收到的DCN拓扑发现报文获取自身直连的网络拓扑信息，并根据DCN拓扑发现报文或IGP路由协议确定DCN网络路由，这样，SDN交换机就能够发现自身周围的网络拓扑变化、计算出相应的路由，然后将网络拓扑的变化通知给网管设备和控制器，以便对新的网络拓扑变化完成部署，由于DCN拓扑发现报文与非SDN交换机使用的拓扑发现报文兼容，在上述过程中，SDN交换机与非SDN交换机能够相互识别，相互发现拓扑变化，并基于这些拓扑变化彼此建立连接，有效保证了网络兼容性。
具体而言，SDN交换机上电后，进行初始化，按照一定的规则生成交换机的管理IP地址，并从设备获取到设备标识、设备MAC、设备类型等信息；获取交换机的Openflow协议端口资源信息，并在NNI(Network Node Interface，网络节点接口)侧端口创建出DCN通道的对应的VLAN(Virtual Local Area Network，虚拟局域网)子接口，默认使用DCN通道预留的专属VLAN，接口类型为点对点类型的接口。接口IP地址直接使用租用DCN管理IP地址方式。 将相应配置转换为Openflow流表项下发配置openflow转发表。然后，根据默认的路由协议配置计算路由，将相应路由转换为对应的流表项，配置到转发芯片。
完成上述配置后，SDN交换机通过SDN协议端口定时向外发送特定的DCN拓扑发现报文，该报文为协议的二层(数据链路层)报文，不依赖于IP路由。为兼容现网的PTN设备，该报文应兼容原PTN设备的拓扑报文格式，包括设备类型、设备MAC、设备IP等。
需要说明的是，SDN交换机是指所有支持SDN的交换机，例如软件定义网络分组传输网SPTN交换机等。而非SDN交换机是指不支持SDN的交换机，例如传统的PTN交换机等。
可选的，SPTN交换机按照所提供的功能可划分为SPTN-Hub交换机和SPTN-CPE交换机。其中，SPTN-Hub为SPTN网络的汇聚节点，工程应用时存在与目前的城域PTN网络对接的场景，需要支持环网、星型、mesh等多种网络拓扑。SPTN-CPE则属于SPTN业务的客户接入侧，通过SPTN-Hub节点接入到现在的城域PTN网络，其网络角色简单，SPTN-CPE间不直接互联。SPTN-Hub和SPTN-CPE交换机均能进行DCN处理。根据设备网络角色的差异性，两种交换机的DCN处理也有所不同。
可选的，在本发明的一个实施例中，SPTN交换机为SPTN-hub交换机，步骤S11中，根据DCN拓扑发现报文或内部网关协议IGP路由协议确定DCN网络路由具体可包括：
根据DCN拓扑发现报文，确定邻居节点的设备类型；
在邻居节点的设备类型为SPTN-CPE交换机的情况下，根据DCN拓扑发现报文生成通往邻居节点的路由；
在邻居节点的设备类型为SPTN-hub交换机或PTN交换机的情况下，使用IGP路由协议生成通往邻居节点的路由。
也就是说，当一个SPTN-hub交换机接收到来自其他网元的DCN拓扑发现报文后，可以根据报文中的设备类型信息判断其直连的邻居节点是否是SPTN-CPE交换机。当该邻居节点是SPTN-CPE交换机时，根据拓扑发现报文中携带的该SPTN-CPE交换机的IP地址，MAC，以及本端的出接口等信息生成一条目的为所直连SPTN-CPE设备的直连路由条目，并重发布该直连路由到IGP路由协议。当该邻居节点也是SPTN-hub交换机时，使用IGP路由协议生成通往所述邻居节点的路由。
可选的，在步骤S12中，SPTN-hub交换机对报文处理后，若发现其拓扑邻居发送变化，且网管通道已建立，则上报网元拓扑变更的信息到EMS网管；若交换机已经与控制器建立通道，则也需要将网元拓扑变更的信息封装成openflow协议的packet_in报文上报给控制器；若此时设备与EMS或者控制器的通道均未建立，则缓存邻居信息后直接终结该报文。
可选的，在本发明的另一个实施例中，SPTN交换机为SPTN-CPE交换机；步骤S11中， 根据DCN拓扑发现报文或IGP路由协议确定DCN网络路由包括：
根据DCN拓扑发现报文，确定邻居节点的设备类型；
在邻居节点的设备类型为SPTN-hub交换机的情况下，根据DCN拓扑发现报文生成通往邻居节点的默认路由。
可选的，SPTN-CPE交换机在本地维护有邻居信息表，并定时向所有的SDN协议端口发送拓扑发现报文，该报文内容格式与SPTN-hub发送的报文格式保持一致。接收到来自直连邻居的DCN拓扑报文后，SPTN-CPE交换机需要更新本地的拓扑邻居信息表，并根据拓扑报文中的网元信息检查是否来自SPTN-Hub交换机。如果拓扑信息报文来自SPTN-Hub交换机，则通告到DCN路由单元；如果拓扑信息报文来自非SPTN-Hub交换机的，则不生成该路由条目。
SPTN-CPE交换机根据将拓扑发现报文中所携带的SPTN-Hub的IP地址、设备MAC以及本端收到该拓扑报文的接口等信息，直接生成一条目的IP为0.0.0.0的默认路由条目：下一跳的地址为SPTN-Hub的IP地址，报文目的MAC地址为SPTN-Hub的设备MAC,出接口为本交换机接收到该报文的接口。若SPTN-CPE与2个及其以上的SPTN-Hub间存在连接时，选择其中一条路径生成路由并下发相应的流表条目，另外一条作为备份路径。当主用路径失效时，删除原路由表项，并选择新表项下发。
相应的，如图2所示，本发明的实施例还一种SDN网络设备建链方法，包括：
S21，网管设备接收来自SDN交换机的网络拓扑信息；
S22，网管设备根据网络拓扑信息与SDN交换机建立网管数据连接。
本发明实施例提供的SDN网络设备建链方法，网管设备接收来自SDN交换机的网络拓扑信息，并根据网络拓扑信息与SDN交换机建立网管数据连接。这样，不论是非SDN网元还是SDN网元发生了变化，网管设备都能够获知相应的网络拓扑变化，并基于这些拓扑变化彼此建立连接，有效保证了网络兼容性。
网管设备在接收到SDN交换机上报的网元拓扑信息变化后，可以获取到SDN交换机的IP地址，主动发起与交换机建立网管数据连接请求并在网管的客户端界面上创建虚拟网元。
可选的，在网管设备接收来自SDN交换机的网络拓扑信息之后，该方法还可包括网管设备将网络拓扑信息同步到控制器。由于非SDN交换机并没有将转发平面与控制平面分开，非SDN设备的运行情况不会通知到控制器，为了使控制器对非SDN设备的运行情况也有所掌控，EMS网管需要将拓扑的变化信息通过网管与控制器间的数据通讯接口进行同步。
相应的，如图3所示，本发明的实施例还提供一种SDN网络设备建链方法，包括：
S31，控制器接收来自SDN交换机的网络拓扑信息；
S32，控制器根据网络拓扑信息确定新增网元是否支持SDN；
S33，在新增网元支持SDN的情况下，与SDN交换机建立控制通道。
本发明实施例提供的SDN网络设备建链方法，控制器能够接收来自SDN交换机的网络拓扑信息，根据网络拓扑信息确定新增网元是否支持SDN，在新增网元支持SDN的情况下，与SDN交换机建立通道，从而使控制器实现对网络设备的控制。
可选的，控制器对交换机的控制通道可包括openflow通道和of-config通道。可选的，该方法还可包括：控制器接收来自网管设备的网络拓扑信息同步消息。由于非SDN设备并没有将转发平面与控制平面分开，其运行情况不会通知到控制器，为了使控制器对非SDN设备的运行情况也有所掌控，控制器可以接收EMS网管的同步消息。
下面通过具体实施例来对本发明提供的SDN网络设备建链进行详细说明。
如图4所示，在本发明的一个实施例中，SPTN-Hub类型交换机与、网管设备和控制器建立链接过程可包括如下步骤：
步骤101：交换机上电后，初始化DCN的运行环境，从设备ROM中读取交换机的网元信息,网元信息应包括:网元MAC地址，设备类型和软件版本信息，根据交换机的唯一性标志计算出本交换机的管理地址，其中网元MAC地址可作为交换机的唯一性标志，由交换机出厂时设置。
步骤102：生成默认的流表项，匹配DCN拓扑发现报文，动作为输出到本地。DCN拓扑报文的匹配字段可以是DCN拓扑报文的特殊组播MAC地址字段、预置的DCN VLAN字段、以太网类型字段或者上述三种字段的组合。
步骤103：配置DCN路由，启动DCN的IGP路由实例，实际应用时，为区分DCN的转发条目与业务的转发条目，可以创建DCN专属的VRF。
步骤104：接收设备NNI侧的SDN协议端口通告，并在端口上创建默认的VLAN子接口作为DCN的数据通道，并将相应的路由配置适配为对应的openflow流表项写交换机上的openflow转发模块。实际工程应用时，该默认的VLAN值必须与现网DCN使用的VLAN值一致。
步骤105：根据相应的配置，通过标准的IGP路由协议协商，计算出DCN的路由表，并将计算出来的DCN路由表适配为openflow流表项后写入openflow转发模块。
步骤106：获取SDN协议端口信息，并向所有的SDN协议端口发送的拓扑发现报文，该报文包含有本网元的标识信息。在SPTN-Hub交换机上，该报文格式应该兼容现网PTN设备运行PTN的DCN拓扑发现报文格式，使PTN网络下挂的SPTN-Hub交换机，可以被相关的PTN正常识别。
步骤107：SPTN-hub交换机接收到直连邻居发送的拓扑发现报文后，从中提取出对端的设备类型、设备的管理IP地址、设备的MAC地址以及本地接收到该报文的端口，并缓存到本地的邻居网元信息表。
步骤108：检查邻居信息表是否发生变化，若发现到新的SPTN-CPE交换机直连邻居，则为该邻居主动生成一条直连路由：目的IP为该邻居的DCN管理IP地址，掩码为255.255.255.255，路由的出接口为邻居信息表中所记录到的接收到该网元信息报文的接口，将生成的路由适配为流表项下发到openflow转发模块，并将该直连路由重发布到IGP路由实例中，使所有SPTN-Hub均能通过IGP路由学习生成SPTN-CPE的路由表项。
若在预置的一段时间内，SPTN-hub未收cpe发来的拓扑发现报文，SPTN-hub认为该邻居离线，删除已生成的直连路由表项，取消该路由在IGP中的重发布。
步骤109：检测邻居网元信息表是否发生变化，如果发生变化，则继续检查是否已经与控制器或者EMS网管建立控制连接。如果已经与EMS网管建立通信连接，则将发生变化的网元信息通过网管通道发送给网管；如果已经与控制器网管建立通信连接，则将发生变化的网元信息封装为openflow的packet_in报文上报给控制器。
步骤110：EMS网管接收到来自已经建立网管监控通道的交换机上报的网络拓扑信息时，根据报文携带的新发现的网元IP地址、网元类型、网元标志等信息在EMS上创建出虚拟网元，并通过IP地址与新部署的交换机建立TCP/IP的底层通讯连接，并在其基础上利用网络管理协议(例如SNMP、NETCONT、Qx等)，建立网元管理的监控通道。
步骤111:EMS网管将新上线的SPTN网元信息通过EMS与controller间的通讯接口同步到controller，以使PTN
步骤112：controller接收到来自EMS网管的信息通告或者通过接收到已监控的SPTN-Hub交换机上报的携带有网元发现信息的packet-in报文，感知到新上电的SPTN-Hub或者SPTN-CPE交换机的管理IP地址、设备类型。controller对交换机的类型进行校验，若交换机类型不属于支持SDN特性的SPTN交换机，则不予处理。若新上电的交换机类型为SPTN交换机，且未与controller建立连接，controller则主动发起与SPTN交换机的建链请求，在TCP/IP的基础上建立openflow安全通道和of-config通道。
本实施例提供的SDN网络设备建链，SPTN交换机整个自动部署过程与传统的PTN交换机兼容，从而有效实现了在相关网络下挂SPTN网络时网元的自动部署。
如图5所示，在本发明的另一个实施例中，SPTN-CPE交换机与控制器和EMS网管建立链接的流程可包括:
步骤201：交换机上电后，初始化DCN的运行环境，从设备ROM中读取交换机的网元 信息,网元信息应包括:网元IP,网元MAC地址，设备类型和软件版本信息；
步骤202：接收设备NNI侧的SDN协议端口通告，并在端口上创建默认的VLAN子接口作为DCN的数据通道，并将相应的配置适配为对应的openflow流表项写交换机上的openflow转发模块。实际工程应用时，该默认的VLAN值必须与现网DCN使用的VLAN值一致；
步骤203：生成默认的流表项，根据拓扑发现报文的特征设置匹配字段，动作为输出到本地；
步骤204：以固定的间隔通过SDN协议端口向外发送DCN拓扑发现报文，报文携带有网元管理地址、网元MAC、网元的设备类型等信息，且与现网PTN的DCN自动发现报文保持兼容；
步骤205：接收到直连邻居的自动发现报文时，缓存邻居网元信息到本地的邻居信息表，基本要素包括：本端收接口、邻居的管理IP、邻居设备类型、邻居的设备MAC；
步骤206：检测邻居信息表内容是否有变化。若发相关新的SPTN-hub交换机接入，则邻居信息表项通知到DCN路由单元。接收到邻居信息表项更新的通知后，生成一条目的为0.0.0.0默认路由条目，下一跳地址为邻居信息表项中的管理地址，报文转发的出接口为邻居信息表项中的本端收接口，并将该路由条目适配为openflow表项写入openflow转发模块。
实际工程上，步骤206中，SPTN-CPE交换机可能通过双归接入的方式连接到2个(或者更多)SPTN-hub交换机。此时会生成多个下一跳地址、出接口均不同的默认路由条目，只需要选择其中一个条目生效，其他路由条目作为备选的转发路径。DCN检测到当前转发条目异常时，则使用备份的路由表。
检测手段可以通过链路状态检测、最大超时时间的方式。链路状态检测，即检测SPTN-CPE与SPTN-hub间的物理链路状态，当前主用路由表项对应的连接DOWN时，若存在备份路由表项，应立刻进行切换。最大超时时间检测：即设置一个最大的超时时间，若在该时间间隔内无法与控制器和网管建立TCP/IP的通讯连接，则视为当前通道不可用，若存在备份路径，则切换到备份的转发路径。
图6模拟了SPTN交换机接入到传统的PTN网络时的典型的组网场景，交换机间通过带内端口用以太网连接，PTN/SPTN的接入网关为传统的PTN A交换机，通过带外接口分别直连到openflow控制器和EMS网管。
结合图6，我们进一步阐释本申请所述的SDN网络设备建链方法的应用实例：
如图6所示，SPTN-Hub交换机和传统的PTN交换机均采用OSPF(Open Shortest Path First，开放式最短路径优先)作为NNI侧设备间互通的IGP路由协议。网管使用网络配置协议NETCONF管理设备；SDN控制器为openflow控制器，控制器与交换机使用openflow协议通 道和of-config协议通道，上述通道均基于DCN提供的TCP/IP数据通道。
PTN交换机A为传统的PTN设备(不支持SDN)，分别与EMS和controller直连，网管已经与交换机A建立起基于TCP/IP的通道，controller不直接管理PTN A设备，但可以ping通A的以太网直连地址192.168.2.1。EMS网管与controller间的通道已经部署开通。
现在PTN交换机A下游新建SPTN的网络，该网络由SPTN-Hub交换机B～C，SPTN-CPE交换机D～E组成。
当SPTN交换机上电后，交换机B～E分别生成DCN网元自动发现的openflow流表项，流表项的匹配字段为网元发现报文使用的预置组播MAC+DCN VLAN+网元自动发现报文的以太类型，动作设置为上送到本地，即需要上送到CPU处理。
交换机B～E自动获取本交换机的网元信息，并根据网元的唯一性标识计算出本网元的管理IP地址，因采用与PTN A相同的IP计算方法，B～E也会生成的IP地址首字节相同，假设分别为10.1.1.2～10.1.1.5，将该IP配置到环回接口上。
SPTN-hub交换机B～C自动创建出DCN专属的OSPF路由实例，OSPF RouterID值为DCN的管理地址。
SPTN-hub交换机B～C接收到本交换机上的openflow协议端口信息通告时，为NNI侧的所有openflow协议端口创建出点对点类型的vlan子接口，VLAN值默认为4094。将DCN端口数据适配为openflow的流表下发。
SPTN-hub交换机B～C根据为每个DCN VLAN子接口配置默认的IP，该地址直接使用租借DCN管理地址，即ip unnumbered方式。DCN VLAN子接口上均启用相同的默认OSPF协议配置，用于SPTN-hub to SPTN-hub或SPTN-Hub to PTN间的DCN互通。配置完成后，生成相应的流表项配置到openflow转发模块，匹配DCN端口上的OSPF协议报文，动作为上送本地处理。
通过DCN OSPF路由实例的协议报文交换，交换机A、B、C将会学习到相互之间的IGP路由。
表1SPTN-Hub交换机B上的DCN转发表
目的ip 一下跳ip 出接口
10.1.1.1/32 10.1.1.1 B1.4094
10.1.1.2/32 10.1.1.2 本地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
表2SPTN-Hub交换机C上的DCN路由转发表
目的ip 一下跳ip 出接口
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 本地loopback
192.168.1.0/24 10.1.1.1 C1.4094
192.168.2.0/24 10.1.1.1 C1.4094
此时EMS网管和controller与SPTN间的TCP/IP路由已有但尚未连接，但是EMS和controller网管还不能感知到新建的SPTN交换机，交换机也不能感知到已经存在的控制器和EMS网管。
交换机B～E在上电后，即定时向openflow的协议端口发送网元自动发现报文，报文中包含有本网元的IP地址、设备MAC、设备类型等信息。
因网元自动发现报文格式的可兼容，PTN交换机A上将能够解析出SPTN交换机发送的网元自动发现报文，并发现新上电的SPTN-hub交换机B和C，此时A上的邻居信息表如表3所示：
表3PTN交换机A上的邻居信息表
  SPTN-hub B SPTN-hub C
本端接口 A1 A2
远端IP地址 10.1.1.2 10.1.1.3
远端设备类型 SPTN-hub SPTN-hub
远端网元MAC地址 00d0d0010102 00d0d0010103
PTN交换机A已经与EMS网管建立了监控通道，因此PTN A直接将新上电网SPTN-A和SPTN-B交换机的网元信息上报到EMS网管。
EMS网管根据该报文，感知到网络中新增的SPTN-Hub A和B的关键信息。EMS通过TCP/IP协议分别与SPTN-Hub A(IP地址为10.1.1.2)、SPTN-Hub B(IP地址为10.1.1.3)建立TCP/IP通讯链接。在TCP/IP连接的基础上，网管与交换机进行网络管理协议(NETCONF)的协商，建立NETCONF会话。此时，SPTN-Hub交换机B和C就可以被EMS正常管理上。
EMS网管感知到网络新增的SPTN-Hub B和C上线时，同时将该信息通过与controller间的数据通道同步到controller上。
controller根据将报文解析后，对新上电的网元类型进行解析，若通告的设备类型为PTN，则不予处理。controller发现新上线网元类型为SPTN-Hub，则检查与目标交换机的TCP/IP链接是否已经建立。此时，SPTN A和SPTN B均为新上电网元，controller通过TCP/IP协议分别与SPTN-Hub A(IP地址为10.1.1.2)、SPTN-Hub B(IP地址为10.1.1.3)建立TCP/IP通讯链接。在TCP/IP连接的基础上，controller与交换机B、C进行openflow协商，并建立openflow安全通道。
至此，SPTN-Hub交换机B、C与EMS网管、controller的带内DCN通道全部开通。
对于SPTN-CPE交换机D和E，接收到来自SPTN-Hub交换机的DCN网元自动发现报文后，分别更新本地的邻居信息表。交换机D、E上的邻居信息表状态如表4、表5所示：
表4SPTN-CPE交换机D上的邻居信息表
  SPTN-CPE B
本端接口本端接口 d1
远端IP地址 10.1.1.2
远端设备类型 SPTN-hub
远端网元MAC地址 00d0d0010102
表5SPTN-CPE交换机E上的邻居信息表
  SPTN-CPE C
本端接口 e1
远端IP地址 10.1.1.3
远端设备类型 SPTN-hub
远端网元MAC地址 00d0d0010103
交换机D所直连的邻居交换机B的类型为SPTN-Hub，因此交换机D中的DCN处理模块根据邻居信息表，主动生成一条表6所示的默认路由表项，并适配成openflow流表项下发配置openflow转发模块：
表6SPTN-CPE交换机D上的DCN路由转发表
目的ip 一下跳ip 出接口
0.0.0.0/0 10.1.1.2 d1.4094
与交换机D的场景类似，交换机E上也根据其直连的SPTN-Hub交换机C的邻居表项，生成一条表7所示的默认路由表项，并适配成openflow流表项下发配置openflow转发模块:
表7SPTN-CPE交换机E上的DCN路由转发表
目的ip 一下跳ip 出接口
0.0.0.0/0 10.1.1.3 e1.4094
对于SPTN-Hub交换机B和C，此时接收到来自SPTN-CPE交换机的邻居信息发现报文， 并分别添加SPTN-CPE的信息到各自的邻居信息表项。
交换机B检查到新增的邻居交换机D为SPTN-CPE交换机，因此根据该信息生成一条如表8所示的直连路由表项，并适配成openflow流表项下发配置openflow转发模块。
表8交换机B上新增的DCN路由转发表
目的ip 一下跳ip 出接口
10.1.1.4/32 10.1.1.4 B3.4094
交换机B同时将该直连路由信息通过路由重发布导入到DCN OSPF路由实例中，使PTN A和SPTN-Hub C均可以学习到SPTN-CPE D的路由。
因为交换机B已经与控制器和EMS网管建立通讯连接，所以交换机B直接将交换机D的网元信息分别通过packet-in报文或NETCONF报文发送到controller或者EMS网管。
controller接收到来自SPTN-Hub B的packet-in报文后，解析出报文数据携带的交换机D的信息，主动发起与交换机D建立基于TCP/IP的openflow协议安全通道。
EMS网管接收到来自SPTN-Hub B的网元信息通告后，解析出报文数据携带的交换机D的信息，主动发起与交换机D建立基于TCP/IP的NETCONF网管通道。
交换机C上处理SPTN-CPE交换机E的过程与交换机B上类似。根据邻居网元信息表，新增表9所示的直连路由表项。
表9交换机C上新增的DCN路由转发表
目的ip 一下跳ip 出接口
10.1.1.5/32 10.1.1.5 C3.4094
交换机C将该直连路由表项重发布到DCN OSPF路由实例，使PTN A和SPTN-Hub B均可以学习到SPTN-CPE E的路由。
因为交换机C已经与控制器和EMS网管建立通讯连接，所以交换机B直接将交换机D的网元信息分别通过packet-in报文或NETCONF报文发送到controller或者EMS网管
controller接收到来自SPTN-Hub C的packet-in报文后，解析出报文数据携带的交换机D的信息，主动发起与交换机E建立基于TCP/IP的openflow协议安全通道。
EMS网管接收到来自SPTN-Hub C的网元信息通告后，解析出报文数据携带的交换机D的信息，主动发起与交换机E建立基于TCP/IP的NETCONF网管通道。
至此，SPTN网络的自动部署完成，controller和EMS均可以通过带内的DCN通道管理和控制SPTN交换机。
相应的，如图7所示，本发明实施例还提供一种SDN交换机7，包括：
获取和确定单元71，设置为根据接收到的DCN拓扑发现报文获取自身直连的网络拓扑信息，并根据DCN拓扑发现报文或IGP路由协议确定DCN网络路由，其中，DCN拓扑发现报文与非SDN交换机使用的拓扑发现报文兼容；
发送单元72，设置为通过DCN网络路由分别向网管设备和控制器发送网络拓扑信息。
本发明实施例提供的SDN交换机7，其获取和确定单元71能够根据接收到的DCN拓扑发现报文获取自身直连的网络拓扑信息，并根据DCN拓扑发现报文或IGP路由协议确定DCN网络路由，这样，SDN交换机7就能够发现自身周围的网络拓扑变化、计算出相应的路由，然后由发送单元72将网络拓扑的变化通知给网管设备和控制器，以便对新的网络拓扑变化完成部署，由于DCN拓扑发现报文与非SDN交换机使用的拓扑发现报文兼容，在上述过程中，SDN交换机与非SDN交换机能够相互识别，相互发现拓扑变化，并基于这些拓扑变化彼此建立连接，有效保证了网络兼容性。
需要说明的是，SDN交换机是指所有支持SDN的交换机，例如软件定义网络分组传输网SPTN交换机等。而非SDN交换机是指不支持SDN的交换机，例如传统的PTN交换机等。其中，SPTN交换机又可分为SPTN-hub类型的交换机和SPTN-CPE类型的交换机。
可选的，对于SPTN-hub类型的交换机，获取和确定单元71可具体设置为：
根据DCN拓扑发现报文，确定邻居节点的设备类型；
在邻居节点的设备类型为SPTN-用户侧设备SPTN-CPE交换机的情况下，根据DCN拓扑发现报文生成通往邻居节点的路由；
在邻居节点的设备类型为SPTN-集线器SPTN-hub交换机或PTN交换机的情况下，使用IGP路由协议生成通往邻居节点的路由。
对于SPTN-CPE类型的交换机，获取和确定单元71具体设置为：
根据DCN拓扑发现报文，确定邻居节点的设备类型；
在邻居节点的设备类型为SPTN-hub交换机的情况下，根据DCN拓扑发现报文生成通往邻居节点的默认路由。
相应的，如图8所示，本发明实施例还提供一种网管设备8，包括：
网管接收单元81，设置为接收来自SDN交换机的网络拓扑信息；
网管建立单元82，设置为根据网络拓扑信息与SDN交换机建立网管数据连接。
本发明实施例提供的网管设备8，其网管接收单元81能够接收来自SDN交换机的网络拓扑信息，网管建立单元82根据网络拓扑信息与SDN交换机建立网管数据连接。这样，不论是SDN网元还是非SDN网元发生了变化，网管设备都能够获知相应的网络拓扑变化，并基 于这些拓扑变化建立网络连接，有效保证了网络兼容性。
可选的，网关设备8还可包括网管同步单元，设置为在接收来自SDN交换机的网络拓扑信息之后，将网络拓扑信息同步到控制器。
相应的，如图9所示，本发明实施例还提供一种控制器9，包括：
控制器接收单元91，设置为接收来自SDN交换机的网络拓扑信息；
控制器确定单元92，设置为根据网络拓扑信息确定新增网元是否支持SDN；
控制器建立单元93，设置为在新增网元支持SDN的情况下，与SDN交换机建立控制通道。
本发明实施例提供的控制器9，控制器接收单元91能够接收来自SDN交换机的网络拓扑信息，控制器确定单元92能够根据所述网络拓扑信息确定新增网元是否支持SDN，在所述新增网元支持SDN的情况下，控制器建立单元93能够与所述SDN交换机建立通道，从而使控制器实现对网络设备的控制。
可选的，控制器接收单元91还设置为接收来自网管设备的网络拓扑信息同步消息。
相应的，本发明实施例还提供一种网络系统，包括前述实施例提供的任一种交换机，网管设备，以及控制器，因此也能实现相应的有益技术效果，前文已经进行了详细的说明，此处不再赘述。
需要说明的是，上述各个模块是可以通过软件或硬件来实现的，对于后者，可以通过以下方式实现，但不限于此：上述模块均位于同一处理器中；或者，上述模块分别位于多个处理器中。
本发明的实施例还提供了一种存储介质。可选地，在本实施例中，上述存储介质可以被设置为存储用于执行以下步骤的程序代码：
S1，软件定义网络SDN交换机根据接收到的数据通信网络DCN拓扑发现报文获取自身直连的网络拓扑信息，并根据DCN拓扑发现报文或内部网关协议IGP路由协议确定DCN网络路由，其中，DCN拓扑发现报文与非SDN交换机使用的拓扑发现报文兼容；
S2，SDN交换机通过DCN网络路由分别向网管设备和控制器发送网络拓扑信息。
可选地，在本实施例中，上述存储介质可以包括但不限于：U盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、移动硬盘、磁碟或者光盘等各种可以存储程序代码的介质。
可选地，本实施例中的具体示例可以参考上述实施例及可选实施方式中所描述的示例，本实施例在此不再赘述。
显然，本领域的技术人员应该明白，上述的本发明的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，可选地，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本发明不限制于任何特定的硬件和软件结合。
以上所述仅为本发明的优选实施例而已，并不用于限制本发明，对于本领域的技术人员来说，本发明可以有各种更改和变化。凡在本发明的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。
工业实用性
在本发明实施例中，SDN交换机能够根据接收到的DCN拓扑发现报文获取自身直连的网络拓扑信息，并根据DCN拓扑发现报文或IGP路由协议确定DCN网络路由，这样，SDN交换机就能够发现自身周围的网络拓扑变化、计算出相应的路由，然后将网络拓扑的变化通知给网管设备和控制器，以便对新的网络拓扑变化完成部署，由于DCN拓扑发现报文与非SDN交换机使用的拓扑发现报文兼容，在上述过程中，SDN交换机与非SDN交换机能够相互识别，相互发现拓扑变化，并基于这些拓扑变化彼此建立连接，有效保证了网络兼容性。

Claims (17)

  1. 一种SDN网络设备建链方法，包括：
    软件定义网络SDN交换机根据接收到的数据通信网络DCN拓扑发现报文获取自身直连的网络拓扑信息，并根据所述DCN拓扑发现报文或内部网关协议IGP路由协议确定DCN网络路由，其中，所述DCN拓扑发现报文与非SDN交换机使用的拓扑发现报文兼容；
    所述SDN交换机通过所述DCN网络路由分别向网管设备和控制器发送所述网络拓扑信息。
  2. 根据权利要求1所述的方法，其中，所述SDN交换机包括软件定义网络分组传输网SPTN交换机。
  3. 根据权利要求2所述的方法，其中，所述SPTN交换机为SPTN-hub交换机；
    所述根据所述DCN拓扑发现报文或内部网关协议IGP路由协议确定DCN网络路由包括：
    根据所述DCN拓扑发现报文，确定邻居节点的设备类型；
    在所述邻居节点的设备类型为SPTN-用户侧设备SPTN-CPE交换机的情况下，根据所述DCN拓扑发现报文生成通往所述邻居节点的路由；
    在所述邻居节点的设备类型为SPTN-集线器SPTN-hub交换机或PTN交换机的情况下，使用IGP路由协议生成通往所述邻居节点的路由。
  4. 根据权利要求2所述的方法，其中，所述SPTN交换机为SPTN-CPE交换机；
    所述根据所述DCN拓扑发现报文或内部网关协议IGP路由协议确定DCN网络路由包括：
    根据所述DCN拓扑发现报文，确定邻居节点的设备类型；
    在所述邻居节点的设备类型为SPTN-hub交换机的情况下，根据所述DCN拓扑发现报文生成通往所述邻居节点的默认路由。
  5. 一种SDN网络设备建链方法，包括：
    网管设备接收来自SDN交换机的网络拓扑信息；
    所述网管设备根据所述网络拓扑信息与所述SDN交换机建立网管数据连接。
  6. 根据权利要求5所述的方法，其中，所述网管设备接收来自SDN交换机的网络拓扑信息之后，所述方法还包括：
    所述网管设备将所述网络拓扑信息同步到控制器。
  7. 一种SDN网络设备建链方法，包括：
    控制器接收来自SDN交换机的网络拓扑信息；
    所述控制器根据所述网络拓扑信息确定新增网元是否支持SDN；
    在所述新增网元支持SDN的情况下，与所述SDN交换机建立控制通道。
  8. 根据权利要求7所述的方法，其中，还包括：
    所述控制器接收来自网管设备的网络拓扑信息同步消息。
  9. 一种SDN交换机，包括：
    获取和确定单元，设置为根据接收到的DCN拓扑发现报文获取自身直连的网络拓扑信息，并根据所述DCN拓扑发现报文或IGP路由协议确定DCN网络路由，其中，所述DCN拓扑发现报文与非SND交换机使用的拓扑发现报文兼容；
    发送单元，设置为通过所述DCN网络路由分别向网管设备和控制器发送所述网络拓扑信息。
  10. 根据权利要求9所述的交换机，其中，所述SDN交换机包括SPTN交换机。
  11. 根据权利要求10所述的交换机，其中，所述SPTN交换机为SPTN-hub交换机；
    所述获取和确定单元具体设置为：
    根据所述DCN拓扑发现报文，确定邻居节点的设备类型；
    在所述邻居节点的设备类型为SPTN-用户侧设备SPTN-CPE交换机的情况下，根据所述DCN拓扑发现报文生成通往所述邻居节点的路由；
    在所述邻居节点的设备类型为SPTN-集线器SPTN-hub交换机或PTN交换机的情况下，使用IGP路由协议生成通往所述邻居节点的路由。
  12. 根据权利要求10所述的交换机，其中，所述SPTN交换机为SPTN-CPE交换机；
    所述获取和确定单元具体设置为：
    根据所述DCN拓扑发现报文，确定邻居节点的设备类型；
    在所述邻居节点的设备类型为SPTN-hub交换机的情况下，根据所述DCN拓扑发现报文生成通往所述邻居节点的默认路由。
  13. 一种网管设备，包括：
    网管接收单元，设置为接收来自SDN交换机的网络拓扑信息；
    网管建立单元，设置为根据所述网络拓扑信息与所述SDN交换机建立网管数据连接。
  14. 根据权利要求13所述的设备，其中，还包括网管同步单元，设置为在接收来自SDN交换机的网络拓扑信息之后，将所述网络拓扑信息同步到控制器。
  15. 一种控制器，包括：
    控制器接收单元，设置为接收来自SDN交换机的网络拓扑信息；
    控制器确定单元，设置为根据所述网络拓扑信息确定新增网元是否支持SDN；
    控制器建立单元，设置为在所述新增网元支持SDN的情况下，与所述SDN交换机建立控制通道。
  16. 根据权利要求15所述的控制器，其中，
    所述控制器接收单元，还设置为接收来自网管设备的网络拓扑信息同步消息。
  17. 一种网络系统，包括权利要求9-12中任一项所述的交换机，权利要求13或14所述的网管设备，以及权利要求15或16所述的控制器。
PCT/CN2016/074414 2015-07-07 2016-02-24 Sdn网络设备建链方法、设备和系统 Ceased WO2016177030A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510393327.4A CN106330727A (zh) 2015-07-07 2015-07-07 Sdn网络设备建链方法、设备和系统
CN201510393327.4 2015-07-07

Publications (1)

Publication Number Publication Date
WO2016177030A1 true WO2016177030A1 (zh) 2016-11-10

Family

ID=57217355

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/074414 Ceased WO2016177030A1 (zh) 2015-07-07 2016-02-24 Sdn网络设备建链方法、设备和系统

Country Status (2)

Country Link
CN (1) CN106330727A (zh)
WO (1) WO2016177030A1 (zh)

Cited By (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109274515A (zh) * 2017-07-18 2019-01-25 中兴通讯股份有限公司 业务迁移方法、相应设备及存储介质
CN109639495A (zh) * 2018-12-21 2019-04-16 江西山水光电科技股份有限公司 一种基于分组传送网设备地址池的dcn实现方案
CN110365549A (zh) * 2019-06-10 2019-10-22 烽火通信科技股份有限公司 一种sptn网络的处理方法和处理系统
CN111294244A (zh) * 2020-02-18 2020-06-16 国家电网有限公司 网管网络的优化方法和装置
CN112202620A (zh) * 2020-10-12 2021-01-08 曙光信息产业(北京)有限公司 一种网络拓扑结构生成方法及系统
CN112491587A (zh) * 2020-11-05 2021-03-12 烽火通信科技股份有限公司 一种sptn网络s-scn实现方法及系统
CN113067727A (zh) * 2021-03-16 2021-07-02 牛智军 基于国产系统下跨区全兼容装置及其网络拓扑采集方法
CN113612636A (zh) * 2021-07-28 2021-11-05 北京邮电大学 软件定义网络拓扑发现方法及系统
CN113645078A (zh) * 2021-08-16 2021-11-12 烽火通信科技股份有限公司 一种网管业务自动延展的方法及系统
CN114465885A (zh) * 2020-10-22 2022-05-10 华为技术有限公司 一种生成扩容配置的方法和控制器
CN115413068A (zh) * 2022-09-02 2022-11-29 湖南智领通信科技有限公司 一种适用于无线自组织网的跨域组网通信方法及装置
CN117278647A (zh) * 2023-11-21 2023-12-22 广东优力普物联科技有限公司 一种设备发现方法、存储介质及电子设备

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105471658B (zh) * 2015-12-11 2019-05-14 北京电子科技职业学院 一种sdn网络及其组网方法
CN108259352B (zh) * 2017-12-25 2021-01-15 锐捷网络股份有限公司 Sdn与非sdn互通的方法及装置
CN110708178B (zh) * 2018-07-09 2022-06-21 中兴通讯股份有限公司 网络部署方法及装置
CN109495901B (zh) * 2018-12-27 2022-03-11 南京未来网络产业创新有限公司 一种拓扑自适应的专网组建方法
CN113301668B (zh) * 2019-07-15 2023-06-23 安科讯(福建)科技有限公司 一种借助无线网络的e1点对点通信的方法、终端及系统
CN112653766B (zh) * 2020-12-25 2022-08-16 中国电子科技集团公司第三十四研究所 一种智能业务感知方法

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103888369A (zh) * 2014-04-10 2014-06-25 何顺民 以太网通信方法、系统和sdn交换机
CN104113792A (zh) * 2014-07-30 2014-10-22 上海斐讯数据通信技术有限公司 一种OpenFlow控制通道建立方法及系统
CN104320278A (zh) * 2014-10-31 2015-01-28 杭州华三通信技术有限公司 基于软件定义网络sdn的广域网络实现方法及设备

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104158747B (zh) * 2013-05-14 2019-09-24 中兴通讯股份有限公司 网络拓扑发现方法和系统
US9450823B2 (en) * 2013-08-09 2016-09-20 Nec Corporation Hybrid network management
US9338097B2 (en) * 2013-10-31 2016-05-10 Telefonaktiebolaget L M Ericsson (Publ) Method and system for load balancing at a data network

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103888369A (zh) * 2014-04-10 2014-06-25 何顺民 以太网通信方法、系统和sdn交换机
CN104113792A (zh) * 2014-07-30 2014-10-22 上海斐讯数据通信技术有限公司 一种OpenFlow控制通道建立方法及系统
CN104320278A (zh) * 2014-10-31 2015-01-28 杭州华三通信技术有限公司 基于软件定义网络sdn的广域网络实现方法及设备

Cited By (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109274515A (zh) * 2017-07-18 2019-01-25 中兴通讯股份有限公司 业务迁移方法、相应设备及存储介质
CN109639495A (zh) * 2018-12-21 2019-04-16 江西山水光电科技股份有限公司 一种基于分组传送网设备地址池的dcn实现方案
CN110365549A (zh) * 2019-06-10 2019-10-22 烽火通信科技股份有限公司 一种sptn网络的处理方法和处理系统
CN111294244A (zh) * 2020-02-18 2020-06-16 国家电网有限公司 网管网络的优化方法和装置
CN112202620A (zh) * 2020-10-12 2021-01-08 曙光信息产业(北京)有限公司 一种网络拓扑结构生成方法及系统
CN114465885B (zh) * 2020-10-22 2025-07-08 华为技术有限公司 一种生成扩容配置的方法和控制器
CN114465885A (zh) * 2020-10-22 2022-05-10 华为技术有限公司 一种生成扩容配置的方法和控制器
CN112491587A (zh) * 2020-11-05 2021-03-12 烽火通信科技股份有限公司 一种sptn网络s-scn实现方法及系统
CN113067727A (zh) * 2021-03-16 2021-07-02 牛智军 基于国产系统下跨区全兼容装置及其网络拓扑采集方法
CN113612636A (zh) * 2021-07-28 2021-11-05 北京邮电大学 软件定义网络拓扑发现方法及系统
CN113612636B (zh) * 2021-07-28 2022-08-05 北京邮电大学 软件定义网络拓扑发现方法及系统
CN113645078A (zh) * 2021-08-16 2021-11-12 烽火通信科技股份有限公司 一种网管业务自动延展的方法及系统
CN113645078B (zh) * 2021-08-16 2023-10-27 烽火通信科技股份有限公司 一种网管业务自动延展的方法及系统
CN115413068A (zh) * 2022-09-02 2022-11-29 湖南智领通信科技有限公司 一种适用于无线自组织网的跨域组网通信方法及装置
CN117278647A (zh) * 2023-11-21 2023-12-22 广东优力普物联科技有限公司 一种设备发现方法、存储介质及电子设备
CN117278647B (zh) * 2023-11-21 2024-02-27 广东优力普物联科技有限公司 一种设备发现方法、存储介质及电子设备

Also Published As

Publication number Publication date
CN106330727A (zh) 2017-01-11

Similar Documents

Publication Publication Date Title
WO2016177030A1 (zh) Sdn网络设备建链方法、设备和系统
US9197583B2 (en) Signaling of attachment circuit status and automatic discovery of inter-chassis communication peers
CN104539443B (zh) 多宿网络中的通信网络路径和状态信息
US9634928B2 (en) Mesh network of simple nodes with centralized control
US7898965B2 (en) IP network and performance monitoring using ethernet OAM
US8385353B2 (en) Connectivity fault management (CFM) auto-provisioning using virtual private LAN service (VPLS) auto-discovery
CN110324165B (zh) 网络设备的管理方法、装置及系统
US9007916B2 (en) Network management utilizing topology advertisements
US9112816B2 (en) Dynamic EQAM discovery in M-CMTS architecture
TWI639325B (zh) 自動配置的交換機、自動配置交換機的方法、交換機自動部署的軟體定義網路系統及其方法
WO2015055016A1 (zh) 网元设备配置和管理方法、装置及网元设备
CN111294281B (zh) 基于业务功能链sfc的通信方法和装置
US10404544B2 (en) Network topology determining method and apparatus, and centralized network status information storage device
CN109327318B (zh) 一种sdn管理网络架构和建立sdn管理网络的方法
CN114301824B (zh) 多接入网络中的边界网关协议的邻居发现
WO2016058329A1 (zh) 业务传送方法及装置
US12009984B2 (en) Targeted neighbor discovery for border gateway protocol
EP3583751A1 (en) Method for an improved deployment and use of network nodes of a switching fabric of a data center or within a central office point of delivery of a broadband access network of a telecommunications network
US20140136714A1 (en) Method for exchanging information about network resources
CN113726916A (zh) 一种配置网络设备ip地址的方法及相关设备

Legal Events

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

Ref document number: 16789024

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16789024

Country of ref document: EP

Kind code of ref document: A1