CN102902812A - Method for realizing remote synchronization of database - Google Patents

Abstract

The invention discloses a method for realizing remote synchronization of a database, which belongs to the field of information processing. The method includes: the first database generates a digest based on the received order information and transmits it to the second database through the network, realizing real-time synchronization with the order information of the second database; and the second database updates the order information according to the received order number and logistics number The included content is generated according to the updated order information and the abstract is transmitted to the first database through the network, so as to realize real-time synchronization with the content of the updated order information of the first database. By adopting the method proposed by the invention, the risk brought by the remote data synchronization process can be effectively avoided, and at the same time, no omission of data synchronization can be guaranteed.

Description

A Realization Method of Remote Synchronization of Database

technical field

The invention relates to the field of information processing, in particular to a method for realizing remote synchronization of databases.

Background technique

In daily life, people need to create the same information on different terminal devices. The above-mentioned terminal devices are generally computers. Now the commonly used method is to realize remote synchronization of information on different terminals through the network. However, there is a risk of data being maliciously tampered with in the process of remote data synchronization on the network, and the impact of data security may cause heavy losses to users. If this phenomenon occurs, it is easy to cause the workflow corresponding to the two servers to not correspond, directly causing economic losses. In order to solve the security problem of remote data synchronization, the inventor proposes an implementation method to ensure the security of remote data synchronization.

Contents of the invention

In order to solve the risk problem existing in the data synchronization process in the prior art, the present invention proposes a method for implementing remote database synchronization.

The technical scheme adopted by the present invention is: a method for realizing remote synchronization of databases, comprising

Execute steps S1 to S4 when the first database receives the order information;

Step S1: The first database saves the received order information in the order information table, generates the first abstract according to the first key and the basic user information contained in the order information in the order information table, and sends the second abstract to the second database - request data;

Step S2: The second database obtains the order information and the first abstract from the received first request data, and generates a second Abstract;

Step S3: The second database compares whether the first abstract is consistent with the second abstract, and if yes, executes the next step; otherwise, returns a request response containing an error code to the first database;

Step S4: The second database saves the obtained order information into an official list, and sends a request response containing a synchronization success code to the first database;

Step S5 is also included after the step S4: the second database saves the product serial number for the product serial number field contained in the order information in the official list;

When the second database receives the logistics number and the order number, execute steps S6 to S11;

Step S6: The second database saves the received logistics number and order number in a temporary list, and finds the corresponding order information from the official list according to the order number;

Step S7: The second database generates a third abstract according to the second key, the basic user information contained in the found order information, the product serial number, and the logistics number in the temporary list, and sends the third abstract to the second database. A database sends the second request data;

Step S8: The first database obtains the order information, the logistics number and the third abstract from the received second request data, and according to the first key, the logistics number, and the user information contained in the order information Basic information and product serial number to generate the fourth abstract;

Step S9: The first database compares whether the third abstract is consistent with the fourth abstract, and if yes, executes the next step; otherwise, sends a request response containing an error code to the second database;

Step S10: the first database saves the logistics number for the logistics number field of the order information in the order information table, and sends a request response containing a synchronization success code to the second database;

Step S11: the second database saves the logistics number in the logistics number field contained in the order information in the official list, and deletes the order information in the temporary list.

The above order information includes user basic information, order number, product model field, product serial number field and logistics number field, and the product serial number field and logistics number field are initially empty.

The above-mentioned first key and the second key are session keys pre-negotiated between the first database and the second database. Or: the first database and the second database pre-store the negotiation key file named according to the time, and the step S1 also includes that the first database reads the current system time, reads the current system time according to the current system time Corresponding negotiation key file, obtaining the first key from the negotiation key file, the step S2 also includes, the second database reads the current system time, and reads the corresponding negotiation key according to the current system time file, and obtain the second key from the negotiated key file.

In step S1, the first database generates the first abstract according to the first key and the basic user information contained in the order information in the order information table, specifically: the first database combines the basic user information in the order information with the The first key is spliced into a data string in a pre-agreed order, and a pre-agreed algorithm is used to encrypt the data string to generate a first digest;

The generating of the second abstract according to the second key and the acquired basic user information contained in the order information in step S2 is specifically: the user basic information and the second key in the order information are arranged in a pre-agreed order splicing into a data string, and encrypting the data string with a pre-agreed algorithm to generate a second digest.

The step S2 also includes the process of the second database verifying the validity of the order information obtained from the first request data, and the step S8 further includes the first database verifying the validity of the order information obtained from the first request data. 2. The process of requesting the validity of the order information acquired in the data; the process of verifying the validity of the order information is specifically verifying whether the format and content of the order information are valid.

The step S5 is specifically, the second database searches for the best matching product in the product library according to the product model field requirement contained in the order information, and saves the value of the product serial number field in the retrieved product record to the product serial number field of the order information.

The step S5 includes, the second database creates a first job, creates a trigger and sets trigger parameters, sets a scheduling start time and a scheduling interval time, and starts the task scheduler to schedule when the monitoring system time reaches the scheduling start time The job created, and the scheduling start time is increased by the scheduling interval; the first job created is: automatically traverse all the order information in the official list, and search for eligible products in the product library according to the product model field requirements of the order information Optimally matching the product record, saving the value of the product serial number field in the product record to the product serial number field of the order information.

The step S6 includes, the second database searches the official list for whether the received order number exists, if yes, saves the received logistics number and order number as a record in the temporary list, otherwise it does not save.

Or the step S6 includes that the second database creates a second job and a third job, creates a trigger and sets trigger parameters, sets the second scheduling start time, the third scheduling starting time and the scheduling interval time, when monitoring When the system time reaches the second scheduling start time, start the task scheduler to schedule the created second job, and add the second scheduling start time to the scheduling interval time; when it is detected that the system time reaches the third scheduling start time, start The task scheduler schedules the creation of the third job, and increases the second scheduling start time by the scheduling interval; the second job is to download the official list of order information to the designated storage space, and the third job is , to obtain a temporary list for storing order numbers and logistics numbers from the specified storage space.

After sending the request response containing the successful code to the first database in step S4 includes, after the first database receives the request response, marking the order information as valid.

The step S11 may be replaced by: the second database saves the logistics number in the logistics number field contained in the order information in the official list, and marks the order information in the temporary list as processed. The method of the present invention further includes, when the system time reaches the preset time, starting the task scheduler to schedule a fourth operation, the fourth operation is: retrieving and deleting the order information marked as processed in the temporary table.

In the step S4, when the second database receives the order information to be updated, it includes saving the order information to be updated in the official list, and the product serial number field in the order information to be updated includes the old The product serial number field and the new product serial number field; the step S5 is specifically, saving the new product serial number for the product serial number field of the order information to be updated in the official list, which will be included in the updated order information The product serial number is stored in the old product serial number field of the order information to be updated.

In step S7, the second database generates a third abstract according to the second key, the basic user information contained in the found order information, the product serial number, and the logistics number in the temporary list. Specifically, the second The database splices the basic user information and product serial number in the order information, the logistics number in the temporary list, and the second key into a data string in a pre-agreed order, and uses the pre-agreed The algorithm generates the third abstract;

In step S8, the generation of the fourth abstract according to the first key, the logistics number, the basic user information contained in the order information and the product serial number is specifically, the first database stores the basic user information contained in the order information The information and product serial number, the logistics number, and the first key are spliced into a data string in a pre-agreed order, and a pre-agreed algorithm is used to encrypt the data string to generate a fourth digest.

The beneficial effects of the present invention are: adopting the method proposed by the present invention can effectively avoid the risks brought by the remote data synchronization process, and at the same time ensure that data synchronization is not missed: 1) Real-time trigger interface is used to ensure instant data synchronization, and data is scanned regularly 2) It can detect whether the data has been tampered with in the process of data transmission; 3) The source of the data generated by the abstract in the network transmission is not clear is also the feature of the security guarantee of this method.

Description of drawings

Fig. 1 is a flow chart of a method for realizing remote synchronization of a database provided in Embodiment 1;

Fig. 2 is a data synchronization flowchart of one of the databases provided in Embodiment 2;

FIG. 3 is a flow chart of updating order information provided by Embodiment 3. FIG.

Detailed ways

The following will clearly and completely describe the technical solutions in the embodiments of the present invention with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only some, not all, embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by persons of ordinary skill in the art without making creative efforts belong to the protection scope of the present invention.

The implementation method of database remote synchronization in the embodiment of the present invention is described in detail by taking the remote synchronization of order information in the database as an example.

Example 1

A method for realizing remote synchronization of databases provided in this embodiment can realize real-time synchronization of order information of the first database and the second database, as shown in FIG. 1 , including the following steps:

Step 1: the first database receives the order information applied by the user;

