CN1937536A - Network management topological data synchronous refreshing method and system - Google Patents
Network management topological data synchronous refreshing method and system Download PDFInfo
- Publication number
- CN1937536A CN1937536A CNA2006101376436A CN200610137643A CN1937536A CN 1937536 A CN1937536 A CN 1937536A CN A2006101376436 A CNA2006101376436 A CN A2006101376436A CN 200610137643 A CN200610137643 A CN 200610137643A CN 1937536 A CN1937536 A CN 1937536A
- Authority
- CN
- China
- Prior art keywords
- data
- client
- server end
- status indicator
- module
- 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
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/12—Discovery or management of network topologies
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Computer And Data Communications (AREA)
Abstract
The invention discloses a network manager topological data synchronous refreshing method, comprising: client end transmits client-end data flag and corresponding status flag to server end; the server end compares the client-end status flag with server-end status flag and returns server-end data corresponding to data flag different from the status flag; the client end updates local data according to the received server-end data. And it also discloses a corresponding synchronous refreshing system. And it only transmits the changed data when synchronously refreshing data, largely reducing data interaction caused by synchronous data refreshing and reducing network consumption and whole time consumption. Thus, it also reduces the possibility of service loss in the data synchronizing course.
Description
Technical field
The present invention relates to the method in network management technology field, particularly network management data synchronous refreshing and the system of network management data synchronous refreshing.
Background technology
Network management system is called for short network management system, be the software systems that various telecommunication apparatus are managed, network management system has realized the centralized management to various telecommunication apparatus, and topography module offers user's an important operation man-machine interface as network management system, allow the user topology objects such as equipment, connection, subgraph to be operated, and finish mutual with background server by this interface.For in the quick response telecom operators maintenance process to the response speed of work such as telecommunication apparatus, network operation, topography module adopts the means of client-cache partial data on data distribute, cause delay on the network interaction to reduce the data change that causes because of operation.
Along with the development and the expansion of telecom operators' business, the number of devices that network management system is managed is also increasing, and the device data amount in the Dui Ying network management system is also increasing thereupon with it; And, all may cause the attribute change of telecommunication apparatus data for Business Processing such as the configuration of telecommunication apparatus, maintenance, monitoring, service dispense, and the user of client itself operates, and also can cause the attribute of partial data to change.Attribute described here comprises the title, coordinate position, icon style, text description of equipment and such as normal, off-line, the various states of fault or the like.
The synchronous refresh function that topography module provides as main topological data synchronization means, is a kind of function easily and efficiently that the user solves topology server end and client data difference.And under the large-scale data environment, how to realize the immediate problem that data sync has fast and accurately just become the network management system topography module to be faced.
The general employing of prior art system as shown in Figure 1 realizes the synchronous refresh of network management topological data.Referring to Fig. 1, client comprises client database, data management module, control module, view control module etc., and wherein control module also comprises message sink module and message transmission module; Server end comprises server end database, data management module, control module etc., and control module also comprises message sink module and message transmission module.Between the client and server end, can also comprise the message distribution module that is used for dispatch messages.
When prior art is carried out data synchronous refreshing at needs, at first at the local data of client by data management module full scale clearance client, and by the demonstration of view control module removing view, again read total data from server end then, re-construct the local data of client again in client, repaint whole topological view by the view control module simultaneously.
Prior art can guarantee that by mutual based on massage pattern of client and server end server end when producing data change, can upgrade client data in client.
But in the ordinary course of things, client is when carrying out the data sync refresh process, the discrepant just fraction data of itself and server end, carry out the synchronous of total data for a small amount of inconsistent data, obviously cost is relatively too high, and can bring the performance deficiency of following substantivity:
1) owing to need transmit mass data by network, the network interaction amount of overhead that is produced is bigger;
2) after client is received data, need carry out the parsing again and the structure of mass data, produce more time overhead;
3) the view control module will repaint whole topological views, needs the cost plenty of time, causes efficient to reduce;
4) even more seriously be, because it is bigger to obtain the time overhead that is caused with resolution data, client can't be carried out Business Processing in this process, can cause that serious data loses and problem such as function omission.
Summary of the invention
In view of this, the present invention proposes a kind of method of network management data synchronous refreshing, data quantity transmitted during in order to the reduction network management data synchronous refreshing.Another object of the present invention is to propose a kind of system of network management data synchronous refreshing.
According to above-mentioned purpose, the invention provides a kind of method of network management data synchronous refreshing, this method comprises:
Client sends to server end with the sign and the corresponding status indicator of client data;
The server end comparing data identifies clients corresponding status indicator and server end status indicator, and returns the pairing server end data of the different Data Identification of above-mentioned status indicator to client;
Client is upgraded local data according to the server end data of being received.
The present invention also provides a kind of system of network management data synchronous refreshing, and this system comprises the client and server end;
Wherein, client comprises:
Client database is used to store client data;
The client data administration module is used for the data of client database are read, increase, delete or revise;
The client control module is used for the sign of client data and corresponding status indicator are sent to server end, and the data of returning according to server end, upgrades data in the client database by the client data administration module;
Server end comprises:
The server end database is used for the storage server end data;
The server end data management module is used for the data of server end database are read, increase, delete or revise;
The server end control module is used for more described Data Identification clients corresponding status indicator and server end status indicator, and returns the pairing server end data of the different Data Identification of above-mentioned status indicator to client.
From such scheme as can be seen, because the present invention is provided with the status indicator of the current attribute status of expression for client data and server end data, carrying out data sync when refreshing, client only need send to server end with the sign and the corresponding status indicator of client data, relatively whether each Data Identification clients corresponding status indicator is identical with the server end status indicator for server end then, and return the pairing server end data of the different Data Identification of above-mentioned status indicator to client, client is according to the data of being received, upgrade local data, like this, when refreshing, data sync only transmitted the data that change, having significantly reduced data sync, to refresh the data volume that causes mutual, and therefore also having reduced data sync refreshes network consumption and the whole time loss that causes.Owing to reduced the caused whole time loss of data sync, thereby reduced the possibility that causes loss of traffic and function to omit in the data synchronization process.
Description of drawings
Fig. 1 is a system configuration schematic diagram of the prior art;
Fig. 2 is the data structure schematic diagram that has increased status indicator;
Fig. 3 is the schematic diagram that calculates and preserve check code when adopting the correspondence table form;
Fig. 4 is the schematic diagram that calculates and preserve check code when adopting the form that increases attribute in data;
The schematic flow sheet that Fig. 5 upgrades for check code;
Fig. 6 is the system configuration schematic diagram in the embodiment of the invention;
When being the initialization of client and server end, Fig. 7 produces the schematic flow sheet of check code;
Fig. 8 is the schematic flow sheet of first embodiment of the invention;
Fig. 9 is the schematic flow sheet of second embodiment of the invention.
Embodiment
For making the purpose, technical solutions and advantages of the present invention clearer, the present invention is described in more detail by the following examples.
Among the present invention, carry out data sync when refreshing at the client and server end, by relatively, data that there are differences synchronously only, and asynchronous identical data, thus reduce the data volume of synchronous refresh.Further, also just repaint the topological view part corresponding in client, thereby reduced the topological view refresh time, improved the efficient of refresh operation with variance data.Client described here is meant Topology Foreground, and server end is meant topological backstage.
The embodiment of the invention is added status indicator by the data to the client and server end, in order to represent the change situation of attribute in each data.
Status indicator can be used as the part of data.As shown in Figure 2 be to have increased the data structure schematic diagram behind the status indicator.Data comprised originally the sign (ID) of data and attribute 1, attribute 2 ... attribute n.With reference to Fig. 2, the status indicator that increases in the data is equivalent to a variable attribute of data.
In addition, status indicator also can adopt the mode of correspondence table to unite preservation with corresponding Data Identification.In other words, in database, preserve the corresponding relation of data ID and status indicator.As shown in table 1 is exactly the mapping table of data ID and its status indicator.No matter be the part as data, still in mapping table, the value of status indicator can use integer (int) categorical data to preserve, and can reduce the time complexity of internal memory, calculating and comparison like this.
| ID1 | ID2 | ID3 | ... | |
| Status indicator | ||||
| 1 | Status indicator 2 | Status indicator 3 | ... | Status indicator n |
Table 1
The status indicator of the same data ID correspondence between the client and server end represents that then the data of this ID correspondence are variant not simultaneously, need carry out Synchronous Processing; When if the status indicator of the same data ID correspondence between the client and server end is identical, represent that then data not there are differences, so just do not need to carry out Synchronous Processing.
The status indicator of data can be the timestamp of these data, also can be the check code (Checksum) that comes out by certain algorithm computation.If stab service time as status indicator, then can be directly with the state of representing these data update time as timestamp of these data.If adopt Checksum as status indicator, then can calculate the ID in the data and every combinations of attributes, for example adopt cyclic redundancy code (CRC) algorithm, message digest algorithm (MD5) scheduling algorithm to calculate the Checksum of data, then its status indicator as these data is preserved.In the following description, be that example illustrates enforcement of the present invention with Checksum.
As shown in Figure 3, adopt the Checksum algorithm computation to go out Checksum, and preserve the corresponding relation of data ID and Checksum data.
As shown in Figure 4, adopt the Checksum algorithm computation to go out Checksum to data, and the Checksum that is calculated is preserved as the part of data.
In addition, because the attribute in the data can be divided into variable attribute and immutable attribute.Wherein, immutable attribute is the attribute that can not change, and variable attribute is the attribute that may change at refresh process.Refresh for data sync, there is no need to refresh immutable attribute, in order to reduce complexity and the amount of calculation of calculating Checksum, the further proposition of the embodiment of the invention can only adopt the Checksum algorithm computation to go out the Checksum of these data to the variable attribute in the data.
Special needs to be pointed out is, need adopt consistent Checksum algorithm at the client and server end.Selection to the Checksum algorithm, what mainly consider is to guarantee that the Checksum that the client and server end is calculated is consistent, in addition for consideration to big data quantity applied environment and complicated business, also require the Checksum algorithm to have the high computational efficiency of the rate of exchange, can in the short as far as possible time, finish operation times as much as possible, to guarantee that the calculating of Checksum can not cause too much efficient expense when frequent change takes place data.In embodiments of the present invention, preferably adopt the CRC32 algorithm, 1,000,000 grades of computings of this algorithm can be satisfied service needed fully less than 2 seconds.To the calculating of check code with relatively go up, owing to be by limited variable attribute is calculated, the corresponding relation by Data Identification (ID) and check code relatively the time compares, so also guaranteed the reliability of CRC32 algorithm from another angle.
In the embodiment of the invention, when change takes place in " variable attribute " of topological data, Checksum that can update calculation topological data correspondence, when keeping the change of topological data attribute, the Checksum of client and server end data still is consistent.
To revise this attribute of data name is example, and the handling process of client and server end renewal Checksum comprises the steps: as shown in Figure 5
Step 101, NMS user is in the make amendment operation of data name of client.
Step 102, the user end to server end sends the request of revising data name, comprising amended data name.
Step 103, server end are received the local data name of this request back change, and recomputate Checksum according to the data after the change.
Step 104, server end are sent the broadcasting of revising data name, generally comprise data ID and amended data name.
Step 105, each client are received after the above-mentioned broadcasting, upgrade local data name, and recomputate Checksum according to the data after the change.
Synchronous refresh system in the embodiment of the invention as shown in Figure 6.
With reference to Fig. 6, this system comprises the client and server end.Can further include the message distribution module that is used for dispatch messages between each client and server end in this system, certainly, most of networks can both be realized the distribution of message, therefore also can be particularly including a message distribution module.The said message of the embodiment of the invention can comprise sign, status indicator of data, the data of client and server end or the like.
Client comprises client database, data management module, control module, status indicator generation module.This client can further include view control module or the like.
Wherein, client database is used to store the data of client, can also further store the status indicator corresponding with data if desired.Data management module is used for the data of client database are managed, and for example reads, increases, operation such as modification, deletion.
The control module of client is used for the ID of client data and corresponding status indicator are sent to server end, and receives the data from server end, and by the data in the client data administration module renewal client database.The client control module can comprise message sink module and message transmission module, in order to finish the function of above-mentioned reception message and transmission message.The client control module can also comprise collection module, is used for collecting as required the data of client database, perhaps collects data and corresponding status indicator in the client database.
The status indicator generation module of client is used for producing the status indicator corresponding with these data according to data, for example adopts the Checksum algorithm computation to go out corresponding Checksum, is stored in client database then or offers message transmission module.
The view control module of client is drawn the topological view according to data when the initialization except the same with prior art, in the Refresh Data process, according to the more new data of receiving from server end, repaints the topological view part corresponding with these data.
Continuation is with reference to Fig. 6, and server end comprises server end database, data management module, server end control module, status indicator generation module.
Wherein, the server end database is used for the data of storage server end, can also further store the status indicator corresponding with data if desired.Data management module is used for the data of server end database are managed, and for example reads, increases, operation such as deletion, modification.
The control module of server end, be used for after receiving data ID that client is sent and corresponding status indicator, the client state of more same ID identifies and the server end status indicator, and returns the pairing server end data of the different ID of above-mentioned status indicator to client.This control module can comprise contrast module and collection module and message sink module and message transmission module, and wherein message sink module and message transmission module are in order to finish above-mentioned reception message and to send the function of message.
The control module of server end can comprise the contrast module, the status indicator of the server end data that client data ID that this contrast module provides according to the message sink module and corresponding status indicator and local collection module or status indicator generation module provide, relatively each data ID clients corresponding status indicator and server end status indicator draw the different Data Identification of status indicator and offer control module.The server end control module is then obtained data according to the different Data Identification of these status indicators from the server end database, and sends to client.
The control module of server end can comprise collection module, is used for collecting as required the data of server end database, perhaps collects data and corresponding status indicator in the server end database.
The status indicator generation module of server end is similar to the status indicator generation module of client, is used for producing the status indicator corresponding with these data according to data, is stored in the server end database then or offers the contrast module.
Introduce the flow process of data synchronous refreshing of the present invention below.
In first embodiment, the client and server end produces the status indicator of data in advance, still is the example explanation here with Checksum.
In order to guarantee the normal operation of CheckSum mechanism, the client and server end need be when starting the Checksum of each data of initialization, and, preserve the corresponding relation of data and Checksum according to the ID of data.As shown in Figure 7, the process of client and server end Checksum of each data of initialization when starting is as follows:
Step 200, after server end started, server end status indicator generation module adopted the Checksum algorithm that each data is calculated corresponding Checksum, preserved the Checksum corresponding with each data then in the server end database.
Step 201, NMS user are logined network management system behind client terminal start-up.
It should be noted that the not difference of priority of here step 200 and step 201, just just be divided into two steps for convenience.
Step 202, the request that topological data is obtained in the initiation of user end to server end.
Step 203, server end returns topological data to client.
Step 204, client state sign generation module adopts the Checksum algorithm that each data is calculated, and obtains corresponding Checksum, preserves described data and corresponding Checksum then in client database.
On above-mentioned initialized basis, the flow process of the data synchronous refreshing of first embodiment of the invention comprises the steps: as shown in Figure 8
Step 301, client receive NMS user and carry out the operation that refreshes.
Step 302, the collection module in the client control module is collected local data and the Checksum corresponding with it by data management module from client database.
Step 303, the client message sending module sends to server end with the ID and the corresponding Checksum of collected local data.
The message that client mails to server end can adopt following structure:
ObjectPairId
{
strObjectID STRING，
iChecksum INTEGER
}
Wherein, " strObjectID " is the ID of data, and its type is a character string; " iChecksum " is corresponding Checksum, and type is an integer.The advantage of this structure is that the data volume that comprises is little, needn't comprise all data attributes, thereby lower to the consumption that network interaction caused.
Step 304, after server end message sink module is received the ID and corresponding Checksum of the client data that forwards from the message distribution module, offer the contrast module, by contrast module the topological data ID and the corresponding Checksum that send according to client, compare with the Checksum of the topological data of the identical ID of server end.For each data ID, if the Checksum of the Checksum of client and server end is identical, then explanation does not need to upgrade; If two Checksum differences, then explanation needs to upgrade.
Step 305, server end control module utilize the message transmission module server end data that Checksum is different to send to client.Described data are distributed to client via the message distribution module.
Step 306, client message receiver module are upgraded the data in the client database by data management module after receiving the data that server end returns, and the renewal here comprises operations such as modification, increase or deletion.
Further, the client control module is called the status indicator generation module received variance data is calculated, and calculates Checksum, and passes through the data management module updated stored in client database.
Step 307, the client control module can further be called the view control module and repaint the topological view part corresponding with variance data according to received server end data, thereby refreshes the topological view of client.
Different with first embodiment, second embodiment does not calculate and preserves Checksum when startup is initialized, but calculates Checksum in the process of carrying out synchronous refresh.
Though second embodiment has increased the computation complexity when data sync refreshes, can keep the integrality of topological data structure, and Checksum calculating is more concentrated, less to the degree of influence of system configuration.
In addition, after calculating Checksum, can preserve also and can not preserve described Checksum, be example not preserve Checksum in the flow process below.
The flow process of second embodiment as shown in Figure 9.With reference to Fig. 9, the flow process of second embodiment of the invention may further comprise the steps:
Step 401, client receive NMS user and carry out the operation that refreshes.
Step 402, the collection module in the client control module is collected local data by data management module from client database.
Step 403, client control module are called the status indicator generation module collected local data are produced corresponding Checksum by calculating.
Step 404, the client message sending module sends to server end with the Checksum of the ID of collected local data and the correspondence calculated.
Step 405, after server end message sink module is received the ID and corresponding Checksum of the client data that forwards from the message distribution module, call the status indicator generation module local data is produced corresponding Checksum by calculating, and offer the contrast module.
Step 406, the contrast module compares with the Checksum of the topological data of the identical ID of server end according to topological data ID and the corresponding Checksum that client sends over.
For each data ID, if two Checksum are identical, then explanation does not need to upgrade; If two Checksum differences, then explanation needs to upgrade.
Step 407, server end control module utilize the message transmission module data that Checksum is different to send to client.Described data are distributed to client via the message distribution module.
Step 408, client message receiver module are upgraded the data in the client database by data management module after receiving the data that server end returns, and the renewal here comprises operations such as modification, increase or deletion.
Step 409, the client control module can further be called the view control module and repaint the topological view part corresponding with variance data according to received server end data, thereby refreshes the topological view of client.
Should be appreciated that the software of realizing the inventive method can be stored in the computer read/write memory medium, this software comprises the steps: when carrying out
Client sends to server end with the sign and the corresponding status indicator of client data;
The server end comparing data identifies clients corresponding status indicator and server end status indicator, and returns the pairing server end data of the different Data Identification of above-mentioned status indicator to client;
Client is upgraded local data according to the server end data of being received;
Described storage medium, as: ROM/RAM, magnetic disc, CD etc.
The above only is preferred embodiment of the present invention, and is in order to restriction the present invention, within the spirit and principles in the present invention not all, any modification of being done, is equal to replacement, improvement etc., all should be included within protection scope of the present invention.
Claims (14)
1, a kind of method of network management data synchronous refreshing is characterized in that, this method comprises:
Client sends to server end with the sign and the corresponding status indicator of client data;
The server end comparing data identifies clients corresponding status indicator and server end status indicator, and returns the pairing server end data of the different Data Identification of above-mentioned status indicator to client;
Client is upgraded local data according to the server end data of being received.
2, method according to claim 1 is characterized in that,
This method further comprises: client produces and preserves the status indicator of local data correspondence when initialization; Server end produces and preserves the status indicator of local data correspondence when initialization;
Client further comprised before the status indicator of sign that sends client data and correspondence: client is collected the sign and the corresponding status indicator of local data.
3, method according to claim 2 is characterized in that, further comprises after client is upgraded local data:
Client is according to the status indicator of the server end Data Update client correspondence of being received.
4, method according to claim 1 is characterized in that,
Client further comprised before the status indicator of sign that sends client data and correspondence: client is collected local data, and produces corresponding status indicator according to local data;
Server end further comprised before comparing: server end produces the status indicator of local data.
5, according to claim 2,3 or 4 described methods, it is characterized in that the step of the status indicator of described generation data is:
All properties according to data calculates check code, and with the status indicator of this check code as data; Perhaps,
Variable attribute according to data calculates check code, and with the status indicator of this check code as data.
6, method according to claim 5 is characterized in that, cyclic redundancy code CRC algorithm or message digest algorithm MD5 are adopted in described calculating.
7, according to claim 2,3 or 4 described methods, it is characterized in that the step of the status indicator of described generation data is: the timestamp that utilizes data is as status indicator.
8, method according to claim 1 is characterized in that, client further comprises after upgrading local data: client repaints the topological view part corresponding with it according to the server end data of being received.
9, a kind of system of network management data synchronous refreshing is characterized in that, this system comprises the client and server end;
Wherein, client comprises:
Client database is used to store client data;
The client data administration module is used for the data of client database are read, increase, delete or revise;
The client control module is used for the sign of client data and corresponding status indicator are sent to server end, and the data of returning according to server end, upgrades data in the client database by the client data administration module;
Server end comprises:
The server end database is used for the storage server end data;
The server end data management module is used for the data of server end database are read, increase, delete or revise;
The server end control module is used for more described Data Identification clients corresponding status indicator and server end status indicator, and returns the pairing server end data of the different Data Identification of above-mentioned status indicator to client.
10, system according to claim 9 is characterized in that, this system further comprises:
The message distribution module is used for dispatch messages between client and server end.
11, system according to claim 9 is characterized in that,
Described client further comprises:
Client state sign generation module is used for producing corresponding status indicator according to the data of described client database, and is stored in the described client database;
Described server end further comprises:
Server end status indicator generation module is used for producing corresponding status indicator according to the data of described server end database, and is stored in the described server end database.
12, system according to claim 11 is characterized in that,
Described client control module comprises:
The client message receiver module is used to receive the data that described server end sends;
The client message sending module is used for the sign and the corresponding status indicator of client data are sent to described server end;
The client collection module is used for collecting the sign of described client database data and corresponding status indicator by the client data administration module, and sends to described server end by described client message sending module;
And described server end control module comprises:
Server end message sink module is used to receive sign and the corresponding status indicator that described client is sent client data, and offers the contrast module;
The server end message transmission module is used for the send server end data to described client;
The server end collection module is used for collecting by the server end data management module sign and the corresponding status indicator of described server end database data, and offers the contrast module;
The contrast module be used for more described Data Identification clients corresponding status indicator and server end status indicator, and the pairing server end data of the Data Identification that above-mentioned status indicator is different returns to client by the server end message transmission module.
13, system according to claim 9 is characterized in that,
Described client further comprises: client state sign generation module; Described client control module comprises: be used to send the sign of client data and client message sending module, the client message receiver module that is used for the reception server end data and the client collection module of corresponding status indicator; Described server end further comprises: server end status indicator generation module; Described server end control module comprises: is used for the server end message transmission module of send server end data, the sign that is used to receive described client data and corresponding status indicator and offers server end message sink module, server end collection module and the contrast module of contrast module, wherein:
Described client collection module is used for collecting by the client data administration module data of described client database;
Described client state sign generation module is used for producing corresponding status indicator according to the data of described collection, and sends to server end by described client message sending module;
Described server end collection module is used for collecting by the server end data management module data of described server end database;
Described server end status indicator generation module is used for producing corresponding status indicator according to the data of described collection, and offers described contrast module;
Described contrast module is used for more described Data Identification clients corresponding status indicator and server end status indicator, and the pairing server end data of the Data Identification that above-mentioned status indicator is different return to client by described server end message transmission module.
14, system according to claim 9 is characterized in that, described client further comprises: the view control module, the server end data that are used for receiving according to described client repaint the topological view part corresponding with these data.
Priority Applications (4)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNA2006101376436A CN1937536A (en) | 2006-10-31 | 2006-10-31 | Network management topological data synchronous refreshing method and system |
| PCT/CN2007/070589 WO2008052453A1 (en) | 2006-10-31 | 2007-08-30 | Method of netwoek managing topology data synchronous refreshing as well as clent side and server side |
| CNA2007800003328A CN101317375A (en) | 2006-10-31 | 2007-08-30 | Network management data synchronous refreshing method, and client terminal and server terminal |
| EP07021225A EP1919129A1 (en) | 2006-10-31 | 2007-10-30 | Method and system for synchronizing network management topology data |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNA2006101376436A CN1937536A (en) | 2006-10-31 | 2006-10-31 | Network management topological data synchronous refreshing method and system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN1937536A true CN1937536A (en) | 2007-03-28 |
Family
ID=37954819
Family Applications (2)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNA2006101376436A Pending CN1937536A (en) | 2006-10-31 | 2006-10-31 | Network management topological data synchronous refreshing method and system |
| CNA2007800003328A Pending CN101317375A (en) | 2006-10-31 | 2007-08-30 | Network management data synchronous refreshing method, and client terminal and server terminal |
Family Applications After (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNA2007800003328A Pending CN101317375A (en) | 2006-10-31 | 2007-08-30 | Network management data synchronous refreshing method, and client terminal and server terminal |
Country Status (2)
| Country | Link |
|---|---|
| CN (2) | CN1937536A (en) |
| WO (1) | WO2008052453A1 (en) |
Cited By (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101867605A (en) * | 2010-05-21 | 2010-10-20 | 中兴通讯股份有限公司 | Method, device and system for improving synchronous efficiency of RSS (Really Simple Syndication) business |
| CN102098342A (en) * | 2011-01-31 | 2011-06-15 | 华为技术有限公司 | Transaction level-based data synchronizing method, device thereof and system thereof |
| CN102263798A (en) * | 2010-05-25 | 2011-11-30 | ***通信集团甘肃有限公司 | Data synchronization method, device and system for communication systems |
| CN102609653A (en) * | 2012-02-07 | 2012-07-25 | 奇智软件（北京）有限公司 | File quick-scanning method and file quick-scanning system |
| CN103428264A (en) * | 2013-06-27 | 2013-12-04 | 华为软件技术有限公司 | Data synchronization method, device and system |
| CN103873496A (en) * | 2012-12-10 | 2014-06-18 | 联想(北京)有限公司 | Method and device for contact-list backup |
| CN104715197A (en) * | 2012-02-07 | 2015-06-17 | 北京奇虎科技有限公司 | Quick file scanning method and system |
| CN103117883B (en) * | 2013-03-20 | 2015-09-16 | 烽火通信科技股份有限公司 | A kind of packet equipment running status synchronous method |
| CN105009127A (en) * | 2013-02-15 | 2015-10-28 | 直观外科手术操作公司 | Systems and methods for synchronizing nodes of a robotic system |
| CN105302486A (en) * | 2015-10-20 | 2016-02-03 | 山东乾云启创信息科技股份有限公司 | Virtual offline desktop block device storage synchronization method |
| CN108509172A (en) * | 2018-04-13 | 2018-09-07 | 平安普惠企业管理有限公司 | Data transmission method, device, system and the computer storage media of simultaneous display |
| CN109284332A (en) * | 2018-08-29 | 2019-01-29 | 江苏奇异点网络有限公司 | Data processing method, client, server and computer readable storage medium |
| CN109558458A (en) * | 2018-12-30 | 2019-04-02 | 贝壳技术有限公司 | Method of data synchronization, configuration platform, transaction platform and data synchronous system |
| CN110262946A (en) * | 2019-06-14 | 2019-09-20 | 上海英方软件股份有限公司 | A kind of Topology display method and device of database synchronization Rule Information |
| CN111897886A (en) * | 2020-08-06 | 2020-11-06 | 中国联合网络通信集团有限公司 | Model management method, model management device, electronic equipment and storage medium |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115242717B (en) * | 2022-09-15 | 2022-12-09 | 四川汉唐云分布式存储技术有限公司 | Centralized storage system based on end-side calculation and control method |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7013316B1 (en) * | 2000-07-13 | 2006-03-14 | Microsoft Corporation | System and method for synchronizing multiple database files |
| JP2005530258A (en) * | 2002-06-20 | 2005-10-06 | インターナショナル・ビジネス・マシーンズ・コーポレーション | System and method for resynchronization while refreshing a client device from a server |
| GB2420882A (en) * | 2004-12-02 | 2006-06-07 | Nec Technologies | Database synchronisation system |
-
2006
- 2006-10-31 CN CNA2006101376436A patent/CN1937536A/en active Pending
-
2007
- 2007-08-30 WO PCT/CN2007/070589 patent/WO2008052453A1/en active Application Filing
- 2007-08-30 CN CNA2007800003328A patent/CN101317375A/en active Pending
Cited By (25)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101867605A (en) * | 2010-05-21 | 2010-10-20 | 中兴通讯股份有限公司 | Method, device and system for improving synchronous efficiency of RSS (Really Simple Syndication) business |
| CN102263798B (en) * | 2010-05-25 | 2013-11-20 | ***通信集团甘肃有限公司 | Data synchronization method, device and system for communication systems |
| CN102263798A (en) * | 2010-05-25 | 2011-11-30 | ***通信集团甘肃有限公司 | Data synchronization method, device and system for communication systems |
| CN102098342A (en) * | 2011-01-31 | 2011-06-15 | 华为技术有限公司 | Transaction level-based data synchronizing method, device thereof and system thereof |
| CN102098342B (en) * | 2011-01-31 | 2013-08-28 | 华为技术有限公司 | Transaction level-based data synchronizing method, device thereof and system thereof |
| CN102609653A (en) * | 2012-02-07 | 2012-07-25 | 奇智软件（北京）有限公司 | File quick-scanning method and file quick-scanning system |
| CN102609653B (en) * | 2012-02-07 | 2015-04-29 | 北京奇虎科技有限公司 | File quick-scanning method and file quick-scanning system |
| CN104715197A (en) * | 2012-02-07 | 2015-06-17 | 北京奇虎科技有限公司 | Quick file scanning method and system |
| CN104715197B (en) * | 2012-02-07 | 2019-03-08 | 北京奇虎科技有限公司 | A kind of file fast scanning method and system |
| CN103873496B (en) * | 2012-12-10 | 2018-01-23 | 联想(北京)有限公司 | A kind of method and device of address book backup |
| CN103873496A (en) * | 2012-12-10 | 2014-06-18 | 联想(北京)有限公司 | Method and device for contact-list backup |
| CN105009127A (en) * | 2013-02-15 | 2015-10-28 | 直观外科手术操作公司 | Systems and methods for synchronizing nodes of a robotic system |
| CN105009127B (en) * | 2013-02-15 | 2018-04-10 | 直观外科手术操作公司 | The system and method for synchronous robot system node |
| CN103117883B (en) * | 2013-03-20 | 2015-09-16 | 烽火通信科技股份有限公司 | A kind of packet equipment running status synchronous method |
| CN103428264A (en) * | 2013-06-27 | 2013-12-04 | 华为软件技术有限公司 | Data synchronization method, device and system |
| CN103428264B (en) * | 2013-06-27 | 2016-12-28 | 华为软件技术有限公司 | The method of data syn-chronization, equipment and system |
| CN105302486A (en) * | 2015-10-20 | 2016-02-03 | 山东乾云启创信息科技股份有限公司 | Virtual offline desktop block device storage synchronization method |
| CN108509172A (en) * | 2018-04-13 | 2018-09-07 | 平安普惠企业管理有限公司 | Data transmission method, device, system and the computer storage media of simultaneous display |
| CN108509172B (en) * | 2018-04-13 | 2024-05-24 | 北京神州数码云科信息技术有限公司 | Synchronous display data transmission method, device, system and computer storage medium |
| CN109284332A (en) * | 2018-08-29 | 2019-01-29 | 江苏奇异点网络有限公司 | Data processing method, client, server and computer readable storage medium |
| CN109558458A (en) * | 2018-12-30 | 2019-04-02 | 贝壳技术有限公司 | Method of data synchronization, configuration platform, transaction platform and data synchronous system |
| CN109558458B (en) * | 2018-12-30 | 2021-08-03 | 贝壳找房(北京)科技有限公司 | Data synchronization method, configuration platform, transaction platform and data synchronization system |
| CN110262946A (en) * | 2019-06-14 | 2019-09-20 | 上海英方软件股份有限公司 | A kind of Topology display method and device of database synchronization Rule Information |
| CN110262946B (en) * | 2019-06-14 | 2020-05-08 | 上海英方软件股份有限公司 | Topology display method and device for database synchronization rule information |
| CN111897886A (en) * | 2020-08-06 | 2020-11-06 | 中国联合网络通信集团有限公司 | Model management method, model management device, electronic equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2008052453A1 (en) | 2008-05-08 |
| CN101317375A (en) | 2008-12-03 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN1937536A (en) | Network management topological data synchronous refreshing method and system | |
| CN101409614B (en) | Data synchronization method, system and equipment | |
| CN101902473B (en) | Method for synchronously updating data based on grid GIS (Geographic Information System) | |
| CN102780724B (en) | A kind of sending method of category information, system and equipment | |
| CN101188566B (en) | A method and system for data buffering and synchronization under cluster environment | |
| CN102333029B (en) | Routing method in server cluster system | |
| CN101697166B (en) | Method for accelerating data integration of heterogeneous platform | |
| EP1940107A1 (en) | A method for processing data synchronization and client terminal, server and data synchronization system thereof | |
| US6954801B1 (en) | Method and system for reducing data volume transferred over a wireless communications network | |
| CN103841167A (en) | User data synchronizing method and device | |
| CN102480520B (en) | Media data synchronism method based on differential metadata description structure | |
| CN101706781A (en) | Method and system for centralized management of database caches | |
| CN101098248A (en) | Method and system for implementing universal network management based on configuration describing document | |
| EP1626526B1 (en) | Method and device for configuring data in communication device | |
| CN112650545A (en) | Configuration management system, method and storage medium | |
| CN106210119B (en) | Smooth capacity expansion method and system for message middleware | |
| CN102957546A (en) | Method, device and system for processing configuration | |
| CN100499637C (en) | Method for obtaining information in communication system | |
| CN102006156B (en) | Method and system for synchronizing configuration data among boards | |
| CN101547414B (en) | Short message billing system and method | |
| CN117806683A (en) | System and method for efficiently and dynamically configuring equipment parameters based on rule engine | |
| CN101753336A (en) | System for managing synchronous refreshing of topological data in computer network | |
| CN100407623C (en) | Method and system for user data transaction in communication system | |
| CN103023897B (en) | A kind of synchronous service management system and method | |
| CN111294397A (en) | npm packet management method, device, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C12 | Rejection of a patent application after its publication | ||
| RJ01 | Rejection of invention patent application after publication |
Open date: 20070328 |