WO2018145267A1 - 一种转发器入网识别方法、sdn控制器及转发器 - Google Patents

一种转发器入网识别方法、sdn控制器及转发器 Download PDF

Info

Publication number
WO2018145267A1
WO2018145267A1 PCT/CN2017/073117 CN2017073117W WO2018145267A1 WO 2018145267 A1 WO2018145267 A1 WO 2018145267A1 CN 2017073117 W CN2017073117 W CN 2017073117W WO 2018145267 A1 WO2018145267 A1 WO 2018145267A1
Authority
WO
WIPO (PCT)
Prior art keywords
sdn controller
repeater
forwarder
information
board
Prior art date
Application number
PCT/CN2017/073117
Other languages
English (en)
French (fr)
Inventor
史曙光
张艳华
宁易霖
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP17896035.7A priority Critical patent/EP3573303A4/en
Priority to PCT/CN2017/073117 priority patent/WO2018145267A1/zh
Publication of WO2018145267A1 publication Critical patent/WO2018145267A1/zh

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/08—Configuration management of networks or network elements
    • H04L41/0895—Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
    • 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/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0806—Configuration setting for initial configuration or provisioning, e.g. plug-and-play
    • H04L41/0809—Plug-and-play configuration
    • 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/08—Configuration management of networks or network elements
    • H04L41/085—Retrieval of network configuration; Tracking network configuration history
    • H04L41/0853—Retrieval of network configuration; Tracking network configuration history by actively collecting configuration information or by backing up configuration information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/34—Signalling channels for network management communication
    • H04L41/342—Signalling channels for network management communication between virtual entities, e.g. orchestrators, SDN or NFV entities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/24—Negotiation of communication capabilities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/12—Discovery or management of network topologies
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/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 embodiments of the present invention relate to the field of communications, and in particular, to a repeater network access identification method, an SDN controller, and a repeater.
  • SDN Software Defined Network
  • SDN controller SDN controller
  • a repeater which can perform data processing, data forwarding, and the like based on a flow table delivered by the SDN controller.
  • This network architecture separates the network control from the physical network topology and removes the limitation of the hardware to the network topology. That is, if the network topology needs to be adjusted, expanded, or upgraded, only the control layer needs to be modified accordingly. The network elements in the infrastructure layer do not need to be replaced. In this way, not only can a large amount of cost be saved, but also the iteration cycle of the network topology can be greatly shortened.
  • the repeater in the SDN scenario has the characteristics of simple structure, low production threshold, low cost, and easy integration. Therefore, it may be produced by multiple suppliers, and the configurations of transponders produced by different vendors may be different.
  • the SDN controller when accessing a new transponder in the original SDN system, the SDN controller is required to recognize the newly accessed transponder.
  • the software of the SDN controller is first released. Therefore, when a new transponder is connected to the existing SDN system, the SDN controller may not be able to know the new networked transponder.
  • the hardware and specifications of the SDN controller cannot be used to identify the newly-connected forwarders. Therefore, the control interface cannot display the newly-connected forwarders, and cannot configure service data for the newly-connected forwarders. Add and delete offline new forwarders.
  • the prior art practice is: before the new transponder is accessed, the SDN controller is upgraded, so that the upgraded SDN controller can identify the newly accessed transponder, and the new access transponder can be used. Manage.
  • the SDN controller Since the SDN controller is generally deployed in an SDN scenario, it simultaneously manages multiple transponders, which requires that the SDN control be suspended during the upgrade of the SDN controller.
  • the service of the device causes the ongoing network business to be affected. Especially in the frequent access scenarios of new transponders, the problem is particularly prominent and the user experience is not good.
  • upgrading the SDN controller to support a newly accessed transponder will also result in an increase in cost when the new device enters the network.
  • the embodiment of the invention provides a method for identifying a network access of a transponder, an SDN controller and a repeater, which solves the problem that when a new transponder is accessed in an existing SDN system, the ongoing network service is affected and the network access cost is high.
  • the embodiment of the present invention adopts the following technical solutions:
  • a first aspect of the embodiments of the present invention provides a method for identifying a forwarder network, including:
  • the SDN controller receives the registration information from the first repeater, where the registration information may include the device type and the device model of the first repeater, and the SDN controller does not include the device type of the first forwarder in determining the hardware device capability information base. And the device model, sending a Plug and Play (PnP) data request to the first forwarder, the PnP data request is used to request the first forwarder to report the device capability information, and the SDN controller receives the first forwarder. Device capability information.
  • PnP Plug and Play
  • the SDN controller receives the registration information of the first forwarder, and when determining that the hardware device capability information database does not include the device type and device model of the first forwarder included in the registration information And transmitting, to the first forwarder, a PnP data request for requesting the first repeater to report the device capability information, and receiving device capability information from the first forwarder.
  • the SDN controller can send the PnP data to the repeater when determining the device type and the device model of the repeater in the hardware device capability information base. The request can accurately know the device capability information of the newly-connected transponder.
  • the SDN controller does not need to be upgraded, and the SDN controller can recognize the new incoming transponder, thereby solving the problem that the impact is being performed when accessing the new transponder in the existing SDN system.
  • the repeater network access identification method may further include: the SDN controller adds the device capability information to the hardware. In the device capability information base.
  • the forwarder network identification method may further include: the SDN controller determines the target command according to the device capability information, and adds a new command to the target command according to the device capability information. Command Line.
  • the forwarding device network identification method may further include: determining, by the SDN controller, a device type of the first forwarding device in the hardware device capability information base and The device model; the SDN controller sends service configuration data to the first forwarder.
  • the forwarding network identification method may further include: the SDN controller sends a registration success response to the first forwarder, and sends the registration success response to the first forwarder.
  • the service configuration data is delivered.
  • the forwarding device network identification method may further include: the SDN controller receiving the service request from the upper layer application, and according to the service request, to the second The forwarder sends the service configuration data, and the second forwarder successfully accesses the forwarder of the SDN system before the first forwarder is powered on.
  • the device capability information is an Extensible Markup Language (XML) file using a YANG model; the device capability information may include at least one of the following: The device information of the first forwarder and the board information supported by the first forwarder.
  • XML Extensible Markup Language
  • the device information may include at least one of the following: device type, device model, device description, device capability set, number of slots, and supported.
  • the slot information may include at least one of the following: an identifier (ID), a slot type
  • the board information may include at least one of the following: a board type, a board name, a board description, and a single The board capacity information, the number of ports on the board, and the port information of the board.
  • the port information of the board can include at least one of the following: port ID, port type, and port description.
  • a second aspect of the embodiments of the present invention provides a method for identifying a forwarder network, including:
  • the first repeater sends registration information to the SDN controller, the registration information may include a device type and a device model of the first repeater; the first repeater receives a PnP data request from the SDN controller, and the PnP data request is used for the request A forwarder reports device capability information; the first forwarder obtains device capability information and sends device capability information to the SDN controller.
  • the first forwarder sends registration information including the device type and the device model of the first forwarder to the SDN controller, and after receiving the PnP data request from the SDN controller, Obtain the device capability information of the device and send the device capability information to the SDN controller.
  • the new networked transponder not only needs to report its own device capability information to the SDN controller after receiving the PnP data request from the first transponder.
  • the SDN controller can accurately know the device capability information of the newly-connected transponder, that is, the SDN controller can recognize the new incoming transponder, thereby solving the problem of accessing the new forwarding in the existing SDN system.
  • the SDN controller When it comes to the device, it affects the ongoing network services and the cost of accessing the network is high.
  • the repeater network identification method may further include: the first repeater receives the registration success response from the SDN controller, and receives the service configuration data from the SDN controller.
  • the device capability information is an XML file that adopts a YANG model; the device capability information may include at least one of the following: device information of the first repeater, Board information supported by the first forwarder.
  • the device information may include at least one of the following: device type, device model, device description, device capability set, number of slots, and supported.
  • Slot information can include at least one of the following: slot ID and slot type.
  • the board information can include at least one of the following: board type, board name, board description, board capability set, and The port number of the board and the port information of the board.
  • the port information of the board can include at least one of the following: port ID, port type, and port description.
  • a third aspect of the embodiments of the present invention provides an SDN controller, including: a receiving unit, a determining unit, and a sending unit.
  • the receiving unit is configured to receive registration information from the first repeater, where the registration information includes the first repeater. a device type and a device model; the determining unit is configured to determine that the device type and the device model of the first repeater received by the receiving unit are not included in the hardware device capability information base; and the sending unit is configured to send the PnP data request to the first forwarder
  • the PnP data request is used to request the first repeater to report the device capability information, and the receiving unit is further configured to receive the device capability information from the first forwarder.
  • the method further includes: adding, the device capability information that is received by the receiving unit is added to the hardware device capability information base.
  • the determining unit is further configured to determine, according to device capability information received by the receiving unit, a target command
  • the adding unit is further configured to determine the unit according to the determining unit Determine the device capability information and add a new command line to the target command.
  • the determining unit is further configured to determine a device type and a device model that include the first repeater in the hardware device capability information base; Used to deliver service configuration data to the first forwarder.
  • the sending unit is further configured to send a registration success response to the first forwarder, and deliver the service configuration data to the first forwarder.
  • the receiving unit is further configured to receive a service request from an upper layer application
  • the sending unit is further configured to: according to the service request received by the receiving unit, The service configuration data is sent to the second forwarder, and the second forwarder is successfully connected to the forwarder of the SDN system before the first forwarder is powered on.
  • the device capability information is an XML file that uses the YANG model; the device capability information includes at least one of the following: device information of the first repeater, Board information supported by a repeater.
  • the device information may include at least one of the following: device type, device model, device description, device capability set, number of slots, and supported.
  • Slot information can include at least one of the following: slot ID and slot type.
  • the board information can include at least one of the following: board type, board name, board description, board capability set, and The port number of the board and the port information of the board.
  • the port information of the board can include at least one of the following: port ID, port type, and port description.
  • a fourth aspect of the embodiments of the present invention provides a repeater, including: a sending unit, a receiving unit, and an acquiring unit, and a sending unit, configured to send registration information to the SDN controller, where the registration information includes a device type of the first repeater and a device type, a receiving unit, configured to receive a PnP data request from the SDN controller, the PnP data request is used to request the first forwarder to report the device capability information, the acquiring unit is configured to obtain the device capability information, and the sending unit is further configured to The SDN controller sends the device capability information acquired by the acquiring unit.
  • the receiving unit is further configured to receive a registration success response from the SDN controller, and receive service configuration data from the SDN controller.
  • the device capability information is an XML file that uses a YANG model; the device capability information includes at least one of the following: device information of the first repeater, Board information supported by a repeater.
  • the device information may include at least one of the following: device type, device model, device description, device capability set, number of slots, and supported.
  • Slot information can include at least one of the following: slot ID and slot type.
  • the board information can include at least one of the following: board type, board name, board description, board capability set, and The port number of the board and the port information of the board.
  • the port information of the board can include at least one of the following: port ID, port type, and port description.
  • a fifth aspect of the embodiments of the present invention provides an SDN controller, including: at least one processor, a memory, a communication interface, and a communication bus;
  • the at least one processor is connected to the memory and the communication interface through a communication bus, and the memory is configured to store the computer execution instructions.
  • the processor executes the memory storage computer execution instructions to enable the SDN controller to perform the first aspect or the first A repeater network identification method as described in any of the possible implementations of the invention.
  • a sixth aspect of the embodiments of the present invention provides a repeater, including: at least one processor, a memory, a communication interface, and a communication bus;
  • At least one processor is coupled to the memory and the communication interface via a communication bus, the memory is configured to store the computer execution instructions, and when the repeater is running, the processor executes the memory stored computer execution instructions to cause the repeater to perform the second aspect or the second The repeater network identification method of any of the possible implementations of the aspect.
  • a seventh aspect of the embodiments of the present invention provides a computer storage medium for storing computer software instructions used by the SDN controller, the computer software instructions including a program designed to execute the above-described repeater network identification method.
  • a computer storage medium for storing computer software instructions for use in the forwarder, the computer software instructions comprising a program designed to execute the forwarder network identification method.
  • FIG. 1 is a schematic diagram of a typical architecture of an SDN provided by the prior art
  • FIG. 2 is a simplified schematic diagram of an SDN system to which an embodiment of the present invention is applied according to an embodiment of the present invention
  • FIG. 3 is a schematic structural diagram of an SDN controller according to an embodiment of the present invention.
  • FIG. 4 is a schematic structural diagram of a repeater according to an embodiment of the present invention.
  • FIG. 5 is a flowchart of a method for identifying a network access of a repeater according to an embodiment of the present invention
  • FIG. 6 is a flowchart of another method for identifying a network access of a repeater according to an embodiment of the present invention.
  • FIG. 7 is a schematic structural diagram of an SDN controller according to an embodiment of the present invention.
  • FIG. 8 is a schematic structural diagram of another SDN controller according to an embodiment of the present disclosure.
  • FIG. 9 is a schematic structural diagram of a repeater according to an embodiment of the present disclosure.
  • FIG. 10 is a schematic structural diagram of another repeater according to an embodiment of the present invention.
  • the present invention provides a method for identifying a network access of a forwarder, which is an SDN controller, in order to solve the problem of affecting ongoing network services and high network access costs when accessing a new forwarder in an existing SDN system.
  • Receiving registration information from the first repeater where the registration information may include a device type and a device model of the first repeater, and the SDN controller does not include the device type and device model of the first forwarder in determining the hardware device capability information base.
  • the SDN controller can send the PnP data to the repeater when determining the device type and the device model of the repeater in the hardware device capability information base.
  • the request can accurately know the device capability information of the newly-connected transponder. That is, when a new transponder is accessed, the SDN controller does not need to be upgraded, and the SDN controller can recognize the new incoming transponder, thereby solving the problem.
  • the problem of affecting ongoing network services and high network access costs is high.
  • the SDN system may include an SDN controller 11 and a repeater 12.
  • the number of repeaters 12 is n+1, wherein the n+1th repeater 12 is a repeater of the new access SDN system, and the first-nth repeater 12 A repeater that has been accessed in the SDN system before the n+1th repeater 12 accesses the SDN system.
  • the embodiment of the present invention is also applicable to the scenario where the accessed repeater does not exist in the SDN system before the n+1th repeater 12 accesses the SDN system.
  • the forwarder of the new access SDN system may be the forwarder that accesses the SDN system for the first time, or may be the repeater that resets and restarts.
  • the SDN controller 11 is deployed centrally, and is mainly responsible for processing the infrastructure layer resources and maintaining the network topology. Specifically, the SDN controller 11 is mainly used to manage the repeater 12, for example, configuring service data for the repeater 12, and performing management operations such as offline addition and deletion on the repeater 12.
  • the repeater 12 may specifically be a network unit such as a switch or a router.
  • the repeater 12 can perform operations such as data processing, data forwarding, and the like based on the flow table delivered by the SDN controller 11.
  • the SDN controller 11 and the repeater 12 can communicate with each other through the openflow protocol and the netconf protocol.
  • FIG. 3 is a schematic diagram of a composition of an SDN controller according to an embodiment of the present invention.
  • the SDN controller may include at least one processor 21, a memory 22, a communication interface 23, and a communication bus 24.
  • the processor 21 is a control center of the SDN controller, and may be a processor or a collective name of a plurality of processing elements.
  • the processor 21 is a central processing unit (CPU), may be an application specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of the present invention.
  • CPU central processing unit
  • ASIC application specific integrated circuit
  • microprocessors Digital Signal Processors, DSPs
  • FPGAs Field Programmable Gate Arrays
  • the processor 21 can perform various functions of the SDN controller by running or executing a software program stored in the memory 22 and calling data stored in the memory 22.
  • processor 21 may include one or more CPUs, such as CPU0 and CPU1 shown in FIG.
  • the SDN controller can include multiple processors, such as processor 21 and processor 25 shown in FIG.
  • processors can be a single core processor (CPU) or a multi-core processor (multi-CPU).
  • a processor herein may refer to one or more devices, circuits, and/or processing cores for processing data, such as computer program instructions.
  • the memory 22 can be a Read-Only Memory (ROM) or other type of static storage device that can store static information and instructions, a Random Access Memory (RAM) or other type that can store information and instructions.
  • ROM Read-Only Memory
  • RAM Random Access Memory
  • Memory 22 may be present independently and coupled to processor 21 via communication bus 24. The memory 22 can also be integrated with the processor 21.
  • the memory 22 is used to store a software program that executes the solution of the present invention, and is controlled by the processor 21.
  • the communication interface 23 uses a device such as any transceiver for communicating with other devices or communication networks, such as Ethernet, Radio Access Network (RAN), Wireless Local Area Networks (WLAN), etc. .
  • the communication interface 23 may include a receiving unit that implements a receiving function, and a transmitting unit that implements a transmitting function.
  • the communication bus 24 may be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus.
  • ISA Industry Standard Architecture
  • PCI Peripheral Component Interconnect
  • EISA Extended Industry Standard Architecture
  • the bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 3, but it does not mean that there is only one bus or one type of bus.
  • the device structure shown in FIG. 3 does not constitute a limitation to the SDN controller, and may include more or less components than those illustrated, or some components may be combined, or different component arrangements.
  • FIG. 4 is a schematic diagram of a composition of a repeater according to an embodiment of the present invention.
  • the repeater may include at least one processor 31, a memory 32, a communication interface 33, and a communication bus 34.
  • the processor 31 is a control center of the repeater, and may be a processor or a collective name of a plurality of processing elements.
  • processor 31 is a CPU, which may be an ASIC, or one or more integrated circuits configured to implement embodiments of the present invention, such as one or more DSPs, or one or more FPGAs.
  • the processor 31 can perform various functions of the repeater by running or executing a software program stored in the memory 32 and calling data stored in the memory 32.
  • processor 31 may include one or more CPUs, such as CPU0 and CPU1 shown in FIG.
  • the repeater can include multiple processors, such as processor 31 and processor 35 shown in FIG. Each of these processors can be a single-CPU or a multi-CPU.
  • a processor herein may refer to one or more devices, circuits, and/or processing cores for processing data, such as computer program instructions.
  • Memory 32 may be a ROM or other type of static storage device that may store static information and instructions, RAM or other types of dynamic storage devices that may store information and instructions, or may be EEPROM, CD-ROM or other optical disk storage, optical disk storage. (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or can be used to carry or store desired program code in the form of instructions or data structures and can be Any other media accessed, but not limited to this.
  • Memory 32 may be present independently and coupled to processor 31 via communication bus 34. The memory 32 can also be integrated with the processor 31.
  • the memory 32 is used to store a software program that executes the solution of the present invention, and is controlled by the processor 31 for execution.
  • the communication interface 33 may include a receiving unit that implements a receiving function, and a transmitting unit that implements a transmitting function.
  • the communication bus 34 can be an ISA bus, a PCI bus, or an EISA bus.
  • the bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 4, but it does not mean that there is only one bus or one type of bus.
  • the device structure shown in FIG. 4 does not constitute a definition of a transponder, and may include more or less components than those illustrated, or some components may be combined, or different component arrangements.
  • FIG. 5 is a flowchart of a method for identifying a network access of a repeater according to an embodiment of the present invention. As shown in FIG. 5, the method may include:
  • the first forwarder sends registration information to the SDN controller.
  • the registration information includes a device type and a device model of the first repeater.
  • the first repeater may send registration information to the SDN controller after power-on is completed.
  • the SDN controller receives registration information from the first repeater.
  • the SDN controller determines, in the hardware device capability information database, a device type and a device model that do not include the first repeater.
  • the SDN controller sends a PnP data request to the first forwarder.
  • the PnP data request is used to request the first repeater to report device capability information.
  • the first repeater receives the PnP data request from the SDN controller.
  • the first forwarder obtains device capability information, and sends device capability information to the SDN controller.
  • the SDN controller receives device capability information from the first repeater.
  • the SDN controller receives the registration information of the first forwarder, and when determining that the hardware device capability information database does not include the device type and device model of the first forwarder included in the registration information And transmitting, to the first forwarder, a PnP data request for requesting the first repeater to report the device capability information, and receiving device capability information from the first forwarder.
  • the SDN controller can send the PnP data to the repeater when determining the device type and the device model of the repeater in the hardware device capability information base. The request can accurately know the device capability information of the newly-connected transponder.
  • the SDN controller does not need to be upgraded, and the SDN controller can recognize the new incoming transponder, thereby solving the problem that the impact is being performed when accessing the new transponder in the existing SDN system.
  • FIG. 6 is a flowchart of another method for identifying a network of a transponder according to an embodiment of the present invention. As shown in FIG. 6, the method may include:
  • the first forwarder sends registration information to the SDN controller.
  • the registration information includes a device type and a device model of the first repeater.
  • the first repeater is a repeater that newly accesses the SDN system.
  • the first repeater may send registration information including the device type and the device model of the first repeater to the SDN controller through the openflow channel after the power-on is completed.
  • the new forwarder can send registration information to the SDN controller through the openflow channel.
  • the transponder can send registration information to the SDN controller through the openflow channel after the power is turned on.
  • the registration information may be sent to the SDN controller in the form of an Internet Protocol (IP) message.
  • IP Internet Protocol
  • the SDN controller receives registration information from the first repeater.
  • the SDN controller can receive registration information from the first repeater through the openflow channel.
  • the SDN controller determines a device type and a device model that do not include the first repeater in the hardware device capability information base.
  • the SDN controller may perform comparative analysis on the registration information reported by the first forwarder to determine whether the first forwarder is included in the hardware device capability information base. The device type and device model to confirm whether the SDN system supports the first repeater.
  • the device type and device model of all supported transponders are pre-stored in the hardware device capability information base of the SDN controller.
  • the SDN controller can confirm whether the SDN system supports the first repeater by determining whether the hardware device capability information library includes the device type and the device model of the first repeater.
  • the SDN controller can confirm that the SDN system supports the first forwarder, and the SDN controller can go to the first forwarder.
  • Send business configuration data When the SDN controller determines that the device type and the device model of the first repeater are not included in the hardware device capability information base, the SDN controller can confirm that the first forwarder is not supported by the SDN system, and the following step 504 can be performed.
  • the SDN controller sends a PnP data request to the first forwarder.
  • the PnP data request is used to request the first repeater to report device capability information.
  • the SDN controller may send the PnP data for requesting the device capability information of the first forwarder to the first forwarder. request.
  • the PnP data request may be sent to the first repeater in the form of an IP packet.
  • the first repeater receives the PnP data request from the SDN controller.
  • the first forwarder obtains device capability information, and sends device capability information to the SDN controller.
  • the first forwarder may collect its own device data to obtain device capability information, and send the acquired device capability information to the SDN controller.
  • the device capability information may be an XML file using a YANG model. That is to say, after the first forwarder obtains its own device capability information, the YANG model can be used to generate an XML file of its own device capability information and report it to the SDN controller.
  • the device capability information may include at least one of the following: device information of the first repeater, and board information supported by the first repeater.
  • the device information may include at least one of the following: device type, device model, device description, device capability set, number of slots, and supported slot information.
  • the slot information may include at least one of the following: slot ID and slot type.
  • the board information can include at least one of the following types: board type, board name, board description, board capability set, number of ports on the board, and port information of the board.
  • Port information of the board can be It includes at least one of the following: port ID, port type, and port description.
  • the description of the device data included in the device capability information is shown in Table 1.
  • the SDN controller receives device capability information from the first repeater.
  • the SDN controller may parse the device capability information of the first forwarder, and refresh the system rule and the northbound configuration interface according to the analysis result. Perform the following steps 508-509.
  • the SDN controller adds the device capability information to the hardware device capability information base.
  • the SDN controller may refresh the related basic data according to the device capability information of the first repeater, that is, the device capability information of the first forwarder is added in the hardware device capability information database, so that the SDN system can support the first forwarder.
  • the SDN controller determines the target command according to the device capability information, and adds a new command line to the target command according to the device capability information.
  • the SDN controller may refresh the northbound interface according to the device capability information of the first repeater. Specifically, the SDN controller may determine the target command according to the device capability information of the first repeater, and add a new command line to the target command according to the device capability information of the first forwarder. For example, the target command determined according to the device capability information of the first repeater is add-device-board deviceId frameid/slotid ⁇ HS901GPBA
  • the northbound interface may include at least one of the following: a web interface, a Representational State Transfer (REST), a Transaction Language-1 (TL1), and an American Standard Code for American Standard Code for Information Interchange, ASCII), Command-Line Interface (CLI).
  • REST Representational State Transfer
  • T1 Transaction Language-1
  • ASCII American Standard Code for American Standard Code for Information Interchange
  • CLI Command-Line Interface
  • step 508 and step 509 is not sequential. That is, step 508 may be performed first, and then step 509 may be performed; or step 509 may be performed first, and then step 508 may be performed; or step 508 and step 509 may be performed simultaneously.
  • the embodiment of the present invention does not specifically limit the order of execution of step 508 and step 509.
  • the SDN controller sends a registration success response to the first forwarder, and delivers service configuration data to the first forwarder.
  • the first repeater receives a registration success response from the SDN controller, and receives service configuration data from the SDN controller.
  • the original repeater in the SDN system can still work normally, that is, the following steps 512-513 are performed.
  • the SDN controller receives a service request from an upper layer application.
  • the SDN controller sends the service configuration data to the second forwarder according to the service request.
  • the second repeater is a repeater that has successfully accessed the SDN system before the first repeater is powered on.
  • the SDN controller receives the registration information of the first forwarder, and when determining that the hardware device capability information database does not include the device type and device model of the first forwarder included in the registration information And transmitting, to the first forwarder, a PnP data request for requesting the first repeater to report the device capability information, and receiving device capability information from the first forwarder.
  • the SDN controller can send the PnP data to the repeater when determining the device type and the device model of the repeater in the hardware device capability information base. The request can accurately know the device capability information of the newly-connected transponder.
  • the SDN controller does not need to be upgraded, and the SDN controller can recognize the new incoming transponder, thereby solving the problem that the impact is being performed when accessing the new transponder in the existing SDN system.
  • each network element such as an SDN controller and a repeater
  • each network element includes hardware structures and/or software modules for performing respective functions in order to implement the above functions.
  • the present invention can be implemented in hardware or hardware, in conjunction with the algorithm steps of the various examples described in the embodiments disclosed herein.
  • a combination of computer software is implemented. Whether a function is implemented in hardware or computer software to drive hardware depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods for implementing the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present invention.
  • the embodiment of the present invention may divide the function module of the SDN controller and the repeater according to the foregoing method.
  • each function module may be divided according to each function, or two or more functions may be integrated into one processing module.
  • the above integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of the module in the embodiment of the present invention is schematic, and is only a logical function division, and the actual implementation may have another division manner.
  • FIG. 7 shows a possible composition diagram of the SDN controller involved in the foregoing and the embodiment, and the SDN controller may include: receiving The unit 61, the determining unit 62, and the transmitting unit 63.
  • the receiving unit 61 is configured to support the SDN controller to perform step 402 and step 407 in the repeater network identification method shown in FIG. 5, and step 502, step 507 and step in the repeater network identification method shown in FIG. 512.
  • the determining unit 62 is configured to support the SDN controller to perform step 403 in the method for identifying the network access of the repeater shown in FIG. 5, and according to the device capability information in step 503 and step 509 in the method for identifying the network access of the repeater shown in FIG. Determine the target command.
  • the sending unit 63 is configured to support the SDN controller to perform step 404 in the repeater network identification method shown in FIG. 5, step 504, step 510, and step 513 in the repeater network identification method shown in FIG. 6.
  • the SDN controller may further include: an adding unit 64.
  • the adding unit 64 is configured to support the SDN controller to perform the step 508 in the repeater network identification method shown in FIG. 6 and the device capability information in the step 509, and add a new command line in the target command.
  • the SDN controller provided by the embodiment of the present invention is configured to perform the above-mentioned forwarder network identification method, so that the same effect as the above-mentioned repeater network identification method can be achieved.
  • FIG. 8 shows another possible composition diagram of the SDN controller involved in the above embodiment.
  • the SDN controller includes a processing module 71 and a communication module 72.
  • the processing module 71 is configured to perform control management on the actions of the SDN controller.
  • the processing module 71 is configured to support the SDN controller to perform step 403 in FIG. 5, step 503, step 508, step 509, and/or in FIG. Other processes for the techniques described herein.
  • Communication module 72 is used to support communication between the SDN controller and other network entities, such as communication with the functional modules or network entities shown in FIG. 2, FIG. 4, FIG. 9, or FIG.
  • the communication module 72 is configured to execute the SDN controller to perform step 402, step 404, and step 407 in FIG. 5, step 502, step 504, step 507, step 510, step 512, and step 513 in FIG.
  • the SDN controller may also include a storage module 73 for storing program code and data of the SDN controller.
  • the processing module 71 can be a processor or a controller. It is possible to implement or carry out the various illustrative logical blocks, modules and circuits described in connection with the present disclosure.
  • the processor can also be a combination of computing functions, for example, including one or more microprocessor combinations, a combination of a DSP and a microprocessor, and the like.
  • the communication module 72 can be a transceiver, a transceiver circuit, a communication interface, or the like.
  • the storage module 73 can be a memory.
  • the SDN controller may be the SDN controller shown in FIG.
  • FIG. 9 is a schematic diagram showing a possible composition of the repeater involved in the foregoing and the embodiment.
  • the repeater may include: a sending unit 81.
  • the sending unit 81 is configured to support the repeater to perform the device capability information sent to the SDN controller in steps 401 and 406 in the repeater network identification method shown in FIG. 5, and the repeater network identification method shown in FIG. In step 501 and step 506, the device capability information is sent to the SDN controller.
  • the receiving unit 82 is configured to support the repeater to perform step 405 in the repeater network identification method shown in FIG. 5, and step 505 and step 511 in the repeater network identification method shown in FIG. 6.
  • the obtaining unit 83 is configured to support the forwarding device to perform the acquiring device capability information in step 406 in the repeater network identification method shown in FIG. 5, and the acquiring device capability in step 506 in the repeater network identification method shown in FIG. information.
  • the transponder provided by the embodiment of the present invention is configured to perform the above-mentioned transponder network identification method, so that the same effect as the above-mentioned transponder network access identification method can be achieved.
  • Fig. 10 shows another possible composition diagram of the repeater involved in the above embodiment.
  • the repeater includes a processing module 91 and a communication module 92.
  • the processing module 91 is configured to control and manage the actions of the repeater.
  • the processing module 91 is configured to support the repeater to perform the acquiring device capability information in step 406 of FIG. 5, the device capability information in step 506 in FIG. 6, and/or other processes for the techniques described herein.
  • Communication module 92 is used to support communication between the repeater and other network entities, such as communication with the functional modules or network entities shown in FIG. 2, FIG. 3, FIG. 7, or FIG.
  • the communication module 92 is configured to perform, in the step 401, the step 405, and the step 406 in FIG. 5, the device capability information is sent to the SDN controller, in step 501, step 505, and step 506 in FIG. Send device capability information to the SDN controller, step 511.
  • the repeater may further include a storage module 93 for storing program codes and data of the repeater.
  • the processing module 91 can be a processor or a controller. It is possible to implement or carry out the various illustrative logical blocks, modules and circuits described in connection with the present disclosure.
  • the processor can also be a combination of computing functions, for example, including one or more microprocessor combinations, a combination of a DSP and a microprocessor, and the like.
  • the communication module 92 can be a transceiver, a transceiver circuit, a communication interface, or the like.
  • the storage module 93 can be a memory.
  • the repeater When the processing module 91 is a processor, the communication module 92 is a communication interface, and the storage module 93 is a memory, the repeater according to the embodiment of the present invention may be the repeater shown in FIG.
  • the disclosed apparatus and method may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the modules or units is only a logical function division.
  • there may be another division manner for example, multiple units or components may be used.
  • the combination may be integrated into another device, or some features may be ignored or not performed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may be one physical unit or multiple physical units, that is, may be located in one place, or may be distributed to multiple different places. . Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.
  • the integrated unit if implemented in the form of a software functional unit and sold or used as a standalone product, may be stored in a readable storage medium.
  • the technical solution of the embodiments of the present invention may contribute to the prior art or all or part of the technical solution may be embodied in the form of a software product stored in a storage medium.
  • a number of instructions are included to cause a device (which may be a microcontroller, chip, etc.) or a processor to perform all or part of the steps of the methods described in various embodiments of the present invention.
  • the foregoing storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a ROM, a RAM, a magnetic disk, or an optical disk.

