Data warehouse architecture suitable for digital logistics platform and processing method

Abstract

The invention provides a data warehouse architecture suitable for a digital logistics platform and a processing method. The architecture comprises the steps that a first data sub-warehouse is deployed in the digital logistics platform; the first data sub-warehouse performs data interaction with the user side, and local waybill data is updated according to the state data from the third data sub-warehouse; the second data sub-warehouse is deployed in a transportation enterprise; the second data sub-warehouse completes the synchronization of the first data sub-warehouse and the waybill data in the internal database; the third data sub-warehouse is deployed in a transportation enterprise; and the third data sub-warehouse performs data interaction with the first data sub-warehouse and the internal database, obtains state data of the internal database, and pushes the state data to the first data sub-warehouse. According to the architecture, the data bins are arranged in the digital logistics platform and the transportation enterprise respectively, data synchronization between the digital logistics platform and the transportation enterprise is achieved, the digital logistics platform can be directly connected with internal data of the transportation enterprise, and the automation degree of a system and the enthusiasm of a driver are improved.

Description

Technical Field

[0001] The present invention belongs to the field of logistics technology, and specifically relates to a data warehouse architecture and processing method suitable for a digital logistics platform. Background Art

[0002] In order to improve the efficiency of the logistics industry, transportation companies currently manage transportation orders through digital logistics platforms. Digital logistics platforms realize digital management and optimization of logistics business by integrating advanced information technologies such as big data and the Internet of Things. Internet of Things technology enables the interconnection of goods, vehicles and equipment in the logistics process, and monitors the location, status and transportation environment of goods in real time. Artificial intelligence can realize intelligent route planning, intelligent warehouse management and intelligent customer service. Digital logistics platforms bring better service experience to enterprises and consumers.

[0003] However, the transportation data of the current digital logistics platform still relies on the correct filling of the data by the driver, which seriously affects the accuracy of the transportation capacity and the lack of automation, which affects the driver's enthusiasm and transportation capacity guarantee. Summary of the invention

[0004] In view of the defects in the prior art, the present invention provides a data warehouse architecture and processing method suitable for a digital logistics platform, which directly connects to the internal data of the transportation company, improves the automation level of the system and the enthusiasm of the drivers.

[0005] In the first aspect, a data warehouse architecture suitable for a digital logistics platform is applied to a transportation enterprise including an internal database; the architecture includes:

[0006] The first data sub-warehouse is deployed in the digital logistics platform. The first data sub-warehouse interacts with the user end. The first data sub-warehouse is also used to update the local waybill data according to the status data from the third data sub-warehouse.

[0007] Second data warehouse: deployed in the transport enterprise; the second data warehouse interacts with the first data warehouse and the internal database to complete the synchronization of the waybill data between the first data warehouse and the internal database;

[0008] The third data sub-warehouse is deployed in the transportation enterprise. The third data sub-warehouse interacts with the first data sub-warehouse and the internal database respectively. The third data sub-warehouse is used to obtain the status data of the internal database and push the status data to the first data sub-warehouse.

[0009] Furthermore, the second data sub-warehouse is specifically used to: obtain the local waybill data of the first data sub-warehouse, convert and complete the obtained waybill data, and transmit it to the internal database;

[0010] The internal database is specifically used to update the local waybill data according to the waybill data from the second data warehouse.

[0011] Furthermore, the internal database is specifically used for:

[0012] When a change in the status data in the local waybill data is detected, the new status data is pushed to the third data distribution warehouse;

[0013] The status data includes weighing data.

[0014] Furthermore, the internal database is also used to: generate a maintenance instruction when in the maintenance phase and send it to the second data sub-warehouse; generate an operation instruction when in the normal operation phase and send it to the second data sub-warehouse; and update the local waybill data according to the backup data when receiving the backup data from the second data sub-warehouse;

[0015] The second data sub-warehouse is also used to: send maintenance instructions or operation instructions to the first data sub-warehouse; and to send backup data from the first data sub-warehouse to the internal database;

[0016] The first data sub-warehouse is also used for: when a maintenance instruction or an operation instruction is received, setting its status to a maintenance status or an operation status; when a status query instruction is received from the user end and its status is a maintenance status, receiving status data from the user end, updating the local waybill data according to the status data, and storing the status data in the backup data; when it is detected that its status changes from a maintenance status to an operation status, sending the backup data to the second data sub-warehouse and clearing the backup data; when it is detected that its status is an operation status, updating the local waybill data according to the pushed status data.

[0017] Furthermore, the first data sub-warehouse interacts with the user end and the second data sub-warehouse through a Webservice interface.

[0018] In a second aspect, a processing method for a data warehouse architecture applicable to a digital logistics platform is applied to a transportation enterprise including an internal database; the method comprises:

[0019] The first data sub-warehouse interacts with the user end for data; the first data sub-warehouse is deployed in the digital logistics platform;

[0020] The second data sub-warehouse interacts with the first data sub-warehouse and the internal database respectively to complete the synchronization of the waybill data between the first data sub-warehouse and the internal database; the second data sub-warehouse is deployed in the transportation enterprise;

[0021] The third data sub-warehouse interacts with the first data sub-warehouse and the internal database respectively; the third data sub-warehouse is deployed in the transportation enterprise;

[0022] The third data sub-warehouse obtains the status data of the internal database and pushes the status data to the first data sub-warehouse;

[0023] The first data sub-warehouse updates the local waybill data according to the status data from the third data sub-warehouse.

[0024] Furthermore, the synchronization of the waybill data in the first data sub-warehouse and the internal database specifically includes:

[0025] The second data sub-warehouse obtains the local waybill data of the first data sub-warehouse;

[0026] The second data warehouse converts and completes the acquired waybill data and transmits it to the internal database;

[0027] The internal database updates the local waybill data according to the waybill data from the second data warehouse.

[0028] Furthermore, the third data sub-warehouse obtains the status data in the internal database specifically including:

[0029] When the internal database detects that the status data in the local waybill data has changed, it pushes the new status data to the third data warehouse;

[0030] The status data includes weighing data.

[0031] Furthermore, it also includes:

[0032] When the internal database is in the maintenance phase, a maintenance instruction is generated and sent to the second data sub-warehouse;

[0033] When the internal database is in the normal operation stage, it generates an operation instruction and sends it to the second data warehouse;

[0034] The second data sub-warehouse sends the maintenance instruction or the operation instruction to the first data sub-warehouse;

[0035] When the first data sub-warehouse receives a maintenance instruction or an operation instruction, it sets its state to a maintenance state or an operation state;

[0036] When the first data sub-warehouse receives a status query instruction from the user terminal and its status is in maintenance status, it receives status data from the user terminal, updates local waybill data according to the status data, and stores the status data in the backup data;

[0037] When the first data sub-warehouse detects that its state changes from the maintenance state to the operation state, the backup data is sent to the second data sub-warehouse and the backup data is cleared;

[0038] The second data sub-warehouse sends the backup data from the first data sub-warehouse to the internal database;

[0039] When the internal database receives the backup data from the second data sub-warehouse, it updates the local waybill data according to the backup data;

[0040] When the first data sub-warehouse detects that its status is in the running state, it updates the local waybill data according to the pushed status data.

[0041] Furthermore, the first data sub-warehouse interacts with the user end and the second data sub-warehouse through a Webservice interface.

[0042] It can be seen from the above technical solutions that the data warehouse architecture and processing method suitable for the digital logistics platform provided by the present invention respectively sets up data warehouses in the digital logistics platform and the transportation enterprise to realize data synchronization between the digital logistics platform and the transportation enterprise, so that the digital logistics platform can directly connect to the internal data of the transportation enterprise, thereby improving the system's degree of automation and the enthusiasm of the drivers. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] In order to more clearly illustrate the specific embodiments of the present invention or the technical solutions in the prior art, the following is a brief introduction to the drawings required for the specific embodiments or the description of the prior art. In all the drawings, similar elements or parts are generally identified by similar reference numerals. In the drawings, the elements or parts are not necessarily drawn according to the actual scale.

[0044] Figure 1 A schematic diagram of a data warehouse architecture suitable for a digital logistics platform provided in an embodiment.

[0045] Figure 2 A flowchart of a processing method provided in an embodiment.

[0046] Figure 3 A flow chart of a method for synchronizing data between a first data sub-warehouse and an internal database provided in an embodiment.

[0047] Figure 4 A flowchart of a maintenance phase status data updating method provided by an embodiment. DETAILED DESCRIPTION

[0048] The embodiments of the technical solution of the present invention will be described in detail below in conjunction with the accompanying drawings. The following embodiments are only used to more clearly illustrate the technical solution of the present invention, and are therefore only used as examples, and the protection scope of the present invention cannot be limited thereto. It should be noted that, unless otherwise specified, the technical terms or scientific terms used in this application should be the common meanings understood by those skilled in the art to which the present invention belongs.

[0049] It should be understood that when used in this specification and the appended claims, the terms "include" and "comprises" indicate the presence of described features, integers, steps, operations, elements and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components and / or combinations thereof.

[0050] It should also be understood that the terms used in this specification of the present invention are only for the purpose of describing specific embodiments and are not intended to limit the present invention. As used in the specification of the present invention and the appended claims, unless the context clearly indicates otherwise, the singular forms "a", "an" and "the" are intended to include plural forms.

[0051] As used in this specification and the appended claims, the term "if" may be interpreted as "when" or "upon" or "in response to determining" or "in response to detecting," depending on the context. Similarly, the phrases "if it is determined" or "if [described condition or event] is detected" may be interpreted as meaning "upon determination" or "in response to determining" or "upon detection of [described condition or event]" or "in response to detecting [described condition or event]," depending on the context.

[0052] Example:

[0053] A data warehouse architecture suitable for a digital logistics platform, applied to a transportation enterprise with an internal database; see Figure 1 , the architecture includes:

[0054] The first data sub-warehouse is deployed in the digital logistics platform. The first data sub-warehouse interacts with the user end. The first data sub-warehouse is also used to update the local waybill data according to the status data from the third data sub-warehouse.

[0055] Second data warehouse: deployed in the transport enterprise; the second data warehouse interacts with the first data warehouse and the internal database to complete the synchronization of the waybill data between the first data warehouse and the internal database;

[0056] The third data sub-warehouse is deployed in the transportation enterprise. The third data sub-warehouse interacts with the first data sub-warehouse and the internal database respectively. The third data sub-warehouse is used to obtain the status data of the internal database and push the status data to the first data sub-warehouse.

[0057] In this embodiment, the architecture deploys the first data sub-warehouse in the digital logistics platform, and the first data sub-warehouse interacts with the user end, which includes the consignor end, the carrier end, the driver end, etc. When the user opens the user end, the user end reads the data in the first data sub-warehouse. For example, when the consignor end initiates a waybill, the consignor end saves the filled-in waybill data to the first data sub-warehouse. When the driver end views a waybill, the waybill data is read and displayed from the first data sub-warehouse.

[0058] This architecture deploys the second data sub-warehouse and the third data sub-warehouse in the transportation enterprise. The second data sub-warehouse interacts with the first data sub-warehouse and the internal database respectively. That is, the second data sub-warehouse can send the waybill data in the first data sub-warehouse to the internal database for waybill data synchronization, and can also send the waybill data in the internal database to the first data sub-warehouse for waybill data synchronization. For example, when a carrier adds a new waybill, the second data sub-warehouse reads the new waybill data from the first data sub-warehouse and synchronizes it to the internal database. The third data sub-warehouse is mainly used to synchronize the status data in the waybill data. The internal database is also connected to the internal equipment of the enterprise, reads the status data of each internal equipment of the enterprise and stores it. The third data sub-warehouse obtains the status data of the internal database and pushes the status data to the first data sub-warehouse for data synchronization.

[0059] This data warehouse architecture, which is suitable for the digital logistics platform, sets up data warehouses in the digital logistics platform and the transportation company respectively, realizes data synchronization between the digital logistics platform and the transportation company, so that the digital logistics platform can directly connect to the internal data of the transportation company, improve the system's degree of automation and the enthusiasm of drivers.

[0060] Furthermore, in some embodiments, the second data sub-warehouse is specifically used to: obtain the local waybill data of the first data sub-warehouse, convert and complete the obtained waybill data, and transmit it to the internal database;

[0061] The internal database is specifically used to update the local waybill data according to the waybill data from the second data warehouse.

[0062] In this embodiment, since the storage format, data name, and data category of the data in the digital logistics platform and the transportation enterprise are not necessarily exactly the same, the second data sub-warehouse needs to convert and complete the waybill data before transmitting it when completing the synchronization of the waybill data between the digital logistics platform and the transportation enterprise, so as to ensure the uniformity of the storage format of the databases of both parties. For example, the order date field in the first data sub-warehouse corresponds to the task start time field in the internal database, and the vehicle load field in the first data sub-warehouse corresponds to the approved load field in the internal database. Therefore, the second data sub-warehouse obtains the local waybill data of the first data sub-warehouse, converts the waybill data, and corresponds the fields in the first data sub-warehouse to the fields in the internal database. When a field is missing in the converted waybill data, it can be completed with the default value of the field and then transmitted to the internal database, ensuring the uniformity of the data format in the internal database.

[0063] Furthermore, in some embodiments, the internal database is specifically used for:

[0064] When a change in the status data in the local waybill data is detected, the new status data is pushed to the third data distribution warehouse;

[0065] The status data includes weighing data.

[0066] In this embodiment, in order to ensure the timeliness of the update of the status data in the waybill data in the first data sub-warehouse. When the internal database detects that the status data in the local waybill data has changed, it pushes the new status data to the third data sub-warehouse, and the third data sub-warehouse pushes the new status data to the first data sub-warehouse for updating. The status data may be weighing data including the weight detected by the scale. In this way, when the scale updates the status data to the internal database, the internal database is triggered to update the new status data to the first data sub-warehouse, so that the first data sub-warehouse can obtain the weighing data in the first time, without the need for the driver to fill it out manually, thereby improving the automation of the system and the enthusiasm of the driver.

[0067] Furthermore, in some embodiments, the internal database is also used to: generate a maintenance instruction when in the maintenance phase and send it to the second data sub-warehouse; generate an operation instruction when in the normal operation phase and send it to the second data sub-warehouse; and update the local waybill data according to the backup data when receiving the backup data from the second data sub-warehouse;

[0068] The second data sub-warehouse is also used to: send maintenance instructions or operation instructions to the first data sub-warehouse; and to send backup data from the first data sub-warehouse to the internal database;

[0069] The first data sub-warehouse is also used for: when a maintenance instruction or an operation instruction is received, setting its status to a maintenance status or an operation status; when a status query instruction is received from the user end and its status is a maintenance status, receiving status data from the user end, updating the local waybill data according to the status data, and storing the status data in the backup data; when it is detected that its status changes from a maintenance status to an operation status, sending the backup data to the second data sub-warehouse and clearing the backup data; when it is detected that its status is an operation status, updating the local waybill data according to the pushed status data.

[0070] In this embodiment, when the internal database of the transportation enterprise is in the maintenance stage or the transportation enterprise is in the network maintenance stage, the internal database will disconnect from the external database, and the internal database will generate a maintenance instruction and send it to the second data sub-warehouse. After the maintenance stage of the internal database or the network maintenance stage of the transportation enterprise is over, the internal database is in the normal operation stage, and the internal database will generate an operation instruction and send it to the second data sub-warehouse. The second data sub-warehouse forwards the maintenance instruction or the operation instruction to the first data sub-warehouse.

[0071] In this embodiment, when the first data sub-warehouse receives a maintenance instruction or an operation instruction, it sets its state to a maintenance state or an operation state. When the first data sub-warehouse is in the maintenance state, it means that the internal database has been disconnected from the external database and cannot interact with the internal database temporarily. At this time, if a status query instruction from the user end is received, for example, when the driver end queries the weighing data in the waybill, the user end can remind the driver that the weighing data reading fails, prompt the driver to manually input the weighing data first, and then update the waybill data in the first data sub-warehouse according to the weighing data input by the driver, and store the status data in the backup data, which is used to record the status data manually input by the driver when the internal database is in the maintenance stage. When the first data sub-warehouse detects that its state has changed from the maintenance state to the operation state, it means that the internal database has resumed normal operation. At this time, the backup data can be sent to the second data sub-warehouse, and the second data sub-warehouse sends the backup data to the internal database for data synchronization. The first data sub-warehouse clears the local backup data at the same time. When the first data sub-warehouse is in the operation state, the local waybill data is normally updated according to the status data pushed by the third data sub-warehouse.

[0072] Furthermore, in some embodiments, the first data sub-warehouse interacts with the user end and the second data sub-warehouse through a Webservice interface.

[0073] In this embodiment, the first data sub-warehouse provides a unified external Webservice interface to implement communication between the first data sub-warehouse and the user end and the second data sub-warehouse.

[0074] A processing method for the data warehouse architecture of a digital logistics platform, applied to a transportation enterprise with an internal database; see Figure 2 , methods include:

[0075] The first data sub-warehouse interacts with the user end for data; the first data sub-warehouse is deployed in the digital logistics platform;

[0076] The second data sub-warehouse interacts with the first data sub-warehouse and the internal database respectively to complete the synchronization of the waybill data between the first data sub-warehouse and the internal database; the second data sub-warehouse is deployed in the transportation enterprise;

[0077] The third data sub-warehouse interacts with the first data sub-warehouse and the internal database respectively; the third data sub-warehouse is deployed in the transportation enterprise;

[0078] The third data sub-warehouse obtains the status data of the internal database and pushes the status data to the first data sub-warehouse;

[0079] The first data sub-warehouse updates the local waybill data according to the status data from the third data sub-warehouse.

[0080] Further, in some embodiments, see Figure 3 The synchronization of the waybill data between the first data warehouse and the internal database specifically includes:

[0081] The second data sub-warehouse obtains the local waybill data of the first data sub-warehouse;

[0082] The second data warehouse converts and completes the acquired waybill data and transmits it to the internal database;

[0083] The internal database updates the local waybill data according to the waybill data from the second data warehouse.

[0084] Further, in some embodiments, the third data sub-warehouse obtains the status data in the internal database specifically including:

[0085] When the internal database detects that the status data in the local waybill data has changed, it pushes the new status data to the third data warehouse;

[0086] The status data includes weighing data.

[0087] Further, in some embodiments, see Figure 4 , also includes:

[0088] When the internal database is in the maintenance phase, a maintenance instruction is generated and sent to the second data sub-warehouse;

[0089] When the internal database is in the normal operation stage, it generates an operation instruction and sends it to the second data warehouse;

[0090] The second data sub-warehouse sends the maintenance instruction or the operation instruction to the first data sub-warehouse;

[0091] When the first data sub-warehouse receives a maintenance instruction or an operation instruction, it sets its state to a maintenance state or an operation state;

[0092] When the first data sub-warehouse receives a status query instruction from the user terminal and its status is in maintenance status, it receives status data from the user terminal, updates local waybill data according to the status data, and stores the status data in the backup data;

[0093] When the first data sub-warehouse detects that its state changes from the maintenance state to the operation state, the backup data is sent to the second data sub-warehouse and the backup data is cleared;

[0094] The second data sub-warehouse sends the backup data from the first data sub-warehouse to the internal database;

[0095] When the internal database receives the backup data from the second data sub-warehouse, it updates the local waybill data according to the backup data;

[0096] When the first data sub-warehouse detects that its status is in the running state, it updates the local waybill data according to the pushed status data.

[0097] Furthermore, in some embodiments, the first data sub-warehouse interacts with the user end and the second data sub-warehouse through a Webservice interface.

[0098] The system provided in the embodiment of the present invention is briefly described. For matters not mentioned in the embodiment part, reference may be made to the corresponding contents in the aforementioned embodiment.

[0099] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or replace some or all of the technical features therein by equivalents. These modifications or replacements do not make the essence of the corresponding technical solutions deviate from the scope of the technical solutions of the embodiments of the present invention, and they should all be included in the scope of the claims and specification of the present invention.

Claims

1. A data warehouse architecture suitable for a digital logistics platform, characterized in that: Applied to a transportation enterprise including an internal database; the architecture includes: The first data sub-warehouse is deployed in the digital logistics platform; the first data sub-warehouse interacts with the user end; the first data sub-warehouse is also used to update the local waybill data according to the status data from the third data sub-warehouse; Second data sub-warehouse: deployed in the transport enterprise; the second data sub-warehouse interacts with the first data sub-warehouse and the internal database respectively to complete the synchronization of the waybill data between the first data sub-warehouse and the internal database; The third data sub-warehouse is deployed in the transportation enterprise; the third data sub-warehouse interacts with the first data sub-warehouse and the internal database respectively; the third data sub-warehouse is used to obtain the status data of the internal database and push the status data to the first data sub-warehouse.

2. The data warehouse architecture suitable for the digital logistics platform according to claim 1 is characterized in that: The second data sub-warehouse is specifically used to: obtain the local waybill data of the first data sub-warehouse, convert and complete the obtained waybill data, and transmit it to the internal database; The internal database is specifically used to update local waybill data according to the waybill data from the second data warehouse.

3. The data warehouse architecture suitable for the digital logistics platform according to claim 1 is characterized in that: The internal database is specifically used for: When it is detected that the status data in the local waybill data changes, the new status data is pushed to the third data sub-warehouse; The status data includes weighing data.

4. The data warehouse architecture suitable for the digital logistics platform according to claim 1 is characterized in that: The internal database is further used to: generate a maintenance instruction when in the maintenance phase and send it to the second data sub-warehouse; generate an operation instruction when in the normal operation phase and send it to the second data sub-warehouse; and update the local waybill data according to the backup data when receiving the backup data from the second data sub-warehouse; The second data sub-warehouse is further used to: send the maintenance instruction or the operation instruction to the first data sub-warehouse; and to send the backup data from the first data sub-warehouse to the internal database; The first data sub-warehouse is further used for: when a maintenance instruction or an operation instruction is received, setting its state to a maintenance state or an operation state; when a state query instruction is received from the user end and its state is a maintenance state, receiving the state data from the user end, updating the local waybill data according to the state data, and storing the state data in the backup data; When it is detected that its state changes from the maintenance state to the running state, the backup data is sent to the second data sub-warehouse and the backup data is cleared; when it is detected that its state is the running state, the local waybill data is updated according to the pushed state data.

5. The data warehouse architecture suitable for the digital logistics platform according to claim 1 is characterized in that: The first data sub-warehouse interacts with the user end and the second data sub-warehouse through a Webservice interface.

6. A processing method for a data warehouse architecture suitable for a digital logistics platform, characterized in that: Applied to a transportation enterprise including an internal database; the method comprises: The first data sub-warehouse interacts with the user end for data; the first data sub-warehouse is deployed in the digital logistics platform; The second data sub-warehouse interacts with the first data sub-warehouse and the internal database respectively to complete the synchronization of the waybill data between the first data sub-warehouse and the internal database; the second data sub-warehouse is deployed in the transportation enterprise; The third data sub-warehouse interacts with the first data sub-warehouse and the internal database respectively; the third data sub-warehouse is deployed in the transportation enterprise; The third data sub-warehouse obtains status data of the internal database and pushes the status data to the first data sub-warehouse; The first data sub-warehouse updates the local waybill data according to the status data from the third data sub-warehouse.

7. The processing method for the data warehouse architecture applicable to the digital logistics platform according to claim 6 is characterized in that: The synchronization of the first data sub-warehouse and the waybill data in the internal database specifically includes: The second data sub-warehouse obtains the local waybill data of the first data sub-warehouse; The second data warehouse converts and completes the acquired waybill data and transmits it to the internal database; The internal database updates the local waybill data according to the waybill data from the second data warehouse.

8. The processing method for the data warehouse architecture applicable to the digital logistics platform according to claim 6 is characterized in that: The third data sub-warehouse obtains the status data in the internal database specifically including: When the internal database detects that the status data in the local waybill data has changed, it pushes the new status data to the third data sub-warehouse; The status data includes weighing data.

9. The processing method for the data warehouse architecture applicable to the digital logistics platform according to claim 6 is characterized in that: Also includes: When the internal database is in the maintenance stage, a maintenance instruction is generated and sent to the second data sub-warehouse; When the internal database is in the normal operation stage, it generates an operation instruction and sends it to the second data sub-warehouse; The second data sub-warehouse sends the maintenance instruction or the operation instruction to the first data sub-warehouse; When the first data sub-warehouse receives a maintenance instruction or an operation instruction, it sets its state to a maintenance state or an operation state; When the first data sub-warehouse receives a status query instruction from the user terminal and its status is a maintenance status, it receives the status data from the user terminal, updates the local waybill data according to the status data, and stores the status data in the backup data; When the first data sub-warehouse detects that its state changes from the maintenance state to the operation state, the first data sub-warehouse sends the backup data to the second data sub-warehouse and clears the backup data; The second data sub-warehouse sends the backup data from the first data sub-warehouse to the internal database; When the internal database receives the backup data from the second data sub-warehouse, it updates the local waybill data according to the backup data; When the first data sub-warehouse detects that its status is in the running state, it updates the local waybill data according to the pushed status data.

10. The processing method for the data warehouse architecture applicable to the digital logistics platform according to claim 6 is characterized in that: The first data sub-warehouse interacts with the user end and the second data sub-warehouse through a Webservice interface.

Images