CN100461704C - Data synchronizing method - Google Patents
Data synchronizing method Download PDFInfo
- Publication number
- CN100461704C CN100461704C CNB2006101572408A CN200610157240A CN100461704C CN 100461704 C CN100461704 C CN 100461704C CN B2006101572408 A CNB2006101572408 A CN B2006101572408A CN 200610157240 A CN200610157240 A CN 200610157240A CN 100461704 C CN100461704 C CN 100461704C
- Authority
- CN
- China
- Prior art keywords
- transfer function
- data
- data block
- software
- version software
- 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.)
- Active
Links
Images
Abstract
A method for synchronizing data includes setting dynamic data block coding as the same to old version software in new version software, setting up synchronous data block content conversion function of new version software and old version software, calling up said conversion function when dynamic data is synchronized from unupgraded device to upgraded device in order to finalize synchronization of dynamic data.
Description
Technical field
The present invention relates to the communications field, particularly do not interrupt the method for data sync in the escalation process.
Background technology
At present the upgrading ubiquity of software in the communications field causes service disconnection easily in the escalation process, and in telecommunication service reliability requirement more and more higher today, in-service upgrade becomes very urgent demand.The main process of existing device upgrade is as follows:
(11) upgrading before active and standby plate all normally the operation, operation all be legacy version;
(12) mainboard and slave board all load new program and configuration data;
(13) two master control borads that reset allow new program come into force.
As can be seen, two master control borads have all passed through and have resetted in escalation process, and service disconnection is inevitable.
Because existing technology limitation, temporarily do not accomplish also that master control borad does not reset and program software that will be new is replaced old program software and moved, so the software upgrading master control borad resets unavoidably.General way is to utilize the function of masterslave switchover to realize the unbroken function of staging business now, and step is as follows:
(21) upgrading before active and standby plate all normally the operation, operation all be legacy version;
(22) slave board is upgraded to new version;
(23) mainboard arrives slave board with data sync;
(24) the data sync masterslave switchover that finishes, new mainboard (slave board originally) are brought into use the new professional operation of version program control;
(25) new slave board (mainboard originally) is upgraded to new version.
In the superincumbent operating process, (23) step was crucial, because have only the data of mainboard to be synchronized to slave board fully, active and standbyly just can switch, and could guaranteeing to switch afterwards, any interruption does not take place business.Owing to active and standby version difference this moment, mainboard is synchronized to the data of slave board, and slave board can not guarantee to discern fully and understand.So the data sync of different editions is the key that solves in-service upgrade.
Active and standby data in synchronization can be divided into two classes, and a class is user's a configuration data, and another kind of is the dynamic operation data.Configuration data can use external tool to be upgraded to the mode that redaction reloads slave board then to carry out synchronously by deriving with the form of file earlier, but dynamic data is relevant with the dynamic state of run of system, can not adopt this kind mode, dynamic data can only be in the process of active and standby plate operation, to come synchronously synchronously by the mode of message transmission.
Under the scene of in-service upgrade dynamic data face a difficult point synchronously: active and standby version is inconsistent during data sync, and the synchronous past data slave board of mainboard is understood and can be there are differences according to the data definition rule of redaction.How correctly discerning the data that data that legacy version comes synchronously and the data transaction how will come synchronously become redaction to understand is problems that exist at present.
Just because of the existence of the problems referred to above, the dynamic operation data are lost in escalation process in fact, can't guarantee in-service upgrade.Realize in-service upgrade, crucial technology is the stationary problem that solves dynamic data.
The application scenarios of existing active and standby plate dynamic data synchronization scenario is not the upgrading scene; but the scene that normal slave board shields; what this moment, mainboard and slave board moved all is identical software; in this software, the dynamic data on the active and standby plate is divided into one by one synchronizing data blocks according to function; each synchronizing data blocks all comprises the dynamic data of a certain identical function of some descriptions; the size of each synchronizing data blocks and content all may have nothing in common with each other; each synchronizing data blocks all has two-stage index to identify; the one, module id; the 2nd, the synchronization blocks sequence number in the module; module id shows which module is this synchronization blocks belong to; the synchronization blocks sequence number identifies the numbering of this synchronization blocks in this module, module No.+synchronizing data blocks of synchronization blocks sequence number unique identification.Because active and standby software is in full accord, so the number in active and standby plate upper module number and definition and synchronization blocks sequence number all is absolute consistent with definition, as long as mainboard sends to slave board with a synchronization blocks and carries module No.+synchronization blocks sequence number, slave board receives this synchronizing data blocks, with regard to this synchronization blocks of the unique identification of energy, slave board gets final product the relevant block that the synchronization blocks data that receive cover oneself according to module No.+synchronization blocks sequence number.As shown in Figure 1.
In the process of normal operation, if the dynamic data of mainboard changes, mainboard can send to slave board with the synchronizing data blocks at the dynamic data place of this variation, slave board covers the relevant block of oneself with its content after discerning this synchronizing data blocks, thereby reaches the purpose of the dynamic data of the synchronous mainboard of slave board.When mainboard breaks down, because software, configuration data and the dynamic data of slave board all are in full accord with mainboard, so masterslave switchover can interrupting service.
This synchronization scenario feasible before the make demands content of synchronization blocks of the sign of synchronization blocks of mainboard and slave board and like-identified in full accord, this can only could realize in same software version.So this scheme has only solved the synchronous problem of dynamic data under the on all four situation of active and standby software.Under the upgrading scene, because slave board software has been upgraded to new software in advance, the dynamic block number is compared with old software with content and is all had modification in the new software, adopt this synchronization blocks of identification that this synchronization scenario can't be correct this moment, and identification back content can not adopt the mode of covering, because the content of piece may be inconsistent in the new and old edition software, dynamic data is synchronized to slave board so this scheme can't be correct under the upgrading scene.
Summary of the invention
Embodiments of the invention provide a kind of method of data sync, to solve the problem of service disconnection in the escalation process.
Embodiments of the invention provide data synchronization method in a kind of non-interrupting service escalation process, comprising:
A, in new version software, be provided with legacy version software in identical data block number;
B, set up the transfer function of new version software and legacy version software data piece content conversion, above-mentioned transfer function is to be upgraded to redaction at the corresponding data block of data block numbering from legacy version; And when never updating apparatus is synchronized to updating apparatus, calls the data block of above-mentioned data and number pairing transfer function in data.
Embodiments of the invention by in new version software, be provided with old software version in identical data block number, solved that data block identifies conforming problem in the new and old edition software, and by in new version software, setting up the function of data block contents conversion, guaranteed that new version software can discern the content of the data block of coming synchronously, realize the stationary problem of data between different software versions, thereby realized the function of escalation process non-interrupting service, satisfied the active demand of operator.The application of in-service upgrade function will greatly improve the service quality and the operation reliability of operator.
Description of drawings
Fig. 1 is the schematic diagram of dynamic data method for synchronous in the prior art.
Fig. 2 is the method for data synchronization first embodiment schematic flow sheet of the embodiment of the invention.
Fig. 3 for first embodiment of the embodiment of the invention about new version software and legacy version software data block identification consistency schematic diagram are set.
Fig. 4 is that first embodiment of the embodiment of the invention is about data sync transfer function implementation procedure schematic diagram.
Fig. 5 is the method for data synchronization second embodiment schematic flow sheet of the embodiment of the invention.
Fig. 6 for second embodiment of the embodiment of the invention about new version software and legacy version software data block identification consistency schematic diagram are set.
Fig. 7 is that second embodiment of the embodiment of the invention is about data sync transfer function implementation procedure schematic diagram.
Fig. 8 be the embodiment of the invention about transfer function pointer chain list structure schematic diagram.
Embodiment
In order to make the purpose, technical solutions and advantages of the present invention clearer, below will the present invention program be described in more detail for embodiment and with reference to accompanying drawing.
With reference to figure 2, this figure is the first embodiment flow chart that does not interrupt method of data synchronization in the escalation process of the embodiment of the invention, and its main process is as follows:
Step 201: in new version software, be provided with legacy version software in identical dynamic data block number;
In new version software, be provided with legacy version software in identical dynamic data block number, guarantee that promptly the sign of same data block in the new version software is identical with sign in the legacy version software, on this basis, if newly-increased data block, its sign can only adopt newly-increased numbering, not influence the numbering of data block in the legacy version.With reference to figure 3, module M has N synchronizing data blocks among the software V1.0, the piece 1 among the module M among the piece 1 corresponding V1.0 among the module M in new version software V2.0 then, the piece N among the V2.0 among the corresponding V1.0 of piece N, if increase by a new synchronizing data blocks in the module M of V2.0, then it is numbered N+1.If the situation that block identification need reduce, as long as keep these numberings that do not re-use on block number, the function of removing the piece of minimizing on the function gets final product.
Step 202: set up the function of new version software and legacy version software dynamic data piece content conversion, and dynamic data is called this transfer function when never updating apparatus is synchronized to updating apparatus.
Be implemented as follows:
With reference to figure 4, this figure be the embodiment of the invention one about data sync transfer function implementation procedure schematic diagram, transfer function is realized is conversion from V1.0 to V2.0.Wherein, module M comprises N data block among the V1.0, and module M comprises N data block among the V2.0, and variation has taken place the content of piece 1 among the V2.0, being designated of piece 1: module M+ piece 1 need be changed its content with transfer function.This transfer function transforms to the content format of the piece 1 of V2.0 definition with the content format of piece 1, can understand with the application program that guarantees V2.0 software, the dynamic synchronization piece 1 of realizing module M from V1.0 to V2.0 synchronously.
This transfer function is specifically write and is articulated by the software developer of V2.0, this transfer function only is applicable to the conversion of the piece 1 among the module M, and only be useful in V1.0 to the conversion between the V2.0, promptly any one transfer function all is upgraded to particular version at one specific from particular version.The suction parameter of transfer function is the structure content of piece 1, the inner structure content that carries the piece 1 of V2.0 definition through the conversion outlet parameter of function.Function prototype can be defined as:
IntModule-M-Block-1-Convert-From-V1.0-To-V2.0 (V1.0 piece 1 structure * pBlock1, V2.0 piece 1 structure * pBlock2)
Parameter declaration: the synchronizing data blocks before the conversion of pBlock1 pointed, the synchronizing data blocks after the conversion of pBlock2 pointed.
The transfer function of the newly-increased synchronization blocks of redaction applies for that so newly a data structure is articulated in the pointer chained list of this synchronization blocks.With reference to figure 8, this figure is that the present invention is about transfer function pointer chain list structure schematic diagram.The pointer chained list of synchronization blocks adopts the mode of ordering, is convenient to like this carry out transfer function from front to back in order after slave board receives synchronizing data blocks.
Because the version before the upgrading is uncertain, on new version, articulate a transfer function from the version before upgrading to redaction for the vicissitudinous synchronization blocks of each content, the mode that adopts adjacent version to change one by one during conversion realizes, each version only need be considered and the data block transfer problem of a last adjacent legacy version.
The method that version is upgraded one by one is: all software versions sort according to the software version distribution order, V1.0-for example〉V2.0-〉V3.0-〉V4.0-〉V5.0-〉V6.0, do not settle at one go from Geju City edition upgrading to a redaction, upgrade up step by step according to the version order but adopt, transfer function neither directly call a transfer function from the legacy version to the redaction, but calls this synchronization blocks all transfer functions in the middle of these two upgraded versions in order.For example: after piece X is synchronized to V6.0 from V2.0, not the transfer function from V2.0 to V6.0 of direct invoking block X in the software of V6.0, but the transfer function of first invoking block X from V2.0 to V3.0 changed the synchronization blocks content that is converted to ... to the last the transfer function of invoking block X from V5.0 to V6.0 obtains the piece content that V6.0 can understand again through the transfer function of piece X from V3.0 to V4.0.If certain adjacent two version does not articulate transfer function (if piece X content does not change between adjacent two versions, these two versions just do not articulate transfer function) and then directly skips and continue to call next transfer function in the invoked procedure.
In the dynamic data piece synchronizing process, slave board receives the data block that mainboard is come synchronously, number find unique synchronization blocks corresponding on the slave board according to the module No.+synchronization blocks of carrying, thereby the transfer function chained list that finds this synchronization blocks to articulate, version number (old edition this shop) according to mainboard determines first function that is converted of transfer function chained list, begin to carry out one by one transfer function on the chained list until the end from this function in order then, last transfer function conversion finishes and just can obtain this synchronization blocks content on the new software version, new software can be correct understand this synchronization blocks, this content is sent to application module uses.
If the content of the data block corresponding with legacy version software does not change in the new version software, because new version software can be discerned the content of this piece, so, the data block contents that does not change that transfer function can be set to this; Can transfer function be set at this data block, just this transfer function does not carry out any conversion yet, and its implementation can realize the purpose of data sync as mentioned above equally.
With reference to figure 5, this figure is the second embodiment flow chart that does not interrupt method of data synchronization in the escalation process of the embodiment of the invention, and its main process is as follows:
Step 501: in new version software, be provided with legacy version software in identical dynamic data block number, guarantee that promptly the sign of same data block in the new version software is identical with sign in the legacy version software, on this basis, if newly-increased data block, its sign can only adopt newly-increased numbering, not influence the numbering of data block in the legacy version.With reference to figure 6, module M has N synchronizing data blocks among the software V1.0, the piece 1 among the module M among the piece 1 corresponding V1.0 among the module M in new version software V2.0 then, the piece N among the V2.0 among the corresponding V1.0 of piece N, if increase by a new synchronizing data blocks in the module M of V2.0, it is numbered N+1.If the situation that block identification need reduce, as long as keep these numberings that do not re-use on block number, the function of removing the piece of minimizing on the function gets final product.
Step 502: set up the function of new version software and legacy version software dynamic data piece content conversion, and dynamic data is called this transfer function when never updating apparatus is synchronized to updating apparatus.
Be implemented as follows:
With reference to figure 7, this figure be the embodiment of the invention two about data sync transfer function implementation procedure schematic diagram, transfer function is realized is conversion from V1.0 to V4.0.Wherein, module M comprises N data block among the V1.0, and module M comprises N data block among the V4.0, and variation has taken place the content of piece 1 among the V4.0, being designated of piece 1: module M+ piece 1, need change its content with transfer function.
After the piece among the module M 1 is synchronized to V4.0 from V1.0, variation has taken place in the content of if block 1, then the software of V4.0 must have a transfer function, the content format of piece 1 is transformed to the content format of the piece 1 of V4.0 definition by this transfer function, can understand with the application program that guarantees V4.0 software, the dynamic synchronization piece 1 of realizing module M from V1.0 to V4.0 synchronously.
This transfer function is specifically write and is articulated by the software developer of V4.0, this transfer function only is applicable to the conversion of the piece 1 among the module M, and only be useful in V1.0 to the conversion between the V4.0, promptly any one transfer function all is upgraded to particular version at one specific from particular version.The suction parameter of transfer function is the structure content of piece 1, the inner structure content that carries the piece 1 of V4.0 definition through the conversion outlet parameter of function.Function prototype can be defined as:
IntModule-M-Block-1-Convert-From-V1.0-To-V4.0 (V1.0 piece 1 structure * pBlock1, V4.0 piece 1 structure * pBlock4)
Parameter declaration: the synchronizing data blocks before the conversion of pBlock1 pointed, the synchronizing data blocks after the conversion of pBlock4 pointed.
The transfer function of the newly-increased synchronization blocks of redaction applies for that so newly a data structure is articulated in the pointer chained list of this synchronization blocks.With reference to figure 8, this figure is that the present invention is about transfer function pointer chain list structure schematic diagram.The pointer chained list of synchronization blocks adopts the mode of ordering, is convenient to like this carry out transfer function from front to back in order after slave board receives synchronizing data blocks.
Present embodiment is to articulate a transfer function from the version before upgrading to redaction for the vicissitudinous synchronization blocks of each content on new version, because the version before the upgrading is uncertain, not to adopt adjacent version to change one by one during actual converted, but be reference with former all legacy versions, corresponding each legacy version in the past of each synchronization blocks all articulates a transfer function, slave board does not need adjacent version to call transfer function one by one to the data that receive during data sync, but calls unique transfer function from the legacy version to the redaction.This scheme has improved the efficient of data sync, but redaction need consider to compare with the legacy version before all situation of change of synchronizing data blocks when developing.
In the dynamic data piece synchronizing process, slave board receives the data block that mainboard is come synchronously, number find unique synchronization blocks corresponding on the slave board according to the module No.+synchronization blocks of carrying, thereby the transfer function chained list that finds this synchronization blocks to articulate, version number (old edition this shop) according to mainboard determines the transfer function chained list, find legacy version to arrive the directly function of conversion of redaction, just can obtain this synchronization blocks content on the new software version, new software can be correct understand this synchronization blocks, this content is sent to application module uses.
Embodiments of the invention by in new version software, be provided with old software version in identical data block number, solved that data block identifies conforming problem in the new and old edition software, and by in new version software, setting up the function of data block contents conversion, guaranteed that new version software can discern the content of the data block of coming synchronously, realize the stationary problem of data between different software versions, thereby realized the function of escalation process non-interrupting service, satisfied the active demand of operator.The application of in-service upgrade function will greatly improve the service quality and the operation reliability of operator.
If the content of the data block corresponding with legacy version software does not change in the new version software, because new version software can be discerned the content of this piece, so, the data block contents that does not change that transfer function can be set to this; Can transfer function be set at this data block, just this transfer function does not carry out any conversion yet, and its implementation can realize the purpose of data sync as mentioned above equally.
Obviously, those skilled in the art can carry out various changes and modification to the present invention and not break away from the spirit and scope of the present invention.Like this, if of the present invention these are revised and modification belongs within the scope of claim of the present invention and equivalent technologies thereof, then the present invention also is intended to comprise these changes and modification interior.
Claims (9)
1. the method for a data sync is used for non-interrupting service escalation process data synchronization, it is characterized in that:
A, in new version software, be provided with legacy version software in identical data block number;
B, set up the transfer function of new version software and legacy version software data piece content conversion, described transfer function is to be upgraded to redaction at the corresponding data block of data block numbering from legacy version; And when never updating apparatus is synchronized to updating apparatus, calls the data block of described data and number pairing transfer function in data.
2. method according to claim 1 is characterized in that, described steps A further comprises: when increasing new data block in new version software, keep existing data block numbering, newly-increased numbering is set up on the basis of existing numbering.
3. method according to claim 1 is characterized in that, described step B further comprises: the described transfer function that calls is realized the conversion of same data block contents in new version software and the legacy version software.
4. method according to claim 3 is characterized in that, described step B further comprises: the described transfer function that calls to the conversion of data block contents at be an individual data piece.
5. method according to claim 1, its special this be that described step B further comprises: the described transfer function that calls to the conversion of data block contents at be the vicissitudinous data block of content.
6. method according to claim 1 or 5, it is characterized in that described step B further comprises: the described transfer function that calls is to change step by step according to the software version order to the conversion of data block contents.
7. method according to claim 1 or 5, it is characterized in that described step B further comprises: the described transfer function that calls is directly to be transformed into new version software from legacy version software to the conversion of data block contents.
8. method according to claim 1 or 5 is characterized in that described step B further comprises: when transfer function is set, described transfer function is articulated in the pointer chained list of this transfer function institute data converted piece.
9. method according to claim 1 or 5 is characterized in that described step B further comprises:
When described transfer function was changed, the suction parameter of this transfer function was the structure content of legacy version software institute translation data piece, carried the structure content of institute's translation data piece of new version software definition in the outlet parameter.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2006101572408A CN100461704C (en) | 2006-12-02 | 2006-12-02 | Data synchronizing method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2006101572408A CN100461704C (en) | 2006-12-02 | 2006-12-02 | Data synchronizing method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1976301A CN1976301A (en) | 2007-06-06 |
| CN100461704C true CN100461704C (en) | 2009-02-11 |
Family
ID=38126109
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNB2006101572408A Active CN100461704C (en) | 2006-12-02 | 2006-12-02 | Data synchronizing method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN100461704C (en) |
Families Citing this family (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101256607B (en) * | 2008-03-10 | 2011-08-10 | 北京深思洛克软件技术股份有限公司 | Method for remote updating and controlling use of software protection apparatus |
| US9357554B2 (en) | 2009-03-11 | 2016-05-31 | Huawei Technologies Co., Ltd. | Method and apparatus for coexistence of multiple operating entity systems |
| CN102681863A (en) * | 2011-03-15 | 2012-09-19 | 新奥特（北京）视频技术有限公司 | Method for automatically upgrading data based on command mode |
| JP6217034B2 (en) | 2013-07-31 | 2017-10-25 | 華為技術有限公司Ｈｕａｗｅｉ Ｔｅｃｈｎｏｌｏｇｉｅｓ Ｃｏ．，Ｌｔｄ． | Related plug-in management method, apparatus and system |
| CN106649814A (en) * | 2016-12-29 | 2017-05-10 | 国网江苏省电力公司南京供电公司 | Method for consistency checking of distribution automation cross-domain database |
| CN108769260B (en) * | 2018-06-29 | 2020-10-16 | 苏州浪潮智能科技有限公司 | Event processing method and device in cluster upgrading process |
| CN110321620B (en) * | 2019-06-26 | 2023-07-21 | 浙江杭加泽通建筑节能新材料有限公司 | Design construction method of assembled house building |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6341291B1 (en) * | 1998-09-28 | 2002-01-22 | Bentley Systems, Inc. | System for collaborative engineering using component and file-oriented tools |
| WO2002077862A1 (en) * | 2001-03-27 | 2002-10-03 | British Telecommunications Public Limited Company | File synchronisation |
| US20030177408A1 (en) * | 2001-04-06 | 2003-09-18 | Patientkeeper, Inc. | Synchronizing data between disparate schemas using composite version |
| US6671701B1 (en) * | 2000-06-05 | 2003-12-30 | Bentley Systems, Incorporated | System and method to maintain real-time synchronization of data in different formats |
| CN1801087A (en) * | 2004-12-31 | 2006-07-12 | 英业达股份有限公司 | Synchronous updating system and method for data and application |
| CN1851657A (en) * | 2005-07-21 | 2006-10-25 | 上海华为技术有限公司 | Dual-machine back-up realizing method and system |
| CN1866252A (en) * | 2006-02-20 | 2006-11-22 | 华为技术有限公司 | Method and system for transformation between different version configuration data |
-
2006
- 2006-12-02 CN CNB2006101572408A patent/CN100461704C/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6341291B1 (en) * | 1998-09-28 | 2002-01-22 | Bentley Systems, Inc. | System for collaborative engineering using component and file-oriented tools |
| US6671701B1 (en) * | 2000-06-05 | 2003-12-30 | Bentley Systems, Incorporated | System and method to maintain real-time synchronization of data in different formats |
| WO2002077862A1 (en) * | 2001-03-27 | 2002-10-03 | British Telecommunications Public Limited Company | File synchronisation |
| US20030177408A1 (en) * | 2001-04-06 | 2003-09-18 | Patientkeeper, Inc. | Synchronizing data between disparate schemas using composite version |
| CN1801087A (en) * | 2004-12-31 | 2006-07-12 | 英业达股份有限公司 | Synchronous updating system and method for data and application |
| CN1851657A (en) * | 2005-07-21 | 2006-10-25 | 上海华为技术有限公司 | Dual-machine back-up realizing method and system |
| CN1866252A (en) * | 2006-02-20 | 2006-11-22 | 华为技术有限公司 | Method and system for transformation between different version configuration data |
Also Published As
| Publication number | Publication date |
|---|---|
| CN1976301A (en) | 2007-06-06 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN100461704C (en) | Data synchronizing method | |
| CN100471134C (en) | Method, device for upgrading telecommunication equipment and upgrading engine unit | |
| CN101827302B (en) | Processing method and unified service platform are unified in multi-service | |
| CN110427204B (en) | Automatic gray level release method based on container and service grid technology | |
| CN102866925B (en) | Communication method and system for middleware and user interface | |
| CN101631345B (en) | Method and device for monitoring running state of single plate | |
| CN101600010A (en) | Sharing method of mobile phone interface configuration | |
| CN1617600A (en) | Data disaster tolerance method for attaching location registor | |
| CN100461646C (en) | Method for negat main spare board in communication equipment | |
| CN101499931B (en) | Function expansion method and system based on distributed environment | |
| CN101079676B (en) | An upgrade method of optical synchronization digital transmission network system | |
| CN102905000A (en) | Address book synchronization method and device | |
| CN109787789B (en) | Compatibility management method, device and equipment for software upgrading and storage medium | |
| CN102591684A (en) | Software updating method | |
| CN103259639B (en) | A kind of clock synchronizing method of stack equipment and equipment | |
| JPS5851339A (en) | Control information control system | |
| CN103888283A (en) | SCTP communication method and device | |
| CN115757612A (en) | Data synchronization method and device, computer equipment and storage medium | |
| CN101764713B (en) | Engine method of rule configuration for peripheral interfaces of convergent billing system | |
| CN113886105B (en) | Cross-process calling method and device, storage medium and electronic equipment | |
| CN101626431A (en) | Processing method and processing system capable of adapting to communication mode | |
| CN106685975B (en) | Cascade control method of audio conference equipment | |
| CN108880779A (en) | A kind of text synchronous method based on redis message informing | |
| CN205061206U (en) | Synchronous elevator mainboard of information cloud | |
| CN1333311C (en) | System and method for automatically processing data esp. in field of prodn. assembly, service or maintenance |
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 |