WO2015139533A1 - 一种网管对混合组网业务的反算方法 - Google Patents

一种网管对混合组网业务的反算方法 Download PDF

Info

Publication number
WO2015139533A1
WO2015139533A1 PCT/CN2015/071914 CN2015071914W WO2015139533A1 WO 2015139533 A1 WO2015139533 A1 WO 2015139533A1 CN 2015071914 W CN2015071914 W CN 2015071914W WO 2015139533 A1 WO2015139533 A1 WO 2015139533A1
Authority
WO
WIPO (PCT)
Prior art keywords
network element
service
network
configuration
sequence
Prior art date
Application number
PCT/CN2015/071914
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 WO2015139533A1 publication Critical patent/WO2015139533A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements

Definitions

  • the present invention relates to a telecommunication network transmission management technology, and in particular, to a method for inverse calculation of a network management service of a hybrid network.
  • the network management system in addition to configuring services and downloading services to the telecommunication equipment, the network management system often needs to read the configured service data from the telecommunication equipment.
  • the management personnel In the engineering application, the management personnel often configure the service on the telecommunication device through the command line interface.
  • the network management system In order to maintain the consistency of the service data between the telecommunication device and the network management system, the network management system also needs to read the service data configured by the command line from the telecommunication device.
  • the network management device Since a service managed by the network management generally involves multiple telecommunication devices, and the service data is distributed to the telecommunication devices, the network management device needs to splicing the distributed service data on the plurality of telecommunication devices to form a complete service manageable by the network management device, thereby realizing The end-to-end back-calculation function of the business.
  • the present invention provides an inverse calculation method for a hybrid network service that can support a hybrid network of different types of devices.
  • An inverse calculation method for a hybrid network service of a network management system which is used to form service data of a hybrid network of different types of telecommunication devices into a complete service manageable by the network management system, and the inverse calculation method of the network management service for the hybrid network service includes the following step:
  • the network element reads the service data from the corresponding telecommunication device and converts it into a corresponding configuration block in the network element configuration
  • Each element of the service network element set is traversed and all configuration blocks corresponding to each service are found according to the service keyword and the network element sequence to be spliced into a complete service.
  • the network management method for the hybrid network service converts service data of different types of telecommunication devices into a unified format of network element configuration, and supports hybrid networking of multiple telecommunication devices.
  • the situation has strong scalability.
  • For new telecommunication equipment or new service types only the telecommunication equipment or new types of service data need to be converted into network element configuration, and other parts can support back calculation without modification.
  • with versatility supports the expansion of business types.
  • FIG. 1 is a flowchart of a method for back-calculating a hybrid network service provided by the network management system provided by the present invention.
  • FIG. 2 is a flow chart of obtaining a set of service network elements in FIG.
  • 3 is an internal structure diagram of a set of service network elements.
  • FIG. 1 is a method for calculating a hybrid network service of a network management system according to an embodiment of the present invention, which is used to form service data of a hybrid network of different types of telecommunication devices into a complete service manageable by the network management system.
  • the hybrid network includes a Packet Transport Network (PTN), an IP Radio Access Net (IPRAN), and an Optical Transport Network (OTN).
  • PTN Packet Transport Network
  • IPRAN IP Radio Access Net
  • OTN Optical Transport Network
  • the network element reads the service data from the corresponding telecommunication device and converts it into a corresponding configuration block in the network element configuration.
  • S200 Determine an initial network element set and plan an inverse calculation order of the configuration blocks in each network element configuration according to the service type.
  • S300 traverse each network element in the initial network element set and obtain a service network element set according to the network element configuration of each network element;
  • S400 Traverse each element of the service network element set and find all configuration blocks corresponding to each service according to the service keyword and the network element sequence to be spliced into a complete service.
  • the network element is in one-to-one correspondence with the telecommunication device.
  • the network element is a logical entity of the telecommunication device on the network management device.
  • the network element sends a command for reading the service data to the telecommunication device, and the telecommunication device reports the service data to the network element. Since different telecommunication devices support the same service, but the data format of the service is different on each telecommunication device, the service data reported by the telecommunication device needs to be converted into the network element configuration in the same format in the network element, thus shielding the telecommunication device.
  • the network element configuration is composed of configuration blocks of different service types, and the same type of service data is in the same configuration block.
  • the data containing the service on the network element, a complete service has a corresponding configuration block in the network element configuration on multiple network elements, and the configuration block is a binary data block, including the same type of service entry, and each service entry corresponds to A business on a telecommunications equipment.
  • the network element reads the service data from the corresponding telecommunication device and converts it into a network element configuration, and different types of service data are in different configuration blocks.
  • the configuration blocks of each service type and the support status of various telecommunication devices included in the NE configuration are shown in Table 1 below:
  • the service types supported by different telecommunication devices are different, and the NE configuration is divided into different configuration blocks according to the service type, and the number of configuration blocks is equal to the maximum number of service types.
  • the network element configuration in the same format can be adapted to different telecommunication devices.
  • the service data is converted into the network element configuration, only the configuration block supported by the telecommunication device is filled in the service data, and the configuration block that is not supported by the telecommunication device is set to Empty.
  • the service data of the newly added telecommunication equipment is also converted into the network element configuration. If the service type is newly added, the new service type data is also converted into the network element configuration.
  • step S200 the services in the configuration blocks are back-calculated in turn according to the order of the service types. After all the types of services are back-calculated, the inverse calculation of the next type of services is started.
  • the set of initial network elements is determined by the user of the network management system, and may include only one network element, or several network elements, or network elements of the entire network.
  • the network element configuration of each network element in the initial network element set is traversed, so that all services passing through the network elements are backcalculated, and only the network element is calculated based on the network element configuration of one network element. All services, and according to the needs of the network management user, may need to calculate the services of some network elements, or the services of the entire network, which can be achieved by adjusting the number of network elements in the initial network element set.
  • the service has a hierarchical relationship, for example, the VC must be carried on the tunnel, and the L2VPN must be carried on the VC. Therefore, you need to determine the order of the service type in the back calculation, as shown in Table 2 below.
  • the service keyword is a unique identifier of the service, and one service is dispersed into the network element configuration of multiple network elements, but the keywords are the same.
  • Each element in the set of service network elements includes a service keyword and a sequence of network elements, and the format is such as ⁇ service keyword, network element sequence>, and each service keyword uniquely corresponds to one network element sequence, and each network in the sequence The element is the network element through which the business keyword corresponds to the service.
  • step S300 acquiring a service network element set includes the following steps:
  • S310 Select a current network element from the initial network element set, and sort the configuration block in the network element configuration of the current network element.
  • S320 The service keyword in the configuration block is sequentially extracted from the network element configuration of the current network element, and the network element sequence corresponding to the service keyword is found, and the component element is added to the service network element set.
  • S340 The current network element is removed from the initial network element set and continues to traverse the network element to add the service keyword and the corresponding network element sequence component in each configuration block of each network element to the service network element set until the traversal is completed. All network elements.
  • step S310 the sorting rule is as shown in Table 2 above, and the sorting in the network element configuration is reversed in a certain order.
  • step S320 keywords are generated in a combined manner, and each field is separated by a separator. If a comma is used as a separator, the shape is like ⁇ service type, service id, sub-service id>, and the values of each field are as follows. 3 is shown.
  • a service keyword is a unique service. Although a service is distributed to the NE configuration of each NE, the service keywords are the same in these NE configurations. Different configuration blocks obtain different methods for the next network element, as shown in Table 4 below:
  • step S330 the order of traversing the configuration blocks is in the reverse order of the configuration blocks in Table 2.
  • the order in which the service keywords are traversed in the configuration block is irrelevant, generally in a natural order.
  • step S340 the network element configuration of each network element in the initial network element set is traversed in sequence, and all the services on the network element configuration are traversed, and each service is obtained.
  • the internal structure of this service network element set is shown in Figure 3.
  • each element in the network element set is a service sequence and a corresponding network element sequence.
  • the network element sequence is composed of all network elements in which the complete service is dispersed, and traverses each element in the service network element set for each element.
  • the element traverses the network element configuration of each network element according to the network element sequence corresponding to the service keyword, and finds the configuration block of the service in the configuration of the network element, and performs service splicing, because the service data of the complete service and the network element There is a difference in the structure, and the data mapping relationship between the service data of the network element and the complete service needs to be established.
  • the mapping relationship the network element set obtained in step S300 is traversed, and the service data of each network element is spliced into a complete service. .
  • Table 5 The mapping relationship of related data is shown in Table 5 below:
  • the network management provided by the present invention has different types of inverse calculation methods for hybrid networking services.
  • the service data of the telecommunication equipment is converted into a network element configuration in a unified format, which supports the hybrid networking of multiple telecommunication devices, and has strong scalability.
  • For newly added telecommunication devices or new service types only telecommunication equipment is required.
  • the newly added type of business data is converted into the network element configuration, and other parts can support the back calculation without modification, and have universality, and support the expansion of the service type.

