Rescue towing order management methods, systems, equipment and media

Abstract

This invention relates to the field of order management technology, and discloses a method for managing tow truck rescue orders, comprising: extracting user tow truck rescue application data, determining the order type and initial status, setting the status to "created" and generating an initial tow truck rescue order; obtaining user identity information, calculating rescue fees based on the application data and order type, pushing the data to the user and obtaining a push return result; receiving driver order acceptance requests, associated data, and rescue order acceptance data based on the return result, updating the order acceptance data after verification; obtaining on-site data reported by the driver based on the updated order acceptance data, extracting the actual arrival time and location coordinates, updating the initial order to obtain an updated tow truck rescue order; obtaining the destination data reported by the driver and the actual driving distance to calculate the fee, and marking the updated tow truck rescue order as completed. This invention also proposes a tow truck rescue order management system, device, and storage medium. This invention can improve the management efficiency of tow truck rescue orders.

Description

Technical Field

[0001] This invention relates to the field of order management technology, and in particular to a method, system, device and medium for managing rescue trailer orders. Background Technology

[0002] With the continuous growth of car ownership, the demand for roadside assistance and towing services is increasing, and the industry is showing a trend of multi-channel access and multi-entity collaboration. Users can initiate rescue requests through multiple platforms such as apps, WeChat mini-programs, and back-end management systems. At the same time, rescue services need to connect with multiple insurance companies such as PICC, CPIC, and Ping An to complete key processes such as order verification and financial settlement. Therefore, the industry urgently needs an efficient order management system.

[0003] However, the current towing and rescue industry generally suffers from fragmented management and inefficient collaboration, hindering the improvement of service quality and operational efficiency: order data from multiple platforms is fragmented, lacking a unified management entry point for integration; significant differences in interface protocols among different insurance companies lead to high development costs for enterprise integration; and the lack of standardized processes for order status transitions results in delays in information synchronization, failing to meet the real-time control needs of users and partners for order progress. The existing order processing model is no longer suitable for the industry's large-scale and standardized development requirements, necessitating the construction of a complete closed-loop towing and rescue order management solution. Summary of the Invention

[0004] This invention provides a method, system, device, and medium for managing tow truck rescue orders, the main purpose of which is to improve the management efficiency of tow truck rescue orders.

[0005] To achieve the above objectives, the present invention provides a rescue towing order management method, comprising:

[0006] Extract the application data of the user's towing rescue request, obtain the order type and initial status of the towing rescue based on the application data, and adjust the initial status of the order to the creation status to generate an initial towing rescue order;

[0007] Query the user identity information in the application data, calculate the towing rescue fee based on the application data and order type, and push the towing rescue fee to the user according to the user identity information to obtain the push return result;

[0008] Based on the push return result, the order acceptance request, associated data and rescue order acceptance data of the tow truck driver are received. The order acceptance request is verified using the associated data, and the rescue order acceptance data is updated when the verification is successful, so as to obtain the updated order acceptance data.

[0009] Based on the updated order data, the on-site data reported by the tow truck driver is obtained, and the actual arrival time and location coordinates in the on-site data are extracted. Based on the actual arrival time and location coordinates, the initial tow truck rescue order is updated to obtain the updated tow truck rescue order.

[0010] Obtain the destination data reported by the tow truck driver, extract the actual driving distance from the destination data, calculate the towing rescue fee based on the actual driving distance, and mark the status of the updated towing rescue order as completed.

[0011] Optionally, adjusting the initial state of the order to a creation state and generating an initial towing rescue order includes:

[0012] Using the application data as the basic data source, a preset identifier generation algorithm is invoked to generate a unique identifier corresponding to the application data;

[0013] The unique identifier, order type, and application data are associated, and the initial order status is set to the creation status to generate an initial towing rescue order.

[0014] Optionally, after extracting the user's towing assistance request data, the method further includes:

[0015] The request source and data integrity of the application data are verified based on the preset channel key and signature algorithm, and a security verification pass signal is obtained;

[0016] Based on the security verification pass signal and the preset business rule base, the required order data, data format and user account status in the application data are verified for compliance, and the business compliance identifier and cleaned basic order data are obtained.

[0017] By using the business compliance identifier and the preset associated insurance company interface protocol, the insurance information in the basic order data is validated and the interface fields are pre-adapted to obtain insurance accounting order data;

[0018] Based on the insurance accounting order data, a preset geocoding service is invoked to standardize and convert the addresses in the application data, resulting in verified application data.

[0019] Optionally, the step of querying the user identity information in the application data, calculating the towing fee based on the application data and order type, and pushing the towing fee to the user according to the user identity information to obtain the push return result includes:

[0020] Extract the key pricing parameters from the application data, and verify the key pricing parameters and the order type to obtain valid cost calculation data that passes the verification.

[0021] Based on the effective data for cost calculation and the preset dynamic pricing model, an initial cost estimate is obtained, and the initial cost estimate is updated to the preset order database to generate a towing rescue fee.

[0022] Using the user's identity information in the application data, the user's fee notification receiving parameters are obtained, and the towing rescue fee is assembled according to the preset notification template. The preset message interface is then called to push the fee to the user, and the push return result is obtained.

[0023] Optionally, the step of extracting the actual arrival time and location coordinates from the on-site data, and updating the initial towing rescue order based on the actual arrival time and location coordinates to obtain an updated towing rescue order includes:

[0024] The data from the field is subjected to multiple checks, including the integrity of the data package, the authenticity of the driver's identity, the reasonableness of the time when the order's current status is reported, and the distance range between the driver's location and the order address, to obtain data that passes the field checks.

[0025] Based on the on-site verification, the actual arrival time and original positioning coordinates are extracted from the data. A preset coordinate transformation engine is called to convert the original positioning coordinates into standard coordinates under the preset system standard coordinate system, and the initial distance difference with the order receiving location is calculated.

[0026] Based on the actual arrival time, standard coordinates, and initial distance difference, the arrival time, on-site location, and distance traveled fields of the initial towing rescue order are updated to obtain the updated towing rescue order.

