WO2018033050A1 - 基于软件定义网络的部署方法、装置及系统 - Google Patents

基于软件定义网络的部署方法、装置及系统 Download PDF

Info

Publication number
WO2018033050A1
WO2018033050A1 PCT/CN2017/097411 CN2017097411W WO2018033050A1 WO 2018033050 A1 WO2018033050 A1 WO 2018033050A1 CN 2017097411 W CN2017097411 W CN 2017097411W WO 2018033050 A1 WO2018033050 A1 WO 2018033050A1
Authority
WO
WIPO (PCT)
Prior art keywords
network element
information
ofcp
ofc
network
Prior art date
Application number
PCT/CN2017/097411
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 中兴通讯股份有限公司
Publication of WO2018033050A1 publication Critical patent/WO2018033050A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/40—Support for services or applications
    • 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
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/50—Address allocation

Definitions

  • the present invention relates to the field of communications, and in particular to a method, apparatus, and system for deploying a software-defined network.
  • the Software Defined Network (SDN) in the related art decouples the control plane and the forwarding plane by standardizing a Southbound Interface (SBI).
  • SBI Southbound Interface
  • OpenFlow and OF-Config are the southbound interface standards developed by the International Standards Organization (ONF).
  • ONF International Standards Organization
  • the OF-Config protocol is called OpenFlow Management and Configuration Protocol (OpenFlow Management Configuration Protocol, where OpenFlow is the name of the standard organization), and its transport protocol is NetConf.
  • OpenFlow Management Configuration Protocol where OpenFlow is the name of the standard organization
  • NetConf transport protocol
  • 1 is a relationship diagram of an OF-Config and an OpenFlow protocol component according to the related art of the present invention.
  • an OpenFlow Configuration Point is an OpenFlow configuration point
  • an OpenFlow Controller is an OpenFlow controller
  • an OpenFlow capable switch is an OpenFlow function switch
  • an OF logical switch is OpenFlow logical switch
  • OF Resource egport
  • OFCP OpenFlow Configuration Point
  • OFCP physical switch
  • OpenFlow Capable Swithch described in Chapter 2 of the OF-Config protocol.
  • OF-Config is to provide the channel for the remote configuration OFCS.
  • OF-Config is usually used for port enable, deactivation, etc. with less real-time requirements.
  • Configured channels OpenFlow is usually used for channels with higher real-time requirements such as stream addition and deletion.
  • FIG. 2 is a relationship diagram of a server and a client according to a protocol in the related art according to the present invention.
  • an OFCS is used as a server (server) end
  • an OFCP is used as a client (client) end.
  • the link is established. It was initiated by OFCP to OFCS.
  • the OFLS is the client and the OFC as the server, most of the implementations of the manufacturers are still the same.
  • the establishment of the link is initiated by the OFLS to the OFC.
  • FIG. 3 is a network diagram of an SDN according to the related art of the present invention.
  • the OFC and the OFCP must implement management of the entire network, and each of the network elements must be established separately.
  • the OpenFlow link, an OF-Config link, as shown in the figure, the access network element and the non-access network element 1, and the non-access network elements 2 and 3 are similar to the non-access network element 1, and are omitted in the figure.
  • the client acting as the link initiator needs to know the IP and port as the server to initiate a request to establish a link.
  • how can the OFCP as the OF-Config channel client know the IP and port of all network elements; how can the network element (OFCS) of the OpenFlow channel client know the IP and port of the OFC?
  • Method 1 is preset, that is, when the device is upgraded, the IP address and port of the OFC are written to the configuration file of the network element; and the IP and port of each network element are manually determined for the OFCP.
  • the second method is to manually set the IP and port of each network element manually to the OFCP. After the OFCP manages the device, manually set the IP address and port of the OFC to each network element.
  • the problem is that the operator OFC has more than one IP, and it will change at any time, and the way of configuring the file is difficult to cope with.
  • the user needs to use other means (such as the command line) to obtain the IP address of the device.
  • the device After the device is managed by the OFCP client, the device can be configured with the IP address of the OFC.
  • the newly opened network has a large workload and is not convenient.
  • Embodiments of the present invention provide a deployment method, apparatus, and system based on a software-defined network. To solve at least the problem of low efficiency when deploying network elements in a software-defined network in related technologies.
  • a software-defined network-based deployment method including: configuring a point OFCP to receive network element information of one or more second network elements reported by a first network element, where a network element is connected to the OFCP through an OF-Config management channel, the second network element is a neighboring network element of the first network element, and the OFCP establishes the second network by using the network element information. Yuan's OF-Config management channel.
  • the method further includes: indicating, by the OF-Config management channel, the OFCP The second network element establishes an OpenFlow channel with the controller OFC.
  • the network element information includes: an IP address, an OFConfig-Port channel port.
  • the establishing, by the OFCP, the OF-Config management channel with the second network element by using the network element information, that the OFCP uses the IP address and the OFConfig-Port field to use the second network The element initiates a link establishment request of the OF-Config management channel; after the establishment of the OF-Config management channel, the OFCP sends the OFC information to the first network element and the second network element, the OFC information Includes the IP and OFC ports of the OFC.
  • the OFCP by using the OF-Config management channel, to indicate that the second network element establishes an OpenFlow channel with the controller OFC, includes: the OFCP querying whether the OFC information exists on the second network element; When the OFC information exists on the second network element, the OFCP determines whether the OFC information is the specified OFC information; the OFC information does not exist on the second network element, or the OFC information existing on the second network element is not the specified
  • the OFCP sends the specified OFC information to the second network element, where the specified OFC information is used to describe an OFC in which an OpenFlow channel exists between the second network element.
  • a software-defined network-based deployment method including: acquiring, by a first network element, network element information of a second network element adjacent thereto, where the first network element and configuration Point OFCP is connected through the OF-Config management channel; the first network element reports the network element information to the OFCP, where the network element information is used for the OFCP and the second An OF-Config management channel is established between the NEs.
  • the network element information includes: an IP address, an OFConfig-Port channel port.
  • the acquiring, by the first network element, the network element information of the second network element that is adjacent to the network element includes: the first network element querying the second network element by using a link layer discovery protocol (LLDP) through a data communication network DCN function.
  • LLDP link layer discovery protocol
  • a software-defined network-based deployment apparatus including: a receiving module, configured to receive network element information of one or more second network elements reported by a first network element, where The first network element is connected to the OFCP through an OF-Config management channel, the second network element is a neighboring network element of the first network element, and the first establishing module is configured to use the network element information. Establishing an OF-Config management channel with the second network element.
  • the device further includes: a second establishing module, configured to: after the first establishing module establishes an OF-Config management channel with the second network element by using the network element information, by using the OF The -Config management channel instructs the second network element to establish an OpenFlow channel with the controller OFC.
  • a second establishing module configured to: after the first establishing module establishes an OF-Config management channel with the second network element by using the network element information, by using the OF The -Config management channel instructs the second network element to establish an OpenFlow channel with the controller OFC.
  • the network element information includes: an IP address, an OFConfig-Port channel port.
  • another software-defined network-based deployment apparatus which is applied to the first network element, and includes: an obtaining module, configured to acquire a second network element adjacent to the first network element.
  • the network element information wherein the first network element is connected to the configuration point OFCP through the OF-Config management channel;
  • the reporting module is configured to report the network element information to the OFCP, where the network element information is used for An OF-Config management channel is established between the OFCP and the second network element.
  • the network element information includes: an IP address, an OFConfig-Port channel port.
  • the obtaining module further includes: an obtaining unit, configured to query the network element information of the second network element by using a link layer discovery protocol LLDP by using a data communication network DCN function.
  • an obtaining unit configured to query the network element information of the second network element by using a link layer discovery protocol LLDP by using a data communication network DCN function.
  • a software-defined network-based deployment system including a first network element, a second network element, a configuration point OFCP, and a controller OFC, where the OFCP includes: a receiving module, configured to Receiving the network element of one or more second network elements reported by the first network element Information, wherein the second network element is a neighboring network element of the first network element; the first establishing module is configured to establish an OF-Config management channel with the second network element by using the network element information
  • the first network element includes: an obtaining module, configured to acquire network element information of the second network element, where the first network element and the configuration point OFCP are connected through an OF-Config management channel; the reporting module, It is configured to report the network element information to the OFCP.
  • the first network element is an access network element
  • the second network element is a non-access network element
  • a storage medium is also provided.
  • the storage medium is arranged to store program code for performing the following steps:
  • the configuration point OFCP receives the network element information of the one or more second network elements reported by the first network element, where the first network element is connected to the OFCP through an OF-Config management channel, and the second network element is Adjacent network elements of the first network element;
  • the OFCP establishes an OF-Config management channel with the second network element by using the network element information.
  • a storage medium is further provided, where the storage medium may store an execution instruction for performing the implementation of the preamble transmission software-defined network-based deployment method in the foregoing embodiment.
  • the configuration point OFCP receives the network element information of the one or more second network elements reported by the first network element, where the first network element and the OFCP are connected through the OF-Config management channel.
  • the second network element is a neighboring network element of the first network element; the OFCP uses the network element information to establish an OF-Config management channel with the second network element.
  • the network element information of the other network element to be online is reported to the OFCP through the first network element that has been connected to the OFCP, thereby avoiding manually configuring the to-be-raised network element or using a specific command line to obtain the network element information of the network element to be online.
  • Complex and inefficient operation therefore, can solve the problem of low efficiency when deploying network elements in a software-defined network in the related art.
  • FIG. 1 is a diagram showing relationship between an OF-Config and an OpenFlow protocol component according to the related art of the present invention
  • FIG. 2 is a relationship diagram of a server and a client according to a protocol in the related art according to the present invention
  • FIG. 3 is a network diagram of an SDN in the related art according to the present invention.
  • FIG. 4 is a flow chart of a software-defined network-based deployment method in accordance with an embodiment of the present invention.
  • FIG. 5 is a flow chart of another software-defined network-based deployment method in accordance with an embodiment of the present invention.
  • FIG. 6 is a structural block diagram of a software-defined network-based deployment apparatus according to an embodiment of the present invention.
  • FIG. 7 is a structural block diagram of another software-defined network-based deployment apparatus according to an embodiment of the present invention.
  • FIG. 8 is a structural block diagram of a software-defined network-based deployment system according to an embodiment of the present invention.
  • FIG. 9 is a schematic structural diagram of neighbor information according to an embodiment of the present invention.
  • FIG. 10 is a timing diagram of automatic deployment and uplink of an access network element according to an embodiment of the present invention.
  • FIG. 11 is a timing diagram of automatic deployment and uplink of a non-access network element according to an embodiment of the present invention.
  • FIG. 4 is a method according to an embodiment of the present invention.
  • Step S402 the configuration point OFCP receives the network element information of the one or more second network elements reported by the first network element, where the first network element is connected to the OFCP through the OF-Config management channel, and the second network element is the first network element. Adjacent network element of the element;
  • Step S404 the OFCP establishes an OF-Config management channel with the second network element by using the network element information.
  • the configuration point OFCP receives the network element information of one or more second network elements reported by the first network element, where the first network element is connected to the OFCP through the OF-Config management channel, and the second network element is the first The neighboring network element of the network element; the OFCP uses the network element information to establish an OF-Config management channel with the second network element.
  • the network element information of the other network element to be online is reported to the OFCP through the first network element that has been connected to the OFCP, thereby avoiding manually configuring the to-be-raised network element or using a specific command line to obtain the network element information of the network element to be online.
  • Complex and inefficient operation therefore, can solve the problem of low efficiency when deploying network elements in a software-defined network in the related art.
  • the execution body OFCP of the foregoing steps may be a server, a control terminal, a console, etc., but is not limited thereto.
  • the network element information includes: an IP address, an OFConfig-Port channel port.
  • the NE information "Neighbor" can be defined, including the IP and OFConfig-Port fields, where IP is the IP address of the network element, and OFConfig-Port is the OF-Config channel port that the network element listens to as the OF-Config server.
  • the embodiment further includes: the OFCP instructing the second network element to establish an OpenFlow channel with the controller OFC through the OF-Config management channel.
  • the OFCP establishes an OF-Config management channel with the second network element by using the network element information, including:
  • the OFCP initiates a link establishment request of the OF-Config management channel to the second network element by using an IP address and an OFConfig-Port field.
  • the OFCP sends the OFC information to the first network element and the second network element.
  • the OFC information includes the IP address of the OFC and the port of the OFC.
  • the second network element can also establish an OpenFlow channel with the controller OFC.
  • the OFCP by using the OF-Config management channel, to indicate that the second network element establishes an OpenFlow channel with the controller OFC includes:
  • the OFCP determines whether the OFC information is the specified OFC information.
  • the OFCP sends the specified OFC information to the second network element, where the specified OFC information is used. Describe the OFC with the OpenFlow channel between the second network element.
  • FIG. 5 is a flowchart of another software-defined network-based deployment method according to an embodiment of the present invention. As shown in FIG. 5, the process includes the following steps:
  • Step S502 the first network element acquires network element information of the second network element adjacent thereto, where the first network element and the configuration point OFCP are connected through the OF-Config management channel;
  • Step S504 The first network element reports the network element information to the OFCP, where the network element information is used to establish an OF-Config management channel between the OFCP and the second network element.
  • the first network element of the execution entity of the foregoing step may be an access device, a base station, an MME, etc., but is not limited thereto.
  • the network element information includes: an IP address, an OFConfig-Port channel port.
  • the acquiring, by the first network element, the network element information of the second network element that is adjacent to the network element includes: the first network element uses the link layer discovery protocol LLDP to query the network element information of the second network element by using the link layer discovery protocol LLDP.
  • the method according to the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course, by hardware, but in many cases, the former is A better implementation.
  • the technical solution of the present invention which is essential or contributes to the prior art, may be embodied in the form of a software product stored in a storage medium (such as ROM/RAM, disk,
  • the optical disc includes a number of instructions for causing a terminal device (which may be a cell phone, a computer, a server, or a network device, etc.) to perform the methods of various embodiments of the present invention.
  • a software-defined network-based deployment apparatus and system are also provided, which are used to implement the foregoing embodiments and preferred embodiments, and are not described again.
  • the term "module” may implement a combination of software and/or hardware of a predetermined function.
  • the apparatus described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware, is also possible and contemplated.
  • FIG. 6 is a structural block diagram of a software-defined network-based deployment apparatus according to an embodiment of the present invention. As shown in FIG. 6, the apparatus includes:
  • the receiving module 60 is configured to receive the network element information of the one or more second network elements that are reported by the first network element, where the first network element is connected to the OFCP through the OF-Config management channel, and the second network element is the first network element. Adjacent network element of the element;
  • the first establishing module 62 is configured to establish an OF-Config management channel with the second network element by using the network element information.
  • the apparatus of this embodiment further includes: a second establishing module, configured to: after the first establishing module establishes an OF-Config management channel with the second network element by using the network element information, instructing the channel through the OF-Config management channel The second network element establishes an OpenFlow channel with the controller OFC.
  • a second establishing module configured to: after the first establishing module establishes an OF-Config management channel with the second network element by using the network element information, instructing the channel through the OF-Config management channel The second network element establishes an OpenFlow channel with the controller OFC.
  • the network element information in this embodiment includes: an IP address, an OFConfig-Port channel port.
  • FIG. 7 is a structural block diagram of another software-defined network-based deployment apparatus, which is applied to a first network element, as shown in FIG. 7, the apparatus includes:
  • the acquiring module 70 is configured to acquire network element information of the second network element adjacent to the first network element, where the first network element and the configuration point OFCP are connected through the OF-Config management channel;
  • the reporting module 72 is configured to report the network element information to the OFCP, where the network element information is used to establish an OF-Config management channel between the OFCP and the second network element.
  • the network element information may be, but is not limited to, an IP address and an OFConfig-Port channel port.
  • the obtaining module further includes: an obtaining unit, configured to query the network element information of the second network element by using a link layer discovery protocol LLDP by using a data communication network DCN function.
  • an obtaining unit configured to query the network element information of the second network element by using a link layer discovery protocol LLDP by using a data communication network DCN function.
  • FIG. 8 is a structural block diagram of a software-defined network-based deployment system according to an embodiment of the present invention. As shown in FIG. 8, the method includes: a first network element 80, a second network element 82, a configuration point OFCP84, a controller OFC86, and an OFCP84. include:
  • the receiving module 840 is configured to receive the network element information of the one or more second network elements that are reported by the first network element, where the second network element is a neighboring network element of the first network element;
  • the first establishing module 842 is configured to establish an OF-Config management channel with the second network element by using the network element information
  • the inclusion of the first network element 80 includes:
  • the obtaining module 800 is configured to obtain the network element information of the second network element, where the first network element and the configuration point OFCP are connected through the OF-Config management channel;
  • the reporting module 802 is configured to report the network element information to the OFCP.
  • the first network element in this embodiment is an access network element
  • the second network element is a non-access network element
  • 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 above modules are in any combination.
  • the forms are located in different processors.
  • This embodiment is an optional embodiment according to the present invention, which is used to describe the present application in detail in conjunction with a specific scenario:
  • This embodiment is directed to the problem that the deployment and uplink of different manufacturers in the software-defined network cannot cope with the IP address change and configuration workload of the operator OFC, and a method for automatically deploying and going online of devices of different manufacturers in the software-defined network is proposed. .
  • the technical problem to be solved in this embodiment is that the OFLS and the OFC in the software-defined network of the ONF-based OpenFlow and OF-Config southbound interface protocols can quickly manage all the network elements in the entire network.
  • the present invention implements an automatic deployment and online method of devices of different manufacturers by extending OF-Config based on the existing framework of the ONF.
  • This embodiment provides an implementation method, including:
  • the DCN Data Communication Network
  • the DCN can use mature neighbor discovery protocols such as mature LLDP. The information of other neighbor NEs can be found through each NE in the DCN network.
  • FIG. 9 is a schematic structural diagram of neighbor information according to an embodiment of the present invention. As shown in FIG. 9, the right object, the middle and the left three other objects are defined in the OF-Config standard, and FIG. The representation method is also a method in U-map to describe the Data Model Diagram in OF-Config. One side of the solid diamond has an arrow indicating the combination, indicating the inclusion relationship. The line pointing to the Neighbor by the OpenFow Capable Switch indicates that the former is included. The overall and partial relationship of the person, the "*" model indicates that the former can contain multiple of the latter.
  • the "Neighbor” we defined contains the IP and OFConfig-Port fields, where IP is the IP address of the network element, and OFConfig-Port is the OF-Config channel port that the network element listens to as the OF-Config server.
  • the OFCP establishes an OF-Config management channel with the access NE by manually specifying the access IP and port of the NE.
  • the access network element reports the information "Neighbor" of the neighbor (other non-access network element) to the OFCP through the OF-Config management channel.
  • the OFCP actively initiates a link establishment request with the OF-Config management channel of each network element according to the "Neighbor" information of the entire network reported by the access network element, when OFCP and each network element After the OF-Config management channel is established, the OFCP automatically configures the IP and port of the OFC for all access NEs and non-access NEs.
  • the OpenFlow link establishment request with the OFC is initiated through the DCN network, thereby establishing an OpenFlow channel with the OFC.
  • each network element in the network establishes an OF-Config and OpenFlow channel with OFCP and OFC, and finally achieves automatic deployment and online access of all network elements in the network.
  • the access network element and the non-access network element are respectively described below.
  • the division of the access network element and the non-access network element is shown in FIG. 3.
  • the access network element and the non-access network element are divided, and the automatic deployment and online steps of the access network element are as follows:
  • Step 1 The access network element is powered on, and the OF-Config management channel port is monitored.
  • Step 2 The user establishes an OF-Config management channel with the access network element by using the OFCP by specifying the IP address.
  • Step 3 After the OF-Config link is established, the OFCP automatically queries the OFC information on the NE. If there is no OFC information, the OFC information is automatically sent to the NE. If the OFC information is inconsistent, the OFC on the NE is automatically modified. information.
  • Step 4 After obtaining the OFC information, the network element initiates an OpenFlow link establishment request with the OFC, thereby completing the establishment of the link between the access network element and the OFC.
  • the automatic deployment and online steps of the non-access NE include:
  • Step 1 After the access NE and the non-access NE are powered on, DCN is enabled by default.
  • Step 2 The access network element and the non-access network element discover the neighbor through the DCN.
  • Step 3 The user establishes an OF-Config management channel with the access network element by using the OFCP by specifying the IP address.
  • Step 4 After the access network element establishes an OF-Config link with the OFCP, the access network element automatically reports the neighbor information of all the non-access network elements to the OFCP.
  • Step 5 After acquiring the information of the non-access NE, the OFCP initiates and initiates each non-access.
  • Step 6 After the OFCP is linked with the OF-Config management channel of each non-access network element, the OFCP automatically queries the OFC information on the network element; if there is no OFC information, the OFC information is automatically sent to the network element; if there is an OFC If the information is inconsistent, the OFC information on the NE is automatically modified.
  • Step 7 After receiving the OFC information, the non-access NE initiates an OpenFlow link establishment request with the OFC, thereby completing the establishment of the link between the non-access network element and the OFC.
  • FIG. 9 is a schematic structural diagram of neighbor information according to an embodiment of the present invention.
  • the structure of the neighbor information is defined.
  • a Neighbor object representing the neighbor is added to the OpenFlow Capable Switch, where the IP indicates the IP address of the neighbor, and OFConfig -Port indicates that the NE is the OF-Config channel port that the OF-Config server listens to.
  • FIG. 10 is an automatic deployment and uplink timing diagram of an access network element according to an embodiment of the present invention.
  • the automatic deployment and online steps of the access network element are as follows:
  • Step 1 The user sets the information of the OFC to the OFCP;
  • Step 2 The access network element IP is 10.X.X.A. After power-on, the network element acts as a NetConf server and listens to the NetConf default port 830.
  • Step 3 The user specifies the IP address of the access NE and the monitored OF-Config port number to the OFCP;
  • FIG. 11 is an automatic deployment and uplink timing diagram of a non-access network element according to an embodiment of the present invention.
  • the automatic deployment and online steps of a non-access network element are as follows:
  • Step 1 The user sets the information of the OFC to the OFCP;
  • Step 2 After the access NE is powered on, the DCN is enabled by default, and the NetConf default port 830 is monitored.
  • Step 3 After the non-access NE is powered on, the DCN is enabled by default, and the NetConf default port 830 is monitored;
  • Step 4 The access network element [10.X.X.A] discovers three non-access network elements of the neighbors [10.X.X.B, 10.X.X.C, 10.X.X.D] through the DCN;
  • Step 5 The user specifies the IP address of the access NE and the monitored OF-Config port number to the OFCP;
  • Step 7 After the access network element establishes a link with the OFCP, the access network element automatically reports the neighbor information [10.X.X.B, 10.X.X.C, 10.X.X.D] of the non-access network element to the OFCP;
  • Step 8 After acquiring the information of the non-access network element, the OFCP initiates a management channel link with 10.X.X.B, 10.X.X.C, and 10.X.X.D.
  • Step 1 The user sets multiple OFC information to the OFCP, and specifies whether the role of the OFC is master, slave, or equal;
  • Step 2 The access network element IP is 10.X.X.A. After power-on, the network element acts as a NetConf server and listens to the NetConf default port 830.
  • Step 3 The user specifies the IP address of the access NE and the monitored OF-Config port number to the OFCP;
  • Step 5 After the link is established, the OFCP automatically sends the query command of the OFC object to the network element through the OF-Config channel. If the OFC information is empty, the multiple OFC information set by the user is automatically delivered to the network element; if there is an OFC If the information is inconsistent, the OFC information on the NE is automatically modified.
  • Step 6 After obtaining multiple OFC information, the network element automatically initiates an OpenFlow link establishment request for each OFC according to the set role, thereby completing OpenFlow construction between the access network element and multiple OFCs.
  • Step 1 The user sets multiple OFC information to the OFCP, and specifies whether the role of the OFC is master, slave, or equal;
  • Step 2 After the access NE is powered on, the DCN is enabled by default, and the NetConf default port 830 is monitored.
  • Step 3 After the non-access NE is powered on, the DCN is enabled by default, and the NetConf default port 830 is monitored;
  • Step 4 The access network element [10.X.X.A] discovers neighbors [10.X.X.B, 10.X.X.C, 10.X.X.D] through the DCN, and three non-access network elements;
  • Step 5 The user specifies the IP address of the access NE and the OF-Config of the listening to the OFCP.
  • Step 7 After the access network element establishes a link with the OFCP, the access network element automatically reports the neighbor information [10.X.X.B, 10.X.X.C, 10.X.X.D] of the non-access network element to the OFCP;
  • Step 8 After acquiring the information of the non-access network element, the OFCP initiates a management channel link with 10.X.X.B, 10.X.X.C, and 10.X.X.D.
  • Step 9 After the OFCP and the management channel of the non-access network element are established, the OFCP automatically queries the OFC information on 10.XXB, 10.XXC, and 10.XXD. If the OFC information is empty, the user sets multiple times. The OFC information is sent to each network element. If there is an OFC information and is inconsistent, the OFC information on the network element is automatically modified.
  • Step 10 10.XXB, 10.XXC, and 10.XXD respectively obtain multiple OFC information and then initiate an OpenFlow link request for each OFC according to the set role, thereby completing the non-access network element and multiple OFCs. OpenFlow build chain.
  • 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:
  • S1 Receive network element information of one or more second network elements that are reported by the first network element, where the first network element is connected to the OFCP through the OF-Config management channel, and the second network element is adjacent to the first network element.
  • Network element
  • S2 Establish an OF-Config management channel with the second network element by using the network element information.
  • 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
  • the processor executes according to the stored program code in the storage medium.
  • the line receives the network element information of the one or more second network elements that are reported by the first network element, where the first network element is connected to the OFCP through the OF-Config management channel, and the second network element is the adjacent network of the first network element.
  • the processor performs to establish an OF-Config management channel with the second network element by using the network element information according to the stored program code in the storage medium.
  • 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 configuration point OFCP receives the network element information of the one or more second network elements reported by the first network element, where the first network element and the OFCP are connected through the OF-Config management channel.
  • the second network element is a neighboring network element of the first network element; the OFCP uses the network element information to establish an OF-Config management channel with the second network element.
  • the network element information of the other network element to be online is reported to the OFCP through the first network element that has been connected to the OFCP, thereby avoiding manually configuring the to-be-raised network element or using a specific command line to obtain the network element information of the network element to be online.
  • Complex and inefficient operation therefore, can solve the problem of low efficiency when deploying network elements in a software-defined network in the related art.

Landscapes

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

Abstract

本发明提供了一种基于软件定义网络的部署方法、装置及系统，其中，该方法包括：配置点OFCP接收第一网元上报的一个或多个第二网元的网元信息，其中，第一网元与OFCP通过OF-Config管理通道连接，第二网元为第一网元的相邻网元；OFCP使用网元信息建立与第二网元的OF-Config管理通道。通过本发明，解决了相关技术中在软件定义网络中部署网元上线时效率低的问题。

Description

基于软件定义网络的部署方法、装置及系统 技术领域
本发明涉及通信领域，具体而言，涉及一种基于软件定义网络的部署方法、装置及系统。
背景技术
相关技术中的软件定义网络(Software Defined Network，简称SDN)通过标准化南向接口(Southbound Interface，简称SBI)将控制面和转发面解耦。其中OpenFlow和OF-Config是国际标准组织ONF制定的南向接口标准，通过标准化南向接口OpenFlow和OF-Config后，控制器和转发设备(后文简称设备)之间解耦，各控制器厂家和设备厂家可以实现互联互通、联合组网。
OF-Config协议全称OpenFlow Management and Configuration Protocol(OpenFlow管理配置协议，其中，OpenFlow是标准组织的名称)，其传输协议是NetConf。图1是根据本发明相关技术的OF-Config和OpenFlow协议组件关系图，图1中，OpenFlow Configuration Point为OpenFlow配置点，OpenFlow Controller为OpenFlow控制器，OpenFlow capable switch为OpenFlow功能交换机，OF logical switch为OpenFlow逻辑交换机，OF Resource(e.g.port)为OpenFlow资源(如端口)，如图1，是OF-Config协议第二章描述的配置点(OpenFlow Configuration Point，简称OFCP)、物理交换机(OpenFlow Capable Swithch，简称OFCS)、逻辑交换机(OpenFlow Logical Swith，简称OFLS)、控制器(OpenFlow Controller，简称OFC)的关系图。
那么OF-Config和OpenFlow通道什么关系呢？根据OF-Config协议第二章的描述，OpenFlow协议假定OFCS已经被配置好了OFC的相关参数，并没定义如何配置，OF-Config就是为了提供这个远程配置OFCS的通道。OF-Config通常是用于实时性要求不那么高的端口使能、去使能等 配置的通道，OpenFlow通常是用于实时性要求比较高的流增加、删除等配置的通道。
图2是根据本发明相关技术中协议的Server和Client的关系图，对于OF-Config通道，OFCS作为Server(服务器)端，OFCP作为Client(客户)端，如图2中左边箭头，链接的建立是OFCP向OFCS发起的。对于OpenFlow通道，由于协议早期版本规定OFLS作为Client端，OFC作为Server端，目前各厂家的实现多数还是这样，如图中右边箭头，链接的建立是OFLS向OFC发起的。
图3是根据本发明相关技术中的SDN组网图，对于一个包含多个网元(OFCS)的网络，OFC和OFCP要实现对整个网络的管理，必须分别跟每个网元各都建立一个OpenFlow链接、一个OF-Config的链接，如图中接入网元和非接入网元1，非接入网元2和3跟非接入网元1相似，图中省略。要建立链接那么作为链接发起方的客户端需要知道作为服务端的IP和端口才能发起建立链接的请求。那么作为OF-Config通道客户端的OFCP如何才能得知所有网元的IP和端口；作为OpenFlow通道客户端的网元(OFCS)如何才能得知OFC的IP和端口呢？
相关技术中采用的方法是：方法一是预先设置，即升级设备的时候将OFC的IP和端口写到网元的配置文件；人工给OFCP制定每个网元的IP和端口。方法二是人工设置，人工给OFCP制定每个网元的IP和端口，等OFCP管理上设备后，人工给每个网元设置OFC的IP和端口。
方法一，存在的问题是运营商OFC的IP不只一个，且随时会变化，配置文件的方式就难以应对。方法二，用户需要用别的手段(如命令行)获取设备的IP，通过OFCP客户端管理上设备后才能给设备配置OFC的IP，对于新开通的网络工作量大，不便捷。
针对相关技术中存在的上述问题，目前尚未发现有效的解决方案。
发明内容
本发明实施例提供了一种基于软件定义网络的部署方法、装置及系统， 以至少解决相关技术中在软件定义网络中部署网元上线时效率低的问题。
根据本发明的一个实施例，提供了一种基于软件定义网络的部署方法，包括：配置点OFCP接收第一网元上报的一个或多个第二网元的网元信息，其中，所述第一网元与所述OFCP通过OF-Config管理通道连接，所述第二网元为所述第一网元的相邻网元；所述OFCP使用所述网元信息建立与所述第二网元的OF-Config管理通道。
可选地，在所述OFCP使用所述网元信息建立与所述第二网元的OF-Config管理通道之后，所述方法还包括：所述OFCP通过所述OF-Config管理通道指示所述第二网元与控制器OFC建立OpenFlow通道。
可选地，所述网元信息包括：IP地址、OFConfig-Port通道端口。
可选地，所述OFCP使用所述网元信息建立与所述第二网元的OF-Config管理通道包括：所述OFCP使用所述IP地址和所述OFConfig-Port字段向所述第二网元发起OF-Config管理通道的链接建立请求；在所述OF-Config管理通道建立完成后，所述OFCP给所述第一网元和所述第二网元下发OFC信息，所述OFC信息包括OFC的IP和OFC的端口。
可选地，所述OFCP通过所述OF-Config管理通道指示所述第二网元与控制器OFC建立OpenFlow通道包括：所述OFCP查询所述第二网元上是否存在OFC信息；在所述第二网元上存在OFC信息时，所述OFCP判断存在OFC信息是否为指定的OFC信息；在所述第二网元上不存在OFC信息或第二网元上存在的OFC信息不是所述指定的OFC信息时，所述OFCP向所述第二网元下发所述指定的OFC信息，其中，所述指定的OFC信息用于描述与所述第二网元之间存在OpenFlow通道的OFC。
根据本发明的一个实施例，提供了一种基于软件定义网络的部署方法，包括：第一网元获取与其相邻的第二网元的网元信息，其中，所述第一网元与配置点OFCP通过OF-Config管理通道连接；所述第一网元将所述网元信息上报给所述OFCP，其中所述网元信息用于所述OFCP与所述第二 网元之间建立OF-Config管理通道。
可选地，所述网元信息包括：IP地址、OFConfig-Port通道端口。
可选地，第一网元获取与其相邻的第二网元的网元信息包括：所述第一网元通过数据通信网络DCN功能使用链路层发现协议LLDP查询所述第二网元的网元信息。
根据本发明的另一个实施例，提供了一种基于软件定义网络的部署装置，包括：接收模块，设置为接收第一网元上报的一个或多个第二网元的网元信息，其中，所述第一网元与所述OFCP通过OF-Config管理通道连接，所述第二网元为所述第一网元的相邻网元；第一建立模块，设置为使用所述网元信息建立与所述第二网元的OF-Config管理通道。
可选地，所述装置还包括：第二建立模块，设置为在所述第一建立模块使用所述网元信息建立与所述第二网元的OF-Config管理通道之后，通过所述OF-Config管理通道指示所述第二网元与控制器OFC建立OpenFlow通道。
可选地，所述网元信息包括：IP地址、OFConfig-Port通道端口。
根据本发明的另一个实施例，提供了另一种基于软件定义网络的部署装置，应用在第一网元中，包括：获取模块，设置为获取与第一网元相邻的第二网元的网元信息，其中，所述第一网元与配置点OFCP通过OF-Config管理通道连接；上报模块，设置为将所述网元信息上报给所述OFCP，其中所述网元信息用于所述OFCP与所述第二网元之间建立OF-Config管理通道。
可选地，所述网元信息包括：IP地址、OFConfig-Port通道端口。
可选地，所述获取模块还包括：获取单元，设置为通过数据通信网络DCN功能使用链路层发现协议LLDP查询所述第二网元的网元信息。
根据本发明的又一个实施例，提供了一种基于软件定义网络的部署系统，包括第一网元、第二网元、配置点OFCP、控制器OFC，所述OFCP包括：接收模块，设置为接收第一网元上报的一个或多个第二网元的网元 信息，其中，所述第二网元为所述第一网元的相邻网元；第一建立模块，设置为使用所述网元信息建立与所述第二网元的OF-Config管理通道；所述包括第一网元包括：获取模块，设置为获取所述第二网元的网元信息，其中，所述第一网元与配置点OFCP通过OF-Config管理通道连接；上报模块，设置为将所述网元信息上报给所述OFCP。
可选地，所述第一网元为接入网元，所述第二网元为非接入网元。
根据本发明的又一个实施例，还提供了一种存储介质。该存储介质设置为存储用于执行以下步骤的程序代码：
配置点OFCP接收第一网元上报的一个或多个第二网元的网元信息，其中，所述第一网元与所述OFCP通过OF-Config管理通道连接，所述第二网元为所述第一网元的相邻网元；
所述OFCP使用所述网元信息建立与所述第二网元的OF-Config管理通道。
在本发明实施例中，还提供了一种存储介质，该存储介质可以存储有执行指令，该执行指令用于执行上述实施例中的前导发送基于软件定义网络的部署方法的实现。
通过本发明实施例，配置点OFCP接收第一网元上报的一个或多个第二网元的网元信息，其中，所述第一网元与所述OFCP通过OF-Config管理通道连接，所述第二网元为所述第一网元的相邻网元；所述OFCP使用所述网元信息建立与所述第二网元的OF-Config管理通道。由于是通过已经连接OFCP的第一网元将待上线的其他网元的网元信息上报给OFCP，避免了人工配置待上线网元或使用特定命令行来获取待上线网元的网元信息的复杂和低效率操作，因此，可以解决相关技术中在软件定义网络中部署网元上线时效率低的问题。
附图说明
此处所说明的附图用来提供对本发明的进一步理解，构成本申请的一 部分，本发明的示意性实施例及其说明用于解释本发明，并不构成对本发明的不当限定。在附图中：
图1是根据本发明相关技术的OF-Config和OpenFlow协议组件关系图；
图2是根据本发明相关技术中协议的Server和Client的关系图；
图3是根据本发明相关技术中的SDN组网图；
图4是根据本发明实施例的一种基于软件定义网络的部署方法的流程图；
图5是根据本发明实施例的另一种基于软件定义网络的部署方法的流程图；
图6是根据本发明实施例的一种基于软件定义网络的部署装置的结构框图；
图7是根据本发明实施例的另一种基于软件定义网络的部署装置的结构框图；
图8是根据本发明实施例的基于软件定义网络的部署系统的结构框图；
图9是根据本发明实施例的邻居信息的结构示意图；
图10是根据本发明实施例的接入网元的自动部署和上线时序图；
图11是根据本发明实施例的非接入网元的自动部署和上线时序图。
具体实施方式
下文中将参考附图并结合实施例来详细说明本发明。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互组合。
需要说明的是，本发明的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。
实施例1
本申请实施例可以运行于图3所示的网络架构上，在本实施例中提供了一种运行于上述网络架构的基于软件定义网络的部署方法，图4是根据本发明实施例的一种基于软件定义网络的部署方法的流程图，如图4所示，该流程包括如下步骤：
步骤S402，配置点OFCP接收第一网元上报的一个或多个第二网元的网元信息，其中，第一网元与OFCP通过OF-Config管理通道连接，第二网元为第一网元的相邻网元；
步骤S404，OFCP使用网元信息建立与第二网元的OF-Config管理通道。
通过上述步骤，配置点OFCP接收第一网元上报的一个或多个第二网元的网元信息，其中，第一网元与OFCP通过OF-Config管理通道连接，第二网元为第一网元的相邻网元；OFCP使用网元信息建立与第二网元的OF-Config管理通道。由于是通过已经连接OFCP的第一网元将待上线的其他网元的网元信息上报给OFCP，避免了人工配置待上线网元或使用特定命令行来获取待上线网元的网元信息的复杂和低效率操作，因此，可以解决相关技术中在软件定义网络中部署网元上线时效率低的问题。
可选地，上述步骤的执行主体OFCP可以为服务器，控制端，总控台等，但不限于此。
可选的，网元信息包括：IP地址、OFConfig-Port通道端口。可以定义网元信息“Neighbor”，包含IP和OFConfig-Port字段，其中IP是该网元的IP地址，OFConfig-Port是该网元作为OF-Config服务端监听的OF-Config通道端口。
可选的，在OFCP使用网元信息建立与第二网元的OF-Config管理通道之后，本实施例还包括：OFCP通过OF-Config管理通道指示第二网元与控制器OFC建立OpenFlow通道。
在根据本实施例的可选实施方式中，OFCP使用网元信息建立与第二网元的OF-Config管理通道包括：
S11，OFCP使用IP地址和OFConfig-Port字段向第二网元发起OF-Config管理通道的链接建立请求；
S12，在OF-Config管理通道建立完成后，OFCP给第一网元和第二网元下发OFC信息，OFC信息包括OFC的IP和OFC的端口。在第二网元与控制器OFC建立OpenFlow通道时，第二网元也可以与控制器OFC建立OpenFlow通道。
在根据本实施例的可选实施方式中，OFCP通过OF-Config管理通道指示第二网元与控制器OFC建立OpenFlow通道包括：
S21，OFCP查询第二网元上是否存在OFC信息；
S22，在第二网元上存在OFC信息时，所述OFCP判断存在OFC信息是否为指定的OFC信息；
S23，在第二网元上不存在OFC信息或第二网元上存在的OFC信息不是指定的OFC信息时，OFCP向第二网元下发指定的OFC信息，其中，指定的OFC信息用于描述与第二网元之间存在OpenFlow通道的OFC。
图5是根据本发明实施例的另一种基于软件定义网络的部署方法的流程图，如图5所示，该流程包括如下步骤：
步骤S502，第一网元获取与其相邻的第二网元的网元信息，其中，第一网元与配置点OFCP通过OF-Config管理通道连接；
步骤S504，第一网元将网元信息上报给OFCP，其中网元信息用于OFCP与第二网元之间建立OF-Config管理通道。
可选地，上述步骤的执行主体第一网元可以为接入设备，基站，MME等，但不限于此。
可选的，网元信息包括：IP地址、OFConfig-Port通道端口。
可选的，第一网元获取与其相邻的第二网元的网元信息包括：第一网元通过数据通信网络DCN功能使用链路层发现协议LLDP查询第二网元的网元信息。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到根据上述实施例的方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本发明的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端设备(可以是手机，计算机，服务器，或者网络设备等)执行本发明各个实施例的方法。
实施例2
在本实施例中还提供了一种基于软件定义网络的部署装置、系统，用于实现上述实施例及优选实施方式，已经进行过说明的不再赘述。如以下所使用的，术语“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的装置较佳地以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。
图6是根据本发明实施例的一种基于软件定义网络的部署装置的结构框图，如图6所示，该装置包括：
接收模块60，设置为接收第一网元上报的一个或多个第二网元的网元信息，其中，第一网元与OFCP通过OF-Config管理通道连接，第二网元为第一网元的相邻网元；
第一建立模块62，设置为使用网元信息建立与第二网元的OF-Config管理通道。
可选的，本实施例的装置还包括：第二建立模块，设置为在第一建立模块使用网元信息建立与第二网元的OF-Config管理通道之后，通过OF-Config管理通道指示第二网元与控制器OFC建立OpenFlow通道。
本实施例中的网元信息包括：IP地址、OFConfig-Port通道端口。
图7是根据本发明实施例的另一种基于软件定义网络的部署装置的结构框图，应用在第一网元中，如图7所示，该装置包括：
获取模块70，设置为获取与第一网元相邻的第二网元的网元信息，其中，第一网元与配置点OFCP通过OF-Config管理通道连接；
上报模块72，设置为将网元信息上报给OFCP，其中网元信息用于OFCP与第二网元之间建立OF-Config管理通道。
本实施例中的，网元信息可以但不限于为：IP地址、OFConfig-Port通道端口。
可选的，获取模块还包括：获取单元，设置为通过数据通信网络DCN功能使用链路层发现协议LLDP查询第二网元的网元信息。
图8是根据本发明实施例的基于软件定义网络的部署系统的结构框图，如图8所示，包括：包括第一网元80、第二网元82、配置点OFCP84、控制器OFC86，OFCP84包括：
接收模块840，设置为接收第一网元上报的一个或多个第二网元的网元信息，其中，第二网元为第一网元的相邻网元；
第一建立模块842，设置为使用网元信息建立与第二网元的OF-Config管理通道；
包括第一网元80包括：
获取模块800，设置为获取第二网元的网元信息，其中，第一网元与配置点OFCP通过OF-Config管理通道连接；
上报模块802，设置为将网元信息上报给OFCP。
具体的，本实施例中的第一网元为接入网元，第二网元为非接入网元。
需要说明的是，上述各个模块是可以通过软件或硬件来实现的，对于后者，可以通过以下方式实现，但不限于此：上述模块均位于同一处理器中；或者，上述各个模块以任意组合的形式分别位于不同的处理器中。
实施例3
本实施例是根据本发明的可选实施例，用于结合具体的场景对本申请进行详细的说明：
本实施例是针对上述软件定义网络中不同厂家设备部署和上线不能应对运营商OFC的IP地址变化和配置工作量大等问题，提出了一种软件定义网络中不同厂家设备自动部署和上线的方法。
本实施例所要解决的技术问题是：基于ONF的OpenFlow和OF-Config南向接口协议的软件定义网络中OFLS和OFC如何才能快速的管理上整个网络中所有的网元。
本发明为了解决以上问题，基于ONF现有框架，通过扩展OF-Config实现一种不同厂家设备自动部署和上线的方法。
本实施例提供了一种实施方法，包括：
网元上电后默认启用DCN(数据通信网络)功能，其中DCN可以使用成熟LLDP等成熟的邻居发现协议，通过DCN网络中的每一个网元都可以发现其它邻居网元的信息。
为了实现上述设备自动部署和上线的方法，我们需要扩展OF-Config协议。我们定义一个“Neighbor”的对象，图9是根据本发明实施例的邻居信息的结构示意图，如图9中右边对象，中间和左边其它三个对象为OF-Config标准中所定义，图9中的表示方法也是OF-Config中用UML图来描述数据模型图(Data Model Diagram)的方法，其中一边实心菱形一边箭头的线表示组合，表示包含关系，OpenFow Capable Switch指向Neighbor的线表示前者包含后者的整体与部分关系，“*”型号表示前者可以包含多个后者。我们定义的“Neighbor”中包含IP和OFConfig-Port字段，其中IP是该网元的IP地址，OFConfig-Port是该网元作为OF-Config服务端监听的OF-Config通道端口。
OFCP通过人工指定接入网元IP和端口的方式与接入网元建链OF-Config管理通道。接入网元通过这个OF-Config管理通道将邻居(其它非接入网元)的信息“Neighbor”上报给OFCP。
OFCP根据接入网元上报的整个网络的“Neighbor”信息，主动发起与每一个网元的OF-Config管理通道建链请求，当OFCP与每一个网元的 OF-Config管理通道建立完成后，OFCP自动给所有接入网元和非接入网元一一配置OFC的IP和端口。
所有接入网元和非接入网元被动通过OF-Config通道接收OFCP的OFC配置完成后，通过DCN网络一一发起跟OFC的OpenFlow链接建立请求，从而建立和OFC的OpenFlow通道。
至此，网络中每个网元跟OFCP和OFC都建立了一个OF-Config和OpenFlow通道，最终达到网络中所有网元的自动部署和上线。以下分别对接入网元和非接入网元进行描述，接入网元和非接入网元的划分见图3。
在本实施例中，分为接入网元和非接入网元，接入网元的自动部署和上线步骤如下：
步骤一、接入网元上电，监听OF-Config管理通道端口；
步骤二、用户使用OFCP通过指定IP的方式建立跟接入网元的OF-Config管理通道；
步骤三、OF-Config链接建立后OFCP自动查询网元上的OFC信息；如果没有OFC信息，则自动下发OFC信息到网元；如果有OFC信息，且不一致，则自动修改网元上的OFC信息。
步骤四、网元得到OFC信息后发起跟OFC的OpenFlow建链请求，从而完成接入网元和OFC间的建链。
非接入网元的自动部署和上线步骤包括：
步骤一、接入网元和非接入网元上电后默认启用DCN；
步骤二、接入网元和非接入网元通过DCN发现邻居；
步骤三、用户使用OFCP通过指定IP的方式建立跟接入网元的OF-Config管理通道；
步骤四、接入网元跟OFCP建立OF-Config链接后，接入网元自动上报所有非接入网元的邻居信息给OFCP；
步骤五、OFCP获取到非接入网元的信息后，主动发起跟每个非接入 网元的OF-Config管理通道链接；
步骤六、OFCP跟每非接入网元的OF-Config管理通道链接建立后OFCP自动查询该网元上的OFC信息；如果没有OFC信息，则自动下发OFC信息到该网元；如果有OFC信息，且不一致，则自动修改该网元上的OFC信息。
步骤七、非接入网元收到OFC信息后发起跟OFC的OpenFlow建链请求，从而完成非接入网元和OFC间的建链。
下面通过扩展OF-Config协议的消息来阐述本实施例中的一种实现方式：
图9是根据本发明实施例的邻居信息的结构示意图，定义邻居信息的结构，通过扩展OF-Config中的对象，向OpenFlow Capable Switch加入表示邻居的Neighbor对象，其中IP表示邻居的IP地址，OFConfig-Port表示该网元作为OF-Config服务端监听的OF-Config通道端口。
图10是根据本发明实施例的接入网元的自动部署和上线时序图，一个OFC的场景，接入网元的自动部署和上线步骤如下：
步骤一、用户给OFCP设置OFC的信息；
步骤二、接入网元IP为10.X.X.A，上电后该网元作为NetConf服务端，监听NetConf默认端口830；
步骤三、用户给OFCP指定接入网元的IP地址和监听的OF-Config端口号；
步骤四、OFCP发起对接入网元[Ip＝10.X.X.A，OFConfig-Port＝830]的建链请求，跟该网元建立OF-Config链接；
步骤五、链接建立后OFCP通过OF-Config通道自动下发OFC对象的查询命令到该网元；如果OFC信息为空，则自动下发OFC信息[Ip＝10.X.X.X，Port＝6653]到该网元；如果有OFC信息，且不一致，则自动修改该网元上的OFC信息为[Ip＝10.X.X.X，Port＝6653]。
步骤六、该网元得到OFC信息[IP＝10.X.X.X，Port＝6653]后自动发起跟对[IP＝10.X.X.X，Port＝6653]发起OpenFlow建链请求，从而完成接入网元和OFC间的OpenFlow建链。
在本实施例中的具体示例中，包括以下具体的场景：
图11是根据本发明实施例的非接入网元的自动部署和上线时序图，一个OFC的场景，非接入网元的自动部署和上线步骤如下：
步骤一、用户给OFCP设置OFC的信息；
步骤二、接入网元上电后默认启用DCN，监听NetConf默认端口830；
步骤三、非接入网元上电后默认启用DCN，监听NetConf默认端口830；
步骤四、接入网元[10.X.X.A]通过DCN发现邻居[10.X.X.B、10.X.X.C、10.X.X.D]三个非接入网元；
步骤五、用户给OFCP指定接入网元的IP地址和监听的OF-Config端口号；
步骤六、OFCP发起对接入网元[IP＝10.X.X.A，OFConfig-Port＝830]的建链请求，跟该网元建立OF-Config链接；
步骤七、接入网元跟OFCP建立链接后，接入网元自动上报所有非接入网元的邻居信息[10.X.X.B、10.X.X.C、10.X.X.D]给OFCP；
步骤八、OFCP获取到非接入网元的信息后，主动发起跟10.X.X.B、10.X.X.C、10.X.X.D的管理通道链接；
步骤九、OFCP跟非接入网元的管理通道链接建立后OFCP自动查询10.X.X.B、10.X.X.C、10.X.X.D上的OFC信息；如果没有OFC信息[IP＝10.X.X.X，Port＝6653]，则自动下发OFC信息到该网元；如果有OFC信息，且不一致，则自动修改该网元上的OFC信息[IP＝10.X.X.X，Port＝6653]。
步骤十、10.X.X.B、10.X.X.C、10.X.X.D分别得到OFC信息[IP＝10.X.X.X，Port＝6653]后分别对IP＝10.X.X.X，Port＝6653发起OpenFlow 建链请求，从而完成非接入网元和OFC间的建链。
多个OFC的场景，接入网元的自动部署和上线步骤如下：
步骤一、用户给OFCP设置多个OFC的信息，并指定OFC的角色是master、slave还是equal；
步骤二、接入网元IP为10.X.X.A，上电后该网元作为NetConf服务端，监听NetConf默认端口830；
步骤三、用户给OFCP指定接入网元的IP地址和监听的OF-Config端口号；
步骤四、OFCP发起对接入网元[Ip＝10.X.X.A，OFConfig-Port＝830]的建链请求，跟该网元建立OF-Config链接；
步骤五、链接建立后OFCP通过OF-Config通道自动下发OFC对象的查询命令到该网元；如果OFC信息为空，则自动下发用户设置的多个OFC信息到该网元；如果有OFC信息，且不一致，则自动修改该网元上的OFC信息。
步骤六、该网元得到多个OFC信息后按设定的角色自动发起对每一个OFC的OpenFlow建链请求，从而完成接入网元和多个OFC间的OpenFlow建链。
多个OFC的场景，非接入网元的自动部署和上线步骤如下：
步骤一、用户给OFCP设置多个OFC的信息，并指定OFC的角色是master、slave还是equal；
步骤二、接入网元上电后默认启用DCN，监听NetConf默认端口830；
步骤三、非接入网元上电后默认启用DCN，监听NetConf默认端口830；
步骤四、接入网元[10.X.X.A]通过DCN发现邻居[10.X.X.B、10.X.X.C、10.X.X.D]，三个非接入网元；
步骤五、用户给OFCP指定接入网元的IP地址和监听的OF-Config 端口号；
步骤六、OFCP发起对接入网元[Ip＝10.X.X.A，OFConfig-Port＝830]的建链请求，跟该网元建立OF-Config链接；
步骤七、接入网元跟OFCP建立链接后，接入网元自动上报所有非接入网元的邻居信息[10.X.X.B、10.X.X.C、10.X.X.D]给OFCP；
步骤八、OFCP获取到非接入网元的信息后，主动发起跟10.X.X.B、10.X.X.C、10.X.X.D的管理通道链接；
步骤九、OFCP跟非接入网元的管理通道链接建立后OFCP自动查询10.X.X.B、10.X.X.C、10.X.X.D上的OFC信息；如果OFC信息为空，则自动下发用户设置的多个OFC信息到每一个网元；如果有OFC信息，且不一致，则自动修改网元上的OFC信息。
步骤十、10.X.X.B、10.X.X.C、10.X.X.D分别得到多个OFC信息后按设定的角色各自发起对每一个OFC的OpenFlow建链请求，从而完成非接入网元和多个OFC间的OpenFlow建链。
实施例4
本发明的实施例还提供了一种存储介质。可选地，在本实施例中，上述存储介质可以被设置为存储用于执行以下步骤的程序代码：
S1，接收第一网元上报的一个或多个第二网元的网元信息，其中，第一网元与OFCP通过OF-Config管理通道连接，第二网元为第一网元的相邻网元；
S2，使用网元信息建立与第二网元的OF-Config管理通道。
可选地，在本实施例中，上述存储介质可以包括但不限于：U盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、移动硬盘、磁碟或者光盘等各种可以存储程序代码的介质。
可选地，在本实施例中，处理器根据存储介质中已存储的程序代码执 行接收第一网元上报的一个或多个第二网元的网元信息，其中，第一网元与OFCP通过OF-Config管理通道连接，第二网元为第一网元的相邻网元；
可选地，在本实施例中，处理器根据存储介质中已存储的程序代码执行使用网元信息建立与第二网元的OF-Config管理通道。
可选地，本实施例中的具体示例可以参考上述实施例及可选实施方式中所描述的示例，本实施例在此不再赘述。
显然，本领域的技术人员应该明白，上述的本发明的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，可选地，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本发明不限制于任何特定的硬件和软件结合。
以上所述仅为本发明的优选实施例而已，并不用于限制本发明，对于本领域的技术人员来说，本发明可以有各种更改和变化。凡在本发明的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。
工业实用性
通过本发明实施例，配置点OFCP接收第一网元上报的一个或多个第二网元的网元信息，其中，所述第一网元与所述OFCP通过OF-Config管理通道连接，所述第二网元为所述第一网元的相邻网元；所述OFCP使用所述网元信息建立与所述第二网元的OF-Config管理通道。由于是通过已经连接OFCP的第一网元将待上线的其他网元的网元信息上报给OFCP，避免了人工配置待上线网元或使用特定命令行来获取待上线网元的网元信息的复杂和低效率操作，因此，可以解决相关技术中在软件定义网络中部署网元上线时效率低的问题。

Claims (16)

  1. 一种基于软件定义网络的部署方法，包括：
    配置点OFCP接收第一网元上报的一个或多个第二网元的网元信息，其中，所述第一网元与所述OFCP通过OF-Config管理通道连接，所述第二网元为所述第一网元的相邻网元；
    所述OFCP使用所述网元信息建立与所述第二网元的OF-Config管理通道。
  2. 根据权利要求1所述的方法，其中，在所述OFCP使用所述网元信息建立与所述第二网元的OF-Config管理通道之后，所述方法还包括：
    所述OFCP通过所述OF-Config管理通道指示所述第二网元与控制器OFC建立OpenFlow通道。
  3. 根据权利要求1所述的方法，其中，所述网元信息包括：IP地址、OFConfig-Port通道端口。
  4. 根据权利要求3所述的方法，其中，所述OFCP使用所述网元信息建立与所述第二网元的OF-Config管理通道包括：
    所述OFCP使用所述IP地址和所述OFConfig-Port字段向所述第二网元发起OF-Config管理通道的链接建立请求；
    在所述OF-Config管理通道建立完成后，所述OFCP给所述第一网元和所述第二网元下发OFC信息，所述OFC信息包括OFC的IP和OFC的端口。
  5. 根据权利要求2所述的方法，其中，所述OFCP通过所述OF-Config管理通道指示所述第二网元与控制器OFC建立OpenFlow通道包括：
    所述OFCP查询所述第二网元上是否存在OFC信息；
    在所述第二网元上存在OFC信息时，所述OFCP判断存在OFC信息是否为指定的OFC信息；
    在所述第二网元上不存在OFC信息或第二网元上存在的OFC信息不是所述指定的OFC信息时，所述OFCP向所述第二网元下发所述指定的OFC信息，其中，所述指定的OFC信息用于描述与所述第二网元之间存在OpenFlow通道的OFC。
  6. 一种基于软件定义网络的部署方法，包括：
    第一网元获取与其相邻的第二网元的网元信息，其中，所述第一网元与配置点OFCP通过OF-Config管理通道连接；
    所述第一网元将所述网元信息上报给所述OFCP，其中所述网元信息用于所述OFCP与所述第二网元之间建立OF-Config管理通道。
  7. 根据权利要求6所述的方法，其中，所述网元信息包括：IP地址、OFConfig-Port通道端口。
  8. 根据权利要求6所述的方法，其中，第一网元获取与其相邻的第二网元的网元信息包括：
    所述第一网元通过数据通信网络DCN功能使用链路层发现协议LLDP查询所述第二网元的网元信息。
  9. 一种基于软件定义网络的部署装置，包括：
    接收模块，设置为接收第一网元上报的一个或多个第二网元的网元信息，其中，所述第一网元与OFCP通过OF-Config管理通道连接，所述第二网元为所述第一网元的相邻网元；
    第一建立模块，设置为使用所述网元信息建立与所述第二网元的OF-Config管理通道。
  10. 根据权利要求9所述的装置，其中，所述装置还包括：
    第二建立模块，设置为在所述第一建立模块使用所述网元信息建 立与所述第二网元的OF-Config管理通道之后，通过所述OF-Config管理通道指示所述第二网元与控制器OFC建立OpenFlow通道。
  11. 根据权利要求9所述的装置，其中，所述网元信息包括：IP地址、OFConfig-Port通道端口。
  12. 一种基于软件定义网络的部署装置，应用在第一网元中，包括：
    获取模块，设置为获取与第一网元相邻的第二网元的网元信息，其中，所述第一网元与配置点OFCP通过OF-Config管理通道连接；
    上报模块，设置为将所述网元信息上报给所述OFCP，其中所述网元信息用于所述OFCP与所述第二网元之间建立OF-Config管理通道。
  13. 根据权利要求12所述的装置，其中，所述网元信息包括：IP地址、OFConfig-Port通道端口。
  14. 根据权利要求12所述的装置，其中，所述获取模块还包括：
    获取单元，设置为通过数据通信网络DCN功能使用链路层发现协议LLDP查询所述第二网元的网元信息。
  15. 一种基于软件定义网络的部署系统，包括第一网元、第二网元、配置点OFCP、控制器OFC，
    所述OFCP包括：
    接收模块，设置为接收第一网元上报的一个或多个第二网元的网元信息，其中，所述第二网元为所述第一网元的相邻网元；
    第一建立模块，设置为使用所述网元信息建立与所述第二网元的OF-Config管理通道；
    所述包括第一网元包括：
    获取模块，设置为获取所述第二网元的网元信息，其中，所述第 一网元与配置点OFCP通过OF-Config管理通道连接；
    上报模块，设置为将所述网元信息上报给所述OFCP。
  16. 根据权利要求15所述的系统，其中，所述第一网元为接入网元，所述第二网元为非接入网元。
PCT/CN2017/097411 2016-08-15 2017-08-14 基于软件定义网络的部署方法、装置及系统 WO2018033050A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610671317.7 2016-08-15
CN201610671317.7A CN107769937A (zh) 2016-08-15 2016-08-15 基于软件定义网络的部署方法、装置及系统

Publications (1)

Publication Number Publication Date
WO2018033050A1 true WO2018033050A1 (zh) 2018-02-22

Family

ID=61196368

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/097411 WO2018033050A1 (zh) 2016-08-15 2017-08-14 基于软件定义网络的部署方法、装置及系统

Country Status (2)

Country Link
CN (1) CN107769937A (zh)
WO (1) WO2018033050A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116743570A (zh) * 2023-08-16 2023-09-12 新华三技术有限公司 设备的自动化上线方法、装置、电子设备及介质

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104837147A (zh) * 2014-02-12 2015-08-12 中兴通讯股份有限公司 无线访问接入点的配置方法及系统
CN105430116A (zh) * 2015-11-30 2016-03-23 北京邮电大学 一种建立控制信道的方法及装置

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101860452B (zh) * 2010-05-21 2015-06-10 中兴通讯股份有限公司 网元的管理方法和系统
WO2013134937A1 (zh) * 2012-03-14 2013-09-19 华为技术有限公司 发送建立连接请求的方法、交换机、服务器及系统
CN104158747B (zh) * 2013-05-14 2019-09-24 中兴通讯股份有限公司 网络拓扑发现方法和系统

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104837147A (zh) * 2014-02-12 2015-08-12 中兴通讯股份有限公司 无线访问接入点的配置方法及系统
CN105430116A (zh) * 2015-11-30 2016-03-23 北京邮电大学 一种建立控制信道的方法及装置

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116743570A (zh) * 2023-08-16 2023-09-12 新华三技术有限公司 设备的自动化上线方法、装置、电子设备及介质
CN116743570B (zh) * 2023-08-16 2023-10-24 新华三技术有限公司 设备的自动化上线方法、装置、电子设备及介质

Also Published As

Publication number Publication date
CN107769937A (zh) 2018-03-06

Similar Documents

Publication Publication Date Title
US9474101B2 (en) Apparatus and system for managing a sensor network
CN109219020A (zh) 一种网络切片方法及系统
CN102143599B (zh) 相邻基站连接的建立方法、建立设备和建立系统
CN111865736B (zh) 一种设备控制方法及装置
RU2533638C2 (ru) Способ и устройство для конфигурирования данных
WO2018024121A1 (zh) 一种网络功能nf管理方法及nf管理设备
WO2016177049A1 (zh) 一种实现接入设备扩缩容的方法和装置
WO2006060952A1 (fr) Procede permettant de transferer des informations de configuration et de gestion de reseau entre des systemes de gestion des elements
CN112671904B (zh) 设备状态信息的传输方法及装置、存储介质、电子装置
WO2010105444A1 (zh) 控制自优化开关的方法、装置和系统
JP2019057905A (ja) イーサネット（登録商標）スイッチ用のロールベースの自動構成システム及び方法
CN105960817B (zh) 通信设备和用于配置通信设备的方法、存储介质
US20150023215A1 (en) TRILL Network Establishing Method, Node, and System
US20240106708A1 (en) Fabric availability and synchronization
CN108650116B (zh) 一种用于dmr中转台ip互联下的分组方法
WO2018033050A1 (zh) 基于软件定义网络的部署方法、装置及系统
WO2011137621A1 (zh) 管理分布式基站的方法和装置
CN105472632A (zh) 一种模拟无线网络的构建方法、装置和系统
WO2016188081A1 (zh) 扩展端口的处理方法、装置及系统
WO2015101100A1 (zh) 网络设备及网络中的业务处理方法
CN112217680A (zh) 基于软件定义广域网的控制器能力基准测试方法和装置
CN103765819A (zh) 一种数据配置方法及网络管理服务器
CN112533304B (zh) 自组网络管理方法、装置、系统、电子设备以及存储介质
US20200351153A1 (en) Anima Network Information Processing Method, Device, and System
WO2016177135A1 (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: 17841022

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: 17841022

Country of ref document: EP

Kind code of ref document: A1