CN1783801A - Method for searching historical data in network managing system - Google Patents
Method for searching historical data in network managing system Download PDFInfo
- Publication number
- CN1783801A CN1783801A CN 200410096302 CN200410096302A CN1783801A CN 1783801 A CN1783801 A CN 1783801A CN 200410096302 CN200410096302 CN 200410096302 CN 200410096302 A CN200410096302 A CN 200410096302A CN 1783801 A CN1783801 A CN 1783801A
- Authority
- CN
- China
- Prior art keywords
- time
- data
- equipment
- historical data
- inquiring
- 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.)
- Granted
Links
Images
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
This invention discloses a method for inquiring about historic data in a network management system in the light transmission field, which keeps the time for inquiring historic data to those necessary to be inquired and designs reasonable collection time based on the actual network operation scale then balances the time for enquiring the historic data of each device based on the number of the devices, if a user needs to inquire about data in the period, it exams if all data have been taken from the device in the query time, if not, it triggers the query unit for the network management unit to inquire about them, if the device is off from the management or does not get historic data for some time, then query should be done again next time.
Description
Technical field
The present invention relates to the optical transmission communication field, relate in particular to the inquiry of historical data method in the network management system of optical communication field.
Background technology
At present, in the webmaster of dense wavelength division multiplexing system, network service quality is monitored by the method for continuous acquisition historical data.Historical data has comprised daily record data of the operation in history alarm event data, History Performance Data, the equipment or the like, and these data can reflect the running status of network.The user need analyze and locate some problems according to historical data for the ruuning situation of equipment, network management system not only needs to keep but also can not omit to these data, is critical functions of webmaster so gather these historical datas of storage.
Gathering data such as historical performance in the existing network management system all is to have produced historical data, just regularly gathers preservation, takes off pipe if gather moment equipment, will obliterated data; Equipment along with webmaster management progressively increases in addition, and each regularly arrival gathered for all equipment, and communication abnormality is busy constantly to cause some, influences other bookkeeping of webmaster, also causes losing of historical data easily.
Summary of the invention
Technical problem to be solved by this invention is that the equipment that overcomes the prior art existence takes off under the pipe situation because the timing acquiring data cause some moment communication abnormality busy, thereby the shortcoming that further causes historical data to be lost easily is in the hope of proposing a kind of method that can effectively prevent enquiry of historical data in the network management system that historical data loses easily.
The method of enquiry of historical data in the network management system proposed by the invention comprises following content:
For the historical data that needs timing acquiring, time of each enquiry of historical data is kept, and a rational timing acquisition time is set according to real network operation scale;
According to the number of equipment, all tell the time of searching each device history data again;
If during the user need enquiry of historical data, check in time period of user inquiring data whether all slave unit take out, if also there is not the slave unit collection, then trigger inquiry mechanism, webmaster is enquiry of historical data to the equipment again, to guarantee that the user can view latest data;
If certain period needs inquiry once more because equipment takes off pipe or other reasons is not got historical data when then inquire about next time, to guarantee the integrality of data.
Said method further may further comprise the steps:
The first step: data are carried out initialization, and some data are configured storage;
1,, regularly carry out data acquisition, and the collection between each equipment need be gathered according to the interval of calculating according to the time of webmaster timing acquiring and the equipment scale in the network.
2, gather at every turn or inquiry after time must store, as the zero-time of query history performance time next time; To guarantee not get repeating data; When certain secondary data was not got, once more gathered when inquiring about next time in addition, guarantees the integrality of data.
Second step: carry out timing acquiring work;
1, timing arrives and gathers;
2, after timing acquisition time arrives, divide extracting, gathering, calculate a time average and gather an equipment as the acquisition interval of each equipment or every a few minutes for all equipment.
3, the result who gathers preserves, and the time of gathering is noted.
The 3rd step: user inquiring History Performance Data;
1, the user needs enquiry of historical data, whether the historical performance that needs to compare the time period of user inquiring earlier all goes to inquire about in the equipment, if the time of inquiring about in the time ratio internal memory of user inquiring early, so directly from data with existing, obtain to meet the record of user's condition;
If in evening time of inquiring about in the time ratio internal memory of 2 user inquirings, so just need the structure message to go to inquire about in the equipment historical data;
3, after the inquiry data are stored earlier, construct the record that obtains to meet user's condition again.
Adopt the method for the invention, compared with prior art, because there is record the time of successful inquiring at every turn, if certain inquires about failure, can read again when inquiring about, can not compensate inquiry again next time when certain inquiry came up, and guaranteed the integrality of data next time.The data that need timing acquiring for historical performance, because timing acquisition time can customize, alleviated the burden of network, the while, only can inquire new data when inquiring about next time because the time that will inquire about preserves, guaranteed not have duplicate record, improved storage efficiency, do not had duplicate record again simultaneously, also made the flow minimum in the communication, and since in acquisition time be equipartition time one by one equipment inquire about, the flow-rate ratio of communication is balanced; This is not easy to block communication when network size is bigger, make operation flow also more unobstructed; Can also guarantee that simultaneously historical data can not lose.
Description of drawings
Fig. 1 is a collecting method flow chart such as historical performance in the existing system.
Fig. 2 is the collecting method flow charts such as a kind of historical performance as the method for the invention embodiment.
Fig. 3 is a data collecting methods flow chart such as history alarm in the existing system.
Fig. 4 is the collecting method flow charts such as another kind of historical performance as the method for the invention embodiment.
Embodiment
Be described in further detail below in conjunction with the enforcement of accompanying drawing, and describe with collection and two examples of history alarm data acquisition of History Performance Data respectively technical scheme.
Fig. 1 represents data collecting methods such as historical performance in the existing system, and the figure on the left side is present collecting method, the flow process of webmaster when the figure on the right is the user inquiring data.
Fig. 2 represents after the improvement that historical performance etc. in the system needs the method for the data of timing acquiring, and the figure on the left side is present collecting method, the flow process of webmaster when the figure on the right is the user inquiring data.
Fig. 3 represents data collecting methods such as history alarm in the existing system, and the figure on the left side is present collecting method, the flow process of webmaster when the figure on the right is the user inquiring data.
Fig. 4 represents after the improvement data collecting methods such as history alarm in the system, and the figure on the left side is present collecting method, the flow process of webmaster when the figure on the right is the user inquiring data.
As can see from Figure 1, in present system, be example with historical 15 minutes performances, system's each run 15 minutes, just to the order of all devices transmission query history performance, the data that equipment should the period report, and deposit in the database behind the systematic collection.If the user checks historical data, database reports the data combination that satisfies condition.For 24 hours data such as performance of timing also is these class methods.The benefit of this method is just to obtain after having produced data, and from data base querying, flow process is fairly simple during user inquiring.But this method is when network size is bigger, owing to issue querying command to all devices simultaneously, all Query Results report, cause communication to be blocked, loss of data, if when other problem is exactly regularly to arrive, equipment is not in the management, then, cause losing of this moment historical data owing to follow-uply do not have a means guarantee.
Be described in detail in improving one's methods of query history performance data among Fig. 2 below.In the method, the timing acquiring scheme continues to continue to use, but the parameter that the conduct of the time interval of inquiry can be disposed, this parameter can be adjusted, the networking within 100 equipment at present, and recommending blanking time is 2 hours.During the webmaster initialization, from database, read the time of query history performance last time, the wait timing arrives, with between this moment as zero-time, current time in system is the concluding time to carry out history collection to equipment, if the concluding time just in time is the moment that equipment produces historical data, then to finely tune (being to adjust one minute forward at present) forward.Below being divided into several situations again treats:
If when 1 timing arrived, equipment control was not gone up, and does not then issue acquisition tasks, when regularly arrive next time by the time, issue Query Result together.
If 2 collection result of receiving are mistake, this collection failure is described, do not revise the acquisition time of historical performance this moment, wait for when inquire about next time and still inquiring about according to this time;
If 3 have received and have successfully gathered the message that reports, also need the time of query history performance is made amendment, adjust to the concluding time of collection.
4, gather the message of receiving that reports and to deposit database in,,, do not need to carry out repeatability and judge, improved the efficient of webmaster so the result who gathers directly deposits database in batches because the time of gathering has guaranteed uniqueness.
Carry out the inquiry of historical performance class data the user, this also needs to distinguish various situations and handles:
1, the time of comparison query,, then directly from database, extracts qualified result if should the performance in the time all cross to equipment query;
If the time ratio enquiry of historical data last time time of 2 user inquirings is short, then need to send querying command and inquire about to equipment, if equipment control this moment is not gone up, then directly take out the qualified record of part in the database;
3, make up the message that issues, zero-time is the time of inquiry last time, and the concluding time is the current time in system, if the time is the time that equipment regularly produces History Performance Data, for fear of losing, the time is adjusted one minute forward;
If 4 issue equipment query, but equipment returns the result of failure, then this moment will database in qualified record send to the user;
If 5 issue the equipment query success, then need to revise on the one hand the time of query history performance data this moment, need on the other hand these batch data warehouse-ins are found out qualified record then from the storehouse.
In sum and since adopted some flexibly mechanism carry out the collection of historical data, even equipment takes off and has managed in certain query time, but the next one constantly or the moment of back can inquire about up, guaranteed the integrality of data query; Because query time can customize at interval, the query time of each equipment is separated, and can utilize the communication resources of network fully again; If when the user inquiring data, do not gather in the query time section, then can trigger the mechanism of downward inquiry again, guaranteed the integrality of user inquiring data; The time of each query facility has all preserved in addition, and then the record of each inquiry has all guaranteed can not repeat, and this moment, data loading was the problem that can not have repetition, put in storage in batches, had improved data storage efficiency.
Among Fig. 3, in present network management system, get the data that equipment such as history alarm initiatively reports, network management system has been received just warehouse-in of historical data.Just obtaining qualified record during user inquiring from database returns.The consequence of this scheme is, if webmaster and equipment disconnect, then the data user of off period can not obtain, and this is can not be satisfactory.
In the scheme of improved query history alarm class data, its concrete using method is described below among Fig. 4.In network management system, if such data owner dependence equipment initiatively reports, thus the active reported result of receiving equipment in the system, and the result that will receive deposits in the database.The time of storing queries historical data in system is as the zero-time of each inquiry.When the user inquired about, at first relatively user's query time if webmaster carried out inquiry to this equipment in this query time, then directly found out qualified record and reports from database.If in the query time, do not send querying command to equipment, then check the management condition of present equipment:
If 1 present equipment control is not gone up, then directly from database, inquire about qualified record and report;
If 2 present equipment can be managed, with last time query time be zero-time, current system time is the concluding time, issues querying command to equipment; If equipment returns failure, then the qualified record of inquiry reports from database;
If after 3 inquiries, equipment returns success, then at first with the concluding time of time modification for inquiring about of inquiring about, deposit the record of inquiry in database, need do repeated verification this moment, avoids the repeating data warehouse-in, inquires qualified record then and send to the user from database.
In sum, owing to adopted inquiry mechanism, unusual at webmaster and device talk, the data of perhaps losing in other cases can both report and be saved in database in inquiry, and such flow process has guaranteed the integrality of data.
The collection historical data method that adopts the present invention to propose, at first because all there is record the time of inquiry at every turn, the failure of certain inquiry, still can inquire about next time, up to successful inquiring, guaranteed the integrality of data like this, historical data was lost problem when the equipment that solved in the prior art took off pipe; In addition because can be according to the network size customization acquisition interval time of management equipment, separate image data for each equipment, simultaneously also staggering of each equipment collection inquired about, the communication of avoiding all historical data synchronization to arrive causing is blocked and is professional busy, utilize the communication resources of system fully, can not block other operations of webmaster.Simultaneously owing to can trigger inquiry mechanism during user inquiring, so segment data also can not lack some during from user's angle data query the time.So the present invention is a kind of method of the enquiry of historical data that can guarantee data integrity more again.
Claims (4)
1, the method for enquiry of historical data in a kind of network management system is characterized in that, comprises following content:
For the historical data that needs timing acquiring, time of each enquiry of historical data is kept, and a rational timing acquisition time is set according to real network operation scale;
According to the number of equipment, all tell the time of searching each device history data again;
If during the user need enquiry of historical data, check in time period of user inquiring data whether all slave unit take out, if also there is not the slave unit collection, then trigger inquiry mechanism, webmaster is enquiry of historical data to the equipment again, guarantees that the user can view latest data;
If certain period needs inquiry once more because equipment takes off pipe or other reasons is not got historical data when then inquire about next time, guarantee the integrality of data.
2, the method for enquiry of historical data in the network management system according to claim 1 is characterized in that, further may further comprise the steps:
The first step: data are carried out initialization, and some data are configured storage;
Second step: carry out timing acquiring work;
The 3rd step: user inquiring History Performance Data:
(1) family needs enquiry of historical data, whether the historical performance that needs to compare the time period of user inquiring earlier all goes to inquire about in the equipment, if the time of inquiring about in the time ratio internal memory of user inquiring early, so directly from data with existing, obtain to meet the record of user's condition;
(2) if so just need the structure message to go to inquire about in the equipment historical data evening time of inquiring about in the time ratio internal memory of user inquiring;
(3) after the inquiry data are stored earlier, construct the record that obtains to meet user's condition again.
3, the method for enquiry of historical data in the network management system according to claim 2 is characterized in that the first step further may further comprise the steps:
(1), regularly carry out data acquisition, and the collection between each equipment is gathered according to the interval of calculating according to the time of webmaster timing acquiring and the equipment scale in the network;
(2) gather at every turn or inquiry after time must store, as the zero-time of query history performance time next time; When certain secondary data was not got, once more gathered when inquiring about next time, guarantees the integrality of data.
4, the method for enquiry of historical data in the network management system according to claim 2 is characterized in that, second step further may further comprise the steps:
(1) timing arrives and gathers;
(2) after timing acquisition time arrives, divide extracting, gathering, calculate a time average and gather an equipment as the acquisition interval of each equipment or every a few minutes for all equipment;
(3) result who gathers preserves, and time of arriving of record acquisition.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB200410096302XA CN100388679C (en) | 2004-11-30 | 2004-11-30 | Method for searching historical data in network managing system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB200410096302XA CN100388679C (en) | 2004-11-30 | 2004-11-30 | Method for searching historical data in network managing system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1783801A true CN1783801A (en) | 2006-06-07 |
| CN100388679C CN100388679C (en) | 2008-05-14 |
Family
ID=36773590
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNB200410096302XA Expired - Fee Related CN100388679C (en) | 2004-11-30 | 2004-11-30 | Method for searching historical data in network managing system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN100388679C (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101895426A (en) * | 2010-07-20 | 2010-11-24 | 中兴通讯股份有限公司 | Data acquisition method and system in network resource evaluation |
| CN101841423B (en) * | 2009-03-19 | 2012-06-27 | 大唐移动通信设备有限公司 | Network management system history performance data query method, device and network management system |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP1160682A1 (en) * | 2000-06-02 | 2001-12-05 | Thomas Dr. Seidl | Relation interval tree |
| US7334004B2 (en) * | 2001-06-01 | 2008-02-19 | Oracle International Corporation | Consistent read in a distributed database environment |
-
2004
- 2004-11-30 CN CNB200410096302XA patent/CN100388679C/en not_active Expired - Fee Related
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101841423B (en) * | 2009-03-19 | 2012-06-27 | 大唐移动通信设备有限公司 | Network management system history performance data query method, device and network management system |
| CN101895426A (en) * | 2010-07-20 | 2010-11-24 | 中兴通讯股份有限公司 | Data acquisition method and system in network resource evaluation |
Also Published As
| Publication number | Publication date |
|---|---|
| CN100388679C (en) | 2008-05-14 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN1230737C (en) | Device data polling dispatching method | |
| CN1681248A (en) | Method and system for transmitting data for data synchronization between server and client | |
| CN101039211A (en) | Method for inquiring customization of performance data and system thereof | |
| CN1755676A (en) | System and method for batched indexing of network documents | |
| CN1901568A (en) | Method for realizing historical property collection in net managing system | |
| CN1201949A (en) | Apparatus and method for maintaining integrated data consistency across multiple databases | |
| CN101937474A (en) | Mass data query method and device | |
| CN1407762A (en) | Gated filter | |
| CN101056280A (en) | An upgrade management method and system for instant message client | |
| CN1921407A (en) | Alarm managing method for SNMP protocol network managing system | |
| CN1809108A (en) | Filter based call ticket memory repetition elimination method | |
| CN101997701A (en) | Data processing method and a device thereof | |
| CN1933451A (en) | Interplate communicating method and interface plate | |
| CN1783801A (en) | Method for searching historical data in network managing system | |
| CN1893686A (en) | Method for retesting net-element in shortmessage system | |
| CN1870524A (en) | Network element warning data obtaining method | |
| CN1275429C (en) | A method for performance measurement data acquisition of embedded distributed system | |
| CN1521990A (en) | Fully dynamic distributed network service management system and service method thereof | |
| CN113055490B (en) | Data storage method and device | |
| CN1314228C (en) | Data transferring system and method | |
| CN1385985A (en) | Method for realizing business phonetic dynamic loading in intelligent network and system network establishment | |
| CN1909477A (en) | Method and system for distal equipment maintenance | |
| CN1764121A (en) | The communication means and the communication terminal that are used for star network | |
| CN1780250A (en) | Automatic discovery of network topology | |
| CN1545302A (en) | A method and system for distributed management of relay resources |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20080514 Termination date: 20141130 |
|
| EXPY | Termination of patent right or utility model |