Intelligent order pre-allocation and optimization scheduling method for empty vehicle resources

Abstract

The present application relates to big data processing technology field, specifically to a kind of intelligent order pre-allocation and optimization scheduling method for empty car resources, comprising the following steps: receiving order data, empty car state data and road network time consumption data, generate empty car resource can undertake window and order candidate demand area;When satisfying the condition of space-time overlap, determine the candidate vehicle set, generate pre-allocation combination in combination with the time consumption of arriving at the boarding point, direction consistency, waiting level and vehicle occupation state;When the correction trigger condition is satisfied, release or replace temporary occupation state.The present application converts single position screening into space-time relationship screening by matching the vehicle side can undertake range with the order side demand set, and updates the pre-allocation relationship when the driver response timeout, vehicle position deviation, order cancellation or new order enters by temporary occupation state and rolling correction, reduces vehicle repeated occupation, adjacent order contention and matching deviation.

Description

Technical Field

[0001] This invention relates to the field of big data processing technology, and in particular to an intelligent order pre-allocation and optimized scheduling method for empty vehicle resources. Background Technology

[0002] In the field of big data processing technology, the collection, transmission, storage, cleaning, association, calculation, and retrieval of order records, vehicle status, trajectory coordinates, timestamps, and service area data generated by business terminals, servers, databases, and location service interfaces are carried out. The terminal side uploads business events and status fields, while the server side processes the data in batches or in real-time according to field relationships, temporal relationships, spatial locations, and rule conditions. Among these, the traditional intelligent order pre-allocation and optimized scheduling method for empty vehicle resources refers to the dispatching process between empty vehicles and pending orders. It receives the passenger terminal's submission of the boarding location, destination, order time, and vehicle type requirements, combines this with the driver terminal's uploaded information on the vehicle's current location, empty status, driving direction, service area, and historical order records, reads map road networks, distances, estimated travel time, and order priority rules from the dispatch server, filters, sorts, and pre-allocates candidate vehicles, and sends the scheduling results to the driver terminal and order management database for status updates.

[0003] Traditional order pre-allocation relies on passenger terminal order data, driver terminal empty vehicle status data, and map road network time data to filter and sort candidate vehicles. Vehicle capacity is mainly characterized by current location, empty status, estimated arrival time, and service area. Order demand enters the dispatch process as an individual order. When empty vehicle resources change in a short period of time due to changes in driving direction, response status, and orders, discrepancies can easily arise between the pre-allocation results and the actual available capacity. Duplicate vehicle occupancy and competition for the same vehicle between adjacent areas can affect dispatch continuity. Summary of the Invention

[0004] The purpose of this invention is to provide an intelligent order pre-allocation and optimized scheduling method for empty vehicle resources. In order scheduling scenarios where empty vehicle resources, order demand, and driver response status are constantly changing, a verifiable and updatable scheduling link is formed between the available status of empty vehicle resources, order candidate demand areas, pre-allocation combinations, and temporary occupancy status. This reduces resource duplication, matching deviations, and scheduling status asynchronization that occur when order pre-allocation is based solely on static distance or single sorting.

[0005] To achieve the above objectives, this invention employs an intelligent order pre-allocation and optimized scheduling method for empty vehicle resources, comprising the following steps:

[0006] The dispatch server receives order data uploaded from passenger terminals and empty vehicle status data uploaded from driver terminals, and accesses map road network time data. Based on vehicle location, driving direction, empty duration, service area boundaries, time to pick-up point, and driver response records, an available window of empty vehicle resources is generated. Based on pick-up location, order placement time, destination direction, vehicle type demand, and waiting time, pending orders are aggregated into candidate demand areas. The spatiotemporal overlap between the available empty vehicle resources window and the candidate demand areas is compared. If the overlap meets preset spatiotemporal overlap conditions, a candidate vehicle set is determined; otherwise, the corresponding vehicle is excluded. Based on time to pick-up point, direction consistency, order waiting level, driver response records, and vehicle occupancy status, the candidate vehicle set and pending orders are combined and sorted to generate a pre-allocated combination. A temporary occupancy status is set for vehicles entering the pre-assigned combination. When a vehicle's location deviates, a driver's response times out, an order is canceled, a new order enters the same order candidate demand area, or the order waiting level changes, the pre-assigned combination is recalculated and synchronized to the driver terminal and the order management database.

[0007] Furthermore, the order data includes the passenger terminal's pick-up location, destination, order time, and vehicle type requirement written when placing the order. The vehicle availability status data includes the vehicle location, driving direction, service area boundary, driver response record, and upload record indicating that the vehicle is in an available state, uploaded by the driver terminal. The dispatch server performs time alignment on the order data, the vehicle availability status data, and the map road network time consumption data according to the vehicle identifier, order identifier, and upload timestamp. When the interval between the vehicle location upload time and the order data's order placement time meets a preset synchronization duration, the server determines the empty duration based on the upload records of consecutively available vehicles with the same vehicle identifier within a preset historical query period and includes the corresponding vehicle in the generation range of the available available vehicle resource window. When the interval does not meet the preset synchronization duration, the vehicle availability status data of the corresponding vehicle is removed.

[0008] Furthermore, the process of generating the available window for empty vehicle resources includes: reading map road network time data with the vehicle location as the starting point and the boarding location as the target point to obtain the time taken to reach the boarding point, and calculating the estimated time to reach the boarding point in combination with the current timestamp; determining directional consistency based on the deviation relationship between the driving direction and the road network direction from the vehicle location to the boarding location; and forming an initial vehicle available time range and an initial vehicle available spatial range based on the empty vehicle duration, service area boundary, the time taken to reach the boarding point, the directional consistency, and the driver response record.

[0009] Furthermore, before writing the available vehicle resource window, boundary checks are performed on the initial available vehicle time range and the initial available vehicle space range. Boundary checks include: when the expected arrival time at the boarding point falls within the initial available vehicle time range and the boarding location falls within the initial available vehicle space range, the check passes, and the initial available vehicle time range and the initial available vehicle space range are written into the corresponding vehicle's available vehicle resource window; when the expected arrival time at the boarding point does not fall within the initial available vehicle time range, or the boarding location does not fall within the initial available vehicle space range, the corresponding vehicle is removed from the candidate vehicle pre-generation range.

[0010] Furthermore, the process of aggregating pending orders into the order candidate demand area includes: the scheduling server initially collects pending orders according to the service grid to which the boarding location belongs; within the same service grid, the pending orders are further divided according to the time interval of the order placement time, the destination direction, and the vehicle type requirement; the order waiting level is determined according to the waiting time, and pending orders with the same service grid, the same time interval, the same destination direction, and the same vehicle type requirement are written into the same order candidate demand area.

[0011] Furthermore, the process of comparing the spatiotemporal overlap between the available vehicle resource window and the candidate order demand area includes: reading the available vehicle time range and available vehicle space range from the available vehicle resource window, and reading the order time interval and boarding location distribution from the candidate order demand area; first comparing the order time interval with the available vehicle time range, and if the order time interval and the available vehicle time range overlap, continuing to compare the boarding location distribution with the available vehicle space range; if the order time interval and the available vehicle time range do not overlap, excluding the corresponding vehicle; when the boarding location distribution is covered by the available vehicle space range, adding the corresponding vehicle to the candidate vehicle set; when the boarding location distribution is not covered by the available vehicle space range, not adding it to the candidate vehicle set.

[0012] Furthermore, the process of combining and sorting the candidate vehicle set with the pending orders includes: generating arrival time at the pick-up point, direction consistency, order waiting level, driver response record, and vehicle occupancy status for each candidate vehicle; when the vehicle occupancy status indicates that the vehicle is in the temporary occupancy state, the corresponding vehicle is excluded from the sortable objects of the current pending orders; when the vehicle occupancy status indicates that the vehicle is not in the temporary occupancy state, a combination sorting result is formed according to the preset priority of the arrival time at the pick-up point, direction consistency, order waiting level, and driver response record, and the pre-allocated combination is generated based on the combination sorting result.

[0013] Furthermore, the process of setting a temporary occupancy status for vehicles entering the pre-allocated combination includes: determining the correspondence between vehicles and pending orders based on the combination sorting result; performing a secondary status check before writing the vehicle occupancy status; reading the vehicle occupancy status item and determining whether the corresponding vehicle has been changed to a temporary occupancy status during the sorting period; when the vehicle occupancy status item indicates that the corresponding vehicle is not yet in a temporary occupancy status, writing the vehicle identifier, order identifier, temporary occupancy start time, response deadline, and occupancy release condition into the vehicle occupancy status; when the vehicle occupancy status item indicates that the corresponding vehicle has been changed to a temporary occupancy status, keeping the corresponding vehicle excluded from the sortable objects of the current pending orders, and selecting the next vehicle according to the combination sorting result to form a pre-allocated combination with the current pending orders.

[0014] Furthermore, the conditions for releasing the temporary occupancy include vehicle position deviation, driver response timeout, order cancellation, new order entering the same order candidate demand area, and change in order waiting level. The process of releasing the temporary occupancy status includes: when the vehicle position deviation meets the preset deviation conditions, recalculating the time taken to reach the pick-up point and directional consistency based on the updated vehicle position; when the driver response timeout or the order is cancelled, deleting the temporary occupancy correspondence between the vehicle identifier and the order identifier, and writing the vehicle identifier back to the candidate vehicle set used for combination sorting; when a new order enters the same order candidate demand area or the order waiting level changes, recalculating the pre-allocated combination according to the order waiting level, time taken to reach the pick-up point, directional consistency, and vehicle occupancy status.

[0015] Furthermore, the synchronization process after recalculating the pre-allocated combination includes: comparing the updated pre-allocated combination with the pre-allocated combination before recalculation using order identifiers and vehicle identifiers; when the correspondence between order identifiers and vehicle identifiers changes, generating release and replacement instructions, sending the release instruction to the driver terminal corresponding to the released vehicle, sending the replacement instruction to the driver terminal corresponding to the selected vehicle, and writing the updated pre-allocated combination into the order management database; when the correspondence between order identifiers and vehicle identifiers remains unchanged, only updating the response deadline and occupancy release conditions corresponding to the vehicle occupancy status.

[0016] Compared with the prior art, the advantages and positive effects of the present invention are as follows:

[0017] In this invention, by inputting passenger terminal order data, driver terminal empty vehicle status data, and road network time consumption data, the empty vehicle resource receiving window can form intermediate results on the vehicle side by including vehicle location, driving direction, empty duration, service range, and response records. The order candidate demand area can form intermediate results on the order side by including boarding location, order placement time, destination direction, vehicle type requirement, and waiting time. These two types of intermediate results are compared through spatiotemporal overlap to form a candidate vehicle set. A pre-allocation combination is then generated by combining arrival time at the boarding point, direction consistency, order waiting level, and vehicle occupancy status. Temporary occupancy status and correction trigger conditions release or replace the pre-allocation relationship when a vehicle deviates, a driver's response times out, an order is canceled, or a new order enters, reducing resource duplication and matching deviation. Attached Figure Description

[0018] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on the accompanying drawings without creative effort.

[0019] Figure 1 This is the main flowchart for the pre-allocation of empty vehicle resource orders in this invention;

[0020] Figure 2 This is a schematic diagram illustrating data time alignment in this invention;

[0021] Figure 3 This is a schematic diagram illustrating the generation of the empty vehicle resource acceptance window in this invention;

[0022] Figure 4 This is a schematic diagram illustrating the aggregation of candidate order demand areas in this invention;

[0023] Figure 5 This is a schematic diagram of the temporary occupancy state and rolling correction of the present invention. Detailed Implementation

[0024] The technical solution described in this invention will be further described below with reference to the accompanying drawings. Subsequent embodiments, based on the scope of protection text and the invention content, will describe the data source, processing order, judgment conditions, intermediate results, state changes, and output destination in the intelligent order pre-allocation and optimized scheduling method for empty vehicle resources. In subsequent embodiments, order data, empty vehicle status data, map road network time consumption data, empty vehicle resource acceptable window, order candidate demand area, candidate vehicle set, pre-allocation combination, temporary occupancy status, vehicle occupancy status, occupancy release conditions, response deadline, and order management database will all adopt the same meaning as in the scope of protection text. Since the technical solution described in this invention is a method subject, the subsequent content revolves around the data reception, data alignment, window generation, order aggregation, spatiotemporal overlap comparison, combination sorting, temporary occupancy, release correction, and state synchronization of the scheduling server in the order pre-allocation process, and will not be further expanded in a carrier form that does not appear as an independent subject in the technical solution described in the application documents. No numerical labels are set for physical components in the accompanying drawings; the process nodes, data nodes, and status nodes in the accompanying drawings are only used to identify the method processing objects, execution order, and data flow direction.

[0025] Please see Figures 1 to 5 This embodiment provides an intelligent order pre-allocation and optimized scheduling method for empty vehicle resources, applicable to ride-hailing, taxi scheduling, or order scheduling scenarios with vehicle empty status reporting capabilities. The method is executed by the scheduling server after receiving order data uploaded from passenger terminals and empty vehicle status data uploaded from driver terminals. During execution, the scheduling server calls map road network time data and synchronizes the pre-allocation combination, temporary occupancy status, and recalculated status to the driver terminal and order management database.

[0026] S1, the dispatch server receives order data uploaded by passenger terminals and empty vehicle status data uploaded by driver terminals, and calls map road network time consumption data.

[0027] Order data is written by passengers when they place an order. This data includes the boarding location, destination, order time, and vehicle type requirement. The boarding location determines the departure point of the order, the destination direction, the order time the time frame for entering the scheduling process, and the vehicle type requirement limits the service type a vehicle must fulfill for pre-allocation. After the order data enters the scheduling server, it is aggregated according to order identifiers, ensuring that the boarding location, destination, order time, and vehicle type requirement for the same order can be continuously accessed during subsequent order aggregation, waiting level determination, and sorting processes.

[0028] The vehicle vacancy status data is uploaded by the driver's terminal. This data includes vehicle location, direction of travel, service area boundary, driver response record, and upload record indicating the vehicle is in an vacant state. Vehicle location determines the vehicle's current spatial position; direction of travel is used to determine deviation from the road network direction from the vehicle's location to the pick-up location; service area boundary defines the spatial boundary for the vehicle's participation in pre-assignment; driver response record reflects the driver's terminal's response status to historical pre-assignment or dispatch requests; and upload record indicating the vehicle is in an vacant state determines the duration of the vacancy. After the vacancy status data enters the dispatch server, the server aggregates it according to vehicle identifiers, ensuring that the vehicle location, direction of travel, service area boundary, driver response record, and upload record for the same vehicle form a continuous vehicle-side status basis.

[0029] Map road network time consumption data is retrieved by the dispatch server when generating the available window for empty vehicle resources and during combination sorting. This data is used to determine the time taken to reach the pick-up point based on vehicle location, pick-up location, and road network direction, and participates in subsequent steps in generating the estimated arrival time at the pick-up point, direction consistency, and combination sorting results. As the external road network foundation used in the calculations, map road network time consumption data does not alter the meaning of fields in the order data and empty vehicle status data.

[0030] S2, the dispatch server aligns the order data, empty vehicle status data, and map road network time data according to the vehicle identifier, order identifier, and upload timestamp.

[0031] Time alignment compares the order placement time in the order data with the vehicle location upload time in the vehicle availability status data. The dispatch server first determines the pending orders entering the current dispatch round based on the order identifier, then reads the corresponding vehicle's availability status data based on the vehicle identifier, and uses the upload timestamp to determine whether the vehicle's location, driving direction, service area boundary, driver response record, and upload record indicating that the vehicle is in an availability state belong to the data range eligible to participate in the current dispatch round. When map road network time consumption data is retrieved, a correspondence is established with the vehicle location, boarding location, and current timestamp to prevent data from different time sources from directly entering the same calculation process.

[0032] When the interval between the vehicle location upload time and the order placement time meets the preset synchronization duration, the dispatch server includes the corresponding vehicle in the generated range of the available empty vehicle resource window. Meeting the preset synchronization duration indicates that the vehicle location and the order placement time of the pending order have a temporal correspondence within the same dispatch round, which can serve as input for the consistency of subsequent arrival time at the pick-up point, estimated arrival time at the pick-up point, and direction. The dispatch server reads upload records of vehicles with the same identifier continuously in an empty state within a preset historical query period and determines the empty duration based on these consecutive empty upload records. The empty duration serves as the vehicle-side time status, used to subsequently form the available vehicle time range.

[0033] When the interval between the vehicle location upload time and the order placement time does not meet the preset synchronization time, the scheduling server removes the corresponding vehicle's available vehicle status data. The removed available vehicle status data does not enter the generation process of the available vehicle resource window, nor does it participate in the formation of the subsequent candidate vehicle set. Through the above processing, the data entering subsequent steps establishes a correspondence between vehicle identifier, order identifier, and upload timestamp, avoiding direct matching of expired vehicle status with currently pending orders.

[0034] S3 generates an available window for empty vehicle resources based on vehicle location, driving direction, empty duration, service area boundary, time taken to reach the pick-up point, and driver response records.

[0035] The dispatch server reads map road network time data starting from the vehicle's location and ending at the boarding location to obtain the time taken to reach the boarding point. It then combines this with the current timestamp to calculate the estimated arrival time at the boarding point. The arrival time at the boarding point serves as the time consumed by the vehicle from its current location to the boarding location of the pending order, while the estimated arrival time serves as input for determining the vehicle's available time. The current timestamp can be the time record from when the dispatch server initiated the current dispatch round, ensuring a unified time reference between the arrival time at the boarding point and the current dispatch round.

[0036] The dispatch server determines directional consistency based on the deviation between the driving direction and the road network direction from the vehicle's location to the pick-up location. The driving direction is derived from the vehicle's empty vehicle status data uploaded by the driver's terminal, while the road network direction is derived from the map's road network time-travel data describing the path direction from the vehicle's location to the pick-up location. Directional consistency indicates whether there is a corresponding direction that can participate in pre-assignment between the vehicle's current driving direction and the road network direction near the pick-up location. Directional consistency does not determine the pre-assignment combination independently, but is included in the combination and sorting process along with the time taken to reach the pick-up point, order waiting level, driver response record, and vehicle occupancy status.

[0037] The dispatch server generates initial vehicle-capable time and spatial ranges based on idle duration, service area boundaries, time to reach the pick-up point, directional consistency, and driver response records. The initial vehicle-capable time range is constrained by idle duration, time to reach the pick-up point, and estimated time to reach the pick-up point, representing the time boundary of orders a vehicle can accept in the current dispatch round. The initial vehicle-capable spatial range is constrained by vehicle location, service area boundaries, and directional consistency, representing the spatial boundary of orders a vehicle can accept in the current dispatch round. Driver response records, when used in generating these ranges, reflect the driver's terminal's response status to pre-assignment requests, establishing a correspondence between the response status and the vehicle's capacity to accept orders.

[0038] S4, before writing the available window for empty vehicle resources, performs boundary checks on the initial available time range and the initial available space range for vehicles.

[0039] Boundary verification considers the estimated arrival time at the boarding point, the boarding location, the initial vehicle's available time range, and the initial vehicle's available space range. The scheduling server first determines whether the estimated arrival time at the boarding point falls within the initial vehicle's available time range, and then determines whether the boarding location falls within the initial vehicle's available space range. If both determinations pass, the verification is successful, and the scheduling server writes the initial vehicle's available time range and available space range into the corresponding vehicle's available time and space ranges. The written available space window includes the vehicle's available time and space ranges, serving as an intermediate result on the vehicle side for subsequent comparisons of spatiotemporal overlap with candidate order demand areas.

[0040] When the estimated arrival time at the boarding point does not fall within the initial vehicle's available time range, or the boarding location does not fall within the initial vehicle's available spatial range, the dispatch server removes the corresponding vehicle from the candidate vehicle generation range. Removed vehicles do not enter the candidate vehicle set formation process for the current pending order. Through boundary checks, the dispatch server constrains the vehicle's temporal and spatial boundaries before forming the available vehicle resource window, ensuring that vehicles subsequently participating in spatiotemporal overlap comparisons have a clear available window.

[0041] S5 aggregates pending orders into candidate demand areas based on pick-up location, order time, destination direction, vehicle type requirements, and waiting time.