[0027] Optionally, after updating the initial towing order based on the actual arrival time and the location coordinates to obtain the updated towing order, the method further includes:

[0028] Generate a structured service record containing on-site photos, coordinate transformation records, status change details, and operation timestamps, and store the structured service record on a preset cloud server.

[0029] Optionally, after calculating the towing and rescue fee based on the application data and order type, the method further includes:

[0030] The calculation process and details of towing rescue costs are integrated according to the preset log format to construct a cost accounting log.

[0031] To address the above problems, the present invention also provides a rescue towing order management system, the system comprising:

[0032] The rescue order creation module is used to extract the application data of the user's towing rescue request, obtain the order type and initial status of the towing rescue based on the application data, and adjust the initial status of the order to the creation status to generate an initial towing rescue order;

[0033] The order message push module is used to query the user identity information in the application data, calculate the towing rescue fee based on the application data and order type, and push the towing rescue fee to the user according to the user identity information, and obtain the push return result;

[0034] The order data update module is used to receive the order request, associated data and rescue order data of the tow truck driver based on the push return result, verify the order request using the associated data, and update the rescue order data when the verification is successful to obtain the updated order data.

[0035] The towing order update module is used to obtain the on-site data reported by the towing driver based on the updated order data, extract the actual arrival time and location coordinates from the on-site data, update the initial towing rescue order based on the actual arrival time and the location coordinates, and obtain the updated towing rescue order.

[0036] The rescue order completion module is used to obtain the destination data reported by the tow truck driver, extract the actual driving distance from the destination data, calculate the tow rescue fee based on the actual driving distance, and mark the status of the updated tow rescue order as completed.

[0037] To address the above problems, the present invention also provides an electronic device, the electronic device comprising:

[0038] At least one processor; and,

[0039] A memory communicatively connected to the at least one processor; wherein,

[0040] The memory stores a computer program that can be executed by the at least one processor, which enables the at least one processor to perform the rescue towing order management method as described above.

[0041] To address the aforementioned problems, the present invention also provides a computer-readable storage medium, including a data storage area and a program storage area. The data storage area stores created data, and the program storage area stores a computer program. When the computer program is executed by a processor, it implements the rescue towing order management method described above.

[0042] This invention, through its embodiments, extracts user towing and rescue application data to determine the order type and initial status, sets the status to "created," and generates an initial towing and rescue order. It then obtains user identity information, calculates rescue fees based on the application data and order type, pushes the information to the user, and receives a push notification. Based on the notification, it receives driver order acceptance requests, associated data, and rescue order acceptance data; after verification, it updates the order acceptance data. Based on the updated order acceptance data, it obtains on-site data reported by the driver, extracts the actual arrival time and location coordinates, updates the initial order, and generates an updated towing and rescue order. Finally, it obtains the driver-reported destination data and actual driving distance to calculate the fee, and marks the updated towing and rescue order as completed. Therefore, the towing and rescue order management method, system, electronic device, and computer-readable storage medium proposed in this invention, through the steps of extracting rescue application data to generate an initial order, calculating fees and pushing notifications to obtain user feedback, verifying driver order acceptance requests to update order acceptance data, collecting on-site data to update the order status, extracting destination data to calculate the final fee, and marking the order as completed, solves the problems of fragmented order data, inefficient multi-entity collaboration, and non-standard status transitions in the towing and rescue industry, thereby improving the management efficiency of towing and rescue orders. Attached Figure Description

[0043] Figure 1 This is a flowchart illustrating a rescue towing order management method according to an embodiment of the present invention;

[0044] Figure 2 A schematic diagram of the modules of a rescue towing order management system provided in an embodiment of the present invention;

[0045] Figure 3 This is a schematic diagram of the internal structure of an electronic device for implementing a rescue trailer order management method according to an embodiment of the present invention.

[0046] The realization of the objective, functional features and advantages of the present invention will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0047] It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

[0048] This application provides a method for managing tow truck orders. The executing entity of the tow truck order management method includes, but is not limited to, at least one of the following electronic devices that can be configured to execute the method provided in this application: a server, a terminal, etc. The server can be a standalone server or a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery networks (CDNs), and big data and artificial intelligence platforms. In other words, the tow truck order management method can be executed by software or hardware installed on remote devices or server-side devices, and the software can be a blockchain platform. The server includes, but is not limited to, a single server, a server cluster, a cloud server, or a cloud server cluster.

[0049] Reference Figure 1 The diagram shown is a flowchart illustrating a rescue tow truck order management method according to an embodiment of the present invention. In this embodiment, the rescue tow truck order management method includes the following steps S1-S5:

[0050] S1. Extract the application data of the user's towing rescue request, obtain the order type and initial status of the towing rescue based on the application data, and adjust the initial status of the order to the creation status to generate an initial towing rescue order.

[0051] Understandably, by extracting and verifying user application data, automatically identifying order types, setting initial states, and generating structured order records, unstructured user requests can be transformed into standard business objects that the system can process. This provides a unified data foundation and process starting point for subsequent driver matching, status transitions, and fee calculations, effectively improving the accuracy, consistency, and processing efficiency of order creation.

[0052] The order type refers to a business classification identifier used to distinguish different types of roadside assistance requests. It typically includes at least two types: "Immediate Assistance" (vehicle breakdown requiring immediate on-site assistance) and "Scheduled Towing" (vehicle transfer with a pre-arranged service time). In this embodiment of the invention, the order type determines the subsequent lifecycle of the entire order, pricing rules, driver matching strategy, and process logic.

[0053] The initial order status refers to the first business status of an order in the system's lifecycle. It is usually set to an initial value indicating "received request, pending processing" when the order is created, such as "pending confirmation" or "pending dispatch". This signifies that the order has successfully entered the system workflow and is the starting point for all subsequent status transitions.

