CN107423923A - Material flow tracking and dispatching method using dispatching person as core - Google Patents

Abstract

A logistics tracking and dispatching method centered on a delivery person belongs to the technical field of logistics distribution. The present invention tracks the position of the courier through the smart phone terminal, thereby realizing the tracking of logistics. At the same time, the server side of the intelligent terminal is used to realize the reasonable scheduling of logistics. This method makes distribution more real-time, wider applicability and lower distribution threshold. This method uses the method of tracking the delivery person to track the location of the goods, breaking the traditional tracking system of node scanning, and realizing real-time tracking in the true sense. After the buyer places an order, if the seller does not want to use third-party delivery, but chooses to deliver the goods by himself, he can register as a deliveryman and deliver the goods by himself, as long as the deliveryman's mobile phone or delivery vehicle is equipped with corresponding software to locate its location. Send to the server in real time, buyers can check the location of the purchased goods in real time. The present invention makes great use of social resources.

Description

Logistics Tracking and Scheduling Method Centered on Distributors

technical field

The invention relates to a logistics tracking and dispatching method centered on delivery personnel, which belongs to the field of logistics distribution.

Background technique

In recent years, with the vigorous development of e-commerce, online shopping has become a habit. In the process of online shopping, the efficiency of logistics has become an important factor affecting user experience, and it has also become a major bottleneck restricting e-commerce. The efficient distribution of logistics has also become the focus of people's research.

In the modern logistics system, the movement of logistics is tracked by scanning the code at the node with the location of the goods as the core. This tracking method is highly targeted and not easy to lose. In case of problems during the delivery process, it is easy to locate the location of the problem in a relatively short period of time. At the same time, after scanning, the goods can be further sorted, so as to better plan a reasonable route for the next delivery. But its shortcomings are also obvious: node scanning wastes a lot of time; the location of goods cannot be tracked in real time, and can only be checked at the location of the node; for suppliers of goods that sell large quantities of raw materials, if they rely on the first Third-party logistics companies need to paste scanning codes on raw materials, which is time-consuming and laborious; if the seller provides freight services by himself, he cannot obtain the location of the goods through other online channels. Even if it can be acquired in real time by renting positioning equipment, the cost is quite expensive. And it is difficult to connect with its warehouse cargo system.

JD.com has made some explorations in real-time delivery, and has basically realized the function of obtaining the location of the goods in real time on the mobile phone for self-operated and intra-city delivery orders. Many food delivery platforms are also very good at tracking the location of food delivery in real time. However, the delivery staff must be registered employees of these platforms, and the delivery barriers between various delivery platforms cannot be broken. Logistics scheduling is very limited. Unable to make good use of social resources.

The "last mile" problem of logistics has always been a major bottleneck in the development of logistics. It refers to the final link of logistics distribution, that is, the problem of high cost and low efficiency when the goods arrive near the consignee and are handed over to the consignee. In recent years, relevant research and solutions have emerged in an endless stream. Such as setting up self-lifting cabinets, drone delivery, etc. The space of the self-lifting cabinet is limited, and it is generally difficult to make an appointment. The distribution of drones is not smart enough, and the requirements for the volume and weight of the goods are relatively strict. These solutions still fail to fundamentally solve the time and efficiency problems.

Contents of the invention

The present invention designs a logistics tracking and dispatching method centering on the delivery staff, aiming at the problems faced by the current logistics distribution and the diversified distribution requirements. Track the location of the courier through the smart phone terminal, so as to realize the tracking of logistics. At the same time, the server side of the intelligent terminal is used to realize the reasonable scheduling of logistics.

The "China Mobile Internet Development Status and Security Report (2016)" shows that in 2015, there were 1.13 billion active smart phone networking terminals in China. Using this method, taking advantage of the positioning advantages of intelligent terminals, the logistics tracking and dispatching platform constructed can well integrate the logistics distribution system, optimize the logistics distribution structure, and maximize the use of social resources to serve the logistics system.

This method makes distribution more real-time, wider applicability and lower distribution threshold. This method uses the method of tracking the delivery person to track the location of the goods, breaking the traditional tracking system of node scanning, and realizing real-time tracking in the true sense. After the buyer places an order, if the seller does not want to use third-party delivery, but chooses to deliver the goods by himself, he can register as a deliveryman and deliver the goods by himself, as long as the deliveryman's mobile phone or delivery vehicle is equipped with corresponding software to locate its location. Send to the server in real time, buyers can check the location of the purchased goods in real time. At the same time, if anyone registers as a delivery person, as long as it is convenient, he can accept the order dispatched or transferred by other delivery personnel to complete a single delivery. It breaks the barriers that delivery personnel belong to a certain platform, creates a "pure delivery personnel" profession, lowers the delivery threshold, and makes great use of social resources.

The system is connected with the traditional logistics company's system, which can well solve the "last mile" problem. The logistics system only needs to send the distribution information to the platform, and the platform distributes the tasks to the appropriate delivery personnel through scheduling. Individuals registered as "pure delivery personnel" no matter they are commuting to get off work or on the way out for an outing, as long as the scheduling is reasonable, these "pure delivery personnel" can "drop in" to complete a single delivery. The logistics company can track the location of the goods in real time by integrating the SDK of our platform or calling the query interface.

The system is connected with the company's goods management system, which can realize automatic delivery, and can realize real-time location query of the goods after delivery. Enterprises that have applied for an enterprise account can also customize their own delivery staff to realize the customized distribution and management of delivery orders.

To use the system, individual users only need to fill in the delivery information (shipping place, receiving place, consignee and cargo information, etc.) to complete online ordering. The system can help select or recommend suitable delivery personnel for delivery. It is also possible to assign tasks by grabbing orders after the user places an order.

Through this system, consignors, consignees, dispatchers, logistics companies, distributors, and cargo providers who provide distribution services can be deeply integrated, and finally achieve the purpose of improving logistics distribution efficiency, optimizing social resources, and saving logistics costs.

During the transition period from the IT era to the DT era, the value of data is increasingly valued by people. The detailed information of each link of distribution is recorded, and the real-time logistics data and distribution data accurate to the minute level can provide users with valuable reference from multiple dimensions. These data are not limited to the use of this system, and other systems can easily query the required relevant data by introducing the SDK package of this system. Dispatchers can use these data to make more reasonable scheduling, and even realize automatic scheduling through some algorithms. Goods providers can use this data to guide their own production. The consignee can use these data to reasonably arrange the receiving time and warehouse storage.

Figure 1 is a logistics distribution business diagram, and the logistics distribution business process is as follows,

A logistics process can be simply abstracted into four key elements: place of dispatch, place of receipt, cargo information and consignee. What the user needs to do is to place an order to fill in the information (the content of the order is shown in Table 1). The user here may be a logistics company, an individual, or an enterprise providing distribution services (hereinafter referred to as enterprise or enterprise user). No matter what kind of user it is, there are only two parts that concern it, one is to place an order, and the other is to query the logistics status. Therefore, a complete logistics scheduling system only needs to ensure the development of the above two interfaces.

Table 1 Logistics distribution information table

name Introduction Shipping place Shipping place name delivery address Delivery address Receipt Receiving place name harvest address The detailed address of the receiving place Receiver Consignee name and contact information cargo description The type, volume and quality of the goods, etc. Expected delivery time (optional) It is optional and can be used to satisfy users with strict time requirements

Description of System Deployment Diagram

This system is mainly aimed at three types of groups: logistics companies, individual users and enterprises that provide distribution services.

For logistics companies, the system can help them solve the "last mile" problem. Embed the SDK of this system in the logistics management system of the logistics company. You only need to call the relevant functions in the SDK and pass in the contents in Table 1. You can complete the order. The interface for communicating with the dispatch center is implemented inside the SDK. The following single interface is taken as an example for illustration.

Description of the logistics SDK class object sequence diagram:

The SendAssembleServer class is an abstract class, and NetServer is an interface.

Using the template method pattern, execute the getOrderInfo method, getIp method and send method sequentially in the sdkCreateOrder method. The getOrderInfo method and the getIp method are abstract methods that need to be implemented in the subclass line. The function is to return the information to be sent (Map format) and the dispatch center Ip, pass the information and ip address into the send method, and then call the SendNetServer method to send it out. Use the proxy mode to receive the returned results. The SendManager class and SendAssembleServer class implement the NetServer interface, rewrite the result method, and finally let SendNetServer call back to the result method in SendManager layer by layer, and return the processing result of the dispatch center.

Logistics SDK instructions:

In the logistics company's system, create a SendManager class. And let this class inherit the SendAssembleServer class, realize the NetServer interface, and rewrite the getOrderInfo, getIp and result methods. In the getOrderInfo method, receive the information from the logistics system in the format required by the dispatch center. After sorting it out, save it in the map, and let the map be put back as the return value. In the getIp method, return the ip address of the dispatch center. Create an external class A, A also needs to implement the NetServer interface, rewrite the result method. Create an object B of the SendManager class in the function of A, and pass the reference of the A object to the object B. Call getOrderInfo(Map map) of object B to pass in the required sending information. Then call the sdkCreateOrder method of object B to send the information. According to the proxy mechanism, after the dispatch center returns the message, it will automatically call back the result method of A.

The implementation of the interface for querying the location and status of goods is similar.

For individual users, they only need to send the content in Table 1 to the dispatching center through the mobile phone APP through the interface to complete the order.

For enterprises that provide distribution services, it is necessary to embed an enterprise SDK that interacts with the dispatch center in the enterprise's cargo management system (the structure of the enterprise SDK is similar to the logistics SDK). After shipment, the goods management system will automatically send the content in Table 1 plus the company's ID to the dispatch center through the interface of the company's SDK to complete the order. After the order is placed, the company sets the delivery staff to complete the delivery. See S6 for the setting method. Either way, for enterprise users, the delivery person must be a delivery person that has been set within the enterprise. All interfaces used by enterprise users must carry the enterprise ID.

After the order is placed, the system will return a prompt indicating whether it is successful, and if successful, it will return the order number at the same time.

All three types of groups can call the interface of the dispatch center to query the status of the order and the location of the goods through the order number.

The dispatch center server architecture is divided into dispatch module, address management, location tracking, personnel management, statistics and billing, order management and invitation.

The scheduling module is responsible for dispatching orders to each delivery person, and notifying the push server to push. The push can be pushed using a third-party push platform.

Address management is a function that can only be used by enterprise users, and its purpose is to store frequently used address information.

The location tracking module is used to receive the location information sent by each courier for users to query.

Personnel management is responsible for adding, deleting, checking and modifying personnel information.

The statistics and billing function is responsible for returning the order quantity and order details delivered by each courier. By setting a certain billing mode (see S6 for setting the billing mode), the current income and expenditure situation of each courier is displayed.

Order management is responsible for order placement and order information query functions.

The invitation function is responsible for generating invitation codes for each role.

The mobile APP architecture is divided into a push receiving module, a registration module, a setting module, a third-party map module, an order module, an order list and details module, and a statistical data display module.

The push receiving module is used to receive the push information sent by the push platform.

The registration module provides new user registration function.

The content that can be set in the setting module is different for different roles. For details, see S1 Assigning System Roles.

Different content is displayed in third-party maps according to different roles. The dispatch shows the location of each courier. The courier shows the location of the harvester. The consignee shows the location of the goods to be received.

In the order module, you can fill in the order information and place an order.

The order list displays all orders and their status. Click on an order item to view order details.

The statistical data display module is responsible for displaying statistical data.

In the data analysis server architecture, there is only the data analysis module, which is responsible for providing external data query interfaces. The shared data includes: the distribution of delivery personnel's location at a certain time, the flow direction of delivered goods, the occurrence time of delivery peaks, etc. By analyzing these data, dispatchers can schedule more accurately, cargo suppliers can better arrange production, and consignees can reasonably arrange warehouse storage and receiving time.

The data analysis server and the dispatching center server share a set of databases.

The database table relationship diagram and data isolation methods are as follows:

Personnel information table: mainly includes the identity information and location coordinates of the person.

Login information table: store the login information, user name and password of the personnel.

Role table: store role information.

Role permission table: stores the menu permission of the role.

Enterprise information table: For enterprise users who provide freight services, store the organization code and corresponding ID of the enterprise.

Order information table: store order information. The place of delivery and the condition of the goods, etc.

Order delivery form: store the delivery information of the delivery staff.

Address information table: store address information. Place names and zip codes, etc.

Invitation code table: store the invitation codes of each role.

The logistics SDK and the personal call interface do not need to pass the enterprise number when storing data in the database. When an enterprise user saves data in the database, it needs to pass the enterprise number, which can be found in the enterprise information table. All tables in the database except the enterprise information table must have an enterprise number field, which is used to distinguish which enterprise has stored the data.

The shipping process is as follows:

Order: individual users place an order directly. The logistics company calls the interface to place an order through the logistics SDK. Enterprises that provide freight services place orders through the enterprise SDK call interface, because the freight services are provided by the enterprises themselves, and the customers of freight services are relatively fixed, so when filling in Form 1, the place of delivery and the place of receipt can be selected from the list. It is also possible to add, delete, check and modify addresses and personnel in this system.

Order receiving at the distribution center: The distribution center receives order requests through different channels.

Assignment of delivery personnel: For the assignment method, please refer to the division of S4 dispatching method. Orders placed by individual users and logistics companies are dispatched uniformly by the system, and users who are registered as delivery staff can receive orders. The delivery staff of enterprises that provide self-delivery freight services must be internal employees of the enterprise.

Distributor receives order: After receiving the task, the distributor receives the order.

Transfer: The delivery staff can transfer the order to others during the delivery process. The delivery personnel of enterprises that provide self-delivery freight services can only transfer to employees within the enterprise. There is an option to cancel the turnaround until the order is picked up by the next courier.

The delivery person confirms the delivery: the delivery person clicks the confirmation delivery button through the mobile APP. Service is divided into face-to-face service and non-face-to-face service. For face-to-face delivery, just click the Confirm Delivery button; for non-face-to-face delivery, you need to upload the photo of the goods at that time and then click the Confirm Delivery button.

Sign for receipt: The consignee chooses to sign for receipt.

Description of drawings

Figure 1 Logistics distribution business diagram

Figure 2 System deployment diagram

Figure 3 Logistics SDK class object sequence diagram

Figure 4 SendAssembleServer and NetServer class diagram

Figure 5 Overall System Implementation

Figure 6 Database table relationship diagram

Figure 7 delivery flow chart

Figure 8 Order Status Diagram

detailed description

A logistics tracking and dispatching method centered on delivery personnel, the method includes the following processes.

S1 assigns system roles

Administrator: Responsible for personnel management. It is the role that the system has from the very beginning. Invitation codes of other roles can be generated, and the accounts of other roles are generated through invitation codes.

Sender: Responsible for placing orders, currently facing three groups: logistics companies, enterprises and individuals. The logistics company mainly needs to integrate the SDK of this system in the internal system of the logistics company to solve the "last mile" problem, and interact with the dispatch center through the interface in the SDK. Enterprises refer to those companies that provide goods distribution services, and also need to integrate the SDK of this system in their goods management system, and interact with the dispatch center through the interface in the SDK. Individuals refer to individuals who need freight services, just register directly. When registering, the company organization code and invitation code are left blank.

Dispatcher: Responsible for assigning orders to couriers. Perform manual scheduling (for other scheduling policy suggestions, see S4 Division of Scheduling Policies). The dispatcher of an enterprise user can only dispatch the orders of the enterprise and assign the delivery personnel of the enterprise. At the same time, the dispatcher of the enterprise user can also manage the addresses.

Distributor: Responsible for delivery.

Recipient: responsible for receiving the goods.

Table 2 Detailed list of menu content displayed by different roles in APP

Role show menu content administrator Orders, maps, statistics, settings (change password, change mobile phone number, invitation code, address management, personnel management, logout) sender Order, map, order, statistics, settings (change password, change mobile phone number, add address, logout) dispatcher Orders, maps, statistics, settings (change password, change mobile phone number, invitation code, logout) courier Orders, maps, settings (change password, change mobile phone number, logout) Receiver Orders, maps, settings (change password, change mobile phone number, logout)

Note: For the invitation code function, administrators can generate invitation codes for all roles, and dispatchers can only generate invitation codes for delivery personnel.

S2 sets the status of the system order

The order status description is as follows:

The order status is generally divided into the following six types (the order status displayed by different roles may be different):

New task: This status is displayed when the dispatcher receives a new order; this status is displayed when the dispatcher is assigned as the delivery person or turnover person of an order. Pending response: Including the following three situations, the order is placed and waiting for delivery; the initial delivery is waiting for the order to be received; after the turnaround, the order is waiting for the order to be received. In these three cases, except for the role that should process the task, it will be displayed as a new task, and the other roles will be displayed as waiting for a response.

In Turnaround: The order request is turned around but not responded to. In this case, except for the delivery person who is turned over, it is displayed as a new task, and other roles are shown as being turned over. Delivering: The item is being delivered by the courier.

Waiting to sign for receipt: The courier has completed the delivery and is waiting for the recipient to sign for receipt. At this time, except the recipient is displayed as a new task, other roles are displayed as waiting to sign.

Completed: Complete the entire shipping process.

S3 builds a dispatch center server

The server can use javaWeb technology, such as SSH and SpringMVC+mybatis, or PHP and .net technology. The database uses MySQl database. The format of data transfer between servers is json or xml.

S4 write APP

The written APP is divided into ios version and Android version. The third-party map SDK is integrated in the software, which is convenient for logistics dynamic viewing and location uploading.

The software architecture adopts the MVC model, and some third-party frameworks and custom controls can be used. For example, Imageloader and recyclerview in Android, AFNetworking in iOS, etc.

For the development of the map module, the following points should be paid attention to:

The delivery staff needs to upload their location every half minute, and they can see the location of the destination of the goods they need to deliver on the embedded map. They can use the API developed by Baidu Maps to obtain real-time traffic conditions, so as to guide their delivery.

The dispatcher can view the location information and delivery information of all delivery personnel, so as to reasonably assign new tasks to the delivery personnel.

The sender and recipient can see the real-time location of the goods through the location uploaded by the delivery staff.

S5 Choose a reasonable dispatcher scheduling method

The dispatching methods of delivery personnel are mainly divided into manual dispatching mode and order grabbing mode.

Manual scheduling mode: The person registered as the scheduling role manually sets the delivery staff according to the delivery situation.

Order grabbing mode: After the order is issued, the courier will grab the order according to his own situation. The disadvantage is that it is easy to cause unreasonable order grabbing, which may result in poor user experience. Not recommended for use.

The manual scheduling mode is more suitable for small and medium-sized enterprises that provide self-delivery services. The order grabbing mode is suitable for large enterprises that provide self-delivery services, and it is also the most suitable scheduling method for dispatch centers to dispatch delivery personnel for logistics companies and individual users.

S6 set billing mode

The billing mode of the delivery staff who provide delivery services for the enterprise is determined by the enterprise itself according to the number of orders completed by the delivery staff.

Other users (mainly for couriers and consignees) are billed through the amount of distribution currency.

Distribution currency is a kind of virtual currency in this system, which can be consumed in this system.

Distribution coin usage rules: Users accumulate distribution coins by delivering items for others, and the distribution coins will be accumulated according to the weight and delivery mileage of their own delivery items. To enjoy other people's delivery services, you need to consume delivery coins. In the process of delivery for a certain user by others, after arriving at the destination, if the consignee has not received it after a certain period of time, part of the delivery currency of the consignee will be deducted for punishment.

S7 registration and operation

Individual users register directly through the mobile APP. When registering, the company organization code column and the invitation code column are left blank. After successful registration, the corresponding roles of the user are consignor, delivery person and consignee. The logistics company registers offline. After successful registration, a consignor account will be assigned. It is integrated into the logistics SDK in the logistics system and can be used after logging in with the consignor account. Enterprises that provide freight services also register offline. After successful registration, they are assigned an enterprise ID and an administrator account, and embed the enterprise version SDK in their cargo management system. Enterprise employees can register consignors, delivery personnel, dispatchers or consignees through the invitation code issued by the administrator, and then they can carry out normal transportation activities.

Claims (2)

1. The logistics tracking and dispatching method centered on the dispatcher, which is characterized in that: the logistics distribution business process is as follows, A logistics process can be simply abstracted into four key elements: place of delivery, place of receipt, cargo information, and consignee; all the user needs to do is place an order to fill in the information, and the content of the order is shown in Table 1. ;The user here can be a logistics company, an individual, or an enterprise that provides delivery services. Hereinafter referred to as an enterprise or enterprise user; no matter what kind of user, there are only two parts that are concerned, one is to place an order, and the other is to query the logistics status; so A complete logistics scheduling system only needs to ensure the development of the above two interfaces; Table 1 Logistics distribution information table name Introduction Shipping place Shipping place name delivery address Delivery address Receipt Receiving place name harvest address The detailed address of the receiving place Receiver Consignee name and contact information cargo description The type, volume and quality of the goods, etc. Expected delivery time (optional) It is optional and can be used to satisfy users with strict time requirements This system is mainly aimed at three types of groups: logistics companies, individual users and enterprises that provide distribution services; For logistics companies, the system can help them solve the "last mile" problem; embed the SDK of this system in the logistics management system of the logistics company; only need to call the relevant functions in the SDK and pass in the content in Table 1; that is The order can be placed; the SDK internally realizes the communication interface with the dispatch center; Description of the logistics SDK class object sequence diagram: The SendAssembleServer class is an abstract class, and NetServer is an interface; Using the template method pattern, execute the getOrderInfo method, getIp method, and send method sequentially in the sdkCreateOrder method. The getOrderInfo method and the getIp method are abstract methods that need to be implemented in the subclass line. The function is to return the information that needs to be sent and the IP of the dispatch center. The information and ip address are passed into the send method, and then the SendNetServer method is called to send it out; the proxy mode is used to receive the returned result, the SendManager class and the SendAssembleServer class implement the NetServer interface, rewrite the result method, and finally let SendNetServer call back layer by layer to the SendManager The result method returns the processing result of the dispatch center; Logistics SDK instructions: In the logistics company's system, create a SendManager class; let this class inherit the SendAssembleServer class, implement the NetServer interface, rewrite the getOrderInfo, getIp and result methods; receive the information from the logistics system in the getOrderInfo method, and follow the requirements of the dispatch center format; sort it out, store it in the map, and let the map be returned as the return value; in the getIp method, return the ip address of the dispatch center; create an external class A, A also needs to implement the NetServer interface, and rewrite the result method; Create an object B of the SendManager class in the function of A, and pass the reference of the A object to the object B; call the getOrderInfo of the object B to pass in the required sending information; then call the sdkCreateOrder method of the object B to send the information; according to Proxy mechanism, after the dispatch center returns the message, it will automatically call back the result method of A; The implementation of the interface for querying the location and status of goods is similar; For individual users, they only need to send the content in Table 1 to the dispatching center through the interface through the mobile APP, and then complete the order; for enterprises that provide delivery services, they need to embed and dispatch the center in the enterprise's cargo management system Interactive enterprise SDK; after shipment, the goods management system will automatically send the content in Table 1 plus the enterprise ID to the dispatch center through the interface of the enterprise SDK, and complete the order; after the order is placed, the enterprise sets the delivery staff to complete the delivery; In this way, for enterprise users, the delivery person must be a delivery person that has been set within the enterprise; all interfaces used by enterprise users must carry the enterprise ID; After the order is placed, the system will return a prompt indicating whether it is successful, and if successful, it will return the order number at the same time; All three types of groups can call the interface of the dispatch center to query the status of the order and the location of the goods through the order number; The dispatch center server architecture is divided into dispatch module, address management, location tracking, personnel management, statistics and billing, order management and invitation; The scheduling module is responsible for assigning the order to each delivery person, and notifying the push server to push; the push can be pushed using a third-party push platform; Address management is a function only used by enterprise users, the purpose is to store commonly used address information; The location tracking module is used to receive the location information sent by each courier for users to query; Personnel management is responsible for adding, deleting, checking and modifying personnel information; The statistics and billing function is responsible for returning the order quantity and order details of each courier; by setting a certain billing mode, it displays the current income and expenditure of each courier; Order management is responsible for order placement and order information query functions; The invitation function is responsible for generating invitation codes for each role; The mobile APP architecture is divided into a push receiving module, a registration module, a setting module, a third-party map module, an order module, an order list and details module, and a statistical data display module; The push receiving module is used to receive the push information sent by the push platform; The registration module provides new user registration function; The content of the setting module is different for different characters; The third-party map displays different content according to different roles; the dispatch shows the location of each delivery person; the delivery person displays the location of the harvester; the consignee displays the location of the goods to be received; Fill in the order information in the order module, and then place the order; The order list displays all orders and their status, click on an order item to view order details; The statistical data display module is responsible for displaying statistical data; There is only a data analysis module in the data analysis server architecture, which is responsible for providing external data query interfaces; the shared data includes: the distribution of the location of the delivery personnel, the flow direction of the delivered goods, and the occurrence time of the delivery peak at a certain time; by analyzing these data, Scheduling personnel can schedule more accurately, cargo suppliers can better arrange production, and consignees can reasonably arrange warehouse storage and receiving time; The data analysis server and the dispatching center server share a set of databases; The database table relationship diagram and data isolation methods are as follows: Personnel information table: mainly includes the identity information and location coordinates of the person; Login information table: store personnel's login information, user name and password; Role table: store role information; Role permission table: store the menu permissions of the role; Enterprise information table: For enterprise users who provide freight services, store the organization code and corresponding ID of the enterprise; Order information table: store order information; place of receipt and delivery and goods status, etc.; Order delivery table: store the delivery information of the delivery staff; Address information table: store address information; place names and zip codes, etc.; Invitation code table: store the invitation codes of each role; The logistics SDK and the personal call interface do not need to pass the enterprise number when storing data in the database; when enterprise users store data in the database, they need to pass the enterprise number, which can be found in the enterprise information table; Tables in all other databases must have an enterprise number field, which is used to distinguish which enterprise has stored the data; The shipping process is as follows: Order: individual users directly place an order; logistics companies place orders through the logistics SDK call interface; companies that provide freight services place orders through the enterprise SDK call interface, because the freight service is provided by the enterprise itself, and the customers of the freight service are relatively fixed, so fill in In Table 1, the place of delivery and the place of receipt can be selected through the list; it is also possible to add, delete, check and modify addresses and personnel in this system; Receiving orders at the distribution center: the distribution center receives order requests through different channels; Assignment of delivery personnel: the allocation method can refer to the division of S4 dispatching methods; the orders placed by individual users and logistics companies are dispatched by the system in a unified manner, as long as users who are registered as delivery personnel can receive orders; the delivery of enterprises that provide self-delivery freight services The employee must be an internal employee of the enterprise; Order receiving by delivery staff: After receiving the task, the delivery staff will accept the order; Transfer: The delivery staff can transfer the order to others during the delivery process; the delivery staff of the company that provides self-delivery freight services can only transfer the order to the employees of the company; you can choose to cancel the turnover before the next delivery staff accepts the order; The delivery person confirms the delivery: the delivery person clicks the confirmation delivery button through the mobile APP; delivery is divided into face-to-face delivery and non-face-to-face delivery; face-to-face delivery can be directly clicked on the confirmation delivery button; non-face-to-face delivery needs to upload the current Click the confirm delivery button after the photo of the goods; Sign for receipt: The consignee chooses to sign for receipt. 2. The logistics tracking and dispatching method centered on delivery personnel according to claim 1, characterized in that: the method includes the following process, S1 assigns system roles Administrator: Responsible for personnel management; it is a role that the system has at the beginning; it can generate invitation codes for other roles, and accounts for other roles are generated through invitation codes; Sender: Responsible for placing orders, currently facing three types of groups: logistics companies, enterprises and individuals; logistics companies mainly need to integrate the SDK of this system in the internal system of logistics companies to solve the "last mile" problem, and pass Interact with the dispatch center through the interface in the SDK; enterprises refer to those companies that provide cargo delivery services, and also need to integrate the SDK of this system in their cargo management system, and interact with the dispatch center through the interface in the SDK; individuals refer to the need for freight The individual of the service can register directly; when registering, the company organization code and invitation code are left blank; Dispatcher: Responsible for assigning orders to delivery personnel; performing manual scheduling; the dispatcher of an enterprise user can only schedule the orders of the enterprise and assign the delivery personnel of the enterprise; at the same time, the dispatcher of the enterprise user can also manage the address; Distributor: responsible for delivery; Recipient: responsible for receiving the goods; Table 2 Detailed list of menu content displayed by different roles in APP Role show menu content administrator Orders, maps, statistics, settings (change password, change mobile phone number, invitation code, address management, personnel management, logout) sender Order, map, order, statistics, settings (change password, change mobile phone number, add address, logout) dispatcher Orders, maps, statistics, settings (change password, change mobile phone number, invitation code, logout) courier Orders, maps, settings (change password, change mobile phone number, logout) Receiver Orders, maps, settings (change password, change mobile phone number, logout) Note: For the invitation code function, the administrator can generate invitation codes for all roles, and the dispatcher can only generate invitation codes for delivery personnel; S2 sets the status of the system order The order status description is as follows: The order status is generally divided into the following six types (the order status displayed by different roles may be different): New task: This status is displayed when the dispatcher receives a new order; this status is displayed when the dispatcher is assigned as the delivery person or turnover person of an order; Pending response: Including the following three situations, the order is placed and waiting for delivery; the initial delivery is waiting for the order to be received; after the turnaround, the order is waiting to be received; in these three cases, except for the role that should process the task, it will be displayed as a new task, and other roles will be displayed as pending response; Turning: The order has applied for turnaround but has not responded; in this case, except for the delivery person who is turned over, it is displayed as a new task, and other roles are shown as turning around; Delivering: being delivered by the delivery staff; Waiting to sign for receipt: The delivery person completes the delivery and waits for the recipient to sign for receipt; at this time, except the recipient is displayed as a new task, other roles are displayed as pending receipt; Completed: complete the entire distribution process; S3 builds a dispatch center server The server can use javaWeb technology, such as SSH and SpringMVC+mybatis, or PHP and .net technology; the database uses MySQl database; the format of data transmission between servers is json or xml; S4 write APP The written APP is divided into ios version and Android version. The third-party map SDK is integrated in the software, which is convenient for logistics dynamic viewing and location uploading; the software architecture adopts MVC mode, using some third-party frameworks and custom controls; For the development of the map module, the following points should be paid attention to: The delivery staff needs to upload their own location every half minute, see the location of the destination of the goods they need to deliver on the embedded map, and use the API developed by Baidu Maps to obtain real-time road conditions, so as to guide their delivery; The dispatcher can view the location information and delivery information of all delivery personnel, so as to reasonably assign new tasks to the delivery personnel; The sender and receiver can see the real-time location of the goods through the location uploaded by the delivery staff; S5 Choose a reasonable dispatcher scheduling method The delivery staff scheduling method is mainly divided into manual scheduling mode and order grabbing mode; Manual scheduling mode: the person registered as the scheduling role manually sets the delivery staff according to the delivery situation; Order grabbing mode: After the order is issued, the delivery staff will grab the order according to their own situation; the manual scheduling mode is more suitable for small and medium-sized enterprises that provide self-delivery services; the order grabbing mode is suitable for large enterprises that provide self-delivery services, and it is also a scheduling The most suitable scheduling method for logistics companies and individual users to dispatch delivery personnel; S6 set billing mode The billing mode of the delivery staff who provide delivery services for the enterprise is determined by the enterprise itself according to the number of orders completed by the delivery staff; other users are billed through the distribution currency amount; Distribution currency is a kind of virtual currency in this system, which is consumed in this system; Distribution coin usage rules: Users accumulate distribution coins by delivering items for others, and the distribution coins will be accumulated according to the weight of the delivered items and the delivery mileage; to enjoy the delivery service of others, you need to consume distribution coins; In the process, after arriving at the destination, if the consignee has not received it after a certain period of time, part of the consignee's delivery currency will be deducted for punishment; S7 registration and operation Individual users register directly through the mobile APP. When registering, the company organization code column and the invitation code column are left blank; after successful registration, the corresponding roles of the user are consignor, delivery person and consignee; logistics company Through offline registration; after the registration is successful, a consignor account will be assigned; the logistics SDK is integrated into the logistics system, and it can be used after logging in with the consignor account; companies that provide freight services also register through offline, and the registration is successful Finally, assign an enterprise ID and an administrator account for it, and embed the enterprise version SDK in its cargo management system; enterprise employees register consignors, delivery personnel, dispatchers or consignees through the invitation code issued by the administrator, and then Carry out normal transportation activities.