CN105827424A - Data acquisition method and data acquisition device - Google Patents
Data acquisition method and data acquisition device Download PDFInfo
- Publication number
- CN105827424A CN105827424A CN201510007236.2A CN201510007236A CN105827424A CN 105827424 A CN105827424 A CN 105827424A CN 201510007236 A CN201510007236 A CN 201510007236A CN 105827424 A CN105827424 A CN 105827424A
- Authority
- CN
- China
- Prior art keywords
- list
- data
- index
- data acquisition
- parameter
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
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
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Computer And Data Communications (AREA)
Abstract
The embodiment of the invention discloses a data acquisition method and a data acquisition device. The data acquisition method comprises the steps that management equipment confirms whether proxy equipment supports an extended data acquisition operation or not, and sends an extended data acquisition request to the proxy equipment after confirming that the proxy equipment supports the extended data acquisition operation; the data acquisition request at least carries operating parameters of a filtering condition, a starting index and the return record number; the management equipment receives a data response message sent by the proxy equipment and acquires the return record number of data, which conforms to the filtering condition and starts from the starting index, from the data response message.
Description
Technical field
The present invention relates to webmaster management technique based on NETCONF agreement, particularly relate to a kind of data capture method and device.
Background technology
Use in the system of NETCONF protocol realization network equipments configuration management, NETCONF management equipment (Manager) is when obtaining all kinds of configuration management data of agent equipment (Agent), get/getconfig method is generally used to obtain these data, when data volume is the biggest, response message, probably due to cannot send too greatly, causes get operation unsuccessful.Additionally, when obtaining data, management equipment often has only to a part of data of certain subtree in the configuration management information of the acquisition network equipment, without the data obtaining whole subtrees, although management equipment carries out data screening after can subtree information all being got again, but this data acquiring mode efficiency is the lowest, and for no reason increases network traffics.
Summary of the invention
For solving above-mentioned technical problem, the embodiment of the present invention provides a kind of data capture method and device, can obtain in the middle part of agent equipment data in batches easily, and data acquiring mode is flexible.
The technical scheme is that and be achieved in that:
A kind of data capture method, including:
Management equipment confirms whether agent equipment supports the data acquisition operations of extension, and after confirming to support, sends the data acquisition request of extension to described agent equipment；Described data acquisition request at least carries filtercondition, initial index, the operating parameter of Record to return；
After described management equipment receives the data response message that described agent equipment sends, obtain from described data response message and meet described filtercondition, described Record to return data from described initial index.
Preferably, described management equipment confirms whether agent equipment supports the data acquisition operations of extension, including:
Described management equipment is to described agent equipment transmitting capacity inquiry request, and receives the capabilities response that described agent equipment sends, and confirms whether described agent equipment supports the data acquisition operations of extension according to the ability information carried in described capabilities response.
Preferably, described data are tree data based on expandable mark language XML；
Described data acquisition request at least carries following parameter:
Filter、Number、Start-index、Filter-index；
Wherein, described Filter parameter is for specifying the inquiry mode of data, and it is to show during subtree that data are inquired about by subtree that described Filter parameter comprises attribute type, described type；
Described Number parameter is the record number for given query data, and the attribute of described Number parameter is only used on the node of list list type, for indicating subtree to be checked；
Described Start-index parameter is the key field of list type node；When there being multilamellar list nesting, comprise the key field of list nested for list of described Number attribute for initial index, and comprise or comprise described in nesting the key field of the list of the list of described Number attribute for initial index or filtercondition；
Described Filter-index is only used on the node of list type, for representing that the key field of list is only used for initial index, or for initiateing index and doubling as filtercondition.
Preferably, before described management equipment confirms the data acquisition operations whether agent equipment supports extension, described method also includes:
Described management equipment is set up with described agent equipment and is connected.
A kind of data capture method, including:
Agent equipment receives the data acquisition request of the extension that management equipment sends, and resolves described data acquisition request, at least obtains the filtercondition carried in described data acquisition request, initial index, the operating parameter of Record to return；
Described agent equipment goes out to meet described filtercondition, described Record to return data from described initial index at local search, and the data inquired are packaged in the response message of described data acquisition request, send described response message to described management equipment.
Preferably, before agent equipment receives the data acquisition request of the extension that management equipment sends, described method also includes:
Described agent equipment receives the capability query request that described management equipment sends, and confirms self whether to support the data acquisition operations of extension, and sends the information capability response carrying the data acquisition operations supporting extension when confirming to support to described management equipment.
Preferably, described data are tree data based on expandable mark language XML；
Described request at least carries following parameter:
Filter、Number、Start-index、Filter-index；
Wherein, described Filter parameter is for specifying the inquiry mode of data, and it is to show during subtree that data are inquired about by subtree that described Filter parameter comprises attribute type, described type；
Described Number parameter is the record number for given query data, and the attribute of described Number parameter is only used on the node of list list type, for indicating subtree to be checked；
Described Start-index parameter is the key field of list type node；When there being multilamellar list nesting, comprise the key field of list nested for list of described Number attribute for initial index, and comprise or comprise described in nesting the key field of the list of the list of described Number attribute for initial index or filtercondition；
Described Filter-index is only used on the node of list type, for representing that the key field of list is only used for initial index, or for initiateing index and doubling as filtercondition.
Preferably, before agent equipment receives the data acquisition request of the extension that management equipment sends, described method also includes:
Described agent equipment is set up with described management equipment and is connected.
A kind of data acquisition facility, including: confirmation unit, transmitting element, reception unit and acquiring unit, wherein:
Confirmation unit, for confirming whether agent equipment supports the data acquisition operations of extension, and triggers described transmitting element when confirming and supporting；
Transmitting element, for sending the data acquisition request of extension to described agent equipment；Described data acquisition request at least carries filtercondition, initial index, the operating parameter of Record to return；
Receive unit, for receiving the data response message that described agent equipment sends；
Acquiring unit, meets described filtercondition, described Record to return data from described initial index for obtaining from described data response message.
Preferably, described confirmation unit includes: sends subelement, receives subelement and confirm subelement, wherein:
Send subelement, for described agent equipment transmitting capacity inquiry request；
Receive subelement, for receiving the capabilities response that described agent equipment sends；
Confirm subelement, for confirming whether described agent equipment supports the data acquisition operations of extension according to the ability information carried in described capabilities response.
Preferably, described data are tree data based on expandable mark language XML；
Described data acquisition request at least carries following parameter:
Filter、Number、Start-index、Filter-index；
Wherein, described Filter parameter is for specifying the inquiry mode of data, and it is to show during subtree that data are inquired about by subtree that described Filter parameter comprises attribute type, described type；
Described Number parameter is the record number for given query data, and the attribute of described Number parameter is only used on the node of list list type, for indicating subtree to be checked；
Described Start-index parameter is the key field of list type node；When there being multilamellar list nesting, comprise the key field of list nested for list of described Number attribute for initial index, and comprise or comprise described in nesting the key field of the list of the list of described Number attribute for initial index or filtercondition；
Described Filter-index is only used on the node of list type, for representing that the key field of list is only used for initial index, or for initiateing index and doubling as filtercondition.
A kind of data acquisition facility, including: receive unit, resolve acquiring unit, query unit and transmitting element, wherein:
Receive unit, for receiving the data acquisition request of the extension that management equipment sends；
Resolve acquiring unit, be used for resolving described data acquisition request, at least obtain the filtercondition carried in described data acquisition request, initial index, the operating parameter of Record to return；
Query unit, for going out to meet described filtercondition, described Record to return data from described initial index at local search；
Transmitting element, for the data inquired being packaged in the response message of described data acquisition request, sends described response message to described management equipment.
Preferably, described device also includes: confirmation unit；
Described reception unit, is additionally operable to receive the capability query request that described management equipment sends；
Described confirmation unit, is used for the data acquisition operations confirming self whether to support extension, and triggers the information capability response that described transmitting element carries the data acquisition operations of support extension to the transmission of described management equipment when confirming and supporting.
Preferably, described data are tree data based on expandable mark language XML；
Described request at least carries following parameter:
Filter、Number、Start-index、Filter-index；
Wherein, described Filter parameter is for specifying the inquiry mode of data, and it is to show during subtree that data are inquired about by subtree that described Filter parameter comprises attribute type, described type；
Described Number parameter is the record number for given query data, and the attribute of described Number parameter is only used on the node of list list type, for indicating subtree to be checked；
Described Start-index parameter is the key field of list type node；When there being multilamellar list nesting, comprise the key field of list nested for list of described Number attribute for initial index, and comprise or comprise described in nesting the key field of the list of the list of described Number attribute for initial index or filtercondition；
Described Filter-index is only used on the node of list type, for representing that the key field of list is only used for initial index, or for initiateing index and doubling as filtercondition.
In the embodiment of the present invention, obtain operation by growth data, set up the operating parameter of filtercondition, initial index, Record to return etc. for data acquisition operations, can be to agent equipment batch fetching portion data.The technical scheme of the embodiment of the present invention, uses the mode that breaks the whole up into parts, and makes big data quantity obtain and is possibly realized；And need not the information such as maintenance state, breakpoint, management station and agent equipment realization simplicity, data query granularity is adjustable, and inquiry mode is flexible, and inquiry precision is high.
Accompanying drawing explanation
Fig. 1 is the flow chart of the data capture method of the embodiment of the present invention one；
Fig. 2 is the flow chart of the data capture method of the embodiment of the present invention two；
Fig. 3 is the management equipment flow chart with agent equipment negotiation of the embodiment of the present invention；
Fig. 4 is flow chart mutual between management equipment and the agent equipment of the embodiment of the present invention；
Fig. 5 is the flow chart that the agent equipment of the embodiment of the present invention carries out data query；
Fig. 6 is the composition structural representation of the data acquisition facility of the embodiment of the present invention one；
Fig. 7 is the composition structural representation of the data acquisition facility of the embodiment of the present invention two.
Detailed description of the invention
For making the object, technical solutions and advantages of the present invention clearer, by the following examples and referring to the drawings, the present invention is described in more detail.
Below by way of concrete example, it is further elucidated with the essence of the technical scheme of the embodiment of the present invention.
Fig. 1 is the flow chart of the data capture method of the embodiment of the present invention one, as it is shown in figure 1, the data capture method of this example comprises the following steps:
Step 101, management equipment confirms whether agent equipment supports the data acquisition operations of extension, and after confirming to support, sends the data acquisition request of extension to described agent equipment.
In the embodiment of the present invention, described data acquisition request at least carries filtercondition, initial index, the operating parameter of Record to return.
Described data are tree data based on expandable mark language XML；
Described data acquisition request at least carries following parameter:
Filter、Number、Start-index、Filter-index；
Wherein, Filter parameter is for specifying the inquiry mode of data, and Filter parameter comprises an attribute type, and type shows to inquire about by subtree for " subtree ", i.e. the subtree that inquiry nesting comprises.
Number is content layer parameter, for the record number of given query data, the data acknowledgment number i.e. returned.Number attribute only allows to occur on the node of list type, and when there being the list nesting of 2 or more than 2, Number attribute occurs on the node of which list type, and just explanation is to inquire about which subtree.If the node of the list type comprising Number attribute comprises nested list, then record number is the record number of the deepest nested list.The span of Number attribute is 0～1000, at most specify i.e. every time and return 1000 records, Number is appointed as 0 expression return Data Entry number and is not intended to, NETCONF agent equipment can carry out Automatic adjusument according to self-ability and current data size cases, the record that return as much as possible is complete on the premise of ensureing message not super large.
In the embodiment of the present invention, data acquisition request is get-bulk operation, the embodiment of the present invention is by the operation layer newly-increased one operation in NETCONF agreement, i.e. get-bulk operates, this operation can be specified initial index and return entry number, NETCONF management equipment operates by repeatedly issuing get-bulk to NETCONF agent equipment, can realize obtaining high-volume data in batches, in the case of there is multiple list nesting, the index that can specify upper strata list is filtercondition, it is achieved the only function of a part of data in query sub tree.In one get-bulk request, the node of 1 list type at most can only be had to comprise Number attribute.
Start-index parameter is content layer parameter, and its concrete manifestation form is the key field of list type node.When there being multilamellar list nesting to comprise, the list comprising Number attribute and this list the key field of the nested list comprised always for positioning initial index, and comprise or the key field of those list that nesting comprises this list (list comprising Number attribute) can serve as positioning initial index, it is also possible to it is used simultaneously as filtercondition.Be meant that as filtercondition, when NETCONF agent equipment sequential query to data and filtercondition be not inconsistent time, then agent equipment terminates inquiry automatically, i.e. poll-final, so, filtercondition is set and can complete that granularity is less, inquire about more accurately.Start-index can partly specify, but when multiple list nestings comprise, if the Start-index of preceding layer list does not specify completely, does not allows to specify the Start-index of this layer of list.When not specifying Start-index, represent and start a query at from the 1st.
Filter-index is content layer parameter, only allows to occur on the node of list type, for representing that the key field of this list is only used for positioning initial index, is still used simultaneously as filtercondition.During Filter-index=" no ", represent and be only used for positioning initial index, during Filter-index=" yes ", represent and be used simultaneously as filtercondition.During as filtercondition, the key field of this list must all be specified, and does not allow not specify or part appointment.When multiple list nestings comprise, only allowing the upper strata list comprising the list of Number attribute to use Filter-index attribute, if upper strata list is multilayer nest comprises list, the list the most only allowing top nested continuously uses Filter-index attribute.
Agent equipment receives the data acquisition request of the extension that management equipment sends, and resolves described data acquisition request, at least obtains the filtercondition carried in described data acquisition request, initial index, the operating parameter of Record to return；
Described agent equipment goes out to meet described filtercondition, described Record to return data from described initial index at local search, and the data inquired are packaged in the response message of described data acquisition request, send described response message to described management equipment.
Step 102, after described management equipment receives the data response message that described agent equipment sends, obtains from described data response message and meets described filtercondition, described Record to return data from described initial index.
In the embodiment of the present invention, before described management equipment confirms the data acquisition operations whether agent equipment supports extension, described management equipment is set up with described agent equipment and is connected.
Fig. 2 is the flow chart of the data capture method of the embodiment of the present invention two, as in figure 2 it is shown, the data capture method of this example comprises the following steps:
Step 201, agent equipment receives the data acquisition request of the extension that management equipment sends, resolves described data acquisition request, at least obtains the filtercondition carried in described data acquisition request, initial index, the operating parameter of Record to return.
In the embodiment of the present invention, first management equipment send the data acquisition request of extension to described agent equipment.
Before the data acquisition request of the extension that management equipment sends to agent equipment, described method also includes:
Described agent equipment receives the capability query request that described management equipment sends, and confirms self whether to support the data acquisition operations of extension, and sends the information capability response carrying the data acquisition operations supporting extension when confirming to support to described management equipment.
In the embodiment of the present invention, described data are tree data based on expandable mark language XML；Described data acquisition request at least carries following parameter: Filter, Number, Start-index, Filter-index；
Wherein, Filter parameter is for specifying the inquiry mode of data, and Filter parameter comprises an attribute type, and type shows to inquire about by subtree for " subtree ", i.e. the subtree that inquiry nesting comprises.
Number is content layer parameter, for the record number of given query data, the data acknowledgment number i.e. returned.Number attribute only allows to occur on the node of list type, and when there being the list nesting of 2 or more than 2, Number attribute occurs on the node of which list type, and just explanation is to inquire about which subtree.If the node of the list type comprising Number attribute comprises nested list, then record number is the record number of the deepest nested list.The span of Number attribute is 0～1000, at most specify i.e. every time and return 1000 records, Number is appointed as 0 expression return Data Entry number and is not intended to, NETCONF agent equipment can carry out Automatic adjusument according to self-ability and current data size cases, the record that return as much as possible is complete on the premise of ensureing message not super large.In one get-bulk request, the node of 1 list type at most can only be had to comprise Number attribute.
Start-index parameter is content layer parameter, and its concrete manifestation form is the key field of list type node.When there being multilamellar list nesting to comprise, the list comprising Number attribute and this list (list comprising Number attribute) the key field of the nested list comprised always for positioning initial index, and comprise or the key field of those list that nesting comprises this list can serve as positioning initial index, it is also possible to it is used simultaneously as filtercondition.Be meant that as filtercondition, when NETCONF agent equipment sequential query to data and filtercondition be not inconsistent time, then agent equipment terminates inquiry automatically, i.e. poll-final, so, filtercondition is set and can complete that granularity is less, inquire about more accurately.Start-index can partly specify, but when multiple list nestings comprise, if the Start-index of preceding layer list does not specify completely, does not allows to specify the Start-index of this layer of list.When not specifying Start-index, represent and start a query at from the 1st.
Filter-index is content layer parameter, only allows to occur on the node of list type, for representing that the key field of this list is only used for positioning initial index, is still used simultaneously as filtercondition.During Filter-index=" no ", represent and be only used for positioning initial index, during Filter-index=" yes ", represent and be used simultaneously as filtercondition.During as filtercondition, the key field of this list must all be specified, and does not allow not specify or part appointment.When multiple list nestings comprise, only allowing the upper strata list comprising the list of Number attribute to use Filter-index attribute, if upper strata list is multilayer nest comprises list, the list the most only allowing top nested continuously uses Filter-index attribute.
Step 202, agent equipment goes out to meet described filtercondition, described Record to return data from described initial index at local search, and the data inquired are packaged in the response message of described data acquisition request, send described response message to described management equipment.
In the embodiment of the present invention, before agent equipment receives the data acquisition request of the extension that management equipment sends, described agent equipment is set up with described management equipment and is connected.
In order to be more fully understood that above-described embodiment, preferred embodiment and relevant drawings below in conjunction with above-described embodiment describe in detail.
NETCONF agreement mainly uses get/get-config operation to obtain configuration management data at present, and both modes all cannot solve when obtaining high-volume data, the problem causing because of excessive cannot the sending of message obtaining data failure.
The embodiment of the present invention is by the operation layer newly-increased one operation in NETCONF agreement, i.e. get-bulk operates, this operation can be specified initial index and return entry number, NETCONF management equipment operates by repeatedly issuing get-bulk to NETCONF agent equipment, can realize obtaining high-volume data in batches, in the case of there is multiple list nesting, it is possible to specify the index of upper strata list is filtercondition, it is achieved the only function of a part of data in query sub tree.
The operating parameter of get-bulk operation can include Filter, Number, Start-index and Filter-index etc..Wherein:
Filter parameter is for specifying the inquiry mode of data, and Filter parameter comprises an attribute type, and type shows to inquire about by subtree for " subtree ", i.e. the subtree that inquiry nesting comprises.
Number is content layer parameter, for the record number of given query data, the data acknowledgment number i.e. returned.Number attribute only allows to occur on the node of list type, and when there being the list nesting of 2 or more than 2, Number attribute occurs on the node of which list type, and just explanation is to inquire about which subtree.If the node of the list type comprising Number attribute comprises nested list, then record number is the record number of the deepest nested list.The span of Number attribute is 0～1000, at most specify i.e. every time and return 1000 records, Number is appointed as 0 expression return Data Entry number and is not intended to, NETCONF agent equipment can carry out Automatic adjusument according to self-ability and current data size cases, the record that return as much as possible is complete on the premise of ensureing message not super large.In one get-bulk request, the node of 1 list type at most can only be had to comprise Number attribute.
Start-index parameter is content layer parameter, and its concrete manifestation form is the key field of list type node.When there being multilamellar list nesting to comprise, the list comprising Number attribute and this list the key field of the nested list comprised always for positioning initial index, and comprise or the key field of those list that nesting comprises this list (list comprising Number attribute) can serve as positioning initial index, it is also possible to it is used simultaneously as filtercondition.Be meant that as filtercondition, when NETCONF agent equipment sequential query to data and filtercondition be not inconsistent time, then agent equipment terminates inquiry automatically, i.e. poll-final, so, filtercondition is set and can complete that granularity is less, inquire about more accurately.Start-index can partly specify, but when multiple list nestings comprise, if the Start-index of preceding layer list does not specify completely, does not allows to specify the Start-index of this layer of list.When not specifying Start-index, represent and start a query at from first.
Filter-index is content layer parameter, only allows to occur on the node of list type, for representing that the key field of this list is only used for positioning initial index, is still used simultaneously as filtercondition.During Filter-index=" no ", represent and be only used for positioning initial index, during Filter-index=" yes ", represent and be used simultaneously as filtercondition.During as filtercondition, the key field of this list must all be specified, and does not allow not specify or part appointment.When multiple list nestings comprise, only allowing the upper strata list comprising the list of Number attribute to use Filter-index attribute, if upper strata list is multilayer nest comprises list, the list the most only allowing top nested continuously uses Filter-index attribute.
By returning entry number, NETCONF management equipment can judge whether inquiry terminates.If specifying Record to return, then, when the record number returned is less than the number specified, represent poll-final.If not specified Record to return, i.e. by NETCONF agent equipment Automatic adjusument record number, then, when the record number returned is 0, represent poll-final.
The handling process of the embodiment of the present invention comprises the following steps:
1, management equipment and agency set up and connect, and after being successfully established, both sides carry out capabilities exchange.
2, management equipment uses agent functionality to find to confirm whether agent equipment supports that get-bulk operates, after confirming to support, it is possible to use get-bulk operates, and otherwise can not use.
3, management equipment sends get-bulk operation requests.
4, after agent equipment receives get-bulk operation requests, resolve the operating parameter such as filtercondition, initial index, Record to return, complete data query response response message.
5, agent equipment sends response message to management equipment.
6, after management equipment receives response message, determine that next step operates according to Query Result, if continuing inquiry, specifying the parameter of next get-bulk operation, repeating step 3～6, until terminating inquiry.
Fig. 3 is the flow chart that management equipment (Manager) and the agent equipment (Agent) of the embodiment of the present invention is consulted, and comprises the following steps as it is shown on figure 3, Manager and Agent sets up to connect and carry out capability negotiation flow process:
Step 301:Manager and Agent send out hello packet mutually.
Step 302: consult get-bulk ability.
Step 303: if the success of get-bulk capability negotiation, then perform step 304, otherwise perform step 305.
Step 304: set up and connect.
Step 305: close and connect.
Fig. 4 is flow chart mutual between management equipment and the agent equipment of the embodiment of the present invention, and as shown in Figure 4, initiation and the responding process of get-bulk operation requests comprise the following steps:
Step 401:Manager determines the parameter that get-bulk operates, the parameter such as such as subtree, Record to return, the index of home record, filtercondition.
Step 402:Manager sends get-bulk operation requests to Agent.
Step 403:Agent receives get-bulk operation requests.
Step 404:Agent resolves operating parameter, processes get-bulk operation requests.
Step 405:Agent sends get-bulk response to Client.
Step 406:Manager receives get-bulk response.
Step 407:Manager processes get-bulk response.
Step 408:Manager judges whether to continue inquiry data, continues inquiry and then performs step 401, otherwise terminates currently processed.
Fig. 5 is the flow chart that the agent equipment of the embodiment of the present invention carries out data query, as it is shown in figure 5, the flow process that Agent processes get-bulk operation requests comprises the following steps:
Step 501: receive get-bulk operation requests.
Step 502: process get-bulk operation requests.
Step 503: without there are abnormal then jump procedure 504 in processing procedure, otherwise perform step 507.
Step 504: judge whether response message size exceedes restriction, then performs step 505 without exceeding restriction, otherwise performs step 506.
Step 505: inquiry data set is made into response message, sends get-bulk response message to Manager.
Step 506: send exception message to Manager, excessive for the data volume exception causing message is informed Manager.
Step 507: send exception message to Manager, abnormal information is informed Manager.
In the embodiment of the present invention, get-bulk operation requests is initiated by NETCONF management equipment, after NETCONF agent equipment receives, requirements such as the inquiry mode specified by operating parameters such as Filter, Number, Start-index and the Filter-index carried, inquiry record number, record start index, filtercondition obtains inquires about data, returns data to NETCONF management equipment after having inquired about.
Limit or the restriction of transmission condition if NETCONF agent equipment exceedes message size by the data volume that the requirement of NETCONF management equipment obtains, message will be unable to send, when this thing happens, NETCONF management equipment adjustable operating parameter is so that returning data volume and reducing, such as reduce the numerical value of Number parameter, finer filtercondition etc. is set, again initiate get-bulk operation requests.
Each get-bulk operation requests and return are independent process, and previous operation requests and return do not have any relation.
When the data volume that NETCONF management equipment needs inquiry is the biggest, can be completed by the continuous print get-bulk operation requests initiated repeatedly.Concrete mode is: when initiating get-bulk request next time, uses the index initial index as the request of get-bulk next time of the last the last item record returning data.
The query script of typical case application scenarios is exemplified below.
Assume to exist with drag:
Wherein, leafa1, leafa11, leafa111 and leafa21 are the key of lista, lista1, lista11 and lista2 respectively.
Assume that the data that this model stores are as follows:
Storage data form is expressed as follows shown in table 1:
| lista | lista1 | lista11 | lista2 | ||||
| leafa1 | leafa2 | leafa11 | leafa12 | leafa111 | leafa112 | leafa21 | leafa22 |
| 1 | test | 1 | test | 1 | test | 1 | test |
| 2 | test | 2 | test | ||||
| 3 | test | 3 | test | ||||
| 2 | test | 4 | test | ||||
| 5 | test | ||||||
| 3 | test | 6 | test | ||||
| 7 | test | ||||||
| 2 | test | 4 | test | 8 | test | 4 | test |
| 9 | test | 5 | test | ||||
| 10 | test | 6 | test | ||||
| 5 | test | 11 | test | 7 | test | ||
| 12 | test |
Table 1
Example 1
Assume to need to obtain all data of lista place subtree, i.e. all data in runic wire frame in table 2 below:
Table 2
Because data volume is more, may result in get request and obtain unsuccessfully, it is possible to use get-bulk asks, and each fetching portion data repeatedly obtain, are finally reached the purpose obtaining all data.First request does not specify the key of all list, and Record to return could be arranged to fixed number (this example is set to 10) it can also be provided that be automatically adjusted by NETCONF agent equipment, such as, issue following get-bulk and ask:
Return data and briefly express as follows:
Continue request next part data, be recorded as home record with the last item of the data of last time return, 10 records after inquiry home record:
Return data and briefly express as follows:
Record to return is 5, less than specifying Record to return 10, represents poll-final.
Example 2
Assume the total data needing to inquire about lista2 place subtree, i.e. data in runic wire frame in table 3 below:
Table 3
Number attribute can be arranged on lista2 place node, initiate get-bulk inquiry, inquire about the key not specifying lista2 upper strata list (i.e. lista) first, Record to return is appointed as 5, such as, issue following get-bulk operation requests:
Return data are as follows:
Continue request next part data, be recorded as home record with the last item of the data of last time return, 5 records after inquiry home record:
Return data are as follows:
Returning data acknowledgment number is 2, less than specifying Record to return 5, represents poll-final.
Example 3
Assume to want to accurately acquire the part data of certain subtree, such as the part data in lista1, i.e. data in runic wire frame in table 4 below:
Table 4
These part data are the key of lista all data of lista1 subtree when being 1, accurately fetching portion data can complete by arranging filtercondition, such as arranging the key of lista is 1 to be filtercondition, obtain the part data (this example is 4 records) of lista1 subtree every time, repeatedly obtain, then can complete.Issue following get-bulk operation requests for the first time:
Return data are as follows:
Continue to inquire about:
Return data are as follows:
Returning data acknowledgment number is 3, less than specifying Record to return 4, represents poll-final.
The technical scheme of the embodiment of the present invention breaks the whole up into parts, and makes big data quantity obtain and is possibly realized.Get-bulk operational approach can complete once batch and obtain the data of specified quantity, NETCONF management station can by multiple times, continuously with the method, be finally reached and obtain the purpose of high-volume data in NETCONF agent equipment.
The technical scheme of the embodiment of the present invention need not the information such as maintenance state, breakpoint, management station and agent equipment and realizes simplicity.Being not in contact with and continuity between multiple get-bulk operation, request and response each time are all independent.
The granularity of query of the technical scheme of the embodiment of the present invention is adjustable, and inquiry mode is flexible, and inquiry precision is high.The method can specify the contents such as the filtercondition of data, initial index and Record to return, can meet more flexible, granularity query demand adjustable, more accurate.
Fig. 6 is the composition structural representation of the data acquisition facility of the embodiment of the present invention one, and as shown in Figure 6, the data acquisition facility of this example includes validating that unit 60, transmitting element 61, receives unit 62 and acquiring unit 63, wherein:
Confirmation unit 60, for confirming whether agent equipment supports the data acquisition operations of extension, and triggers described transmitting element 61 when confirming and supporting；
Transmitting element 61, for sending the data acquisition request of extension to described agent equipment；Described data acquisition request at least carries filtercondition, initial index, the operating parameter of Record to return；
Receive unit 62, for receiving the data response message that described agent equipment sends；
Acquiring unit 63, meets described filtercondition, described Record to return data from described initial index for obtaining from described data response message.
The confirmation unit 60 of the embodiment of the present invention includes: sends subelement (not shown in Fig. 6), receives subelement (not shown in Fig. 6) and confirm subelement (not shown in Fig. 6), wherein:
Send subelement, for described agent equipment transmitting capacity inquiry request；
Receive subelement, for receiving the capabilities response that described agent equipment sends；
Confirm subelement, for confirming whether described agent equipment supports the data acquisition operations of extension according to the ability information carried in described capabilities response.
In the embodiment of the present invention, described data are tree data based on expandable mark language XML；
Described data acquisition request at least carries following parameter:
Filter、Number、Start-index、Filter-index；
Wherein, described Filter parameter is for specifying the inquiry mode of data, and it is to show during subtree that data are inquired about by subtree that described Filter parameter comprises attribute type, described type；
Described Number parameter is the record number for given query data, and the attribute of described Number parameter is only used on the node of list list type, for indicating subtree to be checked；
Described Start-index parameter is the key field of list type node；When there being multilamellar list nesting, comprise the key field of list nested for list of described Number attribute for initial index, and comprise or comprise described in nesting the key field of the list of the list of described Number attribute for initial index or filtercondition；
Described Filter-index is only used on the node of list type, for representing that the key field of list is only used for initial index, or for initiateing index and doubling as filtercondition.
It will be appreciated by those skilled in the art that the function that realizes of each processing unit in the data acquisition facility shown in Fig. 6 can refer to aforementioned data acquisition methods and the associated description of embodiment and understands.It will be appreciated by those skilled in the art that the function of each processing unit in the data acquisition facility shown in Fig. 6 can be realized by the program that runs on processor, it is possible to realized by concrete logic circuit.
Fig. 7 is the composition structural representation of the data acquisition facility of the embodiment of the present invention two, as it is shown in fig. 7, the data acquisition facility of this example includes receiving unit 70, resolving acquiring unit 71, query unit 72 and transmitting element 73, wherein:
Receive unit 70, for receiving the data acquisition request of the extension that management equipment sends；
Resolve acquiring unit 71, be used for resolving described data acquisition request, at least obtain the filtercondition carried in described data acquisition request, initial index, the operating parameter of Record to return；
Query unit 72, for going out to meet described filtercondition, described Record to return data from described initial index at local search；
Transmitting element 73, for the data inquired being packaged in the response message of described data acquisition request, sends described response message to described management equipment.
On the basis of the data acquisition facility shown in Fig. 7, described data acquisition facility also includes: confirmation unit (not shown in Fig. 7)；
Described reception unit 70, is additionally operable to receive the capability query request that described management equipment sends；
Described confirmation unit, is used for the data acquisition operations confirming self whether to support extension, and triggers the information capability response that described transmitting element 73 carries the data acquisition operations of support extension to the transmission of described management equipment when confirming and supporting.
In the embodiment of the present invention, described data are tree data based on expandable mark language XML；
Described request at least carries following parameter:
Filter、Number、Start-index、Filter-index；
Wherein, described Filter parameter is for specifying the inquiry mode of data, and it is to show during subtree that data are inquired about by subtree that described Filter parameter comprises attribute type, described type；
Described Number parameter is the record number for given query data, and the attribute of described Number parameter is only used on the node of list list type, for indicating subtree to be checked；
Described Start-index parameter is the key field of list type node；When there being multilamellar list nesting, comprise the key field of list nested for list of described Number attribute for initial index, and comprise or comprise described in nesting the key field of the list of the list of described Number attribute for initial index or filtercondition；
Described Filter-index is only used on the node of list type, for representing that the key field of list is only used for initial index, or for initiateing index and doubling as filtercondition.
It will be appreciated by those skilled in the art that the function that realizes of each processing unit in the data acquisition facility shown in Fig. 7 can refer to aforementioned data acquisition methods and the associated description of embodiment and understands.It will be appreciated by those skilled in the art that the function of each processing unit in the data acquisition facility shown in Fig. 7 can be realized by the program that runs on processor, it is possible to realized by concrete logic circuit.
On the premise of not conflicting, can merge between the technical scheme of the embodiment of the present invention.
In several embodiments provided by the present invention, it should be understood that disclosed method and smart machine, can realize by another way.Apparatus embodiments described above is only schematically, such as, the division of described unit, it is only a kind of logic function to divide, actual can have other dividing mode, such as when realizing: multiple unit or assembly can be in conjunction with, or are desirably integrated into another system, or some features can ignore, or do not perform.It addition, the coupling each other of shown or discussed each ingredient or direct-coupling or communication connection can be the INDIRECT COUPLING by some interfaces, equipment or unit or communication connection, can be being electrical, machinery or other form.
The above-mentioned unit illustrated as separating component can be or may not be physically separate, and the parts shown as unit can be or may not be physical location, i.e. may be located at a place, it is also possible to be distributed on multiple NE；Part or all of unit therein can be selected according to the actual needs to realize the purpose of the present embodiment scheme.
It addition, each functional unit in various embodiments of the present invention can be fully integrated in a processing unit, it is also possible to be that each unit is individually as a unit, it is also possible to two or more unit are integrated in a unit；Above-mentioned integrated unit both can realize to use the form of hardware, it would however also be possible to employ hardware adds the form of SFU software functional unit and realizes.
One of ordinary skill in the art will appreciate that: all or part of step realizing said method embodiment can be completed by the hardware that application instruction is relevant, aforesaid application can be stored in a computer read/write memory medium, this application upon execution, performs to include the step of said method embodiment；And aforesaid storage medium includes: movable storage device, read only memory (ROM, Read-OnlyMemory), the various media that can store application code such as random access memory (RAM, RandomAccessMemory), magnetic disc or CD.
Or, if the above-mentioned integrated unit of the embodiment of the present invention realizes using the form of software function module and as independent production marketing or when using, it is also possible to be stored in a computer read/write memory medium.Based on such understanding, the part that prior art is contributed by the technical scheme of the embodiment of the present invention the most in other words can embody with the form of software product, this computer software product is stored in a storage medium, including some instructions with so that a computer equipment (can be personal computer, server or the network equipment etc.) performs all or part of of method described in each embodiment of the present invention.And aforesaid storage medium includes: movable storage device, read only memory (ROM, Read-OnlyMemory), the various media that can store application code such as random access memory (RAM, RandomAccessMemory), magnetic disc or CD.
The above; being only the detailed description of the invention of the present invention, but protection scope of the present invention is not limited thereto, any those familiar with the art is in the technical scope that the invention discloses; change can be readily occurred in or replace, all should contain within protection scope of the present invention.
Claims (14)
1. a data capture method, it is characterised in that described method includes:
Management equipment confirms whether agent equipment supports the data acquisition operations of extension, and after confirming to support, sends the data acquisition request of extension to described agent equipment；Described data acquisition request at least carries filtercondition, initial index, the operating parameter of Record to return；
After described management equipment receives the data response message that described agent equipment sends, obtain from described data response message and meet described filtercondition, described Record to return data from described initial index.
Method the most according to claim 1, it is characterised in that described management equipment confirms whether agent equipment supports the data acquisition operations of extension, including:
Described management equipment is to described agent equipment transmitting capacity inquiry request, and receives the capabilities response that described agent equipment sends, and confirms whether described agent equipment supports the data acquisition operations of extension according to the ability information carried in described capabilities response.
Method the most according to claim 1 and 2, it is characterised in that described data are tree data based on expandable mark language XML；
Described data acquisition request at least carries following parameter:
Filter、Number、Start-index、Filter-index；
Wherein, described Filter parameter is for specifying the inquiry mode of data, and it is to show during subtree that data are inquired about by subtree that described Filter parameter comprises attribute type, described type；
Described Number parameter is the record number for given query data, and the attribute of described Number parameter is only used on the node of list list type, for indicating subtree to be checked；
Described Start-index parameter is the key field of list type node；When there being multilamellar list nesting, comprise the key field of list nested for list of described Number attribute for initial index, and comprise or comprise described in nesting the key field of the list of the list of described Number attribute for initial index or filtercondition；
Described Filter-index is only used on the node of list type, for representing that the key field of list is only used for initial index, or for initiateing index and doubling as filtercondition.
Method the most according to claim 1, it is characterised in that before described management equipment confirms the data acquisition operations whether agent equipment supports extension, described method also includes:
Described management equipment is set up with described agent equipment and is connected.
5. a data capture method, it is characterised in that described method includes:
Agent equipment receives the data acquisition request of the extension that management equipment sends, and resolves described data acquisition request, at least obtains the filtercondition carried in described data acquisition request, initial index, the operating parameter of Record to return；
Described agent equipment goes out to meet described filtercondition, described Record to return data from described initial index at local search, and the data inquired are packaged in the response message of described data acquisition request, send described response message to described management equipment.
Method the most according to claim 5, it is characterised in that before agent equipment receives the data acquisition request of the extension that management equipment sends, described method also includes:
Described agent equipment receives the capability query request that described management equipment sends, and confirms self whether to support the data acquisition operations of extension, and sends the information capability response carrying the data acquisition operations supporting extension when confirming to support to described management equipment.
Method the most according to claim 5, it is characterised in that described data are tree data based on expandable mark language XML；
Described request at least carries following parameter:
Filter、Number、Start-index、Filter-index；
Wherein, described Filter parameter is for specifying the inquiry mode of data, and it is to show during subtree that data are inquired about by subtree that described Filter parameter comprises attribute type, described type；
Described Number parameter is the record number for given query data, and the attribute of described Number parameter is only used on the node of list list type, for indicating subtree to be checked；
Described Start-index parameter is the key field of list type node；When there being multilamellar list nesting, comprise the key field of list nested for list of described Number attribute for initial index, and comprise or comprise described in nesting the key field of the list of the list of described Number attribute for initial index or filtercondition；
Described Filter-index is only used on the node of list type, for representing that the key field of list is only used for initial index, or for initiateing index and doubling as filtercondition.
Method the most according to claim 5, it is characterised in that before agent equipment receives the data acquisition request of the extension that management equipment sends, described method also includes:
Described agent equipment is set up with described management equipment and is connected.
9. a data acquisition facility, it is characterised in that described device includes: confirmation unit, transmitting element, reception unit and acquiring unit, wherein:
Confirmation unit, for confirming whether agent equipment supports the data acquisition operations of extension, and triggers described transmitting element when confirming and supporting；
Transmitting element, for sending the data acquisition request of extension to described agent equipment；Described data acquisition request at least carries filtercondition, initial index, the operating parameter of Record to return；
Receive unit, for receiving the data response message that described agent equipment sends；
Acquiring unit, meets described filtercondition, described Record to return data from described initial index for obtaining from described data response message.
Device the most according to claim 9, it is characterised in that described confirmation unit includes: send subelement, receive subelement and confirm subelement, wherein:
Send subelement, for described agent equipment transmitting capacity inquiry request；
Receive subelement, for receiving the capabilities response that described agent equipment sends；
Confirm subelement, for confirming whether described agent equipment supports the data acquisition operations of extension according to the ability information carried in described capabilities response.
11. according to the device described in claim 9 or 10, it is characterised in that described data are tree data based on expandable mark language XML；
Described data acquisition request at least carries following parameter:
Filter、Number、Start-index、Filter-index；
Wherein, described Filter parameter is for specifying the inquiry mode of data, and it is to show during subtree that data are inquired about by subtree that described Filter parameter comprises attribute type, described type；
Described Number parameter is the record number for given query data, and the attribute of described Number parameter is only used on the node of list list type, for indicating subtree to be checked；
Described Start-index parameter is the key field of list type node；When there being multilamellar list nesting, comprise the key field of list nested for list of described Number attribute for initial index, and comprise or comprise described in nesting the key field of the list of the list of described Number attribute for initial index or filtercondition；
Described Filter-index is only used on the node of list type, for representing that the key field of list is only used for initial index, or for initiateing index and doubling as filtercondition.
12. 1 kinds of data acquisition facilities, it is characterised in that described device includes: receive unit, resolve acquiring unit, query unit and transmitting element, wherein:
Receive unit, for receiving the data acquisition request of the extension that management equipment sends；
Resolve acquiring unit, be used for resolving described data acquisition request, at least obtain the filtercondition carried in described data acquisition request, initial index, the operating parameter of Record to return；
Query unit, for going out to meet described filtercondition, described Record to return data from described initial index at local search；
Transmitting element, for the data inquired being packaged in the response message of described data acquisition request, sends described response message to described management equipment.
13. devices according to claim 12, it is characterised in that described device also includes: confirmation unit；
Described reception unit, is additionally operable to receive the capability query request that described management equipment sends；
Described confirmation unit, is used for the data acquisition operations confirming self whether to support extension, and triggers the information capability response that described transmitting element carries the data acquisition operations of support extension to the transmission of described management equipment when confirming and supporting.
14. according to the device described in claim 12 or 13, it is characterised in that described data are tree data based on expandable mark language XML；
Described request at least carries following parameter:
Filter、Number、Start-index、Filter-index；
Wherein, described Filter parameter is for specifying the inquiry mode of data, and it is to show during subtree that data are inquired about by subtree that described Filter parameter comprises attribute type, described type；
Described Number parameter is the record number for given query data, and the attribute of described Number parameter is only used on the node of list list type, for indicating subtree to be checked；
Described Start-index parameter is the key field of list type node；When there being multilamellar list nesting, comprise the key field of list nested for list of described Number attribute for initial index, and comprise or comprise described in nesting the key field of the list of the list of described Number attribute for initial index or filtercondition；
Described Filter-index is only used on the node of list type, for representing that the key field of list is only used for initial index, or for initiateing index and doubling as filtercondition.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510007236.2A CN105827424A (en) | 2015-01-07 | 2015-01-07 | Data acquisition method and data acquisition device |
| PCT/CN2015/083893 WO2016110078A1 (en) | 2015-01-07 | 2015-07-13 | Data acquisition method and apparatus, and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510007236.2A CN105827424A (en) | 2015-01-07 | 2015-01-07 | Data acquisition method and data acquisition device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN105827424A true CN105827424A (en) | 2016-08-03 |
Family
ID=56355469
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510007236.2A Pending CN105827424A (en) | 2015-01-07 | 2015-01-07 | Data acquisition method and data acquisition device |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN105827424A (en) |
| WO (1) | WO2016110078A1 (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108073661A (en) * | 2016-11-18 | 2018-05-25 | 北京京东尚科信息技术有限公司 | Data retrieval method and device, report generating system and method |
| CN111181772A (en) * | 2019-12-12 | 2020-05-19 | 新华三大数据技术有限公司 | Network protocol issuing method, device and system |
| CN112887113A (en) * | 2019-11-29 | 2021-06-01 | 华为技术有限公司 | Method, device and system for processing data |
| CN113676437A (en) * | 2020-05-14 | 2021-11-19 | 中国移动通信集团云南有限公司 | Parameter analysis method, parameter acquisition method, parameter setting method and device |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2020034155A1 (en) * | 2018-08-16 | 2020-02-20 | 朱小军 | Biochemical data protein acting on biomimetic data cell body |
| CN112307486A (en) * | 2019-07-29 | 2021-02-02 | 华为技术有限公司 | Authority obtaining method, equipment and system |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102355374A (en) * | 2011-10-28 | 2012-02-15 | 杭州华三通信技术有限公司 | Data acquisition method and equipment |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101110822B (en) * | 2007-07-06 | 2011-11-02 | 华为技术有限公司 | Event notice sending method, system and equipment based on network configuration protocol |
| CN102368716A (en) * | 2011-11-29 | 2012-03-07 | 迈普通信技术股份有限公司 | Data acquisition method of network configuration protocol and network configuration server |
| US9258132B2 (en) * | 2013-06-06 | 2016-02-09 | Alcatel Lucent | NETCONF SNMP gateway |
| CN104065514A (en) * | 2014-07-02 | 2014-09-24 | 清华大学 | Home network management method based on network configuration protocol (NETCONF) relay |
-
2015
- 2015-01-07 CN CN201510007236.2A patent/CN105827424A/en active Pending
- 2015-07-13 WO PCT/CN2015/083893 patent/WO2016110078A1/en active Application Filing
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102355374A (en) * | 2011-10-28 | 2012-02-15 | 杭州华三通信技术有限公司 | Data acquisition method and equipment |
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108073661A (en) * | 2016-11-18 | 2018-05-25 | 北京京东尚科信息技术有限公司 | Data retrieval method and device, report generating system and method |
| CN112887113A (en) * | 2019-11-29 | 2021-06-01 | 华为技术有限公司 | Method, device and system for processing data |
| WO2021103791A1 (en) * | 2019-11-29 | 2021-06-03 | 华为技术有限公司 | Data processing method, apparatus, and system |
| CN111181772A (en) * | 2019-12-12 | 2020-05-19 | 新华三大数据技术有限公司 | Network protocol issuing method, device and system |
| CN111181772B (en) * | 2019-12-12 | 2022-03-29 | 新华三大数据技术有限公司 | Network protocol issuing method, device and system |
| CN113676437A (en) * | 2020-05-14 | 2021-11-19 | 中国移动通信集团云南有限公司 | Parameter analysis method, parameter acquisition method, parameter setting method and device |
| CN113676437B (en) * | 2020-05-14 | 2023-08-18 | 中国移动通信集团云南有限公司 | Parameter acquisition method, parameter setting method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2016110078A1 (en) | 2016-07-14 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105827424A (en) | Data acquisition method and data acquisition device | |
| EP3481017A1 (en) | Network slice selection method, apparatus and system | |
| CN110311831B (en) | Container cloud-based system resource monitoring method and related equipment | |
| CN111756674B (en) | Network communication method, system, device and computer readable storage medium | |
| CN104883267A (en) | Network configuration accessing method and device thereof | |
| CN109547524B (en) | User behavior storage method, device, equipment and storage medium based on Internet of things | |
| CN103488696A (en) | Business query method, device and system of CPE (customer premises equipment), ACS (auto-configuration server) and CPE | |
| CN108092789B (en) | Method and device for managing network slice template | |
| CN102891768A (en) | Method and network element for network management | |
| CN103885865A (en) | Method and device for managing sensors | |
| EP3174318A1 (en) | Method for realizing resource attribute notification, and common service entity | |
| CN105827423A (en) | Data acquisition method and data acquisition device | |
| EP3010182A1 (en) | Fault management method and apparatus | |
| CN114710549A (en) | Dynamic management method, system and service node of network card in container platform | |
| CN102148702B (en) | Method for managing network by utilizing network configuration protocol | |
| CN110784358A (en) | Method and device for constructing network call relation topological graph | |
| CN117453272A (en) | Automobile software version management system | |
| CN101873228A (en) | Management system and method for material information of network equipment | |
| CN104125622A (en) | Configuration method of access system, equipment and system | |
| CN114363306A (en) | Data transmission method based on Netconf protocol and related equipment | |
| CN105516319A (en) | Method and device for managing HTTP messages | |
| EP3174322A1 (en) | Method for deleting notification resource, and common service entity | |
| CN106254122B (en) | Simple network management protocol agent implementation method based on EOC equipment | |
| CN108829709A (en) | Distributed database management method, apparatus, storage medium and processor | |
| EP2988476A1 (en) | Method and apparatus for processing operation on endpoint peripheral |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| WD01 | Invention patent application deemed withdrawn after publication |
Application publication date: 20160803 |
|
| WD01 | Invention patent application deemed withdrawn after publication |