WO2018001253A1 - 多子网元分层管理的方法及装置 - Google Patents

多子网元分层管理的方法及装置 Download PDF

Info

Publication number
WO2018001253A1
WO2018001253A1 PCT/CN2017/090405 CN2017090405W WO2018001253A1 WO 2018001253 A1 WO2018001253 A1 WO 2018001253A1 CN 2017090405 W CN2017090405 W CN 2017090405W WO 2018001253 A1 WO2018001253 A1 WO 2018001253A1
Authority
WO
WIPO (PCT)
Prior art keywords
subnet
sub
network
sent
information
Prior art date
Application number
PCT/CN2017/090405
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 WO2018001253A1 publication Critical patent/WO2018001253A1/zh

Links

Images

Definitions

  • the present disclosure relates to the field of subrack management technologies, for example, to a method and apparatus for multi-subnet element hierarchical management.
  • the subrack management method in the related art is mainly based on a single network element flat management technology, that is, the managed subracks are all included in a single network element, and the subrack includes a primary subrack and a secondary subrack, and the primary subrack carries the primary subrack.
  • the main subrack and the slave subrack are cascaded and communicated with each other through the monitoring board.
  • the entire network element runs a main control board on the main subrack.
  • the main control board serves as the external interface of the NE.
  • the main control board controls and manages all the subracks and boards in the NE.
  • the board is the service board.
  • the main control board needs to have the processing capability of managing thousands or even tens of thousands of boards, which is the data processing capability of the current stage processor and the main control board space cannot support;
  • the communication and connection of the internal subrack of the network element, as well as the communication overhead, may limit the extension of the subrack
  • the solution provided in this embodiment solves the problem that the subrack management method in the related art cannot meet the requirements for the diversity and scalability of the subrack.
  • a method for hierarchical management of multiple subnets includes:
  • Each of the plurality of subnet elements receives the dedicated subnet configuration data sent by the network management system, and delivers the received private subnet configuration data to respective service boards, and the Each subnet element generates subnet meta service information according to the specific subnet element configuration data;
  • the top logical unit receives the subnet element device information sent by the network management unit;
  • the top-level logic unit receives the sub-network element service information sent by each sub-network element, and generates, according to the sub-sub-element device information and the sub-sub-element service information, for controlling and scheduling each sub-network element. Controlling and scheduling commands, so that each subnet element controls and schedules its respective service board according to the control and scheduling commands.
  • each sub-network element includes a main control board and a plurality of the service boards, where the main control board receives the dedicated sub-network element configuration data sent by the network management system and the control and scheduling commands sent by the top-level logic unit.
  • the subnet meta service information is sent to the top level logical unit.
  • the top logic unit is disposed in a main control board of any one of the plurality of subnet elements.
  • the top level logic unit includes a control plane and a top level proxy
  • the method further includes: receiving, by the top-level proxy, the sub-network device information sent by the network management, and sending the sub-sub-device information to the control plane, so that the control plane saves the sub-sub-device information.
  • the top level logic unit further includes a communication agent
  • the method further includes: when the subnet element receives the subnet element device information sent by the network management, the main control board of the subnet element sends the subnet element device information to the communication of the top level logic unit And a proxy, wherein the communication agent forwards the subnet metadevice information to the control plane, and the control plane stores the subnet metadevice information.
  • a device for hierarchical management of multiple subnets includes:
  • the receiving module is configured in each subnet, and is configured to receive the dedicated subnet configuration data sent by the network management system, and send the received configuration data of the specific subnet element to the corresponding service board. And each of the subnet elements respectively generates subnet meta service information according to the specific subnet element configuration data;
  • the configuration module is configured in the top logical unit and configured to receive subnet meta device information sent by the network management device;
  • control and scheduling module configured in the top-level logic unit, configured to receive the sub-network meta-service information sent by each sub-network element, and generate, according to the received sub-sub-element device information and the sub-network element service information And a control and scheduling command for controlling and scheduling each subnet element, so that each subnet element controls and schedules a respective service board according to the control and scheduling commands.
  • each sub-network element includes a main control board and a plurality of the service boards, where the main control board is configured to receive the dedicated sub-network element configuration data sent by the network management system and the control and scheduling sent by the top-level logic unit. Command and send subnet meta device information to the top logical unit.
  • the top level logic unit is disposed in a main control board of any one of the plurality of subnet elements.
  • the top level logic unit includes a control plane and a top level proxy
  • the top-level proxy is configured to receive the sub-network element device information sent by the network management device, and send the sub-substrate device information to the control plane, so that the control plane saves the sub-substrate device information.
  • the top level logic unit further includes a communication agent
  • the receiving module is configured to: when receiving the subnet metadevice information sent by the network management, the main control board of the subnet element sends the subnet metadevice information to a communication agent of the top level logical unit, so that the communication The proxy forwards the subnet metadevice information to the control plane, so that the control plane stores the subnet metadevice information.
  • the computer readable storage medium stores computer executable instructions for performing the method described in any one of the above.
  • An electronic device provided by this embodiment includes at least one processor
  • a memory communicatively coupled to the at least one processor
  • the memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to perform the method of any of the above.
  • the solution provided by the embodiment solves the limitation of the sub-rack expansion by the constraint conditions of the main control board memory, the processor data processing level and the communication control bandwidth in the related technology, and realizes hierarchical management of the service and improves compatibility.
  • FIG. 1 is a flowchart of a method for hierarchical management of multiple subnets according to the embodiment
  • FIG. 2 is a schematic diagram of a device for hierarchical management of multiple subnets according to this embodiment
  • FIG. 3 is a diagram of a multi-subrack hierarchical management system provided by this embodiment.
  • FIG. 4 is a structural diagram of a multi-subrack network element provided in this embodiment.
  • FIG. 5 is a top-level logic software deployment diagram provided by this embodiment.
  • FIG. 7 is a flow chart of a top-level logical transceiver package provided by this embodiment.
  • FIG. 9 is a flowchart of Embodiment 1 of multi-subnet element hierarchical management provided by this embodiment.
  • Embodiment 10 is a flowchart of Embodiment 2 of multi-subnet element hierarchical management provided by this embodiment;
  • Embodiment 11 is a flowchart of Embodiment 3 of multi-subnet element hierarchical management provided by this embodiment;
  • FIG. 12 is a structural block diagram of a multi-subnet element hierarchical management device provided by this embodiment.
  • FIG. 1 is a flowchart of a method for hierarchical management of multiple sub-subnets according to the embodiment. As shown in FIG. 1, the method includes: S110-S140.
  • each subnet element of the plurality of subnet elements respectively receives the dedicated subnet element configuration data sent by the network management device, and delivers the received specific subnet element configuration data to the respective service boards.
  • the subnet element generates subnet meta service information according to the specific subnet element configuration data.
  • the dedicated subnet element configuration data may be configuration data corresponding to each of the plurality of service boards of each subnet element.
  • the top level logic unit receives the subnet element device information sent by the network management.
  • the subnet element device information may be identification information including a subnet element, a type of multiple service boards in the subnet element, and a software and hardware version.
  • the top logic unit receives the subnet meta service information sent by each subnet element, and generates, according to the subnet element device information and the subnet meta service information, for controlling and scheduling each Control and scheduling commands for subnet elements.
  • each of the subnet elements controls and schedules respective service boards according to the control and scheduling commands.
  • the subnet element includes a main control board and a plurality of the service boards, and the main control board receives the dedicated subnet configuration data sent by the network management system and the control and scheduling commands sent by the top logic unit, and The subnet meta service information is sent to the top logical unit.
  • the top logic unit is disposed in a main control board of any one of the plurality of subnet elements.
  • the top level logic unit includes a control plane, a top layer proxy, and a communication proxy; the top layer proxy receives the subnet metadevice information sent by the network management, and sends the subnet metadevice information to the control plane, so as to control the plane saver. Describe the subnet meta device information.
  • the embodiment may further include: when the subnet element receives the subnet metadevice information sent by the network management, the main control board of the subnet element sends the subnet metadevice information to the top logical unit. And a communication agent, wherein the communication agent forwards the subnet element device information to the control plane, and the control plane stores the subnet element device information.
  • FIG. 2 is a schematic diagram of a multi-subnet element hierarchical management apparatus according to the embodiment.
  • the method includes: a receiving module 201, configured in each subnet element, configured to respectively receive a proprietary sent by the network management system.
  • the subnet element configures the data, and sends the received specific subnet element configuration data to the respective service boards, and each of the subnet elements respectively generates data according to the specific subnet element configuration data.
  • the network element service information the configuration module 202, configured in the top-level logic unit, configured to receive the sub-network element device information sent by the network management, and the control and scheduling module 203, configured in the top-level logic unit, configured to receive the each sub-network element Sending subnet meta service information, and generating control and scheduling commands for controlling and scheduling each subnet element according to the received subnet metadevice information and the subnet meta service information, so that each The subnet elements control and schedule respective service boards according to the control and scheduling commands.
  • the subnet element includes a main control board and a plurality of the service boards, and the main control board receives the dedicated subnet configuration data sent by the network management system and the control and scheduling commands sent by the top logic unit, and Subnet meta device information is sent to the top logical unit.
  • the top logic unit is disposed in a main control board of any one of the plurality of subnet elements.
  • the top-level logic unit includes a control plane, a top-level proxy, and a communication proxy; the top-level proxy is configured to receive sub-network meta-device information sent by the network management, and send the sub-sub-device information to the control plane, so that the control plane The subnet meta device information is saved.
  • the receiving module 201 is configured to: when receiving the subnet metadevice information sent by the network management, the main control board of the subnet element sends the subnet metadevice information to a communication agent of the top logical unit, so that The communication agent forwards the subnet element device information to the control plane, so that the control plane stores the subnet element device information.
  • the multi-subrack hierarchical management system includes a plurality of sub-shelf network elements, a top-level logic, a control plane, and a network management.
  • the sub-shelf network elements in this embodiment and other embodiments all refer to sub-network elements.
  • the subracks are managed hierarchically.
  • the multiple subracks that need to be managed are planned to be multiple independent subracks according to the types of bearer services. These subracks are used as subnets.
  • Conduct independent management The single subrack mentioned here does not refer to only one subrack, but refers to a subrack group. There is only one packet switching subrack in this subrack group. In addition, there may be other subracks, such as a transmission subrack and a pure OTN crossover. Subracks, etc.
  • To implement independent management of subnet elements run the main control board on the primary subrack of the subnet element.
  • the subnet element is the same as the subrack management mode of the original single network element, that is, the subnet element and the network management are separately constructed.
  • the chain refers to the establishment of a communication link for data interaction, and the sub-rack and the card in the network element are managed by the main control board.
  • the board in this embodiment refers to the service board.
  • these subnet elements together form a unified large network element.
  • the large network element is a subnet tuple, which can also be called a total network element.
  • the resources of the entire large network element can be uniformly managed and scheduled, as shown in Figure 4. Show. That is to say, the concept of subnet element is introduced.
  • the large network element is expanded from the original single network element to be composed of subnet element 1, subnet element 2, ... and subnet element n.
  • Different services require independent management of the network management to implement hierarchical management of subracks. It also supports unified scheduling of the WASON control plane to implement the WASON function of the device.
  • the top-level proxy mainly serves the WASON (WDM/OTN Automatically Switched Optical Network) control plane.
  • the WASON control plane needs unified control and scheduling of resources of the entire large network element.
  • the top-level logical agent is responsible for summarizing the device information (capability information, configuration information, and running information) of the relevant sub-network element to the WASON control plane, and receiving the control and scheduling commands sent from the control plane to be sent to the corresponding hardware device for execution. That is to say, in order to realize the unified scheduling of the entire large network element by the WASON control plane, the design of the top-level logical agent is introduced.
  • the top-level logical agent mainly serves the WASON service, and reports the device information of the entire network element and the OTN service configuration information to the WASON control plane through the configuration of the network management (that is, the information of all the sub-sub-devices) and the active reporting of the sub-network.
  • the control and scheduling commands of the WASON control plane are sent to the corresponding subnet.
  • the control plane (that is, the WASON control plane) is responsible for the entire large network element. Control and scheduling with call control and connection control.
  • Network management Provides a human-machine interface to configure and manage each subnet element (including the top-level logical unit).
  • the network management virtualizes a subnet mapping module corresponding to each subnet element and a top level logical unit mapping module, and the top logical unit mapping module manages the top logical unit.
  • the top level logic unit includes the WASON control plane and top level agent described above.
  • the top-level logical unit runs on the main control board of the main sub-frame of a specific sub-network element, and the sub-substrate is a host sub-subst.
  • the logical router is isolated from the sub-master control software. It is an independent software logic entity. As shown in Figure 5, the top-level logic unit operates as LR1, and the main control software runs as LR0.
  • the network management system sends the configuration data required by the WASON control plane to the top-level logical agent.
  • the network management virtualizes a top-level logical unit mapping module to map the top-level logical unit to operate on the top-level logical unit, and configures it through the management IP of the top-level logical unit.
  • the communication between the network management system and LR1 needs to be relayed through LR0.
  • the receiving thread in LR0 recognizes that the message with the destination IP address LR1 is sent to the CommCenter (second communication agent) of LR1 through the CommAgent (first communication agent). ),As shown in Figure 6.
  • Each subnet actively synchronizes the data related to the WASON service to the top proxy, and the WASON control plane (referred to as the control plane in FIG. 7) generates control and scheduling commands according to the data.
  • the communication between the top-level proxy and each sub-subnet is implemented by the TCP protocol.
  • the IP of the destination sub-net is specified, and the CommCenter (second communication proxy) is based on the IP of the destination sub-network.
  • the corresponding destination subnet element CommAgent (first communication agent) establishes a TCP connection, and then sends the message to the destination address.
  • the process of sending and receiving packets of the top-level agent is shown in Figure 7.
  • the top-level proxy sends the control and scheduling commands of the WASON control plane to the corresponding destination subnet.
  • the network management agent of the sub-board is sent to the corresponding service board for processing.
  • the main control board determines if the configuration related to the WASON service is through the communication agent. Synchronize to the top-level proxy for use by the WASON control plane.
  • the subnet meta-device information of the top-level logical unit of the network management is directly sent to the top-level proxy for processing, and the top-level proxy notifies the WASON control plane of the message.
  • the configuration commands (that is, the control and scheduling commands) sent by the WASON control plane are delivered to the NE proxy module of each subrack main control board through the communication agent, and finally delivered to each service board for processing.
  • sub-rack network elements that is, subnet elements
  • Embodiment 1 The network management configures the subnet element by directly establishing a chain with the subnet element:
  • the NMS is connected to each subnet by the management IP address, and the configuration command is sent to each subnet by direct communication.
  • Embodiment 2 The network management device configures the subnet element through a GNE (Gateway Network Element):
  • a specific subnet element is configured as a GNE, and the network management system and the GNE are chained, and the GNE is directly connected to each subnet element as a gateway.
  • the NMS sends a command to each subnet to GNE, it forwards the IP address to the destination subnet through the GNE route.
  • Embodiment 3 The network management system configures the subnet element by using an EGNE (Gateway Enhanced Network Element):
  • a specific subnet element is configured as an EGNE, the network management system and the EGNE are chained, and the EGNE is respectively connected with other subnet elements, and the network management communicates with the subnet element through the forwarding of the EGNE.
  • the EGNE After receiving the packet sent by the NMS, the EGNE identifies the destination IP address as the subnet IP and creates a sending thread to forward the command to the subnet.
  • the subrack in the related art includes a primary subrack and a plurality of secondary subracks, and one primary subrack manages multiple secondary subracks.
  • the slave subracks are grouped to form a plurality of slave subrack groups, and a plurality of main subracks are added to manage the slave subrack groups, so that the subracks are hierarchically managed, and the main control board memory is solved.
  • the embodiment further provides a computer readable storage medium storing computer executable instructions for performing the multi-subnet element hierarchical management method described in the foregoing embodiments.
  • FIG. 12 is a structural block diagram of a multi-subnet element hierarchical management device according to an embodiment of the present invention.
  • the management device provided in this embodiment may include a processor 1201 and a memory 1203, and may further include a communication interface 1202 and a bus 1204.
  • the processor 1201, the communication interface 1202, and the memory 1203 can complete communication with each other through the bus 1204. Communication interface 1202 can be used for information transmission.
  • the processor 1201 can call the logic instructions in the memory 1203 to perform the multi-subnet element hierarchical management method of the above embodiment.
  • the logic instructions in the memory 1203 described above may be implemented in the form of a software functional unit and sold or used as a stand-alone product, and may be stored in a computer readable storage medium.
  • the technical solution of the present disclosure may be embodied in the form of a software product stored in a storage medium, including one or more instructions for causing a computer device (which may be a personal computer, a server) , or a network device, etc.) performs all or part of the steps of the methods described in various embodiments of the present disclosure.
  • the foregoing storage medium may be a non-transitory storage medium, including: a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM, Random Access Memoty), a magnetic disk, or an optical disk.
  • a medium that can store program code, or a transitory storage medium including: a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM, Random Access Memoty), a magnetic disk, or an optical disk.
  • the solution provided by the embodiment solves the limitation of the sub-rack expansion by the constraint conditions of the main control board memory, the processor data processing level and the communication control bandwidth in the related technology, and realizes hierarchical management of the service and improves compatibility.

