A method, device and storage medium for automatically associating terminal agent points

Abstract

An embodiment of the present invention provides a method for automatically associating terminal agent points, which belongs to the technical field of express delivery. The method includes: putting an express parcel into a terminal third-party agent point, generating delivery entry and exit information; checking whether the waybill number in the delivery entry and exit information meets the preset waybill number rules, and for the waybill number that meets the preset waybill number rules, sending the delivery entry and exit information to the MQ message queue, obtaining the scanning outlet and the scanner number information; merging the scanning outlet, the scanner number and the terminal third-party agent point number information in the delivery entry and exit information into one message and sending it to the MQ message queue, asynchronously processing the terminal third-party agent point binding relationship; verifying the terminal third-party agent point binding relationship, and if the verification is successful, updating the terminal third-party agent point binding relationship already in the system Redis cache; this application solves the problem in the prior art that the outlets rely on manual confirmation of the cooperation relationship on the page, which adds additional manual operations.

Description

Technical Field

[0001] The present invention belongs to the technical field of express delivery, and in particular relates to a method, device and storage medium for automatically associating terminal agent points. Background Art

[0002] With the continuous growth in the volume of express parcels, the pressure and challenges faced by salesmen when collecting and delivering packages at the end of the express delivery are also escalating. Existing technologies mainly rely on the operations of salesmen. The routing information is generated based on the salesmen's scanning of the incoming packages, which will lead to a large number of non-standard routes. In addition, the outlets have to manually confirm the cooperative relationship on the page, which adds additional manual operations and is cumbersome. Summary of the Invention

[0003] In order to at least solve the above problems existing in the prior art, the present invention provides a method, device and storage medium for automatically associating terminal agent points.

[0004] The technical solutions provided by the present invention are as follows:

[0005] A method for automatically associating terminal agent points, the method comprising:

[0006] Deliver the express to the third-party agency at the end and generate the delivery entry and exit information;

[0007] Check whether the waybill number in the delivery inbound and outbound information meets the preset waybill number rules. If the waybill number meets the preset waybill number rules, send the delivery inbound and outbound information to the MQ message queue;

[0008] Obtaining the scanning point and the scanner number according to the first query method; when the first query method fails to obtain the scanning point and the scanner number, using the second query method to obtain the scanning point and the scanner number information; when the second query method fails to obtain the scanning point and the scanner number information, using the third query method to obtain the scanning point and the scanner number information;

[0009] According to the scanning network point and scanner number information obtained by the first query method, the second query method, or the third query method, the scanning network point, the scanner number, and the terminal third-party agent point number information in the delivery inbound and outbound information are combined into a message and sent to the MQ message queue to asynchronously process the terminal third-party agent point binding relationship;

[0010] The terminal third-party proxy point binding relationship is verified. If the verification is successful, the terminal third-party proxy point binding relationship already in the system Redis cache is updated.

[0011] Furthermore, the delivery entry and exit information includes the waybill number, entry and exit status, the terminal third-party agency point number, and the province, city, district and detailed address of the terminal third-party agency point.

[0012] Furthermore, the first query method includes:

[0013] After the system consumer obtains the delivery entry and exit information from the MQ message queue, it calls the waybill track interface according to the waybill number, obtains the last scan information in the waybill track, and obtains the scanning point and scanner number in the last scan information.

[0014] Furthermore, the second query method includes:

[0015] Obtain the three-segment code interface of the delivery point according to the waybill number, and obtain the scanning point and scanner number information in the three-segment code interface.

[0016] Furthermore, the third query method includes:

[0017] According to the terminal third-party agency point number in the delivery inbound and outbound information, the existing scanning point and scanner number information are queried in the system Redis cache.

[0018] Furthermore, the verification of the terminal third-party agent point binding relationship includes:

[0019] The system consumer obtains the terminal tripartite proxy point binding relationship from the MQ message queue;

[0020] Call the waybill track interface according to the waybill number, obtain the scanning time of the last scanned information in the waybill track, calculate the difference between the scanning time and the current time, and if the time difference exceeds the preset specified time, the verification fails;

[0021] Based on the scanning outlet information in the terminal third-party agency binding relationship, the outlet basic data interface is called to obtain the outlet province, city, and district data, and the outlet province, city, and district data are compared with the terminal third-party agency province, city, and district data in the delivery inbound and outbound information to see if they are consistent. If the data are inconsistent, the verification fails;

