CN101400043A - Method and system for consistency comparison of front-background data in mobile communication system - Google Patents
Method and system for consistency comparison of front-background data in mobile communication system Download PDFInfo
- Publication number
- CN101400043A CN101400043A CNA2007101224194A CN200710122419A CN101400043A CN 101400043 A CN101400043 A CN 101400043A CN A2007101224194 A CNA2007101224194 A CN A2007101224194A CN 200710122419 A CN200710122419 A CN 200710122419A CN 101400043 A CN101400043 A CN 101400043A
- Authority
- CN
- China
- Prior art keywords
- foreground
- unit
- data
- data library
- client
- 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)
- Information Transfer Between Computers (AREA)
Abstract
The invention discloses a method for comparing coherence of front end data and back end data in mobile communication system. After the front end data and back end data are synchronized, back end database file is generated to a first front end database file according to format of front end database file by using data transformation interface of back end unit and front end unit, compares the file with front end unit executed a second front end database file for accomplishing accurate comparison between front end and back end database file. The invention also can compares front end and back end database file before synchronizing front end and back end data to get hold of the influence back end data configuration exerts on front end data after synchronization of front end data and back end data; compares two front end database files or two back end database files after synchronization of front end and back end data to know history of configuration for front end data and back end data. Accordingly, the invention also provides a system for comparing coherence of front end data and back end data in mobile communication system.
Description
Technical field
The present invention relates to mobile communication system, relate in particular to foreground and background data consistency method and system thereof relatively in a kind of mobile communication system.
Background technology
The mobile communcations system core net comprises foreground and backstage, and the foreground is the veneer of operation mobile communication business, and the backstage is the system of the veneer of Operation and Maintenance foreground mobile communication business.All there are database in foreground and backstage, and the Foreground Data storehouse is the memory bank that autonomous property right is arranged, and the backstage is a commercial data base, for example, and oracle database, sybase database, and Sqlserver database.The Foreground Data model provides support for the mobile communication business, except the static data that background synchronization is come, also comprises the dynamic field of foreground business information.In Foreground Data and back-end data synchronizing process, the back-end data model comes down to a reflection of Foreground Data model, data are configured to the relational data model of a complexity on the backstage, be convenient configuration simultaneously, can comprise field or mapping table that some and foreground business datum have nothing to do in the back-end data model.
Because the foreground informational needs simplifies as much as possible, the information of a plurality of fields of depositing on the backstage then, being synchronized to the foreground needs to be converted to 1 byte (byte) array, 1 word (individual character) array or 1 dword (double word) array later on.Also comprise various BCD (Binary Coded Decimal during this time, binary-coded decimal number) exemplary process of sign indicating number, character and 16 system characters, and on the backstage before data are transmitted on the foreground, 1 field on foreground need obtain according to the information complicated calculations of several tables of backstage.Therefore, back-end data model and Foreground Data model are widely different, and a lot of backstages relation mapping table information can be lost in the backstage in the process of data is transmitted on the foreground, make can't directly compare after the backwards and forwards data synchronization.Back-end data model and Foreground Data model can be realized conversion, but for above-mentioned reasons, the mobile communcations system core net can't be accomplished the conversion of Foreground Data model to the back-end data model.And after foreground and background data success synchronously, there is not necessarily consistent situation in foreground and background data, this mainly be because: if back-end data is configuration error, the foreground not necessarily can send information to the backstage, and when this situation took place, the backstage must take measures to handle, if do not take measures in the backstage, behind user's configuration error,, then be not easy the location if user side breaks down.In addition, after configuration data was revised on the backstage, the user need know the modification on backstage may have influence on which table on foreground, can compare with the present existing data of database.Moreover, when rear recovery office number formulary certificate is analyzed, owing to do not have technology can directly recover the Foreground Data storehouse at present, and can only recover background data base, can't verify whether data recovered is correct.
But, in mobile communication product research and development, field testing, product use, whether foreground and background data has consistency is very crucial, if can not reach consistent after the backwards and forwards data synchronization, then can cause business normally to move because of backstage configuration data mistake.And know whether foreground and background data has consistency, and take the corresponding techniques means to change the guarantee that the inconsistent situation of foreground and background data is the normal operation of maintenance service according to the conforming situation of foreground and background data.
Have following several foreground and background data Conformance Test for Size in the prior art, first kind is that backstage table and foreground table are done CRC (Cyclic Redundancy Code, cyclic redundancy code) calculated value respectively, then the CRC calculated value is compared.And the foreground table does not just have strict one-to-one relationship with the backstage table at all, so this technology can not solve the consistency check problem of core net.Whether second kind relatively to come judgment data to revise by foreground daily record and backstage daily record consistent, but all there is detailed modification daily record on the foreground of not all system to the modification of configuration, so also just can't support correctly to compare the consistency of foreground and background data.Whether synchronously the third be to verify success by version database this shop, the problem that this technology exists has been backwards and forwards data synchronization success sometimes, but because backstage transcription error, the value that is sent to the foreground may not be expectation, and should be worth in the scope of foreground permission, alarm or prompting are not then sent in the foreground.And can't knowing this backstage, the user who uses this technical scheme is sent in the data on foreground to have revised which field.
Conforming checking required after above-mentioned backwards and forwards data synchronization, the user also wished to realize other some functions.For example, in the process of backwards and forwards data synchronization, also have polytype data need detect its consistency, also be very necessary such as the modification of locating 2 Foreground Data models, the history that can connect the foreground and background data model modification like this, fault location fast; Moreover the back-end data configuration finishes before the foreground is synchronous, and the user can compare foreground and background data, show its difference results, whether the user can judge that this secondary data changes according to difference results and conform to expection like this, if inequality then do not transmit to the foreground, avoids the user to transmit wrong data; At last, after data sync finished, this moment, foreground and background data on the principle was consistent, but the user can carry out the foreground and background data consistency relatively by force, be sure of whether data are synchronous.But the conforming verification technique of existing foreground and background data all can not realize above-mentioned some function.
In sum, existing foreground and background data consistency check technology exists not enough, on reality is used, obviously has inconvenience and defective, so be necessary to be improved.
Summary of the invention
At above-mentioned defective, the object of the present invention is to provide foreground and background data consistency method and system thereof relatively in a kind of mobile communication system, to realize the conforming accurate comparison of foreground and background data in the mobile communication system.
To achieve these goals, the invention provides foreground and background data consistency method relatively in a kind of mobile communication system, be used to comprise the mobile communication system of unit, foreground and unit, backstage, described method comprises:
Foreground and background data consistency step relatively after the data sync: after unit, backstage and foreground cell data are synchronous, the data transformation interface of this unit of backstage unit by using and unit, foreground generates the first Foreground Data library file with the back-end data model information by Foreground Data library file form, and the executed second Foreground Data library file of this document and unit, foreground is carried out the comparison of static fields; And/or
Data transmit the step of checking: before unit, backstage and foreground cell data are synchronous, the data transformation interface of this unit of backstage unit by using and unit, foreground generates the first Foreground Data library file with the back-end data model information by Foreground Data library file form, and the executed second Foreground Data library file of this document and unit, foreground is carried out the comparison of static fields; And/or
Adjacent twice data consistency step relatively after the data sync: after unit, backstage and foreground cell data were synchronous, the data transformation interface of this unit of backstage unit by using and unit, foreground carried out the comparison of static fields with adjacent twice back-end data model information by two the first Foreground Data library files that Foreground Data library file form generates.
The method according to this invention, unit, described backstage comprises client and server, the step of foreground and background data consistency comparison further comprises after the described data sync:
A1. user end to server is got the data transformation interface that utilizes this unit and unit, foreground, according to the first Foreground Data library file of Foreground Data library file form generation;
A2. client is got the executed second Foreground Data library file to the unit, foreground;
A3. the change list of the described first Foreground Data library file of client selection comparison server generation and the executed second Foreground Data library file in unit, foreground and/or all table and/or particular table;
A4. the change list of the described first Foreground Data library file of the relatively more selected server generation relatively of client and the executed second Foreground Data library file in unit, foreground and/or all table and/or particular table;
A5. after every table was relatively finished, client showed comparative result, output report.
The method according to this invention, unit, described backstage comprises client and server, the step that described data transmit preliminary examination further comprises:
B1. the data transformation interface of this unit of server by utilizing and unit, foreground generates the first Foreground Data library file according to Foreground Data library file form;
B2. user end to server is got the first Foreground Data library file that described server generates;
B3. client is got the executed second Foreground Data library file to the unit, foreground;
B4. client is selected the change list of the described first Foreground Data library file of relatively server generation and the second Foreground Data library file that the unit, foreground enters into force and/or is all shown and/or particular table;
B5. the change list of the described first Foreground Data library file of the relatively more selected server generation relatively of client and the second Foreground Data library file that the unit, foreground enters into force and/or all table and/or particular table;
B6. after every table was relatively finished, client showed comparative result, output report.
The method according to this invention, described steps A 4 or step B5 may further comprise the steps:
Client judges whether the described first Foreground Data library file that server generates is identical with the data dictionary of the executed second Foreground Data library file in unit, foreground, be execution in step next step then, otherwise client shows comparative result, output report;
Client is got the keyword of whole keywords of the executed second Foreground Data library file in unit, foreground for table;
Whole fields that client is got the described first Foreground Data library file of server generation are static fields, and the static fields of getting the executed second Foreground Data library file in unit, foreground;
Client sorts the executed second Foreground Data library file of described first Foreground Data library file and unit, foreground that server generates by described keyword, the table that does not have keyword is sorted according to the field of data dictionary order with fundamental type, till not having duplicate record;
Whole static fields in the client record that relatively the described first Foreground Data library file that generates of server is identical with keyword in the executed second Foreground Data library file in unit, foreground, and the different record of statistical static field, and only there is a situation in the file in the keyword corresponding record in two files.
The method according to this invention, unit, described backstage comprises client and server, the step of adjacent twice back-end data consistency comparison further comprises after the described data sync:
C1. user end to server get its certain utilize the data transformation interface of this unit and unit, foreground, the first Foreground Data library file that generates according to Foreground Data library file form;
C2. user end to server is got itself and certain adjacent data transformation interface that utilizes this unit and unit, foreground, the first Foreground Data library file that generates according to Foreground Data library file form;
C3. the change list of described two the first Foreground Data library files of client selection comparison server generation and/or all table and/or particular table;
C4. the change list of described two the first Foreground Data library files of the relatively more selected server generation relatively of client and/or all table and/or particular table;
C5. after every table was relatively finished, client showed comparative result, output report.
The method according to this invention, described step C4 further comprises:
C41. client judges whether the data dictionary of described two the first Foreground Data library files that server generates is identical, is execution in step C42 then, otherwise execution in step C5;
C42. client is got the keyword of whole keywords for showing of the first Foreground Data library file of corresponding unit, foreground of the last time;
C43. to get whole fields of described two the first Foreground Data library files that server generates be static fields to client;
C44. client sorts described two the first Foreground Data library files that server generates by described keyword, the table that does not have keyword is sorted according to the field of data dictionary order with fundamental type, till not having duplicate record;
C45. whole static fields in the client record that relatively keyword is identical in described two the first Foreground Data library files that generate of server, and the different record of statistical static field, and only there is a situation in the file in the keyword corresponding record in two files.
The method according to this invention, described method also comprises adjacent twice Foreground Data consistency step relatively after the data sync: after unit, backstage and foreground cell data were synchronous, the unit, backstage carried out the comparison of static fields with adjacent twice first Foreground Data library files.
The method according to this invention, unit, described backstage comprises client and server, the step of adjacent twice Foreground Data consistency comparison further comprises after the described data sync:
D1. client is got certain executed second Foreground Data library file of unit, foreground by server to the unit, foreground;
D2. client is got the adjacent executed second Foreground Data library file with certain in unit, foreground by server to the unit, foreground;
D3. client is selected the change list of more described two executed second Foreground Data library files and/or is all shown and/or particular table;
D4. the change list of relatively more selected described two the executed second Foreground Data library files relatively of client and/or all table and/or particular table;
D5. after every table was relatively finished, client showed comparative result, output report.
The method according to this invention, described step D4 further comprises:
D41. client judges whether the data dictionary of two second adjacent Foreground Data library files that the unit, foreground enters into force is identical, is execution in step D42 then, otherwise execution in step D5;
D42. client is got the keyword of whole keywords of the executed second Foreground Data library file in unit, foreground for table;
D43. to get the field of two second adjacent Foreground Data library files that the unit, foreground of table adapter configuration file configuration enters into force be static fields to client;
D44. client sorts two second adjacent Foreground Data library files that the unit, foreground enters into force by described keyword, the table that does not have keyword is sorted according to the field of data dictionary order with fundamental type, till not having duplicate record;
D45. whole static fields in the record that keyword is identical in two second adjacent Foreground Data library files entering into force of unit, client comparison foreground, and the different record of statistical static field, and only there is a situation in the file in the keyword corresponding record in two files.
The method according to this invention, after described every table was relatively finished, client showed comparative result, comprised the comparative result of table level and record level in the step of output report, wherein: described table level comparative result comprises: two file data dictionary differences; Two file data dictionaries are identical, the data field value difference; Two file data dictionaries are identical, and a file has data, and a file does not have data;
Described record level comparative result comprises: two file data unanimities; Two file data key field values are same, and other field values have difference; The record of two file same keyword does not have coupling, only exists in the file.
The present invention also provides foreground and background data consistency system relatively in a kind of mobile communication system, and this system comprises unit, foreground and unit, backstage, wherein:
After unit, described backstage and foreground cell data are synchronous, the data transformation interface of this unit of backstage unit by using and unit, foreground generates the first Foreground Data library file with the back-end data model information by Foreground Data library file form, and the executed second Foreground Data library file of this document and unit, foreground is carried out the comparison of static fields; And/or
Before unit, described backstage and foreground cell data are synchronous, the data transformation interface of this unit of backstage unit by using and unit, foreground generates the first Foreground Data library file with the back-end data model information by Foreground Data library file form, and the executed second Foreground Data library file of this document and unit, foreground is carried out the comparison of static fields; And/or
After unit, described backstage and foreground cell data were synchronous, the unit, backstage carried out the comparison of static fields with adjacent twice back-end data model information by two first Foreground Data library files of Foreground Data library file form generation with the data transformation interface of this unit of backstage unit by using and unit, foreground.
The present invention is after backwards and forwards data synchronization, the data transformation interface that utilizes unit, backstage and unit, foreground generates the first Foreground Data library file with the back-end data library file according to the form of Foreground Data library file, and with the executed second Foreground Data library file of this document and unit, foreground relatively, realize the comparison of foreground and background data library file accurately.In addition, the present invention can also compare the foreground and background data library file before backwards and forwards data synchronization, to grasp after backwards and forwards data synchronization the influence that the back-end data configuration produces Foreground Data; After also having backwards and forwards data synchronization, the comparison of twice Foreground Data library file or twice back-end data library file is to understand the account of the history of foreground and background data configuration.Simultaneously, provide the display mode of data consistency comparative result intuitively, made the attendant can get information about the conforming situation of foreground and background data.
Description of drawings
Fig. 1 is a foreground and background data consistency comparison system structure chart provided by the invention;
Fig. 2 is the method flow diagram that data consistency compares after the backwards and forwards data synchronization in the first embodiment of the invention;
Fig. 3 is the first Foreground Data library file of unit, the client comparison backstage generation in the first embodiment of the invention and the method flow of the second Foreground Data library file that the unit, foreground enters into force;
Fig. 4 is that the user is mandatory to foreground and background data consistency method flow diagram relatively in the second embodiment of the invention;
Fig. 5 is the conforming comparative approach flow chart of foreground and background data before the backwards and forwards data synchronization that provides in the third embodiment of the invention;
Fig. 6 is the comparative approach flow chart of the difference of twice transmission of backstage cell data of providing in the fourth embodiment of the invention;
Fig. 7 is the method flow diagram of unit, more adjacent twice backstage of the client in the fourth embodiment of the invention by the first Foreground Data library file of Foreground Data library file form generation;
Fig. 8 is the comparative approach flow chart of the difference of twice transmission of foreground cell data of providing in the fifth embodiment of the invention;
Fig. 9 is the method flow diagram of the more adjacent twice Foreground Data library file of client among five embodiment of the present invention;
Figure 10 is that foreground and background data consistency comparative result client of the present invention shows schematic diagram.
Embodiment
In order to make purpose of the present invention, technical scheme and advantage clearer,, the present invention is further elaborated below in conjunction with drawings and Examples.Should be appreciated that specific embodiment described herein only in order to explanation the present invention, and be not used in qualification the present invention.
Basic thought of the present invention is: the data transformation interface of existing this unit of backstage unit by using and unit, foreground, the back-end data model information is generated the first Foreground Data library file by Foreground Data library file form, the second Foreground Data library file that enters into force with the unit of fetching to the unit, foreground, foreground compares, because the two form is identical, adopt identical switching strategy and data source to generate, both difference is exactly to be that the first Foreground Data library file that the backstage generates does not have loss of data possible in the network transmission process or the out of order data contamination that causes, because being the data file that directly unit, backstage is generated, it directly writes file simultaneously, the data consistent check and the uniqueness that do not have the Foreground Data storehouse of unit, foreground warehouse-in, there is not the relevant dynamic field information of the foreground unit business that comprises in the Foreground Data library file yet, this document its in fact real embodiment the complete information of background data base, use the executed second Foreground Data library file in this document and corresponding unit, foreground relatively, can be understood as the comparison of backstage model and foreground model.
Fig. 1 is a foreground and background data consistency comparison system structure chart provided by the invention, is described below;
This system has comprised unit, foreground 101 and unit, backstage 102, after unit, backstage 102 and unit, foreground 101 data sync, unit, backstage 102 utilizes the data transformation interface of this unit and unit, foreground 101 that the back-end data model information is generated the first Foreground Data library file by Foreground Data library file form, and this document and unit, the foreground 101 executed second Foreground Data library files are carried out the comparison of static fields; And/or
Before unit, backstage 102 and unit, foreground 101 data sync, unit, backstage 102 utilizes this unit 102 and the data transformation interface of unit, foreground 101 that the back-end data model information is generated the first Foreground Data library file by Foreground Data library file form, and this document and unit, the foreground 101 executed second Foreground Data library files are carried out the comparison of static fields; And/or
After unit, backstage 102 and unit, foreground 101 data sync, unit, backstage 102 utilizes unit, backstage 102 data transformation interface of this unit and unit, foreground 101 adjacent twice back-end data model information carried out the comparison of static fields by two the first Foreground Data library files that Foreground Data library file form generates; And/or
After unit, backstage 102 and unit, foreground 101 data sync, unit, backstage 102 carries out the comparison of static fields with adjacent twice second Foreground Data library files.
Utilize above-mentioned foreground and background data consistency comparison system to carry out comprising in the method for foreground and background data consistency comparison foreground and background data consistency step relatively after unit, backstage 102 and unit, foreground 101 data sync: after unit, backstage 102 and unit, foreground 101 data sync, unit, backstage 102 utilizes the data transformation interface of this unit and unit, foreground 101 that the back-end data model information is generated the first Foreground Data library file by Foreground Data library file form, and this document and unit, the foreground 101 executed second Foreground Data library files are carried out the comparison of static fields.
In the present invention, unit, backstage 102 utilizes the data transformation interface of this unit and unit, foreground 101, the first Foreground Data library file by the generation of Foreground Data library file form, directly use the identical foreground and background data of backwards and forwards data synchronization adaptive, guaranteed that database file is identical with the actual effect that transmits.
Because the field of the table in cell data storehouse, foreground is divided into static fields and dynamic field, static fields is relevant with the configuration of unit, backstage, relatively the static fields of foreground and background data library file can be relatively after data sync, the difference of Foreground Data library file and 102 configurations of unit, backstage.The configuration relation of the dynamic field of this and Foreground Data library file is little, is business procedure information, in comparison procedure it is masked, and to dynamic field not with relatively, this can be provided with switch, whether control shields dynamic field.The dynamic field of each table allows the user dispose because each version may be all different, maintenance is very big, utilize existing table adapter configuration file, because static fields is all in the table adapter configuration file, as long as non-existent field is all thought dynamic field in the correspondence table adapter arrangement file, for there being unit, backstage 102 to utilize the data transformation interface of this unit and unit, foreground 101, the Foreground Data library file that generates by Foreground Data library file form participates in its whole fields to be decided to be static fields under the situation relatively.
Fig. 2 is the method flow diagram that data consistency compares after the backwards and forwards data synchronization in the first embodiment of the invention;
In this embodiment, unit, backstage 102 comprises client and server.
Among the step S201, user end to server is got the data transformation interface that utilizes this unit and unit, foreground 101, according to the first Foreground Data library file of Foreground Data library file form generation;
Among the step S202, client is got the executed second Foreground Data library file to unit, foreground 101;
Among the step S203, client is selected the change list of described first Foreground Data library file that server relatively generates and the executed second Foreground Data library file in unit, foreground and/or all table and/or particular table;
Among the step S204, the described first Foreground Data library file that the relatively selected server relatively of client generates and the change list of unit, the foreground 101 executed second Foreground Data library files and/or all table and/or particular table;
Among the step S205, after every table was relatively finished, client showed comparative result, output report.
Unit, backstage 102 utilizes the data transformation interface of this unit and unit, foreground 101, the multidate information that does not comprise the Foreground Data library file according to the first Foreground Data library file of Foreground Data library file form generation, the order that the while data record is deposited may be different, the Foreground Data storehouse does not provide keyword to static table, the table that keyword arranged is unique index not necessarily also, relatively brings difficulty for the foreground and background data consistency.Because the Foreground Data model is placed on data dictionary and data in the same file, itself possesses self descriptiveness, can utilize data dictionary information, the keyword that adopts when being comparison with the keyword of unit, foreground 101 database files, the foreground and background data consistency is relatively more preceding to sort to data, sort according to the field of data dictionary order for the table that does not have keyword, till not having duplicate record with fundamental type such as byte, word, dword, char (field).Comparison procedure should be only to compare the static fields of two groups of data simultaneously, comparison procedure is only with the whole fields in the first Foreground Data library file of relatively unit, backstage 102 generations like this, exist in the second Foreground Data library file that enters into force for unit, foreground 101, and non-existent field does not participate in comparison in the first Foreground Data library file that unit, backstage 102 generates.
Fig. 3 is the first Foreground Data library file of unit, client comparison backstage 102 generations in the first embodiment of the invention and the method flow diagram of the second Foreground Data library file that unit, foreground 101 enters into force, and is described below;
Among the step S301, client judges whether the described first Foreground Data library file of server generation is identical with the data dictionary of unit, the foreground 101 executed second Foreground Data library files, be that then execution in step S302 writes down level relatively, otherwise execution in step S306; The table level that this step belongs to described two files compares.
The data dictionary of these two files relatively in, all the static fields definition must be identical, wherein needs comparison field name, field type, field length.There is any inconsistent situation in data dictionary, this table information is not compared, and it is inconsistent directly to report two table data dictionaries.
Among the step S302, client is got the keyword of whole keywords of unit, the foreground 101 executed second Foreground Data library files for table;
Write down relatively bad comparison of level because the record of foreground and background data library file table order possibility is different, need to get the keyword of whole keywords of unit, the foreground 101 executed second Foreground Data library files in the present embodiment for table by identical keyword ordering.
Among the step S303, whole fields that client is got the described first Foreground Data library file of server generation are static fields, and the static fields of getting unit, the foreground 101 executed second Foreground Data library files;
Among the step S304, client sorts described first Foreground Data library file and unit, the foreground 101 executed second Foreground Data library files that server generates by described keyword, the table that does not have keyword is sorted according to the field of data dictionary order with fundamental type, till not having duplicate record.
When if definition acquiescence sorts with the field of fundamental type, then can unify the order that the field with fundamental type occurs in the back-end data dictionary is that comparative sequence is checked other fields, till not having identical recordings.
Among the step S305, whole static fields in the client record that relatively the described first Foreground Data library file that generates of server is identical with keyword in unit, the foreground 101 executed second Foreground Data library files, and the different record of statistical static field, and only there is a situation in the file in the keyword corresponding record in two files.
Among the step S306, client presents comparative result, and output is report relatively.Comparative result is divided into table level comparative result and record level comparative result, uses different icon representations, intuitive and convenient when showing respectively.Simultaneously also provide the comparative result form, make things convenient for Macro or mass analysis.
Fig. 4 is that the user is mandatory to foreground and background data consistency method flow diagram relatively in the second embodiment of the invention, and in this embodiment, unit, backstage 102 comprises client and server.
Among the step S401, client is got the first Foreground Data library file by the generation of Foreground Data library file form that server transmitted successfully preservation last time;
Among the step S402, client is got the unit, foreground by server and was transmitted the second Foreground Data library file of successfully preserving 101 last time;
Among the step S403, client need to select the table of the described first and second foreground and background data library files relatively, compares as selecting change list, whole table or particular table;
Among the step S404, client is according to selecting to need the table of the described first and second foreground and background data library files relatively to compare, comparative approach is as among first embodiment, and the first Foreground Data library file that unit, client comparison backstage 102 generates is consistent with the method for the second Foreground Data library file that unit, foreground 101 enters into force.
Among the step S405, after every table relatively finished, client showed comparative result.Comparative result is divided into, table level result and record level comparative result.
For mobile communication business there being one grasp preferably and control, the present invention also provides the foreground and background data before backwards and forwards data synchronization conforming comparative approach, after can grasping backwards and forwards data synchronization in advance by the preliminary examination before transmitting, the influence that the data configuration on backstage will produce the foreground configuration.According to the comparing difference result, judge that this secondary data changes whether to conform to expection, if inequality then do not transmit, avoid the user to transmit wrong data to the foreground.
In the step that the foreground and background data consistency compares after this data sync, after unit, backstage 102 and unit, foreground 101 data sync, unit, backstage 102 utilizes the data transformation interface of this unit and unit, foreground 101 that the back-end data model information is generated the first Foreground Data library file by Foreground Data library file form, and this document and unit, the foreground 101 executed second Foreground Data library files are carried out the comparison of static fields;
Fig. 5 is the conforming comparative approach flow chart of foreground and background data before the backwards and forwards data synchronization that provides in the third embodiment of the invention; In this embodiment, unit, backstage 102 comprises client and server.
Among the step S501, the data transformation interface of this unit of server by utilizing and unit, foreground 101 generates the first Foreground Data library file according to Foreground Data library file form;
Among the step S502, user end to server is got the first Foreground Data library file that described server generates;
Among the step S503, client is got the executed second Foreground Data library file in foreground to unit, foreground 101;
Among the step S504, client is selected the change list of the described first Foreground Data library file of relatively server generation and the second Foreground Data library file that unit, foreground 101 enters into force and/or is all shown and/or particular table;
Among the step S505, client is relatively selected the change list of the described first Foreground Data library file of server generation relatively and the second Foreground Data library file that unit, foreground 101 enters into force and/or is all shown and/or particular table;
Among the step S506, after every table relatively finished, client showed comparative result.Comparative result is divided into, table level result and record level comparative result.
Among the of the present invention second and the 3rd embodiment, second Foreground Data library file that unit, foreground 101 enters into force and unit, backstage 102 are according to the comparative approach of two files among same first embodiment of the comparative approach of the first Foreground Data file of Foreground Data library file form generation.
In mobile communication system, the modification of 2 the foreground and background data models in location also is very necessary, can connect the history of foreground and background data model modification like this, fast fault location; The comparison that also provides forward and backward data to transmit difference twice in the present invention among other embodiment.
Adjacent twice back-end data consistency step relatively after the data sync: after unit, backstage 102 and unit, foreground 101 data sync, unit, backstage 102 carries out the comparison of static fields with adjacent twice back-end data model information by two the first Foreground Data library files that Foreground Data library file form generates with this unit by using foreground and background data translation interface.
Fig. 6 is the comparative approach flow chart of the difference of twice transmission of unit, backstage 101 data of providing in the fourth embodiment of the invention, and in this embodiment, unit, backstage 102 comprises client and to server.
Among the step S601, user end to server get its certain utilize the data transformation interface of this unit and unit, foreground 101, the first Foreground Data library file that generates according to Foreground Data library file form;
Among the step S602, user end to server is got itself and certain adjacent data transformation interface that utilizes this unit and unit, foreground 101, the first Foreground Data library file that generates according to Foreground Data library file form;
Among the step S603, client is selected the change list of described two the first Foreground Data library files that server relatively generates and/or all table and/or particular table;
Among the step S604, the change list of described two the first Foreground Data library files that the relatively selected server relatively of client generates and/or all table and/or particular table;
Among the step S605, after every table was relatively finished, client showed comparative result, output report.Comparative result is divided into, table level result and record level comparative result.
Fig. 7 is the method flow diagram of unit, more adjacent twice backstage of the client in the fourth embodiment of the invention by the Foreground Data library file of Foreground Data library file form generation, is described below;
Among the step S701, client judges whether the data dictionary of described two the first Foreground Data library files that server generates is identical, is that then execution in step S702 writes down level relatively, otherwise execution in step S706; This table level that belongs to described two files compares.
In the comparison of the data dictionary of these two files, all the static fields definition must be identical.Wherein need comparison field name, field type, field length.There is any inconsistent situation in data dictionary, this table information is not compared, and it is inconsistent directly to report two table data dictionaries.
Among the step S702, client is got the keyword of whole keywords for showing of the first Foreground Data library file of corresponding unit, foreground 101 of the last time.
Among the step S703, whole fields that client is got described two the first Foreground Data library files of server generation are static fields.
Among the step S704, client sorts by two the first Foreground Data library files that Foreground Data library file form generates server by described keyword, the table that does not have keyword is sorted according to the field of data dictionary order with fundamental type, till not having duplicate record.
Among the step S705, client compares server by whole static fields in the record that keyword is identical in two the first Foreground Data library files of Foreground Data library file form generation, and the different record of statistical static field, and only there is a situation in the file in the keyword corresponding record in two files.
Among the step S706, client presents comparative result, and output is report relatively.Comparative result is divided into table level comparative result and record level comparative result.
In another embodiment of the present invention, different with a last embodiment is that present embodiment is adjacent twice Foreground Data consistency step relatively after the data sync: after unit, backstage 102 and unit, foreground 101 data sync, unit, backstage 102 compares adjacent twice second Foreground Data library files.
Fig. 8 is the comparative approach flow chart of the difference of twice transmission of unit, foreground 101 data of providing in the fifth embodiment of the invention, and in this embodiment, unit, backstage 102 comprises client and server.
Among the step S801, client is got its certain executed second Foreground Data library file by server to unit, foreground 101;
Among the step S802, client is got itself and certain adjacent executed second Foreground Data library file by server to unit, foreground 101;
Among the step S803, client is selected to compare the change list of two executed Foreground Data library files and/or is all shown and/or particular table;
Among the step S804, client is relatively selected the change list of two executed second Foreground Data library files relatively and/or is all shown and/or particular table;
Among the step S805, after every table was relatively finished, client showed comparative result, output report.
Fig. 9 is the method flow diagram of the more adjacent twice second Foreground Data library files of client among five embodiment of the present invention.
Among the step S901, client judges whether the data dictionary of two second adjacent Foreground Data library files that unit, foreground 101 enters into force is identical, is that then execution in step S902 writes down level relatively, otherwise execution in step S906; The table level that this step belongs to described two files compares.
In the data dictionary of these two files, all the static fields definition must be identical.Wherein need comparison field name, field type, field length.There is any inconsistent situation in data dictionary, this table information is not compared, and it is inconsistent directly to report two table data dictionaries.
Among the step S902, client is got the keyword of whole keywords of unit, the foreground 101 executed second Foreground Data library files for table.
Among the step S903, the field that client is got two second adjacent Foreground Data library files that the unit, foreground 101 of table adapter configuration file configuration enters into force is a static fields;
Among the step S904, client sorts two second adjacent Foreground Data library files that unit, foreground 101 enters into force by described keyword, the table that does not have keyword is sorted according to the field of data dictionary order with fundamental type, till not having duplicate record.
Among the step S905, whole static fields in the record that keyword is identical in two second adjacent Foreground Data library files that unit, client comparison foreground 101 enters into force, and the different record of statistical static field, and only there is a situation in the file in the keyword corresponding record in two files.
Among the step S906, client presents comparative result, and output is report relatively.Comparative result is divided into table level comparative result and record level comparative result.
In above-mentioned a plurality of embodiment, after every table was relatively finished, client showed comparative result, comprised the comparative result of table level and record level in the step of output report, and wherein: table level comparative result comprises: two file data dictionary differences; Two file data dictionaries are identical, the data field value difference; Two file data dictionaries are identical, and a file has data, and a file does not have data;
Record level comparative result comprises: two file data unanimities; Two file data key field values are same, and other field values have difference; The record of two file same keyword does not have coupling, only exists in the file.
The record rank provides detailed comparative result presentation mode shown in Figure 10, can embody two differences on the field between comparison document in mode the most intuitively, 1002 sign difference fields are while 1001 signs have the record that does not have, double-click the row of difference simultaneously, print zone has detail analysis information.
In sum, the present invention is after backwards and forwards data synchronization, the data transformation interface that utilizes unit, backstage and unit, foreground generates the first Foreground Data library file with the back-end data library file according to the form of Foreground Data library file, and with the executed second Foreground Data library file of this document and unit, foreground relatively, realize the comparison of foreground and background data library file accurately.In addition, the present invention can also compare the foreground and background data library file before backwards and forwards data synchronization, to grasp after backwards and forwards data synchronization the influence that the back-end data configuration produces Foreground Data; After also having backwards and forwards data synchronization, the comparison of twice Foreground Data library file or twice back-end data library file is to understand the account of the history of foreground and background data configuration.Simultaneously, provide the display mode of data consistency comparative result intuitively, made the attendant can intuitively understand the conforming situation of foreground and background data.
Certainly; the present invention also can have other various embodiments; under the situation that does not deviate from spirit of the present invention and essence thereof; those of ordinary skill in the art work as can make various corresponding changes and distortion according to the present invention, but these corresponding changes and distortion all should belong to the protection range of the appended claim of the present invention.
Claims (11)
1, foreground and background data consistency method relatively in a kind of mobile communication system is used to comprise the mobile communication system of unit, foreground and unit, backstage it is characterized in that described method comprises:
Foreground and background data consistency step relatively after the data sync: after unit, backstage and foreground cell data are synchronous, the data transformation interface of this unit of backstage unit by using and unit, foreground generates the first Foreground Data library file with the back-end data model information by Foreground Data library file form, and the executed second Foreground Data library file of this document and unit, foreground is carried out the comparison of static fields; And/or
Data transmit the step of checking: before unit, backstage and foreground cell data are synchronous, the data transformation interface of this unit of backstage unit by using and unit, foreground generates the first Foreground Data library file with the back-end data model information by Foreground Data library file form, and the executed second Foreground Data library file of this document and unit, foreground is carried out the comparison of static fields; And/or
Adjacent twice data consistency step relatively after the data sync: after unit, backstage and foreground cell data were synchronous, the data transformation interface of this unit of backstage unit by using and unit, foreground carried out the comparison of static fields with adjacent twice back-end data model information by two the first Foreground Data library files that Foreground Data library file form generates.
2, method according to claim 1 is characterized in that, unit, described backstage comprises client and server, and the step of foreground and background data consistency comparison further comprises after the described data sync:
A1. user end to server is got the data transformation interface that utilizes this unit and unit, foreground, according to the first Foreground Data library file of Foreground Data library file form generation;
A2. client is got the executed second Foreground Data library file to the unit, foreground;
A3. the change list of the described first Foreground Data library file of client selection comparison server generation and the executed second Foreground Data library file in unit, foreground and/or all table and/or particular table;
A4. the change list of the described first Foreground Data library file of the relatively more selected server generation relatively of client and the executed second Foreground Data library file in unit, foreground and/or all table and/or particular table;
A5. after every table was relatively finished, client showed comparative result, output report.
3, method according to claim 1 is characterized in that, unit, described backstage comprises client and server, and the step that described data transmit preliminary examination further comprises:
B1. the data transformation interface of this unit of server by utilizing and unit, foreground generates the first Foreground Data library file according to Foreground Data library file form;
B2. user end to server is got the first Foreground Data library file that described server generates;
B3. client is got the executed second Foreground Data library file to the unit, foreground;
B4. client is selected the change list of the described first Foreground Data library file of relatively server generation and the second Foreground Data library file that the unit, foreground enters into force and/or is all shown and/or particular table;
B5. the change list of the described first Foreground Data library file of the relatively more selected server generation relatively of client and the second Foreground Data library file that the unit, foreground enters into force and/or all table and/or particular table;
B6. after every table was relatively finished, client showed comparative result, output report.
According to claim 2 or 3 described methods, it is characterized in that 4, described steps A 4 or step B5 may further comprise the steps:
Client judges whether the described first Foreground Data library file that server generates is identical with the data dictionary of the executed second Foreground Data library file in unit, foreground, be execution in step next step then, otherwise client shows comparative result, output report;
Client is got the keyword of whole keywords of the executed second Foreground Data library file in unit, foreground for table;
Whole fields that client is got the described first Foreground Data library file of server generation are static fields, and the static fields of getting the executed second Foreground Data library file in unit, foreground;
Client sorts the executed second Foreground Data library file of described first Foreground Data library file and unit, foreground that server generates by described keyword, the table that does not have keyword is sorted according to the field of data dictionary order with fundamental type, till not having duplicate record;
Whole static fields in the client record that relatively the described first Foreground Data library file that generates of server is identical with keyword in the executed second Foreground Data library file in unit, foreground, and the different record of statistical static field, and only there is a situation in the file in the keyword corresponding record in two files.
5, method according to claim 1 is characterized in that, unit, described backstage comprises client and server, and the step of adjacent twice back-end data consistency comparison further comprises after the described data sync:
C1. user end to server get its certain utilize the data transformation interface of this unit and unit, foreground, the first Foreground Data library file that generates according to Foreground Data library file form;
C2. user end to server is got itself and certain adjacent data transformation interface that utilizes this unit and unit, foreground, the first Foreground Data library file that generates according to Foreground Data library file form;
C3. the change list of described two the first Foreground Data library files of client selection comparison server generation and/or all table and/or particular table;
C4. the change list of described two the first Foreground Data library files of the relatively more selected server generation relatively of client and/or all table and/or particular table;
C5. after every table was relatively finished, client showed comparative result, output report.
6, method according to claim 5 is characterized in that, described step C4 further comprises:
C41. client judges whether the data dictionary of described two the first Foreground Data library files that server generates is identical, is execution in step C42 then, otherwise execution in step C5;
C42. client is got the keyword of whole keywords for showing of the first Foreground Data library file of corresponding unit, foreground of the last time;
C43. to get whole fields of described two the first Foreground Data library files that server generates be static fields to client;
C44. client sorts described two the first Foreground Data library files that server generates by described keyword, the table that does not have keyword is sorted according to the field of data dictionary order with fundamental type, till not having duplicate record;
C45. whole static fields in the client record that relatively keyword is identical in described two the first Foreground Data library files that generate of server, and the different record of statistical static field, and only there is a situation in the file in the keyword corresponding record in two files.
7, method according to claim 1, it is characterized in that, described method also comprises adjacent twice Foreground Data consistency step relatively after the data sync: after unit, backstage and foreground cell data were synchronous, the unit, backstage carried out the comparison of static fields with adjacent twice first Foreground Data library files.
8, method according to claim 7 is characterized in that, unit, described backstage comprises client and server, and the step of adjacent twice Foreground Data consistency comparison further comprises after the described data sync:
D1. client is got certain executed second Foreground Data library file of unit, foreground by server to the unit, foreground;
D2. client is got the adjacent executed second Foreground Data library file with certain in unit, foreground by server to the unit, foreground;
D3. client is selected the change list of more described two executed second Foreground Data library files and/or is all shown and/or particular table;
D4. the change list of relatively more selected described two the executed second Foreground Data library files relatively of client and/or all table and/or particular table;
D5. after every table was relatively finished, client showed comparative result, output report.
9, method according to claim 8 is characterized in that, described step D4 further comprises:
D41. client judges whether the data dictionary of two second adjacent Foreground Data library files that the unit, foreground enters into force is identical, is execution in step D42 then, otherwise execution in step D5;
D42. client is got the keyword of whole keywords of the executed second Foreground Data library file in unit, foreground for table;
D43. to get the field of two second adjacent Foreground Data library files that the unit, foreground of table adapter configuration file configuration enters into force be static fields to client;
D44. client sorts two second adjacent Foreground Data library files that the unit, foreground enters into force by described keyword, the table that does not have keyword is sorted according to the field of data dictionary order with fundamental type, till not having duplicate record;
D45. whole static fields in the record that keyword is identical in two second adjacent Foreground Data library files entering into force of unit, client comparison foreground, and the different record of statistical static field, and only there is a situation in the file in the keyword corresponding record in two files.
10, according to claim 2,3,5,8 described methods, it is characterized in that, after described every table is relatively finished, client shows comparative result, the comparative result that comprises table level and record level in the step of output report, wherein: described table level comparative result comprises: two file data dictionary differences; Two file data dictionaries are identical, the data field value difference; Two file data dictionaries are identical, and a file has data, and a file does not have data;
Described record level comparative result comprises: two file data unanimities; Two file data key field values are same, and other field values have difference; The record of two file same keyword does not have coupling, only exists in the file.
11, a kind of system that realizes claim 1,2,3,5 or 6 any described methods of claim, this system comprises unit, foreground and unit, backstage, it is characterized in that,
After unit, described backstage and foreground cell data are synchronous, the data transformation interface of this unit of backstage unit by using and unit, foreground generates the first Foreground Data library file with the back-end data model information by Foreground Data library file form, and the executed second Foreground Data library file of this document and unit, foreground is carried out the comparison of static fields; And/or
Before unit, described backstage and foreground cell data are synchronous, the data transformation interface of this unit of backstage unit by using and unit, foreground generates the first Foreground Data library file with the back-end data model information by Foreground Data library file form, and the executed second Foreground Data library file of this document and unit, foreground is carried out the comparison of static fields; And/or
After unit, described backstage and foreground cell data were synchronous, the unit, backstage carried out the comparison of static fields with adjacent twice back-end data model information by two first Foreground Data library files of Foreground Data library file form generation with the data transformation interface of this unit of backstage unit by using and unit, foreground.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2007101224194A CN101400043B (en) | 2007-09-25 | 2007-09-25 | Method and system for consistency comparison of front-background data in mobile communication system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2007101224194A CN101400043B (en) | 2007-09-25 | 2007-09-25 | Method and system for consistency comparison of front-background data in mobile communication system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101400043A true CN101400043A (en) | 2009-04-01 |
| CN101400043B CN101400043B (en) | 2010-11-24 |
Family
ID=40518235
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2007101224194A Expired - Fee Related CN101400043B (en) | 2007-09-25 | 2007-09-25 | Method and system for consistency comparison of front-background data in mobile communication system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101400043B (en) |
Cited By (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102083123A (en) * | 2011-03-01 | 2011-06-01 | 中国联合网络通信集团有限公司 | Gateway test method, device and system |
| CN102263798A (en) * | 2010-05-25 | 2011-11-30 | ***通信集团甘肃有限公司 | Data synchronization method, device and system for communication systems |
| CN102629263A (en) * | 2012-02-29 | 2012-08-08 | 上海安捷力信息***有限公司 | Method and system for format conversion of interactive business data among enterprises |
| WO2014169738A1 (en) * | 2013-04-18 | 2014-10-23 | 中兴通讯股份有限公司 | Active and standby databases, consistency checking and recovering methods and apparatuses, and storage medium |
| CN106202111A (en) * | 2015-05-06 | 2016-12-07 | 阿里巴巴集团控股有限公司 | The method of calibration of database data and device |
| CN106293678A (en) * | 2015-06-09 | 2017-01-04 | 北京京东尚科信息技术有限公司 | A kind of method and system of the variable managing application service |
| CN107040872A (en) * | 2016-02-03 | 2017-08-11 | 西门子保健有限责任公司 | The config update of the medical equipment connected without internet |
| CN107103086A (en) * | 2017-04-28 | 2017-08-29 | 努比亚技术有限公司 | A kind of method and system of data acquisition audit, computer-readable recording medium |
| CN108228443A (en) * | 2016-12-14 | 2018-06-29 | 北京国双科技有限公司 | A kind of test method and device of web applications |
| CN110928879A (en) * | 2019-11-20 | 2020-03-27 | 贵州电网有限责任公司电力科学研究院 | Wide table generation method and device |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6832226B1 (en) * | 2000-10-11 | 2004-12-14 | Bruce H. Parker | Method of providing data dictionary-driven web-based database applications |
| CN1232062C (en) * | 2002-12-05 | 2005-12-14 | 华为技术有限公司 | A method for guaranteeing foreground and background data consistency in mobile switching center |
| CN100388675C (en) * | 2003-11-13 | 2008-05-14 | 中兴通讯股份有限公司 | A method for implementing foreground data configuration in network management system |
| CN1835444B (en) * | 2005-03-16 | 2010-04-28 | 中兴通讯股份有限公司 | Multi-processor static parameter synchronous system of radio internet controller and method thereof |
-
2007
- 2007-09-25 CN CN2007101224194A patent/CN101400043B/en not_active Expired - Fee Related
Cited By (16)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102263798A (en) * | 2010-05-25 | 2011-11-30 | ***通信集团甘肃有限公司 | Data synchronization method, device and system for communication systems |
| CN102263798B (en) * | 2010-05-25 | 2013-11-20 | ***通信集团甘肃有限公司 | Data synchronization method, device and system for communication systems |
| CN102083123A (en) * | 2011-03-01 | 2011-06-01 | 中国联合网络通信集团有限公司 | Gateway test method, device and system |
| CN102629263A (en) * | 2012-02-29 | 2012-08-08 | 上海安捷力信息***有限公司 | Method and system for format conversion of interactive business data among enterprises |
| CN102629263B (en) * | 2012-02-29 | 2014-08-20 | 上海安捷力信息***有限公司 | Method and system for format conversion of interactive business data among enterprises |
| WO2014169738A1 (en) * | 2013-04-18 | 2014-10-23 | 中兴通讯股份有限公司 | Active and standby databases, consistency checking and recovering methods and apparatuses, and storage medium |
| CN106202111B (en) * | 2015-05-06 | 2019-10-29 | 阿里巴巴集团控股有限公司 | The method of calibration and device of database data |
| CN106202111A (en) * | 2015-05-06 | 2016-12-07 | 阿里巴巴集团控股有限公司 | The method of calibration of database data and device |
| CN106293678A (en) * | 2015-06-09 | 2017-01-04 | 北京京东尚科信息技术有限公司 | A kind of method and system of the variable managing application service |
| CN106293678B (en) * | 2015-06-09 | 2020-11-24 | 北京京东尚科信息技术有限公司 | Method and system for managing variables of application service |
| CN107040872A (en) * | 2016-02-03 | 2017-08-11 | 西门子保健有限责任公司 | The config update of the medical equipment connected without internet |
| CN108228443A (en) * | 2016-12-14 | 2018-06-29 | 北京国双科技有限公司 | A kind of test method and device of web applications |
| CN108228443B (en) * | 2016-12-14 | 2021-10-15 | 北京国双科技有限公司 | Web application testing method and device |
| CN107103086B (en) * | 2017-04-28 | 2020-11-06 | 杭州升迈科技有限公司 | Data acquisition auditing method and system, and computer readable storage medium |
| CN107103086A (en) * | 2017-04-28 | 2017-08-29 | 努比亚技术有限公司 | A kind of method and system of data acquisition audit, computer-readable recording medium |
| CN110928879A (en) * | 2019-11-20 | 2020-03-27 | 贵州电网有限责任公司电力科学研究院 | Wide table generation method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101400043B (en) | 2010-11-24 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101400043B (en) | Method and system for consistency comparison of front-background data in mobile communication system | |
| CN107807982B (en) | Consistency checking method and device for heterogeneous database | |
| US10237295B2 (en) | Automated event ID field analysis on heterogeneous logs | |
| US9639591B2 (en) | Low latency replication techniques with content addressable storage | |
| US20190050470A1 (en) | Method and apparatus for processing database data in distributed database system | |
| CN104021123B (en) | method and system for data migration | |
| US10067999B2 (en) | High-performance database replication systems and methods | |
| CN104268272A (en) | Method and device for checking uniqueness of data | |
| CN105554044B (en) | The method and device of synchronization object in native object memory node | |
| CN104484131B (en) | The data processing equipment of multiple disks server and corresponding processing method | |
| CN102981882B (en) | Analytic method and device | |
| CN109522228A (en) | Interface automatic test data configuration method, apparatus, platform and storage medium | |
| CN104809250A (en) | Loose type data consistency checking method | |
| CN103473056A (en) | Automatic generation method for telemetering configuration files | |
| CN103176989A (en) | Method and system used for comparing database table levels and based on data dictionary and variable rules | |
| CN114281793A (en) | Data verification method, device and system | |
| CN110121694B (en) | Log management method, server and database system | |
| CN112579007A (en) | Method and device for acquiring full storage link and electronic equipment | |
| US20050066316A1 (en) | Localization cataloguing tool | |
| CN106682141B (en) | Data synchronization method based on service operation log | |
| EP3258377B1 (en) | Replication of log-structured data | |
| CN104463460B (en) | Processing method and processing device for the waiting information that network data is launched | |
| CN108845892A (en) | Data processing method, device, equipment and the computer storage medium of distributed data base | |
| CN110121712B (en) | Log management method, server and database system | |
| CN107968722B (en) | Method for converting interface control file into AFDX (avionics full Duplex switched Ethernet) network equipment configuration file |
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 | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20101124 Termination date: 20160925 |