Landscapes

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

Abstract

本发明提供一种网管对混合组网业务的反算方法，其用于将不同类型电信设备混合组网的业务数据形成网管可管理的完整业务，其包括以下步骤：网元从相应的电信设备上读取业务数据并转换为网元配置中相应的配置块；确定初始网元集合并按业务类型规划各网元配置中配置块的反算顺序；遍历初始网元集合中每个网元并根据各网元的网元配置获取业务网元集合；遍历业务网元集合各元素并根据业务关键字和网元序列找到每条业务对应的所有配置块以拼接成完整的业务。该反算方法中，将不同类型电信设备的业务数据转换为统一格式的网元配置，支持多种电信设备混合组网的情况，扩展性较强，对于新增电信设备，仅需将电信设备的业务数据转换为网元配置，通用性较强。

Description

一种网管对混合组网业务的反算方法 技术领域
本发明涉及电信网传输管理技术，尤其涉及一种网管对混合组网业务的反算方法。
背景技术
目前，在传输网网管对电信设备的管理过程中，网管除了配置业务、下载业务到电信设备外，也常需要从电信设备读取已配置的业务数据。工程应用中，管理人员也常通过命令行接口在电信设备上配置业务，为了保持电信设备和网管的业务数据的一致性，网管也需要从电信设备读取命令行配置的业务数据。由于网管管理的一条业务一般涉及到多个电信设备，业务数据是分散到这些电信设备上的，网管需要将多个电信设备上分散的业务数据进行拼接以形成网管可管理的完整业务，从而实现对业务端到端的反算功能。
然而，随着电信设备种类的增加，现有的反算方法一般只支持特定的业务类型，不能支持分组传输网(Packet Transport Network，PTN)、综合承载与传送网络(IP Radio Access Net，IPRAN)等不同电信设备混合组网的情况，因而不具有通用性，对新增的电信设备也无法快速地进行支持，业务类型的扩展性差。
发明内容
有鉴于此，本发明提供一种能支持不同类型设备的混合组网的网管对混合组网业务的反算方法。
一种网管对混合组网业务的反算方法，其用于将不同类型的电信设备混合组网的业务数据形成网管可管理的完整业务，所述网管对混合组网业务的反算方法包括以下步骤：
网元从相应的电信设备上读取业务数据并转换为网元配置中相应的配置块；
确定初始网元集合并按业务类型规划各网元配置中配置块的反算顺序；
遍历初始网元集合中每个网元并根据各网元的网元配置获取业务网元集合；
遍历业务网元集合各个元素并根据业务关键字和网元序列找到每条业务对应的所有配置块以拼接成完整的业务。
与现有技术相比，本发明提供的网管对混合组网业务的反算方法中，将不同类型的电信设备的业务数据转换为统一格式的网元配置，支持了多种电信设备混合组网的情况，具有较强的扩展性，对于新增的电信设备或新的业务类型，仅需将电信设备或新增类型的业务数据转换为网元配置，其他的部分无需修改即可支持反算，具有通用性，支持了业务类型的扩展。
附图说明
图1是本发明提供的一种网管对混合组网业务的反算方法的流程图。
图2是图1中获取业务网元集合的流程图。
图3是业务网元集合的内部结构图。
如下具体实施方式将结合上述附图进一步说明本发明。
具体实施方式
请参阅图1，其为本发明实施方式提供的一种网管对混合组网业务的反算方法，其用于将不同类型的电信设备混合组网的业务数据形成网管可管理的完整业务，本实施方式中，混合组网包括分组传输网(Packet Transport Network，PTN)、综合承载与传送网络(IP Radio Access Net，IPRAN)及光传送网(Optical Transport Network，OTN)。所述网管对混合组网业务的反算方法包括以下步骤：
S100：网元从相应的电信设备上读取业务数据并转换为网元配置中相应的配置块；
S200：确定初始网元集合并按业务类型规划各网元配置中配置块的反算顺序；
S300：遍历初始网元集合中每个网元并根据各网元的网元配置获取业务网元集合；
S400：遍历业务网元集合各个元素并根据业务关键字和网元序列找到每条业务对应的所有配置块以拼接成完整的业务。
在步骤S100中，网元与电信设备一一对应，网元是电信设备在网管上的逻辑实体，网元向电信设备发送读取业务数据的命令，电信设备将业务数据上报给网元。由于不同的电信设备支持同一种业务，但各电信设备上此业务的数据格式不同，所以需要在网元中将电信设备上报的业务数据转换成相同格式的网元配置，这样也屏蔽了电信设备的差异性，网元配置由不同业务类型的配置块组成，相同类型的业务数据都在同一个配置块中。
对完整业务进行反算前，必须首先获取所有网元的网元配置，否则可能由于某些网元没有网元配置而造成业务的不完整，网元配置只 含有业务在此网元上的数据，一条完整业务在多个网元上的网元配置中都有相应配置块，配置块是二进制的数据块，包括同一类型的业务条目，每个业务条目对应着电信设备上的一条业务。
网元从相应的电信设备上读取业务数据，并转换为网元配置，不同类型的业务数据在不同的配置块中。网元配置中包括的各业务类型的配置块和各类电信设备的支持情况如下表1所示：
表1
Figure PCTCN2015071914-appb-000001
Figure PCTCN2015071914-appb-000002
从表1中可以看到，不同电信设备支持的业务类型不同，而网元配置按照业务类型分成不同配置块，配置块数目等于最大的业务类型数目。这样，相同格式的网元配置就可以适配不同的电信设备，业务数据转换为网元配置时，只需将电信设备支持的配置块填入业务数据，将电信设备不支持的配置块设置为空即可。对于新增的电信设备，同样将新增的电信设备的业务数据转换为网元配置，若新增业务类型，同样将新增业务类型数据转换为网元配置。
在步骤S200中，根据业务类型的顺序，依次对这些配置块中的业务进行反算，一种类型的业务全部反算完之后，再启动下一种类型业务的反算。初始网元的集合由网管的使用者来确定，可以只含一个网元，或者数个网元，也可以是整个网络的网元。
在反算过程中，会遍历初始网元集合内各网元的网元配置，从而反算出经过这些网元的所有业务，根据一个网元的网元配置反算出来的仅仅是经过此网元的所有业务，而根据网管使用者的需求，可能需要计算经过某几个网元的业务，或者整个网络的业务，这可以由调整初始网元集合中网元的数目来实现。
由于业务之间存在层次关系，如VC必须承载在Tunnel上，L2VPN必须承载在VC上，所以需要先确定业务类型在反算时的顺序，如下表2所示：
表2
业务类型的反算顺序
Tunnel通道
VC虚电路
保护对
L2VPN二层虚拟专用网
L3VPN三层虚拟专用网
BFD双向转发检测
主动OAM
按需OAM
VRRP虚拟路由器冗余协议
环
按照此顺序，对不同的业务类型的配置块先后进行反算，分别拼接成完整的业务。
在步骤S300中，业务关键字是业务的唯一标示，一条业务分散到多个网元的网元配置中，但其关键字是相同的。业务网元集合中的每个元素包括业务关键字及网元序列，其格式形如<业务关键字，网元序列>，每个业务关键字唯一对应一个网元序列，序列中的每个网元都是此业务关键字对应业务所经过的网元。
需对某类型的业务进行反算时，先要在此类型业务的配置块中取出业务关键字，然后根据此业务关键字再到其他网元的网元配置中寻找相同的关键字，找到之后取出此业务关键字对应的配置块信息。
请参阅图2，在步骤S300中，获取业务网元集合包括以下步骤：
S310：从初始网元集合中选取当前网元并对当前网元的网元配置中配置块排序；
S320：从当前网元的网元配置中按顺序取出配置块中的业务关键字并找到此业务关键字对应的网元序列以组成元素加入到业务网元集合中；
S330：将当前网元的网元配置中所有配置块的业务关键字进行遍历以找到各对应网元序列并组成元素加入业务网元集合中；
S340：从初始网元集合移除当前网元并继续遍历各网元以将各网元的各配置块中的业务关键字及相对应的网元序列组成元素加入业务网元集合中直至遍历完所有网元。
在步骤S310中，排序规则如上表2所示，通过此排序使得网元配置中的配置块按一定的顺序进行反算。
在步骤S320中，关键字以组合的方式生成，各字段由分隔符隔开，若以逗号为分隔符，则形如<业务类型，业务id，子业务id>，各字段的取值如表3所示。
表3
Figure PCTCN2015071914-appb-000003
Figure PCTCN2015071914-appb-000004
业务关键字是唯一确定一条业务的，虽然一条业务分散到各个网元的网元配置中，但在这些网元配置中，业务关键字都是一样的。不同的配置块获取下一个网元的方法有所不同，如下表4所示：
表4
Figure PCTCN2015071914-appb-000005
Figure PCTCN2015071914-appb-000006
在步骤S330中，遍历配置块的顺序按照表2中配置块的反算顺序，配置块中遍历业务关键字的顺序则没有关系，一般按照自然顺序即可。
在步骤S340中，依次遍历了初始网元集合中每个网元的网元配置，遍历了这些网元配置上的所有业务，每条业务都得到<业务关键 字，网元序列>的元素，所有元素最终组成了业务网元集合。此业务网元集合的内部结构图如图3所示。
在步骤S400中，网元集合中的各元素为各业务以及其对应的网元序列，网元序列是完整业务分散的所有网元组成的，遍历业务网元集合中的每个元素，对于每个元素，根据业务关键字对应的网元序列，遍历每个网元的网元配置，在这些网元配置中找到此业务的配置块，进行业务拼接时，由于完整业务与网元的业务数据在结构上有差异，需要建立网元的业务数据与完整业务的数据映射关系，根据此映射关系，遍历在步骤S300中得到的网元集合，由每个网元的业务数据拼接成完整的业务。相关的数据的映射关系如下表5所示：
表5
Figure PCTCN2015071914-appb-000007
Figure PCTCN2015071914-appb-000008
本发明提供的网管对混合组网业务的反算方法中，将不同类型的 电信设备的业务数据转换为统一格式的网元配置，支持了多种电信设备混合组网的情况，具有较强的扩展性，对于新增的电信设备或新的业务类型，仅需将电信设备或新增类型的业务数据转换为网元配置，其他的部分无需修改即可支持反算，具有通用性，支持了业务类型的扩展。
可以理解的是，对于本领域的普通技术人员来说，可以根据本发明的技术构思做出其他各种相应的改变与变形，而所有这些改变与变形都应属于本发明权利要求的保护范围。