[0054] The initial towing and rescue order refers to the first complete and structured data record or business object created by the system based on the user's application data. It contains all basic data such as user information, vehicle information, location information, order type, and initial status.

[0055] Furthermore, after extracting the user's towing assistance request data, the method further includes:

[0056] The request source and data integrity of the application data are verified based on the preset channel key and signature algorithm, and a security verification pass signal is obtained;

[0057] Based on the security verification pass signal and the preset business rule base, the required order data, data format and user account status in the application data are verified for compliance, and the business compliance identifier and cleaned basic order data are obtained.

[0058] By using the business compliance identifier and the preset associated insurance company interface protocol, the insurance information in the basic order data is validated and the interface fields are pre-adapted to obtain insurance accounting order data;

[0059] Based on the insurance accounting order data, a preset geocoding service is invoked to standardize and convert the addresses in the application data, resulting in verified application data.

[0060] Among them, the channel key refers to the unique identity verification key assigned by the platform to various order submission channels (such as APP, mini-program, and interface of cooperative rescue organizations). It is divided into two categories: channel public key and channel private key, which are used to verify the legitimacy of the source of the order request and prevent illegal channels from forging order data and submitting it to the system.

[0061] The signature algorithm refers to the hash / encryption calculation rules (such as MD5, SHA256, HMAC, etc.) used to encrypt order application data, and is used to verify the integrity and tamper-proof nature of order data during transmission. For example, the channel generates a signature value for the application data according to the algorithm, and the system calculates and compares the signature using the same algorithm after receiving it. If they match, it is determined that the data has not been tampered with.

[0062] The business rule base refers to the set of pre-configured towing and rescue order business verification rules in the system. It serves as the basis for determining whether an order meets the platform's service requirements. Specifically, it includes rules for verifying mandatory order fields, data format specifications, user account status determination conditions, and service area restriction rules.

[0063] Among them, the required data for the order refers to the core data fields that are essential for completing the creation of a towing and rescue order. If they are missing, the subsequent process cannot be completed. These fields include: user identity information, rescue location, vehicle information, and order type.

[0064] Among them, the business compliance identifier refers to the status identifier generated after the system completes the business compliance verification of order data, which is used to mark whether the order data meets the requirements of the business rule base.

[0065] Among them, the associated insurance company interface protocol refers to the data interaction standard agreed upon by the platform and the cooperating insurance company, including interface call address, data transmission format (such as JSON / XML), field naming rules, parameter validation requirements, return result definition, etc., to ensure that the order data output by the platform can be correctly parsed by the insurance company system to support subsequent insurance reimbursement, claims and other processes.

[0066] Geocoding service refers to the service that converts non-standardized address text (such as "XX City XX District XX Road XX Community Entrance") in order application data into standardized geographic coordinates (latitude and longitude), or vice versa, to standard address. This is used to unify the address data format and provide accurate location basis for subsequent driver dispatching, driving distance calculation, and service area determination.

[0067] Further, adjusting the initial order status to a creation status and generating an initial towing rescue order includes:

[0068] Using the application data as the basic data source, a preset identifier generation algorithm is invoked to generate a unique identifier corresponding to the application data;

[0069] The unique identifier, order type, and application data are associated, and the initial order status is set to the creation status to generate an initial towing rescue order.

[0070] Among them, the unique identifier refers to the globally unique order code generated by a preset algorithm based on the towing and rescue order application data. The unique identifier serves as the exclusive digital identity of the order, associating the order type with the application data. It runs through the entire process of order creation, order acceptance, fulfillment, and settlement, and is the core index for realizing data association and traceability at each stage.

[0071] S2. Query the user identity information in the application data, calculate the towing rescue fee based on the application data and order type, and push the towing rescue fee to the user according to the user identity information to obtain the push return result.

[0072] Understandably, by querying user identity information, combining order application data and order type to accurately calculate towing and rescue fees and push them to users for feedback, it can not only achieve cost transparency and improve user trust, but also use user fee confirmation results as a prerequisite for order fulfillment, reducing the risk of subsequent service disputes and resource waste. At the same time, it can achieve differentiated pricing and services based on user identity association, and provide legal data support for subsequent financial settlement.

[0073] Among them, the towing rescue fee refers to the total service fee calculated by combining the application data of the towing rescue order (such as rescue location, rescue distance, vehicle type requirements, service time) and the order type (instant rescue / reserved towing) according to the platform's preset pricing rules (basic towing fee + mileage fee + time premium + value-added service fee, etc.).

[0074] Among them, the push return result refers to the user feedback status data obtained after the system pushes the calculated towing rescue fee to the user terminal (APP, mini program, SMS, etc.). It mainly includes two types of results: one is the user's instruction to accept the fee, and the other is the user's instruction to refuse the fee or make adjustment requests. This result is the core prerequisite for the order to enter the subsequent order dispatching stage.

[0075] Further, the process of querying the user identity information in the application data, calculating the towing fee based on the application data and order type, and pushing the towing fee to the user according to the user identity information to obtain the push return result includes:

[0076] Extract the key pricing parameters from the application data, and verify the key pricing parameters and the order type to obtain valid cost calculation data that passes the verification.

[0077] Based on the effective data for cost calculation and the preset dynamic pricing model, an initial cost estimate is obtained, and the initial cost estimate is updated to the preset order database to generate a towing rescue fee.

[0078] Using the user's identity information in the application data, the user's fee notification receiving parameters are obtained, and the towing rescue fee is assembled according to the preset notification template. The preset message interface is then called to push the fee to the user, and the push return result is obtained.

[0079] Among them, the key pricing parameters refer to the core data fields that support the calculation of towing and rescue fees. They directly determine the amount of the fee and are the input data source for the dynamic pricing model. Specifically, they include the distance between the rescue departure point and the destination, the vehicle type of the rescue, the order type, the service time requirements, and the demand for additional value-added services.

