Data Retrieval Method and System for Logistics Digital Control System

Abstract

The present invention belongs to the technical field of data retrieval, and particularly relates to a data retrieval method and system for a logistics digital control system. The method includes: S1. The logistics information of the items arriving at the logistics distribution center is input through an input module to generate a logistics record file, and the generated logistics record file is sent to a storage module; S2. The storage module uses different logistics record files in a first storage unit to fill different logistics record tables in a second storage unit, and a retrieval module sends a first retrieval request to the storage module, and the storage module performs a first retrieval process according to the first retrieval request; S3. After a preset running time, the storage module stores different logistics transfer files in a third storage unit, and the retrieval module sends a second retrieval request to the storage module, and the storage module performs a second retrieval process according to the second retrieval request. The present invention can perform retrieval without completing the filling of the logistics record table.

Description

Technical Field

[0001] The present invention belongs to the technical field of data retrieval, and particularly relates to a data retrieval method and system for a logistics digital control system. Background Art

[0002] With the continuous development of computer application technology, logistics digital control systems are used more and more in people's lives. Through the logistics digital control system, logistics information can be queried, so as to conveniently understand the logistics progress.

[0003] Chinese invention application with publication number CN106844372A discloses a logistics information query method and device. The method includes: receiving a primary query request of a logistics user for specific logistics information, querying information related to the specific logistics information in a specified logistics information storage database according to the query conditions provided by the primary query request, and according to the query conditions and / or the information related to the specific logistics information obtained by the query, sending a secondary query request to the corresponding logistics system, updating the corresponding data in the specified logistics information storage database according to the received real-time logistics information and the information related to the specific logistics information queried in the specified logistics information storage database, forming a query result corresponding to the primary query request according to the updated corresponding data in the specified logistics information storage database, and generating a query result display page and sending it to the logistics user. In addition, Chinese invention application with publication number CN106528636A proposes a courier number query system and method. The system includes a query device, a cloud platform and at least one courier number database. The query device, the cloud platform and the courier number database are connected in sequence. The query device is used for exchanging information with the cloud platform. The cloud platform is used for transmitting information with the query device and receiving the courier number information transmitted by the courier number database. The courier number database is used for transmitting the courier number information to the cloud platform. The method includes the courier number database sending the courier number information to the cloud platform, the query device sending user verification information to the cloud platform, the cloud platform storing the courier number information, the cloud platform receiving and verifying the user's verification information. If the verification is passed, relevant courier number information is queried according to the pre-stored user-related information, and the relevant courier number information is sent to the query device.

[0004] However, in the above-mentioned invention applications, there is a problem that when storing logistics information in the database, it is impossible to retrieve the logistics information that has not been completely stored. Summary of the Invention

[0005] In the present invention, different logistics record files are generated by different input modules, and the different logistics record files are sent to a storage module. The storage module uses the different logistics record files to fill different logistics record tables, retrieves according to a first retrieval request of a retrieval module, and the storage module also performs a transfer storage process on partial data records in the different logistics record tables and retrieves according to a second retrieval request of the retrieval module. The present invention aims to achieve retrieval under the condition that the filling of the logistics record table is not completed.

[0006] In order to achieve the above-mentioned invention purpose, the present invention provides a data retrieval method for a logistics digital control system as described below, which mainly includes the following steps:

[0007] S1. At different logistics distribution centers, the input module inputs logistics information of the items arriving at the logistics distribution center to generate logistics record files, and the input modules at different logistics distribution centers send the generated logistics record files to the storage module;

[0008] S2. The storage module receives the logistics record files sent by the input modules at different logistics distribution centers, stores the different logistics record files into a first storage unit respectively, uses the different logistics record files in the first storage unit to fill different logistics record tables in a second storage unit, and the retrieval module sends a first retrieval request to the storage module, and the storage module performs a first retrieval process according to the first retrieval request;

[0009] S3. After a preset running time, the storage module selects partial data records from different logistics record tables in the second storage unit to generate logistics transfer files, stores the different logistics transfer files into a third storage unit, and the retrieval module sends a second retrieval request to the storage module, and the storage module performs a second retrieval process according to the second retrieval request.

[0010] As a preferred technical solution of the present invention, the storage module stores a first description table, and the data records in the first description table include a logistics record table ID, a block division identifier, a first storage location, a transfer storage identifier, and a second storage location.

[0011] As a preferred technical solution of the present invention, the storage module stores a second description table, and the data records in the second description table include a logistics record table ID, an attribute name, and an attribute identifier.

[0012] As a preferred technical solution of the present invention, the storage module stores a first correspondence table, a second correspondence table, and a third correspondence table. The data records in the first correspondence table include a logistics record form ID, a logistics record file name, a marking time, and a usage identifier. The data records in the second correspondence table include a logistics record form ID, a block number, and a block identifier. The data records in the third correspondence table include a logistics record form ID, a block number, a logistics transfer and storage file name, a minimum attribute value, and a maximum attribute value.

[0013] As a preferred technical solution of the present invention, the storage module fills different logistics record forms in the second storage unit with different logistics record files in the first storage unit, including the following steps:

[0014] S211. The storage module waits for a preset time and then proceeds to S212;

[0015] S212. Based on the first description table, the storage module regards a first storage location in the first description table as the target first storage location, and the storage module performs monitoring processing on the logistics record file stored at the target first storage location, and then proceeds to S213;

[0016] S213. The storage module determines whether the first correspondence table has been updated during the monitoring processing. If so, the storage module fills the corresponding logistics record form with the logistics record file corresponding to the updated data record in the first correspondence table, and then proceeds to S214. If not, it directly proceeds to S214;

[0017] S214. The storage module determines whether all the first storage locations in the first description table have undergone the processing of S212 and S213. If not, it jumps to S212. If so, the storage module continues to determine whether to stop all processing. If so, it ends all steps. If not, it jumps to S211.

[0018] As a preferred technical solution of the present invention, the storage module performs monitoring processing on the logistics record file stored at the target first storage location, including the following steps:

[0019] S2121. Regarding all the logistics record files stored at the target first storage location, the storage module obtains the relevant information of all the logistics record files. The relevant information includes the logistics record file name generated when storing the logistics record file, and the marking time related to the logistics record file;

[0020] S2122. The storage module determines whether all logistics record files have been processed in steps S2123 and subsequent steps. If so, all steps end; if not, S2123 continues;

[0021] S2123. The storage module regards a logistics record file as the target logistics record file and determines whether there is a data record in the first correspondence table whose included logistics record file name is the same as the logistics record file name in the relevant information of the target logistics record file. If not, the storage module adds a new data record in the first correspondence table and jumps to S2122; if so, S2124 continues;

[0022] S2124. The storage module determines whether the marked time in the relevant information of the target logistics record file is later than the marked time in the corresponding data record in the first correspondence table. If so, the storage module updates the corresponding data record, and the updated content includes the marked time and the usage identifier, and jumps to S2122; if not, it directly jumps to S2122.

[0023] As a preferred technical solution of the present invention, the storage module performs a first retrieval process according to the first retrieval request, including the following steps:

[0024] S221. Based on the first retrieval request, the storage module determines whether there is a data record in the first correspondence table whose included logistics record table ID is the same as the logistics record table ID in the first retrieval request. If not, it jumps to S223; if so, it continues to determine whether the usage identifier in the corresponding data record is "used". If so, it jumps to S223; if not, S222 continues;

[0025] S222. The storage module performs a first retrieval on the logistics record table corresponding to the logistics record table ID in the first retrieval request according to the first retrieval request, and performs a second retrieval on the logistics record file corresponding to the logistics record file name in the corresponding data record, and all steps end;

[0026] S223. The storage module performs a first retrieval on the logistics record table corresponding to the logistics record table ID in the first retrieval request according to the first retrieval request.

[0027] As a preferred technical solution of the present invention, the storage module selects some data records from a logistics record table in the second storage unit to generate a logistics transfer file and stores the logistics transfer file in the third storage unit, including the following steps:

[0028] S311. The storage module selects the data record block that was filled into the logistics record table earliest to generate a logistics transfer file, and adds a data record to the third corresponding table. The data record includes the logistics record table ID, block number, logistics transfer file name, minimum attribute value, and maximum attribute value. Here, the minimum attribute value and the maximum attribute value respectively refer to the minimum and maximum values among all the attribute values corresponding to the attribute name corresponding to the attribute identifier "yes" in the data record block that was filled into the logistics record table earliest;

[0029] S312. Based on the added data record, the storage module searches in the second corresponding table for a data record whose included logistics record table ID and block number are respectively the same as those in the added data record, and sets the block identifier in the data record to "transferred";

[0030] S313. The storage module deletes the data record block that was filled into the logistics record table earliest in the logistics record table.

[0031] As a preferred technical solution of the present invention, the storage module executes a second retrieval process according to the second retrieval request, including the following steps:

[0032] S321. Based on the second retrieval request, the storage module determines whether there is a data record in the third corresponding table whose included logistics record table ID is the same as the logistics record table ID in the second retrieval request. If not, it continues with S324; if so, it continues with S322;

[0033] S322. The storage module determines whether the second retrieval request includes a retrieval condition regarding the attribute value corresponding to the attribute name corresponding to the attribute identifier "yes". If so, according to the retrieval condition, it determines the logistics transfer file to be retrieved in the logistics transfer file corresponding to the logistics transfer file name in the corresponding data record, performs a first retrieval on the logistics record table corresponding to the logistics record table ID in the second retrieval request, and performs a second retrieval on the logistics transfer file to be retrieved. If not, it continues with S323;

[0034] S323. The storage module performs a first retrieval on the logistics record table corresponding to the logistics record table ID in the second retrieval request, and performs a second retrieval on the logistics transfer file corresponding to the logistics transfer file name in the corresponding data record, and ends all steps;

[0035] S324. The storage module performs a first retrieval on the logistics record table corresponding to the logistics record table ID in the second retrieval request according to the second retrieval request.

[0036] The present invention also provides a data retrieval system for a logistics digital control system, mainly including the following modules:

[0037] An input module, configured to input logistics information of items arriving at different logistics distribution centers to generate logistics record files, and to send the generated different logistics record files to a storage module;

[0038] A storage module, configured to separately store different logistics record files into a first storage unit, use the different logistics record files in the first storage unit to fill different logistics record tables in a second storage unit, and to select partial data records from the different logistics record tables in the second storage unit to generate logistics transfer files, store the different logistics transfer files into a third storage unit, and further configured to perform a first retrieval process according to a first retrieval request, and perform a second retrieval process according to a second retrieval request;

[0039] A retrieval module, configured to send a first retrieval request and a second retrieval request to the storage module.

[0040] Compared with the prior art, the beneficial effects of the present invention are at least as follows:

[0041] In the present invention, first, the input module inputs logistics information of items arriving at the logistics distribution center to generate logistics record files, and the input modules of different logistics distribution centers send the generated logistics record files to the storage module. Second, the storage module separately stores different logistics record files into the first storage unit, uses the different logistics record files in the first storage unit to fill different logistics record tables in the second storage unit. The retrieval module sends a first retrieval request to the storage module, and the storage module performs a first retrieval process according to the first retrieval request. Finally, after a preset running time, the storage module selects partial data records from the different logistics record tables in the second storage unit to generate logistics transfer files, stores the different logistics transfer files into the third storage unit. The retrieval module sends a second retrieval request to the storage module, and the storage module performs a second retrieval process according to the second retrieval request. Through the present invention, even when the filling of the logistics record table is not completed, the retrieval process can be performed, so as to timely respond to the retrieval request, and at the same time, while ensuring that the storage module has available storage space, when partial data records in the logistics record table are deleted, the retrieval process can be performed to avoid the failure of responding to the retrieval request. Description of the Drawings

[0042] Figure 1 It is a step flow chart of the data retrieval method for the logistics digital control system of the present invention;

[0043] Figure 2 It is a composition structure diagram of the data retrieval system for the logistics digital control system of the present invention. Detailed Embodiments

[0044] In order to make the objectives, technical solutions and advantages of the present invention more clear and understandable, the present invention will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not used to limit the present invention.

[0045] It can be understood that the terms "first", "second", etc. used in this application may be used in this document to describe various elements, but unless otherwise specified, these elements are not limited by these terms. These terms are only used to distinguish one element from another. For example, without departing from the scope of this application, the first xx script may be referred to as the second xx script, and similarly, the second xx script may be referred to as the first xx script.

[0046] The present invention provides a data retrieval method for a logistics digital control system as Figure 1 shown, which is mainly implemented by performing the following steps:

[0047] S1. At different logistics distribution centers, the logistics information of the items arriving at the logistics distribution centers is input through the input module to generate logistics record files, and the input modules of different logistics distribution centers send the generated logistics record files to the storage module;

[0048] S2. The storage module receives the logistics record files sent by the input modules of different logistics distribution centers, stores the different logistics record files into the first storage unit respectively, uses the different logistics record files in the first storage unit to fill the different logistics record tables in the second storage unit, and the retrieval module sends a first retrieval request to the storage module, and the storage module performs a first retrieval process according to the first retrieval request;

[0049] S3. After a preset running time, the storage module selects some data records from the different logistics record tables in the second storage unit to generate logistics transfer files, stores the different logistics transfer files into the third storage unit, and the retrieval module sends a second retrieval request to the storage module, and the storage module performs a second retrieval process according to the second retrieval request.

[0050] Specifically, first, an input module is set up at different logistics distribution centers. The input module can input the logistics information of the items arriving at the logistics distribution center to generate a logistics record file. Among them, the logistics information includes the logistics order number, the time of arrival at the distribution center, etc. The logistics record file contains different data records. For example, a data record is "SF6787989O, 2024 / 06 / 01 9:10". The logistics order number and the time of arrival at the distribution center are separated by a comma. The input modules of different logistics distribution centers send the generated logistics record files to the storage module for storage. Thus, by uniformly sending a retrieval request to the storage module, the logistics progress can be queried, which is convenient for controlling the logistics process. Secondly, the storage module stores the logistics record files from the input modules of different logistics distribution centers separately in its first storage unit. The first storage positions of different logistics record files in the first storage unit are set in advance by the storage module. The storage module uses different logistics record files in the first storage unit to fill different logistics record tables in the second storage unit. It should be noted that multiple logistics record files may be needed to fill one logistics record table, and the first storage positions of multiple logistics record files are the same. In addition, the meaning of filling here refers to automatically importing the data records in the logistics record file into the logistics record table. When the number of data records to be imported is relatively large, it will take a long time. During the process of the storage module filling different logistics record tables, the retrieval module can send a first retrieval request to the storage module, and the storage module performs a first retrieval process according to the first retrieval request. Finally, as time goes by, the data volume stored in the second storage unit will also increase continuously, making the available space of the second storage unit continuously decrease. Therefore, every time a running time elapses, for example, the running time can be one month, the storage module selects some data records from different logistics record tables in the second storage unit to generate logistics transfer files. The format of the logistics transfer files is the same as that of the logistics record files. The storage module stores different logistics transfer files in the third storage unit. The second storage positions of different logistics transfer files in the third storage unit are also set in advance by the storage module. It should be noted that multiple logistics transfer files can be stored in one second storage position, and the multiple logistics transfer files stored in one second storage position correspond to one logistics record table. During the process of the storage module transferring some data records of different logistics record tables, the retrieval module sends a second retrieval request to the storage module, and the storage module performs a second retrieval process according to the second retrieval request.

[0051] Furthermore, the storage module stores a first description table. The data records in the first description table include the logistics record table ID, block division identifier, first storage position, transfer identifier, and second storage position.

[0052] Specifically, the data record in the first description table records the setting information about different logistics record tables. The data record includes a logistics record table ID, a block division identifier, a first storage location, a transfer identifier, and a second storage location. The logistics record table ID can uniquely identify the logistics record table. The block division identifier represents whether it is allowed to fill the logistics record table corresponding to the logistics record table ID in units of data record blocks. The data record block contains multiple data records. When the block division identifier is yes, it indicates permission, otherwise it indicates no permission. For ease of understanding, the data record block is explained here. When multiple logistics record files are needed to fill a logistics record table, each logistics record file corresponds to a data record block in the logistics record table. The first storage location refers to the storage location of the logistics record file that fills the logistics record table corresponding to the logistics record table ID in the first storage unit. The transfer identifier represents whether it is allowed to transfer part of the data records in the logistics record table corresponding to the logistics record table ID to the third storage unit. The transfer identifier is yes, indicating permission, otherwise it indicates no permission. The second storage location refers to the storage location of the logistics transfer file corresponding to the logistics record table corresponding to the logistics record table ID in the third storage unit. In the first description table, one logistics record table ID corresponds to one data record.

[0053] Furthermore, the storage module stores a second description table, and the data records in the second description table include a logistics record table ID, an attribute name, and an attribute identifier.

[0054] Specifically, the data records in the second description table record information about the attribute names in different logistics record tables. The attribute name is the attribute name in the logistics record table corresponding to the logistics record table ID. The attribute identifier represents whether the corresponding attribute name is regarded as an identification attribute name. If the attribute identifier is yes, it indicates that the corresponding attribute name is an identification attribute name. Otherwise, it indicates that the corresponding attribute name is not an identification attribute name. When initiating a retrieval request, the retrieval module usually restricts the size range of the attribute value corresponding to the identification attribute name. In the second description table, a combination of the logistics record table ID and the attribute name corresponds to a data record.

[0055] Furthermore, the storage module stores a first corresponding table, a second corresponding table, and a third corresponding table. The data records in the first corresponding table include a logistics record table ID, a logistics record file name, a marking time, and a usage identifier. The data records in the second corresponding table include a logistics record table ID, a block number, and a block identifier. The data records in the third corresponding table include a logistics record table ID, a block number, a logistics transfer file name, a minimum attribute value, and a maximum attribute value.

[0056] Specifically, the first correspondence table, the second correspondence table, and the third correspondence table are introduced respectively here. Among them, in the first correspondence table, the data record includes the logistics record form ID, the logistics record file name, the marking time, and the usage identifier. In the first correspondence table, one logistics record file name corresponds to one data record. The logistics record file name is generated by the storage module when storing the logistics record file. The marking time refers to the time when the logistics record file corresponding to the logistics record file name is stored, or the time when the logistics record file corresponding to the logistics record file name is updated. After the input module updates the generated logistics record file, the storage module also updates the stored logistics record file accordingly. The usage identifier represents whether the logistics record file corresponding to the logistics record file name has been used to fill the logistics record form corresponding to the logistics record form ID. The usage identifier being "yes" indicates that it has been used, otherwise, it indicates that it has not been used. In the second correspondence table, the data record includes the logistics record form ID, the block number, and the block identifier. In the second correspondence table, a combination of the logistics record form ID and the block number corresponds to one data record. The block number represents the unique number of the data record block in the logistics record form corresponding to the logistics record form ID. The block identifier represents whether the data record block corresponding to the block number has been transferred and stored. The content of the block identifier includes "transferred and stored" and "not transferred and stored". In the third correspondence table, the data record includes the logistics record form ID, the block number, the logistics transfer and storage file name, the minimum attribute value, and the maximum attribute value. In the third correspondence table, one logistics transfer and storage file name corresponds to one data record. The logistics transfer and storage file name represents the name of the logistics transfer and storage file generated when the data record block corresponding to the block number is transferred and stored. The minimum attribute value refers to the minimum value among all the attribute values corresponding to the identification attribute name in the logistics transfer and storage file corresponding to the logistics transfer and storage file name. The maximum attribute value refers to the maximum value among all the attribute values corresponding to the identification attribute name in the logistics transfer and storage file corresponding to the logistics transfer and storage file name. The identification attribute name has been introduced above.

[0057] Furthermore, the storage module uses different logistics record files in the first storage unit to fill different logistics record forms in the second storage unit, including the following steps:

[0058] S211. The storage module waits for a preset time and then proceeds to S212;

[0059] S212. The storage module, based on the first description table, regards a first storage location in the first description table as the target first storage location, and the storage module monitors and processes the logistics record file stored at the target first storage location, and then proceeds to S213;

[0060] S213. The storage module determines whether the first correspondence table has been updated during the monitoring process. If so, the storage module fills the corresponding logistics record table with the logistics record file corresponding to the logistics record file name in the updated data record in the first correspondence table, and continues with S214. If not, it directly continues with S214;

[0061] S214. The storage module determines whether all the first storage locations in the first description table have undergone the processing of S212 and S213. If not, it jumps to S212. If so, the storage module continues to determine whether to stop all processing. If so, it ends all steps. If not, it jumps to S211.

[0062] Specifically, in step S211, the storage module waits for a certain period of time and then executes step S212. In step S212, according to the first description table, the storage module regards one of the first storage locations in the first description table as the target first storage location. The selection of this first storage location can be arbitrary. The monitoring process for the logistics record file stored at the target first storage location will be described in detail below. Then it continues with step S213. In step S213, the storage module determines whether the first correspondence table has been updated during the monitoring process. If so, it fills the corresponding logistics record table with the logistics record file corresponding to the logistics record file name in the updated data record in the first correspondence table. The corresponding logistics record table is the logistics record table corresponding to the logistics record table ID corresponding to the logistics record file name in the updated data record. It should be noted that after the filling is completed, the usage flag corresponding to the logistics record file name in the updated data record in the first correspondence table is also set to yes, and then it continues with step S214. If not, it directly continues with step S214. In step S214, the storage module determines whether all the first storage locations in the first description table have undergone the above processing. If not, it jumps to step S212 and regards other first storage locations as new target first storage locations. If so, the storage module continues to determine whether to stop all processing. If so, it ends all steps. If not, it jumps to step S211. That is to say, when the storage module does not receive a message indicating to stop all processing, the storage module executes steps S212 to S214 every certain period of time.

[0063] Furthermore, the monitoring process of the storage module for the logistics record file stored at the target first storage location includes the following steps:

[0064] S2121. For all the logistics record files stored at the target first storage location, the storage module obtains the relevant information of all the logistics record files. The relevant information includes the logistics record file name generated when storing the logistics record file, and the marked time related to the logistics record file;

[0065] S2122. The storage module determines whether all the logistics record files have undergone the processing of S2123 and subsequent steps. If so, all steps are ended. If not, S2123 is continued;

[0066] S2123. The storage module regards a logistics record file as the target logistics record file, and determines whether there is a data record in the first correspondence table whose included logistics record file name is the same as the logistics record file name in the relevant information of the target logistics record file. If not, the storage module adds a new data record in the first correspondence table and jumps to S2122. If so, S2124 is continued;

[0067] S2124. The storage module determines whether the marked time in the relevant information of the target logistics record file is later than the marked time in the corresponding data record in the first correspondence table. If so, the storage module updates the corresponding data record, and the updated content includes the marked time and the usage identifier, and jumps to S2122. If not, it directly jumps to S2122.

[0068] Specifically, the process of monitoring and processing is introduced here. In step S2121, for all the logistics record files stored at the target first storage location, the storage module obtains the relevant information of all the logistics record files. Among them, the relevant information includes the logistics record file name generated when storing the logistics record file and the marked time related to the logistics record file. The marked time has been introduced above. Then continue with step S2122. In step S2122, the storage module determines whether all the logistics record files have been processed in the subsequent steps. If so, all steps are ended. If not, continue with step S2123. In step S2123, the storage module regards a logistics record file as the target logistics record file. The selection of this logistics record file is arbitrary. It is judged whether there is a data record in the first correspondence table that contains the same logistics record file name as the logistics record file name in the relevant information of the target logistics record file. If not, the storage module adds a new data record in the first correspondence table. To determine the logistics record table ID in this data record, first search in the first description table for the data record that contains the same first storage location as the target first storage location, and then determine the logistics record table ID in the found data record. Subsequently, supplement the logistics record file name, marked time, and usage identifier in this data record. The usage identifier is "no". Then jump to step S2122. If so, continue with step S2124. In step S2124, the storage module determines whether the marked time in the relevant information of the target logistics record file is later than the marked time in the corresponding data record in the first correspondence table. The corresponding data record refers to the data record in the first correspondence table that contains the same logistics record file name as the logistics record file name in the relevant information of the target logistics record file. If so, the storage module updates the corresponding data record. The updated content includes the marked time and the usage identifier. The usage identifier is "no", and then jump to step S2122. If not, directly jump to step S2122. After that, other logistics record files may also be regarded as new target logistics record files.

[0069] Further, the storage module performs a first retrieval process according to the first retrieval request, including the following steps:

[0070] S221. Based on the first retrieval request, the storage module determines whether there is a data record in the first correspondence table that contains the same logistics record table ID as the logistics record table ID in the first retrieval request. In the case of "no", jump to S223. In the case of "yes", continue to determine whether the usage identifier in the corresponding data record is "used". In the case of "yes", jump to S223. In the case of "no", continue with S222;

[0071] S222. The storage module performs a first search on the logistics record table corresponding to the logistics record table ID in the first search request, and performs a second search on the logistics record file corresponding to the logistics record file name in the corresponding data record, and ends all steps;

[0072] S223. The storage module performs a first search on the logistics record table corresponding to the logistics record table ID in the first search request.

[0073] Specifically, in step S221, the storage module determines, according to the first search request, whether there is a data record in the first correspondence table that contains the same logistics record table ID as the logistics record table ID in the first search request. If not, it jumps to step S223. If so, it continues to determine whether the usage flag in the corresponding data record is yes. The corresponding data record refers to the data record in the first correspondence table that contains the same logistics record table ID as the logistics record table ID in the first search request. In the case of yes, it jumps to step S223. In the case of no, it continues with step S222. In step S222, since the logistics record file corresponding to the logistics record file name in the corresponding data record has not been used for filling processing, the storage module performs a first search on the logistics record table corresponding to the logistics record table ID in the first search request, and performs a second search on the logistics record file corresponding to the logistics record file name in the corresponding data record, and then ends all steps. In step S223, the storage module only needs to perform a first search on the logistics record table corresponding to the logistics record table ID in the first search request, and then ends all steps. Through the above method, even if the storage module has not completed the filling of the logistics record file, it can still perform a search, so as to respond to the search request of the search module in a timely manner.

[0074] Furthermore, the storage module selects some data records from a logistics record table in the second storage unit to generate a logistics transfer file, and stores the logistics transfer file in the third storage unit, including the following steps:

[0075] S311. The storage module selects the data record block that was filled into the logistics record table earliest to generate a logistics transfer file, and adds a data record to the third correspondence table. The data record includes the logistics record table ID, block number, logistics transfer file name, minimum attribute value, and maximum attribute value. Among them, the minimum attribute value and the maximum attribute value respectively refer to the minimum value and the maximum value among all the attribute values corresponding to the attribute name with the attribute flag being yes in the data record block that was filled into the logistics record table earliest;

[0076] S312. The storage module looks up in the second corresponding table for a data record whose included logistics record table ID and block number are respectively the same as those in the added data record based on the added data record, and sets the block identifier in the data record to "transferred and stored".

[0077] S313. The storage module deletes the data record block that was earliest filled into the logistics record table in the logistics record table.

[0078] Specifically, here it is described by taking the example that the storage module selects some data record blocks from a logistics record table in the second storage unit to generate a logistics transfer file and stores the logistics transfer file in the third storage unit. The transfer identifier corresponding to the logistics record table ID of this logistics record table in the data record of the first description table is "yes". In step S311, the storage module selects the data record block that was earliest filled into this logistics record table, generates a logistics transfer file, stores the logistics transfer file according to the second storage location recorded in the first description table, and adds a data record in the third corresponding table. This data record includes the logistics record table ID, block number, logistics transfer file name, minimum attribute value, and maximum attribute value. The block number is the block number of the data record block that was earliest filled into this logistics record table. The logistics transfer file name is the name of the logistics transfer file generated when transferring the data record block. The minimum attribute value and the maximum attribute value respectively refer to the minimum value and the maximum value among all the attribute values corresponding to the attribute name corresponding to the attribute identifier "yes" in the data record block that was earliest filled into this logistics record table. The attribute name corresponding to the attribute identifier "yes" is also the identified attribute name. In step S312, the storage module looks up in the second corresponding table for a data record whose included logistics record table ID and block number are respectively the same as those in the added data record based on the added data record, and sets the block identifier in the data record to "transferred and stored". In step S313, the storage module deletes the data record block that was earliest filled into this logistics record table in the logistics record table, thereby increasing the available space of the second storage unit.

[0079] Furthermore, the storage module performs a second retrieval process according to the second retrieval request, including the following steps:

[0080] S321. Based on the second retrieval request, the storage module determines whether there is a data record in the third corresponding table whose included logistics record table ID is the same as the logistics record table ID in the second retrieval request. If not, continue with S324. If so, continue with S322.

[0081] S322. The storage module determines whether the second retrieval request contains a retrieval condition regarding the attribute value corresponding to the attribute name corresponding to the attribute identifier being "yes". If so, according to the retrieval condition, it determines the logistics transfer file to be retrieved in the logistics transfer file corresponding to the logistics transfer file name in the corresponding data record, conducts a first retrieval on the logistics record table corresponding to the logistics record table ID in the second retrieval request, and conducts a second retrieval on the logistics transfer file to be retrieved. If not, it proceeds to S323;

[0082] S323. The storage module conducts a first retrieval on the logistics record table corresponding to the logistics record table ID in the second retrieval request, and conducts a second retrieval on the logistics transfer file corresponding to the logistics transfer file name in the corresponding data record, ending all steps;

[0083] S324. The storage module conducts a first retrieval on the logistics record table corresponding to the logistics record table ID in the second retrieval request according to the second retrieval request.

[0084] Specifically, in step S321, the storage module determines, according to the second retrieval request, whether there is a data record in the third correspondence table whose included logistics record table ID is the same as the logistics record table ID in the second retrieval request. If not, it proceeds to step S324. If so, it proceeds to step S322. In step S322, the storage module determines whether the second retrieval request contains a retrieval condition regarding the attribute value corresponding to the attribute name corresponding to the attribute identifier being "yes". The attribute name corresponding to the attribute identifier being "yes" refers to the identification attribute name. The retrieval condition limits the size of the attribute value within a certain range, so that the logistics transfer file to be retrieved can be determined in the logistics transfer file corresponding to the logistics transfer file name in the corresponding data record. This can shorten the time spent on retrieval. The specific method is to compare the retrieval condition with the minimum attribute value and the maximum attribute value corresponding to the logistics transfer file. The corresponding data record is the data record in the third correspondence table whose included logistics record table ID is the same as the logistics record table ID in the second retrieval request. The storage module conducts a first retrieval on the logistics record table corresponding to the logistics record table ID in the second retrieval request, and conducts a second retrieval on the logistics transfer file to be retrieved. If not, it proceeds to step S323. In step S323, the storage module conducts a first retrieval on the logistics record table corresponding to the logistics record table ID in the second retrieval request, and directly conducts a second retrieval on the logistics transfer file corresponding to the logistics transfer file name in the corresponding data record, and then ends all steps. In step S324, the storage module only needs to conduct a first retrieval on the logistics record table corresponding to the logistics record table ID in the second retrieval request according to the second retrieval request, and then ends all steps. Through the above method, the storage module can conduct retrieval in the case where some data records in the logistics record table have been deleted, avoiding the failure of the response to the retrieval request of the retrieval module.

[0085] As shown in Figure 2 the present invention also provides a data retrieval system for a logistics digital control system, including an input module, a storage module, and a retrieval module, which are used to implement the data retrieval method for the logistics digital control system described above.

[0086] Among them, the functions of each module are described as follows:

[0087] The input module is used to input logistics information of items arriving at different logistics distribution centers to generate logistics record files, and is used to send the generated different logistics record files to the storage module;

[0088] The storage module is used to store different logistics record files into the first storage unit respectively, use the different logistics record files in the first storage unit to fill different logistics record tables in the second storage unit, and is used to select part of the data records from the different logistics record tables in the second storage unit to generate logistics transfer files, store the different logistics transfer files into the third storage unit, and is also used to perform a first retrieval process according to a first retrieval request and a second retrieval process according to a second retrieval request.

[0089] The retrieval module is used to send a first retrieval request and a second retrieval request to the storage module.

[0090] It should be understood that although each step in the flowchart of each embodiment of the present invention is shown sequentially according to the indication of the arrow, these steps are not necessarily executed sequentially according to the order indicated by the arrow. Unless there is a clear description in this article, the execution of these steps has no strict order limit, and these steps can be executed in other orders. Moreover, at least a part of the steps in each embodiment may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily executed at the same time, but can be executed at different times. The execution order of these sub-steps or stages is not necessarily sequential, but can be executed alternately or alternately with at least a part of other steps or sub-steps or stages of other steps.

[0091] Those of ordinary skill in the art can understand that all or part of the processes in the methods of the above embodiments can be completed by instructing relevant hardware through a computer program. The above program can be stored in a non-volatile computer-readable storage medium. When the program is executed, it can include the processes of the embodiments of the above methods. Among them, any reference to a memory, storage, database, or other medium used in the embodiments provided in the present application can include non-volatile and / or volatile memories. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in various forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), Rambus direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and Rambus dynamic RAM (RDRAM), etc.

[0092] The technical features of the above embodiments can be combined arbitrarily. For the sake of brevity of description, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, it should be considered as the scope recorded in this specification.

[0093] The above embodiments only represent several implementation manners of the present invention. The description is relatively specific and detailed, but it should not be construed as a limitation on the scope of the invention patent of the present invention. It should be noted that for those of ordinary skill in the art, without departing from the concept of the present invention, several modifications and improvements can still be made, and these all belong to the protection scope of the present invention. Therefore, the protection scope of the invention patent of the present invention should be subject to the appended claims.

[0094] The above is only the preferred embodiment of the present invention and is not used to limit the present invention. Any modifications, equivalent replacements, and improvements made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims

1. A data retrieval method for a digital logistics control system, applied to a data retrieval system for a digital logistics control system, comprising an input module, a storage module, and a retrieval module, characterized in that: The method comprises the following steps: S1. In different logistics distribution centers, the logistics information of the items arriving at the logistics distribution centers is input through the input module to generate a logistics record file, and the input modules of the different logistics distribution centers send the generated logistics record files to the storage module; S2, the storage module receives the logistics record files sent by the input modules of different logistics distribution centers, stores the different logistics record files in the first storage unit respectively, fills the different logistics record tables in the second storage unit with the different logistics record files in the first storage unit, and the retrieval module sends a first retrieval request to the storage module, and the storage module performs a first retrieval process according to the first retrieval request; S3, after a preset running time, the storage module selects some data records from different logistics record tables in the second storage unit to generate logistics transfer files, stores the different logistics transfer files in the third storage unit, and the retrieval module sends a second retrieval request to the storage module, and the storage module performs a second retrieval process according to the second retrieval request; The storage module stores a first description table, wherein the data records in the first description table include a logistics record table ID, a block division identifier, a first storage location, a transfer identifier, and a second storage location; The storage module stores a first corresponding table, and the data records in the first corresponding table include a logistics record table ID, a logistics record file name, a marking time, and a use identifier; The storage module uses different logistics record files in the first storage unit to fill different logistics record tables in the second storage unit, including the following steps: S211, the storage module waits for a preset time, and then proceeds to S212; S212, based on the first description table, the storage module uses a first storage location in the first description table as a target first storage location, and the storage module monitors and processes the logistics record file stored in the target first storage location, and then continues to S213; S213, the storage module determines whether the first corresponding table is updated in the monitoring process. If yes, the storage module fills the corresponding logistics record table with the logistics record file corresponding to the logistics record file name in the updated data record in the first corresponding table, and continues to S214. If no, directly continue to S214; S214, the storage module determines whether all the first storage locations in the first description table have been processed by S212 and S213. If not, jump to S212. If yes, the storage module continues to determine whether to stop all processing. If yes, end all steps. If no, jump to S211.

2. The method according to claim 1, characterized in that The storage module stores a second description table, and the data records in the second description table include a logistics record table ID, an attribute name, and an attribute identifier.

3. The method according to claim 2, characterized in that The storage module stores a second corresponding table and a third corresponding table. The data records in the second corresponding table include the logistics record table ID, block number, and block identifier. The data records in the third corresponding table include the logistics record table ID, block number, logistics transfer file name, minimum attribute value, and maximum attribute value.

4. The method according to claim 3, characterized in that The storage module monitors and processes the logistics record file stored in the target first storage location, including the following steps: S2121. With respect to all logistics record files stored in the target first storage location, the storage module obtains relevant information of all logistics record files, the relevant information including the logistics record file name generated when the logistics record file is stored, and the marking time related to the logistics record file; S2122, the storage module determines whether all logistics record files have been processed by S2123 and steps after S2123. If yes, all steps are terminated; if no, continue with S2123; S2123, the storage module regards a logistics record file as a target logistics record file, and determines whether there is a data record in the first corresponding table containing a logistics record file name that is the same as the logistics record file name in the relevant information of the target logistics record file. If not, the storage module adds a data record in the first corresponding table and jumps to S2122. If yes, continue to S2124; S2124. The storage module determines whether the marking time in the relevant information of the target logistics record file is later than the marking time in the corresponding data record in the first corresponding table. If so, the storage module updates the corresponding data record, and the updated content includes the marking time and the usage identifier, and jumps to S2122. If not, jump directly to S2122.

5. The method according to claim 4, characterized in that The storage module performs a first search process according to the first search request, including the following steps: S221, based on the first search request, the storage module determines whether there is a data record in the first corresponding table containing the same logistics record table ID as the logistics record table ID in the first search request, if not, jump to S223, if yes, continue to determine whether the use identifier in the corresponding data record is used, if yes, jump to S223, if no, continue to S222; S222: The storage module performs a first search on the logistics record table corresponding to the logistics record table ID in the first search request according to the first search request, and performs a second search on the logistics record file corresponding to the logistics record file name in the corresponding data record, and ends all steps; S223. The storage module performs a first search on the logistics record table corresponding to the logistics record table ID in the first search request according to the first search request.

6. The method according to claim 5, characterized in that The storage module selects part of the data records from a logistics record table in the second storage unit to generate a logistics transfer file, and stores the logistics transfer file in the third storage unit, including the following steps: S311, the storage module selects the data record block that is first filled into the logistics record table to generate a logistics transfer file, and adds a data record in the third corresponding table, the data record includes the logistics record table ID, the block number, the logistics transfer file name, the minimum attribute value, and the maximum attribute value, wherein the minimum attribute value and the maximum attribute value refer to the minimum value and the maximum value of all attribute values ​​corresponding to the attribute name corresponding to the attribute identifier in the data record block that is first filled into the logistics record table; S312, based on the added data record, the storage module searches the second corresponding table for a data record containing a logistics record table ID and a block number that respectively correspond to the logistics record table ID and the block number in the added data record, and sets the block identifier in the data record to have been transferred; S313. The storage module deletes the data record block that is first filled into the logistics record table in the logistics record table.

7. The method according to claim 6, characterized in that The storage module performs a second search process according to the second search request, including the following steps: S321, based on the second search request, the storage module determines whether there is a data record in the third corresponding table whose logistics record table ID is the same as the logistics record table ID in the second search request, if not, proceed to S324, if yes, proceed to S322; S322, the storage module determines whether the second search request contains a search condition for the attribute value corresponding to the attribute name corresponding to the attribute identifier, if yes, determines the logistics transfer file to be searched in the logistics transfer file corresponding to the logistics transfer file name in the corresponding data record according to the search condition, performs a first search on the logistics record table corresponding to the logistics record table ID in the second search request, and performs a second search on the logistics transfer file to be searched, if no, continues to S323; S323, the storage module performs a first search on the logistics record table corresponding to the logistics record table ID in the second search request, and performs a second search on the logistics transfer file corresponding to the logistics transfer file name in the corresponding data record, and ends all steps; S324. The storage module performs a first search on the logistics record table corresponding to the logistics record table ID in the second search request according to the second search request.

8. A data retrieval system for a digital logistics management and control system, used to implement the method according to any one of claims 1 to 7, characterized in that: Includes the following modules: An input module, used for inputting logistics information of items arriving at different logistics distribution centers to generate logistics record files, and for sending the generated different logistics record files to the storage module; A storage module, used to store different logistics record files in a first storage unit respectively, to fill different logistics record tables in a second storage unit with different logistics record files in the first storage unit, and to select part of data records from different logistics record tables in the second storage unit to generate logistics transfer files, to store different logistics transfer files in a third storage unit, and to perform a first retrieval process according to a first retrieval request, and to perform a second retrieval process according to a second retrieval request; The retrieval module is used to send a first retrieval request and a second retrieval request to the storage module.

Images