Landscapes

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

Abstract

本发明实施例公开了一种转发器入网识别方法、SDN控制器及转发器，涉及通信领域，解决了在现有SDN系统中接入新的转发器时，影响正在进行的网络业务且入网成本高的问题。具体方案为：SDN控制器接收来自第一转发器的注册信息，注册信息包括第一转发器的设备类型和设备型号；SDN控制器根据第一转发器的设备类型和设备型号，确定SDN系统不支持第一转发器；SDN控制器向第一转发器发送PnP数据请求，PnP数据请求用于请求第一转发器上报设备能力信息；SDN控制器接收来自第一转发器的设备能力信息。本发明实施例用于转发器入网的过程中。

Description

一种转发器入网识别方法、SDN控制器及转发器 技术领域
本发明实施例涉及通信领域，尤其涉及一种转发器入网识别方法、SDN控制器及转发器。
背景技术
软件定义网络(Software Defined Network，SDN)是由美国斯坦福大学cleanslate研究组提出的一种新型网络架构，其核心技术开放流(openflow)通过将网络设备的控制面与数据面分离开来，从而实现了网络流量的灵活控制，为核心网络及应用的创新提供了良好的平台。如图1所示，SDN的典型架构分为三层：应用层(Application layer)、控制层(Control layer)和基础设施层(Infrastructure layer)。其中，应用层部署有SDN应用(SDN application)，控制层部署有SDN控制器(SDN controller)，其主要负责处理基础设施层资源的编排，维护网络拓扑等，基础设施层部署有网络单元(Network element)，如交换机、路由器等(下文统称为转发器)，其可以基于SDN控制器下发的流表进行数据的处理，数据的转发等。这种网络架构通过将网络控制和物理网络拓扑分离开来，摆脱了硬件对网络拓扑的限制，也就是说，若需要对网络拓扑进行调整、扩容或升级，只需对控制层进行相应的修改，而基础设施层中的网络单元则无需替换。这样，不仅能够节省大量的成本，还可以大大缩短网络拓扑的迭代周期。
在SDN场景下，为了提升性能，需要在原有SDN系统中不断接入新的转发器。且SDN场景下的转发器具有结构简单、生产门槛低、成本低、易集成等特点，因此，其可能由多家供应商进行生产，不同供应商生产的转发器的配置可能不同。这样，在原有SDN系统中接入新的转发器时，需要SDN控制器能够识别新接入的转发器。目前，在现有的SDN系统中，SDN控制器的软件是先发布的，因此，当有新的转发器接入现有的SDN系统中时，SDN控制器可能由于无法获知新入网的转发器的硬件、规格等信息，导致SDN控制器无法识别新入网的转发器，从而无法对其进行管理，如，控制界面无法显示新入网的转发器、无法为新入网的转发器配置业务数据、无法对新入网的转发器进行离线添加、删除等操作。现有技术的做法是：在新的转发器接入之前，先对SDN控制器进行升级，使得升级后的SDN控制器能够识别新接入的转发器，进而可以对该新接入的转发器进行管理。
现有技术中至少存在如下问题：由于在SDN场景下，SDN控制器一般是集中部署的，其同时管理着多台转发器，这就要求在对SDN控制器进行升级的过程中，暂停SDN控制器的服务，导致正在进行的网络业务受到影响。尤其在接入新的转发器频繁的场景，问题尤为突出，用户体验不好。并且，为了支持一个新接入的转发器而对SDN控制器进行升级，也会导致新设备入网时成本的增加。
发明内容
本发明实施例提供一种转发器入网识别方法、SDN控制器及转发器，解决了在现有SDN系统中接入新的转发器时，影响正在进行的网络业务且入网成本高的问题。
为达到上述目的，本发明实施例采用如下技术方案：
本发明实施例的第一方面，提供一种转发器入网识别方法，包括：
SDN控制器接收来自第一转发器的注册信息，该注册信息中可以包括第一转发器的设备类型和设备型号，SDN控制器在确定硬件设备能力信息库中未包含第一转发器的设备类型和设备型号时，向第一转发器发送即插即用(Plug n Play，PnP)数据请求，该PnP数据请求用于请求第一转发器上报设备能力信息，SDN控制器接收来自第一转发器的设备能力信息。
本发明实施例提供的转发器入网识别方法，SDN控制器接收第一转发器的注册信息，在确定硬件设备能力信息库中未包含注册信息中包括的第一转发器的设备类型和设备型号时，向第一转发器发送用于请求第一转发器上报设备能力信息的PnP数据请求，并接收来自第一转发器的设备能力信息。这样，在现有SDN系统中有新的转发器接入时，SDN控制器可以在确定硬件设备能力信息库中未包含该转发器的设备类型和设备型号时，通过向该转发器发送PnP数据请求，便可以准确获知新入网的转发器的设备能力信息。即在有新的转发器接入时，无需对SDN控制器进行升级，SDN控制器便可以识别新入网转发器，从而解决了在现有SDN系统中接入新的转发器时，影响正在进行的网络业务且入网成本高的问题。
结合第一方面，在一种可能的实现方式中，在SDN控制器接收来自第一转发器的设备能力信息之后，该转发器入网识别方法还可以包括：SDN控制器将设备能力信息添加在硬件设备能力信息库中。
结合第一方面和上述可能的实现方式，在另一种可能的实现方式中，为了能够实现对新入网的转发器的离线配置。在SDN控制器接收来自第一转发器的设备能力信息之后，该转发器入网识别方法还可以包括：SDN控制器根据设备能力信息，确定目标命令，并根据设备能力信息，在目标命令中添加新命令行。
结合第一方面和上述可能的实现方式，在另一种可能的实现方式中，该转发器入网识别方法还可以包括：SDN控制器确定硬件设备能力信息库中包含第一转发器的设备类型和设备型号；SDN控制器向第一转发器下发业务配置数据。
结合第一方面和上述可能的实现方式，在另一种可能的实现方式中，该转发器入网识别方法还可以包括：SDN控制器向第一转发器发送注册成功响应，并向第一转发器下发业务配置数据。
结合第一方面和上述可能的实现方式，在另一种可能的实现方式中，该转发器入网识别方法还可以包括：SDN控制器接收来自上层应用的业务请求，并根据业务请求，向第二转发器下发业务配置数据，第二转发器为在第一转发器上电完成之前，已成功接入SDN系统的转发器。
结合第一方面和上述可能的实现方式，在另一种可能的实现方式中，设备能力信息是采用YANG模型的可扩展标记语言(Extensible Markup Language，XML)文件；设备能力信息可以包括以下至少一种：第一转发器的设备信息、第一转发器支持的单板信息。
结合第一方面和上述可能的实现方式，在另一种可能的实现方式中，设备信息可以包括以下至少一种：设备类型、设备型号、设备描述、设备能力集、槽位个数、支持的槽位信息；槽位信息可以包括以下至少一种：槽位标识(Identify，ID)、槽位类型；单板信息可以包括以下至少一种：单板类型、单板名称、单板描述、单板能力集、单板的端口个数、单板的端口信息；单板的端口信息可以包括以下至少一种：端口ID、端口类型、端口描述。
本发明实施例的第二方面，提供一种转发器入网识别方法，包括：
第一转发器向SDN控制器发送注册信息，该注册信息可以包括第一转发器的设备类型和设备型号；第一转发器接收来自SDN控制器的PnP数据请求，该PnP数据请求用于请求第一转发器上报设备能力信息；第一转发器获取设备能力信息，并向SDN控制器发送设备能力信息。
本发明实施例提供的转发器入网识别方法，第一转发器向SDN控制器发送包括第一转发器的设备类型和设备型号的注册信息，并在接收到来自SDN控制器的PnP数据请求之后，获取自身的设备能力信息，并向SDN控制器发送该设备能力信息。这样，在现有SDN系统中有新的转发器接入时，新入网的转发器在接收到第一转发器发送PnP数据请求之后，通过向SDN控制器上报自身的设备能力信息，以使得无需对SDN控制器进行升级，SDN控制器便可以准确获知新入网的转发器的设备能力信息，即SDN控制器便可以识别新入网转发器，从而解决了在现有SDN系统中接入新的转发器时，影响正在进行的网络业务且入网成本高的问题。
结合第二方面，在一种可能的实现方式中，该转发器入网识别方法还可以包括：第一转发器接收来自SDN控制器的注册成功响应，并接收来自SDN控制器的业务配置数据。
结合第二方面和上述可能的实现方式，在另一种可能的实现方式中，设备能力信息是采用YANG模型的XML文件；设备能力信息可以包括以下至少一种：第一转发器的设备信息、第一转发器支持的单板信息。
结合第二方面和上述可能的实现方式，在另一种可能的实现方式中，设备信息可以包括以下至少一种：设备类型、设备型号、设备描述、设备能力集、槽位个数、支持的槽位信息；槽位信息可以包括以下至少一种：槽位ID、槽位类型；单板信息可以包括以下至少一种：单板类型、单板名称、单板描述、单板能力集、单板的端口个数、单板的端口信息；单板的端口信息可以包括以下至少一种：端口ID、端口类型、端口描述。
本发明实施例的第三方面，提供一种SDN控制器，包括：接收单元、确定单元和发送单元；接收单元，用于接收来自第一转发器的注册信息，注册信息包括第一转发器的设备类型和设备型号；确定单元，用于确定硬件设备能力信息库中未包含接收单元接收到的第一转发器的设备类型和设备型号；发送单元，用于向第一转发器发送PnP数据请求，PnP数据请求用于请求第一转发器上报设备能力信息；接收单元，还用于接收来自第一转发器的设备能力信息。
结合第三方面，在一种可能的实现方式中，还包括：添加单元，用于将接收单元接到的设备能力信息添加在硬件设备能力信息库中。
结合第三方面和上述可能的实现方式，在另一种可能的实现方式中，确定单元，还用于根据接收单元接收到的设备能力信息，确定目标命令；添加单元，还用于根据确定单元确定出的设备能力信息，在目标命令中添加新命令行。
结合第三方面和上述可能的实现方式，在另一种可能的实现方式中，确定单元，还用于确定硬件设备能力信息库中包含第一转发器的设备类型和设备型号；发送单元，还用于向第一转发器下发业务配置数据。
结合第三方面和上述可能的实现方式，在另一种可能的实现方式中，发送单元，还用于向第一转发器发送注册成功响应，并向第一转发器下发业务配置数据。
结合第三方面和上述可能的实现方式，在另一种可能的实现方式中，接收单元，还用于接收来自上层应用的业务请求；发送单元，还用于根据接收单元接收到的业务请求，向第二转发器下发业务配置数据，第二转发器为在第一转发器上电完成之前，已成功接入SDN系统的转发器。
结合第三方面和上述可能的实现方式，在另一种可能的实现方式中，设备能力信息是采用YANG模型的XML文件；设备能力信息包括以下至少一种：第一转发器的设备信息、第一转发器支持的单板信息。
结合第三方面和上述可能的实现方式，在另一种可能的实现方式中，设备信息可以包括以下至少一种：设备类型、设备型号、设备描述、设备能力集、槽位个数、支持的槽位信息；槽位信息可以包括以下至少一种：槽位ID、槽位类型；单板信息可以包括以下至少一种：单板类型、单板名称、单板描述、单板能力集、单板的端口个数、单板的端口信息；单板的端口信息可以包括以下至少一种：端口ID、端口类型、端口描述。
本发明实施例的第四方面，提供一种转发器，包括：发送单元、接收单元和获取单元；发送单元，用于向SDN控制器发送注册信息，注册信息包括第一转发器的设备类型和设备型号；接收单元，用于接收来自SDN控制器的PnP数据请求，PnP数据请求用于请求第一转发器上报设备能力信息；获取单元，用于获取设备能力信息；发送单元，还用于向SDN控制器发送获取单元获取到的设备能力信息。
结合第四方面，在一种可能的实现方式中，接收单元，还用于接收来自SDN控制器的注册成功响应，接收来自SDN控制器的业务配置数据。
结合第四方面和上述可能的实现方式，在另一种可能的实现方式中，设备能力信息是采用YANG模型的XML文件；设备能力信息包括以下至少一种：第一转发器的设备信息、第一转发器支持的单板信息。
结合第四方面和上述可能的实现方式，在另一种可能的实现方式中，设备信息可以包括以下至少一种：设备类型、设备型号、设备描述、设备能力集、槽位个数、支持的槽位信息；槽位信息可以包括以下至少一种：槽位ID、槽位类型；单板信息可以包括以下至少一种：单板类型、单板名称、单板描述、单板能力集、单板的端口个数、单板的端口信息；单板的端口信息可以包括以下至少一种：端口ID、端口类型、端口描述。
本发明实施例的第五方面，提供一种SDN控制器，包括：至少一个处理器、存储器、通信接口、通信总线；
至少一个处理器与存储器、通信接口通过通信总线连接，存储器用于存储计算机执行指令，当SDN控制器运行时，处理器执行存储器存储的计算机执行指令，以使SDN控制器执行第一方面或第一方面的可能的实现方式中任一所述的转发器入网识别方法。
本发明实施例的第六方面，提供一种转发器，包括：至少一个处理器、存储器、通信接口、通信总线；
至少一个处理器与存储器、通信接口通过通信总线连接，存储器用于存储计算机执行指令，当转发器运行时，处理器执行存储器存储的计算机执行指令，以使转发器执行如第二方面或第二方面的可能的实现方式中任一所述的转发器入网识别方法。
本发明实施例的第七方面，提供一种计算机存储介质，用于存储上述SDN控制器所用的计算机软件指令，该计算机软件指令包含用于执行上述转发器入网识别方法所设计的程序。
本发明实施例的第八方面，提供一种计算机存储介质，用于存储上述转发器所用的计算机软件指令，该计算机软件指令包含用于执行上述转发器入网识别方法所设计的程序。
附图说明
图1为现有技术提供的一种SDN的典型架构示意图；
图2为本发明实施例提供的一种应用本发明实施例的SDN系统的简化示意图；
图3为本发明实施例提供的一种SDN控制器的组成示意图；
图4为本发明实施例提供的一种转发器的组成示意图；
图5为本发明实施例提供的一种转发器入网识别方法的流程图；
图6为本发明实施例提供的另一种转发器入网识别方法的流程图；
图7为本发明实施例提供的一种SDN控制器的组成示意图；
图8为本发明实施例提供的另一种SDN控制器的组成示意图；
图9为本发明实施例提供的一种转发器的组成示意图；
图10为本发明实施例提供的另一种转发器的组成示意图。
具体实施方式
为了解决在现有SDN系统中接入新的转发器时，影响正在进行的网络业务且入网成本高的问题，本发明实施例提供一种转发器入网识别方法，其基本原理是：SDN控制器接收来自第一转发器的注册信息，该注册信息中可以包括第一转发器的设备类型和设备型号，SDN控制器在确定硬件设备能力信息库中未包含第一转发器的设备类型和设备型号时，向第一转发器发送PnP数据请求，该PnP数据请求用于请求第一转发器上报设备能力信息，SDN控制器接收来自第一转发器的设备能力信息。这样，在现有SDN系统中有新的转发器接入时，SDN控制器可以在确定硬件设备能力信息库中未包含该转发器的设备类型和设备型号时，通过向该转发器发送PnP数据请求，便可以准确获知新入网的转发器的设备能力信息。即在有新的转发器接入时，无需对SDN控制器进行升级，SDN控制器便可以识别新入网转发器，从而解决 了在现有SDN系统中接入新的转发器时，影响正在进行的网络业务且入网成本高的问题。
下面将结合附图对本发明实施例的实施方式进行详细描述。
图2示出的是可以应用本发明实施例的SDN系统的简化示意图。如图2所示，该SDN系统可以包括：SDN控制器11和转发器12。
另外，假设在该SDN系统中，转发器12的个数为n+1，其中，第n+1个转发器12为新接入SDN系统的转发器，第1个-第n个转发器12为在第n+1个转发器12接入SDN系统之前，SDN系统中已接入的转发器。当然，本发明实施例也同样适用于在第n+1个转发器12接入SDN系统之前，SDN系统中不存在已接入的转发器的场景。需要说明的是，在本发明实施例中，新接入SDN系统的转发器可以是第一次接入SDN系统的转发器，也可以是复位重启的转发器。
其中，SDN控制器11集中布放，主要负责处理基础设施层资源的编排，维护网络拓扑。具体的，SDN控制器11主要用于对转发器12进行管理，如，为转发器12配置业务数据，对转发器12进行离线添加、删除等管理操作。
转发器12，具体的可以是交换机、路由器等网络单元。转发器12可以基于SDN控制器11下发的流表进行数据的处理，数据的转发等操作。
SDN控制器11和转发器12之间可以通过openflow协议和netconf协议进行通信。
图3为本发明实施例提供的一种SDN控制器的组成示意图，如图3所示，SDN控制器可以包括至少一个处理器21，存储器22、通信接口23、通信总线24。
下面结合图3对SDN控制器的各个构成部件进行具体的介绍：
处理器21是SDN控制器的控制中心，可以是一个处理器，也可以是多个处理元件的统称。例如，处理器21是一个中央处理器(Central Processing Unit，CPU)，也可以是特定集成电路(Application Specific Integrated Circuit，ASIC)，或者是被配置成实施本发明实施例的一个或多个集成电路，例如：一个或多个微处理器(Digital Signal Processor，DSP)，或，一个或者多个现场可编程门阵列(Field Programmable Gate Array，FPGA)。
其中，处理器21可以通过运行或执行存储在存储器22内的软件程序，以及调用存储在存储器22内的数据，执行SDN控制器的各种功能。
在具体的实现中，作为一种实施例，处理器21可以包括一个或多个CPU，例如图3中所示的CPU0和CPU1。
在具体实现中，作为一种实施例，SDN控制器可以包括多个处理器，例如图3中所示的处理器21和处理器25。这些处理器中的每一个可以是一个单核处理器(single-CPU)，也可以是一个多核处理器(multi-CPU)。这里的处理器可以指一个或多个设备、电路、和/或用于处理数据(例如计算机程序指令)的处理核。
存储器22可以是只读存储器(Read-Only Memory，ROM)或可存储静态信息和指令的其他类型的静态存储设备，随机存取存储器(Random Access Memory，RAM)或者可存储信息和指令的其他类型的动态存储设备，也可以是电可擦可编程只读存储器(Electrically Erasable Programmable Read-Only Memory，EEPROM)、只读光盘 (Compact Disc Read-Only Memory，CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器22可以是独立存在，通过通信总线24与处理器21相连接。存储器22也可以和处理器21集成在一起。
其中，所述存储器22用于存储执行本发明方案的软件程序，并由处理器21来控制执行。
通信接口23，使用任何收发器一类的装置，用于与其他设备或通信网络通信，如以太网，无线接入网(Radio Access Network，RAN)，无线局域网(Wireless Local Area Networks，WLAN)等。通信接口23可以包括接收单元实现接收功能，以及发送单元实现发送功能。
通信总线24，可以是工业标准体系结构(Industry Standard Architecture，ISA)总线、外部设备互连(Peripheral Component Interconnect，PCI)总线或扩展工业标准体系结构(Extended Industry Standard Architecture，EISA)总线等。该总线可以分为地址总线、数据总线、控制总线等。为便于表示，图3中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
图3中示出的设备结构并不构成对SDN控制器的限定，可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置。
图4为本发明实施例提供的一种转发器的组成示意图，如图4所示，转发器可以包括至少一个处理器31、存储器32、通信接口33、通信总线34。
下面结合图4对转发器的各个构成部件进行具体的介绍：
处理器31是转发器的控制中心，可以是一个处理器，也可以是多个处理元件的统称。例如，处理器31是一个CPU，也可以是ASIC，或者是被配置成实施本发明实施例的一个或多个集成电路，例如：一个或多个DSP，或，一个或者多个FPGA。
其中，处理器31可以通过运行或执行存储在存储器32内的软件程序，以及调用存储在存储器32内的数据，执行转发器的各种功能。
在具体的实现中，作为一种实施例，处理器31可以包括一个或多个CPU，例如图4中所示的CPU0和CPU1。
在具体实现中，作为一种实施例，转发器可以包括多个处理器，例如图4中所示的处理器31和处理器35。这些处理器中的每一个可以是一个single-CPU，也可以是一个multi-CPU。这里的处理器可以指一个或多个设备、电路、和/或用于处理数据(例如计算机程序指令)的处理核。
存储器32可以是ROM或可存储静态信息和指令的其他类型的静态存储设备，RAM或者可存储信息和指令的其他类型的动态存储设备，也可以是EEPROM、CD-ROM或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器32可以是独立存在，通过通信总线34与处理器31相连接。存储器32也可以和处理器31集成在一起。
其中，所述存储器32用于存储执行本发明方案的软件程序，并由处理器31来控制执行。
通信接口33，使用任何收发器一类的装置，用于与其他设备或通信网络通信，如以太网，RAN，WLAN等。通信接口33可以包括接收单元实现接收功能，以及发送单元实现发送功能。
通信总线34，可以是ISA总线、PCI总线或EISA总线等。该总线可以分为地址总线、数据总线、控制总线等。为便于表示，图4中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
图4中示出的设备结构并不构成对转发器的限定，可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置。
图5为本发明实施例提供的一种转发器入网识别方法的流程图，如图5所示，该方法可以包括：
401、第一转发器向SDN控制器发送注册信息。
其中，该注册信息包括第一转发器的设备类型和设备型号。示例性的，第一转发器可以在上电完成之后，向SDN控制器发送注册信息。
402、SDN控制器接收来自第一转发器的注册信息。
403、SDN控制器确定硬件设备能力信息库中未包含第一转发器的设备类型和设备型号。
404、SDN控制器向第一转发器发送PnP数据请求。
其中，该PnP数据请求用于请求第一转发器上报设备能力信息。
405、第一转发器接收来自SDN控制器的PnP数据请求。
406、第一转发器获取设备能力信息，并向SDN控制器发送设备能力信息。
407、SDN控制器接收来自第一转发器的设备能力信息。
本发明实施例提供的转发器入网识别方法，SDN控制器接收第一转发器的注册信息，在确定硬件设备能力信息库中未包含注册信息中包括的第一转发器的设备类型和设备型号时，向第一转发器发送用于请求第一转发器上报设备能力信息的PnP数据请求，并接收来自第一转发器的设备能力信息。这样，在现有SDN系统中有新的转发器接入时，SDN控制器可以在确定硬件设备能力信息库中未包含该转发器的设备类型和设备型号时，通过向该转发器发送PnP数据请求，便可以准确获知新入网的转发器的设备能力信息。即在有新的转发器接入时，无需对SDN控制器进行升级，SDN控制器便可以识别新入网转发器，从而解决了在现有SDN系统中接入新的转发器时，影响正在进行的网络业务且入网成本高的问题。
图6为本发明实施例提供的另一种转发器入网识别方法的流程图，如图6所示，该方法可以包括：
501、第一转发器向SDN控制器发送注册信息。
其中，该注册信息包括第一转发器的设备类型和设备型号。第一转发器是新接入SDN系统的转发器。示例性的，第一转发器可以在上电完成之后，通过openflow通道向SDN控制器发送包括第一转发器的设备类型和设备型号的注册信息。
例如，假设现有的SDN系统中需要引入一台新的转发器，此时，在这台新的转 发器接入SDN系统，并完成上电之后，这台新的转发器可以通过openflow通道向SDN控制器发送注册信息。或者，在现有的SDN系统中，有一台转发器在断电的情况下，需重新上电，那么，这台转发器可以在上电完成之后，通过openflow通道向SDN控制器发送注册信息。
示例性的，注册信息可以采用互联网协议(Internet Protocol，IP)报文的形式发送给SDN控制器。
502、SDN控制器接收来自第一转发器的注册信息。
其中，SDN控制器可以通过openflow通道接收来自第一转发器的注册信息。
503、SDN控制器确定硬件设备能力信息库中未包含第一转发器的设备类型和设备型号。
其中，在SDN控制器接收到来自第一转发器的注册信息之后，SDN控制器可以对第一转发器上报的注册信息进行对比分析，以通过确定硬件设备能力信息库中是否包含第一转发器的设备类型和设备型号，来确认SDN系统是否支持第一转发器。
示例性的，在具体实现中，SDN控制器的硬件设备能力信息库中预先保存有所有支持的转发器的设备类型和设备型号。SDN控制器可以通过判断硬件设备能力信息库中是否包含第一转发器的设备类型和设备型号，来确认SDN系统是否支持第一转发器。当SDN控制器确定硬件设备能力信息库中包含第一转发器的设备类型和设备型号时，SDN控制器可以确认SDN系统支持该第一转发器，此时SDN控制器可以向第一转发器下发业务配置数据。当SDN控制器确定硬件设备能力信息库中未包含第一转发器的设备类型和设备型号时，SDN控制器可以确认SDN系统不支持该第一转发器，此时可以执行以下步骤504。
504、SDN控制器向第一转发器发送PnP数据请求。
其中，该PnP数据请求用于请求第一转发器上报设备能力信息。在SDN控制器确定出硬件设备能力信息库中未包含第一转发器的设备类型和设备型号时，SDN控制器可以向第一转发器发送用于请求第一转发器的设备能力信息的PnP数据请求。
示例性的，PnP数据请求可以采用IP报文的形式发送给第一转发器。
505、第一转发器接收来自SDN控制器的PnP数据请求。
506、第一转发器获取设备能力信息，并向SDN控制器发送设备能力信息。
其中，在第一转发器接收到来自SDN控制器的PnP数据请求之后，第一转发器可以收集自身的设备数据，以获得设备能力信息，并将获取到的设备能力信息发送至SDN控制器。
示例性的，设备能力信息可以是采用YANG模型的XML文件。也就是说，当第一转发器获得自身的设备能力信息之后，可以采用YANG模型将自身的设备能力信息生成一个XML文件上报给SDN控制器。
其中，设备能力信息可以包括以下至少一种：第一转发器的设备信息、第一转发器支持的单板信息。设备信息可以包括以下至少一种：设备类型、设备型号、设备描述、设备能力集、槽位个数、支持的槽位信息；槽位信息可以包括以下至少一种：槽位ID、槽位类型；单板信息可以包括以下至少一种：单板类型、单板名称、单板描述、单板能力集、单板的端口个数、单板的端口信息；单板的端口信息可以 包括以下至少一种：端口ID、端口类型、端口描述。另外，设备能力信息中包括的设备数据的描述参见表1所示。
表1
Figure PCTCN2017073117-appb-000001
507、SDN控制器接收来自第一转发器的设备能力信息。
其中，在SDN控制器接收到来自第一转发器的设备能力信息之后，SDN控制器可以对第一转发器的设备能力信息进行解析，并根据解析结果刷新系统规则和北向配置接口，具体的可以执行以下步骤508-步骤509。
508、SDN控制器将设备能力信息添加在硬件设备能力信息库中。
其中，SDN控制器可以根据第一转发器的设备能力信息刷新相关基础数据，即将第一转发器的设备能力信息添加在硬件设备能力信息库中，以使得SDN系统能够支持该第一转发器。
509、SDN控制器根据设备能力信息，确定目标命令，并根据设备能力信息，在目标命令中添加新命令行。
其中，SDN控制器可以根据第一转发器的设备能力信息刷新北向接口。具体的，SDN控制器可以根据第一转发器的设备能力信息，确定目标命令，并根据第一转发器的设备能力信息，在目标命令中添加新命令行。例如，根据第一转发器的设备能力信息确定的目标命令为add-device-board deviceId frameid/slotid{HS901GPBA|HS901GPBC}。根据设备能力信息判断槽位支持HS901GPBF，则设置新的命令为add-device-board deviceId frameid/slotid{HS901GPBA|HS901GPBC|HS901GPBF}。这样，SDN控制器能够根据第一转发器的设备能力信息离线配置与第一转发器具有相同设备能力信息的转发器。
示例性的，北向接口可以包括以下至少一种：web接口、表现层状态转化(Representational State Transfer，REST)、交易语言1(Transaction Language-1，TL1)，美国信息交换标准码(American Standard Code for Information Interchange，ASCII)、命令行接口(Command-line Interface，CLI)。
需要说明的是，在本发明实施例中，步骤508和步骤509的执行没有先后顺序。也就是说，可以先执行步骤508，再执行步骤509；或者也可以先执行步骤509，再执行步骤508；或者，还可以同时执行步骤508和步骤509。本发明实施例在此对步骤508和步骤509的执行先后顺序不做具体限制。
510、SDN控制器向第一转发器发送注册成功响应，并向第一转发器下发业务配置数据。
511、第一转发器接收来自SDN控制器的注册成功响应，接收来自SDN控制器的业务配置数据。
在执行上述步骤501-511的过程中，SDN系统中原有的转发器仍可以正常工作，即执行以下步骤512-步骤513。
512、SDN控制器接收来自上层应用的业务请求。
513、SDN控制器根据业务请求，向第二转发器下发业务配置数据。
其中，第二转发器为在第一转发器上电完成之前，已成功接入SDN系统的转发器。
本发明实施例提供的转发器入网识别方法，SDN控制器接收第一转发器的注册信息，在确定硬件设备能力信息库中未包含注册信息中包括的第一转发器的设备类型和设备型号时，向第一转发器发送用于请求第一转发器上报设备能力信息的PnP数据请求，并接收来自第一转发器的设备能力信息。这样，在现有SDN系统中有新的转发器接入时，SDN控制器可以在确定硬件设备能力信息库中未包含该转发器的设备类型和设备型号时，通过向该转发器发送PnP数据请求，便可以准确获知新入网的转发器的设备能力信息。即在有新的转发器接入时，无需对SDN控制器进行升级，SDN控制器便可以识别新入网转发器，从而解决了在现有SDN系统中接入新的转发器时，影响正在进行的网络业务且入网成本高的问题。
上述主要从各个网元之间交互的角度对本发明实施例提供的方案进行了介绍。可以理解的是，各个网元，例如SDN控制器、转发器为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的算法步骤，本发明能够以硬件或硬件和 计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本发明的范围。
本发明实施例可以根据上述方法示例对SDN控制器、转发器进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本发明实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
在采用对应各个功能划分各个功能模块的情况下，图7示出了上述和实施例中涉及的SDN控制器的一种可能的组成示意图，如图7所示，该SDN控制器可以包括：接收单元61、确定单元62、发送单元63。
其中，接收单元61，用于支持SDN控制器执行图5所示的转发器入网识别方法中的步骤402、步骤407，图6所示的转发器入网识别方法中的步骤502、步骤507、步骤512。
确定单元62，用于支持SDN控制器执行图5所示的转发器入网识别方法中的步骤403，图6所示的转发器入网识别方法中的步骤503、步骤509中的根据设备能力信息，确定目标命令。
发送单元63，用于支持SDN控制器执行图5所示的转发器入网识别方法中的步骤404，图6所示的转发器入网识别方法中的步骤504、步骤510、步骤513。
在本发明实施例中，进一步的，如图7所示，该SDN控制器还可以包括：添加单元64。
添加单元64，用于支持SDN控制器执行图6所示的转发器入网识别方法中的步骤508、步骤509中的根据设备能力信息，在目标命令中添加新命令行。
需要说明的是，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
本发明实施例提供的SDN控制器，用于执行上述转发器入网识别方法，因此可以达到与上述转发器入网识别方法相同的效果。
在采用集成的单元的情况下，图8示出了上述实施例中所涉及的SDN控制器的另一种可能的组成示意图。如图8所示，该SDN控制器包括：处理模块71和通信模块72。
处理模块71用于对SDN控制器的动作进行控制管理，例如，处理模块71用于支持SDN控制器执行图5中的步骤403，图6中的步骤503、步骤508、步骤509、和/或用于本文所描述的技术的其它过程。通信模块72用于支持SDN控制器与其他网络实体的通信，例如与图2、图4、图9或图10中示出的功能模块或网络实体之间的通信。具体的，如通信模块72用于执行SDN控制器执行图5中的步骤402、步骤404、步骤407，图6中的步骤502、步骤504、步骤507、步骤510、步骤512、步骤513。SDN控制器还可以包括存储模块73，用于存储SDN控制器的程序代码和数据。
其中，处理模块71可以是处理器或控制器。其可以实现或执行结合本发明公开内容所描述的各种示例性的逻辑方框，模块和电路。处理器也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，DSP和微处理器的组合等等。通信模块72可以是收发器、收发电路或通信接口等。存储模块73可以是存储器。
当处理模块71为处理器，通信模块72为通信接口，存储模块73为存储器时，本发明实施例所涉及的SDN控制器可以为图3所示的SDN控制器。
在采用对应各个功能划分各个功能模块的情况下，图9示出了上述和实施例中涉及的转发器的一种可能的组成示意图，如图9所示，该转发器可以包括：发送单元81、接收单元82和获取单元83。
其中，发送单元81，用于支持转发器执行图5所示的转发器入网识别方法中的步骤401、步骤406中的向SDN控制器发送设备能力信息，图6所示的转发器入网识别方法中的步骤501、步骤506中的向SDN控制器发送设备能力信息。
接收单元82，用于支持转发器执行图5所示的转发器入网识别方法中的步骤405，图6所示的转发器入网识别方法中的步骤505、步骤511。
获取单元83，用于支持转发器执行图5所示的转发器入网识别方法中的步骤406中的获取设备能力信息，图6所示的转发器入网识别方法中的步骤506中的获取设备能力信息。
需要说明的是，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
本发明实施例提供的转发器，用于执行上述转发器入网识别方法，因此可以达到与上述转发器入网识别方法相同的效果。
在采用集成的单元的情况下，图10示出了上述实施例中所涉及的转发器的另一种可能的组成示意图。如图10所示，该转发器包括：处理模块91和通信模块92。
处理模块91用于对转发器的动作进行控制管理。例如，处理模块91用于支持转发器执行图5中的步骤406中的获取设备能力信息，图6中的步骤506中获取设备能力信息、和/或用于本文所描述的技术的其它过程。通信模块92用于支持转发器与其他网络实体的通信，例如与图2、图3、图7或图8中示出的功能模块或网络实体之间的通信。具体的，如通信模块92用于执行转发器执行图5中的步骤401、步骤405、步骤406中的向SDN控制器发送设备能力信息，图6中的步骤501、步骤505、步骤506中的向SDN控制器发送设备能力信息、步骤511。转发器还可以包括存储模块93，用于存储转发器的程序代码和数据。
其中，处理模块91可以是处理器或控制器。其可以实现或执行结合本发明公开内容所描述的各种示例性的逻辑方框，模块和电路。处理器也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，DSP和微处理器的组合等等。通信模块92可以是收发器、收发电路或通信接口等。存储模块93可以是存储器。
当处理模块91为处理器，通信模块92为通信接口，存储模块93为存储器时，本发明实施例所涉及的转发器可以为图4所示的转发器。
通过以上的实施方式的描述，所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，仅以上述各功能模块的划分进行举例说明，实际应用中，可以根据 需要而将上述功能分配由不同的功能模块完成，即将装置的内部结构划分成不同的功能模块，以完成以上描述的全部或者部分功能。
在本申请所提供的几个实施例中，应该理解到，所揭露的装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述模块或单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个装置，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是一个物理单元或多个物理单元，即可以位于一个地方，或者也可以分布到多个不同地方。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本发明各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个可读取存储介质中。基于这样的理解，本发明实施例的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该软件产品存储在一个存储介质中，包括若干指令用以使得一个设备(可以是单片机，芯片等)或处理器(processor)执行本发明各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、ROM、RAM、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本发明的具体实施方式，但本发明的保护范围并不局限于此，任何在本发明揭露的技术范围内的变化或替换，都应涵盖在本发明的保护范围之内。因此，本发明的保护范围应以所述权利要求的保护范围为准。

Claims (26)

  1. 一种转发器入网识别方法，其特征在于，包括：
    软件定义网络SDN控制器接收来自第一转发器的注册信息，所述注册信息包括所述第一转发器的设备类型和设备型号；
    所述SDN控制器确定硬件设备能力信息库中未包含所述第一转发器的设备类型和设备型号；
    所述SDN控制器向所述第一转发器发送即插即用PnP数据请求，所述PnP数据请求用于请求所述第一转发器上报设备能力信息；
    所述SDN控制器接收来自所述第一转发器的设备能力信息。
  2. 根据权利要求1所述的方法，其特征在于，在所述SDN控制器接收来自所述第一转发器的设备能力信息之后，还包括：
    所述SDN控制器将所述设备能力信息添加在硬件设备能力信息库中。
  3. 根据权利要求1或2所述的方法，其特征在于，在所述SDN控制器接收来自所述第一转发器的设备能力信息之后，还包括：
    所述SDN控制器根据所述设备能力信息，确定目标命令；
    所述SDN控制器根据所述设备能力信息，在所述目标命令中添加新命令行。
  4. 根据权利要求1-3中任一项所述的方法，其特征在于，所述方法还包括：
    所述SDN控制器确定所述硬件设备能力信息库中包含所述第一转发器的设备类型和设备型号；
    所述SDN控制器向所述第一转发器下发业务配置数据。
  5. 根据权利要求1-3中任一项所述的方法，其特征在于，所述方法还包括：
    所述SDN控制器向所述第一转发器发送注册成功响应，并向所述第一转发器下发业务配置数据。
  6. 根据权利要求1-5中任一项所述的方法，其特征在于，所述方法还包括：
    所述SDN控制器接收来自上层应用的业务请求；
    所述SDN控制器根据所述业务请求，向第二转发器下发业务配置数据，所述第二转发器为在所述第一转发器上电完成之前，已成功接入所述SDN系统的转发器。
  7. 根据权利要求1-6中任一项所述的方法，其特征在于，所述设备能力信息是采用YANG模型的可扩展标记语言XML文件；
    所述设备能力信息包括以下至少一种：所述第一转发器的设备信息、所述第一转发器支持的单板信息。
  8. 根据权利要求7所述的方法，其特征在于，
    所述设备信息包括以下至少一种：所述设备类型、所述设备型号、设备描述、设备能力集、槽位个数、支持的槽位信息；所述槽位信息包括以下至少一种：槽位标识ID、槽位类型；
    所述单板信息包括以下至少一种：单板类型、单板名称、单板描述、单板能力集、单板的端口个数、单板的端口信息；所述单板的端口信息包括以下至少一种：端口ID、端口类型、端口描述。
  9. 一种转发器入网识别方法，其特征在于，包括：
    第一转发器向软件定义网络SDN控制器发送注册信息，所述注册信息包括所述第一转发器的设备类型和设备型号；
    所述第一转发器接收来自所述SDN控制器的即插即用PnP数据请求，所述PnP数据请求用于请求所述第一转发器上报设备能力信息；
    所述第一转发器获取所述设备能力信息，并向所述SDN控制器发送所述设备能力信息。
  10. 根据权利要求9所述的方法，其特征在于，还包括：
    所述第一转发器接收来自所述SDN控制器的注册成功响应；
    所述第一转发器接收来自所述SDN控制器的业务配置数据。
  11. 根据权利要求9或10所述的方法，其特征在于，所述设备能力信息是采用YANG模型的可扩展标记语言XML文件；
    所述设备能力信息包括以下至少一种：所述第一转发器的设备信息、所述第一转发器支持的单板信息。
  12. 根据权利要求11所述的方法，其特征在于，
    所述设备信息包括以下至少一种：所述设备类型、所述设备型号、设备描述、设备能力集、槽位个数、支持的槽位信息；所述槽位信息包括以下至少一种：槽位标识ID、槽位类型；
    所述单板信息包括以下至少一种：单板类型、单板名称、单板描述、单板能力集、单板的端口个数、单板的端口信息；所述单板的端口信息包括以下至少一种：端口ID、端口类型、端口描述。
  13. 一种软件定义网络SDN控制器，其特征在于，包括：接收单元、确定单元和发送单元；
    所述接收单元，用于接收来自第一转发器的注册信息，所述注册信息包括所述第一转发器的设备类型和设备型号；
    所述确定单元，用于确定硬件设备能力信息库中未包含所述接收单元接收到的所述第一转发器的设备类型和设备型号；
    所述发送单元，用于向所述第一转发器发送即插即用PnP数据请求，所述PnP数据请求用于请求所述第一转发器上报设备能力信息；
    所述接收单元，还用于接收来自所述第一转发器的设备能力信息。
  14. 根据权利要求13所述的SDN控制器，其特征在于，还包括：添加单元；
    所述添加单元，用于将所述接收单元接到的所述设备能力信息添加在硬件设备能力信息库中。
  15. 根据权利要求14所述的SDN控制器，其特征在于，
    所述确定单元，还用于根据所述接收单元接收到的所述设备能力信息，确定目标命令；
    所述添加单元，还用于根据所述确定单元确定出的所述设备能力信息，在所述目标命令中添加新命令行。
  16. 根据权利要求13-15中任一项所述的SDN控制器，其特征在于，
    所述确定单元，还用于确定所述硬件设备能力信息库中包含所述第一转发器的设 备类型和设备型号；
    所述发送单元，还用于向所述第一转发器下发业务配置数据。
  17. 根据权利要求13-15中任一项所述的SDN控制器，其特征在于，
    所述发送单元，还用于向所述第一转发器发送注册成功响应，并向所述第一转发器下发业务配置数据。
  18. 根据权利要求13-17中任一项所述的SDN控制器，其特征在于，
    所述接收单元，还用于接收来自上层应用的业务请求；
    所述发送单元，还用于根据所述接收单元接收到的所述业务请求，向第二转发器下发业务配置数据，所述第二转发器为在所述第一转发器上电完成之前，已成功接入所述SDN系统的转发器。
  19. 根据权利要求13-18中任一项所述的SDN控制器，其特征在于，所述设备能力信息是采用YANG模型的可扩展标记语言XML文件；
    所述设备能力信息包括以下至少一种：所述第一转发器的设备信息、所述第一转发器支持的单板信息。
  20. 根据权利要求19所述的SDN控制器，其特征在于，
    所述设备信息包括以下至少一种：所述设备类型、所述设备型号、设备描述、设备能力集、槽位个数、支持的槽位信息；所述槽位信息包括以下至少一种：槽位标识ID、槽位类型；
    所述单板信息包括以下至少一种：单板类型、单板名称、单板描述、单板能力集、单板的端口个数、单板的端口信息；所述单板的端口信息包括以下至少一种：端口ID、端口类型、端口描述。
  21. 一种转发器，其特征在于，包括：发送单元、接收单元和获取单元；
    所述发送单元，用于向软件定义网络SDN控制器发送注册信息，所述注册信息包括所述第一转发器的设备类型和设备型号；
    所述接收单元，用于接收来自所述SDN控制器的即插即用PnP数据请求，所述PnP数据请求用于请求所述第一转发器上报设备能力信息；
    所述获取单元，用于获取所述设备能力信息；
    所述发送单元，还用于向所述SDN控制器发送所述获取单元获取到的所述设备能力信息。
  22. 根据权利要求21所述的转发器，其特征在于，
    所述接收单元，还用于接收来自所述SDN控制器的注册成功响应，接收来自所述SDN控制器的业务配置数据。
  23. 根据权利要求21或22所述的转发器，其特征在于，所述设备能力信息是采用YANG模型的可扩展标记语言XML文件；
    所述设备能力信息包括以下至少一种：所述第一转发器的设备信息、所述第一转发器支持的单板信息。
  24. 根据权利要求23所述的转发器，其特征在于，
    所述设备信息包括以下至少一种：所述设备类型、所述设备型号、设备描述、设备能力集、槽位个数、支持的槽位信息；所述槽位信息包括以下至少一种：槽位标识 ID、槽位类型；
    所述单板信息包括以下至少一种：单板类型、单板名称、单板描述、单板能力集、单板的端口个数、单板的端口信息；所述单板的端口信息包括以下至少一种：端口ID、端口类型、端口描述。
  25. 一种软件定义网络SDN控制器，其特征在于，包括：至少一个处理器、存储器、通信接口、通信总线；
    所述至少一个处理器与所述存储器、所述通信接口通过所述通信总线连接，所述存储器用于存储计算机执行指令，当所述SDN控制器运行时，所述处理器执行所述存储器存储的所述计算机执行指令，以使所述SDN控制器执行如权利要求1-8中任一项所述的转发器入网识别方法。
  26. 一种转发器，其特征在于，包括：至少一个处理器、存储器、通信接口、通信总线；
    所述至少一个处理器与所述存储器、所述通信接口通过所述通信总线连接，所述存储器用于存储计算机执行指令，当所述转发器运行时，所述处理器执行所述存储器存储的所述计算机执行指令，以使所述转发器执行如权利要求9-12中任一项所述的转发器入网识别方法。
PCT/CN2017/073117 2017-02-08 2017-02-08 一种转发器入网识别方法、sdn控制器及转发器 WO2018145267A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP17896035.7A EP3573303A4 (en) 2017-02-08 2017-02-08 METHOD FOR RECOGNIZING NETWORK ACCESS BY A REHEATHER, SDN CONTROLLER, AND REHEATER
PCT/CN2017/073117 WO2018145267A1 (zh) 2017-02-08 2017-02-08 一种转发器入网识别方法、sdn控制器及转发器

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2017/073117 WO2018145267A1 (zh) 2017-02-08 2017-02-08 一种转发器入网识别方法、sdn控制器及转发器

Publications (1)

Publication Number Publication Date
WO2018145267A1 true WO2018145267A1 (zh) 2018-08-16

Family

ID=63107709

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/073117 WO2018145267A1 (zh) 2017-02-08 2017-02-08 一种转发器入网识别方法、sdn控制器及转发器

Country Status (2)

Country Link
EP (1) EP3573303A4 (zh)
WO (1) WO2018145267A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111181772A (zh) * 2019-12-12 2020-05-19 新华三大数据技术有限公司 网络协议下发方法、装置及系统
CN113587392A (zh) * 2021-08-05 2021-11-02 青岛海信日立空调系统有限公司 中央空调控制系统

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103200122A (zh) * 2013-03-05 2013-07-10 中兴通讯股份有限公司 一种软件定义网络中组表的处理方法、系统和控制器
CN103391296A (zh) * 2013-07-29 2013-11-13 北京华为数字技术有限公司 一种控制器、转发器及通道建立方法和系统
CN104389803A (zh) * 2014-11-18 2015-03-04 杭州华三通信技术有限公司 风扇控制方法及装置
WO2016206741A1 (en) * 2015-06-25 2016-12-29 Siemens Aktiengesellschaft Forwarding device, controller and method

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2012004424A1 (es) * 2010-07-08 2012-01-12 Telefonica, S.A. Método y sistema de gestión de topologías de red en redes domésticas
US9853870B2 (en) * 2015-03-31 2017-12-26 Verizon Patent And Licensing Inc. Controller supported service maps within a federation of forwarding boxes

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103200122A (zh) * 2013-03-05 2013-07-10 中兴通讯股份有限公司 一种软件定义网络中组表的处理方法、系统和控制器
CN103391296A (zh) * 2013-07-29 2013-11-13 北京华为数字技术有限公司 一种控制器、转发器及通道建立方法和系统
CN104389803A (zh) * 2014-11-18 2015-03-04 杭州华三通信技术有限公司 风扇控制方法及装置
WO2016206741A1 (en) * 2015-06-25 2016-12-29 Siemens Aktiengesellschaft Forwarding device, controller and method

Non-Patent Citations (1)

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

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111181772A (zh) * 2019-12-12 2020-05-19 新华三大数据技术有限公司 网络协议下发方法、装置及系统
CN111181772B (zh) * 2019-12-12 2022-03-29 新华三大数据技术有限公司 网络协议下发方法、装置及系统
CN113587392A (zh) * 2021-08-05 2021-11-02 青岛海信日立空调系统有限公司 中央空调控制系统
CN113587392B (zh) * 2021-08-05 2022-06-28 青岛海信日立空调系统有限公司 中央空调控制系统

Also Published As

Publication number Publication date
EP3573303A1 (en) 2019-11-27
EP3573303A4 (en) 2020-01-01

Similar Documents

Publication Publication Date Title
US11704144B2 (en) Creating virtual machine groups based on request
US10270648B2 (en) Configuration information management method, device, network element management system and storage medium
US20170163479A1 (en) Method, Device and System of Renewing Terminal Configuration In a Memcached System
US11575592B2 (en) Message processing method and apparatus, control-plane device, and computer storage medium
US9999030B2 (en) Resource provisioning method
US20170289791A1 (en) Communication method and apparatus using network slice
US20170163478A1 (en) Method,electronic device and system for updating client configuration in key-value pair database
JP2020530722A (ja) Ｐｄｕタイプ設定方法、ｕｅポリシー設定方法、および関連エンティティ
WO2014026524A1 (zh) 一种分配资源的方法及装置
JP6888078B2 (ja) ネットワーク機能ｎｆ管理方法及びｎｆ管理装置
WO2019137516A1 (zh) 网络切片部署方法及其装置
WO2020062959A1 (zh) 配置数据的方法及装置
WO2019062995A1 (zh) 网络管理方法、设备及系统
WO2019057015A1 (zh) 一种网络切片管理方法及装置
JP2016116184A (ja) 網監視装置および仮想ネットワーク管理方法
JP7003876B2 (ja) 通信システム及び通信方法
WO2017185992A1 (zh) 一种请求消息传输方法及装置
WO2018145267A1 (zh) 一种转发器入网识别方法、sdn控制器及转发器
CN112073555A (zh) Ip地址的配置方法、电子设备和计算机可读存储介质
WO2017032110A1 (zh) 一种应用消息的处理系统、方法及应用设备
KR20150088462A (ko) 클라우드 환경에서 네트워크 장치의 연동 방법 및 장치
JP5782393B2 (ja) ネットワークリソース分散管理方法およびプログラム
TWI566168B (zh) 用於叢集式儲存系統的路由方法
WO2023035777A1 (zh) 网络配置方法、代理组件、控制器、电子设备和存储介质
CN117041147B (zh) 智能网卡设备、主机设备和方法及系统

Legal Events

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

Ref document number: 17896035

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2017896035

Country of ref document: EP

Effective date: 20190819