Landscapes

  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

一种多子网元分层管理的方法及装置，涉及子架管理技术领域，包括：多个子网元中的每个子网元分别接收网管发送的专有子网元配置数据，并将所收到的所述专有子网元配置数据下发到各自的相应业务板，以及所述每个子网元分别根据所述专有子网元配置数据生成子网元业务信息；顶层逻辑单元接收网管发送的子网元设备信息；以及顶层逻辑单元接收所述每个子网元发送的所述子网元业务信息，并根据所述子网元设备信息以及所述子网元业务信息生成用于控制和调度所述每个子网元的控制和调度命令，以便所述每个子网元根据所述控制和调度命令对各自的相应业务板进行控制和调度。

Description

多子网元分层管理的方法及装置 技术领域
本公开涉及子架管理技术领域，例如涉及一种多子网元分层管理的方法及装置。
背景技术
相关技术中的子架管理方法主要基于单网元扁平化的管理技术，即被管理子架都包含在一个单网元内，所述子架包括主子架和从子架，所述主子架承载有主控板的装置，所述从子架承载有业务板的装置。主子架与从子架通过监控板相互级联、通信。整个网元在主子架上运行一块主控板，该主控板作为网元对外的接口，该主控板控制和管理网元内所有的子架和板卡，所述板卡即业务板。
随着WDM(Wavelength Division Multiplexing，波分复用)/OTN(Optical Transport Network，光传送网)产品的演进，对子架多样性和扩展性的需求越来越高，相关技术中这种子架管理方式存在着一些不足，如下所述：
1、主控板需要具有管理几千甚至上万块的板卡的处理能力，这是现阶段的处理器的数据处理能力和主控板空间所不能支持的；
2、网元内部子架的通信和连接，以及通信开销都可能限制子架的扩展；
3、网元内部子架的兼容能力差，新业务扩容和升级都可能影响已有业务。
发明内容
本实施例提供的方案解决了相关技术中子架管理方法无法达到对子架多样性和扩展性的需求的问题。
一种多子网元分层管理的方法，包括：
多个子网元中的每个子网元分别接收网管发送的专有子网元配置数据，并将所收到的所述专有子网元配置数据下发到各自的相应业务板，以及所述每个子网元分别根据所述专有子网元配置数据生成子网元业务信息；
顶层逻辑单元接收网管发送的子网元设备信息；
顶层逻辑单元接收所述每个子网元发送的所述子网元业务信息，并根据所述子网元设备信息以及所述子网元业务信息生成用于控制和调度所述每个子网元的控制和调度命令，以便所述每个子网元根据所述控制和调度命令对各自的相应业务板进行控制和调度。
可选的，所述每个子网元包含一个主控板和多个所述业务板，所述主控板接收网管发送的专有子网元配置数据和顶层逻辑单元发送的控制和调度命令，并将子网元业务信息发送给顶层逻辑单元。
可选的，所述顶层逻辑单元设置在所述多个子网元中的任意一个的主控板中。
可选的，所述顶层逻辑单元包括控制平面和顶层代理；
所述方法还包括：所述顶层代理接收网管发送的子网元设备信息，并将所述子网元设备信息发送到控制平面，以便控制平面保存所述子网元设备信息。
可选的，所述顶层逻辑单元还包括通信代理；
所述方法还包括：当所述子网元接收到网管发送的子网元设备信息时，所述子网元的主控板将所述子网元设备信息发送到所述顶层逻辑单元的通信代理，以便所述通信代理将所述子网元设备信息转发到所述控制平面，所述控制平面存储所述子网元设备信息。
一种多子网元分层管理的装置，包括：
接收模块，配置在每个子网元中，设置为分别接收网管发送的专有子网元配置数据，并将所收到的所述专有子网元配置数据下发到各自的相应业务板，以及所述每个子网元分别根据所述专有子网元配置数据生成子网元业务信息；
配置模块，配置在顶层逻辑单元中，设置为接收网管发送的子网元设备信息；以及
控制和调度模块，配置在顶层逻辑单元中，设置为接收所述每个子网元发送的子网元业务信息，并根据收到的所述子网元设备信息以及所述子网元业务信息生成用于控制和调度所述每个子网元的控制和调度命令，以便所述每个子网元根据所述控制和调度命令对各自的相应业务板进行控制和调度。
可选的，所述每个子网元包含一个主控板和多个所述业务板，所述主控板设置为接收网管发送的专有子网元配置数据和顶层逻辑单元发送的控制和调度命令，并将子网元设备信息发送给顶层逻辑单元。
可选的，所述顶层逻辑单元被设置在所述多个子网元中的任意一个的主控板中。
可选的，所述顶层逻辑单元包括控制平面和顶层代理；
所述顶层代理设置为接收网管发送的子网元设备信息，并将所述子网元设备信息发送到控制平面，以便控制平面保存所述子网元设备信息。
可选的，所述顶层逻辑单元还包括通信代理；
所述接收模块是设置为当接收到网管发送的子网元设备信息时，所述子网元的主控板将所述子网元设备信息发送到顶层逻辑单元的通信代理，以便所述通信代理将所述子网元设备信息转发到所述控制平面，使所述控制平面存储所述子网元设备信息。
本实施例提供的一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令用于执行上述任一项所述的方法。
本实施例提供的一种电子设备，包括至少一个处理器；以及
与所述至少一个处理器通信连接的存储器；
其中，所述存储器存储有可被所述至少一个处理器执行的指令，所述指令被所述至少一个处理器执行，执行如上述任一项所述的方法。
本实施例提供的方案，解决了主控板内存、相关技术中处理器数据处理水平和通信控制带宽等约束条件对子架扩展的限制，并实现对业务的分层管理，提高兼容能力。
附图概述
图1是本实施例提供的一种多子网元分层管理的方法流程图；
图2是本实施例提供的一种多子网元分层管理的装置示意图；
图3是本实施例提供的多子架分层管理系统图；
图4是本实施例提供的多子架网元结构图；
图5是本实施例提供的顶层逻辑软件部署图；
图6是本实施例提供的顶层逻辑与网管通信流程图；
图7是本实施例提供的顶层逻辑收发包流程图；
图8是本实施例提供的设备业务管理框图；
图9是本实施例提供的多子网元分层管理的实施例一流程图；
图10是本实施例提供的多子网元分层管理的实施例二流程图；
图11是本实施例提供的多子网元分层管理的实施例三流程图；
图12是本实施例提供的多子网元分层管理设备的结构框图。
具体实施方式
以下结合附图对本公开的实施例进行详细说明，应当理解，以下所说明的优选实施例仅用于说明和解释本公开。在不冲突的情况下，以下实施例和实施例中的特征可以相互组合。
图1是本实施例提供的一种多子网元分层管理的方法流程图，如图1所示，包括：S110-S140。
其中，在S110中，多个子网元中的每个子网元分别接收网管发送的专有子网元配置数据，并将所收到的专有子网元配置数据下发到各自的相应业务板，所述每个子网元分别根据所述专有子网元配置数据生成子网元业务信息。
所述专有子网元配置数据可以是包括每个子网元的多个业务板中的每个业务板对应的配置数据。
在S120中，顶层逻辑单元接收网管发送的子网元设备信息。所述子网元设备信息可以是包括子网元的标识信息，以及子网元中多个业务板的类型以及软硬件版本等。
在S130中，顶层逻辑单元接收所述每个子网元发送的所述子网元业务信息，并根据所述子网元设备信息以及所述子网元业务信息生成用于控制和调度所述每个子网元的控制和调度命令。
在S140中，所述每个子网元根据所述控制和调度命令对各自的相应业务板进行控制和调度。
其中，所述每个子网元包含一个主控板和多个所述业务板，所述主控板接收网管发送的专有子网元配置数据和顶层逻辑单元发送的控制和调度命令，并将子网元业务信息发送给顶层逻辑单元。
其中，所述顶层逻辑单元被设置在所述多个子网元中的任意一个的主控板中。
其中，所述顶层逻辑单元包括控制平面、顶层代理以及通信代理；所述顶层代理接收网管发送的子网元设备信息，并将所述子网元设备信息发送到控制平面，以便控制平面保存所述子网元设备信息。
本实施例还可以是包括：当所述子网元接收到网管发送的子网元设备信息时，所述子网元的主控板将所述子网元设备信息发送到所述顶层逻辑单元的通信代理，以便所述通信代理将所述子网元设备信息转发到所述控制平面，所述控制平面存储所述子网元设备信息。
图2是本实施例提供的一种多子网元分层管理的装置示意图，如图2所示，包括：接收模块201，配置在每个子网元中，设置为分别接收网管发送的专有子网元配置数据，并将所收到的所述专有子网元配置数据下发到各自的相应业务板，以及所述每个子网元分别根据所述专有子网元配置数据生成子网元业务信息；配置模块202，配置在顶层逻辑单元中，设置为接收网管发送的子网元设备信息；控制和调度模块203，配置在顶层逻辑单元中，设置为接收所述每个子网元发送的子网元业务信息，并根据收到的所述子网元设备信息以及所述子网元业务信息生成用于控制和调度所述每个子网元的控制和调度命令，以便所述每个子网元根据所述控制和调度命令对各自的相应业务板进行控制和调度。
其中，所述每个子网元包含一个主控板和多个所述业务板，所述主控板接收网管发送的专有子网元配置数据和顶层逻辑单元发送的控制和调度命令，并将子网元设备信息发送给顶层逻辑单元。
其中，所述顶层逻辑单元被设置在所述多个子网元中的任意一个的主控板中。
其中，所述顶层逻辑单元包括控制平面、顶层代理以及通信代理；所述顶层代理设置为接收网管发送的子网元设备信息，并将所述子网元设备信息发送到控制平面，以便控制平面保存所述子网元设备信息。
其中，所述接收模块201是设置为当接收到网管发送的子网元设备信息时，所述子网元的主控板将所述子网元设备信息发送到顶层逻辑单元的通信代理，以便所述通信代理将所述子网元设备信息转发到所述控制平面，使所述控制平面存储所述子网元设备信息。
下面结合图3至图11对本实施例的技术内容进行说明：
如图3所示，多子架分层管理系统包括多个子架子网元、顶层逻辑、控制平面和网管。本实施例以及其他实施例中的子架子网元都是指子网元。
多个子网元：这里对子架进行分层管理，即将需要管理的多子架，按其承载业务种类的不同，规划为多个可相互独立的单子架，将这些单子架作为一个个子网元进行独立管理。这里所说的单子架，并非单指一个子架，而是指一个子架组，这个子架组中分组交换子架只有一个，此外还可有其他子架，例如传输子架、纯OTN交叉子架等。为实现子网元的独立管理，在子网元的主子架上运行主控板，子网元与原先单网元的子架管理模式相同，即子网元与网管分别建链，所述建链是指建立通信链接，以进行数据交互，通过主控板管理网元内的子架与板卡，本实施例中所述板卡是指业务板。同时，这些子网元又共同构成一个统一的大网元，该大网元为子网元组，也可以称为总网元，整个大网元的资源可统一管理、调度，如图4所示。也就是说，引入子网元的概念，大网元由原先的单一网元，扩展为由子网元1、子网元2、...以及子网元n共同组成，这些子网元承载着不同的业务，要求既可通过网管独立管理，实现子架的分层管理；也可支持WASON控制平面的统一调度，实现设备的WASON功能。
顶层代理主要服务于WASON(WDM/OTN Automatically Switched Optical Network，基于WDM/OTN的自动交换光网络)控制平面。WASON控制平面需要对整个大网元的资源进行统一的控制和调度。顶层逻辑代理负责汇总相关子网元的设备信息(能力信息、配置信息以及运行信息)报告给WASON控制平面，并接收从控制平面下发的控制和调度命令发送给相应的硬件设备执行。也就是说，为实现WASON控制平面对整个大网元的统一调度，引入顶层逻辑代理的设计。顶层逻辑代理主要服务于WASON业务，通过网管下发配置(即下发所有子网元设备信息)和子网元主动上报的方式汇总全网元的设备信息和OTN业务配置信息报告给WASON控制平面，并接收WASON控制平面的控制和调度命令下发给相应子网元。控制平面(即WASON控制平面)负责对整个大网元 进行控制和调度，具有呼叫控制和连接控制功能。
网管：提供人机交互界面，对每个子网元(含顶层逻辑单元)进行配置和管理。其中，网管虚拟出对应每个子网元的子网元映射模块以及一个顶层逻辑单元映射模块，顶层逻辑单元映射模块对顶层逻辑单元进行管理。所述顶层逻辑单元包括上述WASON控制平面和顶层代理。
以下为顶层逻辑单元的对子网元进行管理的具体方法：
(1)、顶层逻辑单元运行在一特定的子网元的主子架的主控板上，该子网元为宿主子网元。采用逻辑路由器的方法与子架主控软件进行隔离，是一个独立的软件逻辑实体，如图5所示，顶层逻辑单元作为LR1运行，主控软件作为LR0运行。
(2)、宿主子网元上电时，判断顶层逻辑单元是否存在，若存在，则运行顶层逻辑。
(3)、网管向顶层逻辑代理下发WASON控制平面需要的配置数据。网管虚拟出一个顶层逻辑单元映射模块以映射顶层逻辑单元从而对顶层逻辑单元进行操作，通过顶层逻辑单元的管理IP对其进行配置。网管与LR1的通信需要通过LR0中转，LR0中的收包线程收到报文后，识别到目的IP为LR1的报文则通过CommAgent(第一通信代理)发送给LR1的CommCenter(第二通信代理)，如图6所示。
(4)、每个子网元主动向顶层代理同步与WASON业务相关的数据，WASON控制平面(图7中简称控制平面)根据该数据生成控制和调度命令。顶层代理与每个子网元的通信通过TCP协议实现，每个子网元向顶层代理发送报文时，指定目的子网元的IP，CommCenter(第二通信代理)根据目的子网元的IP，与相应目的子网元CommAgent(第一通信代理)建立TCP连接，之后将报文发送到目的地址。顶层代理的收发包流程如图7所示。
(5)、顶层代理将WASON控制平面的控制和调度命令下发给相应的目的子网元。
以下是整个大网元的消息协作流程，如图8所示：
1)、网管对子架子网元的配置，通过主控板的网元代理后，下发到相应业务板进行处理。主控板判断若是与WASON业务相关的配置，通过通信代理， 同步给顶层代理，以便WASON控制平面使用。
2)、网管对顶层逻辑单元的子网元设备信息，直接下发给顶层代理处理，顶层代理将消息通知给WASON控制平面。
3)、WASON控制平面下发的配置命令(即控制和调度命令)，通过通信代理下发到每个子架主控板的网元代理模块，最终下发到每个业务板进行处理。
下面是三个网管对子架子网元(即子网元)进行配置的具体实施例：
实施例1：网管通过与子网元直接建链对子网元进行配置：
如图9所示，网管通过管理IP与每个子网元分别建链，通过直接通信的方式将配置命令下发给每个子网元。
实施例2：网管通过GNE(Gateway Network Element，网关网元)对子网元进行配置：
如图10所示，将一特定的子网元配置为GNE，网管与GNE建链，并将GNE作为网关与每子网元直接建链。网管下发给每子网元的命令到达GNE后，通过GNE路由转发至目的子网元的IP地址。
实施例3：网管通过EGNE(Gateway Enhanced Network Element，增强型网关网元)对子网元进行配置：
如图11所示，将一特定的子网元配置为EGNE，网管与EGNE进行建链，EGNE分别与其他子网元建链，网管通过EGNE的转发与子网元通信。EGNE收到网管下发的报文后，识别目的IP为子网元IP，创建发送线程将命令转发至子网元。
根据本实施例提供的方案，提出了去中心化的思想，相关技术中的子架是包括一个主子架和多个从子架，由一个主子架对多个从子架进行管理，本实施例对所述从子架进行了分组形成多个从子架组，增设多个主子架分别对所述从子架组进行管理，如此对所述子架进行分层管理，解决了主控板内存、相关技术中处理器数据处理水平和通信控制带宽等约束条件对子架扩展的限制；通过扩展子网元的方式，扩容子架和新增业务，例如PTN(分组传送网，Packet Transport Network)、OTN等业务子架可作为不同子网元同时管理，互不影响，提高了设备的兼容性；降低了一特定的子架主控板故障后对整个网元的管理风 险，提升了整个网络的运行品质。
本实施例还提供了一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令用于执行上述实施例所述的多子网元分层管理的方法。
图12为本实施例提供的多子网元分层管理设备的结构框图。本实施例提供的管理设备可以是包括：处理器(processor)1201和存储器(memoty)1203，还可以包括通信接口(Communications Interface)1202以及总线1204。
其中，处理器1201、通信接口1202、存储器1203可以通过总线1204完成相互间的通信。通信接口1202可以用于信息传输。处理器1201可以调用存储器1203中的逻辑指令，以执行上述实施例的多子网元分层管理的方法。
此外，上述的存储器1203中的逻辑指令可以通过软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本公开的技术方案可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括一个或多个指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本公开各个实施例所述方法的全部或部分步骤。而前述的存储介质可以是非暂态存储介质，包括：U盘、移动硬盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memoty)、磁碟或者光盘等各种可以存储程序代码的介质，也可以是暂态存储介质。
工业实用性
本实施例提供的方案，解决了主控板内存、相关技术中处理器数据处理水平和通信控制带宽等约束条件对子架扩展的限制，并实现对业务的分层管理，提高兼容能力。