[0080] Among them, valid data for cost calculation refers to usable data that meets preset rules after the key pricing parameters and order type have been verified for legality, completeness, and consistency. For example, the rescue distance must be a non-negative number, the order type must match the system's preset type, and the vehicle model must be within the platform's service range. Invalid data will be filtered out, and only data that passes the verification can enter the cost calculation process.

[0081] The dynamic pricing model refers to the platform's preset fee calculation rules and algorithm engine, which can dynamically output corresponding fees based on different input parameters, rather than using fixed pricing.

[0082] For example, one model is a dynamic pricing model based on basic mileage plus time-based coefficients. For instance, if the basic rescue fee is 100 yuan, the mileage unit price is 5 yuan / km, the rescue mileage is 20km, and the daytime time-based coefficient is 1.0, then the cost is 100 + 20 × 5 × 1.0 = 200 yuan. If the nighttime coefficient is 1.3, then the cost is 100 + 20 × 5 × 1.3 = 230 yuan. Another model is a pricing model that combines vehicle type, distance, and value-added services. For instance, if the basic fee is 100 yuan, the mileage is 15km, the mileage unit price is 5 yuan, and the coefficient for small vehicles is 1.0, then the cost is 100 + 15 × 5 + 0 × 100 = 175 yuan. If the coefficient for large vehicles is 1.8 plus a highway rescue value-added service fee of 80 yuan, then the cost is 100 + 15 × 5 + 1.8 × 100 + 80 = 435 yuan. This model can adapt to the pricing needs of different vehicle types and complex rescue scenarios.

[0083] The order database refers to a structured database used to store data on the entire lifecycle of towing and rescue orders, and serves as a unified management platform for order data.

[0084] Among them, the towing and rescue fee refers to the standardized and pushable formal fee amount generated after the initial cost estimate is updated to the order database, which is the basis for the final quotation displayed to the user.

[0085] Among them, the preset notification template refers to the fee notification format template pre-configured by the platform, which is used to unify the content and style of fee push and improve user experience.

[0086] The message push interface refers to the technical interface used to transmit fee notifications to user terminals, serving as a communication bridge between the system and the user. Interface types include: in-app message interfaces, SMS interfaces, and WeChat official account template message interfaces; interface functions include: receiving the fee notification content assembled by the system, pushing it according to the user's receiving parameters (phone number, app account), and returning the push status.

[0087] Furthermore, after obtaining the towing rescue fee, the calculation process and details of the towing rescue fee can be integrated according to the preset log format to obtain the fee accounting log information.

[0088] S3. Based on the push return result, receive the tow truck driver's order acceptance request, associated data, and rescue order acceptance data. Use the associated data to verify the order acceptance request, and update the rescue order acceptance data when the verification is successful to obtain updated order acceptance data.

[0089] Understandably, verifying the legality and uniqueness of tow truck driver order requests through data correlation, and updating rescue order data in real time after verification, not only reduces the risk of invalid order dispatch and resource waste, but also provides accurate and consistent data source support for subsequent order fulfillment.

[0090] Among them, the associated data refers to various verification and business data that are strongly related to the tow truck driver's order acceptance request. It is the core basis for verifying the legality and matching degree of the order acceptance request and mainly includes three types of information: First, driver-side data, such as driver ID, qualification certificate status, service area range, current transportation capacity status, identity key, etc.; Second, order-side data, such as order unique identifier, order type, rescue location, user fee confirmation status, order current status, etc.; Third, system-side rule data, such as the lock status to prevent duplicate orders, driver and order matching rules, platform service permission configuration, etc.

[0091] Updating order acceptance data refers to the real-time fulfillment data set generated by the system after the driver's order acceptance request has been verified. This data set integrates order data and driver information and serves as the core data carrier for the order to enter subsequent service stages. Specifically, it includes the driver's order acceptance location, order acceptance timestamp, bound unique order identifier, and updated order status. This data is synchronized to the order database to provide data support for subsequent stages such as driver location tracking, on-site arrival verification, and final fare calculation.

[0092] Specifically, the updated order data may include driver location update data, complete order data, notification push results, and structured notification logs.

[0093] S4. Based on the updated order data, obtain the on-site data reported by the tow truck driver, extract the actual arrival time and location coordinates from the on-site data, update the initial tow truck rescue order based on the actual arrival time and the location coordinates, and obtain the updated tow truck rescue order.

[0094] Understandably, by acquiring and extracting the actual arrival time and location coordinates from the on-site data reported by the tow truck driver, and updating the initial towing and rescue order to generate an updated order, on the one hand, the order fulfillment status is synchronized in real time, allowing the platform and users to clearly grasp the rescue progress and avoid communication costs and trust loss caused by information lag; on the other hand, accurate fulfillment data is retained, and the actual arrival time and location coordinates can serve as the core basis for subsequent calculation of actual service time and mileage, providing real and effective data support for final fee settlement and insurance reimbursement, and ensuring the traceability of the entire order fulfillment process.

[0095] Among them, on-site data refers to the first-hand data related to rescue contract fulfillment reported by the tow truck driver through the platform terminal (APP, mini program, etc.) after arriving at the rescue site. It is the core basis for recording the driver's arrival status. In addition to the actual arrival time and location coordinates, it usually includes on-site vehicle malfunction photos / videos, details of the location of the vehicle to be rescued, and on-site service condition remarks (such as whether it is on the highway, whether crane assistance is required), etc.

[0096] The actual arrival time refers to the precise time when the tow truck driver arrives at the rescue site. It is generally based on the system timestamp when the driver clicks the "Arrived" button on the terminal at the scene, or the time recorded by location tracking. This time is crucial data for calculating the driver's order response time and service efficiency, and is also an important basis for subsequent fee settlement and order fulfillment assessment.

[0097] Further, the step of extracting the actual arrival time and location coordinates from the on-site data, and updating the initial towing rescue order based on the actual arrival time and location coordinates to obtain an updated towing rescue order includes:

[0098] The data from the field is subjected to multiple checks, including the integrity of the data package, the authenticity of the driver's identity, the reasonableness of the time when the order's current status is reported, and the distance range between the driver's location and the order address, to obtain data that passes the field checks.

[0099] Based on the on-site verification, the actual arrival time and original positioning coordinates are extracted from the data. A preset coordinate transformation engine is called to convert the original positioning coordinates into standard coordinates under the preset system standard coordinate system, and the initial distance difference with the order receiving location is calculated.

[0100] Based on the actual arrival time, standard coordinates, and initial distance difference, the arrival time, on-site location, and distance traveled fields of the initial towing rescue order are updated to obtain the updated towing rescue order.

[0101] Packet integrity refers to the integrity verification of the data packets reported by the driver, used to confirm that the data packets have not been lost, tampered with, or damaged during transmission. Verification includes checking whether the data packet contains required fields, whether the data packet format conforms to preset specifications, and whether the data signature matches the system's calculated value. If the data packet is missing key information or has an abnormal format, it is determined to be "incomplete," and the report is rejected.

[0102] The verification of driver identity authenticity refers to confirming whether the entity reporting the on-site data is the compliant tow truck driver bound to the order. Verification methods typically include: verifying whether the driver's login account matches the driver ID bound to the order; confirming the validity of the driver's submitted identity key (such as terminal device code or dynamic password); and confirming that the driver's current status is "order accepted" and not frozen. This verification prevents others from impersonating the driver and falsifying on-site data.

[0103] The reasonableness of the order's current status reporting time refers to verifying whether the reporting time of the on-site data matches the current fulfillment status of the order, avoiding time logic contradictions. The core verification logic is: the reporting time must be later than the driver's order acceptance time, must be within the reasonable fulfillment time frame preset for the order (e.g., for immediate rescue, arrival data must be reported within 2 hours after order acceptance), and the deviation from the current system time must be within the allowable range (e.g., ±5 minutes, to prevent malicious tampering with the timestamp).

[0104] The distance range between the driver's location and the order address refers to verifying whether the actual straight-line distance between the driver's reported location coordinates and the preset rescue address in the order is within a reasonable threshold. The platform will preset a distance threshold (e.g., ±500 meters). If the distance exceeds the threshold, it is judged as "location abnormal," requiring the driver to re-confirm the report or manual intervention for verification. This verification is used to ensure that the driver has indeed arrived at the rescue site specified in the order and to avoid false check-ins.

[0105] The raw location coordinates refer to the unstandardized geographic coordinate data directly collected and reported by the driver's terminal (mobile phone, vehicle positioning device, etc.). These coordinates may be based on different coordinate systems, and due to differences in terminals or map service providers, there may be issues with inconsistent formats and incompatibility with the platform system's coordinate system. They need to be converted before they can be used for subsequent calculations.

[0106] The coordinate transformation engine refers to the platform's pre-defined geographic coordinate system transformation tools / algorithms. Its core function is to convert raw location coordinates from different sources into the standard coordinate system specified by the platform system. It has built-in transformation formulas for multiple coordinate systems, can automatically identify the coordinate system type of the original coordinates, and output standard coordinates in a uniform format, ensuring the accuracy of subsequent distance calculations and location display.

[0107] Furthermore, after receiving the updated towing and rescue order, the method also includes generating a structured service record containing on-site photos, coordinate transformation records, status change details, and operation timestamps, and storing the structured service record to a preset cloud server.

[0108] In this embodiment of the invention, by generating a structured service record containing on-site photos, coordinate transformation records, status change details, and operation timestamps and storing it on a cloud server, it can retain complete data credentials for key nodes of order fulfillment, providing a true and traceable basis for subsequent cost calculation, insurance reimbursement, and dispute investigation. It can also achieve standardized management of order service data, facilitating the platform to perform operational optimization work such as fulfillment efficiency analysis and driver service quality assessment.

[0109] S5. Obtain the destination data reported by the tow truck driver, extract the actual driving distance from the destination data, calculate the towing rescue fee based on the actual driving distance, and mark the status of the updated towing rescue order as completed.

[0110] Understandably, by obtaining the destination data reported by the driver and extracting the actual driving distance to calculate the final towing and rescue fee, and marking the order as completed, the platform achieves accurate cost calculation, replaces the pre-estimated cost with actual performance data, ensures the fairness of the fee settlement between the platform and the user, completes the closed-loop management of the entire order lifecycle, clarifies the final node of order performance, and retains data such as the actual driving distance, which can serve as the core basis for driver service settlement and insurance claim verification.

[0111] The destination data refers to the complete set of data reported by the tow truck driver through the platform terminal after completing the rescue service and delivering the vehicle to the user's designated destination. In addition to the core actual driving distance, it usually includes destination location coordinates, delivery timestamp, vehicle delivery confirmation information, photos / videos of the service completion site, and user signature confirmation records (electronic or paper), which are the key basis for determining the completion of order fulfillment.

[0112] The actual driving distance refers to the actual mileage traveled by the tow truck from the rescue site to the designated destination. This data is generally obtained through trajectory records from onboard positioning devices, mileage statistics from navigation systems, or mileage reports from driver terminals, combined with the platform's preset mileage calibration rules. It is the core data for calculating the final towing rescue cost and comparing the difference with the estimated mileage.

[0113] This invention extracts towing assistance application data, obtains the order type and initial status, and generates an initial order by setting it to the creation status; queries user identity information, calculates the fee based on the application data and order type, and pushes it to the system, obtaining the returned result; receives driver order acceptance requests and related data based on the result, and updates the order acceptance data after verification; obtains on-site data reported by the driver, extracts the arrival time and coordinates to update the order; obtains destination data, extracts the actual driving distance to calculate the fee, and marks the order as completed. Therefore, the towing assistance order management method, system, electronic device, and computer-readable storage medium proposed in this invention solve the problems of fragmented order data, inefficient multi-entity collaboration, and non-standard status transitions in the towing assistance industry by extracting assistance application data to generate an initial order, calculating the fee and pushing it to obtain user feedback, verifying driver order acceptance requests to update order acceptance data, collecting on-site data to update the order status, extracting destination data to calculate the final fee, and marking the order as completed. This improves the management efficiency of towing assistance orders.