Specifically, the order information includes user basic information, order number, product model field, product serial number field, and logistics number field. The product serial number field and logistics number field are initially empty, and the first database will receive Save the order information to the order information table.

In this embodiment, before the first database receives the order information requested by the user, the first database negotiates with the second database to generate a pair of session keys, that is, the first key and the second key, and the first database stores the second session key. a key, and the second database stores the second key.

Step 2: the first database generates the first abstract according to the first key and the basic user information in the order information;

Specifically: splicing the basic user information and the first key in the order information into a data string in a pre-agreed order, and encrypting the data string with a pre-agreed algorithm to generate the first digest.

In this embodiment, the basic user information in the order information specifically includes consignee name, address, phone number and other information.

Preferably, the basic user information in the order information and the first key are sequentially spliced into a data string, and the MD5 algorithm is used to calculate the data string to obtain the first digest. In addition, the SHA1 algorithm can also be used to encrypt the data string to generate the first digest, so as to achieve the purpose of protecting the transmitted synchronous data.

Step 3: The first database packages the order information and the first abstract into first request data and sends it to the second database.

Specifically, the mutual calling between the first database and the second database adopts a URL request path. In this embodiment, preferably, the order information and the first abstract are packaged as URL first request data and sent to the second database.

Step 4: The second database receives the first request data to obtain the order information and the first abstract, and generates the second abstract according to the second key and the basic user information in the order information;

Specifically, the second database receives the first URL request data, reads the order information and the first abstract from it, and splices the basic user information and the second key in the order information into a data string in a pre-agreed order, using A pre-agreed algorithm encrypts the data string to generate a second digest. Preferably, the order information and the second key are sequentially spliced into a data string, and the MD5 algorithm is used to calculate the data string to obtain the second digest. In addition, the SHA1 algorithm can also be used to encrypt the data string to generate the second digest, so as to achieve the purpose of protecting the transmitted synchronous data.

Preferably, it is also possible to set the first database and the second database to renegotiate the key at a certain time interval, for example, the interval is 1 month, and the specific implementation method is: pre-store some negotiation key files in the first database and the second database , the file name of the negotiated key file is represented by the month, step 2 also includes that the first database reads the current system time, reads the negotiated key file of the corresponding month according to the current system time, and obtains the first key from the file, Corresponding step 4 also includes that the second database reads the current system time, reads the negotiation key file of the corresponding month according to the current system time, and obtains the second key from the file.

Further, step 4 in this embodiment may also specifically be the following steps:

Step 4-1: The second database verifies the validity of the order information in the first URL request data, if valid, proceed to step 4-2, otherwise execute step 4-3;

Specifically in this embodiment, verifying the validity of the order information in the first request data of the URL is specifically verifying whether the format and content of the order information are valid, for example, verifying whether the user name contained in the order information conforms to the preset format, verifying Whether the length of the mobile phone number included in the order information is valid.

Step 4-2: The second database receives the order information in the first URL request data, splices the basic user information in the order information and the second key into a data string according to the pre-agreed order, and uses this data string to adopt the pre-agreed The algorithm produces the second digest.

Step 4-3: The second database returns a request response Response to the first database. Response encapsulates the error code of data validity verification failure, and skips to step 1.

For example, error code 2000017 indicates that the product model parameter is missing.

Step 5: The second database compares whether the second abstract is consistent with the first abstract, if yes, execute step 7, otherwise execute step 6;

Step 6: The second database returns a request response Response including an error code to the first database. Response encapsulates the error code of data synchronization verification failure, and then returns to step 1;

For example, error code 2000000 indicates that the signature verification digest failed.

Step 7: the second database saves the order information in the URL request data to the official list;

Step 8: the second database sends a request response containing a synchronization success code to the first database;

Specifically, in this embodiment, after the second database finishes saving the order information, it returns a request response Response to the first database, and the Response encapsulates a code indicating that the data synchronization is successful. So far, the first database and the second database have completed the data synchronization of the user's basic information in the order information.

Step 9: After receiving the successful Response message from the second database, the first database marks the order information as valid.

Step 10: the second database saves the product serial number for the product serial number field of the order information in the official list;

Specifically, the second database traverses all the order information in the official list, searches for the best matching product in the product library according to the product model field requirements in the order information, and if it is retrieved, the product sequence in the retrieved product record No. field value is stored in the serial number field of the order information; if not retrieved, the second database sends out a reminder that the product serial number failed to be saved.

Preferably, the quartz scheduler can also be used to implement task scheduling, set the start time of scheduling and the interval of scheduling, such as an interval of 24 hours, the specific implementation method is: create a quartz job, create a trigger and set the parameters of the trigger, set Scheduling start time and scheduling interval time, for example, set the scheduling start time to am8:00, set the scheduling interval time to 12 hours, when the monitoring system time reaches the scheduling start time, start the quartz job created by the quartz scheduler and schedule The scheduling start time is added to the interval time as the next scheduling start time. The quartz job created in this embodiment is specifically: automatically traverse all order information in the official list, search for the best matching product record that meets the conditions in the product library according to the product model field requirements of the order information, and insert the product serial number field in the product record The value is saved to the Product Serial Number field in this order message.

The supporting priority scheme also uses quartz task scheduling for unsold (matched) inventory warnings in the product library, that is, creating multiple quartz jobs. The quartz job also includes: the second database queries the remaining inventory in the inventory table. When retrieving When the out-of-stock quantity is less than the preset value, an email and SMS reminder will be sent to the product center personnel.

Step 11: The second database receives the logistics number and order number input by the product delivery personnel and saves them in the temporary list;

Specifically, the second database receives the logistics number and order number input by the product delivery personnel, and searches through the order number to see if there is such an order number in the official list of order information, and if so, the logistics number and order number entered by the product delivery personnel Save it to the temporary list; if there is no such order number in the official list of order information, continue to receive the next order number and logistics number entered by the product delivery personnel.

Specifically, in this embodiment, the product dispatcher is an order operator who logs into the current system, that is, the second database, so the system obtains the logistics number under the condition that the order operator logs in. The order number of each record stored in the temporary list also ensures that there is a corresponding order number in the official list.

Furthermore, it is also possible to set the second database to use quartz task scheduling to realize that the second database regularly downloads the order information to the mailbox or other storage space of the product delivery personnel every day. The specific implementation method is the same as that described in step 10, except that this The quartz job created and called in the step is to download the order information to the mailbox or other storage space of the product delivery personnel.

Furthermore, the product delivery personnel do not need to log in to the system, but only save the logistics number and order number of each order in the mailbox or other storage space, and the second database uses quartz task scheduling to set the start time of scheduling and the scheduling interval , such as at an interval of 24 hours, the second database reads all logistics numbers and corresponding order numbers from the mailbox or other storage space of the product delivery personnel regularly every day, and the second database uses the order number to search whether there is such an order number in the official list of order information , if there is, save the read logistics number and order number in the temporary list, if the order number is not retrieved in the official list of order information, it will not be saved. The creation process of the quartz task scheduler is the same as that described in step 10. The created job can be invoked regularly through the quartz task scheduler. For example, the second database can automatically download the order information to the mailbox specified by the product delivery person or The storage space automatically obtains the order number and corresponding logistics number from the designated mailbox or storage space every night at 8 o'clock. In this way, product delivery personnel can obtain the order list without logging in to the system. After binding the logistics number to the order information, there is no need to log in to the system to import the logistics number. The system can automatically obtain the logistics number, saving manual login. Operation steps.

Step 12: The second database queries the corresponding order information from the official list according to the order number in the temporary list.

Specifically, the second database retrieves the same order number in the official list according to the order number in the temporary list, and uses the order information corresponding to the order number as the found order information.

In this step, the second database may regularly obtain the temporary list records, extract the logistics number and order number from them, and query the order information from the official list according to the order number.

Specifically, the timing of this step is realized through quartz task scheduling. The specific process is the same as that described in step 10. The difference is that in this step, the interval time is set to 24 hours, and the quartz job created and called is: obtain the temporary list record, extract from it Logistics number and order number, and query the order information from the official list according to the order number.

This step includes two methods of instant and timing. Immediately can ensure that the logistics number is obtained at the first time and then synchronized to the first database in time, and timing can ensure that after obtaining the logistics number, it can be synchronized to the first database without omission.

Step 13: The second database generates a third abstract according to the basic user information and product serial number in the order information, the logistics number in the temporary list, and the second key;

Specifically, the user's basic information, product serial number, logistics number and second key in the order information are spliced into a data string in a pre-agreed order, and a pre-agreed algorithm is used to generate a third abstract for this data string.

Preferably in this embodiment, the basic information of the user, the product serial number, the logistics number and the second key in the order information are sequentially spliced into a data string, and the data string is calculated using MD5 to generate a third abstract, which can also be combined with the first A database pre-agrees to use other algorithms, such as SHA1 and other algorithms.

Step 14: The second database encapsulates the order information, logistics number and third abstract into second request data and sends it to the first database;

Specifically, the second database encapsulates the order information, the logistics number and the third abstract into URL second request data and sends it to the first database.

Step 15: The first database receives the second request data, obtains the order information, logistics number and third abstract from it, and generates the fourth Abstract;

Specifically, the first database receives the second URL request data, reads the order information, logistics number and third abstract from it, and stores the basic user information, product serial number, logistics number and first key in the order information in advance The agreed sequence is spliced into a data string, and a pre-agreed algorithm is used to encrypt the data string to generate the fourth digest. Preferably, the basic user information in the order information, the product serial number, the logistics number and the first key are spliced into a data string in sequence, and the data string is calculated using the MD5 algorithm to obtain the fourth digest.

Specifically, in this embodiment, step 15 also includes verifying the validity of the order information obtained from the second request data of the URL, and the specific verification process is the same as step 4, and will not be repeated here.

Step 16: The first database compares whether the fourth abstract is consistent with the third abstract, if yes, execute step 18, otherwise execute step 17;

Step 17: The first database sends a request response containing an error code to the second database; jump to step 12;

Specifically: the first database returns a request response Response to the second database, and the Response encapsulates the error code of data synchronization failure; then returns to step 12;

Preferably, a counter can also be set to record the number of synchronization failures. When an order fails to synchronize data for 3 consecutive times, an email or SMS reminder will be sent to the designated maintenance personnel.

The specific counter is to save 1 to the identification field of this order after a synchronization failure once, update 2 to the identification field of this order after another synchronization failure, and send an email or SMS reminder after updating to 3 in turn.

Step 18: The first database saves the logistics number in the logistics number field of the order information, and updates the order information to the order information table;

Step 19: the first database sends a request response containing a synchronization success code to the second database;

Specifically, the first database sends a request response Response to the second database, and the Response encapsulates the code of successful data synchronization; so far, the first database and the second database complete the synchronization of logistics numbers. Users can activate and use the product.

Step 20: the second database stores the logistics number in the logistics number field of the order information in the official list;

Preferably, it is also possible to set the second database to use quartz task scheduling, set the start time of scheduling and the interval of scheduling, such as an interval of 24 hours, to realize whether the official list of order information retrieved by the second database every day has exceeded the predetermined number of days and has not yet been bound. Order information with a specified logistics number. When the existence of order information that meets the conditions is detected, the email or mobile phone of the designated product delivery personnel will be reminded to deliver the goods.

Step 21: the second database marks the order information in the temporary list as processed;

Step 22: The second database periodically clears the order information marked as processed in the temporary list.

Specifically, this step is implemented through quartz task scheduling, and the specific process is the same as that described in step 10. The difference is that in this step, the interval time is set to 24 hours, and the quartz job created and called is: retrieve the order marked as already in the temporary table Processed order information records, delete them.

Example 2

As shown in Figure 2, on the basis of Embodiment 1, the operation performed by the second database in the data synchronization process is taken as an example to describe in detail, as follows:

Step 201: Receive the first request data and obtain the order information and the first abstract therefrom;

例如，接收到的第一请求数据为URL请求数据，具体为：http://IP:port/application/notify?address=101103&amount=1024&area=lufu&buyer_alias=eb25cf0249971db8cf57c683efe1e5c2&city=sheng&country=china&input_charset=GBK&invoice_title=galenzhang&invoice_type=nornal&need_invoice=1&out_trade_no =20000005012011102498749808&partner=2000000501&phone=0755-12345667&product_model=10001&prov=guang&recv_name=zhang&sign=E10ADC3949BA59ABBE56E057F20F883E&transaction_id=1212419701201112210078541998&zip_code=Ty%23%2Bs%2B

The first abstract contained in it is: E10ADC3949BA59ABBE56E057F20F883E, and the basic user information contained in the order information includes the recipient's country, recipient's address, recipient's phone number, etc.

Step 202: Determine whether the order information is valid, if yes, execute the next step, otherwise return to execute step 201;

In this embodiment, judging whether the order information is valid is specifically verifying whether the format and/or content of the order information is valid, for example, verifying whether the user name contained in the order information conforms to the preset format, and verifying the mobile phone number contained in the order information length is valid.

Step 203: Generate a second digest according to the pre-stored second key and the basic user information in the order information;

Specifically: splice the basic user information and the second key in the order information into a data string, and use the MD5 algorithm to encrypt the data string to generate a second digest; the second key is pre-negotiated with the synchronization database session key.

Specifically, in this embodiment, the generated second abstract is: E10ADC3949BA59ABBE56E057F20F883E.

Step 204: Check whether the second abstract is consistent with the first abstract, if yes, execute the next step, otherwise return to step 201;

Step 205: Save the order information to the official list and send a reminder of successful saving to the synchronization database;

For example, the packet format of a successfully saved reminder is:

Step 206: matching products to order information according to pre-agreed rules;

Specifically, in this embodiment, products are matched to the order information according to the distribution identifier and label size of the product, and the pre-agreed rule is to preferentially select products with an unallocated distribution identifier and a smaller label for order information allocation.

Preferably, it is also possible to regularly monitor whether there are enough products for matching. The implementation method is: create a quartz job, create a trigger and set the parameters of the trigger, set the scheduling start time and scheduling interval, for example, set the scheduling start time to am7 :00, set the scheduling interval to 24 hours. When the monitoring system time reaches the scheduling start time, start the quartz scheduler to schedule the created quartz job, and add the scheduling start time to the interval as the next scheduling start time. The quartz job created in this embodiment is specifically: when it is detected that the number of products available for matching is less than the preset number, send a reminder email to the designated employee mailbox or send a mobile phone SMS reminder. This ensures data continuity.

Step 207: Save the product serial number for the product serial number field in the order information in the official list;

Specifically, the second database traverses all the order information in the official list, searches for the best matching product that meets the conditions in the product library according to the product model field requirements contained in the order information, and if retrieved, the product corresponding to the retrieved product The serial number is saved in the serial number field of the order information. If it is not retrieved, a reminder of failure to save the product serial number will be sent out.

Step 208: Receive the logistics number and order number bound to the order information input by the product delivery personnel, and save them in the temporary list;

Step 209: Obtain the temporary list, extract the logistics number and order number from it, and query the corresponding order information from the official list according to the order number;

Step 210: Generate a third abstract according to the basic user information and product serial number in the order information, logistics number, and second key;

Specifically, in this embodiment, the basic user information in the order information, the product serial number, the logistics number, and the second key are sequentially spliced into a data string, and the pre-agreed MD5 algorithm is used to encrypt the data string to generate a third digest .

Step 211: Encapsulate the order information, logistics number and third abstract into the second request data and send it to the synchronization database;

例如，向同步数据库发送的第二请求数据为：http://IP:port/application/notify?address=101103&amount=1024&area=lufu&buyer_alias=eb25cf0249971db8cf57c683efe1e5c2&city=sheng&country=china&input_charset=GBK&invoice_title=galenzhang&invoice_type=nornal&need_invoice=1&out_trade_no=20000005012011102498749808&partner=2000000501&phone =0755-12345667&product_model=10001&prov=guang&recv_name=zhang&old_product_isn=1090123123&product_isn=1090123187&product_sn=FT010983&express_co=6168785922&sign=BC9ADBN7809W39A456ERE057F20MN89E&transaction_id=1212419701201112210078541998&zip_code=Ty%23%2Bs%2B

The third abstract contained therein is: BC9ADBN7809W39A456ERE057F20MN89E.

The logistics number included is: 6168785922.

Step 212: waiting to receive the response returned by the synchronization database;

Step 213: Judging whether the received response contains a synchronization success code, if yes, execute the next step, otherwise return to execute step 209;

The received response containing the sync success code is:

Step 214: Save the logistics number in the logistics number field in the order information in the official list;

Step 215: mark the order information as processed in the temporary list;

Step 216: Periodically clear the order information marked as processed in the temporary list.

Example 3

On the basis of Embodiment 1 or 2, further, the product serial number field in the order information specifically includes an old product serial number field and a new product serial number field. When there is an order to be updated, in the case of ensuring data synchronization, as shown in Figure 3, the update order operation performed by the second database is as follows:

Step 301: Receive the order information to be updated and save it in the official list;

Specifically in this embodiment, the updated order information is imported into the official list by the user when there is an order that needs to be updated.

Step 302: saving the new product serial number for the product serial number field of the order information to be updated in the official list;

Specifically, in the official list, according to the requirements of the product model field included in the updated order information, search for the best matching product that meets the conditions in the product library, and save the serial number corresponding to the product in the new product serial number field of the order information.