[0022] If the time difference does not exceed the preset set time, and the province, city, and district data of the outlet are consistent with the province, city, and district data of the terminal third-party agency in the delivery inbound and outbound information, the verification is successful.

[0023] A device for automatically associating terminal agent points, the device comprising:

[0024] Parcel delivery inbound and outbound information generation module: used to deliver express parcels to the terminal third-party agency point and generate parcel delivery inbound and outbound information;

[0025] Verification module: used to verify whether the waybill number in the delivery inbound and outbound information meets the preset waybill number rules. For waybill numbers that meet the preset waybill number rules, the delivery inbound and outbound information is sent to the MQ message queue;

[0026] Scanning point and scanner number acquisition module: used to obtain the scanning point and the scanner number according to the first query method, and when the first query method fails to obtain the scanning point and the scanner number, use the second query method to obtain the scanning point and the scanner number information, and when the second query method fails to obtain the scanning point and the scanner number information, use the third query method to obtain the scanning point and the scanner number information;

[0027] The terminal third-party agent point binding module is used to combine the scanning point and scanner number information obtained by the first query method, the second query method, or the third query method into a single message, send it to the MQ message queue, and asynchronously process the terminal third-party agent point binding relationship.

[0028] Verification and update module: used to verify the terminal third-party proxy point binding relationship. If the verification is successful, the terminal third-party proxy point binding relationship already in the system Redis cache is updated.

[0029] A storage medium stores a computer program, and when the computer program is executed by a processor, each step of the method for automatically associating terminal agent points is implemented.

[0030] The beneficial effects of the present invention are:

[0031] The present invention automatically obtains the scanning point and scanner number information based on the delivery entry and exit information, and verifies the scanning point, scanner number and the terminal third-party agency point number information. If the verification is successful, the three-party binding relationship is automatically updated, avoiding the problem of relying on the branch to manually confirm the cooperative relationship on the page in the existing technology, which adds additional manual operations. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0033] Figure 1 A flowchart of a method for automatically associating terminal agent points provided by an embodiment of the present invention;

[0034] Figure 2 A schematic diagram of the terminal third-party proxy point binding relationship verification process provided by an embodiment of the present invention;

[0035] Figure 3 A system diagram of a device for automatically associating terminal agent points provided by an embodiment of the present invention;

[0036] Reference numerals:

[0037] 1- Delivery entry and exit information generation module, 2- Inspection module, 3- Scanning point and scanner number acquisition module, 4- Terminal third-party agent point binding module, 5- Verification update module. DETAILED DESCRIPTION

[0038] To make the objectives, technical solutions, and advantages of the present invention more apparent, the technical solutions of the present invention will be described in detail below. Obviously, the embodiments described are only some of the embodiments of the present invention, not all of them. Based on the embodiments of the present invention, all other implementations obtained by those of ordinary skill in the art without inventive effort are within the scope of protection of the present invention.

[0039] In the existing technology, parcel scanning mainly relies on the operation of the salesperson. Generating routing information based on the salesperson's scanning of the parcels will result in a large number of irregular routes. In addition, the branch has to manually confirm the cooperative relationship on the page, which adds additional manual operations and is cumbersome.

[0040] In order to at least solve the technical problem raised in the present invention, an embodiment of the present invention provides a method for automatically associating terminal proxy points.

[0041] Figure 1 A flowchart of a method for automatically associating terminal agent points provided by an embodiment of the present invention; as shown in the attached figure Figure 1 As shown, the method includes:

[0042] S1: Deliver the express to the third-party agent at the terminal and generate the inbound and outbound information;

[0043] S2, checking whether the waybill number in the inbound and outbound delivery information meets the preset waybill number rules. If the waybill number meets the preset waybill number rules, the inbound and outbound delivery information is sent to the MQ message queue;

[0044] S3, obtaining the scanning point and the scanner number according to the first query method, and when the first query method fails to obtain the scanning point and the scanner number, using the second query method to obtain the scanning point and the scanner number information, and when the second query method fails to obtain the scanning point and the scanner number information, using the third query method to obtain the scanning point and the scanner number information;

[0045] S4, based on the scanning point and scanner ID information obtained by the first query method, the second query method, or the third query method, the scanning point, the scanner ID, and the terminal third-party agent ID information in the delivery inbound and outbound information are combined into a single message and sent to the MQ message queue, asynchronously processing the terminal third-party agent binding relationship;

[0046] S5, verifying the terminal third-party proxy point binding relationship. If the verification succeeds, updating the terminal third-party proxy point binding relationship already in the system Redis cache;

[0047] Specifically, the salesperson puts the express delivery into the terminal third-party agency point, generates a delivery entry and exit information, verifies whether the delivery waybill number conforms to the ZTO delivery waybill number rules through the waybill number in the delivery entry and exit information, and sends the delivery entry and exit information of the waybill number that conforms to the verification rules to the MQ message queue for asynchronous processing, and obtains the scanning point and scanner number information through the first query method. If the first query method does not obtain the scanning point and scanner number information, the second query method is used to obtain the information. If the first query method and the second query method do not obtain the scanning point and scanner number information, the third query method is used. In terms of the accuracy of the data obtained, the first query method is better than the second query method. The query method is good, and the second query method is better than the third query method. The queried scanning outlets, scanner numbers and the terminal third-party agent point numbers in the delivery in and out information are combined into a message and sent to the MQ message queue, and the terminal third-party agent point binding relationship is processed asynchronously. The terminal third-party agent point binding relationship is verified. If the verification is qualified, the scanning outlets and scanner numbers, and the terminal third-party agent point number binding relationship saved in the system Redis cache are cleared, and new data is rewritten to realize the update of the terminal third-party agent point binding relationship. Through this application, there is no need for sales staff to manually confirm the cooperation relationship on the page with the outlets, which improves the delivery efficiency and reduces errors caused by human factors.

[0048] Furthermore, the delivery inbound and outbound information includes the waybill number, inbound and outbound status, the terminal third-party agency point number, and the province, city, district and detailed address of the terminal third-party agency point;

[0049] Specifically, the delivery entry and exit information includes the waybill number, entry and exit status, the terminal third-party agent point number, and the province, city, district and detailed address of the terminal third-party agent point. The waybill number information is used to determine whether it meets the preset waybill number rules. The terminal third-party agent point number is used to generate a terminal third-party agent point binding relationship with the scanning outlet and the scanner number. The terminal third-party agent point province, city, district and detailed address are used to verify the generated terminal third-party agent point binding relationship.

[0050] Furthermore, the first query method includes:

[0051] After the system consumer obtains the delivery entry and exit information from the MQ message queue, it calls the waybill track interface according to the waybill number, obtains the last scan information in the waybill track, and obtains the scanning point and scanner number in the last scan information.

[0052] Furthermore, the second query method includes:

[0053] Obtain the three-segment code interface of the delivery point according to the waybill number, and obtain the scanning point and scanner number information in the three-segment code interface.

[0054] Furthermore, the third query method includes:

[0055] According to the terminal third-party agency point number in the delivery inbound and outbound information, the existing scanning point and scanner number information are queried in the system Redis cache.

[0056] Specifically, as attached Figure 2 As shown, this application also discloses the binding relationship between the terminal three-party agent points

[0057] The verification process includes:

[0058] S501, the system consumer obtains the terminal tripartite proxy point binding relationship from the MQ message queue;

[0059] S502: Call the waybill track interface according to the waybill number, obtain the scanning time of the last scanned information in the waybill track, calculate the time difference between the scanning time and the current time, and if the time difference exceeds the preset specified time, the verification fails;

[0060] S503: Based on the scanned branch information in the terminal third-party agency binding relationship, the branch basic data interface is called to obtain the branch's province, city, and district data. The branch's province, city, and district data is compared with the terminal third-party agency's province, city, and district data in the delivery inbound and outbound information to see if they are consistent. If the data are inconsistent, the verification fails.

[0061] If the time difference does not exceed the preset time, and the province, city, and district data of the outlet are consistent with the province, city, and district data of the terminal third-party agency in the delivery inbound and outbound information, the verification is successful;

[0062] Specifically, the time difference between the scanning time and the current time is compared with the preset specified time. If it exceeds the preset specified time, the verification fails, and the scanning outlets and scanner numbers, and the terminal third-party agent point number binding relationship saved in the system Redis cache are not updated. At the same time, the outlet province, city, and district data are compared with the terminal third-party agent point province, city, and district data. If they are inconsistent, the verification fails, and the scanning outlets and scanner numbers, and the terminal third-party agent point number binding relationship saved in the system Redis cache are not updated. On the contrary, if the above two verifications are passed, it means that the terminal third-party agent point binding relationship verification is successful, then the scanning outlets and scanner numbers, and the terminal third-party agent point number binding relationship saved in the system Redis cache are cleared, and new data is rewritten.

