CN111475533A

CN111475533A - Logistics document information processing method and device and logistics data information query method and device

Info

Publication number: CN111475533A
Application number: CN202010345197.8A
Authority: CN
Inventors: 冯波; 田道驎; 梁军
Original assignee: Wanlian Yida Logistics Technology Co ltd
Current assignee: Wanlian Yida Logistics Technology Co ltd
Priority date: 2020-04-27
Filing date: 2020-04-27
Publication date: 2020-07-31

Abstract

The application discloses a method and a device for processing logistics document information and a method and a device for querying logistics data information. The method comprises the following steps: acquiring document information of a target document associated with the logistics business, wherein the document information comprises business data information and/or logistics data information associated with the target document; generating a level code of the target document according to the service level of the target document in the logistics service; associating the hierarchical code of the target document with document information of the target document, wherein the hierarchical code of the target document is a designated identifier under the condition that the target document is an initial document of the logistics service; and in the case that the target document is not the starting document of the logistics business, the hierarchical code of the target document comprises: the system comprises a hierarchical code of a previous-level document of a target document and a peer identification code of the target document in a peer document under the previous-level document. Through the embodiment, the efficiency of inquiring the logistics data information in the logistics platform system can be improved.

Description

Logistics document information processing method and device and logistics data information query method and device

Technical Field

The application relates to the field of electronic commerce, in particular to a method and a device for processing logistics document information and a method and a device for querying logistics data information.

Background

With the continuous development of internet technology, the combined mode of 'logistics + internet' business collaboration is widely applied and popularized in a logistics comprehensive service platform. Due to the fact that logistics business needs to be subjected to packet transfer and packet packaging layer by layer, a whole tracking link of logistics information is too long, logistics information needs to be inquired layer by layer, and therefore long time is needed to be completed, and after the logistics data or the logistics business is subjected to packet transfer and packet packaging for multiple times, the inquiry efficiency of tracking logistics information is reduced.

At present, business data information corresponding to documents (including two types of orders and waybills) associated with logistics business comprises document numbers, enterprise identification information and superior document numbers corresponding to the document numbers, and the business data information corresponding to each document and corresponding logistics information form logistics data information, so that the logistics data information associated with a target document can be inquired in the logistics data information according to the business data information of the documents.

Specifically, fig. 1A shows a schematic diagram of a service chain of a logistics service. Referring to FIG. 1A, after receiving the logistics business, Enterprise A subcontracts the logistics business to enterprises A1, A2 and A3 to complete. After receiving the sub-package logistics service, the enterprise A1 is responsible for the transportation of part of the service, and sub-packages the other part of the service to the enterprise A11. The enterprises a2 and A3 did not sub-package the sub-packaged logistics business to other enterprises after receiving the sub-packaged logistics business, but completed the sub-packaged logistics business by themselves.

Fig. 1B is a schematic diagram illustrating a service data information storage structure of document information corresponding to the logistics service shown in fig. 1A. Referring to fig. 1B, after receiving a parent order with an order number of 1000 corresponding to the logistics business, enterprise a initiates corresponding child orders to enterprise a1, enterprise a2, and enterprise A3, wherein the child orders are 1100, 1200, and 1300, respectively. Referring to fig. 1B, the document information corresponding to the sub-order further includes a previous order number and a business name. Enterprise a1, while completing part of the subcontracted transaction, generates a manifest corresponding to the sub-order with order number 1100, with manifest numbers 111 and 112, respectively. And enterprise a1 sends a sub-order with order number 1110 to enterprise a11 when subcontracting part of the logistics traffic to enterprise a 11. Enterprise a11 completes the logistics business and generates the orders with the order numbers 121 and 122 after receiving the sub-order.

In addition, enterprise a2 and enterprise A3, upon receiving the sub-orders, also complete the subcontracted logistics traffic and generate corresponding orders, 211, 212, 311, 312, and 313, respectively.

In the business data information configured in fig. 1B, the inquirer inquires the logistics data information associated with a certain document according to the business data information structure, and then the inquiry needs to be performed hierarchically and repeatedly. For example, if the business data information storage structure diagram shown in fig. 1B queries the logistics data information associated with the order number 1100, the business personnel needs to perform the following steps when querying in the logistics data information base corresponding to fig. 1B:

s1, inquiring the logistics information of the sub order number 1100 by taking the enterprise A1 and the sub order number 1100 as inquiry conditions, and obtaining the logistics information corresponding to the order number 1100;

s2, inquiring the logistics information of the waybill number to which the sub-order number 1100 belongs by taking the enterprise A1 and the sub-order number 1100 as inquiry conditions to obtain the logistics information of the waybill number 111 and the waybill number 112;

s3, inquiring the logistics information of the sub order number 1110 to which the sub order number 1100 belongs by taking the enterprise A1 and the sub order number 1100 as inquiry conditions to obtain the logistics information of the sub order number 1110;

s4, with the enterprise A1 and the sub-order number 1110 as query conditions, querying the logistics information of the freight note number 121 and the freight note number 122 to which the sub-order number 1110 belongs to obtain the logistics information of the freight note number 121 and the freight note number 122;

and S5, splicing the logistics information obtained by querying in S1, S2 and S4 through a logistics platform system to obtain the related logistics data information of the order number 1100.

Therefore, in the method for inquiring the logistics data information associated with the target document in the prior art, the business data information corresponding to the document is used as a basis, the document information is stored layer by layer according to the sub-packets of the business, so the inquiry work can involve multi-layer and multi-time inquiry, then the inquiry results are spliced after the multi-layer and multi-time inquiry is finished to obtain the inquiry result of the logistics data information associated with the target document, and finally, the logistics platform system movably displays the inquiry result to a front-end interface through the terminal of an inquirer. Due to the fact that the query times are large, the processing time of the logistics platform system is prolonged due to the long data splicing time, or the query result cannot be obtained due to overtime, the query efficiency of the logistics data information is low.

Therefore, no effective solution is provided at present for the technical problem of low efficiency of querying logistics data information in the existing logistics platform system.