Claims (4)

  1. 一种网管对混合组网业务的反算方法，其用于将不同类型的电信设备混合组网的业务数据形成网管可管理的完整业务，所述网管对混合组网业务的反算方法包括以下步骤：
    网元从相应的电信设备上读取业务数据并转换为网元配置中相应的配置块；
    确定初始网元集合并按业务类型规划各网元配置中配置块的反算顺序；
    遍历初始网元集合中每个网元并根据各网元的网元配置获取业务网元集合；
    遍历业务网元集合各个元素并根据业务关键字和网元序列找到每条业务对应的所有配置块以拼接成完整的业务。
  2. 如权利要求1所述的网管对混合组网业务的反算方法，其特征在于，所述业务网元集合中的每个元素包括业务关键字及网元序列，每个业务关键字唯一对应一个网元序列，各网元序列中的每个网元都是此业务关键字对应业务所经过的网元。
  3. 如权利要求1所述的网管对混合组网业务的反算方法，其特征在于，在获取业务网元集合的步骤中包括以下步骤：
    从初始网元集合中选取当前网元并将当前网元的网元配置中的配置块排序；
    从当前网元的网元配置中按顺序取出配置块中的业务关键字并找到此业务关键字对应的网元序列以组成元素加入到业务网元集合中；
    将当前网元的网元配置中所有配置块的业务关键字进行遍历以 找到各对应网元序列并组成元素加入业务网元集合中；
    从初始网元集合移除当前网元并继续遍历各网元以将各网元的网配置中的各配置块中的业务关键字及相对应的网元序列组成元素加入业务网元集合中直至遍历完所有初始网元集合的网元。
  4. 如权利要求1所述的网管对混合组网业务的反算方法，其特征在于，所述混合组网包括分组传输网(Packet Transport Network，PTN)、综合承载与传送网络(IP Radio Access Net，IPRAN)及光传送网(Optical Transport Network，OTN)。