Claims (11)

  1. 一种多子网元分层管理的方法，包括：
    多个子网元中的每个子网元分别接收网管发送的专有子网元配置数据，并将所收到的所述专有子网元配置数据下发到各自的相应业务板，以及所述每个子网元分别根据所述专有子网元配置数据生成子网元业务信息；
    顶层逻辑单元接收网管发送的子网元设备信息；
    顶层逻辑单元接收所述每个子网元发送的所述子网元业务信息，并根据所述子网元设备信息以及所述子网元业务信息生成用于控制和调度所述每个子网元的控制和调度命令，以便所述每个子网元根据所述控制和调度命令对各自的相应业务板进行控制和调度。
  2. 根据权利要求1所述的方法，其中，所述每个子网元包含一个主控板和多个所述业务板，所述主控板接收网管发送的专有子网元配置数据和顶层逻辑单元发送的控制和调度命令，并将子网元业务信息发送给顶层逻辑单元。
  3. 根据权利要求2所述的方法，其中，所述顶层逻辑单元设置在所述多个子网元中的任意一个的主控板中。
  4. 根据权利要求3所述的方法，其中，所述顶层逻辑单元包括控制平面和顶层代理；
    所述方法还包括：所述顶层代理接收网管发送的子网元设备信息，并将所述子网元设备信息发送到控制平面，以便控制平面保存所述子网元设备信息。
  5. 根据权利要求4所述的方法，其中，所述顶层逻辑单元还包括通信代理；
    所述方法还包括：当所述子网元接收到网管发送的子网元设备信息时，所述子网元的主控板将所述子网元设备信息发送到所述顶层逻辑单元的通信代理，以便所述通信代理将所述子网元设备信息转发到所述控制平面，所述控制平面存储所述子网元设备信息。
  6. 一种多子网元分层管理的装置，包括：
    接收模块，配置在每个子网元中，设置为分别接收网管发送的专有子网元配置数据，并将所收到的所述专有子网元配置数据下发到各自的相应业务板，以及所述每个子网元分别根据所述专有子网元配置数据生成子网元业务信息；
    配置模块，配置在顶层逻辑单元中，设置为接收网管发送的子网元设备信息；以及
    控制和调度模块，配置在顶层逻辑单元中，设置为接收所述每个子网元发送的子网元业务信息，并根据收到的所述子网元设备信息以及所述子网元业务信息生成用于控制和调度所述每个子网元的控制和调度命令，以便所述每个子网元根据所述控制和调度命令对各自的相应业务板进行控制和调度。
  7. 根据权利要求6所述的装置，其中，所述每个子网元包含一个主控板和多个所述业务板，所述主控板设置为接收网管发送的专有子网元配置数据和顶层逻辑单元发送的控制和调度命令，并将子网元设备信息发送给顶层逻辑单元。
  8. 根据权利要求7所述的装置，其中，所述顶层逻辑单元被设置在所述多个子网元中的任意一个的主控板中。
  9. 根据权利要求8所述的装置，其中，所述顶层逻辑单元包括控制平面和顶层代理；
    所述顶层代理设置为接收网管发送的子网元设备信息，并将所述子网元设备信息发送到控制平面，以便控制平面保存所述子网元设备信息。
  10. 根据权利要求9所述的装置，其中，所述顶层逻辑单元还包括通信代理；
    所述接收模块是设置为当接收到网管发送的子网元设备信息时，所述子网元的主控板将所述子网元设备信息发送到顶层逻辑单元的通信代理，以便所述通信代理将所述子网元设备信息转发到所述控制平面，使所述控制平面存储所述子网元设备信息。
  11. 一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令用于执行权利要求1-5任一项所述的方法。
PCT/CN2017/090405 2016-06-27 2017-06-27 多子网元分层管理的方法及装置 WO2018001253A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610481511.9A CN107547220A (zh) 2016-06-27 2016-06-27 一种多子网元分层管理的方法及装置
CN201610481511.9 2016-06-27

Publications (1)

Publication Number Publication Date
WO2018001253A1 true WO2018001253A1 (zh) 2018-01-04

Family

ID=60786514

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/090405 WO2018001253A1 (zh) 2016-06-27 2017-06-27 多子网元分层管理的方法及装置

Country Status (2)

Country Link
CN (1) CN107547220A (zh)
WO (1) WO2018001253A1 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111917621B (zh) * 2019-05-10 2021-09-07 烽火通信科技股份有限公司 通信设备的网管服务器与网元的通信方法及系统
CN114727167A (zh) * 2020-12-18 2022-07-08 中兴通讯股份有限公司 基于虚拟网元的业务配置方法、系统、虚拟网元及设备
CN114401179B (zh) * 2022-01-11 2023-09-05 中国联合网络通信集团有限公司 一种网元管理方法、装置、设备及存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1642135A (zh) * 2004-01-17 2005-07-20 华为技术有限公司 一种ggsn/pdsn设备及其数据转发的方法
CN101309170A (zh) * 2008-06-05 2008-11-19 中兴通讯股份有限公司 主子架扩展方法、数据传输方法及扩展子架
CN101500249A (zh) * 2008-02-02 2009-08-05 中兴通讯股份有限公司 一种单板状态检测的实现方法
CN101616024A (zh) * 2009-07-16 2009-12-30 中兴通讯股份有限公司 一种业务开通/阻断的方法和系统

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101202662A (zh) * 2003-04-30 2008-06-18 华为技术有限公司 满足海量终端设备网络管理需求的系统及方法
CN100349408C (zh) * 2004-02-12 2007-11-14 华为技术有限公司 实现网管系统和网元设备配置数据实时同步的方法
CN1815974A (zh) * 2005-02-06 2006-08-09 华为技术有限公司 备份和恢复网元配置数据的方法及其系统
CN101610173B (zh) * 2009-07-14 2012-09-05 中兴通讯股份有限公司 一种对多网元进行数据配置的方法和网管服务器
CN101959089B (zh) * 2009-07-17 2013-06-12 中兴通讯股份有限公司 一种集中管理网元数据的方法及网元设备
CN102752148B (zh) * 2012-07-18 2015-04-29 烽火通信科技股份有限公司 基于网元适配子系统的管理系统及方法
CN103929327B (zh) * 2014-03-18 2017-08-01 烽火通信科技股份有限公司 一种网管对混合组网业务的反算方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1642135A (zh) * 2004-01-17 2005-07-20 华为技术有限公司 一种ggsn/pdsn设备及其数据转发的方法
CN101500249A (zh) * 2008-02-02 2009-08-05 中兴通讯股份有限公司 一种单板状态检测的实现方法
CN101309170A (zh) * 2008-06-05 2008-11-19 中兴通讯股份有限公司 主子架扩展方法、数据传输方法及扩展子架
CN101616024A (zh) * 2009-07-16 2009-12-30 中兴通讯股份有限公司 一种业务开通/阻断的方法和系统