Disclosure of Invention

The embodiment of the disclosure provides a method and a device for processing logistics document information and a method and a device for querying logistics data information, so as to improve the efficiency of querying the logistics data information in a logistics platform system.

In a first aspect, an embodiment of the present disclosure provides a method for processing logistics document information, including:

acquiring document information of a target document associated with the logistics business, wherein the document information comprises business data information and/or logistics data information associated with the target document;

generating a level code of the target document according to the service level of the target document in the logistics service; and

associating the hierarchical code of the target document with document information of the target document, wherein

Under the condition that the target document is the initial document of the logistics business, the level code of the target document is a designated identification; and

in the case that the target document is not the starting document of the logistics business, the hierarchical code of the target document comprises: the hierarchical code of the upper level document of the target document and the peer identification code in the peer document of the target document under the upper level document.

In a second aspect, an embodiment of the present disclosure further provides a method for querying logistics data information, including:

receiving a query instruction related to the logistics service, wherein the query instruction comprises service data information to be queried;

acquiring document information and a level code of a target document matched with the inquired business data information according to the business data information to be inquired, wherein the document information comprises business data information and/or logistics data information associated with the target document, and the level code is generated according to a business level of the target document in the logistics business;

acquiring the document information of the associated waybill of the target document according to the level code of the target document and the document information; and

and determining logistics data information associated with the target document according to the document information of the associated waybill.

In a third aspect, an embodiment of the present disclosure further provides a storage medium including a stored program. Wherein, the processing method of the logistics document information and the query method of the logistics data information as described in the above first aspect and the above second aspect are executed by the processor when the program runs.

In a fourth aspect, there is also provided a device for processing logistics document information according to an embodiment of the present disclosure, including:

the system comprises a document information acquisition module, a document information acquisition module and a document information processing module, wherein the document information acquisition module is used for acquiring document information of a target document associated with the logistics business, and the document information comprises business data information and/or logistics data information associated with the target document;

the hierarchical code generation module is used for generating the hierarchical code of the target document according to the service hierarchy of the target document in the logistics service; and

the system comprises a hierarchical code association module, a data processing module and a data processing module, wherein the hierarchical code association module is used for associating the hierarchical code of a target document with document information of the target document, and under the condition that the target document is an initial document of the logistics business, the hierarchical code of the target document is a designated identifier; and in the case that the target document is not the starting document of the logistics business, the hierarchical code of the target document comprises: the hierarchical code of the upper level document of the target document and the peer identification code in the peer document of the target document under the upper level document.

In a fifth aspect, an apparatus for querying logistics data information is further provided according to an embodiment of the present disclosure, including:

the query instruction receiving module is used for receiving a query instruction related to the logistics service, wherein the query instruction comprises service data information to be queried;

the system comprises a hierarchical code acquisition module, a business data acquisition module and a hierarchical code acquisition module, wherein the hierarchical code acquisition module is used for acquiring document information and a hierarchical code of a target document matched with inquired business data information according to the to-be-inquired business data information, the document information comprises business data information and/or logistics data information associated with the target document, and the hierarchical code is generated according to a business hierarchy of the target document in the logistics business;

the associated document acquisition module is used for acquiring document information of the associated shipping bill of the target document according to the level code of the target document and the document information; and

and the logistics data determining module is used for determining logistics data information associated with the target document according to the document information of the associated freight bill.

In a sixth aspect, an embodiment of the present disclosure further provides another processing apparatus for logistics document information, including:

a first processor; and

a first memory coupled to the first processor for providing instructions to the first processor to process the following process steps:

In a seventh aspect, an embodiment of the present disclosure further provides another device for querying logistics data information, including:

a second processor; and

a second memory coupled to the second processor for providing instructions to the second processor to process the following process steps:

According to the technical scheme of the embodiment, the logistics platform system acquires the document information of the target document associated with the logistics business, wherein the document information comprises business data information and/or logistics data information associated with the target document. Generating a level code of the target document according to the service level of the target document in the logistics service; and associating the hierarchical code of the target document with the document information of the target document, wherein the hierarchical code of the target document is the designated identification under the condition that the target document is the initial document of the logistics service. In the case that the target document is not the starting document of the logistics business, the hierarchical code of the target document comprises: the hierarchical code of the upper level document of the target document and the peer identification code in the peer document of the target document under the upper level document. According to the level code associated with the target document information, the logistics platform system can acquire the logistics data information associated with the target document by inquiring the document information corresponding to all the waybills corresponding to the level code, and the plurality of inquiry information are spliced without multi-layer and multi-time logistics inquiry, so that the efficiency of inquiring the logistics data information in the logistics platform system is improved.

Drawings

The accompanying drawings, which are included to provide a further understanding of the disclosure and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the disclosure and together with the description serve to explain the disclosure and not to limit the disclosure. In the drawings:

FIG. 1A shows a schematic diagram of a business chain of a logistics business;

fig. 1B is a schematic diagram illustrating a service data information storage structure of document information corresponding to the logistics service illustrated in fig. 1A;

fig. 2A shows a hardware structure block diagram of a computing device for implementing the processing method for logistics document information according to embodiment 1 of the present disclosure;

fig. 2B illustrates an application scenario diagram for implementing the processing method for implementing logistics document information according to embodiment 1 of the present disclosure;

fig. 3 is a schematic flow chart illustrating a method for processing logistics document information according to a first aspect of embodiment 1 of the present disclosure;

FIG. 4A is a schematic diagram illustrating an organization structure of document information associated with the logistics business shown in FIG. 1A provided by an embodiment of the present disclosure;

FIG. 4B is a schematic diagram illustrating the logistics data structure information corresponding to the document information organization structure shown in FIG. 4A according to an embodiment of the disclosure;

fig. 5 is a schematic flow chart illustrating a method for querying logistics data information according to a second aspect of embodiment 1 of the present disclosure;

fig. 6 is a schematic view showing a processing apparatus of logistics document information according to the first aspect of embodiment 2 of the present disclosure;

fig. 7 is a schematic diagram of a query device for logistics data information according to a second aspect of embodiment 2 of the present disclosure;

fig. 8 is a schematic view showing a processing apparatus of logistics document information according to the first aspect of embodiment 3 of the present disclosure;

fig. 9 is a schematic diagram of a logistics data information query device according to a second aspect of embodiment 3 of the present disclosure.

Reference numerals: the logistics platform system 100, the terminal device 200 of enterprise a, the terminal device 210 of enterprise a1, the terminal device 220 of enterprise a2, the terminal device 230 of enterprise A3, and the terminal device 211 of enterprise a 11.

Detailed Description

In order to make those skilled in the art better understand the technical solutions of the present disclosure, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below with reference to the drawings in the embodiments of the present disclosure. It is to be understood that the described embodiments are merely exemplary of some, and not all, of the present disclosure. All other embodiments, which can be derived by a person skilled in the art from the embodiments disclosed herein without making any creative effort, shall fall within the protection scope of the present disclosure.

It should be noted that the terms "first," "second," and the like in the description and claims of the present disclosure and in the above-described drawings are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the disclosure described herein are capable of operation in sequences other than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.

Example 1

According to the present embodiment, a method for processing logistics document information is provided, it should be noted that the steps shown in the flowchart of the figure can be executed in a computer system such as a set of computer executable instructions, and that although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that here.

The method embodiments provided by the present embodiment may be executed in a mobile terminal, a computer terminal, a server or a similar computing device. Fig. 2A shows a hardware configuration block diagram of a computing device for implementing a method of processing logistics document information. As shown in fig. 2A, the computing device may include one or more processors (which may include, but are not limited to, a processing device such as a microprocessor MCU or a programmable logic device FPGA), a memory for storing data, and a transmission device for communication functions. Besides, the method can also comprise the following steps: a display, an input/output interface (I/O interface), a Universal Serial Bus (USB) port (which may be included as one of the ports of the I/O interface), a network interface, a power source, and/or a camera. It will be understood by those skilled in the art that the structure shown in fig. 2A is only an illustration and is not intended to limit the structure of the electronic device. For example, the computing device may also include more or fewer components than shown in FIG. 2A, or have a different configuration than shown in FIG. 2A.

It should be noted that the one or more processors and/or other data processing circuitry described above may be referred to generally herein as "data processing circuitry". The data processing circuitry may be embodied in whole or in part in software, hardware, firmware, or any combination thereof. Further, the data processing circuitry may be a single, stand-alone processing module, or incorporated in whole or in part into any of the other elements in the computing device. As referred to in the disclosed embodiments, the data processing circuit acts as a processor control (e.g., selection of a variable resistance termination path connected to the interface).

The memory may be configured to store software programs and modules of application software, such as program instructions/data storage devices corresponding to the method for processing logistics document information in the embodiments of the present disclosure, and the processor executes various functional applications and data processing by running the software programs and modules stored in the memory, that is, implements the method for processing logistics document information of the application program. The memory may include high speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory may further include memory located remotely from the processor, which may be connected to the computing device over a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.

The transmission device is used for receiving or transmitting data via a network. Specific examples of such networks may include wireless networks provided by communication providers of the computing devices. In one example, the transmission device includes a Network adapter (NIC) that can be connected to other Network devices through a base station to communicate with the internet. In one example, the transmission device may be a Radio Frequency (RF) module, which is used for communicating with the internet in a wireless manner.

The display may be, for example, a touch screen-type liquid crystal display (L CD) that may enable a user to interact with a user interface of the computing device.

It should be noted here that in some alternative embodiments, the computing device shown in fig. 2A described above may include hardware elements (including circuitry), software elements (including computer code stored on a computer-readable medium), or a combination of both hardware and software elements. It should be noted that FIG. 2A is only one example of a particular specific example and is intended to illustrate the types of components that may be present in the computing devices described above.

Fig. 2B shows a schematic diagram of a logistics platform system for implementing the processing method for implementing logistics document information according to embodiment 1 of the present disclosure. Referring to fig. 2B, a terminal device 200 of enterprise a, a terminal device 210 of enterprise a1, a terminal device 220 of enterprise a2, a terminal device 230 of enterprise A3, and a terminal device 211 of enterprise a11 are respectively connected to the logistics platform system 100, so that enterprise a, enterprise a1, enterprise a2, enterprise A3, and enterprise a11 can perform interaction of logistics business through the logistics platform system 100, and the logistics platform system 100 can store document information related to the logistics business. It should be noted that the logistics platform system 100 shown in fig. 2B can be applied to the hardware structure diagram shown in fig. 2A.

Under the above operating environment, according to the first aspect of the present embodiment, a method for processing logistics document information is provided, which may be implemented by the logistics platform system 100 shown in fig. 2B, for example. Fig. 3 is a flow chart diagram illustrating a processing method for implementing logistics document information, and referring to fig. 3, the method includes:

s301, acquiring document information of a target document associated with the logistics business, wherein the document information comprises business data information and/or logistics data information associated with the target document;

s302, generating a level code of the target document according to the service level of the target document in the logistics service; and

and S303, associating the hierarchical code of the target document with document information of the target document.

Under the condition that the target document is the initial document of the logistics service, the level code of the target document is a designated identification; and in the case that the target document is not the starting document of the logistics business, the hierarchical code of the target document comprises: the hierarchical code of the upper level document of the target document and the peer identification code in the peer document of the target document under the upper level document.

Specifically, referring to fig. 1A, after receiving the logistics business, enterprise a subcontracts the logistics business to enterprises a1, a2, and A3 to complete. After receiving the sub-package logistics service, the enterprise A1 is responsible for the transportation of part of the service, and sub-packages the other part of the service to the enterprise A11. The enterprises a2 and A3 did not sub-package the sub-packaged logistics business to other enterprises after receiving the sub-packaged logistics business, but completed the sub-packaged logistics business by themselves.

