WO2016110078A1 - Procédé et appareil d'acquisition de données, et support de stockage - Google Patents

Procédé et appareil d'acquisition de données, et support de stockage Download PDF

Info

Publication number
WO2016110078A1
WO2016110078A1 PCT/CN2015/083893 CN2015083893W WO2016110078A1 WO 2016110078 A1 WO2016110078 A1 WO 2016110078A1 CN 2015083893 W CN2015083893 W CN 2015083893W WO 2016110078 A1 WO2016110078 A1 WO 2016110078A1
Authority
WO
WIPO (PCT)
Prior art keywords
index
data
list
data acquisition
filter
Prior art date
Application number
PCT/CN2015/083893
Other languages
English (en)
Chinese (zh)
Inventor
冯冲
侯小燕
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2016110078A1 publication Critical patent/WO2016110078A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/34—Signalling channels for network management communication

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 at least the filter condition, the start index, and the return record number.
  • the management device After receiving the data response message sent by the proxy device, the management device obtains, from the data response message, the return token from the start index that meets the filtering condition. Record a number of data.
  • 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 the following parameters:
  • the Filter parameter is used to specify a query mode of the data, and the Filter parameter includes an attribute type, and the type is a subtree, indicating that the data is queried by the subtree;
  • the number parameter is a number of records for specifying the query data, and the attribute of the Number parameter is only used on the node of the list type, and is used to indicate the subtree to be queried;
  • a method of data acquisition comprising:
  • the proxy device receives the extended data acquisition request sent by the management device, and parses the data to obtain Obtaining at least the operation parameter of the filtering condition, the starting index, and the number of returned records carried in the data obtaining request;
  • the proxy device locally queries the return record number of data from the start index that meets the filtering condition, and encapsulates the queried data in the response message of the data acquisition request. Sending the response message 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 request carries at least the following parameters:
  • the number parameter is a number of records for specifying the query data, and the attribute of the Number parameter is only used on the node of the list type, and is used to indicate the subtree to be queried;
  • the Filter-index is only used on the node of the list type, and is used to indicate whether the key field of the list is used only for the starting index or for the starting index and also serves as a filtering condition.
  • the proxy device receives the extended data acquisition sent by the management device. Before the request, the method further includes:
  • 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, where the data acquisition request carries at least an operation parameter of a filter condition, a start index, and a return record number;
  • a receiving unit configured to receive a data response message sent by the proxy device
  • an acquiring unit configured to acquire, from the data response message, the return record number of data from the start index that meets the filtering condition.
  • 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 data acquisition request carries at least the following parameters:
  • the Filter parameter is used to specify a query mode of the data, and the Filter parameter includes an attribute type, and the type is a subtree, indicating that the data is queried by the subtree;
  • the number parameter is a number of records for specifying the query data, and the attribute of the Number parameter is only used on the node of the list type, and is used to indicate the subtree to be queried;
  • 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 obtain at least an operation parameter of a filter condition, a start index, and a return record number carried in the data acquisition request;
  • a query unit configured to locally query, according to the filtering condition, the return record number of data from the start index
  • 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 Filter parameter is used to specify a query mode of the data, and the Filter parameter includes Attribute type, when the type is subtree, it indicates that the data is queried by subtree;
  • the number parameter is a number of records for specifying the query data, and the attribute of the Number parameter is only used on the node of the list type, and is used to indicate the subtree to be queried;
  • the Start-index parameter is a key field of a list type node; when there are multiple levels of list nesting, the key field of the list nested by the list containing the Number attribute is used to start the index, and the inclusion or nesting The key field of the list containing the list of the Number attribute is used to start the index or filter condition;
  • the Filter-index is only used on the node of the list type, and is used to indicate whether the key field of the list is used only for the starting index or for the starting index and also serves as a filtering condition.
  • a storage medium having stored therein a computer program configured to perform the data acquisition method.
  • an operation parameter such as a filter condition, a start index, and a return record number is added to the data acquisition operation, and part of the data can be obtained in batches from the proxy device.
  • the technical solution of the embodiment of the present invention adopts a rounding-down mode to make large data volume acquisition possible; and does not require maintenance status, breakpoints and the like, the management station and the proxy device are simple to implement, the data query granularity is adjustable, and the query mode is Flexible and high query accuracy.
  • 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 negotiation between a management device and a proxy device according to an embodiment of the present invention
  • FIG. 4 is a flowchart of interaction 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.
  • 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 at least an operation parameter of a filter condition, a start index, and a return record number.
  • the data is tree structure data based on Extensible Markup Language XML;
  • the data acquisition request carries at least the following parameters:
  • the Filter parameter is used to specify the query mode of the data.
  • the Filter parameter contains an attribute type, and the type "subtree" indicates that the subtree query is performed by the subtree query.
  • Number is the content layer parameter, which is used to specify the number of records of the query data, that is, the number of data records returned.
  • the Number property is only allowed to appear on the node of the list type. When there are 2 or more lists nested, the Number property appears on which list type node, which indicates which subtree is queried. If the node of the list type containing the Number attribute contains a nested list, the number of records is the number of records of the deepest nested list.
  • the value of the number attribute ranges from 0 to 1000. That is, the maximum number of records returned is 1000.
  • the number specified by 0 is 0.
  • the number of returned data entries is not limited.
  • the NETCONF proxy device can adjust adaptively according to its own capabilities and current data size. Return as many complete records as possible while ensuring that the message is not oversized.
  • the data acquisition request is a get-bulk operation.
  • an operation that is, a get-bulk operation, is added in the operation layer of the NETCONF protocol, and the operation may be performed.
  • the NETCONF management device can obtain large batches of data in batches by sending get-bulk operations to the NETCONF proxy device multiple times.
  • the upper list can be specified.
  • the index is a filter condition, which implements the function of querying only a part of the data in the subtree.
  • at most one node of type list can contain the Number attribute.
  • the Start-index parameter is a content layer parameter, and its specific form is a key field of a list type node.
  • the list containing the Number property and the key field of the list contained in the list are always used to locate the starting index, and the containing or nesting contains the list (list containing the Number property)
  • the key fields of those lists can be used as a positioning start index or as a filter condition.
  • the meaning of the filter condition is that when the data and filter conditions that the NETCONF proxy device sequentially queries do not match, the proxy device automatically terminates the query, that is, the query ends, so setting the filter condition can complete the query with smaller granularity and more precision.
  • Start-index can be specified in part, but when multiple lists are nested, if the start-index of the previous list is not specified, the Start-index of this layer list is not allowed. When the Start-index is not specified, it means that the query starts from the first one.
  • the proxy device locally queries the return record number of data from the start index that meets the filtering condition, and encapsulates the queried data in the response message of the data acquisition request. Sending the response message to the management device.
  • Step 102 After receiving the data response message sent by the proxy device, the management device obtains, from the data response packet, the number of returned records from the start index that meet the filtering condition. Data.
  • 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:
  • the method further includes:
  • the data is tree structure data based on the extensible markup language XML;
  • the data acquisition request carries at least the following parameters: Filter, Number, Start-index, and Filter-index;
  • the Filter parameter is used to specify the query mode of the data.
  • the Filter parameter contains an attribute type, and the type "subtree" indicates that the subtree query is performed by the subtree query.
  • Step 202 The proxy device locally queries the return record number of data from the start index that meets the filtering condition, and encapsulates the queried data in the response message of the data acquisition request. Sending the response message 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.
  • the NETCONF protocol mainly uses the get/get-config operation to obtain configuration management data. These two methods cannot solve the problem that the data acquisition fails because the message is too large to be sent when the large amount of data is acquired.
  • the embodiment of the present invention adds an operation, that is, a get-bulk operation, to the operation layer of the NETCONF protocol, which can specify the starting index and the number of returned entries, and the NETCONF management device sends the get-bulk to the NETCONF proxy device multiple times.
  • the operation can be used to obtain large batches of data in batches.
  • the index of the upper list can be specified as a filter condition, and the function of querying only a part of the data in the subtree can be realized.
  • the operational parameters of the get-bulk operation may include Filter, Number, Start-index, and Filter-index. among them:
  • Number is the content layer parameter, which is used to specify the number of records of the query data, that is, the number of data records returned.
  • the Number property is only allowed to appear on the node of the list type. When there are 2 or more lists nested, the Number property appears on which list type node, which indicates which subtree is queried. If the node of the list type containing the Number attribute contains a nested list, the number of records is the number of records of the deepest nested list.
  • the value of the Number attribute ranges from 0 to 1000, that is, the most Multiple designation returns 1000 records. Number is specified as 0 to indicate that the number of returned data entries is not limited.
  • the Start-index parameter is a content layer parameter, and its specific form is a key field of a list type node.
  • the list containing the Number property and the key field of the list contained in the list are always used to locate the starting index, and the containing or nesting contains the list (list containing the Number property)
  • the key fields of those lists can be used as a positioning start index or as a filter condition.
  • the meaning of the filter condition is that when the data and filter conditions that the NETCONF proxy device sequentially queries do not match, the proxy device automatically terminates the query, that is, the query ends, so setting the filter condition can complete the query with smaller granularity and more precision.
  • Start-index can be specified in part, but when multiple lists are nested, if the start-index of the previous list is not specified, the Start-index of this layer list is not allowed. When the Start-index is not specified, it means that the query starts from the first one.
  • the management device and the agent establish a connection. After the establishment is successful, the two parties exchange capabilities.
  • the management device sends a get-bulk operation request.
  • the proxy device After receiving the get-bulk operation request, the proxy device parses the operation parameters such as the filter condition, the start index, and the number of returned records, completes the data query, and responds to the response message.
  • the proxy device sends a response packet to the management device.
  • the management device determines the next operation according to the query result. If the query continues, specify the parameters of the next get-bulk operation, and repeat steps 3-6 until the query is terminated.
  • FIG. 3 is a flowchart of a 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 a Manager and an agent and performing a capability negotiation process includes the following steps:
  • Step 301 The Manager and the agent mutually send hello messages.
  • Step 302 negotiateate the get-bulk capability.
  • Step 303 If the get-bulk capability negotiation is successful, go to step 304, otherwise go to step 305.
  • Step 304 Establish a connection.
  • Step 305 Close the connection.
  • FIG. 4 is a flowchart of interaction between a management device and a proxy device according to an embodiment of the present invention. As shown in FIG. 4, the process of initiating and responding to a get-bulk operation request includes the following steps:
  • Step 401 The Manager determines parameters of the get-bulk operation, such as a subtree, a number of returned records, an index of the starting record, and a filter condition.
  • Step 402 The Manager sends a get-bulk operation request to the Agent.
  • Step 403 The Agent receives the get-bulk operation request.
  • Step 404 The Agent parses the operation parameters and processes the get-bulk operation request.
  • Step 405 The Agent sends a get-bulk response to the client.
  • Step 406 The Manager receives the get-bulk response.
  • Step 407 The Manager processes the get-bulk response.
  • Step 408 The Manager determines whether to continue to query the data. If the query continues, the process proceeds to step 401, otherwise the current process ends.
  • 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 the Agent processing a get-bulk operation request includes the following steps:
  • Step 501 Receive a get-bulk operation request.
  • Step 502 Process the get-bulk operation request.
  • Step 503 If no abnormality occurs during the process, the process proceeds to step 504, otherwise 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 a get-bulk response message is sent to the Manager.
  • Step 506 Send an abnormal packet to the Manager, and notify the Manager of the abnormality of the packet caused by the excessive amount of data.
  • Step 507 Send an exception packet to the Manager, and notify the Manager of the exception information.
  • the get-bulk operation request is initiated by the NETCONF management device, and after receiving the NETCONF proxy device, the query mode, the number of query records, and the number of query records specified by the operation parameters such as Filter, Number, Start-index, and Filter-index are carried. Record the starting index, filter conditions, etc. to obtain the query data, and return the data to the NETCONF management device after the query is completed.
  • the NETCONF proxy device obtains the amount of data as required by the NETCONF management device If the message size limit or the transmission condition limit is exceeded, the message will not be sent. When this happens, the NETCONF management device can adjust the operation parameters to reduce the amount of returned data, such as reducing the value of the Number parameter and setting finer filtering conditions. Wait, start the get-bulk operation request again.
  • the NETCONF management device needs to query When the amount of data that the NETCONF management device needs to query is large, it can be completed by initiating multiple consecutive get-bulk operation requests.
  • the specific way is: when the next get-bulk request is initiated, the index of the last record of the last returned data is used as the starting index of the next get-bulk request.
  • leafa1, leafa11, leafa111, and leafa21 are keys of lista, lista1, lista11, and lista2, respectively.
  • the stored data is represented by a table as shown in Table 1 below:
  • the get-bulk request may cause the acquisition to fail. You can use the get-bulk request to get some data each time, get it multiple times, and finally get all the data.
  • the initial request does not specify the key of all the lists, the number of return records can be set to a fixed number (in this case, set to 10) or can be set to be automatically adjusted by the NETCONF proxy device, for example, the following get-bulk request is issued:
  • the number of returned records is 5, which is less than the specified number of returned records of 10, indicating the end of the query.
  • the first query does not specify the key of the listlist (ie lista).
  • the number of returned records is specified as 5. For example, the following get-bulk operation request is issued:
  • the returned data is as follows:
  • the number of returned data records is 2, which is less than the specified number of returned records, which means the query ends.
  • the part of the data is all the data of the lista1 subtree when the key of the lista is 1.
  • the exact acquisition of the partial data can be completed by setting the filtering condition. For example, setting the key of the lista to 1 is a filtering condition, and each part of the data of the lista1 subtree is obtained. For example, 4 records), if you get multiple times, you can complete it. The first time the following get-bulk operation request is issued:
  • the returned data is as follows:
  • the returned data is as follows:
  • the number of returned data records is 3, which is less than the specified number of returned records of 4, indicating the end of the query.
  • the technical solution of the embodiment of the present invention is completely zero, which makes large data volume acquisition possible.
  • the Get-bulk operation method can complete the batch acquisition of a specified amount of data in a batch, and the NETCONF management station can use the method multiple times and continuously, and finally achieve the purpose of obtaining large-volume data in the NETCONF proxy device.
  • the technical solution of the embodiment of the present invention does not require maintenance status, breakpoints, and the like, and the management station and the proxy device are simple to implement. There is no connection and continuity between multiple get-bulk operations, and each request and response is independent.
  • 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 at least an operation parameter of a filter condition, a start index, and a return record number;
  • the receiving unit 62 is configured to receive a data response message sent by the proxy device.
  • the obtaining unit 63 is configured to obtain, from the data response packet, the filter condition that meets the filtering condition.
  • the return record from the start index records a number of data.
  • 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
  • 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 acquisition request carries at least the following parameters:
  • the Filter parameter is used to specify a query mode of the data, and the Filter parameter includes an attribute type, and the type is a subtree, indicating that the data is queried by the subtree;
  • the number parameter is a number of records for specifying the query data, and the attribute of the Number parameter is only used on the node of the list type, and is used to indicate the subtree to be queried;
  • the Start-index parameter is a key field of a list type node; when there are multiple levels of list nesting, the key field of the list nested by the list containing the Number attribute is used to start the index, and the inclusion or nesting The key field of the list containing the list of the Number attribute is used to start the index or filter condition;
  • the Filter-index is only used on the node of the list type, and is used to indicate whether the key field of the list is used only for the starting index or for the starting index and also serves as a filtering condition.
  • 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 acquire at least an operation parameter of a filter condition, a start index, and a return record number carried in the data acquisition request;
  • the query unit 72 is configured to locally query, according to the filtering condition, the return record number of data from the start index;
  • 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 request carries at least the following parameters:
  • the Filter parameter is used to specify a query mode of the data, and the Filter parameter includes an attribute type, and the type is a subtree, indicating that the data is queried by the subtree;
  • the number parameter is a number of records for specifying the query data, and the attribute of the Number parameter is only used on the node of the list type, and is used to indicate the subtree to be queried;
  • the Start-index parameter is a key field of a list type node; when there are multiple layers of list nesting, The key field of the list nested by the list containing the Number attribute is used to start the index, and the key field of the list containing or nesting the list containing the Number attribute is used to start the index or filter condition;
  • the Filter-index is only used on the node of the list type, and is used to indicate whether the key field of the list is used only for the starting index or for the starting index and also serves as a filtering condition.
  • 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 makes the large data volume acquisition possible by adopting the zeroing method, and does not need maintenance state, breakpoint and other information, the management station and the proxy device are simple to implement, the data query granularity is adjustable, the query mode is flexible, and the query precision is high. .