[0114] like Figure 2 The diagram shown is a schematic diagram of the modules of the rescue trailer order management system of the present invention.

[0115] The rescue towing order management system 100 of this invention can be installed in an electronic device. Depending on the functions implemented, the rescue towing order management system may include a rescue order creation module 101, an order message push module 102, an order data update module 103, a towing order update module 104, and a rescue order completion module 105. The module described in this invention can also be referred to as a unit, which refers to a series of computer program segments that can be executed by the processor of an electronic device and can perform a fixed function, and are stored in the memory of the electronic device.

[0116] In this embodiment, the functions of each module / unit are as follows:

[0117] The rescue order creation module 101 is used to extract the application data of the user's towing rescue application, obtain the order type and initial status of the towing rescue based on the application data, and adjust the initial status of the order to the creation status to generate an initial towing rescue order.

[0118] The order message push module 102 is used to query the user identity information in the application data, calculate the towing rescue fee based on the application data and order type, and push the towing rescue fee to the user according to the user identity information, and obtain the push return result;

[0119] The order data update module 103 is used to receive the order request, associated data and rescue order data of the tow truck driver based on the push return result, verify the order request using the associated data, and update the rescue order data when the verification is successful, so as to obtain the updated order data.

[0120] The towing order update module 104 is used to obtain the on-site data reported by the towing driver based on the updated order data, extract the actual arrival time and location coordinates from the on-site data, update the initial towing rescue order based on the actual arrival time and the location coordinates, and obtain the updated towing rescue order.

[0121] The rescue order completion module 105 is used to obtain the destination data reported by the tow truck driver, extract the actual driving distance from the destination data, calculate the tow rescue fee based on the actual driving distance, and mark the status of the updated tow rescue order as completed.

[0122] In detail, the modules in the rescue towing order management system 100 described in this embodiment of the invention adopt the same usage as described above. Figure 1 The rescue towing order management method uses the same technical means and can produce the same technical effect, so it will not be described in detail here.

[0123] like Figure 3 The diagram shown is a structural schematic of the electronic device for implementing the rescue trailer order management method of the present invention.

[0124] The electronic device may include a processor 10, a memory 11, a communication bus 12 and a communication interface 13, and may also include a computer program stored in the memory 11 and capable of running on the processor 10, such as a rescue towing order management program.

[0125] In some embodiments, the processor 10 may be composed of integrated circuits, such as a single packaged integrated circuit or multiple integrated circuits with the same or different functions, including combinations of one or more central processing units (CPUs), microprocessors, digital processing chips, graphics processors, and various control chips. The processor 10 is the control unit of the electronic device, connecting various components of the entire electronic device through various interfaces and lines. It executes programs or modules stored in the memory 11 (e.g., executing a rescue towing order management program) and calls data stored in the memory 11 to perform various functions of the electronic device and process data.

[0126] The memory 11 includes at least one type of readable storage medium, including flash memory, portable hard drive, multimedia card, card-type memory (e.g., SD or DX memory), magnetic memory, magnetic disk, optical disk, etc. In some embodiments, the memory 11 can be an internal storage unit of an electronic device, such as a portable hard drive. In other embodiments, the memory 11 can be an external storage device of the electronic device, such as a plug-in portable hard drive, smart media card (SMC), secure digital (SD) card, flash card, etc. Furthermore, the memory 11 can include both internal and external storage units of the electronic device. The memory 11 can be used not only to store application software and various types of data installed on the electronic device, such as the code of a rescue towing order management program, but also to temporarily store data that has been output or will be output.

[0127] The communication bus 12 can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. This bus can be divided into an address bus, a data bus, a control bus, etc. The bus is configured to enable communication between the memory 11 and at least one processor 10, etc.

[0128] The communication interface 13 is used for communication between the aforementioned electronic device and other devices, including a network interface and a user interface. Optionally, the network interface may include a wired interface and / or a wireless interface (such as a Wi-Fi interface, Bluetooth interface, etc.), typically used to establish communication connections between the electronic device and other electronic devices. The user interface may be a display, an input unit (such as a keyboard), or optionally, a standard wired or wireless interface. Optionally, in some embodiments, the display may be an LED display, a liquid crystal display, a touch-sensitive liquid crystal display, or an OLED (Organic Light-Emitting Diode) touchscreen, etc. The display may also be appropriately referred to as a screen or display unit, used to display information processed in the electronic device and to display a visual user interface.

[0129] Figure 3 Only electronic devices with components are shown; it will be understood by those skilled in the art that... Figure 3The structure shown does not constitute a limitation on the electronic device and may include fewer or more components than shown, or combine certain components, or have different component arrangements.

[0130] For example, although not shown, the electronic device may also include a power supply (such as a battery) to power the various components. Preferably, the power supply can be logically connected to the at least one processor 10 through a power management device, thereby enabling functions such as charging management, discharging management, and power consumption management. The power supply may also include one or more DC or AC power supplies, recharging devices, power fault detection circuits, power converters or inverters, power status indicators, and other arbitrary components. The electronic device may also include various sensors, Bluetooth modules, Wi-Fi modules, etc., which will not be described in detail here.

[0131] It should be understood that the embodiments described are for illustrative purposes only and are not limited to this structure in the scope of the patent application.

[0132] The rescue towing order management program stored in the memory 11 of the electronic device is a combination of multiple computer programs. When run in the processor 10, it can achieve the following:

[0133] Extract the application data of the user's towing rescue request, obtain the order type and initial status of the towing rescue based on the application data, and adjust the initial status of the order to the creation status to generate an initial towing rescue order;

[0134] Query the user identity information in the application data, calculate the towing rescue fee based on the application data and order type, and push the towing rescue fee to the user according to the user identity information to obtain the push return result;

[0135] Based on the push return result, the order acceptance request, associated data and rescue order acceptance data of the tow truck driver are received. The order acceptance request is verified using the associated data, and the rescue order acceptance data is updated when the verification is successful, so as to obtain the updated order acceptance data.

[0136] Based on the updated order data, the on-site data reported by the tow truck driver is obtained, and the actual arrival time and location coordinates in the on-site data are extracted. Based on the actual arrival time and location coordinates, the initial tow truck rescue order is updated to obtain the updated tow truck rescue order.

[0137] Obtain the destination data reported by the tow truck driver, extract the actual driving distance from the destination data, calculate the towing rescue fee based on the actual driving distance, and mark the status of the updated towing rescue order as completed.

[0138] Specifically, the processor 10's implementation method of the above-mentioned computer program can be found in [reference needed]. Figure 1 The descriptions of the relevant steps in the corresponding embodiments are not repeated here.

[0139] Furthermore, if the modules / units integrated into the electronic device are implemented as software functional units and sold or used as independent products, they can be stored in a non-volatile computer-readable storage medium. The computer-readable storage medium can be volatile or non-volatile. For example, the computer-readable medium may include: any entity or device capable of carrying the computer program code, a recording medium, a USB flash drive, a portable hard drive, a magnetic disk, an optical disk, a computer memory, or a read-only memory (ROM).

[0140] The present invention also provides a computer-readable storage medium storing a computer program, which, when executed by a processor of an electronic device, can perform the following:

[0141] Extract the application data of the user's towing rescue request, obtain the order type and initial status of the towing rescue based on the application data, and adjust the initial status of the order to the creation status to generate an initial towing rescue order;

[0142] Query the user identity information in the application data, calculate the towing rescue fee based on the application data and order type, and push the towing rescue fee to the user according to the user identity information to obtain the push return result;

[0143] Based on the push return result, the order acceptance request, associated data and rescue order acceptance data of the tow truck driver are received. The order acceptance request is verified using the associated data, and the rescue order acceptance data is updated when the verification is successful, so as to obtain the updated order acceptance data.

[0144] Based on the updated order data, the on-site data reported by the tow truck driver is obtained, and the actual arrival time and location coordinates in the on-site data are extracted. Based on the actual arrival time and location coordinates, the initial tow truck rescue order is updated to obtain the updated tow truck rescue order.

[0145] Obtain the destination data reported by the tow truck driver, extract the actual driving distance from the destination data, calculate the towing rescue fee based on the actual driving distance, and mark the status of the updated towing rescue order as completed.

[0146] In the several embodiments provided by this invention, it should be understood that the disclosed devices, systems, and methods can be implemented in other ways. For example, the system embodiments described above are merely illustrative; for instance, the division of modules is only a logical functional division, and other division methods may be used in actual implementation.

[0147] The modules described as separate components may or may not be physically separate. The components shown as modules may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs.

[0148] Furthermore, the functional modules in the various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or in the form of hardware plus software functional modules.

[0149] It will be apparent to those skilled in the art that the present invention is not limited to the details of the exemplary embodiments described above, and that the present invention can be implemented in other specific forms without departing from the spirit or essential characteristics of the present invention.

[0150] Therefore, the embodiments should be considered exemplary and non-limiting in all respects, and the scope of the invention is defined by the appended claims rather than the foregoing description. Thus, all variations falling within the meaning and scope of equivalents of the claims are intended to be embraced within the invention. No appended diagram markings in the claims should be construed as limiting the scope of the claims.

[0151] The blockchain referred to in this invention is a novel application model of computer technologies such as distributed data storage, peer-to-peer transmission, consensus mechanisms, and encryption algorithms. Essentially, a blockchain is a decentralized database, a chain of data blocks linked together using cryptographic methods. Each data block contains information about a batch of network transactions, used to verify the validity of the information (anti-counterfeiting) and generate the next block. A blockchain can include an underlying blockchain platform, a platform product service layer, and an application service layer.

[0152] The embodiments of this application can acquire and process relevant data based on artificial intelligence technology. Artificial intelligence (AI) refers to the theories, methods, technologies, and application systems that use digital computers or machines controlled by digital computers to simulate, extend, and expand human intelligence, perceive the environment, acquire knowledge, and use that knowledge to obtain optimal results.

[0153] Furthermore, it is clear that the word "comprising" does not exclude other units or steps, and the singular does not exclude the plural. Multiple units or systems stated in a system claim may also be implemented by a single unit or system through software or hardware. The term "second class" is used to indicate names and does not indicate any specific order.

[0154] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention and are not intended to limit it. Although the present invention has been described in detail with reference to preferred embodiments, those skilled in the art should understand that modifications or equivalent substitutions can be made to the technical solutions of the present invention without departing from the spirit and scope of the technical solutions of the present invention.

Claims

1. A method of managing orders for rescue trailers, characterized in that, The method includes: Extract the application data of the user's towing rescue request, obtain the order type and initial status of the towing rescue based on the application data, and adjust the initial status of the order to the creation status to generate an initial towing rescue order; Query the user identity information in the application data, calculate the towing rescue fee based on the application data and order type, and push the towing rescue fee to the user according to the user identity information to obtain the push return result; Based on the push return result, the order acceptance request, associated data and rescue order acceptance data of the tow truck driver are received. The order acceptance request is verified using the associated data, and the rescue order acceptance data is updated when the verification is successful, so as to obtain the updated order acceptance data. Based on the updated order data, the on-site data reported by the tow truck driver is obtained, and the actual arrival time and location coordinates in the on-site data are extracted. Based on the actual arrival time and location coordinates, the initial tow truck rescue order is updated to obtain the updated tow truck rescue order. Obtain the destination data reported by the tow truck driver, extract the actual driving distance from the destination data, calculate the towing rescue fee based on the actual driving distance, and mark the status of the updated towing rescue order as completed. The method further includes, after extracting the user's towing assistance request data: The request source and data integrity of the application data are verified based on the preset channel key and signature algorithm, and a security verification pass signal is obtained; Based on the security verification pass signal and the preset business rule base, the required order data, data format and user account status in the application data are verified for compliance, and the business compliance identifier and cleaned basic order data are obtained. By using the business compliance identifier and the preset associated insurance company interface protocol, the insurance information in the basic order data is validated and the interface fields are pre-adapted to obtain insurance accounting order data; Based on the insurance accounting order data, a preset geocoding service is called to standardize and convert the address in the application data to obtain the verified application data; The step of extracting the actual arrival time and location coordinates from the on-site data, and updating the initial towing order based on the actual arrival time and location coordinates to obtain an updated towing order includes: The data from the field is subjected to multiple checks, including the integrity of the data package, the authenticity of the driver's identity, the reasonableness of the time when the order's current status is reported, and the distance range between the driver's location and the order address, to obtain data that passes the field checks. Based on the on-site verification, the actual arrival time and original positioning coordinates are extracted from the data. A preset coordinate transformation engine is called to convert the original positioning coordinates into standard coordinates under the preset system standard coordinate system, and the initial distance difference with the order receiving location is calculated. Based on the actual arrival time, standard coordinates, and initial distance difference, the arrival time, on-site location, and distance traveled fields of the initial towing rescue order are updated to obtain the updated towing rescue order.

2. The rescue trailer order management method of claim 1, wherein, The step of adjusting the initial state of the order to the creation state and generating an initial towing and rescue order includes: Using the application data as the basic data source, a preset identifier generation algorithm is invoked to generate a unique identifier corresponding to the application data; The unique identifier, order type, and application data are associated, and the initial order status is set to the creation status to generate an initial towing rescue order.

3. The rescue towing order management method as described in claim 1, characterized in that, The process of querying user identity information in the application data, calculating towing fees based on the application data and order type, and pushing the towing fees to the user according to the user identity information, resulting in a push return result, includes: Extract the key pricing parameters from the application data, and verify the key pricing parameters and the order type to obtain valid cost calculation data that passes the verification. Based on the effective data for cost calculation and the preset dynamic pricing model, an initial cost estimate is obtained, and the initial cost estimate is updated to the preset order database to generate a towing rescue fee. Using the user's identity information in the application data, the user's fee notification receiving parameters are obtained, and the towing rescue fee is assembled according to the preset notification template. The preset message interface is then called to push the fee to the user, and the push return result is obtained.

4. The rescue towing order management method as described in claim 1, characterized in that, After updating the initial towing order based on the actual arrival time and the location coordinates to obtain the updated towing order, the method further includes: Generate a structured service record containing on-site photos, coordinate transformation records, status change details, and operation timestamps, and store the structured service record on a preset cloud server.

5. The rescue towing order management method as described in any one of claims 1 to 4, characterized in that, After calculating the towing and rescue fee based on the application data and order type, the method further includes: The calculation process and details of towing rescue costs are integrated according to the preset log format to construct a cost accounting log.

6. A rescue towing order management system, characterized in that, The system includes: The rescue order creation module is used to extract the application data of the user's towing rescue request, obtain the order type and initial status of the towing rescue based on the application data, and adjust the initial status of the order to the creation status to generate an initial towing rescue order; After extracting the user's towing assistance request data, the process also includes: The request source and data integrity of the application data are verified based on the preset channel key and signature algorithm, and a security verification pass signal is obtained; Based on the security verification pass signal and the preset business rule base, the required order data, data format and user account status in the application data are verified for compliance, and the business compliance identifier and cleaned basic order data are obtained. By using the business compliance identifier and the preset associated insurance company interface protocol, the insurance information in the basic order data is validated and the interface fields are pre-adapted to obtain insurance accounting order data; Based on the insurance accounting order data, a preset geocoding service is called to standardize and convert the address in the application data to obtain the verified application data; The order message push module is used to query the user identity information in the application data, calculate the towing rescue fee based on the application data and order type, and push the towing rescue fee to the user according to the user identity information, and obtain the push return result; The order data update module is used to receive the order request, associated data and rescue order data of the tow truck driver based on the push return result, verify the order request using the associated data, and update the rescue order data when the verification is successful to obtain the updated order data. The towing order update module is used to obtain the on-site data reported by the towing driver based on the updated order data, extract the actual arrival time and location coordinates from the on-site data, update the initial towing rescue order based on the actual arrival time and the location coordinates, and obtain the updated towing rescue order. The step of extracting the actual arrival time and location coordinates from the on-site data, and updating the initial towing order based on the actual arrival time and location coordinates to obtain an updated towing order includes: The data from the field is subjected to multiple checks, including the integrity of the data package, the authenticity of the driver's identity, the reasonableness of the time when the order's current status is reported, and the distance range between the driver's location and the order address, to obtain data that passes the field checks. Based on the on-site verification, the actual arrival time and original positioning coordinates are extracted from the data. A preset coordinate transformation engine is called to convert the original positioning coordinates into standard coordinates under the preset system standard coordinate system, and the initial distance difference with the order receiving location is calculated. Based on the actual arrival time, standard coordinates, and initial distance difference, the arrival time, on-site location, and distance traveled fields of the initial towing rescue order are updated to obtain the updated towing rescue order; The rescue order completion module is used to obtain the destination data reported by the tow truck driver, extract the actual driving distance from the destination data, calculate the tow rescue fee based on the actual driving distance, and mark the status of the tow rescue order as completed.

7. An electronic device, characterized in that, The electronic device includes: At least one processor; and, A memory communicatively connected to the at least one processor; wherein, The memory stores a computer program that can be executed by the at least one processor, the computer program being executed by the at least one processor to enable the at least one processor to perform the rescue trailer order management method as described in any one of claims 1 to 5.

8. A computer-readable storage medium, characterized in that, It includes a data storage area and a program storage area. The data storage area stores the created data, and the program storage area stores the computer program. When the computer program is executed by the processor, it implements the rescue towing order management method as described in any one of claims 1 to 5.

Images