In this process, the logistics platform system 100 acquires the document information of the document associated with the logistics service. For example, fig. 4A illustrates an organization structure diagram of document information associated with the logistics business shown in fig. 1A provided by an embodiment of the present disclosure. Referring to fig. 4A, when enterprise a packages the logistics service to enterprise a1, a2, and A3, terminal device 200 of enterprise a sends a sub order with sub order number 1100 to terminal device 210 of enterprise a1, sends a sub order with sub order number 1200 to terminal device 220 of enterprise a2, and sends a sub order with sub order number 1300 to terminal device 230 of enterprise A3 through logistics platform system 100. When enterprise a1 subcontracts logistics business to enterprise a11, terminal device 210 of enterprise a11 sends a sub order with sub order number 1110 to terminal device 211 of enterprise a11 through logistics platform system 100. So that the logistics platform system 100 can acquire the document information of the documents.

The business data information of the document (such as the order, the sub-order or the waybill) comprises a document number corresponding to the document, enterprise identification information, a corresponding superior order number and a document type. For example, referring to the organization structure of the document information as shown in fig. 4A, the business data information of the order 1000 received by the enterprise a through the logistics system platform 100 includes: order number 1000, business identification a, and document type "order". The business data information of the sub-order corresponding to the enterprise a1 includes: enterprise identification a1, sublist number 1100, document type "order" and corresponding superior order number 1000. The business data information corresponding to the sub-order corresponding to the enterprise a2 includes: enterprise identification a2, sub order number 1200, document type "order" and corresponding superior order number 1000. The business data information of the sub-order corresponding to the enterprise a3 includes: enterprise identification a3, sub order number 1300, document type "order" and corresponding superior order number 1000.

Further, when the transportation service corresponding to the sub-order 1100 is initiated, the enterprise a1 generates the waybills with waybill numbers 111 and 112 through the logistics platform system 100. The service data information of the waybill corresponding to the waybill number 111 includes: the invoice number 111, the business identification a1, the document type "invoice" and the corresponding superior order number 1100. The service data information of the waybill corresponding to the waybill number 112 includes: the invoice number 112, the business identification a1, the document type "invoice" and the corresponding superior order number 1100.

Similarly, the enterprise a2, the enterprise A3, and the enterprise a11 generate waybills corresponding to respective logistics services through the logistics information platform system, as shown in fig. 4A, where corresponding service data information is not described herein again.

Specifically, in step S301, the document information includes business data information and/or logistics data information associated with the target document, wherein the business data information refers to the schematic organization structure of the document information in fig. 4A. The logistics data information includes logistics state, logistics information, picture information, document remark information and the like associated with the target document, and is not particularly limited herein. For example, the logistics data information includes: and sending the product X to a certain address of Beijing from Shanghai, wherein the logistics company is an express company of Y, and the picture information and the corresponding invoice information of the product X. Referring to fig. 4A, the document information further includes logistics information (not shown in the figure) corresponding to the document, and the logistics platform system 100 acquires the document information of the target document associated with the logistics business. For example, referring to fig. 4A, the logistics platform system 100 obtains the document information of the target document being the waybill number 111, where the document information includes the waybill number 111, the enterprise identifier a1, the document type "waybill", the corresponding upper-level order number 1100, and the corresponding logistics data information.

Then, in the above step S302, the logistics platform system 100 generates a level code of the target document according to the business level of the target document in the logistics business. And under the condition that the target document is the initial document of the logistics service, the hierarchical code of the target document is the designated identification. Referring to fig. 4A, if the target document is the initial document of the initial order number 1000, the hierarchical code of the target document is a preset designated identification "0". In the case that the target document is not the starting document of the logistics business, the hierarchical code of the target document comprises: the hierarchical code of the upper level document of the target document and the peer identification code in the peer document of the target document under the upper level document.

Referring to fig. 4A, for example, if the target document is a document corresponding to the sublist number 1100, the level code of the target document is 0A, where the level code 0A includes the level code "0" of the previous-level document (the document corresponding to the primary order number 1000) of the sublist number 1100 and the peer identification label "a" in the peer document of the previous-level document of the sublist number 1100. For another example, if the target document is a document corresponding to the sub-order number 1200, the level code of the target document is 0B, where the level code 0B includes a level code "0" of a previous-level document (a document corresponding to the main order number 1000) of the sub-order number 1200 and a peer identification label "B" of a peer document in the same-level document of the sub-order number 1200 under the previous-level document. For another example, if the target document is the document corresponding to the sub-order number 1300, the level code of the target document is 0C, where the level code 0C includes the level code "0" of the previous-level document (the document corresponding to the main order number 1000) of the sub-order number 1300 and the peer identification label "C" in the peer document of the previous-level document of the sub-order number 1300. For another example, if the target document is the document corresponding to the sub-order number 1110, the level code of the target document is 0AA, where the level code 0AA includes the level code "0A" of the previous-level document (the document corresponding to the sub-order number 1100) of the sub-order number 1110 and the peer identification label "a" in the peer document of the previous-level document of the sub-order number 1110. Further, for another example, if the target document is the waybill with the waybill number of 111, the level code of the target document is 0A0001, where the level code 0A0001 includes the level code "0A" of the upper-level document (the document corresponding to the sub-order number 1100) of the waybill 111 and the peer identification label "001" in the peer document of the upper-level document of the waybill 111. In addition, if the target document is the other waybill shown in fig. 4A, the hierarchical code thereof is also determined as described above.

Preferably, in order to better identify the type of the order or the waybill, the identification information of the hierarchical code corresponding to the waybill type of the document is different from the identification information type of the order. For example, referring to fig. 4A, the hierarchical code of the document corresponding to the waybill number 111 is 0a0001, where the peer identification code "0001" is identification information of four running numbers, the identification information of the hierarchical code corresponding to the document different from the order type is an english letter, and other types of identification codes may also be used, which is not particularly limited herein.

Then, in step S303, the logistics platform system 100 associates the hierarchical code of the target document with the document information of the target document.