[0063] Specifically, as attached Figure 3 As shown, the present application also discloses a device for automatically associating terminal agent points, the device comprising:

[0064] Parcel delivery inbound and outbound information generation module 1: used to deliver the express parcel to the terminal third-party agency point and generate parcel delivery inbound and outbound information;

[0065] Verification module 2: used to verify whether the waybill number in the delivery inbound and outbound information meets the preset waybill number rules. If the waybill number meets the preset waybill number rules, the delivery inbound and outbound information is sent to the MQ message queue;

[0066] Scanning point and scanner number acquisition module 3: used to acquire the scanning point and the scanner number according to the first query method, and when the first query method fails to acquire the scanning point and the scanner number, adopt the second query method to acquire the scanning point and the scanner number information, and when the second query method fails to acquire the scanning point and the scanner number information, adopt the third query method to acquire the scanning point and the scanner number information;

[0067] The terminal third-party agent point binding module 4 is used to combine the scanning point and scanner number information obtained by the first query method, the second query method, or the third query method into a single message, send the information to the MQ message queue, and asynchronously process the terminal third-party agent point binding relationship.

[0068] Verification and update module 5: used to verify the terminal third-party proxy point binding relationship. If the verification is successful, the terminal third-party proxy point binding relationship already in the system Redis cache is updated.

[0069] A storage medium stores a computer program, and when the computer program is executed by a processor, each step of the method for automatically associating terminal agent points is implemented.

[0070] The above description is merely a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any modifications or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in the present invention should be included in the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be based on the scope of protection of the claims.

[0071] It can be understood that the same or similar parts of the above embodiments can be referenced to each other, and the contents not described in detail in some embodiments can refer to the same or similar contents in other embodiments.

[0072] It should be noted that, in the description of the present invention, the terms "first", "second", etc. are used for descriptive purposes only and should not be understood as indicating or implying relative importance. In addition, in the description of the present invention, unless otherwise specified, the meaning of "plurality" is at least two.

[0073] Any process or method description in a flowchart or otherwise described herein may be understood to represent a module, segment or portion of code comprising one or more executable instructions for implementing the steps of a specific logical function or process, and the scope of the preferred embodiments of the present invention includes alternative implementations in which functions may be performed out of the order shown or discussed, including performing functions in a substantially simultaneous manner or in the reverse order depending on the functions involved, which should be understood by those skilled in the art to which the embodiments of the present invention pertain.

[0074] It should be understood that various parts of the present invention can be implemented using hardware, software, firmware, or a combination thereof. In the above-described embodiments, multiple steps or methods can be implemented using software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented using hardware, as in another embodiment, any one of the following technologies known in the art or a combination thereof can be used: a discrete logic circuit having a logic gate circuit for implementing a logic function on a data signal, an application-specific integrated circuit having a suitable combination of logic gate circuits, a programmable gate array (PGA), a field programmable gate array (FPGA), etc.

[0075] Those skilled in the art will understand that all or part of the steps in the method of the above embodiment can be completed by instructing related hardware through a program, and the program can be stored in a computer-readable storage medium. When the program is executed, it includes one or a combination of the steps of the method embodiment.

[0076] In addition, the functional units in the various embodiments of the present invention may be integrated into a single processing module, or each unit may exist physically separately, or two or more units may be integrated into a single module. The aforementioned integrated modules may be implemented in the form of hardware or in the form of software functional modules. If the integrated modules are implemented in the form of software functional modules and sold or used as independent products, they may also be stored in a computer-readable storage medium.

[0077] The storage medium mentioned above can be a read-only memory, a magnetic disk or an optical disk, etc.

[0078] Throughout this specification, reference to terms such as "one embodiment," "some embodiments," "examples," "specific examples," or "some examples" means that a specific feature, structure, material, or characteristic described in conjunction with that embodiment or example is included in at least one embodiment or example of the present invention. In this specification, schematic representations of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples.

[0079] Although the embodiments of the present invention have been shown and described above, it will be understood that the above embodiments are illustrative and are not to be construed as limitations on the present invention. A person skilled in the art may change, modify, replace and modify the above embodiments within the scope of the present invention.

Claims

1. A method for automatically associating terminal agent points, characterized in that: The method comprises: Deliver the express to the third-party agency at the end and generate the delivery entry and exit information; Check whether the waybill number in the delivery inbound and outbound information meets the preset waybill number rules. If the waybill number meets the preset waybill number rules, send the delivery inbound and outbound information to the MQ message queue; Obtaining the scanning point and the scanner number according to the first query method; when the first query method fails to obtain the scanning point and the scanner number, using the second query method to obtain the scanning point and the scanner number information; when the second query method fails to obtain the scanning point and the scanner number information, using the third query method to obtain the scanning point and the scanner number information; The first query method includes: After the system consumer obtains the delivery inbound and outbound information from the MQ message queue, it calls the waybill track interface according to the waybill number to obtain the last scan information in the waybill track, and obtains the scanning point and scanner number in the last scan information; The second query method includes: Obtain the three-segment code interface of the delivery outlet according to the waybill number, and obtain the scanning outlet and scanner number information in the three-segment code interface; The third query method includes: According to the terminal third-party agent point number in the delivery inbound and outbound information, the system Redis cache is searched for existing scanning point and scanner number information; According to the scanning network point and scanner number information obtained by the first query method, the second query method, or the third query method, the scanning network point, the scanner number, and the terminal third-party agent point number information in the delivery inbound and outbound information are combined into a message and sent to the MQ message queue to asynchronously process the terminal third-party agent point binding relationship; The terminal third-party proxy point binding relationship is verified. If the verification is successful, the terminal third-party proxy point binding relationship already in the system Redis cache is updated.

2. The method for automatically associating terminal agent points according to claim 1, characterized in that: The delivery inbound and outbound information includes the waybill number, inbound and outbound status, the terminal third-party agency point number, and the province, city, district and detailed address of the terminal third-party agency point.

3. The method for automatically associating terminal agent points according to claim 2, characterized in that: The verification of the terminal three-party proxy point binding relationship includes: The system consumer obtains the terminal tripartite proxy point binding relationship from the MQ message queue; Call the waybill track interface according to the waybill number, obtain the scanning time of the last scanned information in the waybill track, calculate the difference between the scanning time and the current time, and if the time difference exceeds the preset specified time, the verification fails; Based on the scanning outlet information in the terminal third-party agency binding relationship, the outlet basic data interface is called to obtain the outlet province, city, and district data, and the outlet province, city, and district data are compared with the terminal third-party agency province, city, and district data in the delivery inbound and outbound information to see if they are consistent. If the data are inconsistent, the verification fails; If the time difference does not exceed the preset set time, and the province, city, and district data of the outlet are consistent with the province, city, and district data of the terminal third-party agency in the delivery inbound and outbound information, the verification is successful.

4. A device for automatically associating terminal agent points, characterized in that: The device comprises: Parcel delivery inbound and outbound information generation module: used to deliver express parcels to the terminal third-party agency point and generate parcel delivery inbound and outbound information; Verification module: used to verify whether the waybill number in the delivery inbound and outbound information meets the preset waybill number rules. For waybill numbers that meet the preset waybill number rules, the delivery inbound and outbound information is sent to the MQ message queue; Scanning point and scanner number acquisition module: used to obtain the scanning point and the scanner number according to the first query method, and when the first query method fails to obtain the scanning point and the scanner number, use the second query method to obtain the scanning point and the scanner number information; when the second query method fails to obtain the scanning point and the scanner number information, use the third query method to obtain the scanning point and the scanner number information; The first query method includes: After the system consumer obtains the delivery inbound and outbound information from the MQ message queue, it calls the waybill track interface according to the waybill number to obtain the last scan information in the waybill track, and obtains the scanning point and scanner number in the last scan information; The second query method includes: Obtain the three-segment code interface of the delivery outlet according to the waybill number, and obtain the scanning outlet and scanner number information in the three-segment code interface; The third query method includes: According to the terminal third-party agent point number in the delivery inbound and outbound information, the system Redis cache is searched for existing scanning point and scanner number information; The terminal third-party agent point binding module is used to combine the scanning point and scanner number information obtained by the first query method, the second query method, or the third query method into a single message, send it to the MQ message queue, and asynchronously process the terminal third-party agent point binding relationship. Verification and update module: used to verify the terminal third-party proxy point binding relationship. If the verification is successful, the terminal third-party proxy point binding relationship already in the system Redis cache is updated.

5. A storage medium, characterized in that The storage medium stores a computer program, and when the computer program is executed by a processor, each step of the method for automatically associating terminal agent points according to any one of claims 1 to 3 is implemented.

Images