Landscapes

  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
  • Computer And Data Communications (AREA)

Abstract

L'invention concerne un procédé et un appareil d'acquisition de données, ainsi qu'un support de stockage. Le procédé comprend les étapes suivantes : un dispositif de gestion détermine si un dispositif proxy supporte une opération d'acquisition de données étendue, et après détermination que le dispositif proxy supporte l'opération d'acquisition de données étendue, envoie une demande d'acquisition de données étendue au dispositif proxy, la demande d'acquisition de données portant au moins les paramètres d'opération de condition de filtrage, d'indice de départ et de nombre d'enregistrements de retour ; et après réception d'un paquet de réponse de données envoyé par le dispositif proxy, le dispositif de gestion acquiert, à partir du paquet de réponse de données, des données qui satisfont la condition de filtrage, qui partent de l'indice de départ, et dont la quantité est le nombre d'enregistrements de retour.
PCT/CN2015/083893 2015-01-07 2015-07-13 Procédé et appareil d'acquisition de données, et support de stockage WO2016110078A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510007236.2A CN105827424A (zh) 2015-01-07 2015-01-07 数据获取方法及装置
CN201510007236.2 2015-01-07

Publications (1)

Publication Number Publication Date
WO2016110078A1 true WO2016110078A1 (fr) 2016-07-14

Family

ID=56355469

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/083893 WO2016110078A1 (fr) 2015-01-07 2015-07-13 Procédé et appareil d'acquisition de données, et support de stockage

Country Status (2)

Country Link
CN (1) CN105827424A (fr)
WO (1) WO2016110078A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020034155A1 (fr) * 2018-08-16 2020-02-20 朱小军 Protéine de données biochimiques agissant sur un corps de cellule de données biomimétique
CN112307486A (zh) * 2019-07-29 2021-02-02 华为技术有限公司 一种权限获取方法、设备和系统
CN113676437A (zh) * 2020-05-14 2021-11-19 中国移动通信集团云南有限公司 参数解析方法、参数获取方法、参数设置方法以及装置

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108073661A (zh) * 2016-11-18 2018-05-25 北京京东尚科信息技术有限公司 数据检索方法及装置、报表生成系统及方法
CN112887113A (zh) * 2019-11-29 2021-06-01 华为技术有限公司 处理数据的方法、装置及系统
CN111181772B (zh) * 2019-12-12 2022-03-29 新华三大数据技术有限公司 网络协议下发方法、装置及系统

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101110822A (zh) * 2007-07-06 2008-01-23 华为技术有限公司 基于网络配置协议的事件通知发送方法、系统及设备
CN102355374A (zh) * 2011-10-28 2012-02-15 杭州华三通信技术有限公司 一种数据获取方法和设备
CN102368716A (zh) * 2011-11-29 2012-03-07 迈普通信技术股份有限公司 一种网络配置协议的数据获取方法及网络配置服务器
CN104065514A (zh) * 2014-07-02 2014-09-24 清华大学 一种基于netconf中继的家庭网络管理方法
US20140365621A1 (en) * 2013-06-06 2014-12-11 Alcatel-Lucent Canada, Inc. Netconf snmp gateway

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101110822A (zh) * 2007-07-06 2008-01-23 华为技术有限公司 基于网络配置协议的事件通知发送方法、系统及设备
CN102355374A (zh) * 2011-10-28 2012-02-15 杭州华三通信技术有限公司 一种数据获取方法和设备
CN102368716A (zh) * 2011-11-29 2012-03-07 迈普通信技术股份有限公司 一种网络配置协议的数据获取方法及网络配置服务器
US20140365621A1 (en) * 2013-06-06 2014-12-11 Alcatel-Lucent Canada, Inc. Netconf snmp gateway
CN104065514A (zh) * 2014-07-02 2014-09-24 清华大学 一种基于netconf中继的家庭网络管理方法

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020034155A1 (fr) * 2018-08-16 2020-02-20 朱小军 Protéine de données biochimiques agissant sur un corps de cellule de données biomimétique
CN112307486A (zh) * 2019-07-29 2021-02-02 华为技术有限公司 一种权限获取方法、设备和系统
CN113676437A (zh) * 2020-05-14 2021-11-19 中国移动通信集团云南有限公司 参数解析方法、参数获取方法、参数设置方法以及装置
CN113676437B (zh) * 2020-05-14 2023-08-18 中国移动通信集团云南有限公司 参数获取方法、参数设置方法以及装置