Also Published As

Publication number Publication date
CN107547220A (zh) 2018-01-05

Similar Documents

Publication Publication Date Title
EP3096490B1 (en) Method for realizing network virtualization and related device and communication system
CN102469021B (zh) 一种智能弹性框架系统中转发业务流量的方法和成员设备
Muñoz et al. Transport network orchestration for end-to-end multilayer provisioning across heterogeneous SDN/OpenFlow and GMPLS/PCE control domains
CN108011732B (zh) 配置业务资源的方法、控制器及系统
US11528190B2 (en) Configuration data migration for distributed micro service-based network applications
WO2018188425A1 (zh) Vxlan单归和双归混合接入方法、装置、pe设备和存储介质
US10819659B2 (en) Direct replying actions in SDN switches
CN103209108B (zh) 一种基于dvpn的路由生成方法和设备
WO2018001253A1 (zh) 多子网元分层管理的方法及装置
CN111615812B (zh) 意欲在使用动态路由协议的网络中实现的配置方法
WO2017197983A1 (zh) 流量处理方法及系统、存储介质、交换机
CN101562576A (zh) 一种路由发布方法和设备
WO2014132298A1 (ja) ネットワークシステム及びリソース制御装置並びに仮想マシン生成装置
EP4236270A2 (en) Software defined access fabric without subnet restriction to a virtual network
US11128558B2 (en) Automatic routing configuration between hosts and network layer devices
CN103516601B (zh) 路由传输方法和装置及系统
US11095514B2 (en) System and method for propagating anima network objective changes
CN114979139A (zh) 边缘计算场景下异构虚拟网关的管理系统及方法
CN106712994B (zh) 软件定义网络管理方法及通信系统
CN113039752B (zh) 用于支持基于服务的架构的网络节点和方法
CN108023801B (zh) 异构网络的资源调度方法及系统
EP2890053B1 (en) Ds domain generating method and system
US9525615B2 (en) Systems and methods for implementing multiple ISIS routing instances on a network element
CN115134232B (zh) 一种虚拟路由器管理方法、设备、系统和存储介质
CN107769983B (zh) 一种基于扩展vSDN的网络功能共享方法及系统

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

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

Country of ref document: EP

Kind code of ref document: A1