Step 303: saving the product serial number contained in the original order information in the field of the old product serial number of the order information to be updated in the official list;

Step 304: Receive the logistics number and order number input by the user for the order information to be updated and store them in a temporary list.

In this embodiment, specifically, when there is an order that needs to be updated, the second database first receives the order information to be updated, and sends it to the first database to realize the synchronization of the basic user information in the order information. The synchronization of the product serial number and the logistics number is the same as in embodiment 1 or 2, and will not be repeated here.

The above is only a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Anyone skilled in the art can easily think of changes or substitutions within the technical scope disclosed in the present invention. Should be covered within the protection scope of the present invention. Therefore, the protection scope of the present invention should be based on the protection scope of the claims.

Claims (15)

1. the implementation method that data-base remote is synchronous is characterized in that: comprise

Execution in step S1 is to step S4 when the first database receives sequence information;

Step S1: the first database is saved to the sequence information table with the sequence information that receives, and generates the first digest according to the user basic information that comprises in the sequence information in the first key and the described sequence information table, and sends the first request msg to the second database;

Step S2: described the second database obtains sequence information and the first digest from described the first request msg that receives, and generates the second digest according to the user basic information that comprises in the second key and the described sequence information that gets access to;

Step S3: whether described the second database is compared described the first digest consistent with described the second digest, is then to carry out next step, otherwise return the request response that comprises error code to described the first database;

Step S4: the described sequence information that described the second database will get access to is saved in the formal tabulation, and sends the request response that comprises synchronous success coding to described the first database;

Also comprise step S5 after the described step S4: described the second database is preserved product ID for the product ID field that comprises in the sequence information in the formal tabulation;

When the second database received thing stream number and order number, execution in step S6 was to step S11;

Step S6: described the second database is saved to thing stream number and the order number that receives in the interim tabulation, and finds corresponding with it sequence information according to described order number from formal tabulation;

Step S7: described the second database root generates the 3rd digest according to the described thing stream number in the user basic information that comprises in the second key, the described sequence information that finds and product ID, the interim tabulation, and sends the second request msg to described the first database;

Step S8: described the first database obtains sequence information, thing stream number and the 3rd digest from described the second request msg that receives, and generates the 4th digest according to the user basic information and the product ID that comprise in the first key, described thing stream number, the described sequence information;

Step S9: whether described the first database is compared described the 3rd digest consistent with described the 4th digest, is then to carry out next step, otherwise send the request response that comprises error code to described the second database;

Step S10: described the first database is that the thing stream number field of the sequence information in the described sequence information table is preserved described thing stream number, and sends the request response that comprises synchronous success coding to described the second database;

Step S11: described the second database is saved to the thing stream number field that the described sequence information in the formal tabulation comprises with described thing stream number, and the described sequence information deletion in will temporarily tabulating.

2. the synchronous implementation method of a kind of data-base remote according to claim 1, it is characterized in that: include user basic information, order number, product type field, product ID field and thing stream number field in the described sequence information, described product ID field and thing stream number field are initially sky.

3. the synchronous implementation method of a kind of data-base remote according to claim 1, it is characterized in that: described the first key and described the second key are the session keys that the first database and the second database are consulted in advance.

4. the synchronous implementation method of a kind of data-base remote according to claim 1, it is characterized in that: prestore the arranging key file according to the time name in described the first database and described the second database, described step S1 also comprises, described the first database reads the current system time, read corresponding arranging key file according to the current system time, from described arranging key file, obtain the first key, described step S2 also comprises, described the second database reads the current system time, read corresponding arranging key file according to the current system time, from described arranging key file, obtain the second key.

5. the synchronous implementation method of a kind of data-base remote according to claim 1, it is characterized in that: described the first database root of step S1 generates the first digest according to the user basic information that comprises in the sequence information in the first key and the sequence information table and is specially: described the first database is spliced into a serial data with the user basic information in the described sequence information and described the first key by the order of making an appointment, and adopts the algorithm of making an appointment that described serial data is encrypted and produces the first digest;

The described user basic information according to comprising in the second key and the described sequence information that gets access to of step S2 generates the second digest and is specially: the user basic information in the described sequence information and the second key are spliced into a serial data by the order of making an appointment, adopt the algorithm of making an appointment that described serial data is encrypted and produce the second digest.

6. the synchronous implementation method of a kind of data-base remote according to claim 1, it is characterized in that: described step S2 also comprises, the process of the validity of the described sequence information that described the second database authentication obtains from described the first request msg, described step S8 also comprises, the process of the validity of the described sequence information that described the first database authentication obtains from described the second request msg; Whether the process of verifying the validity of described sequence information is specially the format and content of the described sequence information of checking effective.

7. the synchronous implementation method of a kind of data-base remote according to claim 1, it is characterized in that: described step S5 is specially, described the second database root requires qualified Optimum Matching product in the retrieval product library according to the product type field that comprises in the described sequence information, and the product ID field value in the product record that retrieves is saved in the product ID field of described sequence information.

8. the synchronous implementation method of a kind of data-base remote according to claim 1, it is characterized in that: described step S5 comprises, the first operation of described the second database initialize, create trigger and the trigger parameter is set, scheduling start time and dispatch interval time are set, reach scheduling during the start time when monitoring system time, the operation that the initiating task scheduler schedules creates, and will dispatch the start time and increase described dispatch interval time; The first operation of described establishment is: all sequence informations during traversal is formally tabulated automatically, product type field according to sequence information requires qualified Optimum Matching product record in the retrieval product library, and product ID field value in the product record is saved in the product ID field of described sequence information.

9. the synchronous implementation method of a kind of data-base remote according to claim 1, it is characterized in that: described step S6 comprises, described the second database searches whether there is the described order number that receives in formal tabulation, be that described thing stream number and the order number that then will receive is saved in the interim tabulation as a record, otherwise do not preserve.

10. the synchronous implementation method of a kind of data-base remote according to claim 1, it is characterized in that: described step S6 comprises, the second operation of described the second database initialize and the 3rd operation, create trigger and the trigger parameter is set, the second scheduling start time was set, the 3rd scheduling start time and dispatch interval time, reach the second scheduling during the start time when monitoring system time, the second operation that the initiating task scheduler schedules creates, and the second scheduling increased described dispatch interval time the start time, reach the 3rd scheduling during the start time when monitoring system time, the 3rd operation that the initiating task scheduler schedules creates, and the second scheduling start time increased described dispatch interval time; Described the second operation is, the formal tabulation of depositing sequence information is downloaded to designated memory space, and described the 3rd operation is to obtain the interim tabulation of preserving order number and thing stream number from described designated memory space.

11. the synchronous implementation method of a kind of data-base remote according to claim 1, it is characterized in that: step S4 is described to be comprised after described the first database transmission comprises the request response of successfully encoding, after described the first database received the described request response, the described sequence information of mark came into force.

12. the synchronous implementation method of a kind of data-base remote according to claim 1, it is characterized in that: described step S11 replaces with: described the second database is saved to the thing stream number field that the described sequence information in the formal tabulation comprises with described thing stream number, and the described sequence information in will temporarily tabulating is labeled as and processes.

13. the synchronous implementation method of a kind of data-base remote according to claim 12, it is characterized in that: described method also comprises, when system time reaches Preset Time, the 4th operation of initiating task scheduler schedules, described the 4th operation is: retrieval is labeled as the sequence information processed in the temporary table and with its deletion.

14. the synchronous implementation method of a kind of data-base remote according to claim 1, it is characterized in that: when described the second database receives the sequence information that will upgrade, comprise among the described step S4, the described sequence information that will upgrade is saved in the formal tabulation, and the product ID field in the described sequence information that will upgrade comprises old product sequence-number field and new product sequence-number field; Described step S5 is specially, preserve the new product sequence number for the product ID field of the described sequence information that will upgrade in the formal tabulation, the product ID that comprises in the sequence information that is updated is saved in the old product sequence-number field of the described sequence information that will upgrade.

15. the synchronous implementation method of a kind of data-base remote according to claim 1, it is characterized in that: described the second database root of step S7 is according to the second key, the user basic information and the product ID that comprise in the described sequence information that finds, described thing stream number in the interim tabulation generates the 3rd digest and is specially, described the second database is with the user basic information in the described sequence information and product ID, described thing stream number and the second key in the interim tabulation are spliced into a serial data according to the order of making an appointment, and adopt the algorithm of making an appointment to produce the 3rd digest to described serial data;

Described user basic information and the product ID according to comprising in the first key, described thing stream number, the described sequence information of step S8 generates the 4th digest and is specially, described the first database is spliced into a serial data with the user basic information in the described sequence information and product ID, described thing stream number and described the first key by the order of making an appointment, and adopts the algorithm of making an appointment that described serial data is encrypted and produces the 4th digest.

Images