Also Published As

Publication number Publication date
CN105827424A (zh) 2016-08-03

Similar Documents

Publication Publication Date Title
WO2016110078A1 (fr) Procédé et appareil d'acquisition de données, et support de stockage
JP7014887B2 (ja) Ｐｄｕタイプ設定方法、ｕｅポリシー設定方法、および関連エンティティ
US20230319534A1 (en) Cross-resource subscription for m2m service layer
KR102415845B1 (ko) 사물 인터넷 리소스 구독 방법, 디바이스, 및 시스템
US11233666B2 (en) Policy control method, network element, and system
US10798646B2 (en) Network slice determining method and system, and apparatus
CN102148817B (zh) 配置网络设备的方法、客户端、服务器端及网络系统
EP4408042A2 (fr) Modèle léger d'informations iot
US20180063879A1 (en) Apparatus and method for interoperation between internet-of-things devices
WO2020173080A1 (fr) Procédé et appareil de demande d'informations de chaîne d'appels
CN111786998A (zh) 基于微服务调用的权限管理方法、装置及存储介质
US20230045914A1 (en) Method and apparatus for controlling device in internet of things, and gateway device and storage medium
WO2016110070A1 (fr) Procédé et dispositif d'acquisition de données et support de stockage
CN110768818B (zh) 一种网络管理方法和装置
CN114416508A (zh) 应用性能监控方法和装置、存储介质及电子设备
CN111064729B (zh) 报文的处理方法及装置、存储介质和电子装置
CN116347467B (zh) 5g网络中udr进行用户数据管理方法及系统
WO2017000540A1 (fr) Procédé et dispositif d'interrogation de données
EP3863312A1 (fr) Procédé et dispositif de publication d'api
US11956337B2 (en) Message parsing method, data transmit end, data receive end, and system
CN111193805B (zh) 一种资源发现的方法及装置
EP3211922A1 (fr) Procédé d'enregistrement et procédé de communication pour noeud spécialisé pour application et noeud
TWI446769B (zh) 處理於軟體及應用控制管理物件中步驟執行結果的方法
CN107784006B (zh) 数据处理方法及装置
US11456889B2 (en) Information notification method, apparatus, and system

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

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

Country of ref document: EP

Kind code of ref document: A1