[0042] The dispatch server initially aggregates pending orders according to the service grid to which the boarding location belongs. A service grid represents the spatial region where the boarding location of an order is located; this initial aggregation ensures that pending orders with similar boarding locations are processed within the same spatial area. Within the same service grid, the dispatch server further divides pending orders according to the time interval of the order placement, the destination direction, and vehicle type requirements. The time interval of the order placement indicates the time range within which a pending order enters the dispatch process; the destination direction is determined by the directional relationship between the destination and the boarding location; and the vehicle type requirements limit the types of vehicles acceptable for the order.

[0043] The scheduling server determines the order waiting level based on the waiting time. The waiting time is determined by the temporal relationship between the time record corresponding to the current scheduling round and the order placement time. The order waiting level is used in the combination and sorting process. The scheduling server writes pending orders with the same service grid, the same time interval, the same destination direction, and the same vehicle type requirement into the same order candidate demand area. The order candidate demand area serves as an intermediate result on the order side, used to compare the spatiotemporal overlap with the available vehicle resource window, and is used to trigger recalculation when new orders enter the same order candidate demand area or when the order waiting level changes.

[0044] S6 compares the spatiotemporal overlap between the available vehicle resources window and the order candidate demand area. When the overlap meets the preset spatiotemporal overlap conditions, the candidate vehicle set is determined. When the overlap does not meet the preset spatiotemporal overlap conditions, the corresponding vehicle is excluded.

[0045] The dispatch server reads the available vehicle time range and available vehicle space range from the available vehicle resource window, and reads the order time intervals and boarding location distribution from the order candidate demand area. The order time interval is formed by the time interval to which the order placement time of the pending orders within the order candidate demand area belongs, and the boarding location distribution is formed by the boarding location of the pending orders within the order candidate demand area. The available vehicle time range and the order time interval constitute the comparison objects in the time dimension, and the available vehicle space range and the boarding location distribution constitute the comparison objects in the spatial dimension.

[0046] The dispatch server first compares the order time interval with the vehicle's available time range. If the order time interval and the vehicle's available time range overlap, it continues to compare the boarding location distribution with the vehicle's available space. If the order time interval and the vehicle's available time range do not overlap, the dispatch server excludes the corresponding vehicle. The above time comparison forms a pre-judgment of the preset spatiotemporal overlap condition, preventing vehicles with mismatched time boundaries from entering the spatial comparison and combination sorting.

[0047] After the time overlap condition is met, the scheduling server compares the boarding location distribution with the available space for each vehicle. If the boarding location distribution is covered by the available space, the corresponding vehicle is added to the candidate vehicle set; if the boarding location distribution is not covered by the available space, it is not added to the candidate vehicle set. The candidate vehicle set consists of vehicles that simultaneously meet the time overlap and spatial coverage conditions, and serves as the vehicle-side input for subsequent combination and sorting.

[0048] S7, based on arrival time at the pick-up point, direction consistency, order waiting level, driver response record, and vehicle occupancy status, combines and sorts the candidate vehicle set with the orders to be served to generate a pre-allocated combination.

[0049] The dispatch server generates four items for each candidate vehicle: arrival time at the pick-up point, direction consistency, order waiting level, driver response record, and vehicle occupancy status. The arrival time at the pick-up point is derived from the arrival time determined by map road network time data. The direction consistency is derived from the deviation between the driving direction and the road network direction from the vehicle's position to the pick-up position. The order waiting level is derived from the order waiting level corresponding to the waiting time. The driver response record is derived from the driver's terminal's historical response status. The vehicle occupancy status is derived from whether the vehicle has been written to a temporary occupancy status. These items are intermediate processing items for combined sorting and are not individually used as the final pre-allocation result.

[0050] When the vehicle occupancy status indicates that a vehicle is in a temporary occupancy state, the scheduling server will exclude the corresponding vehicle from the sortable objects of the current pending orders. This exclusion process is used to prevent the same vehicle from repeatedly entering the combined sorting of the current pending orders during the temporary occupancy period. The excluded vehicle retains its vehicle identifier and the original temporary occupancy correspondence, which is used to release it or re-enter the sorting when the occupancy release conditions are met.

[0051] When the vehicle occupancy status indicates that the vehicle is not in a temporary occupancy state, the dispatch server generates a combined sorting result based on the preset priorities of arrival time at the pick-up point, direction consistency, order waiting level, and driver response record. This combined sorting result is then used to generate a pre-allocated combination. The combined sorting result is used to determine the correspondence between vehicles and pending orders, while the pre-allocated combination serves as input for writing temporary occupancy status, driver terminal notifications, and order management database updates.

[0052] S8 sets a temporary occupancy status for vehicles entering the pre-assigned combination.

[0053] The scheduling server determines the correspondence between vehicles and pending orders based on the combined sorting results. Before writing the vehicle occupancy status, it performs a secondary status check, reading the vehicle occupancy status item and determining whether the corresponding vehicle has been changed to a temporary occupancy status during the sorting process. This secondary status check occurs after the combined sorting results are generated and before the vehicle occupancy status is written, and is used to handle situations where the vehicle occupancy status changes between the sorting process and the status writing process.

[0054] When the vehicle occupancy status indicates that the corresponding vehicle is not yet in a temporary occupancy state, the dispatch server writes the vehicle identifier, order identifier, temporary occupancy start time, response deadline, and occupancy release condition into the vehicle occupancy status. The vehicle identifier points to the vehicle entering the pre-allocation group, the order identifier points to the corresponding pending order, the temporary occupancy start time records the time the vehicle enters the temporary occupancy state, the response deadline determines the time boundary for the driver terminal to provide a response status, and the occupancy release condition is used to subsequently determine whether to release or replace the pre-allocation relationship. After the vehicle occupancy status is written, the corresponding vehicle will not be repeatedly entered into the sorting process as a currently pending order until the response deadline or occupancy release condition is met.

[0055] When a vehicle occupancy status indicates that the corresponding vehicle has been changed to a temporary occupancy status, the scheduling server excludes the corresponding vehicle from the sortable objects of the current pending orders and selects the next vehicle to form a pre-allocated combination with the current pending orders according to the combination sorting result. After the next vehicle is selected, the scheduling server performs a pre-write status check again to ensure that the pre-allocated combination and the vehicle occupancy status maintain a consistent write order.

[0056] S9 releases the temporary occupancy status and recalculates the pre-allocated combination when the vehicle's position deviates, the driver's response timeout occurs, the order is canceled, a new order enters the same order candidate demand area, or the order waiting level changes.

[0057] Conditions for releasing vehicle occupancy include vehicle location deviation, driver response timeout, order cancellation, new order entering the same order candidate demand area, and changes in order waiting level. The scheduling server determines whether to initiate a release or recalculation process based on the vehicle identifier, order identifier, response deadline, and occupancy release conditions recorded in the vehicle occupancy status. Each triggering condition in the occupancy release process corresponds to a different source of status change, but all are based on the correspondence between pre-allocated combinations and vehicle occupancy statuses.

[0058] When a vehicle's position deviates from the preset deviation conditions, the dispatch server recalculates the arrival time and directional consistency at the pick-up point based on the updated vehicle position. The updated vehicle position is derived from the empty vehicle status data subsequently uploaded by the driver's terminal. The recalculated arrival time and directional consistency are then incorporated into the recalculation process of the pre-assigned combination. When the vehicle's position deviates from the preset deviation conditions, the dispatch server does not release the temporary occupancy status due to the change in vehicle position; instead, it maintains the original temporary occupancy correspondence between the vehicle identifier and the order identifier.

[0059] When a driver's response times out or an order is cancelled, the dispatch server deletes the temporary occupancy relationship between the vehicle identifier and the order identifier, and writes the vehicle identifier back to the candidate vehicle set used for combined sorting. Driver response timeout is determined by the time relationship between the response deadline and the driver's terminal response status; order cancellation is triggered by a change in order status in the order management database. After the vehicle identifier is written back, the corresponding vehicle can be re-sorted as a sortable object in subsequent combined sorting processes.

[0060] When a new order enters the same order candidate demand area or the order waiting level changes, the scheduling server recalculates the pre-allocation combinations based on the order waiting level, time taken to reach the pick-up point, directional consistency, and vehicle occupancy status. A new order entering the same order candidate demand area indicates a change in the order-side demand set, while a change in the order waiting level indicates a change in the order's ranking status. During recalculation, the scheduling server retains the established data source order; that is, it first reads the order candidate demand area and candidate vehicle set, then excludes vehicles in a temporary occupancy state that do not meet the release conditions based on vehicle occupancy status, and finally forms a new pre-allocation combination according to the combination ranking rules.

[0061] S10: After recalculating the pre-allocated combination, the recalculation result will be synchronized to the driver terminal and the order management database.

[0062] The scheduling server compares the updated pre-allocated combinations with the pre-allocated combinations before recalculation using order identifiers and vehicle identifiers. Order identifiers are used to identify the same order to be served, and vehicle identifiers are used to identify the same candidate vehicle. The comparison result is used to determine whether the correspondence between vehicles and orders to be served has changed.

[0063] When the mapping between order identifiers and vehicle identifiers changes, the dispatch server generates release and replacement instructions. The release instruction is sent to the driver's terminal corresponding to the released vehicle, and the replacement instruction is sent to the driver's terminal corresponding to the selected vehicle. The updated pre-assignment combination is then written to the order management database. The release instruction causes the driver's terminal of the released vehicle to no longer retain the current order's pre-assignment notification, while the replacement instruction causes the driver's terminal of the selected vehicle to receive the new pre-assignment notification. The order management database records the updated order status and vehicle occupancy status.

[0064] When the correspondence between order identifiers and vehicle identifiers remains unchanged, the dispatch server only updates the response deadline and occupancy release conditions corresponding to the vehicle occupancy status. This process means that the correspondence between vehicles and pending orders remains unchanged after recalculation, but the time boundaries or release trigger conditions in the vehicle occupancy status need to be updated according to the current dispatch round. Through the above synchronization process, the pre-allocation status in the driver terminal, order management database, and dispatch server maintains a consistent data flow.

[0065] In this embodiment, order data, empty vehicle status data, and map road network time consumption data are sequentially used to form vehicle-side intermediate results, order-side intermediate results, and dispatch-side combined results. The available empty vehicle resource window serves as the vehicle-side intermediate result, including the available vehicle time range and available vehicle space range; the order candidate demand area serves as the order-side intermediate result, including the order time interval, boarding location distribution, destination direction, vehicle type requirement, and order waiting level; the pre-allocation combination serves as the dispatch-side combined result, recording the pre-allocation correspondence between vehicles and pending orders; and the temporary occupancy status serves as the resource status result, recording the vehicle identifier, order identifier, temporary occupancy start time, response deadline, and occupancy release conditions. The above results are connected in the order of data input, window generation, order aggregation, spatiotemporal comparison, sorting generation, occupancy writing, trigger correction, and status synchronization.

[0066] The preset synchronization duration, preset historical query cycle, preset priority, and preset deviation conditions in the above implementation process are all determined by the configuration supported by the technical solution described in the application documents. These parameters are used to limit the execution conditions for time alignment, historical record reading, combined sorting, and position deviation judgment, and are not considered as unsourced numerical results or performance data. The vehicle location, driving direction, service area boundary, driver response record, upload timestamp, order identifier, vehicle identifier, response deadline, and occupancy release conditions involved in the above implementation process are all data objects read, generated, or written by the scheduling server in the corresponding steps. Subsequent calls to these data objects are based on the already formed intermediate results.

[0067] The specific processes, field states, processing order, judgment conditions, parameter sources, and data collaboration relationships described above are used to explain the possible implementation methods of this invention and should not be limited to the specific implementation processes listed. Without departing from the scope of the technical solutions described in this invention, any equivalent substitutions, equivalent modifications, equivalent combinations, order adjustments, equivalent transformations of field names, equivalent acceptance of the executing entity, or equivalent changes in the carrier form that can be conceived by those skilled in the art should fall within the protection scope of this invention; however, the aforementioned equivalent changes should not be extended to unclaimed topics, nor should they alter the substantive correspondence between order data, empty vehicle status data, empty vehicle resource availability window, order candidate demand area, candidate vehicle set, pre-allocation combination, temporary occupancy status, and vehicle occupancy status through changes in text names.

Claims

1. A method for intelligent order pre-allocation and optimized scheduling of empty vehicle resources, characterized in that, The dispatch server receives order data uploaded by passenger terminals and empty vehicle status data uploaded by driver terminals, and calls map road network time data; Based on vehicle location, direction of travel, duration of vacancy, service area boundaries, time taken to reach the pick-up point, and driver response records, generate a window of available vacant vehicle resources. Based on the pick-up location, order time, destination direction, vehicle type requirement, and waiting time, pending orders are aggregated into order candidate demand areas; The spatiotemporal overlap between the available vehicle resources window and the candidate order demand area is compared. When the overlap meets the preset spatiotemporal overlap conditions, a candidate vehicle set is determined. When the overlap does not meet the preset spatiotemporal overlap conditions, the corresponding vehicle is excluded. Based on arrival time at the pick-up point, direction consistency, order waiting level, driver response record, and vehicle occupancy status, the candidate vehicle set and the pending orders are combined and sorted to generate a pre-allocated combination. A temporary occupancy status is set for vehicles entering the pre-assigned combination. When a vehicle's location deviates, a driver's response times out, an order is canceled, a new order enters the same order candidate demand area, or the order waiting level changes, the pre-assigned combination is recalculated and synchronized to the driver terminal and the order management database.

2. The intelligent order pre-allocation and optimized scheduling method for empty vehicle resources according to claim 1, characterized in that, The order data includes the passenger terminal's pick-up location, destination, order time, and vehicle type requirements when placing an order. The vehicle availability status data includes the vehicle location, driving direction, service area boundary, driver response record, and upload record indicating that the vehicle is in an available state uploaded by the driver terminal. The dispatch server performs time alignment on the order data, the vehicle availability status data, and the map road network time consumption data according to the vehicle identifier, order identifier, and upload timestamp. When the interval between the vehicle location upload time and the order data placement time meets the preset synchronization time, the idle duration is determined based on the upload records of the same vehicle identifier that are continuously in an empty vehicle state within the preset historical query period, and the corresponding vehicle is included in the generation range of the empty vehicle resource acceptance window. When the interval does not meet the preset synchronization duration, the empty vehicle status data of the corresponding vehicle is removed.

3. The intelligent order pre-allocation and optimized scheduling method for empty vehicle resources according to claim 2, characterized in that, The process of generating the available window for empty vehicles includes: Starting from the vehicle's location and ending at the boarding location, read the map's road network time data to obtain the time taken to reach the boarding point, and combine this with the current timestamp to calculate the estimated time to reach the boarding point. Directional consistency is determined based on the deviation relationship between the driving direction and the road network direction from the vehicle position to the boarding position; The initial vehicle's available time range and initial vehicle's available space range are formed based on the empty load duration, service area boundary, time taken to reach the pick-up point, directional consistency, and driver response records.

4. The intelligent order pre-allocation and optimized scheduling method for empty vehicle resources according to claim 3, characterized in that, Before writing the available vehicle resource window, boundary checks are performed on the initial available vehicle time range and the initial available vehicle space range. The boundary checks include: When the estimated arrival time at the boarding point falls within the initial vehicle's available time range and the boarding location falls within the initial vehicle's available space range, the verification passes, and the initial vehicle's available time range and initial vehicle's available space range are written into the corresponding vehicle's available time range and available space range. If the estimated arrival time at the boarding point does not fall within the initial vehicle's available time range, or the boarding location does not fall within the initial vehicle's available space range, the corresponding vehicle will be removed from the candidate vehicle's preliminary generation range.

5. The intelligent order pre-allocation and optimized scheduling method for empty vehicle resources according to claim 1, characterized in that, The process of aggregating pending orders into the order candidate demand region includes: The dispatch server initially aggregates the service orders to be served according to the service grid to which the boarding location belongs; Within the same service grid, service orders are further divided according to the time interval of the order placement time, the destination direction, and the vehicle type requirements; Order waiting levels are determined based on waiting time, and pending orders with the same service grid, time interval, destination direction, and vehicle type are written into the same order candidate demand area.

6. The intelligent order pre-allocation and optimized scheduling method for empty vehicle resources according to claim 1, characterized in that, The process of comparing the spatiotemporal overlap between the available vehicle resources window and the candidate order demand area includes: Read the available vehicle time range and available vehicle space range from the available vehicle resource window, and read the order time interval and boarding location distribution from the order candidate demand area; First, compare the order time interval with the vehicle's available time range. If the order time interval overlaps with the vehicle's available time range, then continue to compare the boarding location distribution with the vehicle's available space range. If the order time interval does not overlap with the vehicle's available time range, then exclude the corresponding vehicle. When the distribution of boarding locations is covered by the space that the vehicle can accommodate, the corresponding vehicle is added to the candidate vehicle set; when the distribution of boarding locations is not covered by the space that the vehicle can accommodate, it is not added to the candidate vehicle set.

7. The intelligent order pre-allocation and optimized scheduling method for empty vehicle resources according to claim 1, characterized in that, The process of combining and sorting the candidate vehicle set with the pending orders includes: For each candidate vehicle, the following items are generated: arrival time at the pick-up point, direction consistency, order waiting level, driver response record, and vehicle occupancy status. When the vehicle occupancy status item indicates that the vehicle is in the temporary occupancy status, the corresponding vehicle will be excluded from the sortable objects of the current pending orders. When the vehicle occupancy status item indicates that the vehicle is not in the temporary occupancy status, a combination sorting result is formed according to the preset priority of the arrival time at the pick-up point item, the direction consistency item, the order waiting level item, and the driver response record item, and the pre-allocated combination is generated based on the combination sorting result.

8. The intelligent order pre-allocation and optimized scheduling method for empty vehicle resources according to claim 7, characterized in that, The process of setting a temporary occupancy status for vehicles entering the pre-assigned group includes: The correspondence between vehicles and pending orders is determined based on the combined sorting results. A secondary status check is performed before writing the vehicle occupancy status. The vehicle occupancy status item is read and it is determined whether the corresponding vehicle has been changed to a temporary occupancy status during the sorting period. When the vehicle occupancy status item indicates that the corresponding vehicle is not yet in a temporary occupancy status, the vehicle identifier, order identifier, temporary occupancy start time, response deadline time, and occupancy release condition are written into the vehicle occupancy status; When the vehicle occupancy status item indicates that the corresponding vehicle has been changed to a temporary occupancy status, the corresponding vehicle is excluded from the sortable objects of the current pending orders, and the next vehicle is selected according to the combined sorting result to form a pre-allocated combination with the current pending orders.

9. The intelligent order pre-allocation and optimized scheduling method for empty vehicle resources according to claim 8, characterized in that, The conditions for releasing the occupancy include vehicle position deviation, driver response timeout, order cancellation, new order entering the same order candidate demand area, and order waiting level change. The process of releasing the temporary occupancy status includes: when the vehicle position deviation meets the preset deviation conditions, the time taken to reach the pick-up point and the consistency of direction are recalculated based on the updated vehicle position. When a driver's response times out or an order is cancelled, the temporary occupancy relationship between the vehicle identifier and the order identifier is deleted, and the vehicle identifier is written back to the candidate vehicle set used for combination sorting. When a new order enters the same order candidate demand area or the order waiting level changes, the pre-allocation combination is recalculated according to the order waiting level, time taken to reach the boarding point, direction consistency, and vehicle occupancy status.

10. The intelligent order pre-allocation and optimized scheduling method for empty vehicle resources according to claim 9, characterized in that, The synchronization process after recalculating the pre-allocated combination includes: The updated pre-allocation combination is compared with the pre-allocation combination before recalculation using order and vehicle identifiers; When the correspondence between order identifier and vehicle identifier changes, release instruction and replacement instruction are generated. The release instruction is sent to the driver terminal corresponding to the released vehicle, and the replacement instruction is sent to the driver terminal corresponding to the selected vehicle. The updated pre-assigned combination is written to the order management database. When the correspondence between order identifier and vehicle identifier remains unchanged, only the response deadline and occupancy release conditions corresponding to the vehicle occupancy status are updated.

Images