WO2015131523A1

WO2015131523A1 - Data query method, system and computer storage medium

Info

Publication number: WO2015131523A1
Application number: PCT/CN2014/088926
Authority: WO
Inventors: 郑聂聪
Original assignee: 中兴通讯股份有限公司
Priority date: 2014-09-25
Filing date: 2014-10-20
Publication date: 2015-09-11
Also published as: CN105512134A

Abstract

Disclosed in an embodiment of the present invention are a data query method, system and computer storage medium, the method comprising: acquiring a query condition configured for a target requested object; transmitting a getBulk command based on an SNMP protocol, and acquiring entity data of the target requested object according to the query condition. DARWING: FIG. 1: S10 Acquiring a query condition configured for a target requested object S20 Transmitting a getBulk command based on an SNMP protocol, and acquiring entity data of the target requested object according to the query condition

Description

Data query method, system and computer storage medium

Technical field

The present invention relates to a data transmission method in the field of communications, and in particular to a data query method, system and computer storage medium based on the Simple Network Management Protocol (SNMP) protocol.

Background technique

With the rapid development of network technology, the era of big data has also come. Under this situation, the transmission technology of network data is also facing more and more severe challenges.

Network management essentially monitors, analyzes, and controls various devices in the network system to ensure reliable and efficient operation of the network system. The network administrator manages the face of the network by managing the interactive communication between the workstations and the agents. In order to ensure the correct exchange of management information between the management workstation and the agent, it is necessary to define the management information and reach an agreement between the management workstation and the agent. Management information is the management object. The protocol between the management workstation and the agent is the network management protocol. Currently, the most widely used network management protocol is based on the Transmission Control Protocol (TCP)/Internet-based interconnection protocol (IP, Internet Protocol) Simple Network Management Protocol SNMP protocol, which is simple, easy to implement and has good scalability. It is the de facto network management protocol standard in the industry.

The getbulk method introduced by the SNMP protocol from the V2 version, the getBulk is configured to acquire all the data in batches, and actually implements the get-next-request operation by iteratively, wherein the get-next- The request operation is configured to look up the proxy for the value of the next instance of the instance that matches the instance ID of the variable binding list, ie, return the instance that is larger than the delivered index, such as an instance with an index value of 2, 3, or 4. If the index delivered by the get-next-request operation is 2, an instance with an index value of 3 is returned. It can be seen that the getBulk method completely replaces multiple get or getNext operations, so that a large amount of data can be obtained through a single request. the goal of. Its biggest advantage is that it reduces the number of interactions. A request can get a batch of data, which improves the query efficiency compared to the original get and getNext operations.

However, in the related art, there are still many deficiencies in the application for obtaining batch data based on the getBulk method, and it is difficult to implement efficient data query.

Summary of the invention

Embodiments of the present invention provide a data query method, system, and computer storage medium to support efficient query of data.

The embodiment of the invention adopts the following technical solutions:

The embodiment of the invention provides a data query method, including:

Get the query conditions configured for the target request object;

The getBulk command is sent according to the SNMP protocol, and the entity data of the target request object is obtained according to the query condition.

Preferably, the configuration item of the query condition includes at least one of the following configuration items:

Aligning the synchronous OID configuration item of the start operation object identifier OID;

The maximum number of requests configuration item that calibrates the maximum number of requests at a time;

Timeout time configuration item that calibrates a request timeout period;

A retries configuration item that calibrates the number of retries for which a request failed;

And, the overrun message splitting number configuration item is configured, and the overrun message splitting number configuration item identifies the number of the message that divides the overrun message, until the overrun message is supported to be returned normally.

Preferably, the configuration item of the query condition further includes:

A boundary OID configuration item is configured, and the boundary OID configuration item is used to calibrate the subsequent data processing before the target boundary OID is identified.

Preferably, the configuration item of the query condition further includes:

An OID collection list configuration item that calibrates a list of valid OID collections.

Preferably, the data query method further includes:

When the data returned according to the getBulk command does not belong to the target OID set list, the OID self-growth lookup logic is executed according to at least one preset self-growth OID processing mechanism until a valid OID is found.

An embodiment of the present invention provides a data query system, including:

The management terminal is configured to acquire a query condition configured for the target request object, and send a getBulk command to the agent based on the SNMP protocol;

The agent is configured to acquire entity data of the target request object according to the query condition.

Timeout time configuration item that calibrates a request timeout period;

And, calibrating the number of times the message of the overrun message is divided until the overrun message split number configuration item that the message can normally return.

Preferably, the configuration item of the query condition further includes:

A boundary OID is configured to calibrate the boundary OID configuration item that terminates subsequent data processing when the boundary OID is identified.

Preferably, the configuration item of the query condition further includes:

Preferably, the agent is further configured to perform OID self-growth lookup logic according to at least one preset self-growth OID processing mechanism until a valid OID is found, when it is recognized that the data returned according to the getBulk command does not belong to the required OID set list.

The embodiment of the invention further provides a computer storage medium, wherein the computer storage medium stores computer executable instructions, and the computer executable instructions are configured to execute the data query method described above.

The technical solution provided by the embodiment of the invention provides a flexible, effective and fast data query method. Compared with related technologies, it can reduce the number of requests, can filter out unnecessary data processing, can realize as much request data as possible, and support the number of automated probe change requests, thereby effectively improving the query efficiency of batch data.

DRAWINGS

1 is a schematic flowchart 1 of a data query method based on an SNMP protocol according to an embodiment of the present invention;

2 is a schematic flowchart 2 of a data query method based on an SNMP protocol according to an embodiment of the present invention;

3 is a schematic flowchart 3 of a data query method based on an SNMP protocol according to an embodiment of the present invention;

FIG. 4 is a schematic structural diagram of a data query system based on an SNMP protocol according to an embodiment of the present invention.

detailed description

The technical solutions of the present invention will be further described in detail below with reference to the accompanying drawings and specific embodiments to enable those skilled in the art to understand the invention. .

In the process of implementing the present invention, the inventors have found that the application of the batch data based on the getBulk method in the related art is insufficient, which makes it difficult to implement efficient data query, which is manifested in the following aspects:

1, because SNMP is an application layer protocol and is part of the TCP/IP protocol family, it operates through UDP (User Datagram Protocol), in other words, it is limited by the length of the UDP packet, based on the getBulk A data request made by the method may not be able to meet the needs of the user.

2, for big data requests, you may need to perform multiple getBulk operations, in the completion of the In the process of data acquisition, it is necessary to repeatedly start from the last instance OID (Object identifier) of the last request, for example: OID: 1.1.3.6.1.4.1.3902.4101.1.3.1.25.1020, where 1020 is The instance ID, requesting this OID, will start with 1021 instance data, and the process is more complicated.

3. If a data request is made to the table data based on the getBulk method, there may be some unnecessary OID data in the returned data. This is because the getBulk operation has the characteristic of returning the result data in sequence. When all the instances of an OID are returned, the instance data of the next OID is returned until the end. It can be seen that the related technology does not support the query design based on the getBulk method. OID collection data function.

4. The data request based on the getBulk method in the related art is prone to request timeout. For example, the possible reasons for the timeout include: interface timeout, request waiting timeout, network delay caused by network instability, and reduced user experience.

As shown in FIG. 1 , the data query method based on the SNMP protocol provided by the embodiment of the present invention is implemented to implement efficient data query, and includes the following specific steps:

S101. Acquire a query condition configured for the target request object.

S102. Send a getBulk command according to the SNMP protocol, and acquire entity data of the target request object according to the query condition.

It should be noted that, in this embodiment, the process of querying data according to the getBulk command (operation primitive) of the SNMP standard is well known to those skilled in the art, and will not be described in detail herein.

In this embodiment, the configuration item of the query condition includes at least one of the following configuration items:

1. The synchronous OID configuration item of the start operation object identifier OID is calibrated. For example, the configuration of the synchronous OID configuration item in the interface or the configuration file can support the dynamic designation of querying different OIDs, which is flexible and changeable;

2. The maximum number of requests for the maximum number of requests can be calibrated at a time. For example, configuring the maximum number of requests in the interface or configuration file can dynamically specify the maximum request parameters. It is enough to adjust according to the length of the request table instance data, so that the maximum amount of data is obtained once;

3. Set the timeout time configuration item of the request timeout time. For example, configure the timeout time configuration item in the interface or configuration file to support the dynamic timeout time of a request. It can be flexibly set according to the actual network status.

4. The retries configuration item that calibrates the number of retries for which the request fails, for example, configuring the retries configuration item in the interface or the configuration file, and can support the number of attempts to re-request after dynamically requesting the request timeout;

5. And, calibrate the number of messages that are overrun, until the message that supports the overrun can return normally.

For example, configuring the overrun message splitting configuration item in the interface or configuration file may cause the requested OID content instance data to be dynamically changed, which results in uncertainty of the message length, and this configuration may be a long request message. Splitting according to the specified requirements, in the case of increasing the number of requests, the integrity of the data is guaranteed.

In a preferred embodiment, the configuration item of the query condition further includes:

6. Configure a boundary OID to calibrate the boundary OID configuration item that ends the subsequent data processing when the boundary OID is identified.

For example, if you configure a boundary OID configuration item in the interface or configuration file, you can judge according to the boundary OID, discard the data that is not needed later, and return it in time. For example, a request table OID group has a total of 35 attributes, and the OID data collected by the demand only exists in the first 24 OIDs, and the last valid OID is the end OID: .1.3.6.1.4.1.3902.4101.1.3.1.24, boundary The OID is: .1.3.6.1.4.1.3902.4101.1.3.1.25. The query is ended when the 25th attribute is currently taken.

In a further preferred embodiment, the configuration item of the query condition further includes:

7. The OID collection list configuration item of a valid OID collection list is defined. By defining a valid OID collection list, the getBulk operation must return the data in order when requesting the table data, from the first attribute to the nth attribute, and return once. Current instance all instance values, then Returns the next attribute data. In this case, it is confirmed according to the predefined set contents which need to process the OID and which do not have to be processed, thereby reducing redundant data processing.

Preferably, as shown in FIG. 2, based on FIG. 1, the data query method based on the SNMP protocol may further include:

S103. When the data returned according to the getBulk command does not belong to the required OID set list, the OID self-growth search logic is executed according to at least one preset self-growth OID processing mechanism until a valid OID is found.

In the specific implementation, the current set of data has the required OID data, and contains the unnecessary OID data. When it is judged that the first OID instance data is not needed, the subsequent processing flow is skipped, and the self-growth processing mechanism is used until Subsequent processing is performed after the next valid OID (when the boundary OID is not reached), reducing the traversal of unnecessary OID instance data and redundant request overhead.

In addition, the method provided by the embodiment of the present invention provides an over-limit message OID cache mechanism when requesting data according to the getBulk command: the OID is cached while the over-limit message is split. By buffering the OID set, it is determined whether the next batch of data is a split OID, and if so, the number of split requests is continued, otherwise, the original request number is restored. It also provides a request number reset mechanism: the number of proactive automatic reset requests is to get as much data as possible for each time, to send requests as little as possible, and to complete tasks efficiently.

The following is an implementation process of the SNMP-based data query method provided by an embodiment of the present invention. As shown in FIG. 3, the following steps are included:

Step S201: Collect related configuration items from an interface or a configuration file.

In order to cope with different scenarios, the query method is more flexible. In this embodiment, conditions can be formulated according to specific examples to achieve the most efficient and most suitable query. For example, under certain scenarios, the background can pre-set default experience values for configuration items for use.

The configuration items provided in this embodiment are shown in Table 1:

Table 1

Step S202: Prepare an SNMP request object and send a getBulk request.

Step S203: When there is data return, cyclically process each batch of data, and perform an item check as shown in Table 2 on the OID:

Table 2

Step S204: In the case that the request operation is not completed, the last instance OID of the last request data is collected, and then enters the valid OID search logic. When the boundary OID is not reached, the attribute ID mode is accumulated until a valid OID is found.

In the specific implementation, for the following scenarios:

Scenario 1. If the last data requested last time belongs to the required OID, the subsequent processing is continued.

Scenario 2: The last request for the last data does not belong to the required OID, then enter the OID self-growth lookup logic until a valid OID is found. Effectively avoid meaningless request messages.

Step S205: Processing the maximum number of requests, determining whether it is necessary to reset the number of message requests and performing corresponding processing.

Specifically, the following scenarios exist:

Scene 1. This request is a split OID. Continue to use the number of split requests.

Scenario 2, this request is not a split OID. The number of requests to restore the original configuration.

Step S206: Send a getBulk request.

If it is successful, if there is data return, the process goes to step S203, and if it fails, the process goes to step S207.

S207. Determine whether the cause of the failure is a message overrun abnormality. If the message exceeds the limit abnormality, proceed to step S208, and then proceed to step S203; otherwise, stop the process.

S208: Perform a split query on the message according to the required length until all data is returned.

As shown in FIG. 4, the embodiment of the present invention further provides a data query system based on the SNMP protocol, including:

a manager 41 configured to acquire a query condition configured for the target request object, and send a getBulk command to the agent based on the SNMP protocol;

The agent 42 is configured to acquire the entity data of the target request object in the information management library 43 (MIB) according to the query condition.

2. The maximum number of requests for the maximum number of requests can be calibrated at a time. For example, configuring the maximum number of requests in the interface or configuration file can dynamically specify the maximum request parameters. The user can adjust the data length of the request table instance. Requesting the most data at a time;

3. Set the timeout time configuration item of the request timeout time. For example, configure the timeout time configuration item in the interface or configuration file to support the timeout period for dynamically specifying a request. The actual network conditions are flexibly set;

5, and, calibrate the number of the message that divides the message of the overrun message until the number of the message segmentation limit of the message that can be returned normally, for example, configuring the overrun message segmentation configuration item in the interface or the configuration file, so that the request can be made The OID content instance data may be dynamically changed, which leads to the uncertainty of the message length. This configuration can split the long request message according to the specified requirements, and ensure the completeness of the data when the number of requests is increased. .

6. Configure a boundary OID to calibrate the boundary OID configuration item that ends the subsequent data processing when the boundary OID is recognized. For example, the boundary OID configuration item is configured in the interface or configuration file, and can be judged according to the boundary OID, and the discarding is not required. The data is returned in time. For example, a request table OID group has a total of 35 attributes, and the OID data collected by the demand only exists in the first 24 OIDs, and the last valid OID is the end OID: .1.3.6.1.4.1.3902.4101.1.3.1.24, boundary The OID is: .1.3.6.1.4.1.3902.4101.1.3.1.25. The query is ended when the 25th attribute is currently taken.

7. The OID collection list configuration item of a valid OID collection list is defined. By defining a valid OID collection list, the getBulk operation must return the data in order when requesting the table data, from the first attribute to the nth attribute, and return once. All instance values of the current property, and then return to the next property data. In this case, it is confirmed according to the predefined set contents which need to process the OID and which do not have to be processed, thereby reducing redundant data processing.

Preferably, the agent is further configured to perform OID self-growth lookup logic according to at least one preset self-growth OID processing mechanism until a valid OID is found, when it is recognized that the data returned according to the getBulk command does not belong to the required OID set list. In the specific implementation, the current set of data has the required OID data, and contains the unnecessary OID data. When it is judged that the first OID instance data is not needed, the subsequent processing flow is skipped, and the self-growth processing mechanism is used until Subsequent processing is performed after the next valid OID (when the boundary OID is not reached), reducing the traversal of unnecessary OID instance data and redundant request overhead.

In addition, in the embodiment of the present invention, when the agent requests data according to the getBulk command, the agent also provides an overrun message OID cache mechanism: the OID is cached while the overrun message is split. By buffering the OID set, it is determined whether the next batch of data is a split OID, and if so, the number of split requests is continued, otherwise, the original request number is restored. And the agent also provides a request number reset mechanism: the number of probe automatic reset requests is to obtain data as much as possible for each time, to send requests as little as possible, and to complete tasks efficiently.

The embodiment of the invention further describes a computer storage medium, wherein the computer storage medium stores computer executable instructions, and the computer executable instructions are configured to execute the data shown in any one of FIG. 1, FIG. 2 or FIG. Query method.

In the several embodiments provided by the present invention, it should be understood that the disclosed apparatus and method may be implemented in other manners. The device embodiments described above are merely illustrative. For example, the division of the unit is only a logical function division, and the actual implementation may have another The way of dividing, such as: multiple units or components can be combined, or can be integrated into another system, or some features can be ignored, or not executed. In addition, 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.

In addition, 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 integrated into one unit; The unit can be implemented in the form of hardware or in the form of hardware plus software functional units.

A person skilled in the art can understand that all or part of the steps of implementing the above method embodiments may be completed by using hardware related to the program instructions. The foregoing program may be stored in a computer readable storage medium, and the program is executed when executed. The foregoing storage medium includes: a mobile storage device, a random access memory (RAM), a read-only memory (ROM), a magnetic disk, or an optical disk. A medium that can store program code.

Alternatively, the above-described integrated unit 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 standalone product. Based on such understanding, 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, which is stored in a storage medium and includes a plurality of instructions for making A computer device (which may be a personal computer, server, or network device, etc.) performs all or part of the methods described in various embodiments of the present invention. The foregoing storage medium includes: a mobile storage device, a RAM, a ROM, a disk, or a light. A medium such as a disk that can store program code.

The above is only a specific embodiment of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily think of changes or substitutions within the technical scope of the present invention. It should be covered by the scope of the present invention. Therefore, the scope of the invention should be determined by the scope of the appended claims.

Claims

A data query method, including:

Get the query conditions configured for the target request object;

The acquiring data getBulk command is sent according to the SNMP protocol of the Simple Network Management Protocol, and the entity data of the target request object is obtained according to the query condition.
The data query method according to claim 1, wherein the configuration item of the query condition comprises at least one of the following configuration items:

Aligning the synchronous OID configuration item of the start operation object identifier OID;

The maximum number of requests configuration item that calibrates the maximum number of requests at a time;

Timeout time configuration item that calibrates a request timeout period;

A retries configuration item that calibrates the number of retries for which a request failed;

And calibrating the over-limit message splitting number configuration item, where the over-limit message splitting number configuration item identifies the number of the over-limit message segmentation until the over-limit message is supported to be returned normally.
The data query method of claim 2, wherein the configuration item of the query condition further comprises:

A boundary OID configuration item is configured, and the boundary OID configuration item is used to calibrate the subsequent data processing before the identification of the specified boundary OID.
The SNMP-based data query method of claim 2, wherein the configuration item of the query condition further comprises:

An OID collection list configuration item that calibrates a list of valid OID collections.
The data query method based on the SNMP protocol of claim 4, further comprising:

When the data returned according to the getBulk command does not belong to the target OID set list, the OID self-growth lookup logic is executed according to at least one preset self-growth OID processing mechanism until a valid OID is found.
A data query system comprising:

The management terminal is configured to acquire a query condition configured for the target request object, and send a getBulk command to the agent according to the Simple Network Management Protocol (SNMP) protocol;

The agent is configured to acquire entity data of the target request object according to the query condition.
The data query system according to claim 6, wherein the configuration item of the query condition comprises at least one of the following configuration items:

Aligning the synchronous OID configuration item of the start operation object identifier OID;

The maximum number of requests configuration item that calibrates the maximum number of requests at a time;

Timeout time configuration item that calibrates a request timeout period;

A retries configuration item that calibrates the number of retries for which a request failed;

And, the overrun message splitting number configuration item is configured, and the overrun message splitting number configuration item identifies the number of the message that divides the overrun message, until the overrun message is supported to be returned normally.
The data query system of claim 7, wherein the configuration item of the query condition further comprises:

A boundary OID configuration item is configured, and the boundary OID configuration item is used to calibrate the subsequent data processing before the target boundary OID is identified.
The data query system of claim 7, wherein the configuration item of the query condition further comprises:

An OID collection list configuration item that calibrates a list of valid OID collections.
The data query system according to claim 9, wherein the agent is further configured to perform OID self according to at least one preset self-growth OID processing mechanism when it is recognized that the data returned according to the getBulk command does not belong to the target OID set list. Increase the lookup logic until a valid OID is found.
A computer storage medium having computer executable instructions stored therein, the computer executable instructions being configured as the data of any one of claims 1 to 5. Query method.