Waybill processing method, electronic device and storage medium

Abstract

The present application discloses a waybill processing method, electronic device and storage medium. The method comprises: obtaining the dispatch result of the waybill to be dispatched; the dispatch result comprises the waybill, the candidate delivery resources of the waybill and the pricing information matching the candidate delivery resources; generating a person-price data relationship model according to the dispatch result and the waybill information of the waybill; the person-price data relationship model is stored in a memory database and is used to obtain the person-price relationship data corresponding to the delivery resource according to the delivery resource; determining the target delivery resource for pulling the waybill, obtaining the person-price relationship data corresponding to the target delivery resource based on the person-price data relationship model according to the target delivery resource, and generating the waybill pulling result of the target delivery resource. The method solves the problem of how to improve the performance of waybill dispatch processing.

Description

Technical Field

[0001] The present application relates to the field of computer processing technology, and more particularly to a waybill processing method, electronic device and storage medium. The present application also relates to another waybill processing method, electronic device and storage medium. Background Art

[0002] With the development of e-commerce, more and more people shop online, such as ordering food online, buying daily necessities online, running errands, home delivery services, etc., which has led to an increasing volume of delivery, which has promoted the development of the delivery field to a certain extent. With the development of the delivery field, the model of delivery resources independently selecting waybills for delivery has gradually been widely used, so how to improve the performance of pulling candidate waybills is particularly important.

[0003] In the prior art, the dispatch results of the waybills to be dispatched are generally stored in a persistent database. When the distribution resources pull candidate waybills through the client application, they query the dispatch results in the persistent database to obtain the candidate waybills. However, during the peak of waybill production or pulling, there may be a large amount of traffic. It is difficult to ensure a high-speed pull effect for waybill dispatch by accessing the persistent database. In addition, the maintenance cost of the persistent database is also high.

[0004] Therefore, how to improve the processing performance of waybill dispatch is a problem that needs to be solved. Summary of the invention

[0005] The waybill processing method provided in the embodiment of the present application solves the problem of how to improve the performance of waybill dispatch processing.

[0006] An embodiment of the present application provides a waybill processing method, including: obtaining a dispatch result of a waybill that needs to be dispatched; the dispatch result includes the waybill, candidate delivery resources of the waybill, and pricing information matching the candidate delivery resources; generating a person-price data relationship model based on the dispatch result and the waybill information of the waybill; the person-price data relationship model is stored in a memory database and is used to obtain person-price relationship data corresponding to the delivery resource based on the delivery resource; determining a target delivery resource that needs to pull the waybill, obtaining the person-price relationship data corresponding to the target delivery resource based on the person-price data relationship model based on the target delivery resource, and generating a waybill pulling result for the target delivery resource.

[0007] Optionally, generating a person-unit-price data relationship model based on the scheduling result and the waybill information of the waybill includes: determining a first matching relationship between distribution resources and waybills, and a second matching relationship between waybills and pricing information based on the scheduling result; forming a first key-value pair based on the first matching relationship and the waybill information of the waybill, and forming a second key-value pair based on the second matching relationship and the waybill information of the waybill; using the first key-value pair and the second key-value pair as associated data of corresponding attribute information in the person-unit-price data relationship model, respectively, to form the person-unit-price data model; wherein the first key-value pair, the second key-value pair and the person-unit-price data relationship model are stored in the memory database.

[0008] Optionally, the first key-value pair is formed based on the first matching relationship and the waybill information of the waybill, including: generating a first key based on the delivery resources in the first matching relationship; determining the storage value corresponding to the first key according to the waybill information of the waybill that matches the delivery resources in the first matching relationship, to form the first key-value pair.

[0009] Optionally, the second key-value pair is formed based on the second matching relationship and the waybill information of the waybill, including: generating a second key based on the waybill in the second matching relationship; determining the storage value corresponding to the second key according to the pricing information matched with the waybill in the second matching relationship, to form the second key-value pair.

[0010] Optionally, obtaining the person-unit-price relationship data corresponding to the target distribution resource based on the person-unit-price data relationship model according to the target distribution resource includes: determining a first target key value of a first key corresponding to the target distribution resource based on the person-unit-price relationship attribute information in the person-unit-price data relationship model of the target distribution resource; obtaining a first target storage value corresponding to the first target key value and stored in a memory database, the first target storage value including waybill data of one or more waybills corresponding to the target distribution resource and their corresponding scheduling data; determining a second target key value of a second key corresponding to the target distribution resource based on the unit-price relationship attribute information in the person-unit-price data relationship model of the target distribution resource; obtaining a second target storage value corresponding to the second target key value and stored in the memory database, the second target storage value including the pricing data of the one or more waybills; and constituting the person-unit-price relationship data corresponding to the target distribution resource based on the waybill data of the one or more waybills and their corresponding scheduling data, as well as the pricing data of the one or more waybills.

[0011] Optionally, obtaining the dispatch result of the waybill that needs to be dispatched includes: obtaining the waybill that needs to be dispatched according to the waybill status; determining the capacity type and / or delivery area of ​​the waybill, and determining the candidate delivery resources of the waybill according to at least one of the capacity type and the delivery area; determining the pricing information of the waybill that matches the candidate delivery resources according to the waybill and the candidate delivery resources; generating the dispatch result of the waybill based on the waybill, the candidate delivery resources and the pricing information that matches the candidate delivery resources.

[0012] Optionally, the dispatch result of the waybill is generated by a dispatch server; obtaining the dispatch result of the waybill that needs to be dispatched includes: obtaining a call request from the dispatch server for pushing the dispatch result to the fulfillment server that executes the method; the fulfillment server passes the call request to a pre-created asynchronous thread pool corresponding to the waybill dispatch type according to the waybill dispatch type of the waybill contained in the call request, and one of the threads in the asynchronous thread pool obtains the dispatch result according to the waybill call request.

[0013] Optionally, the method further includes: obtaining the waybill dispatching rules of the waybill; determining a specific time period in the waybill dispatching rules that matches the current time; and setting the waybill dispatching type of the waybill according to the waybill dispatching type corresponding to the specific time period.