Specifically, fig. 4B shows a schematic diagram of associating the hierarchical code of the target document with the document information of the target document. Referring to fig. 4B, the logistics platform system 100 can associate the hierarchical code of each document with the document information. For example, the logistics platform system 100 may associate the level code 0 with the document information corresponding to the document number 1000 to form logistics data structure information corresponding to the document 1000; associating the level code 0A with the document information corresponding to the document number 1100 to form logistics data structure information corresponding to the document 1100; ...; and associating the hierarchical code 0C0003 with the document information corresponding to the document number 133 to form logistics data structure information corresponding to the document number 133. Thereby forming a set of logistics data structure information corresponding to the organizational structure of the documentation information associated with the logistics business shown in fig. 4A.

As described in the background art, in the query method of logistics data information associated with a target document in the prior art, the business data information corresponding to the document is used as a basis, and the document information is stored layer by layer according to the sub-packets of the business, so the query work involves multi-layer and multi-time query, then the query results are spliced after the multi-layer and multi-time query is finished to obtain the query result of the logistics data information associated with the target document, and finally the logistics platform system displays the query result to a front-end interface through the terminal movement of a query staff. Due to the fact that the query times are large, the processing time of the logistics platform system is prolonged due to the long data splicing time, or the query result cannot be obtained due to overtime, the query efficiency of the logistics data information is low.

In view of this, in the technical solution of this embodiment, a level code corresponding to the document is generated according to the service level of the document in the logistics service. And according to the level code formulated by the rule of the embodiment, when corresponding logistics data information is inquired according to the document, multi-layer and multi-time inquiry can be avoided.

For example, when the logistics information corresponding to the sub-order of the document number 1100 is queried, since the level code of the document is "0A", it is only necessary to query the shipping bill containing "0A" in the level code, that is, the logistics information of the shipping bills having the level codes of "0A 0001", "0A 0002", "0 AA 0001", and "0 AA 0002".

Therefore, by the mode, logistics information does not need to be inquired layer by layer any more, so that information penetrability in the inquiry process is enhanced, and the technical problem that in the inquiry process, due to the fact that the inquiry times are large and the data splicing time is long, the processing time of a logistics platform system is prolonged, or the inquiry result cannot be obtained due to overtime, and the inquiry efficiency of logistics data information is low is solved.

Optionally, the method for processing the logistics document information further includes: in the case that the type of the target document is an order, the document information includes business data information associated with the target document; and in the case that the type of the target document is the waybill, the document information comprises business data information and logistics data information which are associated with the target document.

Specifically, in the case that the type of the target document is an order, the document information includes service data information associated with the target document, and the document information corresponding to the type of the document as the order includes an order number, enterprise identification information, a document type as the order, a hierarchical code, and a corresponding upper-level order number. In the case that the type of the target document is a waybill, the document information includes business data information and logistics data information associated with the target document. For example, referring to fig. 4A, the document information of the corresponding document of the waybill number 111 includes the waybill number 111, the enterprise identifier a1, the document type "waybill", the corresponding upper order number 1100, and the corresponding logistics data information.

Thus, in this way, the logistics management platform system 100 can determine the logistics business chain information corresponding to each consignment link of the logistics business according to the business data information related to the order, and can determine the logistics information related to the logistics business according to the data information related to the waybill.

Optionally, the associating operation of the hierarchical code of the target document and the document information of the target document includes generating logistics data structure information corresponding to the target document according to the hierarchical code of the target document and the document information of the target document.

Specifically, the logistics platform system 100 generates logistics data structure information corresponding to the target document according to the hierarchical code of the target document and the document information of the target document, where the document information includes service data information and logistics data information, and the logistics data structure information is a document information structure of an associated hierarchical code, referring to fig. 4B specifically.

Fig. 4B is a schematic diagram illustrating logistics data structure information corresponding to the document information organization structure shown in fig. 4A according to an embodiment of the present disclosure, where as shown in fig. 4B, the logistics data structure information corresponding to the target document includes: enterprise identification information, a master order number, a document number, a hierarchy code, a document type and corresponding logistics data information. For example, the target document is the document information of the invoice number 111, wherein the document information includes the enterprise identification a1, the original order number 1000, the invoice number 111, the level code 0a0001, the document type "invoice" and the logistics data information 4. The logistics data structure information may also include a superior order number corresponding to the target document, which is not limited herein. By associating the level code of the target document with the document information of the target document, all the waybills under the associated target document can be inquired by using the level code of the target document, convenience is brought to the inquiry of the logistics data information corresponding to the target document, and the work efficiency of inquiring the logistics data information is improved.

Optionally, the method in this embodiment further includes the following operations:

(a1) receiving a query instruction, wherein the query instruction comprises service data information to be queried;

(a2) acquiring document information and a hierarchical code of a target document matched with the service data information to be inquired according to the service data information to be inquired; and

(a3) and acquiring the document information of the associated waybill of the target document according to the level code of the target document and the document information.

Specifically, in the step (a1), an inquiry command is sent to the logistics platform system 100 by an inquiry person through a mobile terminal, and the logistics platform system 100 receives the inquiry command corresponding to the logistics data information to be inquired, where the inquiry command includes the service data information to be inquired. For example, the query instruction includes a document number, or the query instruction includes a document number and corresponding enterprise identification information.

Then, in the step (a2), referring to fig. 4A and 4B, if the query instruction is a document number 1100, the logistics platform system 100 obtains document information of the target document matching the service data information to be queried and the level code according to the document number 1100 as follows: order number 1100, business identification a1, document type "order", corresponding superior order number 1000, and level code 0A.

Finally, in the step (a3), the document information of the document-associated waybill corresponding to the document number 1100 is acquired according to the hierarchical code of the target document and the document information. For example, when the logistics information corresponding to the sub-order of the document number 1100 is queried, since the level code of the document is "0A", the logistics information of the waybill whose level code includes "0A", that is, the logistics information of the waybill whose level code is "0A 0001", "0A 0002", "0 AA 0001", and "0 AA 0002" is queried.

