CN107809422B - Interface compatible method and device for decoupling interface differentiation - Google Patents
Interface compatible method and device for decoupling interface differentiation Download PDFInfo
- Publication number
- CN107809422B CN107809422B CN201710968532.8A CN201710968532A CN107809422B CN 107809422 B CN107809422 B CN 107809422B CN 201710968532 A CN201710968532 A CN 201710968532A CN 107809422 B CN107809422 B CN 107809422B
- Authority
- CN
- China
- Prior art keywords
- entity
- information
- interface
- function
- managed
- Prior art date
- Legal status (The legal status 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 status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/24—Negotiation of communication capabilities
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q1/00—Details of selecting apparatus or arrangements
- H04Q1/02—Constructional details
- H04Q1/028—Subscriber network interface devices
Abstract
The invention discloses an interface compatible method and device for decoupling interface differentiation. When the management and control entity operates/acts the managed entity according to the functions, the functions of the managed entity generate the operations/acts and parameters, interface pipeline information corresponding to the functions is read, and information interaction is carried out according to the interface pipeline information, so that the managed entity is butted, operated/acted by the management and control entity. According to the invention, the compatibility of the docking modes of the control entity and the controlled entity can be better realized by reading the docking mode of the controlled entity and carrying out information interaction according to the docking mode, and the technical problem that different docking modes cannot be compatible between the devices in the prior art is solved.
Description
Technical Field
The invention relates to the technical field of communication, in particular to an interface compatible method and device for decoupling interface differentiation.
Background
Software Defined Networking (SDN) is gradually accepted by device manufacturers and Network architecture service providers as a Network architecture, wherein the SDN mainly has a core idea of managing Network hardware through centralized Software to implement programmability, and separating a control function and a forwarding function of the Network hardware.
Further, after the control function and the forwarding function of the network hardware are separated, physical hardware, such as a controller, may be separately designed and manufactured for the control function, or physical hardware, such as a switch and a router for forwarding information, may be separately designed and manufactured for the forwarding function. Of course, for the control function, it is not limited to only use the controller, but also can construct a configuration/management/operation and maintenance operation system for implementing data control, which can be called as a management and control entity; for the forwarding function, it is not limited to only use switches and routers, and they are collectively referred to as managed entities.
However, in an architecture formed by a control entity and a controlled entity, there may be differences between an interface protocol and an information model between the control entity and the controlled entity, even though a standard protocol often has custom items of different manufacturers/different models, and the above differences also cause a compatibility problem when the control entity and the controlled entity are docked.
The existing control entity and the controlled entity have the following butt joint modes:
(1) the vertical chimney type is in butt joint with the self, so that the butt joint problem of equipment of multiple manufacturers/models does not exist basically, but the butt joint of different models and different forms is not considered;
(2) the method comprises the following steps of a scene customization mode, wherein a docking mode (an interface protocol/an information model/a self-defined item and the like) in a management and control entity is customized according to the application scene requirement, but the project needs to spend a large amount of work when the project is realized by landing;
(3) and (3) butting the branch manufacturers with the models: the manufacturers/models with the same butt joint mode are operated by one control entity or a control entity cluster, but the resources cannot be globally scheduled because the butt joint modes are distinguished to realize respective management, so that the complexity and the cooperation difficulty of the control entity are increased.
Regarding the docking mode, the existing devices have the technical problem that different docking modes cannot be compatible. Meanwhile, no docking mode can better realize the docking of multiple manufacturers/models simultaneously, and has the characteristics of less workload, lower system complexity and the like.
The above is only for the purpose of assisting understanding of the technical aspects of the present invention, and does not represent an admission that the above is prior art.
Disclosure of Invention
The invention mainly aims to provide an interface compatible method and device for decoupling interface differentiation, and aims to solve the problem that different docking modes cannot be compatible between devices in the prior art.
In order to achieve the above object, the present invention provides an interface compatible method for decoupling interface differentiation, comprising:
when a control entity operates/acts a controlled entity according to a function, the control entity enables the function of the controlled entity to generate the operation/action and parameters;
reading interface pipeline information corresponding to the function;
and carrying out information interaction according to the interface pipeline information so as to realize the butt joint and operation/action of the managed entity by the management and control entity.
Preferably, the interface pipeline information at least comprises an interface protocol, an information model and a self-defining item, wherein the self-defining item is an item different from a preset general standard protocol/model;
correspondingly, the performing information interaction according to the interface pipeline information to implement the interfacing, operating/acting of the managed entity by the management and control entity specifically includes:
carrying out protocol configuration according to the interface protocol, taking the configured interface protocol as a current interface protocol, and establishing data corresponding to a data channel and an interaction/interaction information model of the managed entity according to the current interface protocol;
arranging information according to the information model and the self-defining item, and taking the arranged information as interactive information.
Preferably, the functions include at least one of control functions, configuration, management, operation and maintenance operation functions.
Preferably, when the managing entity operates/acts the managed entity according to the function, the method for generating the operation/action and the parameter by the function of the managed entity includes:
when a control entity controls a controlled entity according to a control function, the control function of the controlled entity generates operation/action and parameters; and/or
When configuring a managed entity according to a configuration function, a management and control entity enables the configuration function of the managed entity to generate operation/action and parameters; and/or
When a management entity manages a managed entity according to a management function, the management function of the managed entity generates operation/action and parameters; and/or
When the management control entity performs operation and maintenance operation on the managed entity according to the operation and maintenance operation function, the operation and maintenance operation function of the managed entity generates operation/action and parameters.
Preferably, the reading of the interface pipe information corresponding to the function specifically includes:
and reading interface pipeline information corresponding to the function from a related database of the managed entity.
In addition, to achieve the above object, the present invention further provides an interface compatible device for decoupling interface differentiation, the device comprising: the system comprises an entity operation module, an interface information determination module and an interactive information arrangement module;
the entity operation module is used for enabling the function of the managed entity to generate operation/action and parameters when the managed entity is operated/acted according to the function;
the interface information determining module is used for reading the interface pipeline information corresponding to the function;
and the interaction information arranging module is used for carrying out information interaction according to the interface pipeline information so as to realize the butt joint of the management and control entity and the operation/action of the managed entity.
Preferably, the interface pipeline information at least comprises an interface protocol, an information model and a self-defining item, wherein the self-defining item is an item different from a preset general standard protocol/model;
the interaction information arranging module is further used for carrying out protocol configuration according to the interface protocol, taking the configured interface protocol as a current interface protocol, and establishing data corresponding to a data channel and an interaction/interaction information model of the controlled entity according to the current interface protocol;
the interactive information arranging module is also used for arranging information according to the information model and the self-defining item, and the arranged information is used as interactive information.
Preferably, the functions include at least one of control functions, configuration, management, operation and maintenance operation functions.
Preferably, the entity operation module is further configured to, when controlling a controlled entity according to a control function, enable the control function of the controlled entity to generate an operation/action and a parameter;
and/or
The entity operation module is further used for enabling the configuration function of the managed entity to generate operation/action and parameters when the managed entity is configured according to the configuration function;
and/or
The entity operation module is further used for enabling the management function of the managed entity to generate operation/action and parameters when the managed entity is managed according to the management function;
and/or
The entity operation module is further configured to enable the operation and maintenance operation function of the managed entity to generate operations/actions and parameters when the managed entity is operated and maintained according to the operation and maintenance operation function.
Preferably, the interface information determining module is further configured to read interface pipeline information corresponding to the function from a relevant database of the managed entity.
According to the invention, the compatibility of the docking modes of the control entity and the controlled entity can be better realized by reading the docking mode of the controlled entity and carrying out information interaction according to the docking mode, and the technical problem that different docking modes cannot be compatible between the devices in the prior art is solved. Meanwhile, the butt joint of different types of equipment with manufacturers is realized, large development workload is not required to be consumed, and resources can be globally scheduled.
Drawings
FIG. 1 is a flowchart of a first embodiment of a method for interface compatibility of a decoupled interface differentiation according to the present invention;
FIG. 2 is a flowchart of a second embodiment of a method for interface compatibility with differentiated decoupling interfaces according to the present invention;
FIG. 3 is a flowchart of a third embodiment of a method for interface compatibility of a decoupled interface differentiation according to the present invention;
FIG. 4 is a block diagram of a first embodiment of an interface compatible device for decoupling interface differentiation according to the present invention;
FIG. 5 is a block diagram of a second embodiment of a device compatible with an interface for decoupling differentiation of interfaces according to the present invention;
fig. 6 is a block diagram of a third embodiment of an interface compatible device for decoupling interface differentiation according to the present invention.
The implementation, functional features and advantages of the objects of the present invention will be further explained with reference to the accompanying drawings.
Detailed Description
It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
Referring to fig. 1, fig. 1 is a flowchart illustrating a first embodiment of an interface compatibility method for decoupling interface differentiation according to the present invention.
In this embodiment, the method comprises the steps of:
step S10: when a control entity operates/acts a controlled entity according to a function, the control entity enables the function of the controlled entity to generate the operation/action and parameters;
it can be understood that, the control entity is used as an execution subject, and in the architecture formed by the control entity and the controlled entity, there is a difference between an interface protocol and an information model between the control entity and the controlled entity, and even if the control entity and the controlled entity are both standard protocols, there may be custom items of different manufacturers or different models, and in the process of docking the control entity and the controlled entity, the above-mentioned difference between the control entity and the controlled entity may cause compatibility problems. In order to solve the problem that the control entity and the controlled entity cannot be successfully docked to avoid subsequent information interaction due to the difference of interface protocols, information models, self-defined items and the like between the control entity and the controlled entity, the control entity can determine the docking mode of the control entity by identifying the docking mode of the controlled entity, and the compatibility difference caused by different docking modes is solved. The interface protocol, the information model and the custom item can be collectively referred to as a docking manner.
Step S20: reading interface pipeline information corresponding to the function;
in a specific implementation, when the management and control entity operates/acts the managed entity according to the function, the function of the managed entity generates corresponding operation/action and parameter, and may intercept interface pipe information of the running function, where the interface pipe information is used to describe a docking manner of the managed entity. For example, the interface pipe information may include interface protocols, information models, and custom items, among others. The self-defined item is a difference between an interface Protocol or an information model defined by a manufacturer or a communication technology organization and a general standard Protocol/model, for example, an Internet Gateway Routing Protocol (IGRP) which is a proprietary Protocol of cisco.
Step S30: and carrying out information interaction according to the interface pipeline information so as to realize the butt joint and operation/action of the managed entity by the management and control entity.
It should be understood that, for example, in the currently read interface pipe Information, the interface Protocol is Simple Network Management Protocol (SNMP), the Information model of the router is Management Information Base (MIB), and the self-definition item of the router is blank. Therefore, after knowing that the docking modes include SNMP and MIB, the managed entity pre-stores the specific configuration parameters of the multiple docking modes, determines the corresponding SNMP configuration parameters according to SNMP, determines the corresponding MIB information model parameters according to MIB, and configures the parameters according to SNMP configuration parameters and MIB information model parameters to implement information interaction. At present, the control entity and the controlled entity have the same docking mode, and the control entity and the controlled entity can perform stable and normal communication, so that the docking of the control entity and the controlled entity is realized. Therefore, the management and control entity can be in butt joint with the managed and controlled entity with different butt joint modes through the scheme, and the infrastructure of different manufacturers/models of equipment is deployed in different application scenes without great customized development workload; meanwhile, the resource scheduling method is realized in the same management and control entity or cluster, and the resources can be globally scheduled without respectively carrying out butt joint on the models of different manufacturers, so that the complexity of the management and control entity, the cooperation and the cluster is further reduced.
In this embodiment, the compatibility of the docking manners of the management and control entity and the managed and controlled entity can be better achieved by reading the docking manner of the managed and controlled entity and performing information interaction according to the docking manner, and the technical problem that different docking manners cannot be compatible between the devices in the prior art is solved. Meanwhile, the butt joint of different types of equipment with manufacturers is realized, large development workload is not required to be consumed, and resources can be globally scheduled.
Referring to fig. 2, fig. 2 is a schematic flowchart of a second embodiment of the interface compatibility method for decoupling interface differentiation according to the present invention, and the second embodiment of the interface compatibility method for decoupling interface differentiation according to the present invention is proposed based on the embodiment shown in fig. 1.
In this embodiment, the interface pipeline information at least includes an interface protocol, an information model, and a self-defining item, where the self-defining item is an item different from a preset general standard protocol/model, where the step S30 specifically includes:
step S301: carrying out protocol configuration according to the interface protocol, taking the configured interface protocol as a current interface protocol, and establishing data corresponding to a data channel and an interaction/interaction information model of the managed entity according to the current interface protocol;
it can be understood that after the interface pipeline information corresponding to each function of the managed entity is read, information interaction can be performed according to the interface pipeline information. The interface pipeline information includes an interface Protocol, an information model and a self-defining item, the interface Protocol is a network Protocol for performing device communication corresponding to functions of control, configuration, management, operation and maintenance, and the like, and the interface Protocol commonly includes OpenFlow, Border Gateway Protocol-Link State (BGP-LS), Path Computation Element Protocol (PCEP), SNMP, and the like; an information model, which is an information layout model corresponding to each function, and is commonly a Topology layout standard (TOSCA) model of MIB, command line format, and Cloud application, and the like; and the self-defining item is different from the general standard protocol/model in the interface protocol or the information model defined by the manufacturer or the communication technology organization. Data corresponding to data channels and interactive/interactive information models can be established through corresponding interface protocols in the interface pipeline information.
Step S302: arranging information according to the information model and the self-defining item, and taking the arranged information as interactive information.
It should be understood that interaction information, such as actions/parameters, etc., may also be generated from information models in the interface pipe information and custom item arrangements.
In a specific implementation, if it is determined that the type of the carried interface protocol is a PCEP protocol, protocol configuration may be performed according to corresponding PCEP protocol parameters, so as to establish data corresponding to a data channel and an interaction/interaction information model of the managed entity according to the current interface protocol; if the information model is determined to be the TOSCA model, information arrangement can be carried out according to the corresponding TOSCA model parameters and the information of the self-defining items so as to determine the corresponding interactive information.
Further, in order to facilitate the management and control entity to determine corresponding interface pipe information, the reading of the interface pipe information corresponding to the function specifically includes: and reading interface pipeline information corresponding to the function from a related database of the managed entity.
It is understood that the interface pipeline information read in the actual operation may be stored in the relevant database of the managed entity in advance. For example, if the interface protocol of the current managed entity is the PCEP protocol, the interface pipeline information of the PCEP protocol may be read from the related database, so that the managed entity may more conveniently perform configuration or auto-negotiation of the interface protocol, the information model, and the self-defined item.
In the embodiment, the specific interface protocol, the specific information model and the specific self-defining item are determined according to the interface pipeline information, so that the management and control entity can be more comprehensively compatible with the docking modes in various aspects; meanwhile, the configuration and auto-negotiation of the docking mode can be more efficient by presetting the relevant database in which the configuration parameters such as various interface protocols, information models, custom items and the like are stored.
Referring to fig. 3, fig. 3 is a schematic flowchart of a third embodiment of the interface compatibility method for decoupling interface differentiation according to the present invention, and the third embodiment of the interface compatibility method for decoupling interface differentiation according to the present invention is proposed based on the embodiment shown in fig. 1.
In this embodiment, the functions include at least one of a control function, a configuration function, a management function, and an operation and maintenance operation function, where the step 10 specifically includes:
step S10': when a control entity controls a controlled entity according to a control function, the control function of the controlled entity generates operation/action and parameters; and/or
When configuring a managed entity according to a configuration function, a management and control entity enables the configuration function of the managed entity to generate operation/action and parameters; and/or
When a management entity manages a managed entity according to a management function, the management function of the managed entity generates operation/action and parameters; and/or
When the management control entity performs operation and maintenance operation on the managed entity according to the operation and maintenance operation function, the operation and maintenance operation function of the managed entity generates operation/action and parameters.
It can be understood that in an architecture formed by the management entity and the managed entity, the management entity has multiple functions, and under different functions, such as a control function, a configuration function, a management function, an operation function, and an maintenance function, the management entity and the managed entity have multiple interface protocols and information models, and even if the standard protocols exist, custom items of different manufacturers/different models often exist.
In a specific implementation, the management and control entity may control the managed entity according to a control function, such as controlling and forwarding information of the flow table, optical layer control items (wavelength/switch, etc.), vendor custom options, and the like; the management and control entity may also configure the managed and control entity according to the configuration function, and may configure a working mode, an Internet Protocol (IP) address, an IP address/domain name/name of the connected management and control entity, a port mode (Access/Trunk/Hybrid, etc.), a Virtual Local Area Network (VLAN), a Label operation (stripping/adding/editing, etc.), and the like of the managed and control entity, where the identifier includes a VLAN, a QinQ, a Virtual eXtensible Local Area Network (VXLAN), a Multi-Protocol Label Switching (MPLS), and the like; the management and control entity may manage the managed and controlled entity according to the management function, for example, the management and control entity may interact management information with the connected management and control entity, such as fault alarm, performance statistics, status information, log, security (authentication and authentication), and the like, and common interaction methods are SNMP, Remote network monitoring (RMON), system log (Syslog) protocol, and the like; the management and control entity may also perform operation and maintenance operations on the managed and controlled entity according to the operation and maintenance operation function, for example, the management and control entity may interact with the management and control entity connected to the management and control entity for operation and maintenance operation information, such as system online test, network monitoring, network environment simulation test, high-level abstract intent mapping, and the like.
It is understood that besides the above-mentioned control function, configuration, management, operation and maintenance function, there may be other functions that affect the operation/action performed by the managed entity, so as to affect the operation/action performed by the managed entity and transmit information such as operation/action and parameters.
In this embodiment, by combining each function, information interaction between the management and control entity and the managed entity is realized.
Based on the above embodiments of the method, the embodiment of the interface compatible device with a differentiated decoupling interface of the present invention is provided, and as shown in fig. 4, fig. 4 is a block diagram of a first embodiment of the interface compatible device with a differentiated decoupling interface of the present invention. Wherein the apparatus comprises: the system comprises an entity operation module 10, an interface information determination module 20 and an interaction information arranging module 30;
an entity operation module 10, configured to, when an operation/action is performed on a controlled entity according to a function, enable the function of the controlled entity to generate the operation/action and a parameter;
it can be understood that, the control entity is used as an execution subject, and in the architecture formed by the control entity and the controlled entity, there is a difference between an interface protocol and an information model between the control entity and the controlled entity, and even if the control entity and the controlled entity are both standard protocols, there may be custom items of different manufacturers or different models, and in the process of docking the control entity and the controlled entity, the above-mentioned difference between the control entity and the controlled entity may cause compatibility problems. In order to solve the problem that the control entity and the controlled entity cannot be successfully docked to avoid subsequent information interaction due to the difference of interface protocols, information models, self-defined items and the like between the control entity and the controlled entity, the control entity can determine the docking mode of the control entity by identifying the docking mode of the controlled entity, and the compatibility difference caused by different docking modes is solved. The interface protocol, the information model and the custom item can be collectively referred to as a docking manner.
An interface information determining module 20, configured to read interface pipeline information corresponding to the function;
in a specific implementation, when the entity operation module 10 of the controlling entity operates/acts the controlled entity according to the function, the function of the controlled entity generates corresponding operation/action and parameter, and may intercept the interface pipe information of the running function, where the interface pipe information is used to describe the docking manner of the controlled entity. For example, the interface pipe information may include interface protocols, information models, and custom items, among others. The custom item is the difference between the interface protocol or the information model defined by the manufacturer or the communication technology organization and the general standard protocol/model, such as the private protocol interior gateway routing protocol IGRP of cisco, and the custom item of the protocol is the difference from the standard protocol.
And the interaction information arranging module 30 is configured to perform information interaction according to the interface pipeline information, so as to implement the docking of the management and control entity and the operation/action of the managed entity.
It should be understood that, for example, the interface pipe information currently read by the interface information determination module 20 is an interface Protocol (Simple Network Management Protocol, SNMP), the information model of the router is a Management Information Base (MIB), and the self-definition item of the router is blank. Therefore, after knowing that the docking modes include SNMP and MIB, the managed entity pre-stores the specific configuration parameters of the multiple docking modes, determines the corresponding SNMP configuration parameters according to SNMP, determines the corresponding MIB information model parameters according to MIB, and configures the parameters according to SNMP configuration parameters and MIB information model parameters to implement information interaction. At present, the control entity and the controlled entity have the same docking mode, and the control entity and the controlled entity can perform stable and normal communication, so that the docking of the control entity and the controlled entity is realized.
In this embodiment, the compatibility of the docking manners of the management and control entity and the managed and controlled entity can be better achieved by reading the docking manner of the managed and controlled entity and performing information interaction according to the docking manner, and the technical problem that different docking manners cannot be compatible between the devices in the prior art is solved. Meanwhile, the butt joint of different types of equipment with manufacturers is realized, large development workload is not required to be consumed, and resources can be globally scheduled.
Referring to fig. 5, fig. 5 is a block diagram illustrating a structure of a second embodiment of the interface compatible device with a decoupled interface difference according to the present invention, and the second embodiment of the interface compatible device with a decoupled interface difference according to the present invention is provided based on the embodiment illustrated in fig. 4.
In this embodiment, the interface pipeline information at least includes an interface protocol, an information model, and a self-defining item, where the self-defining item is an item different from a preset general standard protocol/model.
The interaction information arranging module 301 is further configured to perform protocol configuration according to the interface protocol, use the configured interface protocol as a current interface protocol, and establish data corresponding to a data channel and an interaction/interaction information model of the managed and controlled entity according to the current interface protocol;
it can be understood that after the interface pipeline information corresponding to each function of the managed entity is read, information interaction can be performed according to the interface pipeline information. The interface pipeline information comprises an interface protocol, an information model and a self-defining item, wherein the interface protocol is a network protocol for carrying out equipment communication corresponding to the functions of control, configuration, management, operation and maintenance operation and the like, and the interface protocol commonly comprises OpenFlow, a border gateway protocol-link state BGP-LS, a path computation element protocol PCEP, SNMP and the like; the information model is an information layout model corresponding to each function, and is commonly a topology layout standard TOSCA model of MIB, command line format and cloud application, and the like; and the self-defining item is different from the general standard protocol/model in the interface protocol or the information model defined by the manufacturer or the communication technology organization. Data corresponding to data channels and interactive/interactive information models can be established through corresponding interface protocols in the interface pipeline information.
The interaction information arranging module 302 is further configured to arrange information according to the information model and the custom item, and use the arranged information as interaction information.
It should be understood that interaction information, such as actions/parameters, etc., may also be generated from information models in the interface pipe information and custom item arrangements.
In a specific implementation, if it is determined that the type of the carried interface protocol is a PCEP protocol, protocol configuration may be performed according to corresponding PCEP protocol parameters, so as to establish data corresponding to a data channel and an interaction/interaction information model of the managed entity according to the current interface protocol; if the information model is determined to be the TOSCA model, information arrangement can be carried out according to the corresponding TOSCA model parameters and the information of the self-defining items so as to determine the corresponding interactive information.
Further, in order to facilitate the management and control entity to determine the corresponding interface pipe information, the interface information determination module is further configured to read the interface pipe information corresponding to the function from the relevant database of the managed and controlled entity.
It is understood that the interface pipeline information read in the actual operation may be stored in the relevant database of the managed entity in advance. For example, if the interface protocol of the current managed entity is the PCEP protocol, the interface pipeline information of the PCEP protocol may be read from the related database, so that the managed entity may more conveniently perform configuration or auto-negotiation of the interface protocol, the information model, and the self-defined item.
In the embodiment, the specific interface protocol, the specific information model and the specific self-defining item are determined according to the interface pipeline information, so that the management and control entity can be more comprehensively compatible with the docking modes in various aspects; meanwhile, the configuration and auto-negotiation of the docking mode can be more efficient by presetting the relevant database in which the configuration parameters such as various interface protocols, information models, custom items and the like are stored.
Referring to fig. 6, fig. 6 is a block diagram illustrating a structure of a third embodiment of the interface compatible device with a decoupled interface difference according to the present invention, and the third embodiment of the interface compatible device with a decoupled interface difference according to the present invention is provided based on the embodiment illustrated in fig. 4.
In this embodiment, the functions include at least one of control functions, configuration, management, operation and maintenance functions.
The entity operation module 101 is further configured to, when a controlled entity is controlled according to a control function, enable the control function of the controlled entity to generate an operation/action and a parameter;
and/or
The entity operation module 102 is further configured to enable a configuration function of a managed entity to generate an operation/action and a parameter when the managed entity is configured according to the configuration function;
and/or
The entity operation module 103 is further configured to, when a managed entity is managed according to a management function, enable the management function of the managed entity to generate an operation/action and a parameter;
and/or
The entity operation module 104 is further configured to enable the operation and maintenance operation function of the managed entity to generate operations/actions and parameters when the managed entity is operated and maintained according to the operation and maintenance operation function.
It can be understood that in the architecture formed by the management entity and the managed entity, the management entity has multiple functions.
In a specific implementation, the entity operation module 101 of the management and control entity may control the managed entity according to a control function, such as controlling and forwarding a flow table, optical layer control items (wavelength/switch, etc.), factory-defined options, and other information; the entity operation module 102 of the management and control entity may also configure the managed entity according to the configuration function, and may configure a working mode, a network protocol IP address, an IP address/domain name/name of the management and control entity connected to the management and control entity, a port mode (Access/Trunk/Hybrid, etc.), a VLAN (virtual local area network), a tag operation (stripping/adding/editing, etc.), and the like, where the identifier includes VLAN, QinQ, an extensible virtual local area network VXLAN, a multi-protocol tag switching MPLS, and the like; the entity operation module 103 of the management and control entity may manage the managed entity according to the management function, for example, the entity operation module may interact management information with the management and control entity connected to the entity, such as fault alarm, performance statistics, status information, log, security (authentication and authentication), and the like, and the common interaction mode is SNMP, remote network monitoring RMON, system log (Syslog) protocol, and the like; the entity operation module 104 of the management and control entity may also perform operation and maintenance operations on the managed entity according to the operation and maintenance operation function, for example, may interact with the management and control entity connected to the management and control entity for operation and maintenance operation information, such as system online test, network monitoring, network environment simulation test, high-level abstract intent mapping, and the like.
It is understood that besides the above-mentioned control function, configuration, management, operation and maintenance function, there may be other functions that affect the operation/action performed by the managed entity, so as to affect the operation/action performed by the managed entity and transmit information such as operation/action and parameters.
In this embodiment, by combining each function, information interaction between the management and control entity and the managed entity is realized.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or system that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or system. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or system that comprises the element.
The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.
Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal device (such as a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the method according to the embodiments of the present invention.
The above description is only a preferred embodiment of the present invention, and not intended to limit the scope of the present invention, and all modifications of equivalent structures and equivalent processes, which are made by using the contents of the present specification and the accompanying drawings, or directly or indirectly applied to other related technical fields, are included in the scope of the present invention.
Claims (8)
1. A method of interface compatibility for decoupling interface differentiation, the method comprising the steps of:
when a control entity operates/acts a controlled entity according to a function, the control entity enables the function of the controlled entity to generate the operation/action and parameters;
reading interface pipeline information corresponding to the function;
performing information interaction according to the interface pipeline information to realize the butting of the control entity and the operation/action of the controlled entity;
the interface pipeline information at least comprises an interface protocol, an information model and a self-defining item, wherein the self-defining item is an item which is different from a preset general standard protocol/model;
correspondingly, the performing information interaction according to the interface pipeline information to implement the interfacing, operating/acting of the managed entity by the management and control entity specifically includes:
carrying out protocol configuration according to the interface protocol, taking the configured interface protocol as a current interface protocol, and establishing data corresponding to a data channel and an interaction/interaction information model of the managed entity according to the current interface protocol;
arranging information according to the information model and the self-defining item, and taking the arranged information as interactive information.
2. The method of claim 1, wherein the functions comprise at least one of control functions, configuration, management, operation and maintenance operation functions.
3. The method as claimed in claim 2, wherein the controlling entity, when operating/acting on a controlled entity according to a function, causes the function of the controlled entity to generate an operation/action and a parameter, specifically comprising:
when a control entity controls a controlled entity according to a control function, the control function of the controlled entity generates operation/action and parameters; and/or
When configuring a managed entity according to a configuration function, a management and control entity enables the configuration function of the managed entity to generate operation/action and parameters; and/or
When a management entity manages a managed entity according to a management function, the management function of the managed entity generates operation/action and parameters; and/or
When the management control entity performs operation and maintenance operation on the managed entity according to the operation and maintenance operation function, the operation and maintenance operation function of the managed entity generates operation/action and parameters.
4. The method according to any one of claims 1 to 3, wherein the reading of the interface pipe information corresponding to the function specifically includes:
and reading interface pipeline information corresponding to the function from a related database of the managed entity.
5. An interface compatible device for decoupling interface differentiation, the device comprising at least: the system comprises an entity operation module, an interface information determination module and an interactive information arrangement module;
the entity operation module is used for enabling the function of the managed entity to generate operation/action and parameters when the managed entity is operated/acted according to the function;
the interface information determining module is used for reading the interface pipeline information corresponding to the function;
the interaction information arrangement module is used for carrying out information interaction according to the interface pipeline information so as to realize the butt joint of the management and control entity and the operation/action of the managed entity;
the interface pipeline information at least comprises an interface protocol, an information model and a self-defining item, wherein the self-defining item is an item which is different from a preset general standard protocol/model;
the interaction information arranging module is further used for carrying out protocol configuration according to the interface protocol, taking the configured interface protocol as a current interface protocol, and establishing data corresponding to a data channel and an interaction/interaction information model of the controlled entity according to the current interface protocol;
the interactive information arranging module is also used for arranging information according to the information model and the self-defining item, and the arranged information is used as interactive information.
6. The apparatus of claim 5, wherein the functions comprise at least one of control functions, configuration, management, operation and maintenance operation functions.
7. The apparatus of claim 6,
the entity operation module is further used for enabling the control function of the controlled entity to generate operation/action and parameters when the controlled entity is controlled according to the control function;
and/or
The entity operation module is further used for enabling the configuration function of the managed entity to generate operation/action and parameters when the managed entity is configured according to the configuration function;
and/or
The entity operation module is further used for enabling the management function of the managed entity to generate operation/action and parameters when the managed entity is managed according to the management function;
and/or
The entity operation module is further configured to enable the operation and maintenance operation function of the managed entity to generate operations/actions and parameters when the managed entity is operated and maintained according to the operation and maintenance operation function.
8. The apparatus according to any one of claims 5 to 7, wherein the interface information determining module is further configured to read interface pipe information corresponding to the function from a related database of the managed entity.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710968532.8A CN107809422B (en) | 2017-10-16 | 2017-10-16 | Interface compatible method and device for decoupling interface differentiation |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710968532.8A CN107809422B (en) | 2017-10-16 | 2017-10-16 | Interface compatible method and device for decoupling interface differentiation |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107809422A CN107809422A (en) | 2018-03-16 |
| CN107809422B true CN107809422B (en) | 2020-10-02 |
Family
ID=61585048
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710968532.8A Active CN107809422B (en) | 2017-10-16 | 2017-10-16 | Interface compatible method and device for decoupling interface differentiation |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107809422B (en) |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102158356A (en) * | 2011-03-24 | 2011-08-17 | 无锡路通光电技术有限公司 | Integrated network management agent device for network elements in hybrid fiber coax (HFC) heterogeneous network |
| CN103338163B (en) * | 2013-07-16 | 2016-03-23 | 清华大学 | Support the software defined network controller of dynamic elasticity scheduling of resource |
| CN104901824A (en) * | 2014-03-04 | 2015-09-09 | 中兴通讯股份有限公司 | Method and device for configuring Openflow auxiliary channel |
| US10171336B2 (en) * | 2015-12-16 | 2019-01-01 | Telefonaktiebolaget Lm Ericsson (Publ) | Openflow configured horizontally split hybrid SDN nodes |
| CN106936857B (en) * | 2015-12-29 | 2020-05-19 | 中国电信股份有限公司 | Connection management method of hybrid cloud, SDN controller and hybrid cloud system |
| CN105808365A (en) * | 2016-03-22 | 2016-07-27 | 深圳市宁远科技股份有限公司 | HIS (Hospital Information System) interface calling method and HIS interface configuration method |
-
2017
- 2017-10-16 CN CN201710968532.8A patent/CN107809422B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN107809422A (en) | 2018-03-16 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP2731304B1 (en) | Method, switch and system for transmitting an establish connection request | |
| CN107147509B (en) | Virtual private network service implementation method, device and communication system | |
| US8782210B2 (en) | Network management control program, network management control device, and network management control method | |
| CN103997414A (en) | Configuration information generation method and network control unit | |
| CN106789637B (en) | Cross-domain service intercommunication path establishment method, controller and system | |
| Devlic et al. | A use-case based analysis of network management functions in the ONF SDN model | |
| US11736410B1 (en) | Synchronizing device resources for element management systems | |
| CN112104473A (en) | Programmable configuration templates in a graphics-based intent controller | |
| US20220394010A1 (en) | Method, Apparatus, and System for Sending Control Request Based on Key Value Configuration | |
| Turull et al. | libNetVirt: the network virtualization library | |
| Bahnasse et al. | Smart hybrid SDN approach for MPLS VPN management on digital environment | |
| CN107733727B (en) | Zero configuration method, device and equipment | |
| WO2017000858A1 (en) | Network element device and method for opening data communication network | |
| US9794146B2 (en) | Methods and systems for a monitoring device to execute commands on an attached switch | |
| EP3952212B1 (en) | Using a programmable resource dependency mathematical model to perform root cause analysis | |
| CN107809422B (en) | Interface compatible method and device for decoupling interface differentiation | |
| Matias et al. | The EHU-OEF: an OpenFlow-based layer-2 experimental facility | |
| Farias et al. | Integrating legacy forwarding environment to OpenFlow/SDN control plane | |
| Devlic et al. | Carrier-grade network management extensions to the SDN framework | |
| CN112738250B (en) | Hybrid cloud interconnection special line management system | |
| CN107104811B (en) | Network function implementation method and control device | |
| EP3817341B1 (en) | Bulk configuration of devices behind a network address translation device | |
| CN111416732B (en) | Method and device for automatically configuring service for capacity expansion of network equipment in SDN | |
| Nguyen et al. | S-MANAGE protocol for software-defined IoT | |
| KR102385707B1 (en) | SDN network system by a host abstraction and implemented method therefor |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |