A method and system for collaborative lifecycle management of heterogeneous orders from multiple channels

By adopting a collaborative management approach that unifies order tables and vehicle scheduling tables, the problem of duplicate vehicle allocation in multi-channel order systems has been solved, achieving unified global management and resource scheduling, improving vehicle resource utilization efficiency, and providing a refund mechanism and user experience guarantee.

CN123117657APending Publication Date: 2026-11-17HANGZHOU MAIJU TECHNOLOGY CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202611325545.9
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2026-08-28
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

In existing technologies, multi-channel order systems lack a globally unified vehicle occupancy verification mechanism, which means that the same vehicle may be allocated by multiple channels at the same time, making it difficult to achieve unified global management across multiple channels and resulting in concurrent conflicts in vehicle resource allocation.

Method used

A lifecycle collaborative management method based on heterogeneous orders from multiple channels is adopted. By using a unified order table and a unified vehicle scheduling table, channel orders are obtained and vehicle occupancy requests are generated. Vehicle numbers are locked, existing occupancy records are queried, and occupancy records are unlocked or written, thus solving the problem of overlapping vehicle allocation and achieving unified global management.

Benefits of technology

It enables unified global management of orders from multiple channels, eliminates concurrent conflicts in vehicle resource allocation, improves the utilization efficiency of vehicle resources, and provides a refund mechanism and user experience guarantee.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123117657A_ABST
    Figure CN123117657A_ABST
Patent Text Reader

Abstract

This invention relates to a lifecycle collaborative management method and system based on heterogeneous orders from multiple channels, involving resource scheduling management technology. The method includes: acquiring channel orders and storing them in a unified order table; extracting channel orders from the unified order table; extracting channel orders with a pending lock status as vehicle-occupying orders; generating vehicle occupancy requests; locking vehicle numbers and searching for existing occupancy records corresponding to the vehicle numbers in a unified vehicle scheduling table; extracting vehicle occupancy time periods from existing occupancy records; if the expected occupancy time period overlaps with the vehicle occupancy time period, unlocking the vehicle number and outputting a preset vehicle occupancy signal; if the expected occupancy time period does not overlap with the vehicle occupancy time period, writing the vehicle occupancy request as an occupancy record into the unified vehicle scheduling table and unlocking the vehicle number. This invention achieves unified global management across multiple channels.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention relates to the field of resource scheduling and management technology, and in particular to a lifecycle collaborative management method and system based on multi-channel heterogeneous orders. Background Technology

[0002] As the car rental industry continues to develop, rental companies generally build multiple online ordering channels to expand their customer base. Different channels are adapted to different rules for real-name authentication, deposit payment, and order cancellation, and all of them share the same batch of vehicle rental resources. Therefore, the industry's demand for multi-channel collaborative management is constantly increasing.

[0003] In existing technologies, each online ordering channel independently maintains order data and vehicle occupancy records. Vehicle inventory information is synchronized between channels through periodic polling. Each channel is configured with its own order status flow logic, and resource concurrency control is achieved within a single channel. Each channel independently executes business operations such as vehicle allocation and order cancellation.

[0004] Regarding the aforementioned technologies, storing data separately from multiple channels and relying on polling for synchronization can lead to data time lags. The lack of a globally unified vehicle occupancy verification mechanism makes it easy for the same vehicle to be allocated by multiple channels simultaneously, making it difficult to achieve unified global management across multiple channels. There is still room for improvement. Summary of the Invention

[0005] To achieve unified global management across multiple channels, this invention provides a method and system for collaborative lifecycle management of heterogeneous orders from multiple channels.

[0006] Firstly, the present invention provides a lifecycle collaborative management method based on heterogeneous orders from multiple channels, employing the following technical solution: A lifecycle collaborative management method based on multi-channel heterogeneous orders includes: Step 1: Obtain channel orders from multiple channels and store them in a pre-defined unified order table; Step 2: Extract channel orders from the unified order table, where each channel order includes its order status; Step 3: Extract channel orders with a preset pending order status as orders requiring vehicle occupancy; Step 4: Generate a vehicle occupancy request based on the vehicle occupancy order. The vehicle occupancy request includes the vehicle number and the expected occupancy period. Step 5: Lock the vehicle number and search for the existing occupied record corresponding to the vehicle number in the preset unified vehicle scheduling table. Step 6: Extract the vehicle occupancy period from the existing occupancy records; Step 60: If the expected occupancy period overlaps with the vehicle occupancy period, unlock the vehicle number and output a preset vehicle occupancy signal; Step 61: If the expected occupancy period does not overlap with the vehicle occupancy period, the vehicle occupancy request is written as an occupancy record into the unified vehicle scheduling table, and the vehicle number is unlocked.

[0007] By adopting the above technical solution, channel orders are stored in a unified order table, orders requiring vehicle occupancy are filtered out for those in the pending lock status, and vehicle occupancy requests containing vehicle numbers and expected occupancy time periods are generated. Vehicle numbers are locked, and existing occupancy records are retrieved from the unified vehicle scheduling table, and the vehicle occupancy time periods are extracted. If the time periods overlap, the vehicle is unlocked and a vehicle occupancy signal is output. If there is no overlap, the vehicle number is unlocked after writing the occupancy record. This solves the problem of the same vehicle being allocated by multiple channels at the same time, realizes global unified management of multi-channel orders, achieves global unified scheduling of vehicle resources, and fundamentally eliminates concurrent conflicts in vehicle resource allocation.

[0008] Optionally, before acquiring channel orders from multiple channels, a method for generating the expected time period is also included, which includes: Step 10: Obtain the vehicle query request initiated by the user terminal, and extract the target vehicle number from the vehicle query request; Step 11: Based on the target vehicle number, search for the existing occupied record corresponding to the target vehicle number in the preset unified vehicle scheduling table; Step 12: Based on the existing occupancy records, reverse-engineer the unoccupied time periods corresponding to the target vehicle number as recommended time periods; Step 13: Push the recommended time period and preset time period selection signals to the user terminal; Step 14: Receive the desired time period from the user terminal and output the desired time period as the expected occupancy time period.

[0009] By adopting the above technical solution, the system obtains the vehicle usage query request, extracts the target vehicle number, queries the existing occupancy records of the unified vehicle scheduling table, reversely generates unoccupied time slots as recommended time slots, pushes the recommended time slots and time slot selection signals to the user terminal, receives the expected time slots from the user terminal and outputs them as expected occupancy time slots, thus solving the problem of order failure caused by users not knowing the available dates, and realizing the effect of informing users of the available dates in advance so as to obtain effective time slots.

[0010] Optionally, it also includes a method for handling situations where the expected occupancy period overlaps with the vehicle occupancy period, the method comprising: Step 600: Define vehicle occupancy periods that overlap with the expected occupancy periods as overlapping occupancy periods; Step 601: Obtain the conflicting time period by taking the intersection of the overlapping occupancy time period and the expected occupancy time period; Step 602: Query the users who have occupied the space based on the existing occupancy records corresponding to the overlapping occupancy periods; Step 603: Push the conflict period and the preset early termination signal to the user terminal corresponding to the occupied user; Step 604: If a termination rejection signal is received from the user terminal, unlock the vehicle number and output a preset vehicle occupancy signal; Step 605: If an end confirmation signal is received from the user terminal, the refund amount is calculated based on the conflict period and the preset time refund coefficient, and the refund amount is returned to the user terminal corresponding to the occupied user. Step 606: Remove conflicting periods from the overlapping occupancy periods to obtain the actual occupancy periods; Step 607: Update the existing occupancy record according to the actual occupancy period, write the vehicle occupancy request as an occupancy record into the unified vehicle scheduling table, and unlock the vehicle number.

[0011] By adopting the above technical solution, conflicting time periods are determined, corresponding occupied users are queried, and conflicting time periods and early termination signals are pushed to their user terminals. Upon receiving an termination rejection signal, the vehicle number is unlocked and a vehicle occupancy signal is output. Upon receiving an termination confirmation signal, the refund amount is calculated based on the conflicting time period and the time refund coefficient. The actual occupied time period is obtained by removing the conflicting time period from the overlapping occupied time period. The existing occupancy record is updated, and the vehicle number is unlocked after writing the occupancy record. By coordinating with occupied users to terminate their usage period early, the effect of subsequent users using the vehicles they ordered can be achieved. This provides a refund mechanism to compensate occupied users and improves the utilization efficiency of vehicle resources.

[0012] Optionally, methods for pushing conflict periods and preset early termination signals to the user terminals corresponding to the occupied users include: Step 6030: Obtain the actual vehicle usage records of the users whose vehicles are occupied, corresponding to the vehicle number; Step 6031: Extract the actual usage time and current occupancy time from the actual vehicle usage records; Step 6032: Calculate the actual usage percentage based on the actual usage time and the current occupancy time; Step 6033: If the actual vehicle usage ratio is higher than the preset high frequency ratio, unlock the vehicle number and output the preset vehicle occupancy signal. Step 6034: If the actual usage ratio is not higher than the preset high-frequency ratio, then push the conflict period and the preset early termination signal to the user terminal corresponding to the occupied user.

[0013] By adopting the above technical solution, the actual vehicle usage records of occupied users are obtained, the actual usage time and the current occupation time are extracted, and the actual usage ratio is calculated. If the actual usage ratio is higher than the high frequency ratio, the vehicle number is unlocked and a vehicle occupation signal is output. Otherwise, a conflict time period and an early termination signal are pushed to the user terminal of the occupied user, thus realizing the effect of judging whether the user will end the vehicle usage early based on the user's actual usage ratio.

[0014] Optionally, it also includes a method for handling a termination rejection signal received from a user terminal, the method comprising: Step 6040: Search for the corresponding vehicle model characteristics in the preset vehicle database based on the vehicle number; Step 6041: Search the vehicle database for candidate vehicle numbers that meet the vehicle model characteristics; Step 6042: Find the corresponding candidate occupancy record in the unified vehicle schedule table based on the candidate vehicle number, and extract the candidate occupancy time period from the candidate occupancy record; Step 6043: Compare the candidate occupancy periods with the expected occupancy periods, filter out the candidate occupancy periods that do not overlap with the expected occupancy periods, and define them as recommended occupancy periods; Step 6044: Define the candidate vehicle number corresponding to the recommended time period as the recommended vehicle number and push it to the user terminal; Step 6045: Upon receiving the recommendation confirmation signal from the user terminal, update the vehicle reservation order based on the recommended vehicle number to obtain the recommended vehicle reservation order; Step 6046: Regenerate a vehicle occupancy request based on the recommended vehicle occupancy order and execute steps 5 to 61.

[0015] By adopting the above technical solution, vehicle model characteristics are obtained from the vehicle database based on the vehicle number, and candidate vehicle numbers are searched; candidate occupancy records are queried to extract candidate occupancy time periods, and recommended occupancy time periods are selected by comparison and filtering, and the corresponding recommended vehicle numbers are pushed to the user terminal; upon receiving the recommendation confirmation signal, the vehicle occupancy order is updated to obtain the recommended vehicle occupancy order, the vehicle occupancy request is regenerated, and steps 5 to 61 are executed. This achieves the effect of providing similar vehicles as candidates for the user based on the vehicle currently selected by the user, and provides user experience assurance after the failure of conflict coordination.

[0016] Optionally, it also includes a handling method if the recommended time slot does not exist, the method including: Step 60430: Filter out maintenance occupancy records with the preset maintenance type from the candidate occupancy records; Step 60431: Extract the maintenance occupancy period based on the maintenance occupancy record; Step 60432: Calculate the advance maintenance period based on the maintenance occupancy period and the expected occupancy period; Step 60433: Push the advance maintenance period and the preset advance maintenance signal to the preset maintenance management terminal; Step 60434: After receiving the maintenance completion signal from the maintenance management terminal, find the corresponding vehicle number for maintenance according to the maintenance occupancy record and push the vehicle number for maintenance to the user terminal; Step 60435: Upon receiving the repair confirmation signal from the user terminal, update the vehicle occupancy order based on the vehicle repair number to obtain the final vehicle occupancy order; Step 60436: Regenerate the vehicle occupancy request based on the final vehicle occupancy order and execute steps 5 to 61.

[0017] By adopting the above technical solution, maintenance occupancy records of different maintenance types are filtered from candidate occupancy records, maintenance occupancy time periods are extracted, and advance maintenance time periods are calculated by combining the expected occupancy time periods. The advance maintenance time periods and advance maintenance signals are pushed to the maintenance management terminal. Upon receiving the maintenance completion signal, the vehicle number is extracted and pushed to the user terminal. Upon receiving the maintenance confirmation signal, the vehicle occupancy order is updated to obtain the final vehicle occupancy order. The vehicle occupancy request is regenerated and steps 5 to 61 are executed, thus solving the problem of similar vehicles needing maintenance but being unable to be used by users.

[0018] Optionally, it also includes a monitoring method after pushing the advance maintenance period and the preset advance maintenance signal to the preset maintenance management terminal, the method including: Step 604330: Obtain the real-time maintenance progress of the maintenance occupancy record; Step 604331: Adjust the advance maintenance time period in real time according to the real-time maintenance progress to obtain the actual maintenance time period; Step 604332: Push the actual maintenance period and the preset adjustable occupancy signal to the user terminal; Step 604333: Receive the adjusted adjustable time period from the user terminal; Step 604334: Update the expected occupancy period in the vehicle occupancy request based on the adjustable occupancy period.

[0019] By adopting the above technical solution, the real-time maintenance progress of the maintenance occupancy record is obtained, and the advance maintenance time period is adjusted according to the real-time maintenance progress to obtain the actual maintenance time period. The actual maintenance time period and the adjustable occupancy signal are pushed to the user terminal. The adjustable occupancy time period fed back by the user terminal is received, and the expected occupancy time period in the vehicle occupancy request is updated according to the adjustable occupancy time period. The actual maintenance time period is displayed to the user in real time, realizing the effect that the user can adjust their occupancy time period according to the actual maintenance time period.

[0020] Optionally, it also includes a monitoring method after locking the vehicle number, the method comprising: Step 50: Detect new occupancy requests for the same vehicle number based on vehicle number monitoring; Step 51: Push a preset first prompt signal to the user terminal corresponding to the new occupancy request; Step 52: When unlocking the vehicle number, the expected occupancy period corresponding to the occupancy record written in the unified vehicle scheduling table is defined as the locked occupancy period; Step 53: If the expected occupancy period and the locked occupancy period do not overlap, then execute steps 4 to 61 based on the new occupancy request; Step 54: If the expected occupancy period overlaps with the locked occupancy period, the occupancy records written into the unified vehicle scheduling table are monitored to obtain the monitoring status. Step 55: If the monitored state is the preset existence state, no operation is performed; Step 56: If the monitoring status is the preset release status, then push the preset second prompt signal to the user terminal corresponding to the new occupancy request.

[0021] By adopting the above technical solution, new occupancy requests for the same vehicle number are monitored, and a first prompt signal is pushed to the corresponding user terminal. When the vehicle number is unlocked, the expected occupancy period corresponding to the occupancy record is used as the locked occupancy period. If there is no overlap, steps 4 to 61 are executed according to the new occupancy request. If there is overlap, the occupancy record is monitored to obtain the monitoring status. If there is no processing, the release status is pushed to the corresponding user terminal, thus solving the problem that users cannot know in time and place orders after placing an order for a vehicle that is occupied within their expected time period but is later canceled.

[0022] Optionally, it also includes a method for alerting users to new occupancy requests for the same vehicle number detected by vehicle number monitoring, the method including: Step 500: Count the number of new requests that newly occupy space; Step 501: When a vehicle occupancy request is written as an occupancy record into the unified vehicle scheduling table, a real-time reminder signal is generated based on the number of new requests and the preset reminder signal. Step 502: Push a real-time reminder signal to the user terminal corresponding to the vehicle occupancy request.

[0023] By adopting the above technical solution, the number of new vehicle occupancy requests is counted. When a vehicle occupancy request is written into the unified vehicle scheduling table, a real-time reminder signal is generated based on the number of new requests and the reminder signal. The real-time reminder signal is pushed to the user terminal corresponding to the vehicle occupancy request, thereby informing the user of the current vehicle availability and reminding the user to proceed with the subsequent process as soon as possible.

[0024] Secondly, this invention provides a lifecycle collaborative management system based on multi-channel heterogeneous orders, employing the following technical solution: A lifecycle collaborative management system based on multi-channel heterogeneous orders includes: The acquisition module is used to acquire channel orders, vehicle usage query requests, actual vehicle usage records, and real-time maintenance progress. The memory is used to store the program of the lifecycle collaborative management method based on multi-channel heterogeneous orders as described above; The processor loads and executes programs from memory.

[0025] In summary, the present invention has at least one of the following beneficial technical effects: It solves the problem of the same vehicle being allocated to multiple channels at the same time, realizes the global unified management of multi-channel orders, achieves the global unified scheduling of vehicle resources, and fundamentally eliminates the concurrent conflicts in vehicle resource allocation. By coordinating with users who have already occupied the vehicle to terminate their usage period early, the system enables subsequent users to use the vehicles they ordered. A refund mechanism is provided to compensate users who have already occupied the vehicle, thereby improving the utilization efficiency of vehicle resources. It achieves the effect of providing similar vehicles as candidates based on the user's current vehicle selection, and provides user experience assurance after the failure of conflict coordination. Attached Figure Description

[0026] Figure 1 This is a flowchart of a lifecycle collaborative management method based on multi-channel heterogeneous orders in an embodiment of this application; Figure 2 This is a flowchart of a processing method in this application embodiment for when the expected occupation period overlaps with the vehicle occupation period; Figure 3 This is a flowchart of a method for handling a user terminal's rejection signal if it is received in an embodiment of this application. Figure 4 This is a timing diagram of the dynamic adjustment of maintenance progress in the embodiments of this application. Detailed Implementation

[0027] The present invention will now be described in further detail with reference to the accompanying drawings and embodiments.

[0028] This invention discloses a lifecycle collaborative management method based on heterogeneous orders from multiple channels. (Refer to...) Figure 1 A lifecycle collaborative management method based on multi-channel heterogeneous orders includes: Step 1: Obtain channel orders from multiple channels and store them in a pre-defined unified order table.

[0029] Channel orders refer to user car rental demand information received by vehicle rental operators through various online business channels. The order data submitted by users and received through the business interfaces of each channel constitutes a channel order. A channel order includes user identity information, order status, vehicle number, subscription type, and desired start and end dates. Channel orders originate from WeChat mini-programs, Alipay mini-programs, and third-party credit service platforms. Different source channels correspond to different order placement processes and business rules. Orders placed through WeChat mini-programs or Alipay mini-programs are considered in-app channels. Users must complete pre-order operations such as deposit payment, real-name authentication, and security deposit payment before an order can be generated. Orders placed through third-party credit service platforms are considered out-of-app channels. Users generate orders by applying for a deposit-free contract and reusing their Alipay real-name information, without paying any fees when generating the order. The order status flow logic differs across channels. In-app channel orders have the following statuses in sequence: pending deposit payment, pending order acceptance, and pending order locking. The order statuses from external channels are, in order: pending deposit waiver, pending review, pending appointment, pending order acceptance, and pending order locking.

[0030] A unified order table is a data table that centrally stores order data from all source channels. Deployed in a server-side database, it is implemented using a relational database, and its table structure corresponds to the order data fields received by the business interfaces of each channel. The unified order table is pre-configured by those skilled in the art. Fields in the unified order table include order number, order source, user identifier, vehicle number, order status, subscription type, expected start and end times of ride usage, creation time, and update time. The order source field distinguishes between internal and external channels. After receiving order data at the business interfaces of each channel, the order data is converted into the data structure corresponding to the unified order table and inserted into it; this is the storage method. After storage, the order data enters a centralized management state, allowing for the centralized management of order data from multiple channels.

[0031] Step 2: Extract channel orders from the unified order table. Channel orders include order status.

[0032] Data is read from the unified order table using query statements, retrieving results in chronological order of order creation time. The system triggers real-time retrieval of channel orders when a new order is added or its status changes. A scheduled task is also configured to perform the retrieval operation periodically at preset time intervals, which are set by those skilled in the art based on the order volume for each time slot of the day. Batch processing is also supported, allowing multiple channel orders to be retrieved at once according to the set batch size. Retrieved orders are marked after retrieval to prevent multiple processing nodes from repeatedly retrieving the same order.

[0033] Order status refers to the stage of a channel order in the current business process. It is updated by the system according to the business rules of the order under different channels. User actions and system responses jointly drive changes in order status.

[0034] The order status within the app is sequentially categorized as: pending deposit payment, pending order acceptance, and pending order locking. Pending deposit payment indicates the user has initiated an order but has not yet completed deposit payment; pending order acceptance indicates the user has completed deposit payment and is awaiting sales confirmation; and pending order locking indicates the salesperson has confirmed the order information and triggered vehicle locking.

[0035] The order statuses from external channels are sequentially: Pending Deposit Waiver, Pending Review, Pending Reservation, Pending Order Acceptance, and Pending Order Locking. "Pending Deposit Waiver" indicates the user has placed an order but hasn't completed the deposit waiver agreement; "Pending Review" indicates the user has completed the deposit waiver agreement and is awaiting review; "Pending Reservation" indicates the review has been approved and the user is waiting to confirm the ride time; "Pending Order Acceptance" indicates the user has completed reservation confirmation and is waiting for sales staff to confirm the order; and "Pending Order Locking" indicates the sales staff has confirmed the order information and triggered vehicle locking.

[0036] Step 3: Extract channel orders with the preset pending order status as orders that need to be locked into the vehicle.

[0037] The "pending lock order" status refers to a channel order that has completed its preliminary processes but has not yet had its vehicle locking operation performed. This status is preset by those skilled in the art. The "pending lock order" status is entered jointly by orders from both internal and external channels after completing their respective preliminary processes. Orders from internal channels enter the "pending lock order" status after the salesperson confirms the order. Orders from external channels enter the "pending lock order" status after the salesperson confirms the order.

[0038] Orders requiring vehicle occupancy refer to channel orders whose status is pending lockout, which are extracted from the unified order table.

[0039] Step 4: Generate a vehicle occupancy request based on the vehicle occupancy order. The vehicle occupancy request includes the vehicle number and the expected occupancy period.

[0040] A vehicle occupancy request is a data object that requests vehicle occupancy from a unified vehicle scheduling table, including the vehicle number and the expected occupancy period. The vehicle occupancy request is generated based on the vehicle number stored in the vehicle occupancy order and the expected start and end times of the vehicle usage, where the expected start and end times constitute the expected occupancy period.

[0041] The vehicle number refers to the unique identification number of the target vehicle ordered by the user. Each operating vehicle corresponds to a unique vehicle number, which can be the vehicle identification number (VIN).

[0042] The expected occupancy period refers to the time range within which the vehicle is expected to be used, as recorded in the vehicle occupancy order, including the start and end times. The expected occupancy period can be extracted from the user-confirmed expected start and end times of the vehicle occupancy order; or it can be calculated based on the vehicle allocation completion time and the preset subscription duration in the vehicle occupancy order. The subscription duration is preset by those skilled in the art according to the subscription specifications.

[0043] Step 5: Lock the vehicle number and search for the existing occupied record corresponding to the vehicle number in the preset unified vehicle scheduling table.

[0044] Locking refers to the exclusive locking operation applied to a vehicle number, preventing multiple vehicle occupancy requests from simultaneously attempting to lock the same vehicle number. Once a lock is applied to a vehicle number, other vehicle occupancy requests cannot apply the lock to the same vehicle number again until the lock is released. Locking operations are implemented using distributed locks. Distributed locks are deployed in a distributed system environment and shared among multiple service instances, ensuring that only one service instance can successfully apply the lock to the same vehicle number at any given time. Locking operations are performed on a per-vehicle-number basis, with different vehicle numbers using independent locks. As a preferred implementation, distributed locks employ a pessimistic locking strategy.

[0045] A unified vehicle scheduling table is a data table that stores all vehicle occupancy records. Fields in the unified vehicle scheduling table include vehicle number, start time of the occupancy period, end time of the occupancy period, occupancy record type, and the order number corresponding to the occupancy record. The unified vehicle scheduling table is pre-set by those skilled in the art, and the occupancy records are organized according to vehicle number. Multiple occupancy records can exist for the same vehicle number in the unified vehicle scheduling table, and the occupancy periods of each record do not overlap.

[0046] Existing occupancy records refer to occupancy records that are currently written into the unified vehicle scheduling table and whose occupancy period ends later than the current time. The unified vehicle scheduling table is searched for all existing occupancy records corresponding to that vehicle number. Among all existing occupancy records, records whose occupancy period ends earlier than or equal to the current time are not included in the search results; the remaining occupancy records are the existing occupancy records.

[0047] Step 6: Extract the vehicle occupancy period from the existing occupancy records.

[0048] Vehicle occupancy time slots refer to the time slot sequence extracted from existing occupancy records. Each existing occupancy record includes the vehicle number, start time of the occupancy time slot, end time of the occupancy time slot, occupancy record type, and the order number corresponding to the occupancy record. Based on the vehicle number, all existing occupancy records corresponding to that vehicle number are searched in the unified vehicle scheduling table. The start time and end time of the occupancy time slot are extracted from each existing occupancy record and arranged in chronological order to form the vehicle occupancy time slot corresponding to that vehicle number. If there are multiple existing occupancy records for the same vehicle number in the unified vehicle scheduling table, the vehicle occupancy time slot contains multiple time slots, and these time slots do not overlap. If two time slots are adjacent but do not overlap, they are retained as two independent time slots in the sequence and are not merged.

[0049] Step 60: If the expected occupancy period overlaps with the vehicle occupancy period, unlock the vehicle number and output a preset vehicle occupancy signal.

[0050] Unlocking refers to the operation of removing the exclusive lock applied to a vehicle number. After unlocking, other vehicles can re-lock that vehicle number if they request to use it.

[0051] A vehicle occupancy signal is a notification signal that a user's ordered vehicle has been occupied by another order during the expected occupancy period. This signal is preset by someone skilled in the art.

[0052] If the expected occupancy period overlaps with the vehicle occupancy period, it means that there is a temporal overlap between any two periods. In this case, the vehicle number is unlocked and the vehicle occupancy signal is pushed to the user terminal corresponding to the current vehicle occupancy order, informing the user that the ordered vehicle has been occupied by other orders within the expected occupancy period.

[0053] The method for determining whether the expected occupancy period overlaps with the vehicle occupancy period is as follows: the start and end times of the expected occupancy period are compared one by one with the start and end times of each period in the vehicle occupancy period sequence. If the start time of the expected occupancy period is not later than the end time of a certain period in the vehicle occupancy period sequence, and the end time of the expected occupancy period is not earlier than the start time of that period, then the expected occupancy period is determined to overlap with that period.

[0054] Step 61: If the expected occupancy period does not overlap with the vehicle occupancy period, the vehicle occupancy request is written as an occupancy record into the unified vehicle scheduling table, and the vehicle number is unlocked.

[0055] An occupancy record is a data record written to the unified vehicle schedule table when the expected occupancy period and the vehicle occupancy period do not overlap. It must include at least the vehicle number, the start time of the occupancy period, and the end time of the occupancy period. A vehicle occupancy request is a temporary data object generated based on a vehicle occupancy order and used to apply for vehicle occupancy from the unified vehicle schedule table. An occupancy record is persistent data written to the unified vehicle schedule table after the vehicle occupancy request has been compared for overlap.

[0056] If the expected occupancy period does not overlap with the vehicle occupancy period, it means that there is no temporal overlap between the expected occupancy period and all extracted vehicle occupancy periods. The vehicle ordered by the user is in an idle state during the expected occupancy period. Therefore, the vehicle occupancy request is written as an occupancy record into the unified vehicle scheduling table, and the unlocking operation is performed on the vehicle number.

[0057] This includes a method for generating the expected time period before acquiring channel orders from multiple channels. This method includes: Step 10: Obtain the vehicle query request initiated by the user terminal and extract the target vehicle number from the vehicle query request.

[0058] A vehicle availability query request is a data request from a user to check the current availability of a vehicle they have ordered. After selecting the desired vehicle on their device, the user generates a vehicle availability query request and sends it to the server.

[0059] The target vehicle number refers to the unique identification number of the vehicle ordered by the user, which is obtained by parsing the vehicle query request.

[0060] Step 11: Based on the target vehicle number, search for the existing occupied record corresponding to the target vehicle number in the preset unified vehicle scheduling table.

[0061] Refer to the corresponding description in step 5 for the definition and search method of existing occupancy records.

[0062] Step 12: Based on the existing occupancy records, reverse-engineer the unoccupied time period corresponding to the target vehicle number as the recommended time period.

[0063] An unoccupied time period refers to the continuous free time range of the vehicle corresponding to the target vehicle number that is not currently occupied by any existing occupancy record, including the start and end times. All vehicle occupancy time periods are extracted from the existing occupancy records, arranged on a timeline, and then reversed to obtain the unoccupied time period, which is the continuous time range not covered by any vehicle occupancy time period. This unoccupied time period is then directly pushed to the user's terminal as a recommended time period.

[0064] Step 13: Push the recommended time period and preset time period selection signals to the user terminal.

[0065] The time slot selection signal is a signal that prompts the user to select a time slot for vehicle use. This signal also includes a prompt indicating the maximum number of days the user can select; this signal is preset by someone skilled in the art. After the time slot selection signal is pushed to the user's terminal, a time slot selection interface will be displayed, showing recommended time slots from which the user can choose their desired time slot.

[0066] A user terminal refers to an electronic device used by a user. A user terminal can interact with a server via a network, receiving signals and data pushed by the server and displaying the corresponding interactive interface on its screen.

[0067] Step 14: Receive the desired time period from the user terminal and output the desired time period as the expected occupancy time period.

[0068] The desired time period refers to the time range selected by the user from the recommended time periods, which is obtained by the user on the user terminal according to the recommended time periods.

[0069] The user's expected time period is used as the expected occupancy time period and included in the vehicle occupancy request of the vehicle occupancy order.

[0070] Reference Figure 2 It also includes a method for handling situations where the expected occupancy period overlaps with the vehicle occupancy period, the method comprising: Step 600: Define vehicle occupancy periods that overlap with the expected occupancy periods as overlapping occupancy periods.

[0071] Overlapping occupancy periods refer to vehicle occupancy periods that overlap with the expected occupancy periods in time.

[0072] Step 601: Obtain the conflict period by taking the intersection of the overlapping period and the expected period.

[0073] A conflicting period refers to a time range that overlaps with and is expected to be occupied. The start and end times of the overlapping period are compared with those of the expected period, and the intersection of these two times is taken as the conflicting period. The start time of the conflicting period is the later of the start times of the overlapping and expected periods, and the end time is the earlier of the end times of the overlapping and expected periods.

[0074] Step 602: Query the occupied users based on the existing occupied records corresponding to the overlapping occupied time periods.

[0075] "Already occupied users" refers to users whose existing occupancy records correspond to the overlapping occupancy periods. The correspondence between existing occupancy records and user identifiers is established when the existing occupancy records are written into the unified vehicle scheduling table. Therefore, querying the existing occupancy records for the overlapping occupancy periods will find the corresponding users.

[0076] Step 603: Push the conflict period and the preset early termination signal to the user terminal corresponding to the occupied user.

[0077] The early termination signal is a signal that asks the user who has already booked the vehicle whether they agree to terminate the service before the start of the conflict period. This signal is preset by someone skilled in the art. After receiving the conflict period and the early termination signal, the user's terminal displays a prompt interface asking whether the user agrees to terminate the service before the start of the conflict period. The user selects to agree or disagree through this interface, and the user's terminal feeds back the user's selection to the system.

[0078] Step 604: If a termination rejection signal is received from the user terminal, unlock the vehicle number and output a preset vehicle occupancy signal.

[0079] The termination rejection signal is a feedback signal that the user who has already used the service refuses to end the service before the start of the conflict period. It is generated after the user selects to refuse in the inquiry interface.

[0080] If a termination rejection signal is received from the user terminal, it means that the vehicle has been occupied and the user does not agree to terminate the vehicle use early. In this case, the vehicle cannot be released through coordination. Therefore, the vehicle number is unlocked and a vehicle occupancy signal is output.

[0081] Step 605: If an end confirmation signal is received from the user terminal, the refund amount is calculated based on the conflict period and the preset time refund coefficient, and the refund amount is returned to the user terminal corresponding to the occupied user.

[0082] The termination confirmation signal is a feedback signal indicating that the user has agreed to terminate the vehicle use before the start of the conflict period. It is generated after the user selects "agree" on the inquiry interface.

[0083] The time-based refund factor is a calculation parameter used to calculate the refund amount, which is preset by those skilled in the art according to business rules. The time-based refund factor represents the refund amount or percentage corresponding to a conflicting time period.

[0084] The refund amount refers to the amount that should be refunded to the users who have already used the account, calculated based on the conflict period. The refund amount is calculated by multiplying the length of the conflict period by a time-based refund coefficient.

[0085] If a confirmation signal for termination is received from the user's terminal, it means that the user who has already used the service agrees to end the service before the start of the conflict period. Therefore, the refund amount is calculated by multiplying the conflict period and the time refund coefficient, and the refund amount is returned to the user's terminal.

[0086] Step 606: Remove conflicting periods from the overlapping occupied periods to obtain the actual occupied periods.

[0087] The actual occupied period refers to the remaining time range after removing conflicting periods from the overlapping occupied periods, including the start and end times. The portions corresponding to conflicting periods in the overlapping occupied periods are deleted, and the remaining portion is retained as the actual occupied period.

[0088] Step 607: Update the existing occupancy record according to the actual occupancy period, write the vehicle occupancy request as an occupancy record into the unified vehicle scheduling table, and unlock the vehicle number.

[0089] The overlapping occupancy periods in the existing occupancy records are changed to the actual occupancy periods. The vehicle occupancy request is written as an occupancy record into the unified vehicle scheduling table, so that users can obtain the right to use the vehicle when ordering it during the expected occupancy period, and the vehicle number is unlocked.

[0090] The methods for pushing conflict periods and preset early termination signals to the user terminals of users who have already occupied the space include: Step 6030: Obtain the actual vehicle usage records of the users whose vehicles are occupied, corresponding to the vehicle number.

[0091] Actual vehicle usage records refer to usage behavior data generated during the period a vehicle is occupied, specifically the actual driving time data, which is collected in real time by vehicle terminal equipment installed on the vehicle.

[0092] Step 6031: Extract the actual usage time and current occupancy time from the actual vehicle usage records.

[0093] Actual vehicle usage time refers to the sum of the actual driving time extracted from actual vehicle usage records. All driving time data is extracted from the actual vehicle usage records, and the durations of each driving trip are added together to obtain the actual vehicle usage time.

[0094] The current occupancy duration refers to the total duration from the start time of occupancy to the current time. The start time of occupancy is the beginning time of the occupancy period recorded in the existing occupancy log. The current time is the current system time. The current occupancy duration is obtained by calculating the time difference between the current time and the start time of occupancy.

[0095] Step 6032: Calculate the actual usage percentage based on the actual usage time and the current occupancy time.

[0096] Actual usage percentage refers to the ratio of actual usage time to current occupancy time. The actual usage percentage is obtained by dividing the actual usage time by the current occupancy time.

[0097] Step 6033: If the actual usage ratio is higher than the preset high-frequency ratio, unlock the vehicle number and output the preset vehicle occupancy signal.

[0098] High-frequency usage ratio refers to the threshold for determining whether a user who has already booked a ride belongs to a high-frequency user group. This threshold is pre-set by someone skilled in the art based on business operation data. Business operation data includes the actual usage ratio distribution data of all users who have already booked rides, the average usage intensity of different vehicle models, and typical usage patterns for different subscription types. Someone skilled in the art can periodically analyze the actual usage ratio distribution of users who have already booked rides and adjust the high-frequency usage ratio based on the distribution data.

[0099] If the actual usage rate is higher than the preset high-frequency usage rate, it means that the user who has occupied the vehicle is using it intensively during the current period and is highly dependent on the vehicle. Therefore, the user is unlikely to agree to end the usage early. So, instead of pushing an early termination signal to the user who has occupied the vehicle, the system will directly unlock the vehicle number and output a vehicle occupancy signal to avoid causing unnecessary disturbance to high-frequency users.

[0100] Step 6034: If the actual usage ratio is not higher than the preset high-frequency ratio, then push the conflict period and the preset early termination signal to the user terminal corresponding to the occupied user.

[0101] If the actual usage rate is not higher than the preset high-frequency usage rate, it means that the user who has already occupied the vehicle has a low usage intensity during the current period and the user's dependence on the vehicle is low. Therefore, the user is more likely to agree to end the vehicle use early. Thus, the conflict period and the early termination signal are pushed to the user terminal corresponding to the user who has already occupied the vehicle, and the user is asked whether they are willing to end the vehicle use early during the conflict period.

[0102] Reference Figure 3 It also includes a method for handling a termination rejection signal received from a user terminal, the method comprising: Step 6040: Search for the corresponding vehicle model characteristics in the preset vehicle database based on the vehicle number.

[0103] The vehicle database stores a mapping relationship between vehicle serial numbers and corresponding vehicle model characteristics. The vehicle database is created by those skilled in the art who collect attribute information of the vehicles listed in advance, organize it into vehicle model characteristics, establish a one-to-one correspondence between these characteristics and the vehicle serial numbers, and store this correspondence. Vehicle model characteristics may include attributes such as brand, number of seats, driving range, and vehicle type.

[0104] Vehicle model characteristics refer to the attribute information describing the vehicle corresponding to the vehicle number, which can be found in the vehicle database based on the vehicle number.

[0105] Step 6041: Search the vehicle database for candidate vehicle numbers that meet the vehicle model characteristics.

[0106] Candidate vehicle numbers are unique vehicle identifiers that meet the vehicle model characteristics corresponding to the vehicle number. Using the vehicle model characteristics as a query condition, a search operation is performed in the vehicle database to filter out all vehicle numbers in the database that meet that vehicle model characteristic; these are the candidate vehicle numbers.

[0107] Step 6042: Find the corresponding candidate occupancy record in the unified vehicle schedule table based on the candidate vehicle number, and extract the candidate occupancy time period from the candidate occupancy record.

[0108] Candidate occupancy records refer to existing occupancy records corresponding to candidate vehicle numbers in the unified vehicle scheduling table. Using the candidate vehicle number as a query condition, a search operation is performed in the unified vehicle scheduling table to retrieve all existing occupancy records corresponding to that candidate vehicle number.

[0109] Candidate occupancy periods refer to the time range extracted from candidate occupancy records. The start and end times of the occupancy period are extracted from each candidate occupancy record and arranged in chronological order to form the candidate occupancy periods corresponding to that candidate vehicle number.

[0110] Step 6043: Compare the candidate occupancy periods with the expected occupancy periods, filter out the candidate occupancy periods that do not overlap with the expected occupancy periods, and define them as recommended occupancy periods.

[0111] The recommended occupancy period refers to a candidate occupancy period that does not overlap with the expected occupancy period. The method for determining overlap between the candidate occupancy period and the expected occupancy period in this step is the same as the method used in step 60 for determining overlap between the expected occupancy period and the vehicle occupancy period. If the start time of the candidate occupancy period is not later than the end time of the expected occupancy period, and the end time of the candidate occupancy period is not earlier than the start time of the expected occupancy period, then the candidate occupancy period and the expected occupancy period are determined to overlap; otherwise, they are determined not to overlap.

[0112] Step 6044: Define the candidate vehicle number corresponding to the recommended time period as the recommended vehicle number and push it to the user terminal.

[0113] The candidate vehicle IDs corresponding to the recommended occupancy time slots that do not overlap with the expected occupancy time slots will be pushed to the user's terminal as recommended vehicle IDs for the user to select. After receiving the recommended vehicle ID, the user's terminal will display the recommended vehicle information to the user, who can then choose to accept or reject the recommended vehicle.

[0114] Step 6045: Upon receiving the recommendation confirmation signal from the user terminal, update the vehicle reservation order based on the recommended vehicle number to obtain the recommended vehicle reservation order.

[0115] The recommendation confirmation signal is a feedback signal indicating that the user accepts the recommended vehicle. This signal includes the user's acceptance information and the recommended vehicle number selected by the user. The user terminal generates a recommendation confirmation signal based on the user's acceptance information and the selected recommended vehicle number and sends it back to the system.

[0116] A recommended vehicle reservation order is a new order obtained by updating the vehicle reservation order based on the recommended vehicle number. Simply replace the vehicle number in the vehicle reservation order with the recommended vehicle number, leaving other data unchanged; the resulting order is the recommended vehicle reservation order.

[0117] If a confirmation signal is received from the user's terminal, it means the user agrees to change the vehicle in the order to the recommended vehicle; therefore, the vehicle number in the vehicle reservation order is replaced with the recommended vehicle number to obtain the recommended vehicle reservation order. If no confirmation signal is received from the user's terminal, it means the user does not agree to change the vehicle, and no further action is taken.

[0118] Step 6046: Regenerate a vehicle occupancy request based on the recommended vehicle occupancy order and execute steps 5 to 61.

[0119] Based on the recommended vehicle occupancy order, a new vehicle occupancy request is generated, and steps 5 to 61 are executed. This involves re-executing the complete vehicle occupancy process for the recommended vehicle number, including locking, querying the schedule table, determining overlap, and writing to the schedule table.

[0120] This also includes a handling method for when the recommended time slot does not exist, the method including: Step 60430: Filter out maintenance occupancy records with the preset maintenance type from the candidate occupancy records.

[0121] Occupancy type is an attribute field of occupancy records in the unified vehicle scheduling table. Each occupancy record in the unified vehicle scheduling table carries an occupancy type field. When a vehicle occupancy request is written as an occupancy record into the unified vehicle scheduling table, the value of the occupancy type is set according to the source business type of the request. The occupancy type is preset by those skilled in the art based on the business type and includes at least repair type, maintenance type, transportation type, and user order type.

[0122] Repair type refers to the occupancy type generated by vehicle repair services. When a vehicle needs repair due to a malfunction, the back-end administrator creates a repair work order in the system. The system determines the occupancy type as the repair type based on the vehicle repair service corresponding to the repair work order, generates a vehicle occupancy request based on the repair work order, and writes the repair type and the request together into the unified vehicle scheduling table.

[0123] A maintenance occupancy record refers to an occupancy record among the candidate occupancy records whose occupancy type is maintenance. The occupancy type field of each record is read from the candidate occupancy records; when the occupancy type field value is maintenance, the candidate occupancy record is defined as a maintenance occupancy record.

[0124] Step 60431: Extract the maintenance occupancy period based on the maintenance occupancy record.

[0125] The maintenance occupancy period refers to the time range extracted from the maintenance occupancy records. The start and end times of the occupancy period are extracted from each maintenance occupancy record to form the corresponding maintenance occupancy period.

[0126] Step 60432: Calculate the advance maintenance period based on the maintenance occupancy period and the expected occupancy period.

[0127] The advance maintenance period refers to the target time range within which maintenance personnel are informed to expedite the maintenance process. The target completion time is obtained by subtracting a preset buffer time from the start time of the expected maintenance period. The start time of the advance maintenance period is the same as the start time of the expected maintenance period, and the end time is the target completion time. The preset buffer time is pre-set by those skilled in the art based on the time required for vehicle preparation, cleaning, and safety checks.

[0128] For example, if the maintenance period is from August 1st to August 15th, the expected maintenance period is from August 10th to August 20th, and the preset buffer time is 12 hours, then subtracting 12 hours from the start time of the expected maintenance period at 0:00 on August 10th will give us August 9th at 12:00 as the target time to complete the maintenance. Therefore, the maintenance period is from August 1st to August 9th at 12:00.

[0129] Step 60433: Push the advance maintenance period and the preset advance maintenance signal to the preset maintenance management terminal.

[0130] A maintenance advance signal is a signal that prompts maintenance personnel to complete vehicle maintenance work ahead of schedule; it is preset by those skilled in the art. The maintenance advance signal also includes the vehicle number and the maintenance work order number.

[0131] A maintenance management terminal refers to an electronic device used by maintenance personnel and pre-configured by those skilled in the art.

[0132] By sending the advance maintenance time slot and advance maintenance signal to the maintenance management terminal, maintenance personnel can be informed to complete vehicle maintenance work ahead of schedule during the advance maintenance time slot.

[0133] Step 60434: After receiving the maintenance completion signal from the maintenance management terminal, find the corresponding vehicle number for maintenance based on the maintenance occupancy record and push the vehicle number to the user terminal.

[0134] A maintenance completion signal is a signal from the maintenance management terminal indicating that maintenance is complete. This signal is generated after maintenance personnel confirm the completion of maintenance on the maintenance management terminal and then send it back to the system.

[0135] The vehicle number for maintenance refers to the unique identification number of the vehicle corresponding to the maintenance occupancy record. The vehicle number is obtained by extracting the vehicle number field from the maintenance occupancy record.

[0136] After receiving the repair completion signal from the maintenance management terminal, it means that the maintenance personnel have completed the vehicle repair work and the vehicle can be rented to the user. Therefore, the repair vehicle number is found and pushed to the user terminal to inform the user that there is a vehicle that meets their needs.

[0137] Step 60435: Upon receiving the repair confirmation signal from the user terminal, update the vehicle occupancy order based on the vehicle repair number to obtain the final vehicle occupancy order.

[0138] A repair confirmation signal is a feedback signal indicating that the user accepts the pushed repair vehicle number. The user terminal generates a repair confirmation signal based on the user's acceptance information and the accepted repair vehicle number, and sends it back to the system.

[0139] The final vehicle occupancy order refers to the new order obtained after updating the vehicle occupancy order based on the vehicle number for repair. Simply replace the vehicle number in the vehicle occupancy order with the vehicle number for repair, leaving other data unchanged; the resulting order is the final vehicle occupancy order.

[0140] Upon receiving a repair confirmation signal from the user's terminal, it indicates that the user agrees to replace the vehicle in the order with a vehicle that will be released after repair. Therefore, the vehicle number in the vehicle occupancy order needs to be replaced with the repair vehicle number to obtain the final vehicle occupancy order. If no repair confirmation signal is received from the user's terminal, it means that the user does not agree to replace the vehicle, and no further action will be taken.

[0141] Step 60436: Regenerate the vehicle occupancy request based on the final vehicle occupancy order and execute steps 5 to 61.

[0142] Based on the final vehicle occupancy order, a new vehicle occupancy request is generated, and steps 5 to 61 are executed again, which is to re-execute the complete vehicle occupancy process of locking the recommended vehicle number, querying the schedule table, determining overlap, and writing to the schedule table.

[0143] This includes a monitoring method for pushing the advance maintenance period and the preset advance maintenance signal to a preset maintenance management terminal. This method includes: Step 604330: Obtain the real-time maintenance progress of the maintenance occupancy record.

[0144] Real-time maintenance progress refers to the percentage of maintenance work completed, ranging from 0% to 100%. Real-time maintenance progress is obtained by maintenance personnel entering the current percentage of maintenance work completion into the maintenance management terminal during the maintenance process.

[0145] Step 604331: Adjust the advance maintenance time period in real time according to the real-time maintenance progress to obtain the actual maintenance time period.

[0146] The actual maintenance period refers to the time range obtained by adjusting the advance maintenance period based on the real-time maintenance progress. After obtaining the current real-time maintenance progress, the remaining percentage of incomplete maintenance is calculated. This percentage is then multiplied by the total duration of the maintenance period to obtain the estimated time required for the remaining maintenance. Using the current time as a reference, the end time of the advance maintenance period is adjusted to the current time plus the estimated time required for the remaining maintenance, resulting in the end time of the actual maintenance period. The start time of the actual maintenance period is consistent with the start time of the advance maintenance period.

[0147] Step 604332: Push the actual maintenance period and the preset adjustable occupancy signal to the user terminal.

[0148] The adjustable occupancy signal is a signal that asks the user whether the expected occupancy period can be adjusted according to the actual maintenance period, and is preset by those skilled in the art. After the user terminal receives both the actual maintenance period and the adjustable occupancy signal, it displays an adjustment interface. The interface displays the actual maintenance period, and the user can input the adjusted desired usage time according to the actual maintenance period.

[0149] Reference Figure 4 The vertical axis represents the completion rate of maintenance work, ranging from 0% to 100%, and the horizontal axis represents time. Solid line A is the predicted maintenance progress curve, and dashed line B is the actual maintenance progress curve. T0 to T6 represent the advance maintenance period, and T0 to T7 represent the actual maintenance period.

[0150] Step 604333: Receive the adjusted adjustable time period from the user terminal.

[0151] Adjustable occupancy period refers to the time range that the user adjusts through the user terminal according to the actual maintenance period and then reports back to the system, including the start and end times.

[0152] Step 604334: Update the expected occupancy period in the vehicle occupancy request based on the adjustable occupancy period.

[0153] Replace the expected occupancy period in the vehicle occupancy request with an adjustable occupancy period.

[0154] This also includes a monitoring method after locking the vehicle's serial number, which includes: Step 50: Detect new occupancy requests for the same vehicle number based on vehicle number monitoring.

[0155] A new occupancy request refers to a new vehicle occupancy request detected while the vehicle number is already locked. Monitoring this vehicle number and defining a new occupancy request as one that attempts to lock the vehicle number from another vehicle is considered a new occupancy request.

[0156] Step 51: Push a preset first prompt signal to the user terminal corresponding to the new occupancy request.

[0157] The first notification signal is a signal indicating to the user that the vehicle they ordered is being used by another user and they need to wait. This signal is pre-set by someone skilled in the art. The first notification signal can be presented in the form of an information prompt, for example, displaying a message on the user terminal corresponding to the new occupancy request that the user is placing an order and should try again later.

[0158] Step 52: When unlocking the vehicle number, the expected occupancy period corresponding to the occupancy record written in the unified vehicle scheduling table is defined as the locked occupancy period.

[0159] When a vehicle number is unlocked, it means that the channel order placed by other users has completed the writing and unlocking operations in the vehicle occupancy process, and the vehicle occupancy request of other users has been successfully written into the unified vehicle scheduling table as an occupancy record, and the vehicle number has been unlocked; at this time, the expected occupancy period corresponding to the occupancy record written into the unified vehicle scheduling table is defined as the locked occupancy period.

[0160] Step 53: If the expected occupancy period and the locked occupancy period do not overlap, then execute steps 4 to 61 based on the new occupancy request.

[0161] If the expected occupancy period and the locked occupancy period do not overlap, it means that the expected vehicle usage time of the new occupancy request and the vehicle occupancy time of the locked vehicle do not overlap in time. At this time, steps 4 to 61 are directly re-executed based on the new occupancy request, that is, the complete vehicle occupancy process starts from generating the vehicle occupancy request, and goes through locking, querying the schedule table, judging overlap, and writing to the schedule table.

[0162] Step 54: If the expected occupancy period overlaps with the locked occupancy period, the occupancy records written into the unified vehicle scheduling table are monitored to obtain the monitoring status.

[0163] Monitoring status refers to the current status information of an occupancy record obtained when monitoring the occupancy record written into the unified vehicle schedule table. The monitoring status is obtained by querying the unified vehicle schedule table. The monitoring status includes an existence status and a release status, which are preset by those skilled in the art.

[0164] If the expected occupancy period overlaps with the locked occupancy period, it means that the expected usage time of the new occupancy request and the occupancy time of the already locked vehicle overlap in time. Therefore, the occupancy records written to the unified vehicle scheduling table are monitored, and corresponding user prompt information can be generated based on the monitoring status.

[0165] Step 55: If the monitored state is the preset existence state, no operation is performed.

[0166] The "existence" status refers to the state in which an occupancy record written to the unified vehicle schedule table is still stored in the table. When a query finds that an occupancy record written to the unified vehicle schedule table still exists in the table, the monitoring status is determined to be "existence".

[0167] If the monitoring status is the preset "existence" status, it means that the vehicle required by the user is still occupied, and no operation will be performed.

[0168] Step 56: If the monitoring status is the preset release status, then push the preset second prompt signal to the user terminal corresponding to the new occupancy request.

[0169] The "released" status refers to the state where the occupancy record written to the unified vehicle schedule table has been deleted or marked as invalid. When a query finds that an occupancy record written to the unified vehicle schedule table has been deleted from the unified vehicle schedule table or marked as invalid, the system will determine the status as "released".

[0170] The second prompt signal is a signal that prompts the user to place another order, which is preset by those skilled in the art.

[0171] If the monitoring status is the preset release status, it means that the vehicle ordered by the user is available and can be ordered again. Therefore, a second prompt signal is pushed to the user terminal corresponding to the new occupancy request.

[0172] It should be noted that monitoring the occupancy records written into the unified vehicle scheduling table is an ongoing process. If, during monitoring, the current time has exceeded the expected start time of the occupancy period minus the preset buffer time, a second prompt signal will still be pushed, allowing the user to decide whether they still wish to place an order. If the current time has exceeded the start time of the expected occupancy period, monitoring will stop, and the current process will end.

[0173] This also includes a method for notifying users of new occupancy requests based on vehicle ID monitoring. This method includes: Step 500: Count the number of new requests for newly added occupancy requests.

[0174] The number of new requests refers to the total number of new occupancy requests for the same vehicle number detected during the locking period. During the monitoring of vehicle numbers, whenever a new occupancy request is detected, the system increments the new request count for that vehicle number by one until monitoring stops.

[0175] Step 501: When a vehicle occupancy request is written as an occupancy record into the unified vehicle scheduling table, a real-time reminder signal is generated based on the number of new requests and the preset reminder signal.

[0176] A prompt signal is a notification signal that reminds the user to complete the subsequent confirmation process as soon as possible. It is preset by those skilled in the art according to business needs. The prompt signal is specifically represented by text information.

[0177] A real-time reminder signal is a personalized prompt signal generated by adjusting the reminder signal based on the number of new requests. The number of new requests is embedded as a variable into the reminder signal to form the real-time reminder signal. Specifically, the text message of the real-time reminder signal indicates that there are currently a certain number of users with new requests queuing to order the current vehicle; please complete the subsequent confirmation process as soon as possible.

[0178] When a vehicle occupancy request is written as an occupancy record into the unified vehicle scheduling table, it means that the user can proceed with the subsequent confirmation process. Therefore, a real-time reminder signal is generated based on the number of new requests.

[0179] Step 502: Push a real-time reminder signal to the user terminal corresponding to the vehicle occupancy request.

[0180] A real-time reminder signal will be pushed to the user's corresponding user terminal, prompting them to complete the subsequent confirmation process as soon as possible.

[0181] Based on the same inventive concept, embodiments of the present invention provide a lifecycle collaborative management system based on heterogeneous orders from multiple channels.

[0182] A lifecycle collaborative management system based on multi-channel heterogeneous orders includes: The acquisition module is used to acquire channel orders, vehicle usage query requests, actual vehicle usage records, and real-time maintenance progress. The memory stores a computer program that can be loaded and executed by the processor to provide a lifecycle collaborative management method based on multi-channel heterogeneous orders; The processor loads and executes programs from memory.

[0183] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the above-described division of functional modules is used as an example. In practical applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above. The specific working process of the system, device, and unit described above can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0184] The above description is merely a preferred embodiment of the present invention. The scope of protection of the present invention is not limited to the above embodiments. All technical solutions falling within the scope of the present invention's concept are within the scope of protection of the present invention. It should be noted that for those skilled in the art, any improvements and modifications made without departing from the principles of the present invention should also be considered within the scope of protection of the present invention.

Claims

1. A lifecycle collaborative management method based on multi-channel heterogeneous orders, characterized in that, include: Step 1: Obtain channel orders from multiple channels and store them in a pre-defined unified order table; Step 2: Extract channel orders from the unified order table, where each channel order includes its order status; Step 3: Extract channel orders with a preset pending order status as orders requiring vehicle occupancy; Step 4: Generate a vehicle occupancy request based on the vehicle occupancy order. The vehicle occupancy request includes the vehicle number and the expected occupancy period. Step 5: Lock the vehicle number and search for the existing occupied record corresponding to the vehicle number in the preset unified vehicle scheduling table. Step 6: Extract the vehicle occupancy period from the existing occupancy records; Step 60: If the expected occupancy period overlaps with the vehicle occupancy period, unlock the vehicle number and output a preset vehicle occupancy signal; Step 61: If the expected occupancy period does not overlap with the vehicle occupancy period, the vehicle occupancy request is written as an occupancy record into the unified vehicle scheduling table, and the vehicle number is unlocked.

2. The lifecycle collaborative management method based on multi-channel heterogeneous orders according to claim 1, characterized in that, Before acquiring channel orders from multiple channels, a method for generating the expected time period is also included, which includes: Step 10: Obtain the vehicle query request initiated by the user terminal, and extract the target vehicle number from the vehicle query request; Step 11: Based on the target vehicle number, search for the existing occupied record corresponding to the target vehicle number in the preset unified vehicle scheduling table; Step 12: Based on existing occupancy records, reverse-engineer the unoccupied time periods corresponding to the target vehicle number as recommended time periods; Step 13: Push the recommended time period and preset time period selection signals to the user terminal; Step 14: Receive the desired time period from the user terminal and output the desired time period as the expected occupancy time period.

3. The lifecycle collaborative management method based on multi-channel heterogeneous orders according to claim 2, characterized in that, It also includes a method for handling situations where the expected occupancy period overlaps with the vehicle occupancy period, the method comprising: Step 600: Define vehicle occupancy periods that overlap with the expected occupancy periods as overlapping occupancy periods; Step 601: Obtain the conflicting time period by taking the intersection of the overlapping and expected occupancy time periods; Step 602: Query the users who have occupied the space based on the existing occupancy records corresponding to the overlapping occupancy periods; Step 603: Push the conflict period and the preset early termination signal to the user terminal corresponding to the occupied user; Step 604: If a termination rejection signal is received from the user terminal, unlock the vehicle number and output a preset vehicle occupancy signal; Step 605: If an end confirmation signal is received from the user terminal, the refund amount is calculated based on the conflict period and the preset time refund coefficient, and the refund amount is returned to the user terminal corresponding to the occupied user. Step 606: Remove conflicting periods from the overlapping occupancy periods to obtain the actual occupancy periods; Step 607: Update the existing occupancy record according to the actual occupancy period, write the vehicle occupancy request as an occupancy record into the unified vehicle scheduling table, and unlock the vehicle number.

4. The lifecycle collaborative management method based on multi-channel heterogeneous orders according to claim 3, characterized in that, Methods for pushing conflict periods and preset early termination signals to the user terminals of users whose terminals are already occupied include: Step 6030: Obtain the actual vehicle usage records of the users whose vehicles are occupied, corresponding to the vehicle number; Step 6031: Extract the actual usage time and current occupancy time from the actual vehicle usage records; Step 6032: Calculate the actual usage percentage based on the actual usage time and the current occupancy time; Step 6033: If the actual vehicle usage ratio is higher than the preset high frequency ratio, unlock the vehicle number and output the preset vehicle occupancy signal. Step 6034: If the actual usage ratio is not higher than the preset high-frequency ratio, then push the conflict period and the preset early termination signal to the user terminal corresponding to the occupied user.

5. A lifecycle collaborative management method based on multi-channel heterogeneous orders according to claim 3, characterized in that, It also includes a method for handling a termination rejection signal received from a user terminal, the method comprising: Step 6040: Search for the corresponding vehicle model characteristics in the preset vehicle database based on the vehicle number; Step 6041: Search the vehicle database for candidate vehicle numbers that meet the vehicle model characteristics; Step 6042: Find the corresponding candidate occupancy record in the unified vehicle schedule table based on the candidate vehicle number, and extract the candidate occupancy time period from the candidate occupancy record; Step 6043: Compare the candidate occupancy periods with the expected occupancy periods, filter out the candidate occupancy periods that do not overlap with the expected occupancy periods, and define them as recommended occupancy periods; Step 6044: Define the candidate vehicle number corresponding to the recommended time period as the recommended vehicle number and push it to the user terminal; Step 6045: Upon receiving the recommendation confirmation signal from the user terminal, update the vehicle reservation order based on the recommended vehicle number to obtain the recommended vehicle reservation order; Step 6046: Regenerate a vehicle occupancy request based on the recommended vehicle occupancy order and execute steps 5 to 61.

6. The lifecycle collaborative management method based on multi-channel heterogeneous orders according to claim 5, characterized in that, It also includes a handling method if the recommended time slot does not exist, the method including: Step 60430: Filter out maintenance occupancy records with the preset maintenance type from the candidate occupancy records; Step 60431: Extract the maintenance occupancy period based on the maintenance occupancy record; Step 60432: Calculate the advance maintenance period based on the maintenance occupancy period and the expected occupancy period; Step 60433: Push the advance maintenance period and the preset advance maintenance signal to the preset maintenance management terminal; Step 60434: After receiving the maintenance completion signal from the maintenance management terminal, find the corresponding vehicle number for maintenance according to the maintenance occupancy record and push the vehicle number for maintenance to the user terminal; Step 60435: Upon receiving the repair confirmation signal from the user terminal, update the vehicle occupancy order based on the vehicle repair number to obtain the final vehicle occupancy order; Step 60436: Regenerate the vehicle occupancy request based on the final vehicle occupancy order and execute steps 5 to 61.

7. A lifecycle collaborative management method based on multi-channel heterogeneous orders according to claim 6, characterized in that, It also includes a monitoring method for pushing the advance maintenance period and the preset advance maintenance signal to the preset maintenance management terminal, the method comprising: Step 604330: Obtain the real-time maintenance progress of the maintenance occupancy record; Step 604331: Adjust the advance maintenance time period in real time according to the real-time maintenance progress to obtain the actual maintenance time period; Step 604332: Push the actual maintenance period and the preset adjustable occupancy signal to the user terminal; Step 604333: Receive the adjusted adjustable time period from the user terminal; Step 604334: Update the expected occupancy period in the vehicle occupancy request based on the adjustable occupancy period.

8. The lifecycle collaborative management method based on multi-channel heterogeneous orders according to claim 1, characterized in that, It also includes a monitoring method after locking the vehicle number, which includes: Step 50: Detect new occupancy requests for the same vehicle number based on vehicle number monitoring; Step 51: Push a preset first prompt signal to the user terminal corresponding to the new occupancy request; Step 52: When unlocking the vehicle number, the expected occupancy period corresponding to the occupancy record written in the unified vehicle scheduling table is defined as the locked occupancy period; Step 53: If the expected occupancy period and the locked occupancy period do not overlap, then execute steps 4 to 61 based on the new occupancy request; Step 54: If the expected occupancy period overlaps with the locked occupancy period, the occupancy records written into the unified vehicle scheduling table are monitored to obtain the monitoring status. Step 55: If the monitored state is the preset existence state, no operation is performed; Step 56: If the monitoring status is the preset release status, then push the preset second prompt signal to the user terminal corresponding to the new occupancy request.

9. A lifecycle collaborative management method based on multi-channel heterogeneous orders according to claim 8, characterized in that, It also includes a method for alerting users when a new occupancy request for the same vehicle number is detected based on the vehicle number. This method includes: Step 500: Count the number of new requests that newly occupy space; Step 501: When a vehicle occupancy request is written as an occupancy record into the unified vehicle scheduling table, a real-time reminder signal is generated based on the number of new requests and the preset reminder signal. Step 502: Push a real-time reminder signal to the user terminal corresponding to the vehicle occupancy request.

10. A lifecycle collaborative management system based on multi-channel heterogeneous orders, characterized in that, include: The acquisition module is used to acquire channel orders, vehicle usage query requests, actual vehicle usage records, and real-time maintenance progress. A memory for storing a program of a lifecycle collaborative management method based on multi-channel heterogeneous orders as described in any one of claims 1 to 9; The processor loads and executes programs from memory.