Therefore, by the mode, logistics information does not need to be inquired layer by layer any more, information penetrability in the inquiry process is enhanced, and the technical problem that the logistics data information inquiry efficiency is low due to the fact that the processing time of a logistics platform system is prolonged due to the fact that the inquiry times are large and the data splicing time is long or the inquiry result cannot be obtained due to overtime in the inquiry process is solved.

Optionally, the operation of obtaining the document information of the associated waybill of the target document according to the hierarchical code of the target document and the document information includes: and under the condition that the type of the target document is determined to be the shipping bill according to the document information of the target document, determining the document information of the target document as the document information of the associated shipping bill.

Specifically, if the type of the target document is determined to be the waybill by the document information of the target document in the query instruction, the document information corresponding to the target document is determined to be the document information of the associated waybill. For example, referring to fig. 4A, if it is determined that the target document is the document type corresponding to the document number 121 is "waybill", then the document information corresponding to the document number 121 is determined as the document information of the associated waybill, which can be obtained by referring to the logistics data structure information diagram of fig. 4B, where the document information includes: the system comprises a freight note number 121, enterprise identification information A11, a hierarchical code 0AA0001, a document type 'freight note', a master order number 1000 and logistics data information 6.

Optionally, the operation of obtaining the document information of the associated waybill of the target document according to the hierarchical code of the target document and the document information further includes:

(b1) acquiring the document information of the waybill of the hierarchical code containing the hierarchical code of the target document in the hierarchical code under the condition that the type of the target document is determined to be an order according to the document information of the target document; and

(b2) and determining the acquired documentary information of the waybill as the documentary information of the associated waybill.

Specifically, in the above-described actions (b1) to (b2), in the case where the type of the target document is determined to be an order from the document information of the target document, that is, several orders or sub-orders are associated with the target document. For example, as shown in fig. 4, the target document corresponding to the order number 1100 is associated with the document corresponding to the shipping note number 111, the document corresponding to the shipping note number 112, and the document corresponding to the sub-order number 1110, where the document corresponding to the sub-order number 1110 is also associated with the document corresponding to the shipping note number 121 and the document corresponding to the shipping note number 122. According to the fact that the hierarchical code is 0A in the document information of the document corresponding to the order number 1100, the logistics platform system 100 acquires the document information of the waybill corresponding to the hierarchical code 0A, namely acquires the document information of the waybill corresponding to the hierarchical code 0A0001, the hierarchical code 0A0002, the hierarchical code 0AA0001 and the hierarchical code 0AA0002, and determines the acquired document information of the waybill as the document information of the associated waybill. According to the logistics data structure information shown in fig. 4B, the waybill information associated with the target document corresponding to the document number 1100 acquired by the logistics platform system 100 includes:

enterprise a1, master order number 1000, document number 111, level code 0a0001, document type "waybill", logistics data information 4;

enterprise a1, master order number 1000, document number 112, level code 0a0002, document type "waybill", logistics data information 5;

enterprise a11, master order number 1000, document number 121, level code 0AA0001, document type "waybill", logistics data information 6;

enterprise a11, order number 1000, document number 122, level code 0AA0002, document type "waybill", logistics data information 7.

Optionally, the logistics data information associated with the target document is determined according to the document information of the associated waybill.

Specifically, in the embodiments of the above actions (b1) and (b2), the acquiring, by the logistics platform system 100, logistics data information associated with the target document according to the document information associated with the target document corresponding to the document number 1100 includes: logistics data information 4 corresponding to the waybill number 111, logistics data information 5 corresponding to the waybill number 112, logistics data information 6 corresponding to the waybill number 121, and logistics data information 7 corresponding to the waybill number 122.

Therefore, no matter several layers of documents are associated under the target document, document information corresponding to all the freight notes associated under the target document can be inquired at one time according to the level code corresponding to the target document, logistics data information associated with the target document is obtained according to the inquired document information, and the work efficiency of inquiring the logistics data is improved.

Referring to fig. 5, fig. 5 is a schematic flow chart of a method for querying logistics data information according to a second aspect, and referring to fig. 5, the method includes:

s501, receiving a query instruction related to the logistics service, wherein the query instruction comprises service data information to be queried;

s502, acquiring document information and a level code of a target document matched with the inquired business data information according to the business data information to be inquired, wherein the document information comprises business data information and/or logistics data information associated with the target document, and the level code is generated according to a business level of the target document in the logistics business;

s503, acquiring the document information of the associated waybill of the target document according to the level code of the target document and the document information;

s504, according to the document information of the associated freight bill, determining logistics data information associated with the target document.

Specifically, in the above steps S501 to S504, reference may be made to an embodiment of the method for processing logistics document information according to the first aspect of this embodiment, and details are not repeated here. Therefore, by the mode, logistics information does not need to be inquired layer by layer any more, information penetrability in the inquiry process is enhanced, and the technical problem that the logistics data information inquiry efficiency is low due to the fact that the processing time of a logistics platform system is prolonged due to the fact that the inquiry times are large and the data splicing time is long or the inquiry result cannot be obtained due to overtime in the inquiry process is solved.

Optionally, acquiring logistics data information of an associated waybill of the target document according to the hierarchical code of the target document and the document information, including: and under the condition that the type of the target document is determined to be the waybill according to the document information of the target document, determining the logistics data information in the document information of the target document as the logistics data information of the associated target document.

Optionally, acquiring logistics data information of an associated waybill of the target document according to the hierarchical code of the target document and the document information, further comprising:

(c1) acquiring the document information of the waybill of the hierarchical code containing the hierarchical code of the target document in the hierarchical code under the condition that the type of the target document is determined to be an order according to the document information of the target document; and

(c2) and determining the logistics data information corresponding to the acquired documentary information of the waybill as the logistics data information associated with the target documentary.

Therefore, no matter several layers of documents are associated under the target document, the logistics data information corresponding to all the waybills associated under the target document can be inquired at one time only through the logistics platform system according to the level codes corresponding to the target document, and therefore the work efficiency of inquiring the logistics data is improved.