[0014] Optionally, the method also includes: receiving order grabbing requests for the waybill from multiple delivery resources; in response to the order grabbing request from a first delivery resource among the multiple delivery resources, locking the waybill and assigning it to the first delivery resource, and deleting data related to the waybill in the person-price relationship data of the first delivery resource according to the person-price data relationship model.

[0015] Optionally, the method also includes: generating single-person relationship data based on the scheduling result of the waybill; after assigning the waybill to the first delivery resource, determining candidate delivery resources that match the waybill based on the single-person relationship data, and for each delivery resource among the candidate delivery resources, deleting the data related to the waybill according to the person-price data relationship model.

[0016] An embodiment of the present application also provides a waybill processing method, including: obtaining information of a target delivery resource for which a waybill needs to be pulled; detecting an order pool viewing instruction for the target delivery resource, and sending a waybill pulling request to a server according to the order pool viewing instruction; obtaining a waybill pulling result of the target delivery resource returned by the server in response to the waybill pulling request, extracting information of candidate waybills from the waybill pulling result, and displaying the candidate waybills on a page of the order pool; wherein the waybill pulling result is generated by the server obtaining person-unit-price relationship data according to the target delivery resource and a person-unit-price data relationship model stored in a memory database in response to the waybill pulling request, and extracting waybill data from the person-unit-price relationship data.

[0017] Optionally, the method also includes: detecting that the target delivery resource selects a diffused first target waybill from the candidate waybills to grab the order, and sending a grab request for the first target waybill to the server; and / or detecting that the target delivery resource selects a designated second target waybill from the candidate waybills to accept the order, and sending a confirmation request for the second target waybill to the server; adding the first target waybill and / or the second target waybill to the delivery task of the target delivery resource.

[0018] An embodiment of the present application further provides an electronic device, comprising: a memory, and a processor; the memory is used to store a computer program, and after the computer program is run by the processor, the method provided in the embodiment of the present application is executed.

[0019] The embodiment of the present application also provides a computer storage medium storing computer execution instructions, which are used to implement the method provided in the embodiment of the present application when executed by a processor.

[0020] Compared with the prior art, this application has the following advantages:

[0021] The embodiments of the present application provide a waybill processing method, device, electronic device and storage medium, which obtains the dispatch result of the waybill that needs to be dispatched; the dispatch result includes the waybill, the candidate delivery resources of the waybill and the pricing information matching the candidate delivery resources; generates a person-price data relationship model based on the dispatch result and the waybill information of the waybill; the person-price data relationship model is used to obtain the person-price relationship data corresponding to the delivery resource based on the delivery resource; determines the target delivery resource that needs to pull the waybill, obtains the person-price relationship data corresponding to the target delivery resource based on the person-price data relationship model, and generates the waybill pulling result of the target delivery resource. The person-price data relationship model generated based on the dispatch result is stored in the in-memory database, which can provide high-performance data access and improve the processing performance of waybill dispatch.

[0022] Another waybill processing method, device, electronic device and storage medium provided by the embodiments of the present application obtains information of the target distribution resource for which the waybill needs to be pulled; detects the grab order pool viewing instruction of the target distribution resource, and sends a waybill pulling request to the server according to the grab order pool viewing instruction; obtains the waybill pulling result of the target distribution resource returned by the server in response to the waybill pulling request, extracts information of candidate waybills from the waybill pulling result, and displays the candidate waybills on the grab order pool page; wherein the waybill pulling result is generated by the server obtaining person-unit-price relationship data according to the target distribution resource and the person-unit-price data relationship model stored in the memory database in response to the waybill pulling request, and extracting waybill data from the person-unit-price relationship data. The person-unit-price data relationship model is stored in the memory database, which can provide high-performance data access and improve the processing performance of waybill dispatching. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] Figure 1 It is a processing flow chart of a waybill processing method provided in the first embodiment of the present application;

[0024] Figure 2 This is a schematic diagram of the crowdsourcing waybill dispatching principle provided by the first embodiment of the present application;

[0025] Figure 3 This is a schematic diagram of a person-price data relationship model provided in the first embodiment of the present application;

[0026] Figure 4 is a processing flow chart of a waybill processing method provided in the second embodiment of the present application;

[0027] Figure 5 It is a schematic diagram of a waybill processing device provided in the third embodiment of the present application;

[0028] Figure 6 It is a schematic diagram of a waybill processing device provided in the fourth embodiment of the present application;

[0029] Figure 7 It is a schematic diagram of an electronic device provided by this application. DETAILED DESCRIPTION

[0030] Many specific details are described in the following description to facilitate a full understanding of the present application. However, the present application can be implemented in many other ways than those described herein, and those skilled in the art can make similar generalizations without violating the connotation of the present application, so the present application is not limited by the specific implementation disclosed below.

[0031] The embodiments of the present application provide two waybill processing methods, devices, electronic devices and storage media, which are described one by one in the following embodiments.

[0032] To facilitate understanding, the application scenarios and some concepts of the waybill processing method provided in the embodiment of the present application are first given. In the actual delivery field, an important waybill dispatching mode is the autonomous selection mode, that is, the delivery resources autonomously select waybills for delivery. In the autonomous selection mode, the delivery resources pull candidate waybills from the server through the client application and choose to undertake the delivery task of the target waybill. Each candidate waybill pulled by the delivery resource is displayed on the candidate waybill page, and the candidate waybill page may contain multiple pages. The so-called waybill refers to the delivery information generated in logistics distribution, for example, it can be the delivery information of a group of orders aggregated based on the delivery path, or it can be the delivery information of an order. The so-called delivery resources refer to the resources that execute the delivery of waybills, for example, it can be a rider, or it can be a delivery robot that executes the delivery. The process of a waybill being undertaken by a delivery resource and delivered to the user corresponding to the waybill is the waybill fulfillment process. An example of the self-selection model is the crowdsourcing delivery service in the food delivery industry. Its core feature is that the rider uses the client application to view the candidate waybills corresponding to the rider in the order pool, selects the appropriate target waybill from the candidate waybills, and if the order is successfully selected, the target waybill will be delivered by the rider. The so-called order pool refers to all waybills contained in the page where the rider views the waybills.

[0033] Due to the different processes of assigning waybills to delivery resources, waybill assignment can be divided into two forms: waybill assignment and waybill diffusion. Waybill assignment refers to the process of assigning a waybill to a delivery resource. The delivery resource can confirm to accept the order or confirm not to accept the order. Waybill diffusion refers to the process of assigning a waybill to multiple delivery resources, each of which can initiate an order. The server selects the appropriate delivery resource based on the order of initiation time and / or other scheduling information, and assigns the waybill to the selected delivery resource for delivery.

[0034] It should be noted that the application scenario is merely an embodiment of the application scenario. The purpose of providing this application scenario embodiment is to facilitate the understanding of the waybill processing and dispatching method of the present application, and is not used to limit the waybill processing method of the present application.

[0035] The following combination Figures 1 to 3 The data processing method provided in the first embodiment of the present application is described. Figure 1 The data processing method shown includes: step S101 to step S103.

[0036] Step S101, obtaining the dispatch result of the waybill to be dispatched; the dispatch result includes the waybill, the candidate delivery resources of the waybill and the pricing information matching the candidate delivery resources.

[0037] The waybill processing method provided in the embodiment of the present application can be applied to a server. The server obtains the waybill that needs to be dispatched, matches each waybill with the distribution resource, and determines the pricing information matched by each distribution resource matched with it for each waybill. At least part of the waybills in the waybill that match the target distribution resource are candidate waybills for the target distribution resource. The target distribution resource uses a client application to request the server to pull the candidate waybill, and displays it on the target client corresponding to the target distribution resource. In actual applications, a large number of waybills that need to be dispatched will be generated during the peak period of waybill production, and a large flow of waybill pulls may occur during the peak period of waybill pull, so high-performance data access can ensure high-speed processing of waybills and waybill pull effects during peak periods. In this embodiment, the person-unit price data relationship model and its associated data generated according to the scheduling result are stored in a memory database to provide high-performance data access. The memory database is preferably a Redis database. Based on Redis to store the person-unit price data relationship model and its associated data, the millisecond-level pull effect can be achieved through the high concurrency performance of Redis, and the master-slave replication and keepalive mechanism (keepalive) in the Redis mechanism help to ensure high availability.

[0038] This step is to obtain the dispatch result of the waybill. Wherein, the obtaining of the dispatch result of the waybill that needs to be dispatched includes: obtaining the waybill that needs to be dispatched according to the waybill status; determining the capacity type and / or distribution area of ​​the waybill, and determining the candidate distribution resources of the waybill according to at least one of the capacity type and the distribution area; determining the pricing information of the waybill that matches the candidate distribution resources according to the waybill and the candidate distribution resources; generating the dispatch result of the waybill based on the waybill, the candidate distribution resources and the pricing information that matches the candidate distribution resources. Wherein, determining the pricing information of the waybill that matches the candidate distribution resources according to the waybill and the candidate distribution resources includes: determining the pricing factor of the waybill, and determining the pricing information that matches each candidate distribution resource for each candidate distribution resource of the waybill according to the pricing factor.

[0039] During implementation, the functions of the server to which the method is applied can be decoupled into a scheduling function and a fulfillment function. The scheduling function and the fulfillment function can be implemented as independent scheduling servers and fulfillment servers, respectively, or as scheduling function modules and fulfillment function modules, and this application does not impose any restrictions. Taking the decoupling of the server into a scheduling server and a fulfillment server as an example, the scheduling server determines the scheduling result of the waybill and pushes it to the fulfillment server. The scheduling result includes the matching relationship between the waybill, distribution resources, and pricing information. The pricing information includes at least basic pricing information, and may further include extended pricing information. The so-called extended pricing information can be determined based on the group characteristics of the distribution resources and / or the characteristics of the distribution period. Preferably, the dispatch result of the waybill is generated by a dispatch server; correspondingly, obtaining the dispatch result of the waybill to be dispatched includes: obtaining a call request from the dispatch server for pushing the dispatch result to the fulfillment server that executes the method; the fulfillment server passes the call request to a pre-created asynchronous thread pool corresponding to the waybill dispatch type according to the waybill dispatch type of the waybill contained in the call request, and one of the threads in the asynchronous thread pool obtains the dispatch result according to the waybill call request. During implementation, two asynchronous thread pools, a diffusion thread pool and a dispatch thread pool, can be created to process waybills with diffusion and dispatch types, respectively. The so-called asynchronous thread pool is a technical framework for thread asynchronous or concurrent scenarios. The so-called thread asynchronous means that a call request is sent to the callee, and the caller does not have to wait for the return of its result. Specifically in this embodiment, the diffusion thread in the diffusion thread pool implements an asynchronous diffusion process, which is the process of asynchronously processing diffusion type waybills; the assignment thread in the assignment thread pool implements an asynchronous assignment process, which is the process of asynchronously processing assignment type waybills, so that the scheduling server pushes the scheduling result of the waybill to the fulfillment server without waiting for the processing result of the diffusion thread or assignment thread in the fulfillment server on the scheduling result. Even if the waybill assignment or waybill diffusion of a waybill is unsuccessful, the waybill will still be scheduled to be re-assigned during the next scheduled scheduling.

[0040] In this embodiment, the waybill dispatch type of the waybill is set according to the waybill dispatch form. For example, the waybill dispatch type of the waybill dispatched in the waybill assignment form is set to the assignment type; the waybill dispatch type of the waybill dispatched in the waybill diffusion form is set to the diffusion type. Specifically, the waybill dispatch type can be determined according to the time period characteristics and / or the scheduling round. In one embodiment, it includes: obtaining the waybill dispatch rule of the waybill; determining the specific time period in the waybill dispatch rule that matches the current time; and setting the waybill dispatch type of the waybill according to the waybill dispatch type corresponding to the specific time period. For example, the waybill dispatch rule stipulates that the waybill dispatched in a specific time period 1, such as 3 to 4 pm, has a waybill dispatch type of the assignment type; when scheduling the waybill, if it is judged that the current time is 3:30, the waybill dispatch type is set to the assignment type. For another example, the waybill dispatching rules stipulate that the waybill dispatched during a specific time period 2, such as 5:00 p.m. to 7:00 p.m., is a diffusion type; when dispatching a waybill, if the current time is determined to be 5:30 p.m., the waybill dispatching type is set to a diffusion type. For another example, when dispatching a waybill, if the waybill is determined to be dispatched in the second round, it is set to a diffusion type, regardless of the waybill dispatching type in the first round.

[0041] Please refer to Figure 2, the figure shows a schematic diagram of the crowdsourcing waybill dispatching principle, including: waybill center 201, diversion center 202, crowdsourcing fulfillment server 203, waybill database 204, crowdsourcing scheduling server 205, transportation server 206, pricing server 207, memory database 208, and client 209. Among them, the order receiving server of the waybill center 201 receives the waybill to be dispatched and pushes it to the diversion center 202. The server of the diversion center 202 obtains the transportation service type corresponding to the merchant according to the merchant to which the waybill belongs, such as crowdsourcing delivery, exclusive delivery and other information for diversion. Merchants can pre-customize the corresponding transportation service type according to delivery requirements. Crowdsourcing delivery can also be refined into exclusive crowdsourcing delivery and ordinary crowdsourcing delivery according to the delivery service level. The diversion center 202 diverts the waybill of crowdsourcing delivery to the crowdsourcing fulfillment server 203. The crowdsourcing fulfillment server 203 stores the waybill data of the waybills diverted from the diversion center 202 to the waybill database 204 to achieve decoupling from the diversion center and the waybill center, thereby ensuring that the waybills diverted to the crowdsourcing fulfillment server can be dispatched, and then assigned and delivered. The scheduling server 205 triggers the scheduling task regularly by the scheduling task trigger, such as triggering the scheduling task once every 30 seconds. After the scheduling task of the scheduling server is triggered, it obtains the waybill that needs to be dispatched from the waybill database 204 according to the waybill status, and requests the corresponding candidate delivery resources from the capacity server 206 according to the delivery area and / or the refined capacity type to which the waybill belongs. The refined capacity type includes but is not limited to: exclusive crowdsourcing delivery of crowdsourcing type and ordinary crowdsourcing delivery. The scheduling server 205 inquires the pricing server 207 according to the waybill and the candidate distribution resources corresponding to the waybill, obtains the pricing information of each candidate distribution resource corresponding to the waybill provided by the pricing server 207, and sends the scheduling result including the waybill, each candidate distribution resource and the pricing information matching each candidate resource to the crowdsourcing fulfillment server 203. The crowdsourcing fulfillment server 203 asynchronously processes the scheduling result by the corresponding thread according to the waybill dispatch type of the waybill in the scheduling result, generates a person-unit-price data relationship model according to the scheduling result, and stores the person-unit-price data relationship model and the associated data of the data relationship model in the memory database 208 to improve the performance of data access such as storage / reading. The crowdsourcing fulfillment server 203 receives the waybill pull request sent by the client 209 used by the distribution resource, and sends the information of the candidate waybill corresponding to the distribution resource to the client, so that the distribution resource can view the candidate waybill and facilitate the order grabbing (i.e., self-selection). The client 209 detects the information that triggers the order grabbing for the target waybill among the candidate waybills, and initiates an order grabbing request to the crowdsourcing fulfillment server 203. After the order grabbing is successful, the crowdsourcing fulfillment server 203 deletes the data related to the target waybill in the memory database, and updates the relevant data of the target waybill stored in the waybill database 204, such as the waybill status, information on the delivery resources that successfully grabbed the order, the order grabbing time, etc.

[0042] Step S102, generating a person-price data relationship model according to the dispatch result and the waybill information of the waybill; the person-price data relationship model is stored in a memory database and is used to obtain person-price relationship data corresponding to the distribution resource according to the distribution resource.

[0043] This step is to generate a person-unit-price data relationship model. The person-unit-price data relationship model is a data relationship model used to determine the acquisition path of specific data in the person-unit-price relationship. Its key can be a distribution resource identifier or formed based on the distribution resource identifier and a prefix. The data relationship model contains person-order relationship attribute information and unit-price relationship attribute information. These two types of attribute information are respectively used to determine the data of one or more candidate waybills that match the distribution resource assembled and stored in the memory database according to the scheduling results, so that when it is necessary to obtain candidate waybills that match the distribution resource according to the distribution resource, as well as the data acquisition requirements for the pricing information corresponding to each candidate waybill, the corresponding data can be quickly queried from the memory database. Wherein, the generating of the person-price data relationship model according to the dispatch result and the waybill information of the waybill includes: determining the first matching relationship between the distribution resource and the waybill, and the second matching relationship between the waybill and the pricing information according to the dispatch result; forming a first key-value pair based on the first matching relationship and the waybill information of the waybill, and forming a second key-value pair based on the second matching relationship and the waybill information of the waybill; using the first key-value pair and the second key-value pair as the associated data of the corresponding attribute information in the person-price data relationship model, respectively, to form the person-price data relationship model; wherein the first key-value pair, the second key-value pair and the person-price data relationship model are stored in the memory database. Specifically, the forming of the first key-value pair based on the first matching relationship and the waybill information of the waybill includes: generating a first key based on the distribution resource in the first matching relationship; determining the storage value corresponding to the first key according to the waybill information of the waybill matching the distribution resource in the first matching relationship, to form the first key-value pair. The forming of the second key-value pair based on the waybill information of the second matching relationship and the waybill includes: generating a second key based on the waybill in the second matching relationship; determining the storage value corresponding to the second key according to the pricing information matched with the waybill in the second matching relationship, so as to form the second key-value pair. Among them, the first key-value pair can be understood as the person-order relationship data associated with the person-order relationship attribute information; the second key-value pair can be understood as the unit price relationship data associated with the unit price relationship attribute information. The person-order relationship data and the unit price relationship data constitute the person-unit price relationship data. The person-order relationship data may include the dispatch information of the waybill, and the dispatch information may be specifically the dispatch sorting information for determining the display order of the waybill to be assigned as the candidate waybill, or may be the waybill assignment priority information or the waybill diffusion grab order recommendation priority information. The extended information may also be the delivery prompt information of the recommended delivery path displayed to the delivery resources. The extended information can help the delivery resources make a grab order decision.The unit price relationship data may include pricing information, which includes at least basic pricing information and may also include extended pricing information, so as to facilitate distribution resources to make order grabbing decisions.

[0044] In this embodiment, considering that the query bandwidth for querying the person-unit-price relationship data during the waybill pulling process is large, in order to reduce bandwidth and increase throughput, when the memory database is Redis, the person-order relationship data and the unit-price relationship data that need to be stored in Redis can be serialized and stored separately, and then deserialized after obtaining the query results. Preferably, the protobuf serialization protocol is used for serialization and deserialization. Of course, other algorithms such as the hessian protocol can also be used for serialization to compress bandwidth.

[0045] In this embodiment, it also includes: determining the data length of the person-price relationship data corresponding to the distribution resource according to the person-price data relationship model; judging whether the data length exceeds the preset storage length, and if so, deleting at least part of the person-price relationship data according to the preset deletion strategy. Thus, the person-price relationship data stored in the memory database is refreshed or cleaned to increase the exposure rate of the newly produced waybills to be dispatched and improve the dispatch efficiency.

[0046] Please refer to Figure 3, the figure shows a person-unit-price data relationship model, including: person-unit-price data relationship model 301, waybill information 302, person-unit-price relationship 303, and unit-price relationship 304. Among them, the person-unit-price data relationship model 301 is a data relationship model generated according to the dispatch result of the waybill, which can be understood as a logical table stored in the memory database for determining the metadata acquisition path, and its key is the distribution resource identifier or is formed based on the distribution resource identifier and prefix, and at least includes person-unit-price relationship attribute information and unit-price relationship attribute information. These two types of attribute information are used to determine the metadata of one or more candidate waybills matching the distribution resource stored in the memory database, that is, the data contained in the person-unit-price relationship 303 stored in the memory database, and the metadata of the pricing information corresponding to each candidate waybill of the distribution resource, and the data contained in the unit-price relationship 304 stored in the memory database. The data contained in the person-unit-price relationship 303 and the data contained in the unit-price relationship 304 can be correspondingly obtained from the waybill information 302 according to the dispatch result of the waybill and stored in the memory database. The data in the waybill information 302 may be data stored in the waybill database, including basic waybill information and other information, such as the user, merchant, transportation capacity, event, and dispatch result information shown in the figure. The waybill database may be a MySQL database or other persistent database, without limitation. The data such as "user" and "merchant" contained in the waybill information may be metadata or attribute information, which is associated with the corresponding metadata through these attribute information. It is understandable that the attribute information contained in the person-unit-price data relationship model 301, waybill information 302, person-order relationship 303, and unit-price relationship 304 in the figure are all schematic and do not limit the present method.

[0047] Step S103, determining the target delivery resource for which the waybill needs to be pulled, obtaining the person-unit-price relationship data corresponding to the target delivery resource based on the person-unit-price data relationship model according to the target delivery resource, and generating a waybill pulling result for the target delivery resource.

[0048] This step is to generate the waybill pulling result, and further provide it to the client used by the target distribution resource and display it, so that the distribution resource can view and grab the order. During implementation, the client used by the distribution resource obtains the information of the target distribution resource for which the waybill needs to be pulled; detects the grab order pool viewing instruction of the target distribution resource, and sends a waybill pulling request to the server according to the grab order pool viewing instruction; obtains the waybill pulling result of the target distribution resource returned by the server in response to the waybill pulling request, extracts the information of the candidate waybill from the waybill pulling result, and displays the candidate waybill on the grab order pool page. Preferably, the acquiring of the person-unit-price relationship data corresponding to the target distribution resource based on the person-unit-price data relationship model according to the target distribution resource includes: determining a first target key value of a first key corresponding to the target distribution resource according to the person-unit-price relationship attribute information in the person-unit-price data relationship model of the target distribution resource; acquiring a first target storage value corresponding to the first target key value stored in a memory database, the first target storage value including waybill data of one or more waybills corresponding to the target distribution resource and their corresponding dispatch data; determining a second target key value of a second key corresponding to the target distribution resource according to the unit-price relationship attribute information in the person-unit-price data relationship model of the target distribution resource; acquiring a second target storage value corresponding to the second target key value stored in a memory database, the second target storage value including the pricing data of the one or more waybills; forming the person-unit-price relationship data corresponding to the target distribution resource based on the waybill data of the one or more waybills and their corresponding dispatch data, and the pricing data of the one or more waybills. The pricing data is pricing information expressed in digitized form.

[0049] In this embodiment, multiple distribution resources may simultaneously grab a diffused target waybill. The client used by each distribution resource detects that the corresponding distribution resource selects a diffused target waybill from the candidate waybill of the distribution resource to grab the order, and sends a grab order request for the target waybill to the server; the server needs to lock it when processing the grab order request to execute the grab order for the distribution resource. Specifically including: receiving multiple distribution resources for the waybill grab order request; for the grab order request of the first distribution resource among the multiple distribution resources, the waybill is assigned to the first distribution resource after locking, and the data related to the waybill in the person-unit-price relationship data of the first distribution resource is deleted according to the person-unit-price data relationship model. For example, rider A and rider B grab a target waybill at the same time. If rider A obtains the Redis lock and executes the grab order process when processing the grab order for rider A, rider B waits for rider A to release the Redis lock. If the Redis lock is not released for more than the preset time, rider B is prompted that the waybill has been grabbed by other riders. If rider A succeeds in grabbing the order within the preset time, the Redis lock is released. After the release, rider B obtains the Redis lock. When executing the order grabbing process, the status of the waybill is checked to determine that the waybill has been grabbed by other riders, and rider B is prompted that the waybill has been grabbed by other riders. If rider A fails to grab the order within the preset time, rider A releases the Redis lock, rider B obtains the Redis lock, and the order grabbing process is executed. If any rider succeeds in grabbing the order, the person-order relationship data and unit price relationship data stored in Redis are deleted.

[0050] In this embodiment, it also includes: generating single-person relationship data according to the scheduling result of the waybill; after the waybill is assigned to the first delivery resource, determining the candidate delivery resources matching the waybill according to the single-person relationship data, and for each delivery resource among the candidate delivery resources, deleting the data related to the waybill according to the person-price data relationship model.

[0051] It should be noted that the method is not limited to the distribution field, but can also be adapted to a variety of application fields that can independently select orders, such as vehicle dispatch scenarios in the order-grabbing mode in the transportation field. A data relationship model between drivers, orders and pricing information can be established to improve the processing efficiency of drivers grabbing orders.

[0052] It should be noted that, in the absence of conflict, the features given in this embodiment and other embodiments of the present application can be combined with each other, and steps S101 and S102 or similar terms do not limit the steps to be executed sequentially.

[0053] So far, the method provided in this embodiment has been described. In the method, the person-unit-price data relationship model generated according to the scheduling results is stored in the memory database, which can provide high-performance data access and improve the processing performance of waybill dispatching.

[0054] Based on the above embodiment, the second embodiment of the present application provides another waybill processing method, which is as follows: Figure 4 The method is described in detail. For related parts, please refer to the corresponding part. Figure 4 The waybill processing method shown in the figure includes: steps S401 to S403.

[0055] Step S401, obtaining information of the target delivery resource for which the waybill needs to be pulled;

[0056] Step S402: Detecting an order pool viewing instruction of the target delivery resource, and sending a waybill pulling request to the server according to the order pool viewing instruction;

[0057] Step S403, obtain the waybill pulling result of the target delivery resource returned by the server in response to the waybill pulling request, extract the information of the candidate waybill from the waybill pulling result, and display the candidate waybill on the order grabbing pool page; wherein, the waybill pulling result is generated by extracting the waybill data from the waybill pulling result, obtaining the person-unit-price relationship data according to the target delivery resource and the person-unit-price data relationship model stored in the memory database in response to the waybill pulling request;

[0058] The method provided in this embodiment is applied to the client corresponding to the distribution resource.

[0059] In step S402, the distribution resource can also use the client to set the order range conditions, such as setting the waybill within 7 kilometers. The client generates the waybill pull request according to the location information of the target distribution resource and the order range conditions, and sends it to the server. The location information of the target distribution resource can be the information of the current location of the target distribution resource, or it can be the location information specified by the target distribution resource. The target distribution resource can send a waybill pull request in the start-up state or the non-start-up state to view the waybill in the corresponding grab order pool. The candidate waybill is the first waybill assigned to the distribution resource, or the second waybill diffused to the distribution resource. That is, a waybill that needs to be assigned can be assigned to a specific distribution resource by the waybill assignment method, and can also be assigned to multiple matching candidate distribution resources by the waybill diffusion method. The waybill assignment type of the waybill assigned by the waybill assignment method is the assignment type, and the waybill assignment type of the waybill assigned by the waybill diffusion method is the diffusion type.

[0060] In step S403, the client displays the candidate waybill on the order grabbing pool page of the client. If the candidate waybill includes the scheduling and sorting information of the candidate waybill, the display position of the candidate waybill on the order grabbing pool page can be determined according to the scheduling and sorting information.

[0061] Preferably, it also includes: detecting that the target delivery resource selects the diffused first target waybill from the candidate waybills to grab the order, and sending a grab request for the first target waybill to the server; and / or detecting that the target delivery resource selects the assigned second target waybill from the candidate waybills to accept the order, and sending a confirmation request for the second target waybill to the server; adding the first target waybill and / or the second target waybill to the delivery task of the target delivery resource.

[0062] In this embodiment, it also includes: detecting that the delivery resource triggers the refresh of the waybill or the client triggers the refresh of the waybill periodically, sending a waybill refresh request to the server to request to obtain the current candidate waybill; obtaining the current candidate waybill returned by the server in response to the waybill refresh request, and using the current candidate waybill to refresh the order grabbing pool page.

[0063] So far, the method provided in this embodiment has been described. The waybill pulling result in the method is generated by the server obtaining the person-unit-price relationship data according to the target distribution resources and the person-unit-price data relationship model stored in the memory database in response to the waybill pulling request, and extracting the waybill data from the person-unit-price relationship data. The person-unit-price data relationship model is stored in the memory database, which can provide high-performance data access and improve the processing performance of waybill dispatching.

[0064] Corresponding to the first embodiment, the third embodiment of the present application provides a waybill processing device. For the relevant parts, please refer to the description of the corresponding method embodiment. Figure 5 , the waybill processing device shown in the figure includes:

[0065] The scheduling unit 501 is used to obtain the scheduling result of the waybill to be dispatched; the scheduling result includes the waybill, the candidate delivery resources of the waybill and the pricing information matching the candidate delivery resources;

[0066] The data relationship model building unit 502 is used to generate a person-unit-price data relationship model according to the dispatch result and the waybill information of the waybill; the person-unit-price data relationship model is stored in the memory database and is used to obtain the person-unit-price relationship data corresponding to the distribution resource according to the distribution resource;

[0067] The order pulling unit 503 is used to determine the target delivery resource that needs to pull the waybill, obtain the person-unit-price relationship data corresponding to the target delivery resource based on the person-unit-price data relationship model according to the target delivery resource, and generate the waybill pulling result of the target delivery resource.

[0068] Optionally, the data relationship model establishing unit 502 is specifically used to: determine a first matching relationship between distribution resources and waybills, and a second matching relationship between waybills and pricing information based on the scheduling results; form a first key-value pair based on the first matching relationship and the waybill information of the waybill, and form a second key-value pair based on the second matching relationship and the waybill information of the waybill; use the first key-value pair and the second key-value pair as associated data of corresponding attribute information in the person-unit-price data relationship model, respectively, to form the person-unit-price data model; wherein the first key-value pair, the second key-value pair and the person-unit-price data relationship model are stored in the memory database.

[0069] Optionally, the data relationship model establishing unit 502 is specifically used to: generate a first key based on the delivery resources in the first matching relationship; determine the storage value corresponding to the first key according to the waybill information of the waybill matching the delivery resources in the first matching relationship, to form the first key-value pair.

[0070] Optionally, the data relationship model establishing unit 502 is specifically used to: generate a second key based on the waybill in the second matching relationship; determine the storage value corresponding to the second key according to the pricing information matching the waybill in the second matching relationship, to form the second key-value pair.

[0071] Optionally, the order pulling unit 503 is specifically used to: determine a first target key value of a first key corresponding to the target distribution resource based on the person-order relationship attribute information in the person-unit-price data relationship model of the target distribution resource; obtain a first target storage value corresponding to the first target key value and stored in the memory database, the first target storage value including waybill data of one or more waybills corresponding to the target distribution resource and their corresponding scheduling data; determine a second target key value of a second key corresponding to the target distribution resource based on the unit price relationship attribute information in the person-unit-price data relationship model of the target distribution resource; obtain a second target storage value corresponding to the second target key value and stored in the memory database, the second target storage value including the pricing data of the one or more waybills; based on the waybill data of the one or more waybills and their corresponding scheduling data, as well as the pricing data of the one or more waybills, form the person-unit-price relationship data corresponding to the target distribution resource.

[0072] Optionally, the scheduling unit 501 is specifically used to: obtain the waybill that needs to be dispatched according to the waybill status; determine the capacity type and / or delivery area of ​​the waybill, and determine the candidate delivery resources of the waybill according to at least one of the capacity type and the delivery area; determine the pricing information of the waybill that matches the candidate delivery resources according to the waybill and the candidate delivery resources; and generate a scheduling result for the waybill based on the waybill, the candidate delivery resources, and the pricing information that matches the candidate delivery resources.

[0073] Optionally, the scheduling result of the waybill is generated by a scheduling server; the scheduling unit 501 is specifically used to: obtain a call request from the scheduling server for pushing the scheduling result to the fulfillment server that executes the method; the fulfillment server passes the call request to a pre-created asynchronous thread pool corresponding to the waybill dispatch type of the waybill contained in the call request, and one of the threads in the asynchronous thread pool obtains the scheduling result according to the waybill call request.

[0074] Optionally, the scheduling unit 501 is also used to: obtain the waybill dispatching rules of the waybill; determine the specific time period in the waybill dispatching rules that matches the current time; and set the waybill dispatching type of the waybill according to the waybill dispatching type corresponding to the specific time period.

[0075] Optionally, the device also includes an order grabbing unit, which is used to: receive order grabbing requests for the waybill from multiple delivery resources; in response to the order grabbing request from a first delivery resource among the multiple delivery resources, lock the waybill and assign it to the first delivery resource, and delete the data related to the waybill in the person-price relationship data of the first delivery resource according to the person-price relationship model.

[0076] Optionally, the order grabbing unit is also used to: generate single-person relationship data based on the scheduling result of the waybill; after assigning the waybill to the first delivery resource, determine the candidate delivery resources that match the waybill based on the single-person relationship data, and for each delivery resource among the candidate delivery resources, delete the data related to the waybill according to the person-price data relationship model.

[0077] Corresponding to the second embodiment, the fourth embodiment of the present application provides a waybill processing device. For the relevant parts, please refer to the description of the corresponding method embodiment. Figure 6 , the waybill processing device shown in the figure includes:

[0078] The distribution resource identification unit 601 is used to obtain information about the target distribution resource for which the waybill needs to be pulled;

[0079] The order request unit 602 is used to detect the order pool viewing instruction of the target delivery resource, and send a waybill request to the server according to the order pool viewing instruction;

[0080] The order pull response unit 603 obtains the waybill pulling result of the target delivery resource returned by the server in response to the waybill pulling request, extracts the information of the candidate waybill from the waybill pulling result, and displays the candidate waybill on the order grabbing pool page; wherein, the waybill pulling result is generated by the server obtaining the person-unit-price relationship data according to the target delivery resource and the person-unit-price data relationship model stored in the memory database in response to the waybill pulling request, and extracting the waybill data from the person-unit-price relationship data.

[0081] Optionally, the device also includes an order grabbing unit, which is used to: detect that the target delivery resource selects a diffused first target waybill from the candidate waybills to grab the order, and send an order grabbing request for the first target waybill to the server; and / or detect that the target delivery resource selects a designated second target waybill from the candidate waybills to accept the order, and send a confirmation order request for the second target waybill to the server; add the first target waybill and / or the second target waybill to the delivery task of the target delivery resource.

[0082] Based on the above embodiments, the fifth embodiment of the present application provides an electronic device. For the relevant parts, please refer to the corresponding description of the above embodiments. Figure 7 The electronic device shown in the figure includes: a memory 701 and a processor 702; the memory is used to store a computer program, and after the computer program is run by the processor, the method provided in the embodiment of the present application is executed.

[0083] Based on the above embodiments, the sixth embodiment of the present application provides a computer storage medium. For the relevant parts, please refer to the corresponding description of the above embodiments. Figure 7 The computer storage medium stores computer-executable instructions, and the computer-executable instructions are used to implement the method provided in the embodiment of the present application when executed by the processor.

[0084] In a typical configuration, an electronic device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0085] The memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0086] 1. Computer-readable media includes permanent and non-permanent, removable and non-removable media that can be used to store information by any method or technology. Information can be computer-readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassettes, magnetic tape disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by electronic devices. As defined in this article, computer-readable media does not include non-transitory media such as modulated data signals and carrier waves.

[0087] 2. Those skilled in the art should understand that the embodiments of the present application can be provided as methods, systems or computer program products. Therefore, the present application can take the form of a complete hardware embodiment, a complete software embodiment or an embodiment combining software and hardware. Moreover, the present application can take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0088] Although the present application is disclosed as above in the form of a preferred embodiment, it is not intended to limit the present application. Any technical personnel in this field may make possible changes and modifications without departing from the spirit and scope of the present application. Therefore, the scope of protection of the present application shall be based on the scope defined by the claims of the present application.

Claims

1. A waybill processing method, characterized in that: include: Get the dispatch result of the waybill that needs to be dispatched; The dispatch result includes the waybill, candidate delivery resources of the waybill, and pricing information matching the candidate delivery resources; Generate a person-unit-price data relationship model according to the dispatch result and the waybill information of the waybill; The person-unit-price data relationship model is stored in the memory database and is used to obtain the person-unit-price relationship data corresponding to the distribution resources according to the distribution resources; Determine the target delivery resource for which the waybill needs to be pulled, obtain the person-unit-price relationship data corresponding to the target delivery resource based on the person-unit-price data relationship model according to the target delivery resource, and generate a waybill pulling result for the target delivery resource; The step of generating a person-unit-price data relationship model according to the dispatch result and the waybill information of the waybill includes: Determining a first matching relationship between the delivery resources and the waybill, and a second matching relationship between the waybill and the pricing information according to the scheduling result; forming a first key-value pair based on the first matching relationship and the waybill information of the waybill, and forming a second key-value pair based on the second matching relationship and the waybill information of the waybill; Using the first key-value pair and the second key-value pair as associated data of corresponding attribute information in the person unit price data relation model, respectively, to form the person unit price data relation model; The first key-value pair, the second key-value pair and the person unit price data relationship model are stored in the memory database.

2. The method according to claim 1, characterized in that: The forming of a first key-value pair based on the first matching relationship and the waybill information of the waybill includes: generating a first key based on the delivery resource in the first matching relationship; The storage value corresponding to the first key is determined according to the waybill information of the waybill that matches the delivery resource in the first matching relationship to form the first key-value pair.

3. The method according to claim 2, characterized in that The forming of a second key-value pair based on the second matching relationship and the waybill information of the waybill includes: generating a second key based on the waybill in the second matching relationship; The storage value corresponding to the second key is determined according to the pricing information matched with the waybill in the second matching relationship to form the second key-value pair.

4. The method according to claim 1, characterized in that: The step of obtaining the person-price relationship data corresponding to the target delivery resource based on the person-price data relationship model according to the target delivery resource includes: Determine a first target key value of a first key corresponding to the target delivery resource according to the person-order relationship attribute information in the person-unit-price data relationship model of the target delivery resource; Obtaining a first target storage value corresponding to the first target key value and stored in a memory database, wherein the first target storage value includes waybill data of one or more waybills corresponding to the target delivery resource and the corresponding dispatch data; Determine a second target key value of a second key corresponding to the target delivery resource according to the unit price relationship attribute information of the target delivery resource based on the person unit price data relationship model; Obtaining a second target storage value corresponding to the second target key value and stored in the memory database, wherein the second target storage value includes pricing data of the one or more waybills; Based on the waybill data of the one or more waybills and the corresponding dispatch data, and the pricing data of the one or more waybills, the unit-price relationship data of each person corresponding to the target delivery resource is composed.

5. The method according to claim 1, characterized in that The obtaining of the dispatch result of the waybill to be dispatched includes: Get the waybill that needs to be dispatched according to the waybill status; Determine the transport capacity type and / or delivery area of ​​the waybill, and determine candidate delivery resources for the waybill based on at least one of the transport capacity type and the delivery area; Determining pricing information of the waybill that matches the candidate delivery resource according to the waybill and the candidate delivery resource; A dispatch result of the waybill is generated based on the waybill, the candidate delivery resources, and the pricing information matching the candidate delivery resources.

6. The method according to claim 1 or 5, characterized in that: The dispatch result of the waybill is generated by the dispatch server; The obtaining of the dispatch result of the waybill to be dispatched includes: Obtaining a call request from the scheduling server for pushing the scheduling result to the fulfillment server that executes the method; The fulfillment server passes the call request to a pre-created asynchronous thread pool corresponding to the waybill dispatch type according to the waybill dispatch type contained in the call request, and one of the threads in the asynchronous thread pool obtains the scheduling result according to the waybill call request.

7. The method according to claim 6, characterized in that The method further comprises: Obtaining a waybill dispatching rule for the waybill; Determine that the current time matches the specific time period in the waybill dispatching rule; The waybill dispatch type of the waybill is set according to the waybill dispatch type corresponding to the specific time period.

8. The method according to claim 1, characterized in that: The method further comprises: Receiving order grabbing requests from multiple delivery resources for the waybill; In response to the order grabbing request of the first delivery resource among the multiple delivery resources, the waybill is assigned to the first delivery resource after being locked, and the data related to the waybill in the person-price relationship data of the first delivery resource is deleted according to the person-price data relationship model.

9. The method according to claim 8, characterized in that The method further comprises: Generate single-person relationship data according to the dispatch result of the waybill; After the waybill is assigned to the first delivery resource, candidate delivery resources matching the waybill are determined based on the single-person relationship data, and for each of the candidate delivery resources, data related to the waybill is deleted based on the person-unit-price data relationship model.

10. A waybill processing method, characterized in that: include: Obtain information about the target delivery resource that needs to pull the waybill; Detecting an order pool viewing instruction for the target delivery resource, and sending a waybill pulling request to the server according to the order pool viewing instruction; Obtain the waybill pulling result of the target delivery resource returned by the server in response to the waybill pulling request, extract the information of the candidate waybill from the waybill pulling result, and display the candidate waybill on the order grabbing pool page; wherein the waybill pulling result is generated by the server obtaining the person-unit-price relationship data according to the target delivery resource and the person-unit-price data relationship model stored in the memory database in response to the waybill pulling request, and extracting the waybill data from the person-unit-price relationship data; Among them, the method also includes: obtaining the scheduling result of the waybill that needs to be dispatched; the scheduling result includes the waybill, the candidate distribution resources of the waybill and the pricing information matching the candidate distribution resources; determining a first matching relationship between the distribution resources and the waybill, and a second matching relationship between the waybill and the pricing information according to the scheduling result; forming a first key-value pair based on the first matching relationship and the waybill information of the waybill, and forming a second key-value pair based on the second matching relationship and the waybill information of the waybill; using the first key-value pair and the second key-value pair as associated data of corresponding attribute information in the person-unit-price data relationship model, respectively, to form the person-unit-price data relationship model.

11. The method according to claim 10, characterized in that The method further comprises: detecting that the target delivery resource selects a diffused first target waybill from the candidate waybills to grab the waybill, and sending a grabbing request for the first target waybill to the server; and / or, detecting that the target delivery resource selects a second target waybill assigned to it from the candidate waybill to accept the order, and sending a confirmation order acceptance request for the second target waybill to the server; Add the first target waybill and / or the second target waybill to the delivery task of the target delivery resource.

12. An electronic device, characterized in that: include: A memory and a processor; the memory is used to store a computer program, and after the computer program is run by the processor, the method described in any one of claims 1 to 11 is executed.

13. A computer storage medium, characterized in that: Computer-executable instructions are stored, and when the computer-executable instructions are executed by a processor, they are used to implement the method described in any one of claims 1 to 11.

Images