WO2023005543A1 - 一种查询方法、装置及设备 - Google Patents

一种查询方法、装置及设备 Download PDF

Info

Publication number
WO2023005543A1
WO2023005543A1 PCT/CN2022/101370 CN2022101370W WO2023005543A1 WO 2023005543 A1 WO2023005543 A1 WO 2023005543A1 CN 2022101370 W CN2022101370 W CN 2022101370W WO 2023005543 A1 WO2023005543 A1 WO 2023005543A1
Authority
WO
WIPO (PCT)
Prior art keywords
query
message
node
data node
network
Prior art date
Application number
PCT/CN2022/101370
Other languages
English (en)
French (fr)
Inventor
冯冲
任翔
马秋方
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2023005543A1 publication Critical patent/WO2023005543A1/zh

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/02Standardisation; Integration
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/02Standardisation; Integration
    • H04L41/0213Standardised network management protocols, e.g. simple network management protocol [SNMP]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/02Standardisation; Integration
    • H04L41/0246Exchanging or transporting network management information using the Internet; Embedding network management web servers in network elements; Web-services-based protocols
    • H04L41/0266Exchanging or transporting network management information using the Internet; Embedding network management web servers in network elements; Web-services-based protocols using meta-data, objects or commands for formatting management information, e.g. using eXtensible markup language [XML]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/133Protocols for remote procedure calls [RPC]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W8/00Network data management
    • H04W8/02Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks

Definitions

  • the present application relates to the technical field of communications, and in particular to a query method, device and equipment.
  • Network Configuration Protocol (Network Configuration Protocol, NETCONF) is a network management protocol based on the modeling language of the next generation (yet another next generation, YANG), providing a set of mechanisms for configuring and managing network devices, users can Using this mechanism to add, modify, delete the configuration of network equipment, obtain the configuration and status information of network equipment has been widely used in network management systems.
  • NETCONF adopts the structure of client (Client) and server (Server), and uses the mechanism based on remote procedure call (Remote Procedure Call, RPC) to realize the communication between client and server.
  • YANG is used to design operable configuration data, state data modeling, RPC operation instructions and notification mechanism modeling for the NETCONF protocol.
  • the network management device as Clint can deliver the network configuration modeled with YANG and obtain the Network devices use YANG-modeled configuration and status information to implement device management.
  • the YANG model is implemented based on Extensible Markup Language (XML), and is a file in XML format. Therefore, a YANG model file can define a YANG module, and a YANG module can include multiple nodes, and these nodes can form a tree structure. Among them, the data modeled by YANG can be instantiated, and the data nodes are nodes that can be instantiated in the tree structure.
  • the network management equipment manages the network equipment, it usually manages the data nodes of the YANG model encoded by XML.
  • the support of data nodes in the YANG model of the network equipment may change, resulting in the inability of the network management equipment to manage the network equipment well.
  • the embodiment of the present application provides a query method, device and equipment, so as to achieve the purpose of the network management equipment obtaining the support status of the data nodes by the network equipment.
  • a query method is provided, which can be applied to a network management device deployed with a NETCONF client.
  • the method includes the following steps: the network management device generates a first query message, the first query message includes a first query condition, and the first query condition is used to obtain node identifiers and first indication information of data nodes in the network equipment.
  • the node identifier can be used to identify a data node in the first YANG model in the network device, for example, it can be XML Path (XML Path, XPath) information of the data node.
  • the first indication information may be used to indicate the support of the network device to the data node indicated by the node identifier.
  • the network management device can send the first query message to the network device, so that the network device can query its support for the data node indicated by the node identifier according to the first query message, and obtain the first indication information.
  • the network device may carry the first indication information and the node identifier in the first response message and send it to the network management device, so that the network management device obtains the first indication information through the first response message. In this way, the network management device inquires the support status of the data node from the network device through the query message, so that the network management device can know the change of the support status of the data node in time, and better manage the network device.
  • the network management device may generate the first query message in the following three possible implementation manners:
  • Implementation way 1 In response to generating the second RPC message, the network management device generates the first query message. Wherein, the second second RPC message is used to configure the data node. That is, before configuring the data nodes in the YANG model of the network device, the network management device may first generate a first query message, and use the first query message to query the support of the network device for the data node to be configured.
  • the network management device may send the second RPC message to the network device. In this way, before configuring the data nodes, first query the support status of the data nodes of the network device, which can avoid configuration failures.
  • Implementation manner 2 In response to receiving the second RPC response message, the network management device generates a first query message.
  • the second RPC response message may be used to indicate that the network management device fails to configure the data node. That is, before receiving the second RPC response message, the RPC message sent by the network management device to the network device is used to configure the data node. However, the network device cannot configure the data node according to the RPC message, and sends a second RPC response message to the network management device to notify the network management device that configuration of the data node fails. Then, in order to query the reason of the configuration failure, the network management device may generate a first query message, and use the first query message to query the support of the network device for the data node.
  • the first response message received by the network management device may include the node identifier of the replacement node of the data node.
  • the replacement node is a new data node used to replace the original data node. Based on this, it can be determined that the data node is replaced by a replacement node, which causes the network management device to fail to configure the data node. Therefore, the network management device may generate a third RPC message according to the node identifier of the replacement node and send it to the network device, so as to configure the replacement node through the third RPC message.
  • Implementation manner three in response to receiving the feedback information, the network management device generates a first query message.
  • the feedback information is used to indicate that a license (license) has been purchased or activated, and the purchased or activated license corresponds to the data node corresponding to the node identifier included in the first query message.
  • the purchase or activation of the license may lead to changes in the functions of the network equipment, which in turn may lead to changes in the support of the network equipment for data nodes. Therefore, after receiving the feedback message, the network management device may generate first query information according to the node identifier of the data node corresponding to the license, so as to query the support status of the data node by the network device after the license is activated or purchased.
  • the first query condition in the first query message may include the following four possible implementations:
  • the first query condition includes the node identifier of the data node, and correspondingly, the first query message is used to query the first indication information according to the node identifier of the data node.
  • the network management device wants to inquire about the support of the network device for a specific data node, the network management device can carry the node identifier of the data node in the first query message, so that the network device can obtain the information about the data node according to the node identifier of the data node.
  • the first query message may include an operation instruction, and the operation instruction may be an existing operation instruction of NETCONF, or an operation instruction customized by a technician.
  • the first query condition includes a first query instruction.
  • the first query instruction is used to query the support situation from the YANG Library (YANG Library) of the network device, and the YANG Library includes the node identification of the data node and the first indication information.
  • the network device can store support for data nodes in multiple YANG models (including the first YANG model) in the YANG Library.
  • the network management device can generate the first query message according to the storage location in the YANG Library according to the support of the data node.
  • the network management device can also generate the first query message according to the model set (module set) information or model (module) information to which the support situation of the data node belongs.
  • the first query quality may be an existing operation command of NETCONF, such as a get command, a get-data command, or a get-config command. .
  • Implementation mode 3 the first query condition includes a second query instruction, the second query instruction is used to query the structure (schema) information of the first YAGN model, and the schema includes the node identifier of the data node and the first indication information.
  • the network device may store the support status of data nodes in multiple YANG models (including the first YANG model) in the schema model.
  • the network management device may generate the first query message including the second query instruction, so as to query the support of the network device for the data node from the schema model.
  • the first query condition includes a file name
  • the first query message is used to obtain a node identifier and first indication information of a data node from a file corresponding to the file name.
  • the network device may store the node identifier and the first indication information of the data node in a file. Then the network management device may generate the first query message according to the file name storing the node identifier and the first indication information.
  • the first query message may be an RPC message, also called the first RPC message.
  • the first query message may also be used to establish a subscription between the network device and the network management device.
  • the first response message may be an RPC response (RPC Reply) message, also known as the first RPC response message.
  • the network management device may also query the support status of the network device for the YANG model. Specifically, the network management device may generate a second query message including the second query condition, and the second query condition may include the identifier of the second YANG model. Next, the network management device may send a second query message to the network device, and receive a second response message from the network device. The second response message is generated by the network device according to the second query message, and includes second indication information for indicating the support of the second YANG model by the network device.
  • the node identifier of the data node includes path information of the data node in the structure tree corresponding to the first YANG model.
  • the network management device may include a software-defined network (Software Defined Network, SDN) controller.
  • SDN Software Defined Network
  • a query method which can be applied to a network device deployed with a NETCONF client.
  • the method includes the following steps: the network device receives the first query message sent by the network management device, and the first query message includes the first query condition. Then, according to the first query condition, the network device can query the node identifier of the data node in the first YANG model corresponding to the first query condition from its own storage space, and indicate the support of the network device for the data node The first indication of the . Next, the network device may generate a first response message according to the node identifier of the data node and the first indication information, and send the first response message to the network management device.
  • the network device can determine the corresponding data node from its own first YANG model according to the first query condition carried in the first query message, and according to the data node Generate a first response message based on the node identification and support status of the node.
  • the network management device inquires the support status of the data node from the network device through the query message, so that the network management device can know the change of the support status of the data node in time, and better manage the network device.
  • the first query condition in the first query message may include the following four possible implementations:
  • the first query condition includes the node identifier of the data node, and correspondingly, the first query message is used to query the first indication information according to the node identifier of the data node.
  • the first query message may include an operation instruction, and the operation instruction may be an existing operation instruction of NETCONF, or an operation instruction customized by a technician.
  • the network device may determine the node identifier of the data node according to the first query condition of the first query message, and then obtain the first indication information from the first YANG model.
  • the first query condition includes a first query instruction.
  • the first query instruction is used to query the support situation from the YANG library (YANG Library) of the network device.
  • YANG Library includes the node identification of the data node and the first indication information.
  • the network device may store the support status of each data node in the first YANG model in the YANG Library.
  • the network device can determine the storage location in the YANG Library of the support situation of the data node queried by the network management device according to the first query instruction, and then obtain the first indication information from the YANG Library, And generate the first response message.
  • Implementation mode 3 the first query condition includes a second query instruction, the second query instruction is used to query the structure (schema) information of the first YAGN model, and the schema includes the node identifier of the data node and the first indication information.
  • the network device may store the support status of data nodes in multiple YANG models (including the first YANG model) in the schema model.
  • the network device may obtain the node identifier of the data node and the first indication information from the schema model according to the second query instruction, so as to generate the first response message.
  • the first query condition includes a file name
  • the first query message is used to obtain a node identifier and first indication information of a data node from a file corresponding to the file name.
  • the network device may store the node identifier and the first indication information of the data node in a file. After receiving the first query message, the node identifier and the first indication information of the data node may be obtained from the file corresponding to the file name according to the first query condition in the first query message.
  • the first query message may be an RPC message, also called the first RPC message.
  • the first query message may also be used to establish a subscription between the network device and the network management device.
  • the first response message may be an RPC response (RPC Reply) message, also known as the first RPC response message.
  • the network management device may also query the network device for support of the YANG model. Specifically, the network device may receive a second query message sent by the network management device, where the second query message includes a second query condition, and the second query condition includes an identifier of the second YANG model. After receiving the second query message, the network device can obtain the support of the network device for the second YANG model according to the second query condition, and obtain the second indication information, and the second indication information is used to indicate the support of the network device for the second YANG model Support situation. Next, the network device may generate a second response message including the second indication information according to the second indication information and send it to the network management device.
  • the first response message also includes the node identifier of the replacement node of the data node, which is used to notify the network management device of unsupported data Which data node the node is replaced with.
  • the node identifier of the data node includes path information of the data node in the structure tree corresponding to the first YANG model.
  • the network management device may include a software-defined network (Software Defined Network, SDN) controller.
  • SDN Software Defined Network
  • a query device which is applied to a network management device, and the device includes: a processing unit, configured to generate a first query message, the first query message includes a first query condition, and the first query condition It is used to acquire a node identifier and first indication information of a data node of a network device, the node identifier is used to identify a data node of a first YANG model in the network device, and the first indication information is used to indicate the network device Support for the data node; a sending unit, configured to send the first query message to the network device; a receiving unit, configured to receive a first response message from the network device, the first response message Including the node identifier of the data node and the first indication information.
  • the first query condition includes a node identifier of the data node
  • the first query message is used to query the first indication information according to the node identifier of the data node.
  • the first query condition includes a first query instruction
  • the first query instruction is used to query the YANG library library of the first YANG model
  • the YANG library includes the node of the data node Identification and first indication information
  • the first query condition includes a second query instruction
  • the second query instruction is used to query the structural schema information of the first YANG model
  • the schema information includes the nodes of the data nodes and the first indication information
  • the first query condition includes a file name
  • the first query message is used to obtain the node identifier of the data node and the first indication information from the file corresponding to the file name .
  • the first query message is a first remote procedure call (RPC) message.
  • RPC remote procedure call
  • the first response message includes a first RPC response message or a notification message.
  • the processing unit is configured to generate a first query message in response to generating a second RPC message, where the second RPC message is used to configure the data node.
  • the sending unit is further configured to send the second RPC message to the network device in response to the first indication information indicating that the network device supports the data node.
  • the processing unit is configured to generate a first query message in response to receiving a second RPC response message, where the second RPC response message is used to indicate that the configuration of the data node fails.
  • the first response message further includes a node identifier of a replacement node of the data node; the launching unit is further configured to send a third RPC message to the network device, and the third RPC The messages are used to configure the replacement node.
  • the processing unit is configured to generate a first query message in response to receiving feedback information, the feedback information is used to indicate that the license has been activated or purchased, and the data node is related to the The data node associated with the above license.
  • the processing unit is further configured to generate a second query message, the second query message includes a second query condition, and the second query condition includes an identifier of a second YANG model; the sending a unit, further configured to send the second query message to the network device; the receiving unit, further configured to receive a second response message from the network device, the second response message including the second indication information, the second indication information is used to indicate the support of the second YANG model by the network device.
  • the node identifier of the data node includes path information of the data node in the structure tree corresponding to the first YANG model.
  • the network management device includes a software-defined network SDN controller.
  • a query device which is applied to network equipment, and the device includes: a receiving unit, configured to receive a first query message from a network management device, the first query message includes a first query condition; a processing unit , used to acquire the node identifier and first indication information of the data node in the first YANG model of the network device according to the first query condition, the first indication information being used to indicate the network device's support for the data node Condition: generating a first response message, the first response message including the node identifier of the data node and the first indication information; a sending unit, configured to send the first response message to the network management device.
  • the first query condition includes a node identifier of the data node
  • the first query message is used to query the first indication information according to the node identifier of the data node.
  • the first query condition includes a first query instruction
  • the first query instruction is used to query the YANG library library of the first YANG model
  • the YANG library includes the node of the data node Identification and first indication information
  • the first query condition includes a second query instruction
  • the second query instruction is used to query the structural schema information of the first YANG model
  • the schema information includes the nodes of the data nodes and the first indication information
  • the first query condition includes a file name
  • the query message is used to obtain the node identifier of the data node and the first indication information from a file corresponding to the file name.
  • the first query condition includes the device identifier of the network device, and the first query message is used to obtain the node identifier of the data node and the first indication according to the device identifier and the corresponding relationship information, and the corresponding relationship is a corresponding relationship between the device identifier, the node identifier of the data node, and the first indication information.
  • the first query message is a first remote procedure call (RPC) message.
  • RPC remote procedure call
  • the first response message includes a first RPC response message or a notification message.
  • the receiving unit is further configured to receive a second query message, the second query message includes a second query condition, and the second query condition includes an identifier of a second YANG model; the processing The unit is further configured to obtain second indication information according to the second query condition, the second indication information is used to indicate the support of the network device for the second YANG model; generate a second response message, the The second response message includes the second indication information; and the sending unit is further configured to send the second response message to the network management device.
  • the first response message further includes a node identifier of a replacement node of the data node.
  • the node identifier of the data node includes path information of the data node in the structure tree corresponding to the first YANG model.
  • the network management device includes a software-defined network SDN controller.
  • a network management device in a fifth aspect, includes a processor chip and a memory, the memory is used to store instructions or program codes, and the processor chip is used to call and run the instructions or program codes from the memory, to Execute the query method described in the first aspect.
  • a network device in a sixth aspect, includes a processor chip and a memory, the memory is used to store instructions or program codes, and the processor chip is used to call and run the instructions or program codes from the memory to execute The query method as described in the second aspect.
  • a computer-readable storage medium including instructions, programs or codes, which, when executed on a computer, enable the computer to execute the query method described in any one of the first aspect or the second aspect .
  • FIG. 1 is a schematic diagram of an application scenario of NETCONF provided in an embodiment of the present application
  • FIG. 2 is a schematic diagram of a scene of a network architecture to which the query method provided by the embodiment of the present application can be applied;
  • FIG. 3 is a signaling interaction diagram of the query method provided by the embodiment of the present application.
  • FIG. 4 is a schematic structural diagram of a query device 400 provided in an embodiment of the present application.
  • FIG. 5 is a schematic structural diagram of a query device 500 provided in an embodiment of the present application.
  • FIG. 6 is a schematic structural diagram of a device 600 provided in an embodiment of the present application.
  • FIG. 7 is a schematic structural diagram of a device 700 provided in an embodiment of the present application.
  • YANG (Yet Another Next Generation): It was originally designed as a data modeling language for NETCONF.
  • YANG model A data model built using the YANG data modeling language is called a YANG model.
  • YANG models can be deployed between NETCONF clients and servers, defining data hierarchies that can be used for NETCONF-based operations.
  • the data instantiated using the YANG model can be stored in the encoded format of Extensible Markup Language (Extensible Markup Language, XML) or JavaScript (JS) Object Notation (JavaScript Object Notation, JSON).
  • Extensible Markup Language Extensible Markup Language, XML
  • JS JavaScript
  • JSON JavaScript Object Notation
  • YANG model objects objects in the YANG model, such as YANG module set, model module, data node, YANG package, etc.
  • Module-set A collection of models.
  • Module Defines the hierarchical structure of YANG model data, which is used for NETCONF-based operations.
  • a module includes one or more data nodes. The hierarchical organization of these data nodes is modeled as a tree. Each data node has a name or a value or a set of child nodes. Each data node can be unique logo.
  • YANG Library The method defined by RFC8525 for the NETCONF client to obtain the YANG modules and data sets currently being used by the server.
  • Schema is used to describe the data structure of YANG. Schema defines all managed data nodes in the network device, as well as the hierarchical relationship, read and write attributes and constraints between each data node. In actual application scenarios, the Schemas of different suppliers can be different.
  • XML is a markup language.
  • marks refer to information symbols that computers can understand. Through such marks, computers can process various information, such as articles. It can be used to mark data, define data types, and is a source language that allows users to define their own markup language. The position of each element in the XML document can be located through the XPath language.
  • the XPath language can convert XML documents into a tree structure, and represent the position of elements in the XML document through the path from the root node to the node where the element is located.
  • RPC is a remote call method, which can call the command line stored in the network device through the operation command, and request the network device to execute the command line corresponding to the operation command to complete the corresponding operation.
  • NETCONF message is a message transmitted through NETCONF.
  • the NETCONF message can include the RPC message sent by the network management device, the RPC Reply message sent by the network device, and the notification (Notification) message sent by the network device, etc.
  • the RPC message is a NETCONF message sent by the network management device to the network device, and is used to call a pre-stored function or method in the network device to manage the network device.
  • the RPC message may include an operation instruction, which is used to request the network device to perform a corresponding operation.
  • the network management device can call the command line stored in the network device, so that the network device performs corresponding operations according to the command line.
  • the RPC response message is a response message of the network device to the RPC message, and may include, for example, an execution result of an operation.
  • the notification message is a NETCONF message sent by the network device to the network management device, and is used to notify the network management device of the occurrence of a preset event.
  • the network management device may first establish a subscription (Subscription) with the network device through the RPC message.
  • the figure is a schematic diagram of an application scenario of NETCONF provided by the embodiment of the present application.
  • the network architecture includes a network management device 110 and a network device 120 .
  • a YANG model 121 is deployed in the network device 120, and the YANG model 121 includes a root node 121-1 and one or more data nodes 121-2.
  • the root node 121-1 may be a model (module), and the data node 121-1 is a leaf node of the root node 121-1.
  • the network device 120 can work according to the value of the data node in the YANG model 121 .
  • the network management device 110 may send an RPC message to the network device 120 through the connection.
  • the network device 120 may send an RPC response message or a notification message to the network management device 110 through the connection.
  • the RPC message can be used to modify the value of the data node in the YANG model 121 to achieve the purpose of configuring the data node.
  • Data nodes in the YANG model often have a certain life cycle.
  • the support of data nodes in the YANG model 121 may change.
  • the support capability of the network device 120 for the function corresponding to the data node 121-1 may change from supporting to not supporting, or, the support degree of the network device 120 for the function corresponding to the data node 121-2 may change, etc. See below for details).
  • the network equipment lacks the means to notify the network management equipment of the change in the support status of the data node, so that the network management equipment 110 cannot know the change in the support status of the data node in time, and cannot reasonably respond Network device management.
  • the network management device 110 may still generate a An RPC message to configure the data node 121-2. Since the data node 121-2 is no longer supported by the network device 120, the network management device fails to configure the data node 121-2. It can be seen that in the traditional NETCONF scenario, the network management equipment cannot manage the network equipment well due to the inability to know the changes in the support of the data nodes in the YANG model in time.
  • the embodiment of the present application provides a query method.
  • the network management device can generate a query message and send it to the first device, requesting the network device to report the support status of the data node, so that the network management device can better understand the network device. to manage.
  • the network architecture includes a network management device 210 , one or more network devices 220 and a server 230 .
  • the network management device 210 is respectively connected to each network device 220 in one or more network devices 220 , and the network management device 210 may also be connected to a server 230 .
  • the network management device 210 may send the RPC message to the network device 220 .
  • the network device 220 may also send an RPC response message or a notification message to the network management device 210 through the connection.
  • the network device 210 may also send a message to the server 230 , and may also receive a message sent by the server 230 .
  • the network management device 210 may be a device such as an SDN controller.
  • a NETCONF client (client) may be deployed on the network management device 210 .
  • the network device 220 may be a router (router), a switch (switch) and other physical devices that support routing functions, and may also be a server deployed with a virtual router or a virtual switch.
  • a NETCONF server (server) may be deployed on the network device 220 .
  • a YANG model corresponding to the network device can be deployed on the NETCONF server of each network device 220 respectively.
  • the YANG model corresponding to each network device 220 in one or more network devices 220 may be deployed on the server 230 , or the YANG model of some network devices may be deployed or not.
  • this figure is a signaling interaction diagram of the query method provided by the embodiment of the present application, including:
  • S301 The network management device generates a query message.
  • the network management device may be, for example, the network management device 210 shown in FIG. 2 .
  • the query message generated by the network management device includes a query condition, the query condition is used to obtain the node identification and indication information of the data node in the YANG model of the network equipment, and the indication information is used to indicate the support of the network equipment to the data node Condition.
  • the node identifier of the data node is used to uniquely identify the data node, for example, may include XPath information of the data node, and may also include information such as the name of the data node.
  • the indication information is used to indicate the support of the network device to the data node.
  • the support of the data node may indicate the support capability of the network device to the function corresponding to the data node, or may indicate the support of the network device to the function corresponding to the data node degree.
  • the ability of the network device to support the functions corresponding to the data node includes but not limited to the ability of the network device to perform operations such as configuration or query on the data node.
  • the support of the data node by the network device is not supported, it means that the network device cannot use the function corresponding to the data node; if the support of the data node by the network device is supported, it means that the network device can use the function corresponding to the data node.
  • the support status of the data node may also be used to indicate that the network device partially supports the data node, that is, it can use some functions corresponding to the data node.
  • the query message may be used to query the support status of the data node from the network device, or may be used to query the support status of the data node from the server. If the query message is used to query the support status of the data node from the network device, the query message may be an RPC message.
  • the query message generated by the network management device includes query conditions.
  • the query conditions can be implemented in the following five different ways.
  • the query condition includes the identifier of the data node
  • the query message is used to query the indication information according to the node identifier of the data node.
  • the identifier of the data node may be the XPath information of the data node in the YANG model
  • the query message may be an RPC message.
  • the operation instruction in the query message may have the following two situations:
  • Case 1 The operation instruction in the query message is a user-defined operation instruction.
  • the technician can define a new operation instruction for obtaining the support status of the data node
  • the query message can include the user-defined operation instruction, which is used to control the network device to query and report the data according to the operation instruction Node support.
  • the network device can execute the operation instruction, so as to search for the support status of the data node corresponding to the node identifier.
  • the RPC message M1-1 used to obtain the support of the data node communities can be as follows:
  • the first line of the RPC message M1-1 is the message layer of the RPC message M1-1, indicating that the RPC message M1-1 belongs to the RPC message, and the XML namespace (XML Namespaces, xmlns) of the RPC message M1-1 is urn:ietf :params:xml:ns:netconf:base:1.0.
  • the second line of the RPC message M1-1 is the operation layer of the RPC message M1-1, indicating that the operation command carried in the RPC message M1-1 is a get-node-capability command, which is used to obtain the support status of the data node of the network device.
  • the third to fifth lines of the RPC message M1-1 are the content layer of the RPC message M1-1, indicating that the RPC message M1-1 is used to request the support of the communitys node in the Simple Network Management Protocol (SNMP) .
  • SNMP Simple Network Management Protocol
  • the RPC message M1-2 used to obtain the data node local-storage-limit can be as follows:
  • the RPC message M1-2 may be used to obtain the support status of the data node local-storage-limit whose XPath information is /example-syslog/syslog/local-storage-limit.
  • the operation instruction is the get-node-capability instruction defined by the technician, not the existing operation instruction of NETCONF.
  • the operation instruction may also be an existing operation instruction of NETCONF. For example, it may be a get command, a get-data command, a get-config command, or a create-subscription command.
  • the network device can store the support status of the data node in the YANG model.
  • a target YANG model can be newly created in the network device, and the target YANG model is used to store the support of the network device for the data node, which is a new YANG model defined by the technician in the network device.
  • the network management device can generate an RPC message through existing instructions in NETCONF (such as get instructions, get-data instructions or get-config instructions) and the node identifier of the data node (such as the XPath information of the data node in the target YANG model).
  • the RPC request message M2-1 generated by the network management device may be as follows:
  • the first line of the RPC request message M2-1 is the message layer of the RPC request message M2-1, indicating that the RPC request message M2-1 belongs to the RPC message, and the information identification (message-id) of the RPC request message M-12 is 101 .
  • the second line of the RPC request message M2-1 is the operation layer of the RPC request message M2-1, indicating that the operation command carried in the RPC request message M2-1 is a get command, which is used to obtain information about network devices.
  • the third to sixth lines of the RPC request message M2-1 are the content layer of the RPC request message M2-1.
  • the third line of the RPC request message M2-1 indicates that the xmlns corresponding to the get command is http://example.com/schema/1.2/config, that is, the Uniform Resource Locator (Uniform Resource Locator, URL) stored in the target YANG model is in the file at http://example.com/schema/1.2/config.
  • the fourth line of the RPC request message M2-1 indicates that the data node identifier type (type) is XPath language type, that is, the element in the fifth line of the RPC request message M2-1 is in the XPath language format.
  • the fifth line of the RPC request message M2-1 indicates that the data node targeted by the get command is communitys, and the XPath information of the data node communitys is snmp:snmp/snmp:communitys.
  • the support of data nodes in the YANG model of the network device may change when the network device is running.
  • the network device may also initiate a subscription to the network device for the change of the support status of the data node.
  • the network device detects that the support of the data node in the YANG model of itself occurs, the network device can actively generate a notification (notification) message and send it to the network management device, so that the network management device can know the status of the data node in the YANG model of the network device.
  • the network management device may generate an RPC message including a create-subscription command and a preset event, so that the network device generates and reports a notification message when the preset event is triggered. Then, for the scenario where the network device reports the support status, the RPC message used to create the subscription is the query message. That is, the operation instruction in the query message may include a create-subscription instruction, and the query message may also include subscribing to a corresponding preset event, where the preset event is a change in the support status of the data node.
  • the RPC message M2-2 generated by the network management device may be as follows:
  • the third line of the RPC message M2-2 indicates that the operation instruction corresponding to the RPC message M2-2 is a subscription creation (create-subscription), which is used to create a subscription between the network management device and the network device; the first row of the RPC message M2-2
  • the six lines indicate that the type of subscription created by the network management device is yang-capability-changes, indicating that the preset time is when the support of the data node changes, indicating that the purpose of the subscription initiated by the network management device is to make the network device detect the support of the data node. Notify the network management device after the change; the eighth line of the RPC message M2-2 is used to reflect the start time of the subscription, and the ninth line of the RPC message M2-2 is used to reflect the end time of the subscription.
  • the query condition includes a first query instruction.
  • the first query instruction is used to query the YANG Library of the network device.
  • the query condition may include YANG Library identification and operation instructions, and the query message may be an RPC message.
  • the network device can store the support of the data node in the YANG Library.
  • YANG Library is the YANG model used to store the information of the YANG model.
  • the network device can add a sub-node (hereafter referred to as node C) under the node corresponding to data node B in YANG Library to record the support of data node B.
  • node C a sub-node
  • the network management device can use the existing commands of NETCONF (such as get command, get-data command or get-config command), the YANG Library mark and the node mark of node C Generate RPC message D.
  • the network device After the network device receives the RPC message D, it can determine the node C from the YANG Library according to the node identifier, and send the value of the node C to the network management device through the RPC response message. Since node C is used to store the support of data node A, the value of node C can reflect the support of data node A.
  • the node identifier of node C may be, for example, XPath information of node C, and the identifier of YANG Library may be, for example, xmlns of YANG Library.
  • the RPC message M3 generated by the network management device may be as follows:
  • the above RPC message M3 can be used to query the support status stored in the model set (module-set) named config-modules in the YANG Library.
  • the support of data nodes is stored in the model set of config-modules of YANG Library.
  • one query message can be used to query the support status of multiple data nodes.
  • the RPC message M3 can be used to obtain the support status of multiple data nodes.
  • the query message may not include the name of the model set, so the query message may be used to query the support information stored in multiple model sets. That is, if the RPC message M3 does not include ⁇ name>config-modules ⁇ /name>, then the RPC message M3 can be used to query the support status stored in each model set in multiple model sets of the YANG Library.
  • the query condition includes a second query instruction.
  • the second query instruction is used to query the structural schema information of the YANG model.
  • the query condition may include the identifier of the schema model and an operation instruction, and the query message may be an RPC message.
  • the network equipment may include a Schema model, and the Schema model can provide monitoring information of the network equipment, and can be used for the network management equipment to monitor the network equipment.
  • support for data nodes can be added under the netconf-state/schemas subtree in the Schema model.
  • the RPC message generated by the network management device can search the support status of the data node from the netconf-state/schemas subtree.
  • the RPC message M4 generated by the network management device may be as follows:
  • the support status of the data node is stored in the network device, so the query message is an RPC message, and the network management device can search the support status of the data node from the network device through the query message.
  • the support information of the data nodes may also be stored in the server, so the query conditions generated by the network management device may have the following two possible implementation manners.
  • query messages provided by the following two possible implementations may also be applicable to a scenario where the support information of the data node is stored in the network device.
  • the query condition includes a file name
  • the query message is used to obtain the node identifier of the data node and the indication information from the file on the server.
  • the query condition may include the name of the file in which the support status is stored.
  • the server can determine the name of the file to be queried according to the query condition, and then search the support status of the data node from the file according to the node identifier.
  • the node identifier of the data node may be the name of the data node.
  • Query messages can also include file paths.
  • the query condition includes the device identifier of the network device, and the query message is used to obtain the node identifier and indication information of the data node according to the equipment identifier and the corresponding relationship, and the corresponding relationship is the device identifier and the node identifier and indication of the data node Correspondence between information.
  • the server can establish a link between the data nodes and network devices. The corresponding relationship is used to distinguish the data nodes of different network devices.
  • the server can establish the correspondence between the identifier of network device C and the identifier of data node A and the indication information a, and the correspondence between the identifier of network device D and the identifier of data node B and indication information b.
  • the query message generated by the network management device may include the identifier of the network device D.
  • the server can determine according to the identifier of the network device D that the data node that the network management device wants to query belongs to the network device D, so as to determine the node identifier and indication information b of the data node B according to the corresponding relationship.
  • the query message is introduced above, and in the embodiment of the present application, the query message is used to query the support status of the data node.
  • the support status may indicate the capability of the network device to support the function, and may also indicate the degree of support of the network device to the function. Two possible implementations are described below.
  • the support status indicates whether the network device supports the function corresponding to the data node. That is, the support status of the data node can reflect whether the network device is capable of implementing the function corresponding to the data node. If the network device supports the data node, it means that the network device can implement the function corresponding to the data node. If the support of the data node by the network device is not supported, it means that the network device cannot implement the function corresponding to the data node.
  • the support status can be reflected by the declared value of the status (status) of the data node.
  • the value declared by the Status of the data node in the YANG model can be any one of recommended (current), not recommended (deprecated) and obsolete (obsolete).
  • current indicates that the data node is valid in the current YANG model
  • deprecated indicates that the data node is not recommended, but the network device still has the ability to implement the corresponding functions of the data node
  • obsolete indicates that the data node is not supported by the network device.
  • the declared value of the data node is current or deprecated, it means that the network device can realize the function corresponding to the data node, and the support of the data node by the network device is support; if the declared value of the data node is obsolete, it means that the network device does not have The ability to realize the functions corresponding to the data node, and the support of the data node by the network device is not supported. It should be noted that in some possible implementations, the value declared by the Status may be deprecated or not supported by the data node.
  • the network device may report the declared value of the data node, or directly report the support status of the data node.
  • the support status indicates the support degree of the network device to the function corresponding to the data node. That is to say, the support status of the data node may indicate the parameter range that the network device can adopt when realizing the function corresponding to the data node.
  • the maximum number of access controller (Access Point, AP) devices allowed by the network device to access the wireless local area network (Wireless Local Area Network, WLAN) is 16.
  • the network device allows a maximum of 512 AP devices connected to the WLAN.
  • the network device has different support capabilities for "allowing the AP device to access the WLAN" when the license is activated and when the license is not activated.
  • the query message and support situation are introduced above, and the method of generating query message by the network management device is introduced below.
  • the generation of the query message may be triggered actively by the network management device, or may be triggered by the network management device after receiving a message (for example, an RPC response message) from the network device.
  • a message for example, an RPC response message
  • the query message generated by the network management device may have the following four possible implementation manners.
  • the network management device can actively generate query messages.
  • a timer may be set in the network management device, and a query message is generated and sent to the first device every preset time interval.
  • a query message is generated and sent to the first device every preset time interval.
  • the network management device may generate a query message before sending the RPC message.
  • the network management device can manage the network device through the RPC message, for example, configure the data nodes in the YANG model of the network device. Then, before sending the RPC message to the network device, the network device can first generate a query message, query the support status of the data node through the query message, and perform corresponding operations according to the query result.
  • the network device can first generate a query message Y, the query message Y includes the node identifier of data node A, and is used to query the network device Read the support status of data node A. After receiving the response message returned by the network device, if the indication information in the response message indicates that the network device supports data node A, the network management device may send an RPC message X to the network device.
  • the network management device may generate the query message after receiving the RPC response message sent by the network device.
  • the network management device may generate an RPC message for configuring the data node and send it to the network device.
  • the network device can process the RPC message, and notify the network management device of the configuration result of the RPC message through the RPC response message. If the network device fails to configure the data node, the network device may send an RPC response message to the network management device to notify the network management device that the configuration of the data node fails. Then, after receiving the RPC response message, the network management device can generate a query message, and judge whether the configuration failure is caused by the network device no longer supporting the data node through the query message.
  • RPC message X is used to configure data node A, but the network device no longer supports data node A, then after receiving the RPC message, the network device will not process data node A, and will generate RPC response message Y, through RPC The response message Y notifies the network management device that the configuration of the data node A fails.
  • the network management device may determine according to the RPC response message Y that the network device failed to process the data node A. In order to determine the reason for the failure to process data node A, the network management device may generate a query message, so as to query the support of data node A by the network device. If the support status of data node A is not supported, it means that the reason why the processing of RPC message X fails is that the network device no longer supports data node A.
  • the network management device may generate a query message after receiving the feedback information.
  • the license may be activated or purchased. License is used to allow network devices to perform further processing.
  • the network device may send feedback information to the network management device after the license is activated or purchased. After receiving the feedback information, the network device can know that the license of the network device is activated or purchased.
  • the function of the network device may change as the license is activated or purchased.
  • the support of data nodes in the YANG model by network devices may also change.
  • the maximum number of APs allowed by the network device to access the WLAN is 16, and when the license is activated, the maximum number of APs allowed by the network device to access the WLAN is 512.
  • the network device has different support capabilities for the data nodes corresponding to the function of "allowing the AP device to access the WLAN" when the license is activated and when the license is not activated.
  • the network management device can generate a query message and send it to the network device, so as to know the changes brought about by the activation or purchase of the license to the support situation of the data node.
  • the node identifier included in the query message may be the node identifier associated with the license.
  • the query message is used to query the support status of the data node.
  • the query message generated by the network management device may also be used to query the support of the network device for the YANG model, and the query message may include the identifier of the YANG model.
  • S302 The network management device sends a query message to the first device.
  • the network management device may send the query message to the first device.
  • the first device may be a server or a network device, for example, it may be the network device 220 shown in FIG. 2 , or the server 230 shown in FIG. 2 .
  • S303 The first device acquires indication information.
  • the first device may acquire indication information according to the query condition in the query message, where the indication information is used to indicate the support of the network device to the data node. Specifically, the first device may query the support status of the data node according to the query message, and then obtain the indication information according to the support status of the data node.
  • the first device may be a network device or a server.
  • the following describes how the first device queries the support status of the data node in the two cases where the first device is a network device and the first device is a server.
  • the first device is a network device.
  • the query message sent by the network management device to the first device is an RPC message.
  • the network device after receiving the query message sent by the network management device, the network device can execute the operation instruction included in the RPC message, so as to obtain the instruction information.
  • the indication information may include the support status of the data node.
  • the RPC message may include user-defined operation instructions, or may include existing operation instructions. The two possible situations are introduced respectively below.
  • the RPC message includes an operation instruction defined by a technician (for example, a get-node-capability instruction).
  • the network device can determine the data node queried by the network management device according to the RPC message, and call and execute the stored program or code to determine the support of the data node and obtain the instruction information.
  • the RPC message may include the node identifier of the data node, then the network device may determine the data node queried by the network management device according to the node identifier.
  • the RPC message when the operation instruction in the RPC message is a traditional operation instruction such as get, the RPC message also includes the identification of the storage location of the support status of the data node in the network device. Then, after receiving the RPC message, the network device can execute the operation instruction, obtain the support status of the data node from the storage location included in the RPC message, and obtain the instruction information.
  • the operation instruction in the RPC message is a traditional operation instruction such as get
  • the RPC message also includes the identification of the storage location of the support status of the data node in the network device. Then, after receiving the RPC message, the network device can execute the operation instruction, obtain the support status of the data node from the storage location included in the RPC message, and obtain the instruction information.
  • the RPC message can be used to obtain the support of data nodes from the YANG Library or Schema model.
  • the network device can determine the indication information according to the YANG Library or Schema model.
  • the RPC message may not include the identifier of the data node, but includes the node identifier of the parent node of the child node storing the support.
  • the RPC message M4 does not include the identifier of a specific data node, but includes the identifiers of the parent node schemas of multiple child nodes that store support in the Schema model.
  • the network device when obtaining the indication information, if the RPC message does not include the node identifier of the data node but includes the node identifier of the parent node, the network device can separately obtain the support information and information stored in each of the multiple child nodes of the parent node The data node corresponding to the child node obtains the support status of multiple data nodes, and then determines the indication information according to the support status of the multiple data nodes.
  • the first device is a server.
  • the query message may include a file name or an identifier of a network device. Then, after receiving the query message, the server can analyze the query message, determine the storage location in the server of the support status of the data node to be queried, and then obtain the support status of the data node.
  • the query message sent by the network management device can also be used to query the support of the network device for the YANG model.
  • the indication information generated by the first device according to the query message may be used to indicate the support of the network device for the YANG model.
  • S304 The first device generates a response message according to the indication information.
  • the first device may generate a response message according to the indication information.
  • the response message may include the node identifier and indication information of the data node, and is used to notify the network management device of support of the queried data node by the network device.
  • the response message may be an RPC response message or a notification message. Introduce them separately below.
  • the response message may be an RPC response message.
  • the RPC response message generated by the network device may include the identifier of the data node and corresponding indication information.
  • the support of the data node can include whether the network device supports the function corresponding to the data node
  • a new field can be added in the RPC response message, and the newly added field carries the support of the data node.
  • the support status of the data node indicates the support degree of the network device for the function corresponding to the data node
  • at least two fields can be added in the RPC response message, which are used to carry whether the network device supports the function corresponding to the data node and whether it supports degree. Its specific implementation can be as shown in Example 1-Example 5 below.
  • the RPC response message M5 generated by the network device can be As follows:
  • the third line of the RPC response message M5 indicates that the RPC response message M5 is an RPC response message corresponding to the RPC message including the get-node-capability instruction;
  • the fifth line of the RPC response message M5 indicates that the RPC response message M5 is used to report data The support status of the node communities;
  • the sixth line of the RPC response message M5 indicates that the value declared by the status of the data node communities in the YANG model is deprecated.
  • the seventh line of the RPC response message M5 indicates that the support of the data node communities by the network equipment is not Support (non-supported);
  • the eighth line of the RPC response message M5 indicates that the data node communitiess is replaced by the data node standard-communities.
  • the network management device sends an RPC request message M1-2 to the network device.
  • the RPC response message M6 generated by the network device may be as follows:
  • the third line of the RPC response message M6 indicates that the RPC response message M6 is an RPC response message corresponding to the RPC message M1-2 including the get-node-capability instruction; the fifth to seventh lines of the RPC response message M6 indicate that the RPC The response message M6 is used to report the support of the data node local-storage-limit, and the XPath information of the data node local-storage-limit in the YANG model is example-syslog/syslog; the eighth line of the RPC response message M6 indicates the data The value declared by the Status of the node local-storage-limit is current; the ninth line of the RPC response message M6 indicates that the support of the data node local-storage-limit is partially supported (partial-supported); the tenth line of the RPC response message M6 The line and the eleventh line describe the partial support, indicating that the maximum value supported by the data node local-storage-limit is 128kb, and the reason why the maximum value supported by
  • the support status of the data node communities is stored in the YANG Library of the network device.
  • the RPC response message M7 generated by the network device can be as follows:
  • the fifth and sixth lines of the RPC response message M7 indicate that the content in the RPC response message M7 is the instantiation result of the /yang-library subtree.
  • the seventh and eighth lines of the RPC response message M7 represent the module set (named config-modules) currently supported by the device included in the RPC response message M7.
  • the ninth and tenth lines of the RPC response message M7 indicate that the support included in the RPC response message M7 comes from a YANG module named A-snmp.yang.
  • the fourteenth line of the RPC response message M7 indicates that the RPC response message M7 includes the support status of the data node communitys, and the XPath information of the data node communitys is /snmp:snmp/snmp:communitys.
  • the sixteenth line of the RPC response message M7 indicates that the value declared by the Status of the data node communities is deprecated; the seventeenth line of the RPC response message M7 indicates that the support of the data node communities is not supported (non-supported); the RPC response message
  • the eighteenth line of M7 indicates that the data node communities is replaced by the data node standard-communities.
  • the support of the data node can also be stored in the target YANG model or Schema. Then the RPC response message generated by the network device may be as shown in Example 4 or Example 5.
  • the support status of the nodes is stored in the target YANG model, and the RPC response message M8 generated by the network device can be shown as follows.
  • the third line of the RPC response message M8 indicates that the RPC response message M8 is an RPC response message corresponding to the RPC message including the get-node-capability instruction, and the contents of the remaining lines of the RPC response message M8 are basically consistent with the RPC response message M5, I won't go into details here.
  • the support status of nodes is stored in the Schema model, and the RPC response message M9 generated by the network device can be as follows:
  • the eighth line to the twelfth line of the RPC response message M9 indicate that the support information of the data node carried in the RPC response message M9 comes from the Schema model A-snmp, and the update time of the Schema model A-snmp is 2017.4.11, and the corresponding The URL is http://example.com/schema/A-snmp.yang.
  • the contents of the remaining lines are basically the same as those of the RPC response message M7, and will not be repeated here.
  • the response message is a notification message.
  • the network management device can create a subscription on the network device through the create-subscription command. After the subscription is created, if the network device detects that the support of the data node changes, the network device can generate a notification message and send it to the network management device, so that the network management device knows the change of the support of the data node. Similar to the aforementioned RPC response message, the notification message may also include indication information, and the indication information includes the support status of the data node. Specifically, the notification message M10 generated by the network management device may be as shown in the following 6.
  • the second line of the notification message M10 indicates that the event occurred at 16:51:00 on June 28, 2021.
  • the third line of the notification message M10 indicates that the notification message M10 is a notification message for a subscription of the yang-capability-changes type.
  • the fifth line of the notification message M10 indicates that the name of the event reported by the network device is license-enabled-bgp-sessions.
  • the sixth line of the notification message M10 indicates that the name of the data node whose support has changed is /bgp/sessions; the seventh line of the notification message M10 indicates that the change type of the support of the data node /bgp/sessions is modified; the notification message
  • the eighth and ninth lines of M10 indicate that the maximum number of Border Gateway Protocol (BGP) sessions (BGP sessions) supported by the data node /bgp/sessions has increased from 20 to 50, and the change in support is It is caused by the license being activated (enabled); the tenth line of the notification message M10 indicates that the license is activated by the client whose NETCONF session ID (netconf session ID) is 101.
  • BGP Border Gateway Protocol
  • the server may carry the node identification and support status of the data node in the response message and send it to the network management device.
  • the method for the server to generate the response message is similar to the method for the aforementioned network device to generate the response message, and will not be repeated here.
  • the query message generated by the network management device can be used to query the support of the network device for the YANG model.
  • the response message generated by the first device may include indication information, where the indication information is used to indicate the support of the network device for the YANG model.
  • S305 The first device sends a response message to the network management device.
  • the first device may send the RPC response message to the network management device, so that the network management device can know the support status of the data nodes in the network device.
  • S306 The network management device performs corresponding operations according to the response message.
  • the network management device may perform corresponding operations according to the response message.
  • the query message can be generated before sending the RPC message, or after receiving the RPC response message.
  • the operation performed by the network management device after receiving the response message may have the following two possible implementation manners.
  • the query message is generated by the network management device before sending the RPC message. That is, the query message is used to query the support status of the data node targeted by the RPC message. Then, after receiving the response message, the network management device may send the RPC message or not send the RPC message according to the support of the data node.
  • the network management device can send an RPC message to the network device. If the network device does not support the data node, it means that the network device cannot implement the corresponding function of the data node. Even if the network management device sends an RPC message to the network device, the data node cannot be configured successfully. Therefore, the network management device may not continue to send RPC messages to the network device.
  • the response message may also include information about the replacement node of the data node. Then, if the response message includes information about the replacement node and the response message received by the network management device indicates that the support of the data node is not supported, then the network device can modify the RPC message to be sent according to the response message, and send the modification to the network device The following RPC message is used to configure the replacement node.
  • the query message is generated by the network device after receiving the RPC response message indicating that the configuration of the data node fails. Then, after receiving the response message, the network management device can modify the RPC message according to the support of the data node, or further perform fault detection on the network device.
  • the network device can modify the RPC message that fails to be configured according to the information about the replacement node, and send a new RPC message to the network device. If the network device supports the data node, it means that the failure to configure the data node is not caused by the network device not supporting the data node. The network management device can further troubleshoot the network device to determine the cause of the data node configuration failure.
  • the network management device may generate a query message and send an RPC message to the first device, so that the first device obtains the support status of the data node according to the query message, and returns the response message to the network management device. After receiving the response message returned by the first device, the network management device may perform corresponding operations according to the response message. In this way, the network management device queries the support status of the data node from the first device through the query message, so that the network management device can know the change of the support status of the data node in time, and better manage the network device.
  • the embodiment of the present application also provides a query device 400 , which can implement the functions of the network management device in the embodiment shown in FIG. 3 .
  • the query device 400 includes a processing unit 401 , a sending unit 402 and a receiving unit 403 .
  • the processing unit 401 is used to realize S301 in the embodiment shown in FIG. 3
  • the sending unit 402 is used to realize S302 and S306 in the embodiment shown in FIG. 3
  • the receiving unit 403 is used to receive the The response message sent in the process of S305 in the embodiment.
  • the processing unit 401 is configured to generate a first query message, where the first query message includes a first query condition, and the first query condition is used to obtain a node identifier and first indication information of a data node of the network device,
  • the node identifier is used to identify a data node of the first YANG model in the network device, and the first indication information is used to indicate the support of the network device to the data node.
  • the sending unit 402 is configured to send the query message to the first device.
  • the receiving unit 403 is configured to receive a first response message from the network device, where the first response message includes the node identifier of the data node and the first indication information.
  • the embodiment of the present application also provides a query apparatus 500 , which can realize the function of the first device (eg, network device) in the embodiment shown in FIG. 3 .
  • the query device 500 includes a receiving unit 501 , a processing unit 502 and a sending unit 503 .
  • the receiving unit 501 is used to receive the query message sent by the network management device in the process of executing S302 in the embodiment shown in Figure 3, and the processing unit 502 is used to implement S303 and S304 in the embodiment shown in Figure 3; It is used to implement S305 in the embodiment shown in FIG. 3 .
  • the receiving unit 501 is configured to receive a first query message from a network management device, where the first query message includes a first query condition.
  • the processing unit 502 is configured to acquire a node identifier and first indication information of a data node in a first YANG model of a network device according to the first query condition, and the first indication information is used to indicate that the network equipment is responsible for the data Node support status; generating a first response message, where the first response message includes the node identifier of the data node and the first indication information.
  • the sending unit 503 is configured to send the first response message to the network management device.
  • FIG. 6 is a schematic structural diagram of a device 600 provided in an embodiment of the present application.
  • the above query device 400 or query device 500 may be implemented by the device shown in FIG. 6 .
  • the device 600 includes at least one processor 601 , a communication bus 602 and at least one network interface 604 , and optionally, the device 600 may further include a memory 603 .
  • the processor 601 may be a central processing unit (central processing unit, CPU), a network processor (network processor, NP) or a combination of CPU and NP.
  • the processor 601 may also be a traffic management (traffic management, TM) chip or hardware integrated with NP and TM chips, and the TM chip or hardware integrated with NP and TM chips may control the TM chip
  • the queue executes the queue scheduling method provided by the embodiment of this application.
  • the processor 1010 may further include a hardware chip.
  • the aforementioned hardware chip may be an application-specific integrated circuit (application-specific integrated circuit, ASIC), a programmable logic device (programmable logic device, PLD) or a combination thereof.
  • the aforementioned PLD may be a complex programmable logic device (complex programmable logic device, CPLD), a field-programmable gate array (field-programmable gate array, FPGA), a general array logic (generic array logic, GAL) or any combination thereof.
  • the processor can be used to update or verify the data message, so as to implement the query method provided in the embodiment of the present application.
  • the processor may be configured to: generate a first query message, send the first query message to the network device through the network interface 604, A first response message is received from the network device.
  • the processor may be used to: receive a first query message from the network management device, and obtain the first YANG of the network device according to the first query condition
  • the node identifier of the data node in the model and the first indication information generate a first response message, and send the first response message to the network management device through the network interface 604 .
  • Communication bus 602 is used to transfer information between processor 601 , network interface 604 and memory 603 .
  • the bus system 602 may be a peripheral component interconnect standard (peripheral component interconnect, PCI) bus or an extended industry standard architecture (extended industry standard architecture, EISA) bus or the like.
  • PCI peripheral component interconnect
  • EISA extended industry standard architecture
  • the bus system 602 can be divided into address bus, data bus, control bus, etc., which are represented by only one thick line in FIG. 6 , but it does not mean that there is only one bus or one type of bus.
  • the memory 603 can be a read-only memory (read-only memory, ROM) or other types of static storage devices that can store static information and instructions, and the memory 603 can also be a random access memory (random access memory, RAM) or can store information and other types of dynamic storage devices for instructions, and can also be compact disc read-only Memory (CD-ROM) or other optical disc storage, optical disc storage (including compact disc, laser disc, optical disc, digital versatile disc, Blu-ray optical discs, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited thereto.
  • the memory 603 may exist independently, and is connected to the processor 601 through the communication bus 602 .
  • the memory 603 can also be integrated with the processor 601 .
  • the memory 603 is used to store program codes or instructions for implementing the solutions of the present application, and the execution is controlled by the processor 601 .
  • the processor 601 is used to execute program codes or instructions stored in the memory 603 .
  • One or more software modules may be included in the program code.
  • the processor 601 may also store program codes or instructions for executing the solutions of the present application. In this case, the processor 601 does not need to read the program codes or instructions from the memory 603 .
  • the network interface 604 can be a device such as a transceiver for communicating with other devices or a communication network, and the communication network can be Ethernet, radio access network (RAN) or wireless local area networks (wireless local area networks, WLAN).
  • the network interface 604 may be used to receive messages sent by other nodes in the segment routing network, and may also send messages to other nodes in the segment routing network.
  • the network interface 604 may be an Ethernet interface (ethernet) interface, a fast ethernet (fast ethernet, FE) interface or a gigabit ethernet (gigabit ethernet, GE) interface, etc.
  • the device 600 may include multiple processors, for example, the processor 601 and the processor 605 shown in FIG. 6 .
  • processors may be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor.
  • a processor herein may refer to one or more devices, circuits, and/or processing cores for processing data (eg, computer program instructions).
  • FIG. 7 is a schematic structural diagram of a device 700 provided in an embodiment of the present application. Any one or more of the network management device and the first device in FIG. 3 may be implemented by the device shown in FIG. 7 .
  • the device 700 includes a main control board and one or more interface boards.
  • the main control board is communicatively connected with the interface board.
  • the main control board is also called a main processing unit (main processing unit, MPU) or a route processing card (route processor card).
  • the main control board includes a CPU and a memory. Route calculation, device management and maintenance functions.
  • the interface board is also called a line processing unit (line processing unit, LPU) or a line card (line card), and is used to receive and send packets.
  • the communication between the main control board and the interface board or between the interface board and the interface board is through a bus.
  • the interface boards communicate through a switching fabric board.
  • the device 700 also includes a switching fabric board.
  • the switching fabric board communicates with the main control board and the interface board.
  • the switching fabric board is used to forward the interface board.
  • the data between them, the SFU can also be called a switch fabric unit (SFU).
  • the interface board includes a CPU, a memory, a forwarding engine, and an interface card (interface card, IC), where the interface card may include one or more network interfaces.
  • the network interface may be an Ethernet interface, an FE interface, or a GE interface.
  • the CPU communicates with the memory, the forwarding engine and the interface card respectively.
  • the memory is used to store the forwarding table.
  • the forwarding engine is used to forward the received message based on the forwarding table stored in the memory.
  • the message is sent to the CPU of the main control board or the interface board for further processing. Processing; if the destination address of the received message is not the IP address of the device 700, then look up the forwarding table according to the destination, if the next hop and the outgoing interface corresponding to the destination address are found from the forwarding table, the message will be Forward to the outbound interface corresponding to the destination address.
  • the forwarding engine may be a network processor (network processor, NP).
  • the interface card is also called a daughter card, which can be installed on the interface board. It is responsible for converting the photoelectric signal into a data frame, and checking the validity of the data frame before forwarding it to the forwarding engine for processing or the CPU of the interface board.
  • the CPU can also perform the function of the forwarding engine, such as implementing soft forwarding based on a general-purpose CPU, so that no forwarding engine is needed in the interface board.
  • the forwarding engine may be implemented by an ASIC or a field programmable gate array (field programmable gate array, FPGA).
  • the memory storing the forwarding table can also be integrated into the forwarding engine as a part of the forwarding engine.
  • the embodiment of the present application also provides a chip system, including: a processor, the processor is coupled with a memory, and the memory is used to store programs or instructions, and when the programs or instructions are executed by the processor, the The chip system implements the query method provided in the above embodiment shown in FIG. 3 .
  • processors in the chip system there may be one or more processors in the chip system.
  • the processor can be realized by hardware or by software.
  • the processor may be a logic circuit, an integrated circuit, or the like.
  • the processor may be a general-purpose processor implemented by reading software codes stored in a memory.
  • the memory can be integrated with the processor, or can be set separately from the processor, which is not limited in this application.
  • the memory can be a non-transitory processor, such as a read-only memory ROM, which can be integrated with the processor on the same chip, or can be respectively arranged on different chips.
  • the setting method of the processor is not specifically limited.
  • the system-on-a-chip can be an FPGA, an ASIC, a system on chip (SoC), a CPU, an NP, or a digital signal processing circuit (digital signal processor, DSP), can also be a microcontroller (micro controller unit, MCU), can also be a programmable controller (programmable logic device, PLD) or other integrated chips.
  • SoC system on chip
  • DSP digital signal processing circuit
  • MCU microcontroller
  • PLD programmable controller
  • each step in the foregoing method embodiments may be implemented by an integrated logic circuit of hardware in a processor or instructions in the form of software.
  • the method steps disclosed in connection with the embodiments of the present application may be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules in the processor.
  • the embodiment of the present application also provides a computer-readable storage medium, including instructions, which, when run on a computer, cause the computer to execute the query method provided by the above method embodiment and executed by the network management device, or executed by the first device query method.
  • the embodiment of the present application also provides a computer program product containing instructions. When it is run on a computer, it causes the computer to execute the query method provided by the above method embodiment and executed by the network management device, or the query executed by the first device. method.
  • the disclosed system, device and method can be implemented in other ways.
  • the device embodiments described above are only illustrative.
  • the division of the units is only a logical module division.
  • multiple units or components can be combined or May be integrated into another system, or some features may be ignored, or not implemented.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of devices or units may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place, or may be distributed to multiple network units. Part or all of the units can be obtained according to actual needs to achieve the purpose of the solution of this embodiment.
  • each module unit in each embodiment of the present application may be integrated into one processing unit, each unit may exist separately physically, or two or more units may be integrated into one unit.
  • the above-mentioned integrated units can be implemented in the form of hardware or in the form of software module units.
  • the integrated unit is implemented in the form of a software module unit and sold or used as an independent product, it can be stored in a computer-readable storage medium.
  • the technical solution of the present application is essentially or part of the contribution to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium , including several instructions to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), magnetic disk or optical disc, etc., which can store program codes. .
  • the functions described in the present invention may be implemented by hardware, software, firmware or any combination thereof.
  • the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium.
  • Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another.
  • a storage media may be any available media that can be accessed by a general purpose or special purpose computer.