According to the storage medium of the third aspect provided by the embodiment of the present invention, it is possible to implement the respective processes in the method embodiments of the first aspect and the second aspect, and achieve the same functions and effects, which are not repeated here.

It should be noted that, for simplicity of description, the above-mentioned method embodiments are described as a series of acts or combination of acts, but those skilled in the art will recognize that the present invention is not limited by the order of acts, as some steps may occur in other orders or concurrently in accordance with the invention. Further, those skilled in the art should also appreciate that the embodiments described in the specification are preferred embodiments and that the acts and modules referred to are not necessarily required by the invention.

Through the above description of the embodiments, those skilled in the art can clearly understand that the method according to the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but the former is a better implementation mode in many cases. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which is stored in a storage medium (e.g., ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal device (e.g., a mobile phone, a computer, a server, or a network device) to execute the method according to the embodiments of the present invention.

Example 2

According to the fourth aspect described above, fig. 6 shows a schematic diagram of a processing apparatus of logistics document information according to the first aspect of embodiment 2 of the present disclosure, and this apparatus 600 corresponds to the processing method of providing logistics document information according to fig. 3. Referring to fig. 6, the apparatus 600 includes:

the document information acquiring module 601 is configured to acquire document information of a target document associated with a logistics service, where the document information includes service data information and/or logistics data information associated with the target document;

a hierarchical code generation module 602, configured to generate a hierarchical code of the target document according to a service hierarchy of the target document in the logistics service; and

a hierarchical code association module 603, configured to associate a hierarchical code of the target document with document information of the target document.

Optionally, the apparatus further includes a document data classification module, configured to, in a case where the type of the target document is an order, include the business data information associated with the target document; and in the case that the type of the target document is the waybill, the document information comprises business data information and logistics data information which are associated with the target document.

Optionally, the hierarchical code associating apparatus 603 is specifically configured to: and generating logistics data structure information corresponding to the target document according to the level code of the target document and the document information of the target document.

Optionally, a document information query module is further included. The query instruction is used for receiving a query instruction, wherein the query instruction comprises service data information to be queried; acquiring document information and a hierarchical code of a target document matched with the service data information to be inquired according to the service data information to be inquired; and acquiring the document information of the associated waybill of the target document according to the level code of the target document and the document information.

Optionally, the document information query module is specifically configured to: and under the condition that the type of the target document is determined to be the shipping bill according to the document information of the target document, determining the document information of the target document as the document information of the associated shipping bill.

Optionally, the document information query module is further specifically configured to: under the condition that the type of the target document is determined to be an order according to the document information of the target document, acquiring the document information of the waybill of the hierarchical code containing the hierarchical code of the target document in the hierarchical code; and determining the acquired documentary information of the waybill as documentary information of the associated waybill.

Optionally, the apparatus further includes a logistics data information determining module: and the logistics data information related to the target documents is determined according to the document information related to the waybill.

According to the technical solution of the embodiment, the logistics platform system 100 obtains the document information of the target document associated with the logistics business, wherein the document information includes business data information and/or logistics data information associated with the target document. Generating a level code of the target document according to the service level of the target document in the logistics service; and associating the hierarchical code of the target document with the document information of the target document, wherein the hierarchical code of the target document is the designated identification under the condition that the target document is the initial document of the logistics service. In the case that the target document is not the starting document of the logistics business, the hierarchical code of the target document comprises: the hierarchical code of the upper level document of the target document and the peer identification code in the peer document of the target document under the upper level document. According to the level code associated with the target document information, the logistics platform system 100 can acquire the logistics data information associated with the target document by querying document information corresponding to all documents corresponding to the level code, and does not need to perform multiple logistics queries to splice multiple query information, so that the efficiency of querying the logistics data information in the logistics platform system is improved.

The device for processing logistics document information provided by the embodiment of the application can realize the processes in the embodiments mentioned in the first aspect, and achieve the same functions and effects, and is not repeated here.

According to the fifth aspect, fig. 7 is a schematic diagram of an inquiring apparatus for logistics data information according to the second aspect of embodiment 2 of the present disclosure, and the apparatus 700 corresponds to the inquiring method for logistics data information provided according to fig. 5. Referring to fig. 7, the apparatus 700 includes:

a query instruction receiving module 701, configured to receive a query instruction related to a logistics service, where the query instruction includes service data information to be queried;

a hierarchical code obtaining module 702, configured to obtain, according to the service data information to be queried, document information and a hierarchical code of a target document that matches the queried service data information, where the document information includes service data information and/or logistics data information associated with the target document, and the hierarchical code is generated according to a service hierarchy of the target document in the logistics service;

the associated document acquiring module 703 is configured to acquire document information of an associated waybill of the target document according to the hierarchical code of the target document and the document information; and

and the logistics data determining module 704 is used for determining logistics data information associated with the target document according to the document information of the associated waybill.

Optionally, the associated document acquiring module 703 is specifically configured to:

and under the condition that the type of the target document is determined to be the waybill according to the document information of the target document, determining the logistics data information in the document information of the target document as the logistics data information associated with the target document.

Optionally, the associated document acquiring module 703 is further specifically configured to:

under the condition that the type of the target document is determined to be an order according to the document information of the target document, acquiring the document information of the waybill of the hierarchical code containing the hierarchical code of the target document in the hierarchical code; and

and determining the logistics data information corresponding to the acquired documentary information of the waybill as the logistics data information associated with the target documentary.

According to the logistics data structure information base, the logistics data information corresponding to the freight notes associated with the target documents can be inquired in the logistics data structure information base through the level codes corresponding to the target documents, and therefore information splicing is carried out without multi-layer inquiry, and the work efficiency of inquiring the logistics data is improved.

The logistics data information query device provided by the embodiment of the application can implement the processes in the embodiments mentioned in the second aspect, and achieve the same functions and effects, which are not repeated here.

Example 3

Referring to a sixth aspect described in this embodiment, fig. 8 shows a schematic diagram of an apparatus for processing logistics document information according to the first aspect of embodiment 3 of the present disclosure, the apparatus 800 corresponding to the method according to the first aspect of embodiment 1. Referring to fig. 8, the apparatus 800 includes: a first processor 810; and a first memory 820 coupled to the first processor 810 for providing instructions to the first processor 810 to process the following process steps:

and associating the hierarchical code of the target document with document information of the target document.

Optionally, the apparatus 800 further comprises: in the case that the type of the target document is an order, the document information includes business data information associated with the target document; and

in the case that the type of the target document is a waybill, the document information includes business data information and logistics data information associated with the target document.

Optionally, the apparatus 800 further comprises: receiving a query instruction, wherein the query instruction comprises service data information to be queried;

acquiring document information and a hierarchical code of a target document matched with the service data information to be inquired according to the service data information to be inquired; and

and acquiring the document information of the associated waybill of the target document according to the level code of the target document and the document information.

and determining the acquired documentary information of the freight note as the documentary information of the associated freight note.

Optionally, the apparatus 800 further comprises: and determining logistics data information associated with the target document according to the document information of the associated waybill.

According to the technical scheme of the embodiment, the logistics platform system acquires the document information of the target document associated with the logistics business, wherein the document information comprises business data information and/or logistics data information associated with the target document. Generating a level code of the target document according to the service level of the target document in the logistics service; and associating the hierarchical code of the target document with the document information of the target document, wherein the hierarchical code of the target document is the designated identification under the condition that the target document is the initial document of the logistics service. In the case that the target document is not the starting document of the logistics business, the hierarchical code of the target document comprises: the hierarchical code of the upper level document of the target document and the peer identification code in the peer document of the target document under the upper level document. According to the level code associated with the target document information, the logistics platform system can acquire the logistics data information associated with the target document by inquiring the document information corresponding to all documents corresponding to the level code, and the plurality of inquiry information are spliced without inquiring multi-layer logistics, so that the efficiency of inquiring the logistics data information in the logistics platform system is improved.

According to a seventh aspect provided by this embodiment, fig. 9 shows a schematic diagram of an apparatus for querying logistics data information according to the second aspect of embodiment 3 of this disclosure, where the apparatus 900 corresponds to the method according to the second aspect of embodiment 1. Referring to fig. 9, the apparatus 900 includes: a second processor 910; and a second memory 920, coupled to the second processor 910, for providing instructions to the second processor 910 to process the following steps:

Optionally, acquiring logistics data information of an associated waybill of the target document according to the hierarchical code of the target document and the document information, including:

The query device for logistics data information provided by the embodiment of the application can implement each process in the embodiment mentioned in the foregoing second aspect, and achieve the same functions and effects, which are not repeated here.

The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.

In the above embodiments of the present invention, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.

In the embodiments provided in the present application, it should be understood that the disclosed technology can be implemented in other ways. The above-described embodiments of the apparatus are merely illustrative, and for example, the division of the units is only one type of division of logical functions, and there may be other divisions when actually implemented, for example, a plurality of units or components may be combined or may be integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, units or modules, and may be in an electrical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a removable hard disk, a magnetic or optical disk, and other various media capable of storing program codes.

The foregoing is only a preferred embodiment of the present invention, and it should be noted that, for those skilled in the art, various modifications and decorations can be made without departing from the principle of the present invention, and these modifications and decorations should also be regarded as the protection scope of the present invention.

Claims

1. The method for processing the logistics document information is characterized by comprising the following steps:

acquiring document information of a target document associated with logistics business, wherein the document information comprises business data information and/or logistics data information associated with the target document;

Under the condition that the target document is the initial document of the logistics service, the level code of the target document is a designated identification; and

in the case that the target document is not the starting document of the logistics business, the hierarchical code of the target document comprises: the target document comprises a hierarchical code of a previous-level document of the target document and a peer identification code of the target document in a peer document under the previous-level document.

2. The method of claim 1, comprising:

in the case that the type of the target document is an order, the document information includes business data information associated with the target document; and

and under the condition that the type of the target document is the freight note, the document information comprises business data information and logistics data information which are associated with the target document.

3. The method of claim 2, wherein associating the hierarchical code of the target document with the document information of the target document comprises generating logistics data structure information corresponding to the target document according to the hierarchical code of the target document and the document information of the target document.

4. The method of claim 2 or 3, further comprising:

receiving a query instruction, wherein the query instruction comprises service data information to be queried;

acquiring document information and a hierarchical code of the target document matched with the service data information to be inquired according to the service data information to be inquired; and

5. The method of claim 4, wherein the operation of obtaining the documentation information of the associated waybill of the target document according to the hierarchical code of the target document and the document information comprises:

and under the condition that the type of the target document is determined to be the waybill according to the document information of the target document, determining the document information of the target document as the document information of the associated waybill.

6. The method of claim 4, wherein the operation of obtaining the documentation information of the associated waybill of the target document according to the hierarchical code of the target document and the document information further comprises:

under the condition that the type of the target document is determined to be an order according to the document information of the target document, acquiring the document information of a waybill of a hierarchical code containing the hierarchical code of the target document in a hierarchical code; and

7. The method of claim 4, further comprising: and determining logistics data information associated with the target document according to the document information of the associated waybill.

8. The method for inquiring the logistics data information is characterized by comprising the following steps:

acquiring document information and a hierarchical code of a target document matched with the inquired business data information according to the business data information to be inquired, wherein the document information comprises business data information and/or logistics data information associated with the target document, and the hierarchical code is generated according to a business hierarchy of the target document in the logistics business;

9. The method of claim 8, wherein obtaining logistics data information of the waybill associated with the target document according to the hierarchical code of the target document and document information comprises:

and under the condition that the type of the target document is determined to be the waybill according to the document information of the target document, determining the logistics data information in the document information of the target document to be the logistics data information associated with the target document.

10. The method of claim 8, wherein obtaining logistics data information of the waybill associated with the target document according to the level code of the target document and document information further comprises: