WO2017206565A1 - Procédé, dispositif et contrôleur de gestion d'appareil - Google Patents

Procédé, dispositif et contrôleur de gestion d'appareil Download PDF

Info

Publication number
WO2017206565A1
WO2017206565A1 PCT/CN2017/076492 CN2017076492W WO2017206565A1 WO 2017206565 A1 WO2017206565 A1 WO 2017206565A1 CN 2017076492 W CN2017076492 W CN 2017076492W WO 2017206565 A1 WO2017206565 A1 WO 2017206565A1
Authority
WO
WIPO (PCT)
Prior art keywords
controller
type
topology
service
information
Prior art date
Application number
PCT/CN2017/076492
Other languages
English (en)
Chinese (zh)
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 WO2017206565A1 publication Critical patent/WO2017206565A1/fr

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/04—Network management architectures or arrangements
    • H04L41/044—Network management architectures or arrangements comprising hierarchical management structures
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/12—Discovery or management of network topologies

Definitions

  • the present invention relates to the field of communications, and in particular to a device processing method, apparatus, and controller.
  • the network scale is getting larger and larger, more and more devices are in the network, and the network structure is more and more complicated, which makes network management more and more difficult, and business deployment becomes more and more difficult.
  • the related art has a problem that the operator network management and maintenance and service deployment are highly complex.
  • the embodiments of the present invention provide a device processing method, a device, and a controller, so as to at least solve the problem that the carrier network management maintenance and service deployment complexity in the related art are high.
  • a device processing method including: determining a controller type of a controller for performing a service processing, wherein the controller type includes: controlling a network device in a separate domain a first type of controller, a second type of controller that controls one or more of the first type of controllers, the separate domain being a domain obtained by dividing a network architecture of a predetermined network; And processing the service of the predetermined network.
  • processing the service of the predetermined network according to the determined controller type includes: collecting, by using a southbound interface The first type of controller controls the original topology information of the network device in the domain, where the original topology information includes connection information between the network devices in the first type of controller control domain; and according to the collected original topology information, The first type of controller controls topology information of the network device in the domain; and processes the service of the predetermined network according to the determined topology information.
  • determining, according to the collected original topology information, the topology information of the network device in the control domain of the first type controller includes: removing intermediate node information in the connection information; saving the information of the intermediate node after removing The connection information is obtained, and the topology information of the network device in the control domain of the first type controller is obtained.
  • processing the service of the predetermined network according to the determined topology information including: receiving service deployment information delivered by a second type controller to which the first type of controller belongs, according to the received service Deployment information, and the topology information, for service deployment.
  • processing the service of the predetermined network according to the determined controller type includes: receiving one or more of the foregoing Corresponding to the topology information of the network device in the control domain, where the received topology information includes one or more connection information between the network devices in the control domain corresponding to the first type controller; And the topology information obtained by the second type controller is used to determine the total topology information of the network device in the control domain; and the service of the predetermined network is processed according to the total topology information.
  • determining, according to the received topology information, the total topology information of the network device in the control domain of the second type of controller includes: establishing, according to the received topology information, one or more of the foregoing A sub-topology table corresponding to a type of controller; establishing a total topology table of network devices in the control domain of the second type controller according to the established sub-topology table.
  • processing the service of the predetermined network according to the total topology information includes: querying a total topology table of the second type controller according to the service deployed in the received user configuration request, and determining a source by the source a path from the node to the target node; determining, according to the determined path, and the sub-topology table, a first type of controller to which one or more nodes on the path belong; deploying according to the received user configuration request The service is delivered to the first type controller that is determined by the one or more nodes to perform service deployment.
  • a device processing apparatus comprising: a first determining module configured to determine a controller type of a controller for performing a business process, wherein the controller type comprises: a first type of controller that is controlled by a network device in a separate domain, a second type of controller that controls one or more of the first type of controllers, the separate domain is a domain obtained by dividing a network architecture of a predetermined network; and the processing module is configured to determine the type of the controller according to the determined Processing the service of the predetermined network.
  • the processing module includes: a collecting unit, configured to collect, by using a southbound interface, the first type of controller in a control domain, where the controller for performing service processing is a first type of controller
  • the original topology information of the network device where the original topology information includes the connection information between the network devices in the first type of controller control domain
  • the first determining unit is configured to determine, according to the collected original topology information,
  • the first type of controller controls topology information of the network device in the domain
  • the first processing unit is configured to process the service of the predetermined network according to the determined topology information.
  • the first determining unit includes: a removing subunit, configured to remove intermediate node information in the connection information; and saving the subunit, configured to save connection information after removing the intermediate node information, to obtain a
  • the first type of controller controls topology information of network devices in the domain.
  • the first processing unit includes: a receiving subunit, configured to receive service deployment information delivered by a second type controller to which the first type controller belongs; and a deployment subunit, configured to receive according to the received The service deployment information and the topology information are used for service deployment.
  • the processing module includes: a receiving unit, configured to receive one or more reports sent by the first type controller if the controller for performing service processing is a second type controller Corresponding to the topology information of the network device in the control domain, where the received topology information includes one or more connection information between the network devices in the control domain corresponding to the first type controller; and the second determining unit is configured to receive according to the And the second topology unit is configured to process the service of the predetermined network according to the total topology information.
  • the second determining unit includes: a first establishing subunit, configured to respectively establish a sub-topology table corresponding to one or more of the first type controllers according to the received topology information; And establishing a subunit, configured to establish, according to the established sub-topology table, a total topology table of network devices in the control domain of the second type controller.
  • the second processing unit includes: a first determining subunit, configured to query a total topology table of the second type controller according to the service deployed in the received user configuration request, and determine a source node to a path of the target node, the second determining subunit, configured to determine, according to the determined path, and the sub-topology table, a first type of controller to which one or more nodes on the path belong; And configuring, according to the received service configured in the user configuration request, to send configuration information to the first type controller that is determined by the one or more nodes to perform service deployment.
  • a controller is also provided.
  • the controller includes the device processing apparatus of any of the foregoing.
  • a storage medium is also provided.
  • the storage medium is configured to store program code for performing a step of determining a controller type of a controller for performing a business process, wherein the controller type comprises: a first type that controls network devices within a separate domain a controller, a second type controller that controls one or more of the first type controllers, where the individual domain is a domain obtained by dividing a network architecture of a predetermined network; according to the determined controller type, The business of the predetermined network is processed.
  • the storage medium is further configured to store program code for performing the following steps: in case the controller for performing business processing is a first type controller, according to the determined controller type,
  • the processing of the service of the predetermined network includes: collecting, by the southbound interface, original topology information of the network device in the first type of controller control domain, where the original topology information includes the first type of controller between the network devices in the control domain
  • the connection information is determined, according to the collected original topology information, the topology information of the network device in the control domain of the first type controller is determined; and the service of the predetermined network is processed according to the determined topology information.
  • the storage medium is further configured to store program code for performing the following steps: determining, according to the collected original topology information, the topology information of the network device in the first type controller control domain includes: removing the connection The intermediate node information in the information; the connection information after the information of the intermediate node is removed is saved, and the topology information of the network device in the control domain of the first type controller is obtained.
  • the storage medium is further configured to store program code for performing the following steps: processing the service of the predetermined network according to the determined topology information comprises: receiving a second type to which the first type controller belongs Service deployment information delivered by the controller; performing service deployment according to the received service deployment information and the topology information.
  • the storage medium is further configured to store program code for performing the following steps: in case the controller for performing business processing is a second type controller, according to the determined controller type,
  • the processing of the service of the predetermined network includes: receiving one or more topology information of the network device in the corresponding control domain reported by the first type controller, where the received topology information includes one or more of the first types Corresponding to the connection information between the network devices in the control domain; determining the total topology information of the network devices in the control domain of the second type controller according to the received topology information; and determining the predetermined topology information according to the total topology information
  • the business of the network is processed.
  • the storage medium is further configured to store program code for performing the following steps: determining, according to the received topology information, the total topology information of the network device in the control domain of the second type controller comprises: according to the received The topology information is respectively configured to establish a sub-topology table corresponding to one or more of the first type of controllers; and according to the established sub-topology table, establish a total topology table of network devices in the control domain of the second type controller .
  • the network is hierarchically managed by using the controller: the first type controller is used to control the individual domain, and the second type controller controls the plurality of first type controllers to control the multiple domains. And processing the services in the network according to the type of controller, Therefore, the problem of high complexity of network management and maintenance and service deployment of the carrier in the related art can be solved, and the effect of reducing the complexity of network management and maintenance and service deployment can be achieved.
  • FIG. 1 is a block diagram showing the hardware structure of a controller of a device processing method according to an embodiment of the present invention
  • FIG. 2 is a schematic diagram of a network architecture of a device processing method according to an embodiment of the present invention
  • FIG. 3 is a flowchart of a device processing method according to an embodiment of the present invention.
  • FIG. 4 is a schematic diagram showing the overall internal structure of a controller of a device processing method according to a preferred embodiment of the present invention.
  • FIG. 5 is a schematic diagram showing the internal structure of a topology management module 44 of a device processing method according to a preferred embodiment of the present invention.
  • FIG. 6 is a flow chart of a method of processing a device in accordance with a preferred embodiment of the present invention.
  • FIG. 7 is a schematic diagram of an abstract topology on a D controller of a device processing method in accordance with a preferred embodiment of the present invention.
  • FIG. 8 is a schematic diagram of sub-topology partitioning on a D1 controller of a device processing method according to a preferred embodiment of the present invention.
  • FIG. 9 is a schematic diagram of an abstract topology on an H controller of a device processing method according to a preferred embodiment of the present invention.
  • FIG. 10 is a schematic diagram of a sub-topology on an H controller of a device processing method according to a preferred embodiment of the present invention.
  • FIG. 11 is a block diagram showing the structure of a device processing apparatus according to an embodiment of the present invention.
  • FIG. 12 is a structural block diagram 1 of a processing module 114 in a device processing apparatus according to an embodiment of the present invention.
  • FIG. 13 is a structural block diagram of a first determining unit 124 in a device processing apparatus according to an embodiment of the present invention.
  • FIG. 14 is a structural block diagram of a first processing unit 126 in a device processing apparatus according to an embodiment of the present invention.
  • 15 is a structural block diagram 2 of a processing module 114 in a device processing apparatus according to an embodiment of the present invention.
  • FIG. 16 is a structural block diagram of a second determining unit 154 in a device processing apparatus according to an embodiment of the present invention.
  • FIG. 17 is a structural block diagram of a second processing unit 156 in a device processing apparatus according to an embodiment of the present invention.
  • Figure 18 is a block diagram showing the structure of a controller in accordance with an embodiment of the present invention.
  • FIG. 1 is a hardware structural block diagram of a controller of the device processing method according to the embodiment of the present invention.
  • controller 10 may include one or more (only one shown) processor 102 (processor 102 may include, but is not limited to, a processing device such as a microprocessor MCU or a programmable logic device FPGA)
  • processor 102 may include, but is not limited to, a processing device such as a microprocessor MCU or a programmable logic device FPGA)
  • a memory 104 for storing data
  • a transmission device 106 for communication functions.
  • controller 10 may also include more or fewer components than shown in Figure 1, or have A different configuration than that shown in FIG.
  • the memory 104 can be used to store corresponding data and software programs and modules of the application software, such as program instructions/modules corresponding to the device processing method in the embodiment of the present invention, and the processor 102 runs the software program and the module stored in the memory 104, thereby The above methods are implemented by performing various functional applications and data processing.
  • Memory 104 may include high speed random access memory, and may also include non-volatile memory such as one or more magnetic storage devices, flash memory, or other non-volatile solid state memory.
  • memory 104 may further include memory remotely located relative to processor 102, which may be coupled to controller 10 via a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.
  • Transmission device 106 is for receiving or transmitting data via a network.
  • the network specific examples described above may include a wireless network provided by a communication provider of the controller 10.
  • the transmission device 106 includes a Network Interface Controller (NIC) that can be connected to other network devices through a base station to communicate with the Internet.
  • the transmission device 106 can be a Radio Frequency (RF) module for communicating with the Internet wirelessly.
  • NIC Network Interface Controller
  • RF Radio Frequency
  • FIG. 2 is a schematic diagram of a network architecture of a device processing method according to an embodiment of the present invention.
  • the network architecture of the network is divided into an access domain, a convergence domain, and a core domain, and the left and right are symmetric.
  • the network includes the access device ACC, the aggregation device AGG, the homebrew system border device ASBR, and the device P in each domain.
  • a Software Defined Network (SDN) controller is used to manage the network, and the separation between the control plane and the forwarding plane can be achieved.
  • the SDN controller is divided into two layers. Each domain is managed by a single domain controller, that is, a D controller. On the D controller, a multi-domain controller, that is, an H controller, is used to centrally manage the entire network. That is, in the hierarchical network architecture, each domain is separately managed using the D controller, and the entire network is managed using the H controller.
  • the D controller and the H controller of each domain can have two controllers in active and standby, and the D controller is connected to at least two devices in the domain (D controller general and intra-domain boundaries) The device is connected).
  • a hierarchical controller can be more than two layers, depending on the size of the network.
  • the carrier network may also include more or less domains than those shown in FIG. 3 (the access domain and the aggregation domain are divided according to actual conditions, and are not limited to two or the same number or both, and the core domain is not It is limited to two), or has a different network architecture than that shown in Figure 2 (access domain, aggregation domain, and symmetric domain left and right asymmetric, or divided into different domain types than Figure 2).
  • other types of controllers that can control network devices in separate domains and second type controllers that can control one or more first types of controllers , can achieve the purpose of hierarchical management of the network.
  • FIG. 3 is a flowchart of a device processing method according to an embodiment of the present invention. As shown in FIG. 3, the process includes the following steps:
  • Step S302 determining a controller type of a controller for performing service processing, where the controller type includes: a first type controller that controls network devices in a separate domain, and controls one or more first types a second type of controller that controls the domain, and the separate domain is a domain obtained by dividing a network architecture of a predetermined network;
  • Step S304 processing the service of the predetermined network according to the determined controller type.
  • the network is hierarchically managed by using the controller: the first type controller is used to control the individual domain, and the second type controller controls the plurality of first type controllers to control the multiple domains, and
  • the service of the network is processed according to the controller type, which solves the problem of high complexity of network management and maintenance and service deployment of the carrier in the related technologies, and reduces the complexity of network management and maintenance and service deployment.
  • Step S304 may further include: collecting, by the southbound interface, original topology information of the network device in the first type controller control domain, where the original topology information includes connection information between the network devices in the first type controller control domain; and the original topology information according to the collected And determining, by the first type of controller, topology information of the network device in the control domain, and processing the service of the predetermined network according to the determined topology information.
  • the controller for performing service processing is the first type controller, that is, the determined controller type is a first type controller that controls network devices in a separate domain, and the first type controller can pass SNMP.
  • the southbound interface such as NETCONFIG and BGP-LS, collects the original topology information of the network device in the controlled domain.
  • the original topology information here may be the connection information between the nodes in the control domain of the first type controller.
  • Based on the collected original topology information it may be determined that the first type of controller controls topology information between network devices in the domain.
  • the connection information between the network devices in the control domain of the first type controller may be determined by the topology information between the network devices. Therefore, the topology information of the network devices in the domain may be controlled according to the determined first type controller.
  • the business of the network is processed.
  • the controller for performing the service processing is the first type controller, determining the topology information of the network device in the control domain of the first type controller according to the collected original topology information. And processing the business according to the topology, reducing the complexity of business processing.
  • determining, according to the collected original topology information, the topology information of the network device in the control domain of the first type of controller may be in multiple manners, for example, according to the connection relationship between the network devices in the original topology information, A type of controller controls the topology information of the connection relationship between all devices in the domain. For example, based on the collected original topology information, the role and the location topology of the device in the network may be abstracted according to the location of the device, and the boundary node and the service in the control domain of the first type controller may be reserved.
  • the key nodes of the deployment (such as ACC, AGG, and ASBR nodes in the network) filter out intermediate nodes and/or non-critical nodes (such as P nodes) to determine the topology information of the network devices in the first type of controller control domain.
  • the method determines the topology information of the network device in the control domain of the first type of the controller, for example, the topology information may be determined by using the foregoing manner of establishing topology information, and, for example, may also be based on an internal gateway protocol run by the first type of controller ( The Interior Gateway Protocol (IGP) performs sub-topology division on the confirmed topology information, and the divided sub-topology corresponds to the number of access rings included in the first type controller.
  • IGP Interior Gateway Protocol
  • the topology information of the first type controller When the topology information of the first type controller is determined, the information about the intermediate nodes included in the connection information in the original topology information is removed, which reduces the complexity of the topology information and improves the efficiency of the service processing. .
  • the service of the service of the predetermined network may be processed according to the determined topology information, for example, the service deployment information delivered by the second type controller to which the received first type controller belongs, and the The first type of controller controls the topology information of the network device in the domain, and performs service deployment.
  • the service configuration may include delivering a corresponding border gateway protocol (BGP) to the node related to the service in the control domain of the first type of controller. And configuring, for example, adding, changing, deleting, etc., the service-related nodes in the control domain of the first type controller according to the determined topology information.
  • BGP border gateway protocol
  • the first type of controller performs service deployment and service according to the service deployment information delivered by the controller of the second type of the controller and the topology information of the network device in the domain controller of the first type controller.
  • the deployment is automatically completed through the interaction between controllers, which reduces user operations and reduces the complexity of service deployment.
  • the step S304 may further include: receiving the topology information of the network device in the corresponding control domain reported by the one or more first type controllers.
  • the received topology information includes one or more first type controllers corresponding to the connection information between the network devices in the control domain; and according to the received topology information, determining the total topology information of the network devices in the second type controller control domain
  • the service of the predetermined network is processed according to the total topology information.
  • the second type controller receives the topology information of the network device in the corresponding control domain reported by each first type controller controlled by the controller, and determines the network configuration in the control domain according to the received topology information.
  • the total topology information of the backup device performs processing of the predetermined network service according to the determined total topology information. Since the second type controller has the total topology information of the network devices in its control domain, the service processing entry is single, and only the second type controller can be operated.
  • the service processing of the total topology information of the network device in the domain is controlled according to the second type of controller, which reduces the complexity of network management maintenance and service processing.
  • determining, according to the received topology information, the total topology information of the network device in the control domain of the second type of controller may be in multiple manners, for example, establishing, according to the received topology information, respectively, corresponding to the first type of controller.
  • the sub-topology table that is, the first type controller and the sub-topology table are in one-to-one correspondence, and the total topology table of the network devices in the second type controller is controlled according to the established sub-topology table, and, for example, according to the received topology information.
  • establishing a sub-topology table corresponding to the first type of controller and a total topology table corresponding to the second type of controller are respectively establishing.
  • a sub-topology table corresponding to the first type of controller is established according to the received topology information, and a total topology table of the network device in the second type controller is controlled according to the sub-topology table,
  • a hierarchical topology table By establishing a hierarchical topology table, the complexity of network management maintenance and service processing is reduced.
  • the service of the predetermined network may be processed in multiple manners, for example, according to the service deployed in the received user configuration request, querying the total topology table of the second type controller, and determining a The path from the source node to the target node determines, according to the determined path and the sub-topology table, the first type of controller to which one or more nodes on the path belong, according to the service deployed in the received user configuration request, to the determined one Or the first type of controller to which multiple nodes belong to deliver configuration information for service deployment.
  • the configuration request is sent to the second type controller.
  • the second type controller queries its total topology table based on the deployed services to calculate an end-to-end path and each sub-topology.
  • the table finds which first type of controller each node on the path belongs to.
  • the deployed services are decomposed and delivered to each first type of controller. If there are higher requirements on the reliability and service quality of the business, you can calculate the road.
  • the path is calculated, the multiple paths that meet the requirements are calculated. On this basis, the active/standby path protection of the service or traffic sharing is implemented.
  • the calculations here include both the calculations on the second type of controller and the calculations on the first type of controller.
  • the path corresponding to the service request is decomposed according to the service deployed in the received user configuration request, the total topology table of the second type controller, and the sub-topology table, and is delivered to the corresponding
  • the first type of controller has a single service deployment portal, and only needs to operate on the second type of controller, which reduces the complexity of network management maintenance and service processing.
  • a device processing method in which the first type controller is a D controller,
  • the second type of controller is described by taking an H controller as an example.
  • the device processing method of the preferred embodiment implements topology collection, topology abstraction, and sub-topology division to implement hierarchical management by using a layered SDN controller, which reduces the complexity of network management maintenance and service deployment, and improves deployment service flexibility. Sex.
  • each D controller manages transactions in respective domains, and only stores and manages topology data in the local domain. And each D controller also calculates an abstract topology based on the original topology information managed and sends it to the H controller. If the domain managed by the D controller includes multiple subnets, the sub-topology can be further divided; the H controller is responsible for processing the entire network transaction, storing and managing the abstract topology of the entire network, and according to the source of the topology information. Sub-topology division; after the network topology is collected, you can start service deployment and use the H controller as a unified portal.
  • the H controller queries its own abstract topology data according to the deployed service, calculates an end-to-end path, and finds out which D controller each node on the path belongs to. After obtaining the information, the H-deployed service is deployed. Decomposition and delivery to each D controller, each D controller is responsible for the deployment of services within the domain, thus enabling network-wide service deployment.
  • the service deployment portal is single, and only the H controller needs to be operated, which reduces the complexity of service deployment.
  • the specific business logic can be flexibly implemented by software in the H controller and the D controller according to user requirements, which improves flexibility and can even be customized according to user requirements.
  • the device processing method of the preferred embodiment will be described below in conjunction with a specific processing networking structure and an internal structure of the controller.
  • FIG. 4 is a schematic diagram showing the overall internal structure of a controller of a device processing method according to a preferred embodiment of the present invention, which may be a D controller or an H controller. As shown in FIG. 4, the controller includes a southbound interface 42, a topology management module 44, a calculation module 46, a service deployment module 48, and a northbound interface 410. The controller will be described below.
  • the southbound interface 42 is configured to interact with devices in the controller management domain (control domain); the topology management module 44 is coupled to the southbound interface 42 and configured to manage devices related to devices of the controller management domain
  • the information processing module 46 is connected to the topology management module 44, and is configured to perform path calculation according to related information of the service deployment; the service deployment module 48, the southbound interface 42 and the calculation module 46 are set to be based on the user.
  • the service configuration request and/or the service deployment information sent by the upper controller performs the service configuration related operation;
  • the northbound interface 410 is connected to the topology management module 44 and the service deployment module 48, and is mainly configured to complete with the user and/or The interaction between the superior controllers.
  • the topology management module 44 can also perform functions such as topology collection, topology storage, topology abstraction, sub-topology, and topology query.
  • FIG. 5 is a schematic diagram showing the internal structure of a topology management module 44 of a device processing method according to a preferred embodiment of the present invention. As shown in FIG. 5, the topology management module 44 includes a topology collection unit 52, a topology storage unit 54, a topology abstraction unit 56, a sub-topology division unit 58, and a topology query unit 510. The topology management module 44 will be described below.
  • the topology collection unit 52 is configured to collect original topology information of the network device in the controller control domain;
  • the topology storage unit 54 is connected to the topology collection unit 52, and is configured to store the collected original topology information;
  • the topology abstraction unit 56 is connected to the foregoing Topology storage unit 54, setting The topology is abstracted according to the stored original topology information to generate an abstract topology.
  • the sub-topology dividing unit 58 is connected to the topology storage unit 54 and configured to perform the storage of the original topology information when multiple rings are included in the controller management domain.
  • the topological query unit 510 is connected to the topology storage unit 54 and configured to perform topology query on the controller management domain.
  • FIG. 6 is a flow chart of a method of processing a device in accordance with a preferred embodiment of the present invention. As shown in Figure 6, the process includes the following steps:
  • Step S602 completing the basic configuration of the network.
  • the basic configuration of the network is as follows: The corresponding IP addresses are planned and configured for each interface of each network device and device. The devices are correctly connected to each other and the IGP routes are opened in each domain. It mainly includes assigning and configuring an IP address to each interface of each network device and device, and correctly connecting the devices to each other, and the IGP routes in each domain are opened.
  • step S604 the managed D controller device is added to the H controller, and a channel for information transmission is established between H and D.
  • the established information delivery channels can be RESTCONF and WEBSOCKET channels.
  • Step S606 adding the network device managed by the D controller, assigning a role to each device, and collecting topology information in the managed domain through the southbound interface.
  • the role assigned by the D controller to each device may be one of ACC, AGG, P, and ASBR.
  • the role assigned to the device can be determined according to the location of the device when the network is deployed.
  • the devices managed by the D1 and D5 controllers include the access device ACC, the intermediate device P, and the aggregation device AGG; the devices managed by the D2 and D4 controllers include the aggregation device AGG, and the intermediate device.
  • P the self-made system boundary device ASBR;
  • the device managed by the D3 controller includes the intermediate device P, and the self-made system boundary device ASBR.
  • the D controller can collect the original topology information in the managed domain through the southbound interface 42 such as SNMP, NETCONFIG, BGP-LS, and the like.
  • the original topology information here mainly refers to the connection information between nodes in the managed domain.
  • the path is directional, conversely, there is a path AGG1 -> P1 -> ACC1 from AGG1 to ACC1.
  • This path corresponds to two sides: AGG1 -> P1, P1 -> ACC1.
  • Each edge uses four attributes of the source device name and the source destination interface IP address as key value information. Of course, each side also has some other attributes, including bandwidth, METRIC values, and so on.
  • step S608 the D controller abstracts the topology according to the role set by the device, generates an abstract topology, and reports the generated abstract topology to the H controller.
  • the service key nodes and boundary nodes can be reserved according to the roles set by the device, and the intermediate nodes and non-critical nodes are filtered out, mainly referring to the P nodes.
  • the D controller is processed by the topology abstraction unit 56 to abstract the topology according to the role set by the device and the location of the device in the network.
  • the boundary nodes in the domain and the key nodes of the service deployment are reserved.
  • the ACC, AGG, and ASBR nodes in the network are mainly referred to. Filter out intermediate nodes and non-critical nodes, mainly referring to P nodes.
  • the path ACC1->P1->AGG1 in step S606 after abstract processing, forms an abstract topology of ACC1->AGG1.
  • the abstract topology formed by the abstraction process of its reverse path AGG1->P1->ACC1 is AGG1->ACC1.
  • an abstract topology as shown in Fig. 7 is formed, which includes the case of each D controller.
  • the rules of topology abstraction can be:
  • the source device takes the source device of the corresponding path; the destination device takes the destination device of the corresponding path; the source IP address takes the source interface IP address of the corresponding path; and the destination IP address takes the destination interface IP of the corresponding path.
  • sub-topology partitioning can also be used.
  • the domain managed by the D1 controller includes two access rings, which can be further divided into two sub-topologies.
  • the sub-topology of the sub-topology is as shown in FIG. 8. Shown. This is done by sub-topology partitioning according to the IGPs running in the D1 domain belonging to different IGP instances. For example, if you use the Open Shortest Path First (OSPF) protocol, different access rings are configured with different OSPF domains. If you use the Intermediate System to Intermediate System (ISIS) protocol, different accesses are used. The ring can be configured with different ISIS system-ids, and so on. If this is the case, it is necessary to plan in detail when performing step S402. Depending on the needs of the service, different rings may need to communicate with each other or may not require interworking. By default, it is not interoperable, and the topology needs to be isolated.
  • OSPF Open Shortest Path First
  • ISIS Intermediate System to Intermediate System
  • the D controller reports the generated abstract topology to the H controller, which can be implemented by the channel between the H controller and the D controller established in step S404.
  • the D controller When the network topology changes, such as the node uplink and downlink, interface UP/DOWN, the D controller should be able to respond to changes in time, modify its original topology information, and recalculate the abstract topology and / or sub-topology, and the latest calculation results Re-report to the H controller.
  • the network topology changes such as the node uplink and downlink, interface UP/DOWN
  • the D controller should be able to respond to changes in time, modify its original topology information, and recalculate the abstract topology and / or sub-topology, and the latest calculation results Re-report to the H controller.
  • Step S6010 After receiving the topology reported by each D controller, the H controller forms an abstract topology of the entire network, and according to the source of the topology information, the topology reported by each D controller is divided into a sub-topology.
  • the H controller After receiving the topology reported by each D controller, the H controller forms an abstract topology of the entire network, as shown in FIG. 9. According to the source of the topology information, the topology reported by each D is divided into a sub-topology, as shown in FIG. The eight sides shown in the solid line in Figure 9 are ASBR1->ASBR3, ASBR3->ASBR1, ASBR2->ASBR4, ASBR4->ASBR2, ASBR5->ASBR7, ASBR7->ASBR5, ASBR6->ASBR8, ASBR8- >ASBR6, which belongs to the connection between the boundaries of the homebrew system.
  • the corresponding topology information may not be collected automatically due to network deployment. At this point, the controller needs to support the function of manually entering topology information.
  • the H controller can have the ability to process topology addition, deletion, and update reported by the D controller.
  • Each controller (H controller and D controller) can provide topology query capabilities.
  • step S6012 the configuration request of the user is sent to the H controller, and the H controller queries its own global abstract topology data according to the deployed service, calculates an end-to-end path, and finds the path in each sub-topology. Which D controller belongs to each node, which is deployed The business is decomposed and distributed to each D controller.
  • the H controller can query the global abstract topology data and the sub-topology according to the deployed service, and decompose the deployed services to each D controller. For example, after the H controller receives the L3VPN service configuration request from the user, the service deployment module 48 triggers the calculation module 46 to perform the calculation, and the calculation module 48 queries the H controller's own abstract topology to calculate an end-to-end path. And in the sub-topology, it is found out which D controller each device node on the path belongs to. After the D controller corresponding to the device node machine is obtained, the deployed service is decomposed and delivered to each D controller.
  • an end-to-end path calculated on the H controller is: ACC1 ⁇ ->AGG1 ⁇ ->ASBR1 ⁇ ->ASBR3 ⁇ ->ASBR5 ⁇ ->ASBR7 ⁇ ->AGG3 ⁇ ->ACC4 ( ⁇ -> here refers to the bidirectional path of the forward and the direction).
  • the D controllers where each node is located are queried and grouped.
  • the packet information is as follows: ACC1 and AGG1, AGG1 and ASBR1, ASBR1 and ASBR3, ASBR3 and ASBR5, ASBR5 and ASBR7, ASBR7 and AGG3, AGG3 and ACC4.
  • the packets ACC1 and AGG1, AGG1 and ASBR1, ASBR3 and ASBR5, ASBR7 and AGG3, AGG3 and ACC4 respectively correspond to the domains managed by the D1, D2, D3, D4, and D5 controllers, and the packet information and service configuration information are respectively Send to each D controller.
  • the ASBR1 and the ASBR3, the ASBR5, and the ASBR7 are connected to each other.
  • the EBGP is configured and the SEND-LABLE capability is enabled to implement seamless MPLS service deployment.
  • the H controller can identify this and specify the corresponding D controller to deliver the corresponding BGP configuration, which refers to the D2, D3, and D4 controllers.
  • each D controller is responsible for service deployment in the local area, and completes network-wide service deployment.
  • each D controller After receiving the service deployment information sent by the H controller, each D controller is responsible for service deployment in the local area. For example, the D1 controller receives the packet information and the L3VPN configuration information of the ACC1 and the AGG1.
  • the BGP protocol is configured between the ACC1 and the AGG1 to deliver the virtual private network (VPN Virtual Private Network).
  • VPN virtual private network
  • VPN routing information also need to query local topology information to get a two-way road between ACC1 and AGG1
  • the path ACC1 ⁇ ->P ⁇ ->AGG1 opens the Label Switched Path (LSP) path in the domain. For example, you can configure a bidirectional TUNNEL tunnel or a Label Distribution Protocol (LDP), both of which can carry L3VPN services, depending on specific service requirements.
  • LSP Label Switched Path
  • the calculations here include both the calculations on the H controller and the calculations on the D controller.
  • the service deployment is performed on multiple rings of the same D controller control domain. For example, deploying services between ACC1 and ACC3. As shown in Figure 8, by default, the two rings in the D1 controller are not interworking. Therefore, if you configure services, you need to clear the routes between the two rings. After the H controller receives the service configuration information, it is found that both the ACC1 and the ACC3 are in the domain managed by the D1 controller. Therefore, only the service deployment information is sent to the D1 controller.
  • the D1 controller After receiving the configuration information sent by the H, the D1 controller calculates a path in the original topology information as ACC1 ⁇ ->P1 ⁇ ->AGG1 ⁇ ->P2 ⁇ ->ACC3. After querying the sub-topology, ACC1 and P1 belong to ring 1, and P2 and ACC3 belong to ring 2.
  • AGG1 belongs to the boundary device of the two rings, as shown in Figure 8. In this case, in addition to configuring BGP to open the inbound loop between ACC1 and AGG1, AGG1, and ACC3, you need to open routes between different rings. You can use BGP community attributes to achieve this.
  • the D1 controller can calculate multiple paths that meet the requirements when calculating the path. On this basis, the active/standby path protection of the service or traffic sharing is implemented.
  • the SDN controller is used to abstract and divide the network topology, and the SDN controller is used for layering. Management and rapid deployment of services based on this can effectively reduce the complexity of carrier network management and improve the efficiency and flexibility of deploying services.
  • the method according to the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course, by hardware, but in many cases, the former is A better implementation.
  • the technical solution of the present invention which is essential or contributes to the prior art, may be embodied in the form of a software product stored in a storage medium (such as ROM/RAM, disk,
  • the optical disc includes a number of instructions for causing a terminal device (which may be a cell phone, a computer, a server, or a network device, etc.) to perform the methods described in various embodiments of the present invention.
  • a device processing device is also provided, which is used to implement the above-mentioned embodiments and preferred embodiments, and has not been described again.
  • the term "module” may implement a combination of software and/or hardware of a predetermined function.
  • the apparatus described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware, is also possible and contemplated.
  • FIG. 11 is a structural block diagram of a device processing apparatus according to an embodiment of the present invention. As shown in FIG. 11, the apparatus includes a determining module 112 and a processing module 114, which will be described below.
  • the determining module 112 is configured to determine a controller type of a controller for performing a business process, wherein the controller type comprises: a first type controller that controls network devices in a separate domain, and one or more first types a second type controller controlled by the controller, the separate domain is a domain obtained by dividing a network architecture of the predetermined network; the processing module 114 is connected to the above
  • the determining module 112 is configured to process the services of the predetermined network according to the determined controller type.
  • FIG. 12 is a structural block diagram of a processing module 114 in a device processing apparatus according to an embodiment of the present invention. As shown in FIG. 12, the processing module 114 includes a collecting unit 122, a first determining unit 124, and a first processing unit 126. The processing module 114 will be described below.
  • the collecting unit 122 is configured to collect the original topology information of the network device in the first type controller control domain through the southbound interface, where the controller for performing the service processing is the first type controller, where the original topology information includes
  • the first type of controller controls the connection information between the network devices in the domain;
  • the first determining unit 124 is connected to the collecting unit 122, and is configured to determine, according to the collected original topology information, topology information of the network device in the control domain of the first type controller.
  • the first processing unit 126 is connected to the first determining unit 124, and is configured to process the service of the predetermined network according to the determined topology information.
  • FIG. 13 is a structural block diagram of a first determining unit 124 in a device processing apparatus according to an embodiment of the present invention. As shown in FIG. 13, the first determining unit 124 includes a removing subunit 132 and a saving subunit 134. The first determining unit 124 will be described below.
  • the removing sub-unit 132 is configured to remove the intermediate node information in the connection information; the saving sub-unit 134 is connected to the removing sub-unit 132, and is configured to save the connection information after removing the information of the intermediate node to obtain the first type of control. Controls the topology information of network devices in the domain.
  • FIG. 14 is a structural block diagram of a first processing unit 126 in a device processing apparatus according to an embodiment of the present invention. As shown in FIG. 14, the first processing unit 126 includes a receiving subunit 142 and a deployment subunit 144. The first processing unit 126 will be described below.
  • the receiving sub-unit 142 is configured to receive the service deployment information delivered by the second type controller to which the first type of controller belongs; the deployment sub-unit 144 is connected to the receiving sub-unit 142, and is configured to be configured according to the received service, and Topology information for service deployment.
  • FIG. 15 is a block diagram showing the structure of the processing module 114 in the device processing apparatus according to the embodiment of the present invention. As shown in FIG. 15, the processing module 114 includes a receiving unit 152, a second determining unit 154, and a second processing unit 156. The processing module 114 will be described below.
  • the receiving unit 152 is configured to receive topology information of the network device in the corresponding control domain reported by the one or more first type controllers, where the controller for performing the service processing is the second type controller, where
  • the topology information includes one or more first type controllers corresponding to the connection information between the network devices in the control domain;
  • the second determining unit 154 is connected to the receiving unit 152, and is configured to determine the second type according to the received topology information.
  • the controller controls the total topology information of the network device in the domain;
  • the second processing unit 156 is connected to the second determining unit 154, and is configured to process the service of the predetermined network according to the total topology information.
  • FIG. 16 is a structural block diagram of a second determining unit 154 in a device processing apparatus according to an embodiment of the present invention. As shown in FIG. 16, the second determining unit 154 includes a first establishing subunit 162 and a second establishing subunit 164. The second determining unit 154 will be described below.
  • the first establishing subunit 162 is configured to respectively establish a sub-topology table corresponding to the one or more first type controllers according to the received topology information; the second establishing subunit 164 is connected to the first establishing subunit 162. And being set to establish a total topology table of network devices in the second type controller control domain according to the established sub-topology table.
  • FIG. 17 is a structural block diagram of a second processing unit 156 in a device processing apparatus according to an embodiment of the present invention. As shown in FIG. 17, the second processing unit 156 includes a first determining subunit 172, a second determining subunit 174, and a lower Hair unit 176. The second processing unit 156 will be described below.
  • the first determining sub-unit 172 is configured to query the total topology table of the second type controller according to the service deployed in the received user configuration request, determine a path from the source node to the target node, and determine the second determining sub-unit 174. Up to the first determining subunit 172, configured to determine, according to the determined path, and the sub-topology table, a first type controller to which one or more nodes on the path belong; the sending subunit 176, connected to the second determining The sub-unit 174 is configured to deliver configuration information to the first type controller to which the determined one or more nodes belong according to the service deployed in the received user configuration request, and perform service deployment.
  • FIG. 18 is a structural block diagram of a controller according to an embodiment of the present invention. As shown in FIG. 18, the controller includes the device processing in the above embodiment. Device 182.
  • Embodiments of the present invention also provide a storage medium.
  • the foregoing storage medium may be configured to store program code for performing the following steps:
  • a controller type of a controller for performing service processing where the controller type includes: a first type controller that controls network devices in a separate domain, and controls one or more first type controllers a second type of controller, the separate domain is a domain obtained by dividing a network architecture of a predetermined network;
  • the service of the predetermined network is processed according to the determined controller type.
  • the storage medium is further arranged to store program code for performing the following steps:
  • processing the service of the predetermined network according to the determined controller type includes:
  • the original topology information of the network device in the control domain of the first type is collected by the southbound interface, where the original topology information includes the connection information between the network devices in the domain of the first type controller;
  • the storage medium is further arranged to store program code for performing the following steps:
  • the topology information of the network device in the control domain of the first type controller is determined according to the collected original topology information, including:
  • connection information after the information of the intermediate node is removed is saved, and the topology information of the network device in the control domain of the first type controller is obtained.
  • the storage medium is further arranged to store program code for performing the following steps:
  • Processing the service of the predetermined network according to the determined topology information includes:
  • S2 Perform service deployment according to the received service deployment information and topology information.
  • the storage medium is further arranged to store program code for performing the following steps:
  • processing the service of the predetermined network according to the determined controller type includes:
  • S3 Process the service of the predetermined network according to the total topology information.
  • the storage medium is further arranged to store program code for performing the following steps:
  • the total topology information of the network device in the control domain of the second type controller is determined according to the received topology information, including:
  • S1 according to the received topology information, respectively establish a sub-topology table corresponding to one or more first type controllers;
  • the storage medium is further arranged to store program code for performing the following steps:
  • processing the services of the predetermined network includes:
  • the foregoing storage medium may include, but not limited to, a USB flash drive, a Read-Only Memory (ROM), a Random Access Memory (RAM), a mobile hard disk, and a magnetic memory.
  • ROM Read-Only Memory
  • RAM Random Access Memory
  • a mobile hard disk e.g., a hard disk
  • magnetic memory e.g., a hard disk
  • the processor executes, according to the stored program code in the storage medium, the controller type of the controller for performing the service processing, where the controller type includes: the network device in the separate domain a first type controller for controlling, a second type controller for controlling one or more first type controllers, and a separate domain is a domain obtained by dividing a network architecture of a predetermined network; according to the determined controller type, The business of the predetermined network is processed.
  • the processor executes according to the stored program code in the storage medium: in a case where the controller for performing the service processing is the first type controller, according to the determined controller type,
  • the processing of the service of the predetermined network includes: collecting the original topology information of the network device in the control domain of the first type by using the southbound interface, where the original topology information includes the connection information between the network devices in the domain of the first type controller;
  • the original topology information determines the topology information of the network device in the first type controller control domain; and processes the service of the predetermined network according to the determined topology information.
  • the processor performs, according to the stored program code in the storage medium, determining, according to the collected original topology information, the topology information of the network device in the control domain of the first type controller, including: removing the connection information.
  • the intermediate node information is saved; the connection information after the information of the intermediate node is removed is saved, and the topology information of the network device in the control domain of the first type controller is obtained.
  • the processor performs, according to the stored program code in the storage medium, processing the service of the predetermined network according to the determined topology information, including: receiving the second type controller to which the first type controller belongs Service deployment information; service deployment based on received service deployment information and topology information.
  • the processor executes according to the stored program code in the storage medium: in a case where the controller for performing the service processing is the second type controller, according to the determined controller type,
  • the processing of the service of the predetermined network includes: receiving topology information of the network device in the corresponding control domain reported by the one or more first type controllers, where the received topology information includes one or more networks of the first type controller corresponding to the control domain
  • the connection information between the devices is determined according to the received topology information, and the total topology information of the network devices in the control domain of the second type controller is determined; and the services of the predetermined network are processed according to the total topology information.
  • the processor performs, according to the stored program code in the storage medium, determining, according to the received topology information, that the total topology information of the network device in the control domain of the second type controller comprises: according to the received The topology information is respectively configured to establish a sub-topology table corresponding to one or more first type controllers; and according to the established sub-topology table, a total topology table of network devices in the second type controller control domain is established.
  • the processor performs, according to the stored program code in the storage medium, processing, according to the total topology information, the service of the predetermined network, according to the service deployed in the received user configuration request, querying the first a total topology table of the second type controller, determining a path from the source node to the target node; determining, according to the determined path and the sub-topology table, a first type of controller to which one or more nodes on the path belong; according to the received
  • the service deployed in the user configuration request delivers configuration information to the first type of controller to which the determined one or more nodes belong to perform service deployment.
  • modules or steps of the present invention described above can be implemented by a general-purpose computing device that can be centralized on a single computing device or distributed across a network of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein. Perform the steps shown or described, or separate them into individual integrated circuit modules, or multiple of them Blocks or steps are made in a single integrated circuit module. Thus, the invention is not limited to any specific combination of hardware and software.
  • the controller is used to hierarchically manage the network: the first type controller is used to control the individual domain, and the second type controller is used to control multiple domains.
  • a type of controller performs control to control multiple domains and processes services in the network according to the type of the controller. Therefore, the problem of high complexity of network management and maintenance and service deployment of the carrier in the related technologies can be solved. Reduce the complexity of network management maintenance and business deployment.

Landscapes

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

Abstract

La présente invention concerne un procédé, un dispositif et un contrôleur de gestion d'appareil. Le procédé consiste : à déterminer un type de contrôleur d'un contrôleur exécutant un processus de service, le type de contrôleur comprenant un premier type de contrôleurs commandant un appareil de réseau dans un seul domaine, et un second type de contrôleurs commandant un ou plusieurs premiers types de contrôleurs, et le domaine unique étant un domaine obtenu en divisant une structure de réseau d'un réseau préconfiguré ; et à traiter, en fonction du type déterminé de contrôleur, un service du réseau préconfiguré. Le mode de réalisation de l'invention résout le problème de l'état de la technique d'une gestion de réseau très complexe, d'entretien, et d'un déploiement de service exploité par un opérateur de réseau, ce qui permet d'arriver à l'objectif de réduire la complexité de la gestion, de la maintenance et du déploiement de service du réseau.
PCT/CN2017/076492 2016-05-31 2017-03-13 Procédé, dispositif et contrôleur de gestion d'appareil WO2017206565A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610378527.7A CN107453887A (zh) 2016-05-31 2016-05-31 设备处理方法、装置及控制器
CN201610378527.7 2016-05-31

Publications (1)

Publication Number Publication Date
WO2017206565A1 true WO2017206565A1 (fr) 2017-12-07

Family

ID=60478453

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/076492 WO2017206565A1 (fr) 2016-05-31 2017-03-13 Procédé, dispositif et contrôleur de gestion d'appareil

Country Status (2)

Country Link
CN (1) CN107453887A (fr)
WO (1) WO2017206565A1 (fr)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113778620B (zh) * 2021-08-12 2024-07-09 桂林电子科技大学 基于多sdn控制器与软硬件协同的大规模集群存储系统架构
CN115297157A (zh) * 2022-08-01 2022-11-04 中国电信股份有限公司 业务处理方法、装置、系统、介质及电子设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130333029A1 (en) * 2012-06-11 2013-12-12 Radware, Ltd. Techniques for traffic diversion in software defined networks for mitigating denial of service attacks
CN104065585A (zh) * 2014-07-16 2014-09-24 福州大学 一种在软件定义网络中动态调整控制器负载的方法
CN105099995A (zh) * 2014-04-29 2015-11-25 华为技术有限公司 Sdn网络系统、控制器及控制方法
CN105337904A (zh) * 2014-08-05 2016-02-17 杭州华三通信技术有限公司 控制器集群的升级方法及装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130333029A1 (en) * 2012-06-11 2013-12-12 Radware, Ltd. Techniques for traffic diversion in software defined networks for mitigating denial of service attacks
CN105099995A (zh) * 2014-04-29 2015-11-25 华为技术有限公司 Sdn网络系统、控制器及控制方法
CN104065585A (zh) * 2014-07-16 2014-09-24 福州大学 一种在软件定义网络中动态调整控制器负载的方法
CN105337904A (zh) * 2014-08-05 2016-02-17 杭州华三通信技术有限公司 控制器集群的升级方法及装置

Also Published As

Publication number Publication date
CN107453887A (zh) 2017-12-08

Similar Documents

Publication Publication Date Title
US11368862B2 (en) Point-to-multipoint or multipoint-to-multipoint mesh self-organized network over WIGIG standards with new MAC layer
US10757008B2 (en) Flow specification protocol-based communications method, device, and system
CN105577502B (zh) 业务传送方法及装置
CN109660442B (zh) Overlay网络中组播复制的方法及装置
CN107634842A (zh) 网络拓扑发现方法及装置
CN111130980B (zh) 用于实现组合虚拟专用网vpn的方法与装置
CN107733795B (zh) 以太网虚拟私有网络evpn与公网互通方法及其装置
US10708083B2 (en) Traffic engineering service mapping
CN107592270A (zh) FlowSpec消息的处理方法和装置以及系统
CN107959611B (zh) 一种转发报文的方法，装置及系统
CN107800623A (zh) 异构网络通信方法和系统以及sdn控制器
US11716250B2 (en) Network scale emulator
WO2017206565A1 (fr) Procédé, dispositif et contrôleur de gestion d'appareil
CN111682968B (zh) 一种通信设备入网管理方法及系统
US20190334814A1 (en) Path establishment method and device, and network node
US11824763B2 (en) Filtering topologies for path computation in massively scaled networks
CN108173771B (zh) 一种通信设备的管理方法、装置及系统
Bano et al. A comparative analysis of hybrid routing schemes for SDN based wireless mesh networks
CN107295038A (zh) 一种建立接口组的方法及装置
US11252085B2 (en) Link resource transmission method and apparatus
CN109688062A (zh) 一种路由方法和路由设备
CN105991436B (zh) 端到端业务的传输处理方法及装置

Legal Events

Date Code Title Description
NENP Non-entry into the national phase

Ref country code: DE

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

Ref document number: 17805510

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 17805510

Country of ref document: EP

Kind code of ref document: A1