Landscapes

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

Abstract

本申请提供了一种查询方法、装置及设备,实现网管设备获取到网络设备对数据节点的支持情况的目的。其中,所述查询方法包括:网管设备生成第一查询消息,所述第一查询消息包括第一查询条件,所述第一查询条件用于获取网络设备的数据节点的节点标识和第一指示信息,所述节点标识用于标识所述网络设备中第一YANG模型的数据节点,所述第一指示信息用于指示所述网络设备对所述数据节点的支持情况;所述网管设备向所述网络设备发送所述第一查询消息;所述网管设备接收来自所述网络设备的第一响应消息,所述第一响应消息包括所述数据节点的节点标识和所述第一指示信息。

Description

一种查询方法、装置及设备
本申请要求于2021年7月30日提交的申请号为202110875171.9、申请名称为“一种查询方法、装置及设备”的中国专利申请的优先权,其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域,尤其涉及一种查询方法、装置及设备。
背景技术
网络配置协议(Network Configuration Protocol,NETCONF)是一种基于下一代建模语言(yet another next generation,YANG)建模的网络管理协议,提供了一套对网络设备进行配置和管理的机制,用户可以使用这套机制增加,修改,删除网络设备的配置,获取网络设备的配置和状态信息,在网络管理系统中得到了广泛的应用。NETCONF采用客户端(Client)和服务端(Server)的结构,使用基于基于远程过程调用(Remote Procedure Call,RPC)机制实现客户端和服务器通信。YANG是用来为NETCONF协议设计可操作的配置数据、状态数据建模、RPC操作指令和通知机制建模等,作为Clint的网管设备可以下发用YANG建模的网络配置,并获取作为Server的网络设备用YANG建模的配置和状态信息实现设备的管理。
YANG模型基于可扩展标记语言(Extensible Markup Language,XML)实现,属于XML格式的文件。因此,YANG模型文件可以定义一个YANG module,一个YANG module可以包括多个节点,这些节点可以组成树形结构。其中,用YANG建模的数据可以被实例化,数据节点为树形结构中可以实例化的节点。在网管设备对网络设备进行管理时,往往是对使用XML编码后的YANG模型的数据节点进行管理。
随着网络设备的工作,网络设备的YANG模型中数据节点的支持情况可能发生改变,导致网管设备无法较好地对网络设备进行管理。
发明内容
本申请实施例提供了一种查询方法、装置及设备,实现网管设备获取网络设备对数据节点的支持情况的目的。
第一方面,提供了一种查询方法,该方法可以应用于部署有NETCONF客户端的网管设备。所述方法包括如下步骤:网管设备生成第一查询消息,第一查询消息包括第一查询条件,第一查询条件用于获取网络设备中数据节点的节点标识和第一指示信息。节点标识可以用于标识网络设备中第一YANG模型中的数据节点,例如可以是数据节点的XML路径(XML Path,XPath)信息。第一指示信息可以用于指示网络设备对节点标识所指示的数据节点的支持情况。在生成第一查询消息之后,网管设备可以向网络设备发送第一查询消息,以便网络设备根据的第一查询消息查询自身对节点标识所指示的数据节点的支持情况,得到第一指示信息。在得到第一指示信息之后,网络设备可以将第一指示信息和节点标识携带在第一响应消息中向网管设备发送,以使网管设备通过第一响应消息得到第一指示信息。这样,由网管设备通过查询消息从网络设备处查询数据节点的支持情况,使得网管设备可以及时了解到数据节点的支持情况所发生的变化,更好的对网络设备进行管理。
在本申请实施例中,网管设备生成第一查询消息可以由如下三种可能的实现方式:
实现方式一:响应于生成第二RPC消息,网管设备生成第一查询消息。其中,第二第二RPC消息用于对数据节点进行配置。即,在对网络设备的YANG模型中的数据节点进行配置之前,网管设备可以先生成第一查询消息,通过第一查询消息查询网络设备对将要被配置的数据节点的支持情况。
相应地,如果网管设备接收到的第一响应消息中第一指示信息指示网络设备支持数据节点,网管设备可以向网络设备发送第二RPC消息。这样,在对数据节点进行配置之前先查询网络设备的数据节点的支持情况,可以避免配置失败的情况发生。
实现方式二:响应于接收到第二RPC响应消息,网管设备生成第一查询消息。其中,第二RPC响应消息可以用于指示网管设备对数据节点的配置失败。即,在接收到第二RPC响应消息之前,网管设备向网络设备发送的RPC消息,用于对数据节点进行配置。但是网设备无法根据RPC消息对数据节点进行配置,并向网管设备发送了第二RPC响应消息,以通知网管设备对数据节点配置失败。那么为了查询配置失败的原因,网管设备可以生成第一查询消息,通过第一查询消息查询网络设备对数据节点的支持情况。
相应地,网管设备接收到的第一响应消息可以包括数据节点的替换节点的节点标识。其中替换节点为用于替换原有数据节点的新数据节点。基于此,可以确定数据节点被替换节点代替,导致了网管设备对数据节点的配置失败。因此,网管设备可以根据替换节点的节点标识生成第三PRC消息并向网络设备发送,从而通过第三RPC消息对替换节点进行配置。
实现方式三:响应于接收到反馈信息,网管设备生成第一查询消息。其中,反馈信息用于指示许可证(license)被购买或激活,且被购买或激活的license与第一查询消息所包括的节点标识对应的数据节点相对应。license被购买或激活可能导致网络设备的功能发生变化,进而导致网络设备对数据节点的支持情况发生改变。因此,在接收到反馈消息后,网管设备可以根据license对应的数据节点的节点标识生成第一查询信息,以查询license被激活或购买后网络设备对数据节点的支持情况的改变。
在本申请实施例中,第一查询消息中的第一查询条件可以包括如下四种可能的实现方式:
实现方式一:第一查询条件包括数据节点的节点标识,相应地,第一查询消息用于根据数据节点的节点标识查询第一指示信息。如果网管设备想要查询网络设备对特定的数据节点的支持情况,网管设备可以将该数据节点的节点标识携带在第一查询消息中,以便网络设备根据数据节点的节点标识获取对该数据节点的支持情况。可选地,在这种实现方式中,第一查询消息可以包括操作指令,该操作指令可以是NETCONF已有的操作指令,也可以是技术人员自定义的操作指令。
实现方式二:第一查询条件包括第一查询指令。第一查询指令用于从网络设备的YANG库(YANG Library)中查询支持情况,YANG Library包括数据节点的节点标识和第一指示信息。网络设备可以将对多个YANG模型(包括第一YANG模型)中数据节点的支持情况存储在YANG Library中。网管设备可以根据数据节点的支持情况在YANG Library中的存储位置生成第一查询消息。可选地,网管设备还可以根据数据节点的支持情况所属的模型 集(module set)信息或模型(module)信息生成第一查询消息。可选地,在这种实现方式中,第一查询质量可以是NETCONF已有的操作指令,例如获取(get)指令、获取数据(get-data)指令或获取配置(get-config)指令等指令。
实现方式三:第一查询条件包括第二查询指令,第二查询指令用于查询第一YAGN模型的结构(schema)信息,schema包括数据节点的节点标识和第一指示信息。具体地,与实现方式二类似,网络设备可以将多个YANG模型(包括第一YANG模型)中数据节点的支持情况存储在schema模型中。相应地,网管设备可以生成包括第二查询指令的第一查询消息,以便从schema模型中查询网络设备对数据节点的支持情况。
实现方式四:第一查询条件包括文件名称,第一查询消息用于从与文件名称对应的文件中获取数据节点的节点标识和第一指示信息。具体地,网络设备可以将数据节点的节点标识和第一指示信息存储在文件中。那么网管设备可以根据存储有节点标识和第一指示信息的文件名称生成第一查询消息。
在上述可能的实现方式中,第一查询消息可以为RPC消息,又称第一RPC消息。可选地,第一查询消息也可以用于建立网络设备与网管设备之间的订阅。第一响应消息可以为RPC响应(RPC Reply)消息,又称第一RPC响应消息。
在一种可能的设计中,网管设备还可以查询网络设备对YANG模型的支持情况。具体地,网管设备可以生成包括第二查询条件的第二查询消息,第二查询条件可以包括第二YANG模型的标识。接着,网管设备可以向网络设备发送第二查询消息,并接收来自网络设备的第二响应消息。第二响应消息是网络设备根据第二查询消息生成的,包括第二指示信息,用于指示网络设备对第二YANG模型的支持情况。
在一种可能的设计中,所述数据节点的节点标识包括所述数据节点在与所述第一YANG模型对应的结构树中的路径信息。
在一种可能的设计中,所述网管设备可以包括软件定义网络(Software Defined Network,SDN)控制器。
第二方面,提供了一种查询方法,该方法可以应用于部署有NETCONF客户端的网络设备。所述方法包括如下步骤:网络设备接收网管设备发送的第一查询消息,第一查询消息包括第一查询条件。接着,网络设备可以根据第一查询条件,从自身的存储空间中查询与第一查询条件对应的第一YANG模型中数据节点的节点标识,以及用于指示网络设备对所述数据节点的支持情况的第一指示信息。接着,网络设备可以根据数据节点的节点标识和第一指示信息生成第一响应消息,并向网管设备发送第一响应消息。这样,在接收到网管设备发动的第一查询消息之后,网络设备可以根据第一查询消息所携带的第一查询条件,从自身的第一YANG模型中确定对应的数据节点,并根据该数据节点的节点标识和支持情况生成第一响应消息。这样,由网管设备通过查询消息从网络设备处查询数据节点的支持情况,使得网管设备可以及时了解到数据节点的支持情况所发生的变化,更好的对网络设备进行管理。
在本申请实施例中,第一查询消息中的第一查询条件可以包括如下四种可能的实现方式:
实现方式一:第一查询条件包括数据节点的节点标识,相应地,第一查询消息用于根据数据节点的节点标识查询第一指示信息。可选地,在这种实现方式中,第一查询消息可以包括操作指令,该操作指令可以是NETCONF已有的操作指令,也可以是技术人员自定义的操作指令。那么在接收到第一查询消息之后,网络设备可以根据第一查询消息的第一查询条件中确定数据节点的节点标识,进而从第一YANG模型中获取第一指示信息。
实现方式二:第一查询条件包括第一查询指令。第一查询指令用于从网络设备的YANG库(YANG Library)中查询支持情况。YANG Library包括数据节点的节点标识和第一指示信息。具体地,网络设备可以将第一YANG模型中各个数据节点的支持情况存储在YANG Library中。相应地,在接收到第一查询消息之后,网络设备可以根据第一查询指令确定网管设备所查询的数据节点的支持情况在YANG Library中的存储位置,进而从YANG Library中获取第一指示信息,并生成第一响应消息。
实现方式三:第一查询条件包括第二查询指令,第二查询指令用于查询第一YAGN模型的结构(schema)信息,schema包括数据节点的节点标识和第一指示信息。与实现方式二类似,网络设备可以将多个YANG模型(包括第一YANG模型)中数据节点的支持情况存储在schema模型中。相应地,网络设备在接收到第一查询消息后,可以根据第二查询指令,从schema模型中获取数据节点的节点标识以及第一指示信息,从而生成第一响应消息。
实现方式四:第一查询条件包括文件名称,第一查询消息用于从与文件名称对应的文件中获取数据节点的节点标识和第一指示信息。具体地,网络设备可以将数据节点的节点标识和第一指示信息存储在文件中。在接收到第一查询消息之后,可以根据第一查询消息中第一查询条件从高与文件名称对应的文件中获取数据节点的节点标识和第一指示信息。
上述可能的实现方式中,第一查询消息可以为RPC消息,又称第一RPC消息。可选地,第一查询消息也可以用于建立网络设备与网管设备之间的订阅。第一响应消息可以为RPC响应(RPC Reply)消息,又称第一RPC响应消息。
在一种可能的设计中,网管设备还可以向网络设备查询网络设备对YANG模型的支持情况。具体地,网络设备可以接收网管设备发送的第二查询消息,第二查询消息包括第二查询条件,第二查询条件包括第二YANG模型的标识。在接收到第二查询消息之后,网络设备可以根据第二查询条件获取网络设备对第二YANG模型的支持情况,得到第二指示信息,第二指示信息用于指示网络设备对第二YANG模型的支持情况。接着,网络设备可以根据第二指示信息生成包括第二指示信息的第二响应消息并向网管设备发送。
在一种可能的设计中,如果网络设备对数据节点的支持情况为不支持,所述第一响应消息还包括所述数据节点的替换节点的节点标识,用于向网管设备通告不支持的数据节点被哪个数据节点替换。
在一种可能的设计中,所述数据节点的节点标识包括所述数据节点在与所述第一YANG模型对应的结构树中的路径信息。
在一种可能的设计中,所述网管设备可以包括软件定义网络(Software Defined Network,SDN)控制器。
第三方面,提供了一种查询装置,应用于网管设备,所述装置包括:处理单元,用于 生成第一查询消息,所述第一查询消息包括第一查询条件,所述第一查询条件用于获取网络设备的数据节点的节点标识和第一指示信息,所述节点标识用于标识所述网络设备中第一YANG模型的数据节点,所述第一指示信息用于指示所述网络设备对所述数据节点的支持情况;发送单元,用于向所述网络设备发送所述第一查询消息;接收单元,用于接收来自所述网络设备的第一响应消息,所述第一响应消息包括所述数据节点的节点标识和所述第一指示信息。
作为一种可能的设计,所述第一查询条件包括所述数据节点的节点标识,所述第一查询消息用于根据所述数据节点的节点标识查询所述第一指示信息。
作为一种可能的设计,所述第一查询条件包括第一查询指令,所述第一查询指令用于查询所述第一YANG模型的YANG库library,所述YANG library包括所述数据节点的节点标识和第一指示信息。
作为一种可能的设计,所述第一查询条件包括第二查询指令,所述第二查询指令用于查询所述第一YANG模型的结构schema信息,所述schema信息包括所述数据节点的节点标识和所述第一指示信息。
作为一种可能的设计,所述第一查询条件包括文件名称,所述第一查询消息用于从与所述文件名称对应的文件中获取所述数据节点的节点标识和所述第一指示信息。
作为一种可能的设计,所述第一查询消息为第一远程过程调用RPC消息。
作为一种可能的设计,所述第一响应消息包括第一RPC响应消息或通知notification消息。
作为一种可能的设计,所述处理单元,用于响应于生成第二RPC消息,生成第一查询消息,所述第二RPC消息用于对所述数据节点进行配置。
作为一种可能的设计,所述发送单元,还用于响应于所述第一指示信息指示所述网络设备支持所述数据节点,向所述网络设备发送所述第二RPC消息。
作为一种可能的设计,所述处理单元,用于响应于接收到第二RPC响应消息,生成第一查询消息,所述第二RPC响应消息用于指示所述数据节点配置失败。
作为一种可能的设计,所述第一响应消息还包括所述数据节点的替换节点的节点标识;所述发动单元,还用于向所述网络设备发送第三RPC消息,所述第三RPC消息用于对所述替换节点进行配置。
作为一种可能的设计,所述处理单元,用于响应于接收到反馈信息,生成第一查询消息,所述反馈信息用于指示许可证license已被激活或购买,所述数据节点为与所述license关联的数据节点。
作为一种可能的设计,所述处理单元,还用于生成第二查询消息,所述第二查询消息包括第二查询条件,所述第二查询条件包括第二YANG模型的标识;所述发送单元,还用于向所述网络设备发送所述第二查询消息;所述接收单元,还用于接收来自所述网络设备的第二响应消息,所述第二响应消息包括所述第二指示信息,所述第二指示信息用于指示所述网络设备对所述第二YANG模型的支持情况。
作为一种可能的设计,所述数据节点的节点标识包括所述数据节点在与所述第一 YANG模型对应的结构树中的路径信息。
作为一种可能的设计,所述网管设备包括软件定义网络SDN控制器。
第四方面,提供了一种查询装置,应用于网络设备,所述装置包括:接收单元,用于接收来自网管设备的第一查询消息,所述第一查询消息包括第一查询条件;处理单元,用于根据所述第一查询条件获取网络设备的第一YANG模型中数据节点的节点标识和第一指示信息,所述第一指示信息用于指示所述网络设备对所述数据节点的支持情况;生成第一响应消息,所述第一响应消息包括所述数据节点的节点标识和所述第一指示信息;发送单元,用于向所述网管设备发送所述第一响应消息。
作为一种可能的设计,所述第一查询条件包括所述数据节点的节点标识,所述第一查询消息用于根据所述数据节点的节点标识查询所述第一指示信息。
作为一种可能的设计,所述第一查询条件包括第一查询指令,所述第一查询指令用于查询所述第一YANG模型的YANG库library,所述YANG library包括所述数据节点的节点标识和第一指示信息。
作为一种可能的设计,所述第一查询条件包括第二查询指令,所述第二查询指令用于查询所述第一YANG模型的结构schema信息,所述schema信息包括所述数据节点的节点标识和所述第一指示信息。
作为一种可能的设计,所述第一查询条件包括文件名称,所述查询消息用于从与所述文件名称对应的文件中获取所述数据节点的节点标识和所述第一指示信息。
作为一种可能的设计,所述第一查询条件包括所述网络设备的设备标识,所述第一查询消息用于根据设备标识和对应关系获得所述数据节点的节点标识和所述第一指示信息,所述对应关系为所述设备标识与所述数据节点的节点标识和所述第一指示信息之间的对应关系。
作为一种可能的设计,所述第一查询消息为第一远程过程调用RPC消息。
作为一种可能的设计,所述第一响应消息包括第一RPC响应消息或通知notification消息。
作为一种可能的设计,所述接收单元,还用于接收第二查询消息,所述第二查询消息包括第二查询条件,所述第二查询条件包括第二YANG模型的标识;所述处理单元,还用于根据所述第二查询条件获取第二指示信息,所述第二指示信息用于指示所述网络设备对所述第二YANG模型的支持情况;生成第二响应消息,所述第二响应消息包括所述第二指示信息;所述发送单元,还用于向所述网管设备发送所述第二响应消息。
作为一种可能的设计,所述第一响应消息还包括所述数据节点的替换节点的节点标识。
作为一种可能的设计,所述数据节点的节点标识包括所述数据节点在与所述第一YANG模型对应的结构树中的路径信息。
作为一种可能的设计,所述网管设备包括软件定义网络SDN控制器。
第五方面,提供了一种网管设备,所述网络设备包括处理器芯片和存储器,存储器用于存储指令或程序代码,处理器芯片用于从存储器中调用并运行所述指令或程序代码,以执行如第一方面所述的查询方法。
第六方面,提供了一种网络设备,所述设备包括处理器芯片和存储器,存储器用于存储指令或程序代码,处理器芯片用于从存储器中调用并运行所述指令或程序代码,以执行如第二方面所述的查询方法。
第七方面,提供了一种计算机可读存储介质,包括指令、程序或代码,当其在计算机上执行时,使得所述计算机执行如第一方面或第二方面任一项所述的查询方法。
附图说明
图1为本申请实施例提供的NETCONF的一种应用场景的场景示意图;
图2为本申请实施例提供的查询方法可以应用的网络架构的场景示意图;
图3为本申请实施例提供的查询方法的一种信令交互图;
图4为本申请实施例提供的一种查询装置400的结构示意图;
图5为本申请实施例提供的一种查询装置500的结构示意图;
图6为本申请实施例提供的一种设备600的结构示意图;
图7为本申请实施例提供的一种设备700的结构示意图。
具体实施方式
首先对本申请实施例涉及的名词和概念进行介绍。
YANG(Yet Another Next Generation):最初被设计用来作为NETCONF的数据建模语言。
YANG模型:使用YANG数据建模语言建立的数据模型被称为是YANG模型。YANG模型可以部署在NETCONF客户端和服务器之间,定义可用于基于NETCONF的操作的数据层次结构。使用YANG模型实例化后的数据可以以可扩展标记语言(Extensible Markup Language,XML)或JavaScript(JS)对象简谱(JavaScript Object Notation,JSON)的编码格式存储。
YANG模型对象:YANG模型中的对象,例如YANG module set、模型module、数据节点(data node)、YANG数据包(package)等。
Module-set:模型的集合。
Module:定义了YANG模型数据的层次结构,被用于基于NETCONF的操作。一个module包括一个或多个数据节点,这些数据节点的分层组织被模型化为树的形式,每个数据节点都有一个名称或一个值或一组子节点,每个数据节点都能够被唯一标识。
YANG Library:RFC8525定义的用于让NETCONF client端获取server端目前正在使用的YANG modules和数据集的方式。
schema用于描述YANG的数据结构。Schema定义了网络设备中所有被管理的数据节点,以及各个数据节点之间的层次关系、读写属性和约束条件。在实际的应用场景中,不同供应商的Schema可以不同。
XML:XML是一种标记语言。在电子计算机中,标记指计算机所能理解的信息符号,通过此种标记,计算机之间可以处理包括各种的信息比如文章等。它可以用来标记数据、定义数据类型,是一种允许用户对自己的标记语言进行定义的源语言。XML文档中各个元素的位置可以通过XPath语言位置。
XPath语言:XPath语言可以将XML文档转为树形结构,并通过从根节点到元素所在的节点的路径表示XML文档中元素的位置。
RPC:RPC是一种远程调用方法,可以通过操作指令调用存储在网络设备中的命令行,并请求网络设备执行操作指令对应的命令行,完成相应的操作。
NETCONF消息:NETCONF消息为通过NETCONF传输的消息。NETCONF消息可以包括由网管设备发送的RPC消息、由网络设备发送的RPC Reply消息和由网络设备发送的通知(Notification)消息等
RPC消息:RPC消息为网管设备向网络设备发送的NETCONF消息,用于调用网络设备中预先存储的函数或方法,从而对网络设备进行管理。RPC消息中可以包括操作指令,用于请求网络设备执行相应的操作。通过RPC消息,网管设备可以调用存储在网络设备中的命令行,使得网络设备根据命令行执行相应的操作。
RPC响应消息:RPC响应消息为网络设备对RPC消息的响应消息,例如可以包括操作的执行结果。
Notification消息:notification消息为网络设备向网管设备发送的NETCONF消息,用于向网管设备通告预设事件的发生。在网络设备发送notification消息之前,网管设备可以先通过RPC消息与网络设备建立订阅(Subscription)。
对于上述各个名词的详细介绍,可以参见征求意见(Request For Comments,RFC)6241、RFC6536和RFC7950等协议的规定,这里不再赘述。
下面结合附图对传统技术和本申请实施例提供查询方法进行介绍。
参见图1,该图为本申请实施例提供的NETCONF的一种应用场景的场景示意图。在图1中,网络架构包括网管设备110以及网络设备120。其中,网络设备120中部署有YANG模型121,YANG模型121包括根节点121-1以及一个或多个数据节点121-2。其中,所述根节点121-1可以为模型(module),数据节点121-1为所述根节点121-1的叶子节点。网络设备120可以根据YANG模型121中数据节点的值进行工作。
网管设备110可以通过连接向网络设备120发送RPC消息。网络设备120可以通过连接向网管设备110发送RPC响应消息或notification消息。其中,RPC消息可以用于对YANG模型121中数据节点的值进行修改,实现对数据节点进行配置的目的。
YANG模型中的数据节点往往具有一定的生命周期。在网络设备120工作的过程中,YANG模型121中的数据节点的支持情况可能发生变化。例如网络设备120对数据节点121-1对应的功能的支持能力可能从支持变为不支持,或者,网络设备120对数据节点121-2对应的功能的支持程度可能发生改变等(关于支持情况的详细介绍请参见后文)。但是,在传统的NETCONF技术中,网络设备缺乏向网管设备通告数据节点的支持情况发生改变的手段,导致网管设备110无法及时了解到数据节点的支持情况所发生的改变,也就无法合理地对网络设备进行管理。例如,假设网络设备120对数据节点121-2的支持情况由支持变为不支持,但是网管设备110无法了解到数据节点121-2的支持情况所发生的改变,网管设备110仍可能生成用于对数据节点121-2进行配置的RPC消息。由于数据节点121-2 已不被网络设备120支持,网管设备对数据节点121-2的配置失败。可见,在传统的NETCONF场景下,由于无法及时了解到YANG模型中数据节点的支持情况的改变,网管设备不能较好地对网络设备进行管理。
为了解决上述问题,本申请实施例提供了一种查询方法,网管设备可以生成查询消息并向第一设备发送,请求网络设备上报数据节点的支持情况,从而使得网管设备能够较好地对网络设备进行管理。
本申请实施例提供的查询方法可以应用于图2所示的网络架构。在图2中,该网络架构包括网管设备210、一个或多个网络设备220以及服务器230。其中网管设备210分别与一个或多个网络设备220中的每个网络设备220连接,网管设备210还可以与服务器230连接。
网管设备210可以向网络设备220发送RPC消息。同样,网络设备220也可以通过连接向网管设备210发送RPC响应消息或notification消息。另外,在本申请实施例中,网络设备210还可以向服务器230发送消息,也可以接收服务器230发送的消息。网管设备210可以是SDN控制器等设备。网管设备210上可以部署NETCONF客户端(client)。
网络设备220可以是路由器(router)、交换机(switch)等支持路由功能的实体设备,也可以是部署虚拟路由器或虚拟交换机的服务器等。网络设备220上可以部署有NETCONF服务端(server)。每个网络设备220的NETCONF server上可以分别部署有与该网络设备对应的YANG模型。
服务器230上可以部署有一个或多个网络设备220中每个网络设备220对应的YANG模型,也可以部署部分网络设备的YANG模型或不部署YANG模型。
参见图3,该图为本申请实施例提供的查询方法的一种信令交互图,包括:
S301:网管设备生成查询消息。
在本申请实施例中,网管设备例如可以为图2所示的网管设备210。
所述网管设备生成的查询消息包括查询条件,所述查询条件用于获取网络设备的YANG模型中数据节点的节点标识和指示信息,指示信息用于指示所述网络设备对所述数据节点的支持情况。
其中,数据节点的节点标识用于唯一标识数据节点,例如可以包括数据节点的XPath信息,也可以包括数据节点的名称等信息。指示信息用于指示所述网络设备对所述数据节点的支持情况,数据节点的支持情况可以表示网络设备对数据节点对应的功能的支持能力,也可以表示网络设备对数据节点对应的功能的支持程度。其中,网络设备对数据节点对应的功能的支持的能力,包括但不限于网络设备对数据节点执行配置或查询等操作的能力。如果网络设备对数据节点的支持情况为不支持,说明网络设备无法使用数据节点对应的功能;如果网络设备对数据节点的支持情况为支持,说明网络设备能够使用数据节点对应的功能。数据节点的支持情况还可以用于指示网络设备部分支持数据节点,即能够使用数据节点对应的部分功能。
在本申请实施例中,查询消息可以用于从网络设备中查询数据节点的支持情况,也可以用于从服务器中查询数据节点的支持情况。如果查询消息用于从网络设备中查询数据节点的支持情况,查询消息可以是RPC消息。
在本申请实施例中,网管设备生成的查询消息中包括查询条件,在不同的场景下,查询条件可以有以下五种不同的实现方式。
在第一种实现方式中,查询条件包括数据节点的标识,查询消息用于根据数据节点的节点标识查询指示信息。可选地,数据节点的标识可以是数据节点在YANG模型中的XPath信息,查询消息可以是RPC消息。
具体地,在第一种实现方式中,查询消息中的操作指令可以有以下两种情况:
情况一:查询消息中的操作指令为自定义的操作指令。
在一些可能的实现方式中,技术人员可以定义用于获取数据节点的支持情况的新操作指令,那么查询消息可以包括该自定义的操作指令,用于控制网络设备根据该操作指令查询并上报数据节点的支持情况。这样,在接收到查询消息之后,网络设备可以执行该操作指令,从而查找与节点标识相对应的数据节点的支持情况。
可选地,假设技术人员定义的操作指令为节点支持情况获取(get-node-capability)指令,那么用于获取数据节点communitys的支持情况的RPC消息M1-1可以如下所示:
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<get-node-capability>
<node>
<node-selector>/snmp:snmp/snmp:communitys</node-selector>
</node>
</get-node-capability>
</rpc>
其中,RPC消息M1-1的第一行为RPC消息M1-1的消息层,表示RPC消息M1-1属于RPC消息,且RPC消息M1-1的XML命名空间(XML Namespaces,xmlns)为urn:ietf:params:xml:ns:netconf:base:1.0。RPC消息M1-1的第二行为RPC消息M1-1的操作层,表示RPC消息M1-1中携带的操作指令为get-node-capability指令,用于获取网络设备的数据节点的支持情况。RPC消息M1-1的第三行到第五行为RPC消息M1-1的内容层,表示RPC消息M1-1用于请求简单网络管理协议(Simple Network Management Protocol,SNMP)中communitys这个节点的支持情况。
再比如,用于获取数据节点local-storage-limit的RPC消息M1-2可以如下所示:
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<get-node-capability>
<node-selector>
/example-syslog/syslog/local-storage-limit
</node-selector>
</get-node-capability>
</rpc>
该RPC消息M1-2可以用于获取XPath信息为/example-syslog/syslog/local-storage-limit的数据节点local-storage-limit的支持情况。
情况二:查询消息中的操作指令为NETCONF已有的操作指令。
在上述RPC请求消息M1-2和RPC请求消息M2-2中,操作指令为技术人员定义的get-node-capability指令,并非NETCONF已有的操作指令。在另一些可能的实现方式中,操作指令也可以是NETCONF已有的操作指令。例如可以是get指令、get-data指令get-config指令或订阅创建(create-subscription)指令。
当查询消息中的操作指令为get指令、get-data指令或get-config指令时,网络设备可以将数据节点的支持情况存储在YANG模型中。例如,可以在网络设备中新建目标YANG模型,该目标YANG模型用于存储网络设备对于数据节点的支持情况,为技术人员在网络设备中定义的新的YANG模型。这样,网管设备可以通过NETCONF中已有的指令(例如get指令、get-data指令或get-config指令)和数据节点的节点标识(例如数据节点在目标YANG模型中的XPath信息)生成RPC消息。具体地,网管设备生成的RPC请求消息M2-1可以如下所示:
Figure PCTCN2022101370-appb-000001
其中,RPC请求消息M2-1的第一行为RPC请求消息M2-1的消息层,表示RPC请求消息M2-1属于RPC消息,且RPC请求消息M-12的信息标识(message-id)为101。RPC请求消息M2-1的第二行为RPC请求消息M2-1的操作层,表示RPC请求消息M2-1中携带的操作指令为get指令,用于获取网络设备的信息。RPC请求消息M2-1第三行到第六行为RPC请求消息M2-1的内容层。其中RPC请求消息M2-1的第三行表示get指令对应的xmlns为http://example.com/schema/1.2/config,即目标YANG模型存储的统一资源定位符(Uniform Resource Locator,URL)为http://example.com/schema/1.2/config的文件中。RPC请求消息M2-1的第四行表示数据节点的标识的类型(type)为XPath语言类型,即RPC请求消息M2-1的第五行中元素为XPath语言格式。RPC请求消息M2-1的第五行表示get指令所针对的数据节点为communitys,且该数据节点communitys的XPath信息为snmp:snmp/snmp:communitys。
可见,通过上述RPC请求消息M2-1,网管设备可以向网络设备请求获取URL为http://example.com/schema/1.2/config的YANG模型中XPath为/ync:yang-node-capability/ync:node[ync:nodeselector=”/snmp:snmp/snmp:communitys的节点的支持情况。
根据前文介绍可知,网络设备在运行时可能导致网络设备的YANG模型中数据节点的支持情况发生变化。为了及时知晓数据节点的支持情况的变化,网络设备还可以向网络设备发起针对数据节点的支持情况的变化的订阅。这样,如果网络设备检测到自身的YANG模型中数据节点的支持情况发生,网络设备可以主动生成通知(notification)消息并向网管设备发送,以使网管设备能够知晓网络设备的YANG模型中数据节点的支持情况发生变化。
在建立订阅的过程中,网管设备可以生成包括create-subscription指令和预设事件的RPC消息,以使网络设备在预设事件被触发时生成并上报notification消息。那么对于网络设备上报支持情况的场景来说,该用于创建订阅的RPC消息即为查询消息。即,查询消息中的操作指令可以包括订阅创建(create-subscription)指令,查询消息还可以包括订阅对应的预设事件,该预设事件为数据节点的支持情况发生改变。
具体地,网管设备生成的RPC消息M2-2可以如下所示:
<netconf:rpc message-id="101"
xmlns:netconf="urn:ietf:params:xml:ns:netconf:base:1.0">
<create-subscription
xmlns="urn:ietf:params:xml:ns:netconf:notification:1.0">
<filter type=”subtree”>
<yang-capability-changes/>
</filter>
<startTime>2021-06-28T14:55:00Z</startTime>
<stopTime>2021-06-28T23:59:59Z</stopTime>
</create-subscription>
</netconf:rpc>
其中,RPC消息M2-2的第三行表示RPC消息M2-2对应的操作指令为订阅创建(create-subscription),用于在网管设备和网络设备之间创建订阅;RPC消息M2-2的第六行表示网管设备创建的订阅的类型为yang-capability-changes,表示预设时间为数据节点的支持情况发生改变,说明网管设备发起订阅的目的是使网络设备在检测到数据节点的支持情况发生变化后通知网管设备;RPC消息M2-2的第八行用于体现订阅开始的时间,RPC消息M2-2的第九行用于体现订阅结束的时间。
在第二种实现方式中,查询条件包括第一查询指令。第一查询指令用于对网络设备的YANG Library进行查询。相应地,查询条件可以包括YANG Library的标识和操作指令,查询消息可以为RPC消息。
具体地,网络设备可以将数据节点的支持情况存储在YANG Library中。其中,YANG Library是用于存储YANG模型的信息的YANG模型。为了在YANG Library中存储数据节点的支持情况,可以在YANG Library中添加节点,并通过新增的节点存储数据节点的支持情况。
举例说明。对于YANG模型A中的数据节点B,网络设备可以在YANG Library中数据节点B对应的节点下新增一个子节点(后称节点C),用于记录数据节点B的支持情况。 这样,如果网管设备想要确定数据节点B的支持情况,网管设备可以通过NETCONF已有的指令(例如get指令、get-data指令或get-config指令)、YANG Library的标识和节点C的节点标识生成RPC消息D。网络设备在接收到RPC消息D之后,可以根据节点标识从YANG Library中确定节点C,并将节点C的值通过RPC响应消息发送给网管设备。由于节点C用于存储数据节点A的支持情况,节点C的值能够体现数据节点A的支持情况。
可选地,节点C的节点标识例如可以是节点C的XPath信息,YANG Library的标识例如可以是YANG Library的xmlns。具体地,网管设备生成的RPC消息M3可以如下所示:
Figure PCTCN2022101370-appb-000002
上述RPC消息M3可以用于查询YANG Library中名称为config-modules的模型集(module-set)所存储的支持情况。相应地,数据节点的支持情况被存储在YANG Library的config-modules这一模型集中。
在这种可能的实现方式中,一条查询消息可以用于查询多个数据节点的支持情况。例如,假设模型集config-modules存储了多个数据节点的支持情况,那么RPC消息M3可以用于获取多个数据节点的支持情况。在一些可能的实现中,查询消息也可以不包括模型集的名称,那么该查询消息可以用于查询多个模型集所存储的支持情况。即,如果RPC消息M3不包括<name>config-modules</name>,那么RPC消息M3可以用于查询YANG Library的多个模型集中每个模型集所存储的支持情况。
在第三种实现方式中,查询条件包括第二查询指令。第二查询指令用于查询所述YANG模型的结构schema信息。相应地,查询条件可以包括schema模型的标识和操作指令,查询消息可以为RPC消息。根据RFC6025的规定,网络设备中可以包括Schema模型,该Schema模型能够提供网络设备的监控信息,可以用于网管设备对网络设备进行监控。在本申请实施例中,可以在Schema模型中netconf-state/schemas这支子树下添加数据节点的支 持情况。相应地,网管设备生成的RPC消息可以从netconf-state/schemas子树下查找数据节点的支持情况。具体地,网管设备生成的RPC消息M4可以如下所示:
Figure PCTCN2022101370-appb-000003
在以上三种可能的实现方式中,数据节点的支持情况存储在网络设备中,因此查询消息为RPC消息,网管设备可以通过查询消息从网络设备中查找数据节点的支持情况。在一些可能的实现方式中,数据节点的支持情况还可以存储在服务器中,那么网管设备生成的查询条件可以有以下两种可能的实现方式。
需要说明的是,以下两种可能的实现方式所提供的查询消息也可以适用于数据节点的支持情况存储在网络设备的场景。
在第四种实现方式中,查询条件包括文件名称,查询消息用于从服务器的文件中获取所述数据节点的节点标识和所述指示信息。
如果网络设备的YANG模型中数据节点的支持情况被存储在服务器中,那么查询条件可以包括存储有支持情况的文件的名称。这样,服务器在接收到查询消息之后,可以根据查询条件确定待查询的文件的名称,再根据节点标识从文件中查找数据节点的支持情况。可选地,数据节点的节点标识可以是数据节点的名称。查询消息还可以包括文件路径。
在第五种实现方式中,查询条件包括网络设备的设备标识,查询消息用于根据设备标识和对应关系获得数据节点的节点标识和指示信息,对应关系为设备标识与数据节点的节点标识和指示信息之间的对应关系。
如果服务器中存储有多个网络设备的数据节点的支持情况,由于不同网络设备的YANG模型可能较为相似,那么为了便于对网络设备的YANG模型进行管理,服务器可以建立数据节点与网络设备之间的对应关系,用于区分不同网络设备的数据节点。
举例说明。假设数据节点A和数据节点B的名称均为“communitys”,且数据节点A为网络设备C的YANG模型中的数据节点,对应的指示信息a用于指示网络设备C对数据节点A的支持情况;数据节点B为网络设备D的YANG模型中的数据节点,对应的额指示信息b用于指示网络设备D对数据节点B的支持情况。那么服务器可以建立网络设备C的标识与数据节点A的标识和指示信息a之间的对应关系,以及网络设备D的标识与数据节点B的标识和指示信息b之间的对应关系。
这样,如果网管设备想要查询数据节点B的支持情况,网管设备生成的查询消息中可以包括网络设备D的标识。服务器在接收到查询消息后,可以根据网络设备D的标识确定网管设备想要查询的数据节点属于网络设备D,从而根据对应关系确定数据节点B的节点标识和指示信息b。
上面对查询消息进行了介绍,在本申请实施例中,查询消息用于对数据节点的支持情况进行查询。其中,支持情况可以表示网络设备对功能的支持能力,也可以表示网络设备对功能的支持程度。下面分别对两种可能的实现进行介绍。
在第一种实现方式中,支持情况表示网络设备对数据节点对应的功能的支持与否。即,数据节点的支持情况可以体现网络设备是否有能力实现数据节点对应的功能。如果网络设备对数据节点的支持情况为支持,说明网络设备能够实现该数据节点对应的功能。如果网络设备对数据节点的支持情况为不支持,说明网络设备无法实现该数据节点对应的功能。
可选地,支持情况可以通过数据节点的状态(status)所声明的值体现。根据RFC7950的规定,YANG模型中数据节点的Status所声明的值可以是推荐(current)、不推荐(deprecated)和废弃(obsolete)中的任意一种。其中current表示数据节点在当前的YANG模型中是有效的;deprecated表示数据节点不被建议使用,但是网络设备仍然具有实现该数据节点对应的功能的能力;obsolete表示数据节点不被网络设备支持。那么如果数据节点的声明的值为current或deprecated,说明网络设备能够实现数据节点对应的功能,网络设备对数据节点的支持情况为支持;如果数据节点的声明的值为obsolete,说明网络设备不具有实现数据节点对应的功能的能力,网络设备对数据节点的支持情况为不支持。需要说明的是,在一些可能的实现中Status所声明的值可以为deprecated的数据节点的支持情况也可能是不支持。
在上报数据节点的支持情况时,网络设备可以上报数据节点的声明的值,也可以直接上报数据节点的支持情况。
有关current、deprecated和obsolete三种状态的详细介绍可以参见RFC7950,这里不再赘述。
在第二种实现方式中,支持情况表示网络设备对数据节点对应的功能的支持程度。也就是说,数据节点的支持情况可以表示网络设备在实现数据节点对应的功能时,能够采用的参数范围。例如,在未激活许可(license)的情况下,网络设备允许接入无线局域网(Wireless Local Area Network,WLAN)的接入控制器(Access Point,AP)设备的最大数量为16个,而在激活license的情况下,网络设备允许接入WLAN的AP设备的最大数量为512个。显然,在激活license和未激活license两种情况下,网络设备对“允许AP设备接入WLAN”的支持能力不同。
上面对查询消息和支持情况进行了介绍,下面介绍网管设备生成查询消息的方法。
在本申请实施例中,生成查询消息可以是网管设备主动触发的,也可以是由网管设备在接收到来自网络设备的消息(例如RPC响应消息)之后触发的。在不同的场景下,网管设备生成查询消息可以有以下四种可能的实现方式。
在第一种实现方式中,网管设备可以主动生成查询消息。
具体地,网管设备中可以设置有计时器,每经过预设时间间隔生成一条查询消息并向第一设备发送。如此,可以定期更新网络设备对数据节点的支持情况,便于网管设备对网络设备进行管理。
在第二种实现方式中,网管设备可以在发送RPC消息之前生成查询消息。
网管设备可以通过RPC消息对网络设备进行管理,例如对网络设备的YANG模型中的数据节点进行配置。那么在向网络设备发送RPC消息之前,网络设备可以先生成查询消息,通过查询消息对数据节点的支持情况进行查询,并根据查询结果执行相应的操作。
举例说明。假设RPC消息X用于对数据节点A进行配置,那么在向网络设备发送RPC消息X之前,网络设备可以先生成查询消息Y,该查询消息Y包括数据节点A的节点标识,用于查询网络设备读数据节点A的支持情况。在接收到网络设备返回的响应消息之后,如果响应消息中的指示信息指示网络设备支持数据节点A,网管设备可以向网络设备发送RPC消息X。
在第三种实现方式中,网管设备可以在接收到网络设备发送的RPC响应消息之后生成查询消息。
在网管设备对网络设备进行管理的过程中,网管设备可以生成用于对数据节点进行配置的RPC消息并向网络设备发送。网络设备可以对RPC消息进行处理,并通过RPC响应消息通知网管设备RPC消息的配置结果。如果网络设备对该数据节点配置失败,网络设备可以向网管设备发送RPC响应消息,以通知网管设备对数据节点的配置失败。那么,在接收到RPC响应消息之后,网管设备可以生成查询消息,通过查询消息判断配置失败是否是网络设备不再支持数据节点导致的。
举例说明。假设RPC消息X用于对数据节点A进行配置,但是网络设备不再支持数据节点A,那么在接收到RPC消息之后,网络设备不对数据节点A进行处理,并会生成RPC响应消息Y,通过RPC响应消息Y通知网管设备对数据节点A的配置失败。
在接收到RPC响应消息Y后,网管设备可以根据RPC响应消息Y确定网络设备未能对数据节点A进行处理。为了确定对数据节点A处理失败的原因,网管设备可以生成查询消息,从而查询网络设备对数据节点A的支持情况。如果数据节点A的支持情况为不支持,说明RPC消息X处理失败的原因是网络设备不再支持数据节点A。
在第四种实现方式中,网管设备可以在接收到反馈信息之后生成查询消息。
在网络设备工作的过程中,license可能被激活或购买。License用于允许网络设备进行进一步的处理。可选地,网络设备可以在license被激活或购买之后向网管设备发送反馈信息。网络设备在接收到反馈信息后,可以知晓网络设备的license被激活或购买。
网络设备的功能可能随着license被激活或购买发生改变。相应地,网络设备对其YANG模型中数据节点的支持情况也可能发生改变。例如,在未激活license的情况下,网络设备允许接入WLAN的AP设备的最大数量为16个,而在激活license的情况下,网络设备允许接入WLAN的AP设备的最大数量为512个。显然,在激活license和未激活license两种情况下,网络设备对“允许AP设备接入WLAN”这一功能对应的数据节点的支持能力不同。
在license被激活或购买之后,网管设备可以生成查询消息并向网络设备发送,从而了解license被激活或购买给数据节点的支持情况带来的变化。相应地,查询消息所包括的节点标识可以是与license相关联的节点标识。
在上述可能的实现方式中,查询消息用于对数据节点的支持情况进行查询。在一些可能的实现中,网管设备生成的查询消息也可以用于查询网络设备对YANG模型的支持情况,那么查询消息可以包括YANG模型的标识。
S302:网管设备向第一设备发送查询消息。
在生成查询消息之后,网管设备可以向第一设备发送查询消息。在本申请实施例中,第一设备可以是服务器或网络设备,例如可以是图2所示的网络设备220,或者是图2所示的服务器230。
S303:第一设备获取指示信息。
在接收到查询消息之后,第一设备可以根据查询消息中的查询条件获取指示信息,其中,指示信息用于指示所述网络设备对所述数据节点的支持情况。具体地,第一设备可以根据查询消息查询数据节点的支持情况,进而根据数据节点的支持情况得到指示信息。
根据前文介绍可知,第一设备可以是网络设备或服务器,下面分别介绍第一设备为网络设备和第一设备为服务器这两种情况下,第一设备查询数据节点的支持情况的实现方式。
在第一种实现方式中,第一设备为网络设备。相应地,网管设备向第一设备发送的查询消息属于RPC消息。
根据NETCONF协议,在接收到网管设备发送的查询消息之后,网络设备可以执行RPC消息所包括的操作指令,从而获取指示信息。其中,指示信息可以包括数据节点的支持情况。根据前文介绍可知,RPC消息中可以包括自定义的操作指令,也可以包括已有的操作指令。下面分别对这两种可能的情况进行介绍。
情况一:RPC消息包括技术人员定义的操作指令(例如get-node-capability指令)。
根据NETCONF协议,在新的操作指令被定义后,用于执行该新的操作指令的程序或代码会被存储到网络设备中。那么,在检测到RPC消息中的操作指令后,网络设备可以根据RPC消息确定网管设备所查询的数据节点,并调用执行所存储的程序或代码,确定该数据节点的支持情况,得到指示信息。可选地,RPC消息可以包括数据节点的节点标识,那么网络设备可以根据节点标识确定网管设备所查询的数据节点。
情况2:RPC消息包括NETCONF中传统的操作指令。
根据前文介绍可知,当RPC消息中的操作指令为get等传统的操作指令时,RPC消息还包括数据节点的支持情况在网络设备中存储位置的标识。那么在接收到RPC消息之后,网络设备可以执行操作指令,从RPC消息所包括的存储位置获取数据节点的支持情况,得到指示信息。
根据前文介绍可知,RPC消息可以用于从YANG Library或Schema模型中获取数据节点的支持情况。相应地,网络设备在接收到RPC消息后,可以根据YANG Library或Schema模型确定指示信息。
可选地,如果网络设备将数据节点的支持情况存储在YANG Library或Schema模型中, RPC消息可以不包括数据节点的标识,而是包括存储支持情况的子节点的父节点的节点标识。例如,在前文介绍中,RPC消息M4不包括具体的某个数据节点的标识,而是包括Schema模型中存储支持情况的多个子节点的父节点schemas的标识。相应地,在获取指示信息时,如果RPC消息不包括数据节点的节点标识,而是包括父节点的节点标识,网络设备可以分别获取父节点的多个子节点中每个子节点所存储的支持情况和该子节点对应的数据节点,得到多个数据节点的支持情况,进而根据多个数据节点的支持情况确定指示信息。
在第二种实现方式中,第一设备为服务器。相应地,查询消息可以包括文件名称或网络设备的标识。那么在接收到查询消息后,服务器可以对查询消息进行解析,确定待查询的数据节点的支持情况在服务器中的存储位置,进而得到数据节点的支持情况。
根据前文介绍可知,网管设备发送的查询消息还可以用于查询网络设备对YANG模型的支持情况。相应地,第一设备根据该查询消息生成的指示信息可以用于指示网络设备对YANG模型的支持情况。
S304:第一设备根据指示信息生成响应消息。
在得到数据节点的支持情况之后,第一设备可以根据指示信息生成响应消息。该响应消息可以包括数据节点的节点标识和指示信息,用于向网管设备通告网络设备对所查询的数据节点的支持情况。
下面以第一设备为网络设备为例进行说明。相应地,响应消息可以是RPC响应消息或notification消息。下面分别进行介绍。
在第一种实现方式中,响应消息可以是RPC响应消息。那么,网络设备生成的RPC响应消息可以包括数据节点的标识和对应的指示信息。
具体地,如果数据节点的支持情况可以包括网络设备对数据节点对应的功能的支持与否,可以在RPC响应消息中新增一个字段,并通过新增加的字段携带数据节点的支持情况。如果数据节点的支持情况表示网络设备对数据节点对应的功能的支持程度,可以在RPC响应消息中新增至少两个字段,分别用于携带网络设备对数据节点对应的功能的支持与否和支持程度。其具体实现可以如下示例1-示例5所示。
示例1:
如果RPC消息中操作指令为技术人员自定义的get-node-capability指令,数据节点communitys的支持情况为不支持,且被数据节点standard-communities代替的情况,那么网络设备生成的RPC响应消息M5可以如下所示:
Figure PCTCN2022101370-appb-000004
Figure PCTCN2022101370-appb-000005
其中,RPC响应消息M5的第三行表示RPC响应消息M5是与包括get-node-capability指令的RPC消息相对应的RPC响应消息;RPC响应消息M5的第五行表示RPC响应消息M5用于上报数据节点communitys的支持情况;RPC响应消息M5的第六行表示数据节点communitys在YANG模型中的status所声明的值为deprecated RPC响应消息M5的第七行表示网络设备对数据节点communitys的支持情况为不支持(non-supported);RPC响应消息M5的第八行表示数据节点communitys被数据节点standard-communities代替。示例2:
网管设备向网络设备发送了RPC请求消息M1-2。相应地,网络设备生成的RPC响应消息M6可以如下所示:
<rpc message-id="101"
xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<get-node-capability>
<node>
<node-selector>
/example-syslog/syslog/local-storage-limit
</node-selector>
<Status>current</status>
<Support>partial-supported</support>
<description>current maximize value is 128kb(default 512kb)because of an unpurchased license</description>
</node>
</get-node-capability>
</rpc>
其中,RPC响应消息M6的第三行表示RPC响应消息M6是与包括get-node-capability指令的RPC消息M1-2相对应的RPC响应消息;RPC响应消息M6的第五行到第七行表示RPC响应消息M6用于上报数据节点local-storage-limit的支持情况,且该数据节点local-storage-limit在YANG模型中的XPath信息为example-syslog/syslog;RPC响应消息M6的第八行表示数据节点local-storage-limit的Status所声明的值为current;RPC响应消息M6的第九行表示数据节点local-storage-limit的支持情况为部分支持(partial-supported);RPC响应消息M6的第十行和第十一行为对部分支持的具体描述,表示数据节点local-storage-limit支持的最大值为128kb,且数据节点local-storage-limit支持的最大值不为512kb的原因是未购买license。
示例3:
数据节点communitys的支持情况被存储在网络设备的YANG Library中,相应地,网络设备生成的RPC响应消息M7可以如下所示:
Figure PCTCN2022101370-appb-000006
其中,RPC响应消息M7的第五行和第六行表示RPC响应消息M7中的内容为/yang-library子树的实例化结果。RPC响应消息M7的第七行和第八行表示RPC响应消息M7中所包括的该设备目前支持的module set(名称为config-modules)。RPC响应消息M7的第九行和第十行表示RPC响应消息M7所包括的支持情况来自名称为A-snmp.yang的YANG模块(module)。RPC响应消息M7的第十四行表示RPC响应消息M7包括数据节点communitys的支持情况,且数据节点communitys的XPath信息为/snmp:snmp/snmp:communitys。RPC响应消息M7的第十六行表示数据节点communitys的Status所声明的值为deprecated;RPC响应消息M7的第十七行表示数据节点communitys的支持情况为不支持(non-supported);RPC响应消息M7的第十八行表示数据节点communitys被数据节点standard-communities代替。
在S301的介绍中,数据节点的支持情况还可以被存储在目标YANG模型或Schema中。那么网络设备生成的RPC响应消息可以如示例4或示例5所示。
示例4:
节点的支持情况被存储在目标YANG模型中,网络设备生成的RPC响应消息M8可以如下所示。
Figure PCTCN2022101370-appb-000007
其中,RPC响应消息M8的第三行表示RPC响应消息M8是与包括get-node-capability指令的RPC消息相对应的RPC响应消息,RPC响应消息M8其余各行的内容与RPC响应消息M5基本一致,这里不再赘述。
示例5:
节点的支持情况被存储在Schema模型中,网络设备生成的RPC响应消息M9可以如下所示:
<rpc-reply message-id="101"
xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<data>
<netconf-state
xmlns="urn:ietf:params:xml:ns:yang:ietf-netconf-monitoring">
<schemas>
<schema>
<identifier>A-snmp</identifier>
<version>2017-04-11</version>
<format>yang</format>
<namespace>urn:A:yang:A-snmp</namespace>
<location>
http://example.com/schema/A-snmp.yang
</location>
<location>NETCONF</location>
<node>
<node-selector>/snmp:snmp/snmp:communitys</node-selector>
<status>deprecated</status>
<supported>non-supported</supported>
<recommanded>"/snmp:snmp/snmp:standard-communities"</recommanded>
</node>
</schema>
</schemas>
</netconf-state>
</data>
</rpc-reply>
其中,RPC响应消息M9的第八行至第十二行表示RPC响应消息M9中携带的数据节点的支持信息来自Schema模型A-snmp,且Schema模型A-snmp更新时间为2017.4.11,对应的URL为http://example.com/schema/A-snmp.yang。其余各行的内容与RPC响应消息M7基本一致,这里不再赘述。
在第二种可能的实现方式中,响应消息为notification消息。
根据S301的介绍可知,网管设备可以通过create-subscription指令在网络设备上创建订阅。在订阅被创建后,如果网络设备检测到数据节点的支持情况发生改变,网络设备可以生成notification消息并向网管设备发送,以使网管设备知晓数据节点的支持情况发生改变。与前述RPC响应消息类似,notification消息也可以包括指示信息,指示信息包括数据节点的支持情况。具体地,网管设备生成的notification消息M10可以如下6所示。
Figure PCTCN2022101370-appb-000008
其中,notification消息M10的第二行表示事件的发生时间为2021年6与28日16点51分00秒。notification消息M10的第三行表示notification消息M10是针对yang-capability-changes类型的订阅的notification消息。notification消息M10的第五行表示网络设备上报的事件名为license-enabled-bgp-sessions。notification消息M10的第六行表示 支持情况发生改变的数据节点名称为/bgp/sessions;notification消息M10的第七行表示数据节点/bgp/sessions的支持情况的变化类型为调整(modified);notification消息M10的第八行和第九行表示数据节点/bgp/sessions的支持的边界网关协议(Border Gateway Protocol,BGP)会话(BGP session)的最大数量从20个增加到50个,且支持情况改变是由license被激活(enabled)导致的;notification消息M10的第十行表示license是由NETCONF会话标识(netconf session ID)为101的客户端(client)激活的。
当第一设备为服务器时,服务器可以将数据节点的节点标识和支持情况携带在响应消息中向网管设备发送。服务器生成响应消息的方法与前述网络设备生成响应消息的方法类似,这里不再赘述。
根据前文介绍可知,网管设备生成的查询消息可以用于查询网络设备对YANG模型的支持情况。相应地,第一设备生成的响应消息可以包括指示信息,该指示信息用于指示网络设备对YANG模型的支持情况。
S305:第一设备向网管设备发送响应消息。
在生成RPC响应消息之后,第一设备可以向网管设备发送RPC响应消息,以使网管设备能够知晓网络设备中数据节点的支持情况。
S306:网管设备根据响应消息执行相应的操作。
在接收到第一设备发送的响应消息之后,网管设备可以根据响应消息执行相应地操作。
根据S301中的介绍可知,查询消息可以在发送RPC消息之前生成,也可以在接收到RPC响应消息之后生成。在本申请实施例中,根据网管设备生成查询消息的时间不同,网管设备在接收到响应消息之后执行的操作可以有以下两种可能的实现方式。
在第一种可能的实现方式中,查询消息由网管设备在发送RPC消息之前生成。即查询消息用于查询RPC消息所针对的数据节点的支持情况。那么在接收到响应消息之后,网管设备可以根据数据节点的支持情况发送RPC消息或不发送RPC消息。
具体地,如果网络设备对数据节点的支持情况为支持,说明网络设备能够实现数据节点对应的功能,网管设备可以向网络设备发送RPC消息。如果网络设备对数据节点的支持情况为不支持,说明网络设备不能实现数据节点对应的功能,即使网管设备向网络设备发送了RPC消息,也无法成功地对数据节点进行配置。因此,网管设备可以不继续向网络设备发送RPC消息。
根据前文介绍可知,响应消息还可以包括数据节点的替换节点的相关信息。那么,如果响应消息包括替换节点的相关信息且网管设备接收到的响应消息指示数据节点的支持情况为不支持,那么网络设备可以根据响应消息对待发送的RPC消息进行修改,并向网络设备发送修改后的RPC消息,从而对替换节点进行配置。
在第二种可能的实现中,查询消息由网络设备在接收到用于指示数据节点配置失败的RPC响应消息后生成。那么在接收到响应消息后,网管设备可以根据数据节点的支持情况修改RPC消息,或进一步对网络设备进行故障检测。
具体地,如果网络设备对数据节点的支持情况为不支持,说明对数据节点配置失败是网络设备不支持数据节点导致的。如果响应消息包括替换节点的相关信息,例如替换节点 的节点标识,网络设备可以根据替换节点的相关信息修改配置失败的RPC消息,并向网络设备发送新的RPC消息。如果网络设备对数据节点的支持情况为支持,说明对数据节点配置失败不是网络设备不支持数据节点导致的,网管设备可以对网络设备进行进一步的故障排查,确定导致数据节点配置失败的原因。
在本申请实施例中,网管设备可以生成查询消息并向第一设备发送RPC消息,使得第一设备根据查询消息获取数据节点的支持情况,并通过响应消息返回给网管设备。在接收到第一设备返回的响应消息之后,网管设备可以根据响应消息执行相应的操作。这样,由网管设备通过查询消息从第一设备处查询数据节点的支持情况,使得网管设备可以及时了解到数据节点的支持情况所发生的变化,更好的对网络设备进行管理。
参见图4,本申请实施例还提供了一种查询装置400,该查询装置400可以实现图3所示实施例中网管设备的功能。该查询装置400包括处理单元401、发送单元402和接收单元403。其中,处理单元401用于实现图3所示实施例中的S301,发送单元402用于实现图3所示实施例中的S302和S306;接收单元403用于接收网络设备在执行图3所示实施例中S305的过程中所发送的响应消息。
具体的,处理单元401,用于生成第一查询消息,所述第一查询消息包括第一查询条件,所述第一查询条件用于获取网络设备的数据节点的节点标识和第一指示信息,所述节点标识用于标识所述网络设备中第一YANG模型的数据节点,所述第一指示信息用于指示所述网络设备对所述数据节点的支持情况。
发送单元402,用于向第一设备发送所述查询消息。
接收单元403,用于接收来自所述网络设备的第一响应消息,所述第一响应消息包括所述数据节点的节点标识和所述第一指示信息。
具体执行过程请参考上述图3所示实施例中相应步骤的详细描述,这里不再一一赘述。
参见图5,本申请实施例还提供了一种查询装置500,该查询装置500可以实现图3所示实施例中第一设备(例如网络设备)的功能。该查询装置500包括接收单元501、处理单元502和发送单元503。其中,接收单元501用于接收网管设备在执行图3所示实施例中S302的过程中所发送的查询消息,处理单元502用于实现图3所示实施例中的S303和S304;发送单元403用于实现图3所示实施例中的S305。
具体的,接收单元501,用于接收来自网管设备的第一查询消息,所述第一查询消息包括第一查询条件。
处理单元502,用于根据所述第一查询条件获取网络设备的第一YANG模型中数据节点的节点标识和第一指示信息,所述第一指示信息用于指示所述网络设备对所述数据节点的支持情况;生成第一响应消息,所述第一响应消息包括所述数据节点的节点标识和所述第一指示信息。
发送单元503,用于向所述网管设备发送所述第一响应消息。
具体执行过程请参考上述图3所示实施例中相应步骤的详细描述,这里不再一一赘述。
图6是本申请实施例提供的一种设备600的结构示意图。上文中的查询装置400或查询装置500可以通过图6所示的设备来实现。参见图6,该设备600包括至少一个处理器601,通信总线602以及至少一个网络接口604,可选地,该设备600还可以包括存储器603。
处理器601可以是中央处理器(central processing unit,CPU),网络处理器(network processor,NP)或者CPU和NP的组合。在一种实现方式中,处理器601还可为流量管理(traffic management,TM)芯片或者是集成了NP和TM芯片的硬件,TM芯片或者集成了NP和TM芯片的硬件可对TM芯片中的队列执行本申请实施例提供的调度队列的方法。处理器1010还可以进一步包括硬件芯片。上述硬件芯片可以是专用集成电路(application-specific integrated circuit,ASIC),可编程逻辑器件(programmable logic device,PLD)或其组合。上述PLD可以是复杂可编程逻辑器件(complex programmable logic device,CPLD),现场可编程逻辑门阵列(field-programmable gate array,FPGA),通用阵列逻辑(generic array logic,GAL)或其任意组合。处理器可以用于对数据报文进行更新或校验,以实现本申请实施例中提供的查询方法。
比如,当图3中的网管设备通过图6所示的设备来实现时,该处理器可以用于:生成第一查询消息,通过网络接口604向所述网络设备发送所述第一查询消息,接收来自所述网络设备的第一响应消息。当图3中的第一设备通过图6所示的设备来实现时,该处理器可以用于:接收来自网管设备的第一查询消息,根据所述第一查询条件获取网络设备的第一YANG模型中数据节点的节点标识和第一指示信息,生成第一响应消息,并通过网络接口604向所述网管设备发送所述第一响应消息。
通信总线602用于在处理器601、网络接口604和存储器603之间传送信息。总线系统602可以是外设部件互连标准(peripheral component interconnect,PCI)总线或扩展工业标准结构(extended industry standard architecture,EISA)总线等。总线系统602可以分为地址总线、数据总线、控制总线等,图6中仅用一条粗线表示,但并不表示仅有一根总线或一种类型的总线。
存储器603可以是只读存储器(read-only memory,ROM)或可存储静态信息和指令的其它类型的静态存储设备,存储器603还可以是随机存取存储器(random access memory,RAM)或者可存储信息和指令的其它类型的动态存储设备,也可以是只读光盘(compact disc read-only Memory,CD-ROM)或其它光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其它磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其它介质,但不限于此。存储器603可以是独立存在,通过通信总线602与处理器601相连接。存储器603也可以和处理器601集成在一起。
可选地,存储器603用于存储执行本申请方案的程序代码或指令,并由处理器601来控制执行。处理器601用于执行存储器603中存储的程序代码或指令。程序代码中可以包括一个或多个软件模块。可选地,处理器601也可以存储执行本申请方案的程序代码或指令,在这种情况下处理器601不需要到存储器603中读取程序代码或指令。
网络接口604可以为收发器一类的装置,用于与其它设备或通信网络通信,通信网络可以为以太网、无线接入网(RAN)或无线局域网(wireless local area networks,WLAN)等。在本申请实施例中,网络接口604可以用于接收分段路由网络中的其他节点发送的报文,也可以向分段路由网络中的其他节点发送报文。网络接口604可以为以太接口(ethernet)接口、快速以太(fast ethernet,FE)接口或千兆以太(gigabit ethernet,GE)接口等。
在具体实现中,作为一种实施例,设备600可以包括多个处理器,例如图6中所示的处理器601和处理器605。这些处理器中的每一个可以是一个单核(single-CPU)处理器,也可以是一个多核(multi-CPU)处理器。这里的处理器可以指一个或多个设备、电路、和/或用于处理数据(例如计算机程序指令)的处理核。
图7是本申请实施例提供的一种设备700的结构示意图。图3中的网管设备和第一设备中任意一个或多个设备可以通过图7所示的设备来实现。
参见图7所示的设备结构示意图,设备700包括主控板和一个或多个接口板。主控板与接口板通信连接。主控板也称为主处理单元(main processing unit,MPU)或路由处理卡(route processor card),主控板包括CPU和存储器,主控板负责对设备700中各个组件的控制和管理,包括路由计算、设备管理和维护功能。接口板也称为线处理单元(line processing unit,LPU)或线卡(line card),用于接收和发送报文。在一些实施例中,主控板与接口板之间或接口板与接口板之间通过总线通信。在一些实施例中,接口板之间通过交换网板通信,在这种情况下设备700也包括交换网板,交换网板与主控板、接口板通信连接,交换网板用于转发接口板之间的数据,交换网板也可以称为交换网板单元(switch fabric unit,SFU)。接口板包括CPU、存储器、转发引擎和接口卡(interface card,IC),其中接口卡可以包括一个或多个网络接口。网络接口可以为Ethernet接口、FE接口或GE接口等。CPU与存储器、转发引擎和接口卡分别通信连接。存储器用于存储转发表。转发引擎用于基于存储器中保存的转发表转发接收到的报文,如果接收到的报文的目的地址为设备700的IP地址,则将该报文发送给主控板或接口板的CPU进行处理;如果接收到的报文的目的地址不是设备700的IP地址,则根据该目的地查转发表,如果从转发表中查找到该目的地址对应的下一跳和出接口,将该报文转发到该目的地址对应的出接口。转发引擎可以是网络处理器(network processor,NP)。接口卡也称为子卡,可安装在接口板上,负责将光电信号转换为数据帧,并对数据帧进行合法性检查后转发给转发引擎处理或接口板CPU。在一些实施例中,CPU也可执行转发引擎的功能,比如基于通用CPU实现软转发,从而接口板中不需要转发引擎。在一些实施例中,转发引擎可以通过ASIC或现场可编程门阵列(field programmable gate array,FPGA)实现。在一些实施例中,存储转发表的存储器也可以集成到转发引擎中,作为转发引擎的一部分。
本申请实施例还提供一种芯片系统,包括:处理器,所述处理器与存储器耦合,所述存储器用于存储程序或指令,当所述程序或指令被所述处理器执行时,使得该芯片系统实现上述图3所示实施例中提供的查询方法。
可选地,该芯片系统中的处理器可以为一个或多个。该处理器可以通过硬件实现也可 以通过软件实现。当通过硬件实现时,该处理器可以是逻辑电路、集成电路等。当通过软件实现时,该处理器可以是一个通用处理器,通过读取存储器中存储的软件代码来实现。
可选地,该芯片系统中的存储器也可以为一个或多个。该存储器可以与处理器集成在一起,也可以和处理器分离设置,本申请并不限定。示例性的,存储器可以是非瞬时性处理器,例如只读存储器ROM,其可以与处理器集成在同一块芯片上,也可以分别设置在不同的芯片上,本申请对存储器的类型,以及存储器与处理器的设置方式不作具体限定。
示例性的,该芯片系统可以是FPGA,可以是ASIC,还可以是系统芯片(system on chip,SoC),还可以是CPU,还可以是NP,还可以是数字信号处理电路(digital signal processor,DSP),还可以是微控制器(micro controller unit,MCU),还可以是可编程控制器(programmable logic device,PLD)或其他集成芯片。
应理解,上述方法实施例中的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。结合本申请实施例所公开的方法步骤可以直接体现为硬件处理器执行完成,或者用处理器中的硬件及软件模块组合执行完成。
本申请实施例还提供了一种计算机可读存储介质,包括指令,当其在计算机上运行时,使得计算机执行以上方法实施例提供的、由网管设备执行的查询方法,或由第一设备执行的查询方法。
本申请实施例还提供了一种包含指令的计算机程序产品,当其在计算机上运行时,使得计算机执行以上方法实施例提供的、由网管设备执行的查询方法,或由第一设备执行的查询方法。
本申请的说明书和权利要求书及上述附图中的术语“第一”、“第二”、“第三”、“第四”等(如果存在)是用于区别类似的对象,而不必用于描述特定的顺序或先后次序。应该理解这样使用的数据在适当情况下可以互换,以便这里描述的实施例能够以除了在这里图示或描述的内容以外的顺序实施。此外,术语“包括”和“具有”以及他们的任何变形,意图在于覆盖不排他的包含,例如,包含了一系列步骤或单元的过程、方法、系统、产品或设备不必限于清楚地列出的那些步骤或单元,而是可包括没有清楚地列出的或对于这些过程、方法、产品或设备固有的其它步骤或单元。
所属领域的技术人员可以清楚地了解到,为描述的方便和简洁,上述描述的系统,装置和单元的具体工作过程,可以参考前述方法实施例中的对应过程,在此不再赘述。
在本申请所提供的几个实施例中,应该理解到,所揭露的系统,装置和方法,可以通过其它的方式实现。例如,以上所描述的装置实施例仅仅是示意性的,例如,所述单元的划分,仅仅为一种逻辑模块划分,实际实现时可以有另外的划分方式,例如多个单元或组件可以结合或者可以集成到另一个系统,或一些特征可以忽略,或不执行。另一点,所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口,装置或单元的间接耦合或通信连接,可以是电性,机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的,作为单元显示的部件可以是或者也可以不是物理单元,即可以位于一个地方,或者也可以分布到多个网络单元上。可以根据实际的需要获取其中的部分或者全部单元来实现本实施例方案的目的。
另外,在本申请各个实施例中的各模块单元可以集成在一个处理单元中,也可以是各个单元单独物理存在,也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现,也可以采用软件模块单元的形式实现。
所述集成的单元如果以软件模块单元的形式实现并作为独立的产品销售或使用时,可以存储在一个计算机可读取存储介质中。基于这样的理解,本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来,该计算机软件产品存储在一个存储介质中,包括若干指令用以使得一台计算机设备(可以是个人计算机,服务器,或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括:U盘、移动硬盘、只读存储器(ROM,Read-Only Memory)、随机存取存储器(RAM,Random Access Memory)、磁碟或者光盘等各种可以存储程序代码的介质。
本领域技术人员应该可以意识到,在上述一个或多个示例中,本发明所描述的功能可以用硬件、软件、固件或它们的任意组合来实现。当使用软件实现时,可以将这些功能存储在计算机可读介质中或者作为计算机可读介质上的一个或多个指令或代码进行传输。计算机可读介质包括计算机存储介质和通信介质,其中通信介质包括便于从一个地方向另一个地方传送计算机程序的任何介质。存储介质可以是通用或专用计算机能够存取的任何可用介质。
以上所述的具体实施方式,对本发明的目的、技术方案和有益效果进行了进一步详细说明,所应理解的是,以上所述仅为本发明的具体实施方式而已。
以上所述,以上实施例仅用以说明本申请的技术方案,而非对其限制;尽管参照前述实施例对本申请进行了详细的说明,本领域的普通技术人员应当理解:其依然可以对前述各实施例所记载的技术方案进行修改,或者对其中部分技术特征进行等同替换;而这些修改或者替换,并不使相应技术方案的本质脱离本申请各实施例技术方案的范围。

Claims (57)

  1. 一种查询方法,其特征在于,所述方法包括:
    网管设备生成第一查询消息,所述第一查询消息包括第一查询条件,所述第一查询条件用于获取网络设备的数据节点的节点标识和第一指示信息,所述节点标识用于标识所述网络设备中第一YANG模型的数据节点,所述第一指示信息用于指示所述网络设备对所述数据节点的支持情况;
    所述网管设备向所述网络设备发送所述第一查询消息;
    所述网管设备接收来自所述网络设备的第一响应消息,所述第一响应消息包括所述数据节点的节点标识和所述第一指示信息。
  2. 根据权利要求1所述的方法,其特征在于,所述第一查询条件包括所述数据节点的节点标识,所述第一查询消息用于根据所述数据节点的节点标识查询所述第一指示信息。
  3. 根据权利要求1所述的方法,其特征在于,所述第一查询条件包括第一查询指令,所述第一查询指令用于查询所述第一YANG模型的YANG库library,所述YANG library包括所述数据节点的节点标识和第一指示信息。
  4. 根据权利要求1所述的方法,其特征在于,所述第一查询条件包括第二查询指令,所述第二查询指令用于查询所述第一YANG模型的结构schema信息,所述schema信息包括所述数据节点的节点标识和所述第一指示信息。
  5. 根据权利要求1所述的方法,其特征在于,所述第一查询条件包括文件名称,所述第一查询消息用于从与所述文件名称对应的文件中获取所述数据节点的节点标识和所述第一指示信息。
  6. 根据权利要求1-5任一项所述的方法,其特征在于,所述第一查询消息为第一远程过程调用RPC消息。
  7. 根据权利要求6所述的方法,其特征在于,所述第一响应消息包括第一RPC响应消息或通知notification消息。
  8. 根据权利要求1-7任一项所述的方法,其特征在于,所述网管设备生成第一查询消息包括:
    响应于生成第二RPC消息,所述网管设备生成第一查询消息,所述第二RPC消息用于对所述数据节点进行配置。
  9. 根据权利要求8所述的方法,其特征在于,所述方法还包括:
    响应于所述第一指示信息指示所述网络设备支持所述数据节点,所述网管设备向所述网络设备发送所述第二RPC消息。
  10. 根据权利要求1-7任一项所述的方法,其特征在于,所述网管设备生成第一查询消息包括:
    响应于接收到第二RPC响应消息,所述网管设备生成第一查询消息,所述第二RPC响应消息用于指示所述数据节点配置失败。
  11. 根据权利要求10所述的方法,其特征在于,所述第一响应消息还包括所述数据节点的替换节点的节点标识;所述方法还包括:
    所述网管设备向所述网络设备发送第三RPC消息,所述第三RPC消息用于对所述替换节点进行配置。
  12. 根据权利要求1-7任一项所述的方法,其特征在于,所述网管设备生成第一查询消息包括:
    响应于接收到反馈信息,所述网管设备生成第一查询消息,所述反馈信息用于指示许可证license已被激活或购买,所述数据节点为与所述license关联的数据节点。
  13. 根据权利要求1-12任一项所述的方法,其特征在于,所述方法还包括:
    所述网管设备生成第二查询消息,所述第二查询消息包括第二查询条件,所述第二查询条件包括第二YANG模型的标识;
    所述网管设备向所述网络设备发送所述第二查询消息;
    所述网管设备接收来自所述网络设备的第二响应消息,所述第二响应消息包括所述第二指示信息,所述第二指示信息用于指示所述网络设备对所述第二YANG模型的支持情况。
  14. 根据权利要求1-13任一项所述的方法,其特征在于,所述数据节点的节点标识包括所述数据节点在与所述第一YANG模型对应的结构树中的路径信息。
  15. 根据权利要求1-14任一项所述的方法,其特征在于,所述网管设备包括软件定义网络SDN控制器。
  16. 一种查询方法,其特征在于,所述方法包括:
    网络设备接收来自网管设备的第一查询消息,所述第一查询消息包括第一查询条件;
    所述网络设备根据所述第一查询条件获取网络设备的第一YANG模型中数据节点的节点标识和第一指示信息,所述第一指示信息用于指示所述网络设备对所述数据节点的支持情况;
    所述网络设备生成第一响应消息,所述第一响应消息包括所述数据节点的节点标识和所述第一指示信息;
    所述网络设备向所述网管设备发送所述第一响应消息。
  17. 根据权利要求16所述的方法,其特征在于,所述第一查询条件包括所述数据节点的节点标识,所述第一查询消息用于根据所述数据节点的节点标识查询所述第一指示信息。
  18. 根据权利要求16所述的方法,其特征在于,所述第一查询条件包括第一查询指令,所述第一查询指令用于查询所述第一YANG模型的YANG库library,所述YANG library包括所述数据节点的节点标识和第一指示信息。
  19. 根据权利要求16所述的方法,其特征在于,所述第一查询条件包括第二查询指令,所述第二查询指令用于查询所述第一YANG模型的结构schema信息,所述schema信息包括所述数据节点的节点标识和所述第一指示信息。
  20. 根据权利要求16所述的方法,其特征在于,所述第一查询条件包括文件名称,所述查询消息用于从与所述文件名称对应的文件中获取所述数据节点的节点标识和所述第一指示信息。
  21. 根据权利要求16所述的方法,其特征在于,所述第一查询条件包括所述网络设备的设备标识,所述第一查询消息用于根据设备标识和对应关系获得所述数据节点的节点标 识和所述第一指示信息,所述对应关系为所述设备标识与所述数据节点的节点标识和所述第一指示信息之间的对应关系。
  22. 根据权利要求16-21任一项所述的方法,其特征在于,所述第一查询消息为第一远程过程调用RPC消息。
  23. 根据权利要求22所述的方法,其特征在于,所述第一响应消息包括第一RPC响应消息或通知notification消息。
  24. 根据权利要求16-23任一项所述的方法,其特征在于,所述方法还包括:
    所述网络设备接收第二查询消息,所述第二查询消息包括第二查询条件,所述第二查询条件包括第二YANG模型的标识;
    所述网络设备根据所述第二查询条件获取第二指示信息,所述第二指示信息用于指示所述网络设备对所述第二YANG模型的支持情况;
    所述网络设备生成第二响应消息,所述第二响应消息包括所述第二指示信息;
    所述网络设备向所述网管设备发送所述第二响应消息。
  25. 根据权利要求16-24任一项所述的方法,其特征在于,所述第一响应消息还包括所述数据节点的替换节点的节点标识。
  26. 根据权利要求16-25任一项所述的方法,其特征在于,所述数据节点的节点标识包括所述数据节点在与所述第一YANG模型对应的结构树中的路径信息。
  27. 根据权利要求16-26任一项所述的方法,其特征在于,所述网管设备包括软件定义网络SDN控制器。
  28. 一种查询装置,其特征在于,应用于网管设备,所述装置包括:
    处理单元,用于生成第一查询消息,所述第一查询消息包括第一查询条件,所述第一查询条件用于获取网络设备的数据节点的节点标识和第一指示信息,所述节点标识用于标识所述网络设备中第一YANG模型的数据节点,所述第一指示信息用于指示所述网络设备对所述数据节点的支持情况;
    发送单元,用于向所述网络设备发送所述第一查询消息;
    接收单元,用于接收来自所述网络设备的第一响应消息,所述第一响应消息包括所述数据节点的节点标识和所述第一指示信息。
  29. 根据权利要求28所述的装置,其特征在于,所述第一查询条件包括所述数据节点的节点标识,所述第一查询消息用于根据所述数据节点的节点标识查询所述第一指示信息。
  30. 根据权利要求28所述的装置,其特征在于,所述第一查询条件包括第一查询指令,所述第一查询指令用于查询所述第一YANG模型的YANG库library,所述YANG library包括所述数据节点的节点标识和第一指示信息。
  31. 根据权利要求28所述的装置,其特征在于,所述第一查询条件包括第二查询指令,所述第二查询指令用于查询所述第一YANG模型的结构schema信息,所述schema信息包括所述数据节点的节点标识和所述第一指示信息。
  32. 根据权利要求28所述的装置,其特征在于,所述第一查询条件包括文件名称,所述第一查询消息用于从与所述文件名称对应的文件中获取所述数据节点的节点标识和所述 第一指示信息。
  33. 根据权利要求28-32任一项所述的装置,其特征在于,所述第一查询消息为第一远程过程调用RPC消息。
  34. 根据权利要求33所述的装置,其特征在于,所述第一响应消息包括第一RPC响应消息或通知notification消息。
  35. 根据权利要求28-34任一项所述的装置,其特征在于,
    所述处理单元,用于响应于生成第二RPC消息,生成第一查询消息,所述第二RPC消息用于对所述数据节点进行配置。
  36. 根据权利要求35所述的装置,其特征在于,
    所述发送单元,还用于响应于所述第一指示信息指示所述网络设备支持所述数据节点,向所述网络设备发送所述第二RPC消息。
  37. 根据权利要求28-36任一项所述的装置,其特征在于,
    所述处理单元,用于响应于接收到第二RPC响应消息,生成第一查询消息,所述第二RPC响应消息用于指示所述数据节点配置失败。
  38. 根据权利要求37所述的装置,其特征在于,所述第一响应消息还包括所述数据节点的替换节点的节点标识;
    所述发动单元,还用于向所述网络设备发送第三RPC消息,所述第三RPC消息用于对所述替换节点进行配置。
  39. 根据权利要求28-34任一项所述的装置,其特征在于,
    所述处理单元,用于响应于接收到反馈信息,生成第一查询消息,所述反馈信息用于指示许可证license已被激活或购买,所述数据节点为与所述license关联的数据节点。
  40. 根据权利要求28-39任一项所述的装置,其特征在于,
    所述处理单元,还用于生成第二查询消息,所述第二查询消息包括第二查询条件,所述第二查询条件包括第二YANG模型的标识;
    所述发送单元,还用于向所述网络设备发送所述第二查询消息;
    所述接收单元,还用于接收来自所述网络设备的第二响应消息,所述第二响应消息包括所述第二指示信息,所述第二指示信息用于指示所述网络设备对所述第二YANG模型的支持情况。
  41. 根据权利要求28-40任一项所述的装置,其特征在于,所述数据节点的节点标识包括所述数据节点在与所述第一YANG模型对应的结构树中的路径信息。
  42. 根据权利要求28-41任一项所述的装置,其特征在于,所述网管设备包括软件定义网络SDN控制器。
  43. 一种查询装置,其特征在于,应用于网络设备,所述装置包括:
    接收单元,用于接收来自网管设备的第一查询消息,所述第一查询消息包括第一查询条件;
    处理单元,用于根据所述第一查询条件获取网络设备的第一YANG模型中数据节点的节点标识和第一指示信息,所述第一指示信息用于指示所述网络设备对所述数据节点的支 持情况;生成第一响应消息,所述第一响应消息包括所述数据节点的节点标识和所述第一指示信息;
    发送单元,用于向所述网管设备发送所述第一响应消息。
  44. 根据权利要求43所述的装置,其特征在于,所述第一查询条件包括所述数据节点的节点标识,所述第一查询消息用于根据所述数据节点的节点标识查询所述第一指示信息。
  45. 根据权利要求43所述的装置,其特征在于,所述第一查询条件包括第一查询指令,所述第一查询指令用于查询所述第一YANG模型的YANG库library,所述YANG library包括所述数据节点的节点标识和第一指示信息。
  46. 根据权利要求43所述的装置,其特征在于,所述第一查询条件包括第二查询指令,所述第二查询指令用于查询所述第一YANG模型的结构schema信息,所述schema信息包括所述数据节点的节点标识和所述第一指示信息。
  47. 根据权利要求43所述的装置,其特征在于,所述第一查询条件包括文件名称,所述查询消息用于从与所述文件名称对应的文件中获取所述数据节点的节点标识和所述第一指示信息。
  48. 根据权利要求43所述的装置,其特征在于,所述第一查询条件包括所述网络设备的设备标识,所述第一查询消息用于根据设备标识和对应关系获得所述数据节点的节点标识和所述第一指示信息,所述对应关系为所述设备标识与所述数据节点的节点标识和所述第一指示信息之间的对应关系。
  49. 根据权利要求43-48任一项所述的装置,其特征在于,所述第一查询消息为第一远程过程调用RPC消息。
  50. 根据权利要求49所述的装置,其特征在于,所述第一响应消息包括第一RPC响应消息或通知notification消息。
  51. 根据权利要求43-50任一项所述的装置,其特征在于,
    所述接收单元,还用于接收第二查询消息,所述第二查询消息包括第二查询条件,所述第二查询条件包括第二YANG模型的标识;
    所述处理单元,还用于根据所述第二查询条件获取第二指示信息,所述第二指示信息用于指示所述网络设备对所述第二YANG模型的支持情况;生成第二响应消息,所述第二响应消息包括所述第二指示信息;
    所述发送单元,还用于向所述网管设备发送所述第二响应消息。
  52. 根据权利要求43-51任一项所述的装置,其特征在于,所述第一响应消息还包括所述数据节点的替换节点的节点标识。
  53. 根据权利要求43-52任一项所述的装置,其特征在于,所述数据节点的节点标识包括所述数据节点在与所述第一YANG模型对应的结构树中的路径信息。
  54. 根据权利要求43-53任一项所述的装置,其特征在于,所述网管设备包括软件定义网络SDN控制器。
  55. 一种网管设备,其特征在于,所述网络设备包括处理器芯片和存储器,存储器用于存储指令或程序代码,处理器芯片用于从存储器中调用并运行所述指令或程序代码,以执 行如权利要求1-15任一项所述的查询方法。
  56. 一种网络设备,其特征在于,所述设备包括处理器芯片和存储器,存储器用于存储指令或程序代码,处理器芯片用于从存储器中调用并运行所述指令或程序代码,以执行如权利要求16-32任一项所述的查询方法。
  57. 一种计算机可读存储介质,其特征在于,包括指令、程序或代码,当其在计算机上执行时,使得所述计算机执行如权利要求1-32任一项所述的查询方法。
PCT/CN2022/101370 2021-07-30 2022-06-27 一种查询方法、装置及设备 WO2023005543A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110875171.9 2021-07-30
CN202110875171.9A CN115695134A (zh) 2021-07-30 2021-07-30 一种查询方法、装置及设备

Publications (1)

Publication Number Publication Date
WO2023005543A1 true WO2023005543A1 (zh) 2023-02-02

Family

ID=85060100

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/101370 WO2023005543A1 (zh) 2021-07-30 2022-06-27 一种查询方法、装置及设备

Country Status (2)

Country Link
CN (1) CN115695134A (zh)
WO (1) WO2023005543A1 (zh)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180131745A1 (en) * 2016-11-04 2018-05-10 Google Inc. Network Management Interface
WO2019233616A1 (en) * 2018-06-06 2019-12-12 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for merging of yang configuration and state data in model-driven applications
CN112307486A (zh) * 2019-07-29 2021-02-02 华为技术有限公司 一种权限获取方法、设备和系统

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180131745A1 (en) * 2016-11-04 2018-05-10 Google Inc. Network Management Interface
WO2019233616A1 (en) * 2018-06-06 2019-12-12 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for merging of yang configuration and state data in model-driven applications
CN112307486A (zh) * 2019-07-29 2021-02-02 华为技术有限公司 一种权限获取方法、设备和系统

Also Published As

Publication number Publication date
CN115695134A (zh) 2023-02-03

Similar Documents

Publication Publication Date Title
JP4509916B2 (ja) Snmp基盤のネットワーク管理装置および方法
US9264326B2 (en) Abstract representation and provisioning of network services
US10097397B2 (en) System and method for managing CWSN with GUI
US11252035B2 (en) Data configuration method and apparatus
JP2007188505A (ja) ネットワーク対応デバイスの管理方法及び媒体
JP2010507298A (ja) 目標ipネットワークの論理的配備、配備解除、及び監視のための方法
CN101447895A (zh) 同步网管与网元的配置的方法和装置
CN110580256A (zh) 一种识别应用标识的方法、设备及系统
US10237124B2 (en) Network operation, administration, and maintenance (OAM) method, apparatus, and system
US8924544B2 (en) Techniques for sessionless reporting by device management client
CN106850268B (zh) 一种线性保护倒换的实现装置及方法
CN101404594B (zh) 热备份性能的测试方法与装置、通信设备
EP4030810A1 (en) Method and device for confirming in-situ flow information telemetry capability
WO2023005543A1 (zh) 一种查询方法、装置及设备
CN109194519B (zh) 网络设备的配置方法、装置、控制器及计算机存储介质
CN115514719A (zh) 报文发送方法、装置、交换机及可读存储介质
CN113381875B (zh) 用于获取配置数据的方法
WO2023279848A1 (zh) 一种查询方法、装置及设备
CN114531392A (zh) 组播业务设计方法、服务器及存储介质
US8352592B2 (en) Controlling emission of events from managed systems to external management systems
US7685303B2 (en) Object-oriented discovery framework
CN105765903A (zh) 一种拓扑发现方法及设备
WO2021052248A1 (zh) 链路资源发现方法、装置、设备及计算机可读存储介质
EP4040728A1 (en) Filtering information configuration method and system
WO2020224413A1 (zh) 负荷控制方法、服务提供者nf及服务使用者nf

Legal Events

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

Ref document number: 22848150

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE