WO2016110070A1 - 数据获取方法及装置、存储介质 - Google Patents
数据获取方法及装置、存储介质 Download PDFInfo
- Publication number
- WO2016110070A1 WO2016110070A1 PCT/CN2015/083098 CN2015083098W WO2016110070A1 WO 2016110070 A1 WO2016110070 A1 WO 2016110070A1 CN 2015083098 W CN2015083098 W CN 2015083098W WO 2016110070 A1 WO2016110070 A1 WO 2016110070A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- data
- data acquisition
- proxy device
- management device
- unit
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/40—Network security protocols
Definitions
- the present invention relates to a network management technology based on the NETCONF protocol, and in particular, to a data acquisition method and apparatus, and a storage medium.
- the NETCONF management device In the system that implements network device configuration management by using the NETCONF protocol, the NETCONF management device (Manager) usually obtains the data by using the get/getconfig method when acquiring various configuration management data of the agent device. When the amount of data is large, The response message may be too large to be sent, causing the get operation to be unsuccessful.
- the management device when acquiring data, the management device often only needs to acquire a part of data of a sub-tree in the configuration management information of the network device, and does not need to acquire data of all sub-trees, although the management device can obtain all the sub-tree information and then Data filtering is performed, but this data acquisition method is inefficient and unreasonably increases network traffic.
- an embodiment of the present invention provides a data acquisition method and apparatus, and a storage medium.
- a method of data acquisition comprising:
- the management device confirms whether the proxy device supports the extended data acquisition operation, and sends an extended data acquisition request to the proxy device after confirming the support;
- the data acquisition request carries the operation parameter of the filter condition, where the filter condition includes Specify the identification information of the object;
- the management device After receiving the data response message sent by the proxy device, the management device acquires data corresponding to the specified object identifier from the data response packet.
- the management device confirms whether the proxy device supports extended data acquisition operations, including:
- the management device sends a capability query request to the proxy device, and receives a capability response sent by the proxy device, and confirms whether the proxy device supports the extended data acquisition operation according to the capability information carried in the capability response.
- the data is tree structure data based on Extensible Markup Language (XML);
- the data acquisition request carries at least a filter filter parameter
- the filter parameter includes an attribute type and an identifier of the data object to be acquired, and the type is a mibtree, indicating that the data is queried by the object.
- the method further includes:
- the management device establishes a connection with the proxy device.
- a method of data acquisition comprising:
- the proxy device locally queries the data corresponding to the specified object identifier, and encapsulates the queried data in the response packet of the data acquisition request, and sends the response packet to the management device.
- the method before the proxy device receives the extended data acquisition request sent by the management device, the method further includes:
- the proxy device receives the capability query request sent by the management device, confirms whether it supports the extended data acquisition operation, and sends an information capability response carrying the data acquisition operation supporting the extension to the management device when confirming the support.
- the data is tree structure data based on Extensible Markup Language (XML);
- the data acquisition request carries at least a filter filter parameter
- the filter parameter includes an attribute type and an identifier of the data object to be acquired, and the type is a mibtree, indicating that the data is queried by the object.
- the method before the proxy device receives the extended data acquisition request sent by the management device, the method further includes:
- the proxy device establishes a connection with the management device.
- a data acquisition device includes: a confirmation unit, a transmission unit, a receiving unit, and an acquisition unit, wherein:
- a confirmation unit configured to confirm whether the proxy device supports the extended data acquisition operation, and trigger the sending unit when confirming the support
- a sending unit configured to send an extended data acquisition request to the proxy device;
- the data acquisition request carries an operation parameter of a filtering condition, where the filtering condition includes identifier information of the specified object;
- a receiving unit configured to receive a data response message sent by the proxy device
- an acquiring unit configured to acquire data corresponding to the specified object identifier from the data response packet.
- the confirming unit includes: a sending subunit, a receiving subunit, and an confirming subunit, wherein:
- a sending subunit configured to send a capability query request to the proxy device
- a receiving subunit configured to receive a capability response sent by the proxy device
- the confirmation subunit is configured to confirm whether the proxy device supports the extended data acquisition operation according to the capability information carried in the capability response.
- the data is a tree structure based on Extensible Markup Language XML data
- the data acquisition request carries at least a filter filter parameter
- the filter parameter includes an attribute type and an identifier of the data object to be acquired, and the type is a mibtree, indicating that the data is queried by the object.
- a data acquisition device includes: a receiving unit, a parsing and obtaining unit, a query unit, and a sending unit, wherein:
- a receiving unit configured to receive an extended data acquisition request sent by the management device
- the parsing unit is configured to parse the data acquisition request, and at least obtain an operation parameter that carries the filter condition of the specified object identifier in the data acquisition request;
- the query unit is configured to locally query the data corresponding to the specified object identifier
- the sending unit is configured to encapsulate the queried data in the response message of the data acquisition request, and send the response message to the management device.
- the device further includes: a confirmation unit;
- the receiving unit is further configured to receive a capability query request sent by the management device;
- the confirmation unit is configured to confirm whether it supports the extended data acquisition operation, and triggers the sending unit to send an information capability response carrying the data acquisition operation supporting the extension to the management device when the support is confirmed.
- the data is tree structure data based on Extensible Markup Language (XML);
- the data acquisition request carries at least a filter filter parameter
- the filter parameter includes an attribute type and an identifier of the data object to be acquired, and the type is a mibtree, indicating that the data is queried by the object.
- a storage medium having stored therein a computer program configured to perform the data acquisition method.
- filtering is added for the data acquisition operation by expanding the data acquisition operation.
- the operational parameter of the condition which can obtain the data of the specified object from the proxy device.
- the technical solution of the embodiment of the present invention can obtain the data of an object in the model accurately and flexibly by using the extended get/get-config operation to obtain the data in the XML model after using the technical solution adopted by the present invention.
- the data of nested objects that are not concerned or not needed will not be returned, so the response data message will be greatly reduced, which greatly increases the proportion of valid data in the message, reduces bandwidth usage and improves bandwidth utilization.
- FIG. 1 is a flowchart of a data acquisition method according to Embodiment 1 of the present invention.
- FIG. 2 is a flowchart of a data acquisition method according to Embodiment 2 of the present invention.
- FIG. 3 is a flowchart of a capability negotiation between a management device and a proxy device according to an embodiment of the present invention
- FIG. 4 is a flowchart of data acquisition between a management device and a proxy device according to an embodiment of the present invention
- FIG. 5 is a flowchart of performing data query by a proxy device according to an embodiment of the present invention.
- FIG. 6 is a schematic structural diagram of a data acquiring apparatus according to Embodiment 1 of the present invention.
- FIG. 7 is a schematic structural diagram of a data acquisition apparatus according to Embodiment 2 of the present invention.
- FIG. 1 is a flowchart of a data acquisition method according to Embodiment 1 of the present invention. As shown in FIG. 1 , the data acquisition method of this example includes the following steps:
- Step 101 The management device confirms whether the proxy device supports the extended data acquisition operation, and sends an extended data acquisition request to the proxy device after confirming the support.
- the data acquisition request carries an operation parameter of a filter condition, where the filter condition includes identifier information of the specified object.
- the data is tree structure data based on Extensible Markup Language XML;
- the data acquisition request carries at least a filter filter parameter
- the filter parameter includes an attribute type and an identifier of the data object to be acquired, and the type is a mibtree, indicating that the data is queried by the object.
- the proxy device locally queries the data corresponding to the specified object, and encapsulates the queried data in the response packet of the data acquisition request, and sends the response packet to the management device.
- Step 102 After receiving the data response message sent by the proxy device, the management device acquires data corresponding to the specified object identifier from the data response message.
- the management device After receiving the data response message sent by the proxy device, the management device directly obtains the specified data from the response packet.
- the technical solution of the embodiment of the present invention can obtain the data of an object in the model accurately and flexibly by using the extended get/get-config operation to obtain the data in the XML model after using the technical solution adopted by the present invention.
- the data of nested objects that are not concerned or not needed will not be returned, so the response data message will be greatly reduced, which greatly increases the proportion of valid data in the message, reduces bandwidth usage and improves bandwidth utilization.
- the management device before the management device confirms whether the proxy device supports the extended data acquisition operation, the management device establishes a connection with the proxy device.
- FIG. 2 is a flowchart of a data acquisition method according to Embodiment 2 of the present invention. As shown in FIG. 2, the data acquisition method of this example includes the following steps:
- Step 201 The proxy device receives the extended data acquisition request sent by the management device, parses the data acquisition request, and acquires at least the operation parameter of the filter condition that carries the specified object identifier in the data acquisition request.
- the management device first sends an extended data acquisition request to the proxy device.
- the method further includes:
- the proxy device receives the capability query request sent by the management device, confirms whether it supports the extended data acquisition operation, and sends an information capability response carrying the data acquisition operation supporting the extension to the management device when confirming the support.
- the data is tree structure data based on the extensible markup language XML;
- the data acquisition request carries at least a filter parameter;
- the filter parameter includes an attribute type and an identifier of the data object to be acquired, and the type is a mibtree, indicating that the data is queried by the object.
- Step 202 The proxy device locally queries the data corresponding to the specified object identifier, and encapsulates the queried data in the response packet of the data acquisition request, and sends the response packet to the management device.
- the proxy device After receiving the extended data acquisition request sent by the management device, the proxy device obtains the filtering parameter, and obtains the data corresponding to the object to be acquired from the filtering parameter, and only sends the data corresponding to the specified object, that is, the specified data, to the management device. .
- the proxy device before the proxy device receives the extended data acquisition request sent by the management device, the proxy device establishes a connection with the management device.
- NETCONF is a new network configuration protocol based on Extensible Markup Language (XML). All configuration models and data are represented by XML. XML can express complex, intrinsically logical, modeled management objects. The collection of managed objects forms the content layer of the NETCONF protocol.
- the XML model can implement a management object model that defines complex logical relationships. An XML model usually contains multiple management objects, which represent the parallel and dependent relationships between them in a side-by-side or nested form, and thus form a Tree logical structure. When the logical relationship is more complicated, there are many branches in the tree structure, and each branch may have many sub-branches. Each branch and its sub-branch are called sub-trees.
- the NETCONF protocol stipulates that the data stored in the tree model can be obtained by using the get/getconfig operation method, but it must be obtained in units of subtrees.
- This data acquisition method is called subtree filtering, but for some in the tree structure. Object, but there is no way to get it separately.
- the data acquisition method of operations such as get/get-config is a subtree filtering method, and does not support querying an object in a single hierarchy.
- the data returned by the subtree filtering method is the data of all the objects in the entire subtree. When the subtree nesting level is relatively large or the data content of each hierarchical object is relatively large, the amount of data returned will be large, which may exceed the message limit. The message could not be sent, which eventually caused the query to fail.
- the embodiment of the present invention is directed to the foregoing technical problem, and the data corresponding to the specified object is obtained by carrying the object identifier of the data to be acquired in the data query request, thereby improving data acquisition efficiency and improving network transmission efficiency in the NETCONF.
- the essence of the technical solution of the embodiment of the present invention is further clarified by specific examples below.
- FIG. 3 is a flowchart of the capability negotiation between a management device (Manager) and a proxy device (Agent) according to an embodiment of the present invention. As shown in FIG. 3, the process of establishing a connection between the Manager and the Agent and performing data acquisition capability negotiation includes the following steps:
- Step 301 The Manager and the Agent send Hello packets (referred to as h packets). This step is to determine if the connection between the Manager and the Agent is available.
- Step 302 The Manager and the Agent negotiate data acquisition capabilities. This step is for the Manager to confirm whether the Agent supports obtaining the data of the specified object.
- Step 303 Determine whether the data acquisition capability negotiation is successful. If the agent supports the data of the specified object, the capability negotiation is successful, and step 304 is performed. If the agent does not support the data of the specified object, the capability negotiation fails, and step 305 is performed.
- Step 304 Establish a connection.
- Step 305 Close the connection.
- FIG. 4 is a flowchart of data acquisition between a management device and a proxy device according to an embodiment of the present invention. As shown in FIG. 4, the data acquisition process in the embodiment of the present invention includes the following steps:
- Step 401 The Manager sends an operation request for acquiring data to the agent, and the specified filtering mode is “object filtering”.
- the operation request to acquire data may be a get operation request.
- the get operation request includes an identifier of the data object to be acquired.
- Step 402 The Agent receives an operation request for acquiring data.
- Step 403 The agent parses the operation request for acquiring the data, acquires the relevant parameter in the operation request, and locally finds the data that needs to be acquired by the operation request according to the object filtering manner.
- the data of the specified object acquired by the Agent instead of acquiring the data of all the objects included in the nested object, sends the data of the specified specified object to the Manager.
- Step 404 The Agent sends a response packet to the Manager.
- the response message carries the data of the specified object, not the data of all the objects contained in the nested object.
- Step 405 The Manager receives the response packet sent by the agent.
- Step 406 The Manager processes the response message to obtain data of the specified object.
- FIG. 5 is a flowchart of performing data query by a proxy device according to an embodiment of the present invention. As shown in FIG. 5, the process of performing data query by a proxy device according to an embodiment of the present invention includes the following steps:
- Step 501 The agent receives an operation request for acquiring data in the “object filtering” manner sent by the manager.
- the operation request for acquiring data may be a get operation request.
- Step 502 Parsing the operation parameters, processing the operation request, and returning the data according to the "object filtering" mode.
- the agent parses the operation request for acquiring the data, acquires the operation parameter therein, and acquires the data of the object specified in the operation request according to the operation parameter.
- Step 503 Determine whether an abnormality occurs during the processing. If no abnormality occurs, step 504 is performed, and if an abnormality occurs, step 507 is performed.
- Step 504 Determine whether the size of the response packet exceeds the limit. If the limit is not exceeded, execute step 505. Otherwise, perform step 506.
- Step 505 The query data is organized into a response message, and the response message is sent to the Manager.
- the response message includes data of the object specified in the operation request.
- Step 506 Send a response message to the Manager, and notify the Manager of the abnormal information with a large amount of data.
- Step 507 Send a response message to the Manager, and notify the Manager of the abnormality information.
- the operation request for acquiring data by the NETCONF management device may be a get operation request, and after receiving the operation request, the NETCONF proxy device queries the specified query manner of the filter carried in the operation request, and queries the specified in the filter. The data corresponding to the object is returned to the NETCONF management device after the query is completed.
- the data in the XML model when the data in the XML model is obtained through operations such as get/get-config, the data of an object in the model can be accurately and flexibly acquired, and the nested objects that are not concerned or not needed are obtained.
- the data will not be returned, so the response data packet will be greatly reduced, the risk of packet size exceeding the limit will be minimized, and the proportion of valid data in the packet can be greatly increased, bandwidth consumption can be reduced and bandwidth utilization can be improved. rate.
- the tree structure of the example model is shown in Table 1 below.
- shelf-no, slot-no, and port-no are the keys of the port
- sub-port-no is the key of the sub-port
- the data of the sub-port included in the port nesting is not required to be obtained. If the current get request mechanism is used to achieve the purpose, the Manager first issues the following get request:
- the Agent After the Agent receives the request, it will return all the data of the port subtree, including all the data of the port object and its nested sub-port object, as follows:
- the packet size can be reduced and the proportion of valid data in the packet can be greatly improved.
- the usage method is as follows: First, the Manager sends a get request, and the object filtering method is set in the request, for example, the following get request is delivered:
- the Agent only returns the data of the specified port object, and does not return the data of the sub-ports contained in the nest, that is, all the data in the bold box in Table 3, as follows:
- the data of the above italic part is the data of the port object returned by the Agent.
- the data in the XML model when the data in the XML model is obtained through operations such as get/get-config, the data of an object in the model can be accurately and flexibly acquired, and the nested objects that are not concerned or not needed are obtained.
- the data will not be returned, so the response data packet will be greatly reduced, the risk of packet size exceeding the limit will be minimized, and the proportion of valid data in the packet can be greatly increased, bandwidth consumption can be reduced and bandwidth utilization can be improved. rate.
- FIG. 6 is a schematic structural diagram of a data acquiring apparatus according to Embodiment 1 of the present invention.
- the data acquiring apparatus of this example includes a confirming unit 60, a sending unit 61, a receiving unit 62, and an obtaining unit 63, where:
- the confirmation unit 60 is configured to confirm whether the proxy device supports the extended data acquisition operation, and triggers the sending unit 61 when the support is confirmed;
- the sending unit 61 is configured to send an extended data acquisition request to the proxy device, where the data acquisition request carries an operation parameter of a filter condition, where the filter condition includes identifier information of the specified object;
- the receiving unit 62 is configured to receive a data response message sent by the proxy device.
- the obtaining unit 63 is configured to acquire data corresponding to the specified object identifier from the data response message.
- the confirmation unit 60 of the embodiment of the present invention includes: a transmission subunit (not shown in FIG. 6), a reception subunit (not shown in FIG. 6), and an acknowledgment subunit (not shown in FIG. 6), wherein:
- a sending subunit configured to send a capability query request to the proxy device
- a receiving subunit configured to receive a capability response sent by the proxy device
- a confirmation subunit configured to confirm the generation according to the capability information carried in the capability response Whether the device supports extended data acquisition operations.
- the data is tree structure data based on Extensible Markup Language (XML);
- the data acquisition request carries at least a filter filter parameter
- the filter parameter includes an attribute type and an identifier of the data object to be acquired, and the type is a mibtree, indicating that the data is queried by the object.
- FIG. 7 is a schematic structural diagram of a data acquiring apparatus according to Embodiment 2 of the present invention.
- the data acquiring apparatus of this example includes a receiving unit 70, a parsing acquiring unit 71, a query unit 72, and a sending unit 73, where:
- the receiving unit 70 is configured to receive an extended data acquisition request sent by the management device
- the parsing and obtaining unit 71 is configured to parse the data acquisition request, and obtain at least an operation parameter that carries the filter condition of the specified object identifier in the data acquisition request;
- the query unit 72 is configured to locally query the data corresponding to the specified object identifier.
- the sending unit 73 is configured to encapsulate the queried data in the response packet of the data acquisition request, and send the response packet to the management device.
- the data acquisition device further includes: a confirmation unit (not shown in FIG. 7);
- the receiving unit 70 is further configured to receive a capability query request sent by the management device;
- the confirmation unit is configured to confirm whether it supports the extended data acquisition operation, and triggers the sending unit 73 to send an information capability response carrying the data acquisition operation supporting the extension to the management device when the support is confirmed.
- the data is tree structure data based on Extensible Markup Language (XML);
- the data acquisition request carries at least a filter filter parameter
- the filter parameter includes an attribute type and an identifier of the data object to be acquired, and the type is a mibtree, indicating that the data is queried by the object.
- the embodiment of the invention further describes a storage medium in which a computer program is stored, the computer program being configured to execute the data acquisition method of the foregoing embodiments.
- the disclosed method and smart device may be implemented in other manners.
- the device embodiments described above are merely illustrative.
- the division of the unit is only a logical function division.
- there may be another division manner such as: multiple units or components may be combined, or Can be integrated into another system, or some features can be ignored or not executed.
- the coupling, or direct coupling, or communication connection of the components shown or discussed may be indirect coupling or communication connection through some interfaces, devices or units, and may be electrical, mechanical or other forms. of.
- the units described above as separate components may or may not be physically separated, and the components displayed as the unit may or may not be physical units, that is, may be located in one place or distributed to multiple network units; Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
- each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may be separately used as one unit, or two or more units may be used.
- the elements are integrated in one unit; the above integrated units can be implemented in the form of hardware or in the form of hardware plus software functional units.
- the foregoing storage medium includes: a mobile storage device, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.
- ROM read-only memory
- RAM random access memory
- magnetic disk or an optical disk.
- optical disk A medium that can store application code.
- the above-described integrated unit of the embodiment of the present invention may be stored in a computer readable storage medium if it is implemented in the form of a software function module and sold or used as a stand-alone product.
- the technical solution of the embodiments of the present invention may be embodied in the form of a software product in essence or in the form of a software product stored in a storage medium, including a plurality of instructions.
- a computer device (which may be a personal computer, server, or network device, etc.) is caused to perform all or part of the methods described in various embodiments of the present invention.
- the foregoing storage medium includes: a removable storage device, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like, which can store application code.
- the invention obtains data in the XML model by using an extended get/get-config operation, the data of an object in the model can be accurately and flexibly obtained, and the data of the nested object that is not concerned or not needed will not be obtained. It is returned, so the response data message will be greatly reduced, greatly increasing the proportion of valid data in the message, reducing bandwidth usage and improving bandwidth utilization.
Abstract
本发明实施例公开了一种数据获取方法及装置、存储介质，所述方法包括：管理设备确认代理设备是否支持扩展的数据获取操作，并在确认支持后，向所述代理设备发送扩展的数据获取请求；所述数据获取请求中携带有过滤条件的操作参数，所述过滤条件包括指定对象的标识信息；所述管理设备接收到所述代理设备发送的数据响应报文后，从所述数据响应报文中获取所述指定对象标识对应的数据。
Description
本发明涉及基于NETCONF协议的网管管理技术，尤其涉及一种数据获取方法及装置、存储介质。
使用NETCONF协议实现网络设备配置管理的系统中，NETCONF管理设备(Manager)在获取代理设备(Agent)的各类配置管理数据时，通常使用get/getconfig方法获取这些数据，当数据量很大时，响应报文可能因为太大而无法发出，导致get操作不成功。另外，在获取数据时，管理设备经常只需要获取网络设备的配置管理信息中某个子树的一部分数据，而不需要获取全部子树的数据，虽然管理设备可以将子树信息全部获取到之后再进行数据筛选，但这种数据获取方式效率很低，且无端增大了网络流量。
发明内容
为解决上述技术问题，本发明实施例提供一种数据获取方法及装置、存储介质。
本发明的技术方案是这样实现的：
一种数据获取方法，包括：
管理设备确认代理设备是否支持扩展的数据获取操作，并在确认支持后，向所述代理设备发送扩展的数据获取请求；所述数据获取请求中携带有过滤条件的操作参数，所述过滤条件包括指定对象的标识信息；
所述管理设备接收到所述代理设备发送的数据响应报文后，从所述数据响应报文中获取所述指定对象标识对应的数据。
作为一种实现方式，所述管理设备确认代理设备是否支持扩展的数据获取操作，包括：
所述管理设备向所述代理设备发送能力查询请求，并接收所述代理设备发送的能力响应，根据所述能力响应中携带的能力信息确认所述代理设备是否支持扩展的数据获取操作。
作为一种实现方式，所述数据为基于可扩展标记语言XML的树状结构数据；
所述数据获取请求中至少携带过滤filter参数；
其中，所述filter参数包含属性type和待获取数据对象的标识，所述type为mibtree，表明数据按对象查询。
作为一种实现方式，所述管理设备确认代理设备是否支持扩展的数据获取操作之前，所述方法还包括：
所述管理设备与所述代理设备建立连接。
一种数据获取方法，包括：
代理设备接收管理设备发送的扩展的数据获取请求，解析所述数据获取请求，至少获取所述数据获取请求中携带有指定对象标识的过滤条件的操作参数；
所述代理设备在本地查询出所述指定对象标识对应的数据，并将所查询出的数据封装于所述数据获取请求的响应报文中，向所述管理设备发送所述响应报文。
作为一种实现方式，代理设备接收管理设备发送的扩展的数据获取请求之前，所述方法还包括：
所述代理设备接收所述管理设备发送的能力查询请求，确认自身是否支持扩展的数据获取操作，并在确认支持时向所述管理设备发送携带有支持扩展的数据获取操作的信息能力响应。
作为一种实现方式，所述数据为基于可扩展标记语言XML的树状结构数据；
所述数据获取请求中至少携带过滤filter参数；
其中，所述filter参数包含属性type和待获取数据对象的标识，所述type为mibtree，表明数据按对象查询。
作为一种实现方式，代理设备接收管理设备发送的扩展的数据获取请求之前，所述方法还包括：
所述代理设备与所述管理设备建立连接。
一种数据获取装置，包括：确认单元、发送单元、接收单元和获取单元，其中：
确认单元，配置为确认代理设备是否支持扩展的数据获取操作，并在确认支持时触发所述发送单元；
发送单元，配置为向所述代理设备发送扩展的数据获取请求；所述数据获取请求中携带有过滤条件的操作参数，所述过滤条件包括指定对象的标识信息；
接收单元，配置为接收到所述代理设备发送的数据响应报文；
获取单元，配置为从所述数据响应报文中获取所述指定对象标识对应的数据。
作为一种实现方式，所述确认单元包括：发送子单元、接收子单元和确认子单元，其中：
发送子单元，配置为向所述代理设备发送能力查询请求；
接收子单元，配置为接收所述代理设备发送的能力响应；
确认子单元，配置为根据所述能力响应中携带的能力信息确认所述代理设备是否支持扩展的数据获取操作。
作为一种实现方式，所述数据为基于可扩展标记语言XML的树状结构
数据；
所述数据获取请求中至少携带过滤filter参数；
其中，所述filter参数包含属性type和待获取数据对象的标识，所述type为mibtree，表明数据按对象查询。
一种数据获取装置，包括：接收单元、解析获取单元、查询单元和发送单元，其中：
接收单元，配置为接收管理设备发送的扩展的数据获取请求；
解析获取单元，配置为解析所述数据获取请求，至少获取所述数据获取请求中携带有指定对象标识的过滤条件的操作参数；
查询单元，配置为在本地查询出所述指定对象标识对应的数据；
发送单元，配置为将所查询出的数据封装于所述数据获取请求的响应报文中，向所述管理设备发送所述响应报文。
作为一种实现方式，所述装置还包括：确认单元；
所述接收单元，还配置为接收所述管理设备发送的能力查询请求；
所述确认单元，配置为确认自身是否支持扩展的数据获取操作，并在确认支持时触发所述发送单元向所述管理设备发送携带有支持扩展的数据获取操作的信息能力响应。
作为一种实现方式，所述数据为基于可扩展标记语言XML的树状结构数据；
所述数据获取请求中至少携带过滤filter参数；
其中，所述filter参数包含属性type和待获取数据对象的标识，所述type为mibtree，表明数据按对象查询。
一种存储介质，所述存储介质中存储有计算机程序，所述计算机程序配置为执行所述的数据获取方法。
本发明实施例中，通过扩展数据获取操作，为数据获取操作增设过滤
条件的操作参数，能向代理设备获取指定对象的数据。本发明实施例的技术方案，使用本发明采用的技术方案后，使用扩展的get/get-config等操作获取XML模型中的数据时，可以精确地、灵活地获取模型中某个对象的数据，不关注或不需要的嵌套对象的数据将不会被返回，因此响应数据报文将会大大减小，大大提高了报文中有效数据的比例，降低带宽占用和提高带宽利用率。
图1为本发明实施例一的数据获取方法的流程图；
图2为本发明实施例二的数据获取方法的流程图；
图3为本发明实施例的管理设备与代理设备能力协商的流程图；
图4为本发明实施例的管理设备与代理设备之间数据获取的流程图；
图5为本发明实施例的代理设备进行数据查询的流程图；
图6为本发明实施例一的数据获取装置的组成结构示意图；
图7为本发明实施例二的数据获取装置的组成结构示意图。
为使本发明的目的、技术方案和优点更加清楚明白，以下举实施例并参照附图，对本发明进一步详细说明。
以下通过具体示例，进一步阐明本发明实施例的技术方案的实质。
图1为本发明实施例一的数据获取方法的流程图，如图1所示，本示例的数据获取方法包括以下步骤：
步骤101，管理设备确认代理设备是否支持扩展的数据获取操作，并在确认支持后，向所述代理设备发送扩展的数据获取请求。
本发明实施例中，所述数据获取请求中携带有过滤条件的操作参数，所述过滤条件包括指定对象的标识信息
所述数据为基于可扩展标记语言XML的树状结构数据；
所述数据获取请求中至少携带过滤filter参数；
其中，所述filter参数包含属性type和待获取数据对象的标识，所述type为mibtree，表明数据按对象查询。
代理设备接收管理设备发送的扩展的数据获取请求，解析所述数据获取请求，至少获取所述数据获取请求中携带的过滤条件的参数；
所述代理设备在本地查询出所述指定对象对应的数据，并将所查询出的数据封装于所述数据获取请求的响应报文中，向所述管理设备发送所述响应报文。
步骤102，所述管理设备接收到所述代理设备发送的数据响应报文后，从所述数据响应报文中获取所述指定对象标识对应的数据。
当管理设备接收到代理设备发送的数据响应报文后，从响应报文中直接获取指定的数据。
本发明实施例的技术方案，使用本发明采用的技术方案后，使用扩展的get/get-config等操作获取XML模型中的数据时，可以精确地、灵活地获取模型中某个对象的数据，不关注或不需要的嵌套对象的数据将不会被返回，因此响应数据报文将会大大减小，大大提高了报文中有效数据的比例，降低带宽占用和提高带宽利用率。
本发明实施例中，所述管理设备确认代理设备是否支持扩展的数据获取操作之前，所述管理设备与所述代理设备建立连接。
图2为本发明实施例二的数据获取方法的流程图，如图2所示，本示例的数据获取方法包括以下步骤：
步骤201，代理设备接收管理设备发送的扩展的数据获取请求，解析所述数据获取请求，至少获取所述数据获取请求中携带有指定对象标识的过滤条件的操作参数。
本发明实施例中，管理设备首先向所述代理设备发送扩展的数据获取请求。
管理设备向代理设备发送的扩展的数据获取请求之前，所述方法还包括：
所述代理设备接收所述管理设备发送的能力查询请求，确认自身是否支持扩展的数据获取操作，并在确认支持时向所述管理设备发送携带有支持扩展的数据获取操作的信息能力响应。
本发明实施例中，所述数据为基于可扩展标记语言XML的树状结构数据；所述数据获取请求中至少携带过滤filter参数；
其中，所述filter参数包含属性type和待获取数据对象的标识，所述type为mibtree，表明数据按对象查询。
步骤202，代理设备在本地查询出所述指定对象标识对应的数据，并将所查询出的数据封装于所述数据获取请求的响应报文中，向所述管理设备发送所述响应报文。
代理设备接收到管理设备发送的扩展的数据获取请求后，获取其中的过滤参数，并从过滤参数中获取待获取对象对应的数据，仅将该指定对象对应的数据即指定的数据向管理设备发送。
本发明实施例中，代理设备接收管理设备发送的扩展的数据获取请求之前，所述代理设备与所述管理设备建立连接。
NETCONF是全新的基于可扩展标记语言(XML，Extensible Markup Language)的网络配置协议，所有配置模型及数据都以XML表示，XML可以表达复杂的、具有内在逻辑关系的、模型化的管理对象，这些管理对象的集合构成了NETCONF协议的内容层。XML模型可以实现定义复杂逻辑关系的管理对象模型，一个XML模型通常包含多个管理对象，这些对象以并列或嵌套的形式来表示它们之间的并列和从属等关系，并因此形成一个
树型逻辑结构。当逻辑关系比较复杂时，树型结构中的分支会很多，每个分支可能又有很多子分支，每一个分支及其包含的子分支称为子树。而NETCONF协议规定可以使用get/getconfig操作方法获取树型模型中存储的数据，但必须以子树为单位获取，这种数据获取方式称为子树过滤方式，但对于树型结构中的某个对象，却没有办法单独获取。而get/get-config等操作的数据获取方式是子树过滤方式，不支持查询单层次中某个对象。子树过滤方式返回的数据是整棵子树中所有对象的数据，当子树嵌套层次比较多或各层次对象的数据内容比较多时，返回的数据量就会很大，很可能超过报文限制，而导致报文无法发出，最终导致查询失败。
在实际使用中，经常会有只查询单层次中某个对象的应用场景，而且需要查询的单个对象的数据量不会超过报文限制，但因为get/get-config等操作是子树过滤方式，整个子树的数据量很大时，就导致这样的应用场景无法实现。另外，在只查询单层次中某个对象的应用场景中，子树过滤方式返回的数据中只有一部分是真正需要的数据，其他大量的数据是不需要的，但嵌套包含的那些对象的数据，组织并返回这些数据会占用设备很多时间，最终却被管理站白白丢弃，所以说这种数据查询方式的效率很低。
本发明实施例正是针对上述技术问题，通过在数据查询请求中携带待获取数据的对象标识，来获取该指定对象对应的数据，从而提升NETCONF中数据获取效率，提升网络传输效率。以下通过具体示例，进一步阐明本发明实施例的技术方案的实质。
图3为本发明实施例的管理设备(Manager)与代理设备(Agent)能力协商的流程图，如图3所示，Manager和Agent建立连接并进行数据获取能力协商的流程包括以下步骤：
步骤301：Manager和Agent互发hello报文(简称h报文)。本步骤是确定Manager与Agent之间的连接是否可用。
步骤302：Manager和Agent协商数据获取能力。本步骤是Manager确认Agent是否支持获取指定的对象的数据。
步骤303：判断数据获取能力协商是否成功，如果Agent支持获取指定的对象的数据，则能力协商成功，执行步骤304，如果Agent不支持获取指定的对象的数据，则能力协商失败，执行步骤305。
步骤304：建立连接。
步骤305：关闭连接。
图4为本发明实施例的管理设备与代理设备之间数据获取的流程图，如图4所示，本发明实施例的数据获取流程包括以下步骤：
步骤401：Manager向Agent发送获取数据的操作请求，指定过滤方式为“对象过滤”。该获取数据的操作请求可以是get操作请求。get操作请求中包括待获取数据对象的标识。
步骤402：Agent接收获取数据的操作请求。
步骤403：Agent解析获取数据的操作请求，获取操作请求中的相关参数，按对象过滤方式在本地查找出操作请求需要获取的数据。本发明实施例中，Agent获取的指定对象的数据，而不是获取该对象嵌套包含的所有对象的数据，将所查找出的指定对象的数据向Manager发送。
步骤404：Agent向Manager发送响应报文。该响应报文中承载有指定对象的数据，而不是该对象嵌套包含的所有对象的数据。
步骤405：Manager接收Agent发送的响应报文。
步骤406：Manager处理响应报文，获取指定对象的数据。
图5为本发明实施例的代理设备进行数据查询的流程图，如图5所示，本发明实施例的代理设备进行数据查询的流程包括以下步骤：
步骤501：Agent接收Manager发送的以“对象过滤”方式的获取数据的操作请求；本发明实施例中，获取数据的操作请求可以是get操作请求。
步骤502：解析操作参数，处理操作请求，按“对象过滤”方式返回数据。本步骤中，Agent解析获取数据的操作请求，获取其中的操作参数，根据操作参数，获取操作请求中指定的对象的数据。
步骤503：判断处理过程中是否发生异常，如果没有发生异常则执行步骤504，如果发生异常则执行骤507。
步骤504：判断响应报文大小是否超过限制，如果没有超过限制则执行步骤505，否则执行步骤506。
步骤505：查询数据组织成响应报文，向Manager发送响应报文。响应报文中包括操作请求中指定的对象的数据。
步骤506：向Manager发送响应报文，将数据量过大的异常信息告知Manager。
步骤507：向Manager发送响应报文，将异常信息告知Manager。
本发明实施例中，由NETCONF管理设备发起获取数据的操作请求可以为get操作请求，NETCONF代理设备收到该操作请求后，按操作请求中携带的filter的指定的查询方式，查询filter中指定的对象对应的数据，查询完成后将查询出的指定数据返回给NETCONF管理设备。
使用本发明实施例的技术方案，通过get/get-config等操作获取XML模型中的数据时，可以精确地、灵活地获取模型中某个对象的数据，不关注或不需要的嵌套对象的数据将不会被返回，因此响应数据报文将会大大减小，报文大小超过限制的风险将会最大程度降低，并可以大大提高报文中有效数据的比例，降低带宽占用和提高带宽利用率。
下面举例说明典型应用场景的查询过程。
如表1所示，假设存在以下模型：
该实例模型的树状结构示意如下表1所示。
表1
表1中，shelf-no、slot-no和port-no是port的key，sub-port-no是sub-port的key。
假设该模型存储的数据如下：
该实例模型的存储数据如表2所示。
表2
假设Manager仅需要获取port对象的数据，即下表3中粗体框中所有数据。
表3
本发明实施例中，不需要获取port嵌套包含的sub-port的数据，假如使用目前的get请求机制达到这一目的方法是，首先Manager下发如下get请求：
Agent收到请求后，将返回port子树的所有数据，包括了port对象及其嵌套的sub-port对象的所有数据，如下：
从上述数据获取方式可以看出，Agent返回的数据量非常大，而其中Manager真正需要的只是斜体部分的数据，其他大部分数据都会被丢弃，这样，大量的带宽就浪费了，数据传输的效率很低。更严重的情况是，当嵌套的sub-port对象的数据量也比较大时，Agent试图构造的响应报文很可能超过报文大小的限制，以至于报文太大无法发出，最终导致查询失败。
使用本发明实施例提出的对象过滤方式，可以减小报文大小并极大提高有效数据在报文中比例。使用方式是：首先Manager下发get请求，在请求中设置对象过滤方式，例如下发如下get请求：
Agent只返回指定的port对象的数据，而不返回嵌套包含的sub-port的数据，即表3中粗体框中所有数据，如下：
上述斜体部分的数据，即为Agent返回的port对象的数据。
使用本发明实施例的技术方案，通过get/get-config等操作获取XML模型中的数据时，可以精确地、灵活地获取模型中某个对象的数据，不关注或不需要的嵌套对象的数据将不会被返回，因此响应数据报文将会大大减小，报文大小超过限制的风险将会最大程度降低，并可以大大提高报文中有效数据的比例，降低带宽占用和提高带宽利用率。
图6为本发明实施例一的数据获取装置的组成结构示意图，如图6所示，本示例的数据获取装置包括确认单元60、发送单元61、接收单元62和获取单元63，其中：
确认单元60，配置为确认代理设备是否支持扩展的数据获取操作，并在确认支持时触发所述发送单元61；
发送单元61，配置为向所述代理设备发送扩展的数据获取请求；所述数据获取请求中携带有过滤条件的操作参数，所述过滤条件包括指定对象的标识信息；
接收单元62，配置为接收到所述代理设备发送的数据响应报文；
获取单元63，配置为从所述数据响应报文中获取所述指定对象标识对应的数据。
本发明实施例的确认单元60包括：发送子单元(图6中未示出)、接收子单元(图6中未示出)和确认子单元(图6中未示出)，其中：
发送子单元，配置为向所述代理设备发送能力查询请求；
接收子单元，配置为接收所述代理设备发送的能力响应；
确认子单元，配置为根据所述能力响应中携带的能力信息确认所述代
理设备是否支持扩展的数据获取操作。
本发明实施例中，所述数据为基于可扩展标记语言XML的树状结构数据；
所述数据获取请求中至少携带过滤filter参数；
其中，所述filter参数包含属性type和待获取数据对象的标识，所述type为mibtree，表明数据按对象查询。
本领域技术人员应当理解，图6中所示的数据获取装置中的各处理单元的实现功能可参照前述数据获取方法及其实施例的相关描述而理解。本领域技术人员应当理解，图6所示的数据获取装置中各处理单元的功能可通过运行于处理器上的程序而实现，也可通过具体的逻辑电路而实现。
图7为本发明实施例二的数据获取装置的组成结构示意图，如图7所示，本示例的数据获取装置包括接收单元70、解析获取单元71、查询单元72和发送单元73，其中：
接收单元70，配置为接收管理设备发送的扩展的数据获取请求；
解析获取单元71，配置为解析所述数据获取请求，至少获取所述数据获取请求中携带有指定对象标识的过滤条件的操作参数；
查询单元72，配置为在本地查询出所述指定对象标识对应的数据；
发送单元73，配置为将所查询出的数据封装于所述数据获取请求的响应报文中，向所述管理设备发送所述响应报文。
在图7所示的数据获取装置的基础上，所述数据获取装置还包括：确认单元(图7中未示出)；
所述接收单元70，还配置为接收所述管理设备发送的能力查询请求；
所述确认单元，配置为确认自身是否支持扩展的数据获取操作，并在确认支持时触发所述发送单元73向所述管理设备发送携带有支持扩展的数据获取操作的信息能力响应。
本发明实施例中，所述数据为基于可扩展标记语言XML的树状结构数据；
所述数据获取请求中至少携带过滤filter参数；
其中，所述filter参数包含属性type和待获取数据对象的标识，所述type为mibtree，表明数据按对象查询。
本领域技术人员应当理解，图7中所示的数据获取装置中的各处理单元的实现功能可参照前述数据获取方法及其实施例的相关描述而理解。本领域技术人员应当理解，图7所示的数据获取装置中各处理单元的功能可通过运行于处理器上的程序而实现，也可通过具体的逻辑电路而实现。
本发明实施例还记载了一种存储介质，所述存储介质中存储有计算机程序，所述计算机程序配置为执行前述各实施例的数据获取方法。
在不冲突的前提下，本发明实施例的技术方案之间可以合并。
在本发明所提供的几个实施例中，应该理解到，所揭露的方法和智能设备，可以通过其它的方式实现。以上所描述的设备实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，如：多个单元或组件可以结合，或可以集成到另一个系统，或一些特征可以忽略，或不执行。另外，所显示或讨论的各组成部分相互之间的耦合、或直接耦合、或通信连接可以是通过一些接口，设备或单元的间接耦合或通信连接，可以是电性的、机械的或其它形式的。
上述作为分离部件说明的单元可以是、或也可以不是物理上分开的，作为单元显示的部件可以是、或也可以不是物理单元，即可以位于一个地方，也可以分布到多个网络单元上；可以根据实际的需要选择其中的部分或全部单元来实现本实施例方案的目的。
另外，在本发明各实施例中的各功能单元可以全部集成在一个处理单元中，也可以是各单元分别单独作为一个单元，也可以两个或两个以上单
元集成在一个单元中；上述集成的单元既可以采用硬件的形式实现，也可以采用硬件加软件功能单元的形式实现。
本领域普通技术人员可以理解：实现上述方法实施例的全部或部分步骤可以通过应用指令相关的硬件来完成，前述的应用可以存储于一计算机可读取存储介质中，该应用在执行时，执行包括上述方法实施例的步骤；而前述的存储介质包括：移动存储设备、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、磁碟或者光盘等各种可以存储应用代码的介质。
或者，本发明实施例上述集成的单元如果以软件功能模块的形式实现并作为独立的产品销售或使用时，也可以存储在一个计算机可读取存储介质中。基于这样的理解，本发明实施例的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机、服务器、或者网络设备等)执行本发明各个实施例所述方法的全部或部分。而前述的存储介质包括：移动存储设备、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、磁碟或者光盘等各种可以存储应用代码的介质。
以上所述，仅为本发明的具体实施方式，但本发明的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本发明揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本发明的保护范围之内。
本发明通过使用扩展的get/get-config等操作获取XML模型中的数据时，可以精确地、灵活地获取模型中某个对象的数据，不关注或不需要的嵌套对象的数据将不会被返回，因此响应数据报文将会大大减小，大大提高了报文中有效数据的比例，降低带宽占用和提高带宽利用率。
Claims (15)
- 一种数据获取方法，所述方法包括：管理设备确认代理设备是否支持扩展的数据获取操作，并在确认支持后，向所述代理设备发送扩展的数据获取请求；所述数据获取请求中携带有过滤条件的操作参数，所述过滤条件包括指定对象的标识信息；所述管理设备接收到所述代理设备发送的数据响应报文后，从所述数据响应报文中获取所述指定对象标识对应的数据。
- 根据权利要求1所述的方法，其中，所述管理设备确认代理设备是否支持扩展的数据获取操作，包括：所述管理设备向所述代理设备发送能力查询请求，并接收所述代理设备发送的能力响应，根据所述能力响应中携带的能力信息确认所述代理设备是否支持扩展的数据获取操作。
- 根据权利要求1或2所述的方法，其中，所述数据为基于可扩展标记语言XML的树状结构数据；所述数据获取请求中至少携带过滤filter参数；其中，所述filter参数包含属性type和待获取数据对象的标识，所述type为mibtree，表明数据按对象查询。
- 根据权利要求1所述的方法，其中，所述管理设备确认代理设备是否支持扩展的数据获取操作之前，所述方法还包括：所述管理设备与所述代理设备建立连接。
- 一种数据获取方法，所述方法包括：代理设备接收管理设备发送的扩展的数据获取请求，解析所述数据获取请求，至少获取所述数据获取请求中携带有指定对象标识的过滤条件的操作参数；所述代理设备在本地查询出所述指定对象标识对应的数据，并将所查 询出的数据封装于所述数据获取请求的响应报文中，向所述管理设备发送所述响应报文。
- 根据权利要求5所述的方法，其中，代理设备接收管理设备发送的扩展的数据获取请求之前，所述方法还包括：所述代理设备接收所述管理设备发送的能力查询请求，确认自身是否支持扩展的数据获取操作，并在确认支持时向所述管理设备发送携带有支持扩展的数据获取操作的信息能力响应。
- 根据权利要求5所述的方法，其中，所述数据为基于可扩展标记语言XML的树状结构数据；所述数据获取请求中至少携带过滤filter参数；其中，所述filter参数包含属性type和待获取数据对象的标识，所述type为mibtree，表明数据按对象查询。
- 根据权利要求5所述的方法，其中，代理设备接收管理设备发送的扩展的数据获取请求之前，所述方法还包括：所述代理设备与所述管理设备建立连接。
- 一种数据获取装置，所述装置包括：确认单元、发送单元、接收单元和获取单元，其中：确认单元，配置为确认代理设备是否支持扩展的数据获取操作，并在确认支持时触发所述发送单元；发送单元，配置为向所述代理设备发送扩展的数据获取请求；所述数据获取请求中携带有过滤条件的操作参数，所述过滤条件包括指定对象的标识信息；接收单元，配置为接收到所述代理设备发送的数据响应报文；获取单元，配置为从所述数据响应报文中获取所述指定对象标识对应的数据。
- 根据权利要求9所述的装置，其中，所述确认单元包括：发送子单元、接收子单元和确认子单元，其中：发送子单元，配置为向所述代理设备发送能力查询请求；接收子单元，配置为接收所述代理设备发送的能力响应；确认子单元，配置为根据所述能力响应中携带的能力信息确认所述代理设备是否支持扩展的数据获取操作。
- 根据权利要求9或10所述的装置，其中，所述数据为基于可扩展标记语言XML的树状结构数据；所述数据获取请求中至少携带过滤filter参数；其中，所述filter参数包含属性type和待获取数据对象的标识，所述type为mibtree，表明数据按对象查询。
- 一种数据获取装置，所述装置包括：接收单元、解析获取单元、查询单元和发送单元，其中：接收单元，配置为接收管理设备发送的扩展的数据获取请求；解析获取单元，配置为解析所述数据获取请求，至少获取所述数据获取请求中携带有指定对象标识的过滤条件的操作参数；查询单元，配置为在本地查询出所述指定对象标识对应的数据；发送单元，配置为将所查询出的数据封装于所述数据获取请求的响应报文中，向所述管理设备发送所述响应报文。
- 根据权利要求12所述的装置，其中，所述装置还包括：确认单元；所述接收单元，还配置为接收所述管理设备发送的能力查询请求；所述确认单元，配置为确认自身是否支持扩展的数据获取操作，并在确认支持时触发所述发送单元向所述管理设备发送携带有支持扩展的数据获取操作的信息能力响应。
- 根据权利要求12或13所述的装置，其中，所述数据为基于可扩 展标记语言XML的树状结构数据；所述数据获取请求中至少携带过滤filter参数；其中，所述filter参数包含属性type和待获取数据对象的标识，所述type为mibtree，表明数据按对象查询。
- 一种存储介质，所述存储介质中存储有计算机程序，所述计算机程序配置为执行权利要求1至8任一项所述的数据获取方法。
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510007187.2 | 2015-01-07 | ||
| CN201510007187.2A CN105827423A (zh) | 2015-01-07 | 2015-01-07 | 数据获取方法及装置 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2016110070A1 true WO2016110070A1 (zh) | 2016-07-14 |
Family
ID=56355467
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/CN2015/083098 WO2016110070A1 (zh) | 2015-01-07 | 2015-07-01 | 数据获取方法及装置、存储介质 |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN105827423A (zh) |
| WO (1) | WO2016110070A1 (zh) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112307486A (zh) * | 2019-07-29 | 2021-02-02 | 华为技术有限公司 | 一种权限获取方法、设备和系统 |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112385182A (zh) * | 2018-09-07 | 2021-02-19 | 华为技术有限公司 | 一种基于netconf的数据处理方法及装置 |
| CN111488515A (zh) * | 2019-01-25 | 2020-08-04 | 华为技术有限公司 | 信息查询方法、装置、设备及存储介质 |
| CN110309123A (zh) * | 2019-05-22 | 2019-10-08 | 中国平安人寿保险股份有限公司 | 数据库操作的处理方法、装置、计算机设备及存储介质 |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1674589A (zh) * | 2004-03-11 | 2005-09-28 | 微软公司 | 移动装置管理树下的连通性对象 |
| CN101409718A (zh) * | 2007-10-12 | 2009-04-15 | 华为技术有限公司 | 一种确定用户数据的方法、系统及装置 |
| CN102368716A (zh) * | 2011-11-29 | 2012-03-07 | 迈普通信技术股份有限公司 | 一种网络配置协议的数据获取方法及网络配置服务器 |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8621211B1 (en) * | 2008-10-24 | 2013-12-31 | Juniper Networks, Inc. | NETCONF/DMI-based secure network device discovery |
| CN102263796B (zh) * | 2011-08-30 | 2014-01-15 | 北京佳讯飞鸿电气股份有限公司 | 基于简单网络管理协议的数据传输方法 |
-
2015
- 2015-01-07 CN CN201510007187.2A patent/CN105827423A/zh not_active Withdrawn
- 2015-07-01 WO PCT/CN2015/083098 patent/WO2016110070A1/zh active Application Filing
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1674589A (zh) * | 2004-03-11 | 2005-09-28 | 微软公司 | 移动装置管理树下的连通性对象 |
| CN101409718A (zh) * | 2007-10-12 | 2009-04-15 | 华为技术有限公司 | 一种确定用户数据的方法、系统及装置 |
| CN102368716A (zh) * | 2011-11-29 | 2012-03-07 | 迈普通信技术股份有限公司 | 一种网络配置协议的数据获取方法及网络配置服务器 |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112307486A (zh) * | 2019-07-29 | 2021-02-02 | 华为技术有限公司 | 一种权限获取方法、设备和系统 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN105827423A (zh) | 2016-08-03 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11159606B2 (en) | Lightweight IoT information model | |
| EP3526994B1 (en) | Network management interface | |
| EP3111619B1 (en) | Network configuration access | |
| CN109831318A (zh) | 一种获取网络拓扑的系统、方法和服务器 | |
| WO2016110070A1 (zh) | 数据获取方法及装置、存储介质 | |
| WO2016110078A1 (zh) | 数据获取方法及装置、存储介质 | |
| CN102355374A (zh) | 一种数据获取方法和设备 | |
| WO2013063950A1 (zh) | 多模通信设备的巡检方法和系统 | |
| CN106814975A (zh) | 一种用于多类型存储设备的存储管理方法及其系统 | |
| CN103488696A (zh) | Cpe的业务查询方法、装置及系统、acs和cpe | |
| US10268532B2 (en) | Application message processing system, method, and application device | |
| WO2015131523A1 (zh) | 数据查询方法、系统及计算机存储介质 | |
| CN110768818B (zh) | 一种网络管理方法和装置 | |
| CN107968798A (zh) | 一种网管资源标签获取方法、缓存同步方法、装置及系统 | |
| US20220052902A1 (en) | Method for managing remote device through management device | |
| CA2987316A1 (en) | Local object instance discovery for metric collection on network elements | |
| CN112307486A (zh) | 一种权限获取方法、设备和系统 | |
| EP3629616B1 (en) | Data interaction method, device and equipment | |
| CN109101399B (zh) | 一种主机的监控方法及设备 | |
| CN102684924A (zh) | 网络管理工作站及网络管理软件调试方法 | |
| CN107784006B (zh) | 数据处理方法及装置 | |
| US11956337B2 (en) | Message parsing method, data transmit end, data receive end, and system | |
| CN112087318B (zh) | 一种网络管理方法、服务器、客户端及系统 | |
| CN115065594B (zh) | 数据配置方法、装置、设备、可读存储介质及程序产品 | |
| KR100474358B1 (ko) | 고속 라우터 시스템의 원격 망 모니터링 기능 구현방법 및장치, 이를 수행하는 프로그램을 기록한 기록매체 |
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: 15876574 Country of ref document: EP Kind code of ref document: A1 |
|
| NENP | Non-entry into the national phase |
Ref country code: DE |
|
| 122 | Ep: pct application non-entry in european phase |
Ref document number: 15876574 Country of ref document: EP Kind code of ref document: A1 |