PCT/CN2015/071914 2014-03-18 2015-01-30 一种网管对混合组网业务的反算方法 WO2015139533A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410100267.8 2014-03-18
CN201410100267.8A CN103929327B (zh) 2014-03-18 2014-03-18 一种网管对混合组网业务的反算方法

Publications (1)

Publication Number Publication Date
WO2015139533A1 true WO2015139533A1 (zh) 2015-09-24

Family

ID=51147411

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/071914 WO2015139533A1 (zh) 2014-03-18 2015-01-30 一种网管对混合组网业务的反算方法

Country Status (2)

Country Link
CN (1) CN103929327B (zh)
WO (1) WO2015139533A1 (zh)

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103929327B (zh) * 2014-03-18 2017-08-01 烽火通信科技股份有限公司 一种网管对混合组网业务的反算方法
CN105763379B (zh) * 2016-04-14 2019-01-15 烽火通信科技股份有限公司 减少网管与控制平面间同步数据量的方法及系统
CN107547220A (zh) * 2016-06-27 2018-01-05 中兴通讯股份有限公司 一种多子网元分层管理的方法及装置
CN107343229B (zh) * 2017-06-12 2020-02-18 烽火通信科技股份有限公司 一种potn业务管理的方法
CN109246494B (zh) * 2018-10-18 2021-08-10 广东省电信规划设计院有限公司 Ptn-otn混合组网方法和光传送网络架构
CN109962812B (zh) * 2019-03-04 2022-03-25 烽火通信科技股份有限公司 一种电层离散业务反算方法及系统
CN111526052B (zh) * 2020-04-17 2023-04-07 中移（杭州）信息技术有限公司 网元指令管理方法、装置、网络设备及存储介质
CN112087322B (zh) * 2020-08-19 2021-07-20 烽火通信科技股份有限公司 配置网元基础信息的方法、装置、设备及可读存储介质
CN113055226B (zh) * 2021-02-20 2022-04-26 烽火通信科技股份有限公司 一种网管配置数据下载的排序方法及装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7370109B1 (en) * 2002-07-08 2008-05-06 Cisco Technology, Inc. Hierarchical management of objects
CN102231679A (zh) * 2011-06-29 2011-11-02 烽火通信科技股份有限公司 网元和网管实现配置同步的方法
CN102412996A (zh) * 2011-11-24 2012-04-11 烽火通信科技股份有限公司 基于xml网元动态脚本信息进行业务信息快速校核的方法
CN103929327A (zh) * 2014-03-18 2014-07-16 烽火通信科技股份有限公司 一种网管对混合组网业务的反算方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7370109B1 (en) * 2002-07-08 2008-05-06 Cisco Technology, Inc. Hierarchical management of objects
CN102231679A (zh) * 2011-06-29 2011-11-02 烽火通信科技股份有限公司 网元和网管实现配置同步的方法
CN102412996A (zh) * 2011-11-24 2012-04-11 烽火通信科技股份有限公司 基于xml网元动态脚本信息进行业务信息快速校核的方法
CN103929327A (zh) * 2014-03-18 2014-07-16 烽火通信科技股份有限公司 一种网管对混合组网业务的反算方法

Also Published As

Publication number Publication date
CN103929327A (zh) 2014-07-16
CN103929327B (zh) 2017-08-01

Similar Documents

Publication Publication Date Title
WO2015139533A1 (zh) 一种网管对混合组网业务的反算方法
US10033623B2 (en) Multithreaded system and method for establishing network connections
EP3469765B1 (en) Method, system and computer program for visualizing networks
US8526325B2 (en) Detecting and identifying connectivity in a network
US11075814B2 (en) Sub-topology discovery for operating hybrid solutions
CN109729012B (zh) 一种单播报文传输方法和装置
CN106487558B (zh) 一种实现接入设备扩缩容的方法和装置
CN109818858B (zh) 用于实现域间拓扑关系自动拼接的方法、装置和系统
CN108809847A (zh) 实现负载均衡的方法、装置和网络系统
WO2021047011A1 (zh) 数据处理方法及装置、计算机存储介质
CN112956158B (zh) 结构数据平面监视
US11855893B2 (en) Tag-based cross-region segment management
CN110932906A (zh) 基于snmp技术的数据中心网络拓朴结构发现方法及其拓朴结构发现系统
CN103905251A (zh) 网络拓扑获取方法及装置
US8914503B2 (en) Detected IP link and connectivity inference
CN106452915B (zh) Mpls vpn网络拓扑发现的方法及装置
JP2010097273A (ja) ネットワーク構成情報取得方法および装置
US11799755B2 (en) Metadata-based cross-region segment routing
CN106027396B (zh) 一种路由控制方法、装置和系统
US10069715B2 (en) Method for deploying resource in cloud computing environment
CN104579979A (zh) 一种基于mac信息的网络拓扑发现方法
CN108400922A (zh) 虚拟局域网络配置系统与方法及其计算机程序产品
CN105721346A (zh) 一种基于软件定义网络的应用带宽配置方法及控制器
TW201803314A (zh) 伺服器、開關、通信系統、通信方法及記錄媒體
JP7056207B2 (ja) トポロジ決定装置、トポロジ決定方法、トポロジ決定プログラムおよび通信システム

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

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

Country of ref document: EP

Kind code of ref document: A1