WO2019072147A1 - 一种sdn的业务配置的方法及装置 - Google Patents

一种sdn的业务配置的方法及装置 Download PDF

Info

Publication number
WO2019072147A1
WO2019072147A1 PCT/CN2018/109333 CN2018109333W WO2019072147A1 WO 2019072147 A1 WO2019072147 A1 WO 2019072147A1 CN 2018109333 W CN2018109333 W CN 2018109333W WO 2019072147 A1 WO2019072147 A1 WO 2019072147A1
Authority
WO
WIPO (PCT)
Prior art keywords
model
configuration
service
sdn
controller
Prior art date
Application number
PCT/CN2018/109333
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 EP18866977.4A priority Critical patent/EP3627768A4/en
Publication of WO2019072147A1 publication Critical patent/WO2019072147A1/zh

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08Configuration management of networks or network elements
    • H04L41/0803Configuration setting
    • H04L41/0806Configuration setting for initial configuration or provisioning, e.g. plug-and-play
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08Configuration management of networks or network elements
    • H04L41/0803Configuration setting
    • H04L41/0813Configuration setting characterised by the conditions triggering a change of settings
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08Configuration management of networks or network elements
    • H04L41/0803Configuration setting
    • H04L41/084Configuration by using pre-existing information, e.g. using templates or copying from other elements
    • H04L41/0843Configuration by using pre-existing information, e.g. using templates or copying from other elements based on generic templates
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08Configuration management of networks or network elements
    • H04L41/0876Aspects of the degree of configuration automation
    • H04L41/0883Semiautomatic configuration, e.g. proposals from system
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08Configuration management of networks or network elements
    • H04L41/0895Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/40Arrangements 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
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5041Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
    • H04L41/5045Making service definitions prior to deployment
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/2866Architectures; Arrangements
    • H04L67/30Profiles
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/34Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters 
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/50Network services
    • H04L67/51Discovery or management thereof, e.g. service location protocol [SLP] or web services

Definitions

  • the present invention relates to the field of software defined network (SDN), and specifically relates to a service configuration method and device for an SDN.
  • SDN software defined network
  • the SDN manages the devices in the network through the SDN controller to complete the configuration and management of services, thus simplifying the deployment and maintenance of network services.
  • the SDN controller needs to manage different vendors and different types of devices.
  • the SDN controller delivers the configuration to each device according to the user's orchestration. Different devices usually have different southbound interface models.
  • the SDN controller maps the service data to the corresponding device of the device through the delivery channel.
  • the SDN controller cannot dynamically adjust the device types it manages. Only the southbound interface model corresponding to each type of device can be configured to the SDN controller in advance, and the SDN controller must be restarted to take effect.
  • the embodiment of the invention provides a service configuration method and device for an SDN, which can manage a new type of device without the SDN controller restarting.
  • An SDN service configuration method includes:
  • model correspondence relationship information is correspondence information between the controller configuration model and the device southbound interface model
  • the service data is constructed as device model data by using the model correspondence information, and the device model data is delivered to the corresponding device.
  • the application also provides an SDN service configuration apparatus, including:
  • the configuration module is configured to configure model correspondence relationship information in the SDN controller, where the model correspondence relationship information is correspondence information between the controller configuration model and the device southbound interface model;
  • the service processing module is configured to use the model correspondence relationship information to construct the service data into device model data, and deliver the device model data to the corresponding device.
  • the application also provides an SDN service configuration apparatus, including:
  • a processor configured to read the computer program to perform the operations of the service configuration method of the SDN described above.
  • the present application also provides a computer readable storage medium having stored thereon a computer program, the computer program being executed by a processor to implement the steps of the service configuration method of the SDN described above.
  • FIG. 1 is a schematic flowchart of a method for configuring an SDN service according to an embodiment of the present invention
  • FIG. 2 is a schematic flowchart of sending data according to an embodiment of the present invention
  • FIG. 3 is a schematic diagram of an exemplary specific process of an SDN service configuration method according to an embodiment of the present disclosure
  • FIG. 4 is a schematic structural diagram of a service configuration apparatus of an SDN according to an embodiment of the present invention.
  • FIG. 5 is a schematic diagram of a SDN service configuration process according to an example of the present invention.
  • An embodiment of the present invention provides a service configuration method for an SDN, as shown in FIG. 1 , which may include:
  • Step 101 Configure model correspondence relationship information in the SDN controller, where the model correspondence relationship information is correspondence information between the controller configuration model and the device southbound interface model;
  • Step 102 Construct the service data into the device model data by using the model correspondence information, and deliver the device model data to the corresponding device.
  • the SDN controller can use the model correspondence information to deliver the service data to the corresponding device, so that only the model is updated when a new type of device needs to be added.
  • Correspondence information can be used, no need to hard code, so there is no need to restart the SDN controller to support different devices, easy to implement, low cost, and can adapt to SDN to uniformly manage multi-vendor devices, and often need Update the application requirements of the device types it manages.
  • the configuring the model correspondence relationship information in the SDN controller may include: writing a configuration file in the SDN controller, where the configuration file includes correspondence relationship information between the controller configuration model and the device southbound interface model.
  • the SDN controller can implement compatibility with different devices of different vendors by dynamically loading the configuration file, so that the SDN controller can support different devices of different manufacturers, thereby supporting different SDN controllers without restarting the SDN controller. Type of device.
  • the configuring the model correspondence relationship information in the SDN controller may include: writing, by the SDN controller, a configuration file corresponding to different device types, where the configuration file includes the device southbound interface of the corresponding device type. Correspondence relationship information between the model and the control configuration model. In this way, different configuration files are configured for different device types, which is convenient for management and easier to read when used.
  • the new device type is added to the SDN controller by updating the model correspondence information.
  • the foregoing method may further include: when a new device type needs to be added, creating a pair according to the device southbound interface model of the new device type and the controller configuration model of the SDN controller The model correspondence information of the new type of device should be written to the SDN controller.
  • a configuration file corresponding to the new type device is created and stored in the SDN controller according to the device southbound interface model of the new device type and the controller configuration model of the SDN controller.
  • the configuration file records the correspondence relationship between the device southbound interface model and the controller configuration model of the device of the new type.
  • the configuration file may record the model correspondence relationship information in multiple manners.
  • the configuration file may record a correspondence between a field in the controller configuration model and a field in the device southbound interface model by using a key value mapping format. In this way, not only is it convenient to update the contents of the configuration file, but it is also easy to build device model data based on this configuration file.
  • the constructing the service data into the device model data by using the model correspondence information may include: reading the corresponding device and interface according to the configuration request from the SDN orchestrator (SDN-O)
  • SDN-O SDN orchestrator
  • the model of the device type corresponds to the relationship information
  • the data of the network service is constructed as device model data by using the read model correspondence relationship information.
  • the process may include:
  • Step 201 The user configures the network service by using an SDN orchestrator (SDN-O), and the SDN-O sends a configuration request to the SDN controller, where the configuration request carries the information of the user-specified device and the information of the designated interface.
  • SDN-O SDN orchestrator
  • the information of the specified device may be the name, code, model, manufacturer, or other similar identification information of the device.
  • the information of the specified interface can be the address, code or other similar identification information of the interface.
  • Step 202 After receiving the configuration request of the SDN-O, the SDN controller reads the corresponding model correspondence information according to the information of the user-designated device and the information of the specified interface carried in the SDN controller, and uses the model correspondence information to use the corresponding service information.
  • the data is converted to device model data of the corresponding type of device, and the device model data is delivered to the device specified by the user through the southbound configuration channel.
  • the corresponding model correspondence relationship information refers to the correspondence relationship between the device southbound interface model and the controller configuration model under the device type corresponding to the user specified device.
  • an exemplary implementation process of the foregoing method in this embodiment may include:
  • Step 301 Configure a correspondence relationship between the controller configuration model and the device southbound interface model in the SDN controller through the configuration file.
  • Step 302 The SDN controller dynamically reads the configuration file, and loads the corresponding relationship information between the controller configuration model and the device southbound interface model.
  • Step 303 The SDN-O sends a service to the SDN controller according to the indication of the user.
  • Step 304 The SDN controller converts data required to be delivered into device model data according to the foregoing configuration file loaded at startup;
  • Step 305 The SDN controller sends the device model data to the corresponding device.
  • FIG. 2 and FIG. 3 described above are merely exemplary implementation processes.
  • the foregoing method in this embodiment may also be implemented by other specific processes, which is not limited herein.
  • the embodiment of the present invention further provides an SDN service configuration apparatus, as shown in FIG. 4, which may include:
  • the configuration module 41 is configured to configure model correspondence relationship information in the SDN controller, where the model correspondence relationship information is correspondence information between the controller configuration model and the device southbound interface model;
  • the service processing module 42 is configured to use the model correspondence relationship information to construct service data into device model data, and deliver the device model data to the corresponding device.
  • the configuration module 41 is configured to write a configuration file in the SDN controller, where the configuration file includes correspondence relationship information between the controller configuration model and the device southbound interface model.
  • the configuration module 4 is configured to write a configuration file corresponding to different device types in the SDN controller, where the configuration file includes the device southbound interface model and the control configuration model of the corresponding device type. Correspondence information.
  • the configuration file may record a correspondence between a field in the controller configuration model and a field in the southbound interface model of the device by using a key value mapping format.
  • the service processing module 42 is configured to read the model correspondence relationship information of the corresponding device type according to the device and interface specified by the network service delivered by the user, and utilize the read model correspondence relationship.
  • the information constructs the data of the network service as device model data.
  • the configuration module 41 and the service processing module 42 in the service configuration device of the SDN may be software, hardware, or a combination of the two.
  • the service configuration device of the SDN in this embodiment may be disposed in the computing device.
  • the computing device can be a server that can run an SDN controller.
  • the embodiment of the invention further provides an SDN service configuration apparatus, including:
  • a processor configured to read the computer program to perform the operations of the service configuration method of the SDN described above.
  • the service configuration device of the SDN in this embodiment may be implemented by any computing device capable of supporting the corresponding function.
  • the computing device can be a server that can run an SDN controller.
  • the embodiment of the present invention further provides a computer readable storage medium, where the computer readable storage medium stores a computer program, and when the computer program is executed by the processor, the steps of the service configuration method of the SDN are implemented.
  • the computer readable storage medium may include: a USB flash drive, a Read-Only Memory (ROM), a Random Access Memory (RAM), a mobile hard disk, a magnetic disk, or an optical disk.
  • ROM Read-Only Memory
  • RAM Random Access Memory
  • mobile hard disk a magnetic disk
  • magnetic disk a magnetic disk
  • optical disk a variety of media that can store program code.
  • This example uses the interface configuration as an example for detailed description.
  • the controller configuration model, xml file description, as shown in Table 1 is an example of a controller configuration model configured for an interface, wherein the controller configuration model is described using an xml file according to a specific service drawing field.
  • the device southbound interface model can be a yang file.
  • the device southbound interface model is an interface file used by different vendors to configure services.
  • Table 2 below shows an example of the southbound interface model of the device of the A manufacturer.
  • the name of the southbound interface model of the device is zxr10-interfaces@2016-06-22.yang.
  • Table 3 below shows an example of the southbound interface model of the device from the B vendor.
  • the name of the southbound interface model of the device is port-config.yang.
  • the correspondence relationship between the controller configuration model and the device southbound interface model can be obtained.
  • the correspondence information can be implemented as a configuration file.
  • the configuration file is identified in plain text format, using the "Key-Value" mapping format. The left side is the corresponding field in the business model, and the right side is the field in the southbound interface yang file of the device corresponding to different vendors.
  • Table 4 is a configuration file of the correspondence between the controller configuration model and the southbound interface model of the A vendor device.
  • Table 5 is a configuration file of the correspondence between the controller configuration model and the southbound interface model of the B vendor device.
  • the implementation process of configuring an IP address for the interface of the specified device by using the SDN controller, as shown in FIG. 5, may include:
  • Step 501 The user configures the network service of the A vendor by using the SDN-O.
  • the SDN-O sends a configuration request to the SDN controller, where the configuration request carries the information of the user-specified device, the information of the specified interface, and the IP address of the specified interface.
  • Step 502 The SDN controller receives the configuration request, and reads a corresponding configuration file of the corresponding relationship between the controller configuration model and the A-device device southbound interface model according to the device type indicated in the information of the user-specified device.
  • Step 503 The SDN controller constructs the data configured by the user as the device model data of the A vendor according to the correspondence described in the foregoing configuration file.
  • Step 504 The SDN controller sends the constructed device model data to the device corresponding to the A vendor through the southbound configuration channel of the device.
  • computer storage medium includes volatile and nonvolatile, implemented in any method or technology for storing information, such as computer readable instructions, data structures, program modules, or other data. , removable and non-removable media.
  • Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disc (DVD) or other optical disc storage, magnetic cartridge, magnetic tape, magnetic disk storage or other magnetic storage device, or may Any other medium used to store the desired information and that can be accessed by the computer.
  • communication media typically embodies computer readable instructions, data structures, program modules or other data in a modulated data signal, such as a carrier wave or other transport mechanism, and can include any information delivery media.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Automation & Control Theory (AREA)
  • Stored Programmes (AREA)
  • Telephonic Communication Services (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

一种SDN的业务配置方法及装置,包括:在SDN控制器配置模型对应关系信息,所述模型对应关系信息为控制器配置模型与设备南向接口模型的对应关系信息(101);利用所述模型对应关系信息将业务数据构建为设备模型数据,并将所述设备模型数据下发到相应设备(102)。

Description

一种SDN的业务配置的方法及装置 技术领域
本申请涉及软件定义网络(SDN,Software Defined Network)技术领域,具体涉及一种SDN的业务配置方法及装置。
背景技术
SDN通过SDN控制器统一管理网络中的设备来完成业务的配置和管理,从而简化网络业务的部署和维护。
SDN控制器需要管理不同厂家、不同类型的设备,SDN控制器根据用户的编排将配置下发到各个设备,不同设备通常具有不同的南向接口模型。在一些情况下,SDN控制器将业务数据映射为设备的配置模型通过下发通道下发到对应的设备。但SDN控制器无法动态调整其管理的设备类型,只能预先将每种类型设备对应的南向接口模型配置到SDN控制器,并且必须将SDN控制器重启才能生效。
对于SDN控制器无法在不重启的情况下管理新类型设备的问题,目前尚未提出有效的解决方案。
发明概述
以下是对本文详细描述的主题的概述。本概述并非是为了限制权利要求的保护范围。
本发明实施例提供了一种SDN的业务配置方法及装置,能够在SDN控制器不重启的情况下管理新类型设备。
本申请提供了如下技术方案:
一种SDN的业务配置方法,包括:
在SDN控制器配置模型对应关系信息,所述模型对应关系信息为控制器配置模型与设备南向接口模型的对应关系信息;
利用所述模型对应关系信息将业务数据构建为设备模型数据,并将所述设备模型数据下发到相应设备。
本申请还提供了一种SDN的业务配置装置,包括:
配置模块,设置为在SDN控制器配置模型对应关系信息,所述模型对应关系信息为控制器配置模型与设备南向接口模型的对应关系信息;
业务处理模块,设置为利用所述模型对应关系信息将业务数据构建为设备模型数据,并将所述设备模型数据下发到相应设备。
本申请还提供了一种SDN的业务配置装置,包括:
存储有计算机程序的存储器;
处理器,配置为读取所述计算机程序以执行上述SDN的业务配置方法的操作。
本申请还提供了一种计算机可读存储介质,所述计算机可读存储介质上存储有计算机程序,所述计算机程序被处理器执行时实现上述SDN的业务配置方法的步骤。
在阅读并理解了附图和详细描述后,可以明白其他方面。
附图概述
图1为本发明实施例提供的SDN业务配置方法的流程示意图;
图2为本发明实施例提供的下发数据的流程示意图;
图3为本发明实施例提供的SDN业务配置方法的示例性具体流程示意图;
图4为本发明实施例提供的SDN的业务配置装置的组成结构示意图;
图5为本发明示例提供的SDN业务配置流程示意图。
详述
下文中将结合附图对本发明的实施例进行详细说明。
在附图的流程图示出的步骤可以在诸如一组计算机可执行指令的计算机系统中执行。并且,虽然在流程图中示出了逻辑顺序,但是在某些情况下, 可以以不同于此处的顺序执行所示出或描述的步骤。
在一些情况下,SDN控制器南向接口的实现方案中,在下发不同厂商的设备时,需要进行硬编码,并且需要重新启动SDN控制器以支持不同的设备。
本发明实施例提供了一种SDN的业务配置方法,如图1所示,可以包括:
步骤101,在SDN控制器配置模型对应关系信息,所述模型对应关系信息为控制器配置模型与设备南向接口模型的对应关系信息;
步骤102,利用所述模型对应关系信息将业务数据构建为设备模型数据,并将所述设备模型数据下发到相应设备。
本实施例中,通过将模型对应关系信息配置到SDN控制器,使得SDN控制器可利用该模型对应关系信息将业务数据下发到相应设备,这样,在需要添加新类型的设备时只更新模型对应关系信息即可,不再需要硬编码,从而也就不再需要重新启动SDN控制器来支持不同的设备,易于实现,成本低,而且可适应SDN需统一管理多厂商的设备、以及常常需要更新其所管理的设备类型的应用需求。
本实施例中,所述在SDN控制器配置模型对应关系信息,可以包括:在SDN控制器写入配置文件,所述配置文件包含控制器配置模型与设备南向接口模型的对应关系信息。这样,SDN控制器通过动态加载该配置文件即可实现对不同厂商的不同设备的兼容,从而使得SDN控制器可支持不同厂家的不同设备,从而在不重启SDN控制器的情况下使其支持不同类型的设备。
作为一种其他实现方式,所述在SDN控制器配置模型对应关系信息,可以包括:在SDN控制器写入对应不同设备类型的配置文件,所述配置文件包含相应设备类型下的设备南向接口模型与所述控制配置模型的对应关系信息。这样,针对不同设备类型配置不同的配置文件,方便管理,在使用时也更易于读取。
在需要增加新的设备类型时,通过更新模型对应关系信息来将该新的设备类型添加到SDN控制器中。作为一种实现方式,需要增加新的设备类型时,上述方法还可以包括:需要增加新的设备类型时,根据新设备类型的设备南向接口模型以及SDN控制器的控制器配置模型,创建对应该新类型设备的模 型对应关系信息并写入SDN控制器中。作为一种实现方式,需要增加新的设备类型时,根据新设备类型的设备南向接口模型以及SDN控制器的控制器配置模型,创建对应该新类型设备的配置文件并存储在SDN控制器中,该配置文件中记录有该新类型设备的设备南向接口模型与控制器配置模型之间的对应关系信息。
本实施例中,配置文件可以采用多种方式记录所述模型对应关系信息。作为一种实现方式,所述配置文件可以使用键值映射格式记录所述控制器配置模型中字段与所述设备南向接口模型中字段的对应关系。如此,不仅方便更新配置文件的内容,而且易于基于此配置文件构建设备模型数据。
本实施例中,所述利用模型对应关系信息将业务数据构建为设备模型数据,可以包括:根据来自SDN协同器(SDN Orchestrator,SDN-O)的配置请求中指定的设备、接口,读取相应设备类型的所述模型对应关系信息,并利用所读取的模型对应关系信息将所述网络业务的数据构建为设备模型数据。
下面对本实施例技术细节的示例性实现方式进行详细说明。
如图2所示,为步骤102的示例性实现过程,该过程可以包括:
步骤201,用户通过SDN协同器(SDN Orchestrator,SDN-O)配置网络业务,SDN-O向SDN控制器发送配置请求,该配置请求中携带用户指定设备的信息、指定接口的信息;
实际应用中,指定设备的信息可以是设备的名称、代号、型号、厂商或其他类似的标识信息。指定接口的信息可以是接口的地址、代码或其他类似的标识信息。
步骤202,SDN控制器在收到SDN-O的配置请求后,根据其中携带的用户指定设备的信息、指定接口的信息读取相应的模型对应关系信息,利用该模型对应关系信息将相应业务的数据转换为对应类型设备的设备模型数据,并通过南向配置通道将该设备模型数据下发到用户指定的设备。
这里,相应的模型对应关系信息是指用户指定设备所对应设备类型下的设备南向接口模型与控制器配置模型的对应关系信息。
如图3所示,为本实施例上述方法的示例性实现过程,该过程可以包括:
步骤301,通过配置文件在SDN控制器配置控制器配置模型和设备南向接口模型的对应关系信息;
步骤302,SDN控制器动态读取配置文件,加载控制器配置模型和设备南向接口模型的对应关系信息;
步骤303,SDN-O根据用户的指示,向SDN控制器下发业务;
步骤304,SDN控制器根据启动时加载的上述配置文件,将需要所下发业务的数据转换为设备模型数据;
步骤305,SDN控制器将所述设备模型数据下发到对应的设备。
需要说明的是,上述图2和图3仅为示例性实现流程。本实施例的上述方法还可以通过其他具体流程实现,对此,本文不予限制。
本发明实施例还提供了一种SDN的业务配置装置,如图4所示,可以包括:
配置模块41,设置为在SDN控制器配置模型对应关系信息,所述模型对应关系信息为控制器配置模型与设备南向接口模型的对应关系信息;
业务处理模块42,设置为利用所述模型对应关系信息将业务数据构建为设备模型数据,并将所述设备模型数据下发到相应设备。
本实施例中,所述配置模块41,是设置为在SDN控制器写入配置文件,所述配置文件包含控制器配置模型与设备南向接口模型的对应关系信息。
本实施例中,所述配置模块4,是设置为在SDN控制器写入对应不同设备类型的配置文件,所述配置文件包含相应设备类型下的设备南向接口模型与所述控制配置模型的对应关系信息。
一种实现方式中,所述配置文件可以使用键值映射格式记录所述控制器配置模型中字段与所述设备南向接口模型中字段的对应关系。
本实施例中,所述业务处理模块42,是设置为根据用户下发的网络业务指定的设备、接口,读取相应设备类型的所述模型对应关系信息,并利用所读取的模型对应关系信息将所述网络业务的数据构建为设备模型数据。
实际应用中,上述SDN的业务配置装置中配置模块41、业务处理模块42分别可以是软件、硬件或两者的结合。
本实施例中SDN的业务配置装置可设置于计算设备中。一种实现方式中,该计算设备可以是可运行SDN控制器的服务器。
本发明实施例还提供了一种SDN的业务配置装置,包括:
存储有计算机程序的存储器;
处理器,配置为读取所述计算机程序以执行上述SDN的业务配置方法的操作。
实际应用中,本实施例中SDN的业务配置装置可通过任何能够支持相应功能的计算设备实现。一种实现方式中,该计算设备可以是可运行SDN控制器的服务器。
本实施例的其他技术细节参照上述SDN的业务配置方法实施例。
本发明实施例还提供了一种计算机可读存储介质,所述计算机可读存储介质上存储有计算机程序,所述计算机程序被处理器执行时实现前述SDN的业务配置方法的步骤。
在本实施例中,上述计算机可读存储介质可以包括:U盘、只读存储器(ROM,Read-Only Memory)、随机存取存储器(RAM,Random Access Memory)、移动硬盘、磁碟或者光盘等各种可以存储程序代码的介质。
本实施例的其他技术细节参照上述SDN的业务配置方法实施例。
下面对上述各实施例的示例性实现方式进行详细说明。需要说明的是,下文各示例可任意结合。并且,在实际应用中,上述各实施例还可以有其他的实现方式,下文示例中各流程、执行过程等也可以根据实际应用的需要进行调整。
本示例以接口配置为例进行详细说明。
本示例中,控制器配置模型,xml文件描述,如表1所示为接口配置的控制器配置模型示例,其中,控制器配置模型根据具体的业务抽字段,使用xml文件进行描述。
Figure PCTCN2018109333-appb-000001
表1
设备南向接口模型可以为yang文件。本示例中,设备南向接口模型是不同厂商配置业务使用的接口文件。
下表2为A厂商的设备南向接口模型示例,该设备南向接口模型的名称为zxr10-interfaces@2016-06-22.yang。
Figure PCTCN2018109333-appb-000002
Figure PCTCN2018109333-appb-000003
Figure PCTCN2018109333-appb-000004
表2
下表3为B厂商的设备南向接口模型示例,该设备南向接口模型的名称为port-config.yang。
Figure PCTCN2018109333-appb-000005
Figure PCTCN2018109333-appb-000006
Figure PCTCN2018109333-appb-000007
表3
基于控制器配置模型以及各设备南向接口模块,可以得到控制器配置模型与设备南向接口模型的对应关系信息。本示例中,该对应关系信息可以实现为配置文件。本示例中,该配置文件以纯文本格式标识,使用”Key-Value”映射格式,左侧为业务模型中对应的字段,右侧为不同厂商对应的设备南向接口yang文件中的字段。
基于上述表1和表2得到的配置文件具体示例如下表4所示,表4为控制器配置模型和A厂商设备南向接口模型对应关系的配置文件。
Figure PCTCN2018109333-appb-000008
表4
基于上述表1和表3得到的配置文件具体示例如下表5所示,表5为控制器配置模型和B厂商设备南向接口模型对应关系的配置文件。
Figure PCTCN2018109333-appb-000009
表5
基于本示例的上述配置文件,以A厂商为例,用户通过SDN控制器给指定的设备的接口配置IP地址的实现过程,如图5所示,可以包括:
步骤501,用户通过SDN-O配置A厂商的网络业务,SDN-O向SDN控制器发送配置请求,该配置请求中携带用户指定设备的信息、指定接口的信息、以及指定接口的IP地址。
步骤502,SDN控制器接收所述配置请求,根据所述用户指定设备的信息中指示的设备类型,读取对应的“控制器配置模型和A厂商设备南向接口模型对应关系的配置文件”。
步骤503,SDN控制器根据上述的配置文件中描述的对应关系,将用户配置的数据构建为A厂商的设备模型数据。
步骤504,SDN控制器将构建好的设备模型数据通过设备南向配置通道下发到对应A厂商的设备。
本领域普通技术人员可以理解,上文中所公开方法中的全部或某些步骤、系统、装置中的功能模块/单元可以被实施为软件、固件、硬件及其适当的组合。在硬件实施方式中,在以上描述中提及的功能模块/单元之间的划分不一定对应于物理单元的划分;例如,一个物理组件可以具有多个功能,或者一个功能或步骤可以由若干物理组件合作执行。某些组件或所有组件可以被实施为由处理器,如数字信号处理器或微处理器执行的软件,或者被实施为硬件,或者被实施为集成电路,如专用集成电路。这样的软件可以分布在计算机可读介质上,计算机可读介质可以包括计算机存储介质(或非暂时性介质)和通信介质(或暂时性介质)。如本领域普通技术人员公知的,术语计算机存储介质包括用于存储信息(诸如计算机可读指令、数据结构、程序模块或其他数据)的任何方法或技术中实施的易失性和非易失性、可移除和不可移除介质。计算机存储介质包括但不限于RAM、ROM、EEPROM、闪存或其他存储器技术、CD-ROM、数字多功能盘(DVD)或其他光盘存储、磁盒、磁带、磁盘存储或其他磁存储装置、或者可以用于存储期望的信息并且可以被计算机访问的任何其他的介质。此外,本领域技术人员公知的是,通信介质通常包含计算机可读指令、数据结构、程序模块或者诸如载波或其他传输机制之类的调制数据信号中的其他数据,并且可包括任何信息递送介质。

Claims (12)

  1. 一种软件定义网络SDN的业务配置方法,包括:
    在SDN控制器配置模型对应关系信息,所述模型对应关系信息为控制器配置模型与设备南向接口模型的对应关系信息(101);
    利用所述模型对应关系信息将业务数据构建为设备模型数据,并将所述设备模型数据下发到相应设备(102)。
  2. 根据权利要求1所述的业务配置方法,其中,
    所述在SDN控制器配置模型对应关系信息,包括:在SDN控制器写入配置文件,所述配置文件包含控制器配置模型与设备南向接口模型的对应关系信息。
  3. 根据权利要求1所述的业务配置方法,其中,所述在SDN控制器配置模型对应关系信息,包括:
    在SDN控制器写入对应不同设备类型的配置文件,所述配置文件包含相应设备类型下的设备南向接口模型与所述控制配置模型的对应关系信息。
  4. 根据权利要求2或3所述的业务配置方法,其中,
    所述配置文件使用键值映射格式记录所述控制器配置模型中字段与所述设备南向接口模型中字段的对应关系。
  5. 根据权利要求1至3中任一项所述的业务配置方法,其中,所述利用所述模型对应关系信息将业务数据构建为设备模型数据,包括:
    根据来自SDN协同器SDN-O的配置请求中指定的设备、接口,读取相应设备类型的所述模型对应关系信息,并利用所读取的模型对应关系信息将所述网络业务的数据构建为设备模型数据。
  6. 一种软件定义网络SDN的业务配置装置,包括:
    配置模块(41),设置为在SDN控制器配置模型对应关系信息,所述模型对应关系信息为控制器配置模型与设备南向接口模型的对应关系信息;
    业务处理模块(42),设置为利用所述模型对应关系信息将业务数据构建为设备模型数据,并将所述设备模型数据下发到相应设备。
  7. 根据权利要求6所述的业务配置装置,其中,
    所述配置模块(41),是设置为在SDN控制器写入配置文件,所述配置文件包含控制器配置模型与设备南向接口模型的对应关系信息。
  8. 根据权利要求6所述的业务配置装置,其中,
    所述配置模块(41),是设置为在SDN控制器写入对应不同设备类型的配置文件,所述配置文件包含相应设备类型下的设备南向接口模型与所述控制配置模型的对应关系信息。
  9. 根据权利要求7或8所述的业务配置方法,其中,
    所述配置文件使用键值映射格式记录所述控制器配置模型中字段与所述设备南向接口模型中字段的对应关系。
  10. 根据权利要求6至8中任一项所述的业务配置装置,其中,
    所述业务处理模块(42),是设置为根据用户下发的网络业务指定的设备、接口,读取相应设备类型的所述模型对应关系信息,并利用所读取的模型对应关系信息将所述网络业务的数据构建为设备模型数据。
  11. 一种软件定义网络SDN的业务配置装置,包括:
    存储有计算机程序的存储器;
    处理器,配置为读取所述计算机程序以执行如权利要求1至5中任一项所述SDN的业务配置方法的操作。
  12. 一种计算机可读存储介质,所述计算机可读存储介质上存储有计算机程序,所述计算机程序被处理器执行时实现如权利要求1至5中任一项所述软件定义网络SDN的业务配置方法的步骤。
PCT/CN2018/109333 2017-10-10 2018-10-08 一种sdn的业务配置的方法及装置 WO2019072147A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP18866977.4A EP3627768A4 (en) 2017-10-10 2018-10-08 SERVICE CONFIGURATION PROCESS AND APPARATUS FOR SDN

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710935594.9 2017-10-10
CN201710935594.9A CN109660372B (zh) 2017-10-10 2017-10-10 一种sdn的业务配置的方法及装置

Publications (1)

Publication Number Publication Date
WO2019072147A1 true WO2019072147A1 (zh) 2019-04-18

Family

ID=66100427

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/109333 WO2019072147A1 (zh) 2017-10-10 2018-10-08 一种sdn的业务配置的方法及装置

Country Status (3)

Country Link
EP (1) EP3627768A4 (zh)
CN (1) CN109660372B (zh)
WO (1) WO2019072147A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111008189A (zh) * 2019-11-26 2020-04-14 浙江电子口岸有限公司 一种动态数据模型构建方法
CN112865999A (zh) * 2019-11-28 2021-05-28 华为技术有限公司 信息处理方法及相关设备

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110113197B (zh) * 2019-04-26 2022-10-11 新华三技术有限公司合肥分公司 Sdn控制器配置网络设备的方法和sdn控制器
CN110661651A (zh) * 2019-09-06 2020-01-07 北京浪潮数据技术有限公司 一种sdn控制器数据管理方法、系统、装置及可读存储介质
CN112769699B (zh) * 2019-11-05 2022-04-15 烽火通信科技股份有限公司 一种sd-wan网络中路由信息分发和更新的方法及控制器
CN112217693B (zh) * 2020-11-17 2022-02-22 迈普通信技术股份有限公司 一种控制器测试方法、装置、电子设备及存储介质
CN114205205A (zh) * 2022-02-15 2022-03-18 北京华环电子股份有限公司 一种兼容不同yang模型的南向接口实现方法及装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106470111A (zh) * 2015-08-14 2017-03-01 中国电信股份有限公司 基于sdn架构的延伸设备接入方法、控制器和sdn系统
CN106936857A (zh) * 2015-12-29 2017-07-07 中国电信股份有限公司 一种混合云的连接管理方法、sdn控制器及混合云系统
CN107147509A (zh) * 2016-03-01 2017-09-08 中兴通讯股份有限公司 虚拟专用网业务实现方法、装置及通信系统

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102141973B (zh) * 2010-02-02 2013-12-25 联想(北京)有限公司 一种管理机群的方法、装置以及机群管理与监控系统
CN103326884B (zh) * 2013-05-30 2016-06-01 烽火通信科技股份有限公司 Sdn网络中结合流检测和包检测的业务流感知系统及方法
CN105991299B (zh) * 2015-03-04 2021-04-13 阿尔卡特朗讯 在sdn网络中对数据流进行计费的方法、装置与系统
US10511490B2 (en) * 2015-06-19 2019-12-17 International Business Machines Corporation Automated configuration of software defined network controller
CN106254271B (zh) * 2016-08-08 2019-07-19 北京邮电大学 一种用于软件定义网络的可编程队列配置方法及装置
CN107171852B (zh) * 2017-06-15 2019-11-08 烽火通信科技股份有限公司 基于OpenFlow的二层业务配置系统及其方法

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106470111A (zh) * 2015-08-14 2017-03-01 中国电信股份有限公司 基于sdn架构的延伸设备接入方法、控制器和sdn系统
CN106936857A (zh) * 2015-12-29 2017-07-07 中国电信股份有限公司 一种混合云的连接管理方法、sdn控制器及混合云系统
CN107147509A (zh) * 2016-03-01 2017-09-08 中兴通讯股份有限公司 虚拟专用网业务实现方法、装置及通信系统

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
DONG ZHONGPING: "Model-Driven-based SDN end-to-end quality assurance system", TELECOMMUNICATIONS TECHNOLOGY, vol. 7, 31 July 2016 (2016-07-31), pages 52 - 56, XP009517725, ISSN: 1000-1247 *
See also references of EP3627768A4 *

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111008189A (zh) * 2019-11-26 2020-04-14 浙江电子口岸有限公司 一种动态数据模型构建方法
CN111008189B (zh) * 2019-11-26 2023-08-25 浙江电子口岸有限公司 一种动态数据模型构建方法
CN112865999A (zh) * 2019-11-28 2021-05-28 华为技术有限公司 信息处理方法及相关设备
CN112865999B (zh) * 2019-11-28 2022-08-09 华为技术有限公司 信息处理方法及相关设备

Also Published As

Publication number Publication date
CN109660372B (zh) 2021-12-14
CN109660372A (zh) 2019-04-19
EP3627768A4 (en) 2021-03-03
EP3627768A1 (en) 2020-03-25

Similar Documents

Publication Publication Date Title
WO2019072147A1 (zh) 一种sdn的业务配置的方法及装置
CN107870968B (zh) 对文件系统卷执行实时更新
CN102402446B (zh) 应用软件的安装方法和应用软件的安装装置
US8443361B2 (en) Systems and methods for tracking a history of changes associated with software packages in a computing system
US10146556B2 (en) System and method to perform an OS boot using service location protocol and launching OS using a dynamic update of network boot order without a reboot
US10656845B2 (en) System and method for managing container image
US11003438B2 (en) Method and device for incremental upgrade
US9501296B2 (en) Hypervisor automation manager for starting an operation system with customization data from a disk image
CN109831540B (zh) 分布式存储方法、装置、电子设备及存储介质
CN104158858A (zh) 一种访问分布式集群文件系统方法及系统
CN107463467B (zh) 一种可快速还原虚拟化平台的方法及系统
US10346150B2 (en) Computerized system and method for patching an application by separating executables and working data using different images
US20130167148A1 (en) Computing device and virtual machine operation control method
US20140372560A1 (en) Maintaining system firmware images remotely using a distribute file system protocol
US10474491B2 (en) Method and apparatus for managing cloud server in cloud environment
CN104182257A (zh) 应用软件的安装方法和应用软件的安装装置
CN111433747B (zh) 用于加载操作系统的虚拟存储器
CN109684028B (zh) 一种操作系统与用户数据分离的方法、装置及设备
US11176089B2 (en) Systems and methods for implementing dynamic file systems
US9983866B1 (en) Upgrade compatibility checks in a client-server environment
WO2018028321A1 (zh) 一种虚拟外置存储设备的管理方法、装置及终端
CN110928639B (zh) 一种Windows虚拟化镜像分层管理方法及装置
US10102020B2 (en) Methods, systems, and computer readable media for virtual machine (VM) deployment using read-only memory
WO2016202030A1 (zh) 资源配置加载方法及装置
CN106681771B (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: 18866977

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2018866977

Country of ref document: EP

Effective date: 20191220

NENP Non-entry into the national phase

Ref country code: DE