Online car-hailing operation settlement system based on configurable commission extraction proportion
By using a ride-hailing operation settlement system based on configurable commission rates, the problem of poor adaptability of traditional systems has been solved, enabling accurate fee sharing and flexible management in multiple business scenarios, and improving operational efficiency and data security.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-01-22
- Publication Date
- 2026-04-14
AI Technical Summary
Traditional ride-hailing operation settlement systems have rigid rules and poor adaptability, making it difficult to meet the complex business needs of multiple transportation companies, multiple order categories, and multiple usage scenarios. They are also characterized by extensive management, lack of batch operation functions and clear permission divisions, opaque historical change records, and inability to configure differentiated commission rates.
The design incorporates a configurable commission rate-based ride-hailing operation settlement system, including a rule configuration module, a rule engine module, a settlement execution module, and a permission management module. Through multi-dimensional settlement condition configuration and rule matching, it supports flexible adjustment of commission strategies, achieving accurate matching and reasonable profit sharing. The design of both special and general rules ensures the security and controllability of settlement data.
It improves the adaptability and operational efficiency of the settlement system, enables accurate fee sharing in multiple business scenarios, reduces rule conflicts and data errors, supports multi-dimensional condition configuration, simplifies business adjustments and permission management, and enhances operational flexibility and security.
Smart Images
Figure CN121860828A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of vehicle operation management technology, and more specifically, to a ride-hailing operation settlement system based on configurable commission rates. Background Technology
[0002] With the rapid development of the ride-hailing business, its operating model has become increasingly complex, characterized by cooperation among multiple transportation companies, multiple order categories, and multiple usage scenarios. Traditional settlement systems have significant drawbacks: rigid rules, commission rules strongly bound to specific types (hard-coded), complex code development and deployment required for business adjustments, slow response speed, extensive management, lack of batch operation functions and clear permission division, cumbersome and error-prone repetitive rule configuration, opaque historical change records, difficulty in tracing, lack of fine-grained control, inability to configure differentiated commission rates for surcharges, specific channels, etc., and difficulty in meeting the needs of precise operation. Therefore, we propose a ride-hailing operation settlement system based on configurable commission rates. Summary of the Invention
[0003] The purpose of this invention is to overcome the shortcomings of the prior art, adapt to the needs of reality, and provide a ride-hailing operation settlement system based on a configurable commission rate, so as to solve the technical problem of poor adaptability of the current ride-hailing operation settlement system in complex business scenarios.
[0004] To address the aforementioned technical problems, this invention provides the following technical solution: a ride-hailing operation settlement system based on configurable commission rates, comprising a rule configuration module, which provides a user interface and can create rule sets and configure multi-dimensional settlement conditions; a rule engine module, which stores and manages the rule sets created by the rule configuration module and matches corresponding rules based on order characteristics; the rule engine module also includes a matching unit for matching order characteristics to corresponding rules, which performs rule matching based on business dimensions and rule priorities; a settlement execution module, which completes the fee sharing among drivers, transportation companies, and the platform based on the corresponding rules matched by the rule engine module; and a permission management module, which controls the initial threshold data in the rule configuration module, rule engine module, and settlement execution module based on the permissions of transportation companies. The rule set includes several special rules and one general rule, and the several special rules are configured based on specific business scenarios and order characteristics, and are adjusted based on the rule configuration module.
[0005] Preferably, the matching logic of the matching unit is based on business dimension quantification weights and rule priority hierarchies, and its rule matching is based on the following formula:
[0006] in, For the first The overall matching score of the rules, Configure the total number of dimensions for the settlement conditions supported by the system. For the first Business weight coefficients for each configuration dimension For the first Rule number 1 Matching values for each dimension; Based on the above formula, obtain the matching score between the current order and several rules, and then match the corresponding rules based on the score.
[0007] Preferably, the matching unit matches corresponding rules based on a rule-based matching formula. If several rules have the same matching score for the same order, the matching data is filtered and optimized for that rule to obtain the optimal settlement rule. The filtering formula is as follows:
[0008] in The optimal settlement rule for the final hit. This is the set of rules currently in effect. For the first The priority coefficient of the rule, For the first The final ranking score of the rules is determined by the rule with the highest score, which is the optimal rule.
[0009] Preferably, the overall rule matching logic of the rule engine module is to first traverse all special rules for range matching based on the rule matching formula, and then perform precise matching based on the filtering formula. If no special rule is matched, it automatically falls back to the general rule in the corresponding rule set for execution and settlement.
[0010] Preferably, the user interface within the rule configuration module adopts a multi-tab design, specifically including a settlement rule page, an operation record page, and a rule editing page. The configuration items on the rule editing page include the rule name, driver commission rate, transportation company commission rate, platform commission rate, and at least three settlement conditions from order category, vehicle usage scenario, service type, channel, business type, surcharge, and driver commission availability status.
[0011] Preferably, the settlement execution module remotely links with the financial systems of the transportation company and the platform. After the settlement execution module completes the allocation of the order cost, it synchronizes the settlement result to the financial systems of the transportation company and the platform that accepted the order.
[0012] Preferably, the permission management module isolates data based on an organizational model. It generates access zones through permission separation, and users with permissions for that access zone can view and operate the data in that access zone.
[0013] Preferably, the organizational model of the permission management module divides users into levels, including the platform, transportation companies, and drivers, and performs detailed permission adjustments based on these levels, including the platform's adjustment of the status of transportation companies, the transportation companies' adjustment of the status of drivers, and the adjustment of drivers' own data.
[0014] Preferably, the settlement rules page provides entry points for creating new rules, batch associating with transportation companies, and batch editing operations, for batch data operation management by operations personnel. The operation record page records the creation, modification, and activation status change logs of rules and supports viewing rule modification details.
[0015] Preferably, the rule configuration module can adjust the commission strategy according to the ride-hailing business scenario where multiple transportation companies cooperate, multiple order categories, and multiple vehicle usage scenarios coexist, and is based on the user interface operation.
[0016] Compared with the prior art, the beneficial effects of the present invention are: 1. This invention, through the collaborative efforts of a rule configuration module, a rule engine module, a settlement execution module, and a permission management module, coupled with a rule set design that combines special and general rules, supports multi-dimensional settlement condition configuration and flexible adjustment of commission strategies. It can adapt to complex business needs involving multiple transportation companies, multiple order categories, and multiple vehicle usage scenarios without hard coding, resulting in more efficient responses to business adjustments. The matching unit of the rule engine module achieves accurate order rule matching based on business dimensions and rule priorities, ensuring reasonable and compliant fee sharing among drivers, transportation companies, and the platform. Furthermore, the initial threshold data for transportation company permission control ensures the security and controllability of settlement data, effectively solving the problems of rigid rules, inefficient management, and poor adaptability in traditional systems, thereby improving settlement accuracy and operational efficiency.
[0017] 2. This invention also improves settlement accuracy and rule adaptation flexibility through quantitative matching and priority filtering mechanisms using matching units: Based on the matching formula, it supports configuration of multiple settlement dimensions, with dynamically adjustable weight coefficients and three-level matching values. This can accurately adapt to orders in specific scenarios and also meet fuzzy matching requirements. It can respond to business priority adjustments without modifying the core code. Furthermore, based on the filtering formula, it efficiently solves the conflict problem of multiple rules having the same matching score by linking priority coefficients and matching scores, solidifies the priority logic of special rules, avoids the matching chaos of traditional systems, and further ensures the optimal adaptation of settlement rules under different business scenarios, providing technical support for the rationality of fee sharing.
[0018] 3. To prevent situations where the output results based on the matching formula and the filtering formula differ significantly from the general rules, resulting in orders applicable to the general rules still being selected by the special rules, this invention also automatically reverts to the general rules in the corresponding rule set for settlement when the order score output based on the filtering formula is not matched by any special rules or the matched score is lower than that of the general rules. This operation method ensures that when the special rules are matched first, the general rules can be used as a fallback, reducing the occurrence of situations where no vehicle is matched on the user's end due to this situation, which would affect the subsequent commission settlement. Attached Figure Description
[0019] Figure 1 This is a schematic diagram of the module structure of the present invention; Figure 2 A schematic diagram of the user interface of the rule configuration module of the present invention; Figure 3 This is a schematic diagram of the order matching logic flow of the present invention. Detailed Implementation
[0020] like Figures 1 to 3 As shown, the present invention discloses a ride-hailing operation settlement system based on a configurable commission ratio, comprising: a rule configuration module, which provides a user interface and can create rule sets and configure multi-dimensional settlement conditions; a rule engine module, which stores and manages the rule sets created by the rule configuration module and matches corresponding rules based on order features; a matching unit for matching order features to corresponding rules, which performs rule matching based on business dimensions and rule priorities; a settlement execution module, which completes the fee sharing among drivers, transportation companies, and the platform based on the corresponding rules matched by the rule engine module; and a permission management module, which controls the initial threshold data in the rule configuration module, rule engine module, and settlement execution module based on the permissions of transportation companies. The rule set includes several special rules and one general rule, with the special rules configured based on specific business scenarios and order features and adjusted based on the rule configuration module.
[0021] This invention, through the collaborative efforts of a rule configuration module, a rule engine module, a settlement execution module, and a permission management module, coupled with a rule set design that combines special and general rules, supports multi-dimensional settlement condition configuration and flexible adjustment of commission strategies. It adapts to complex business needs involving multiple transportation companies, multiple order categories, and multiple vehicle usage scenarios without hard coding, resulting in more efficient responses to business adjustments. The matching unit of the rule engine module achieves precise matching of order rules based on business dimensions and rule priorities, ensuring reasonable and compliant fee sharing among drivers, transportation companies, and the platform. Furthermore, the initial threshold data for transportation company permission control ensures the security and controllability of settlement data. This effectively solves the problems of rigid rules, inefficient management, and poor adaptability in traditional systems, improving settlement accuracy and operational efficiency.
[0022] Specifically, the matching logic of the matching unit is based on business dimension quantification weights and rule priority hierarchies, and its rule matching is based on the following formula:
[0023] in, For the first The overall matching score of the rules, ranging from 0 to 100. Configure the total number of dimensions for the settlement conditions supported by the system, such as order category, vehicle usage scenario, channel, etc., n≥10. For the first The business weight coefficients for each configuration dimension can be dynamically adjusted based on business priority. For the first Rule number 1 Matching values for each dimension; Based on the above formula, obtain the matching score between the current order and several rules, and then match the corresponding rules based on the score; Weighting coefficient The weight of the business type dimension can be adjusted according to the business strategy. For example, when the platform focuses on promoting corporate car use, the weight of the business type dimension can be increased from 20 to 40 without modifying the core code, thus solving the problem of fixed dimension priority in traditional systems. pass The three-level matching values of 0 / 0.5 / 1 support precise matching, such as matching specific airport orders, and fuzzy matching, such as matching all reservation scenarios, to adapt to complex order features; The system calculates a comprehensive matching score using a matching formula. It supports ≥10 settlement dimensions, and the weight coefficients can be dynamically adjusted according to business priorities. The matching value is divided into three levels to adapt to precise or fuzzy matching needs. It can respond to business adjustments without modifying the core code, solving the problem of fixed dimension priorities in traditional systems.
[0024] More specifically, the matching unit matches corresponding rules based on a rule-based matching formula. If several rules have the same matching score for the same order, the matching data is filtered and optimized for that rule to obtain the optimal settlement rule. The filtering formula is as follows:
[0025] in The optimal settlement rule for the final hit. This is the set of rules currently in effect. For the first The priority coefficient of the rule, For the first The final ranking score of the rules is determined by the rule with the highest score, which is the optimal rule.
[0026] The coefficients solidify the logic of prioritizing special rules through mathematical operations, avoiding the confusion of matching logic in traditional systems and reducing the probability of rule conflicts.
[0027] For scenarios where multiple rules have the same matching score, a filtering formula is provided. By linking the matching score with the priority coefficient, the ranking score is calculated to lock in the optimal settlement rule. The priority coefficient solidifies the priority logic of special rules, effectively avoiding the matching chaos of traditional systems, reducing the probability of rule conflicts, and providing technical support for the accurate settlement of complex orders.
[0028] This invention also improves settlement accuracy and rule adaptation flexibility through quantitative matching and priority filtering mechanisms using matching units: Based on the matching formula, it supports configuration of multiple settlement dimensions, with dynamically adjustable weight coefficients and three-level matching values. This can accurately adapt to orders in specific scenarios and also meet fuzzy matching requirements. It can respond to business priority adjustments without modifying the core code. Furthermore, based on the filtering formula, it efficiently solves the conflict problem of multiple rules having the same matching score by calculating the priority coefficient and matching score together. It solidifies the priority logic of special rules, avoids the matching chaos of traditional systems, and further ensures the optimal adaptation of settlement rules under different business scenarios, providing technical support for the rationality of fee sharing.
[0029] Furthermore, the overall rule matching logic of the rule engine module is to first traverse all special rules for range matching based on the rule matching formula, and then perform precise matching based on the filtering formula. If no special rule is matched, it will automatically fall back to the general rule in the corresponding rule set for execution and settlement.
[0030] If the difference between the highest score output by the filtering formula and the general rule is too large, meaning the default score of the general rule is higher than the score output by the filtering formula, then the fallback matching formula will be executed, as follows:
[0031] in, The final execution rules for order settlement. A special subset of rules in the rule set. The default is the matching threshold. =60, and is configurable, ensuring the validity of matching results. These are general rules within the rule set, serving as a fallback matching option for all scenarios; Matching thresholds can filter out invalid matches, such as rules that only satisfy one low-weight dimension, ensuring a strong correlation between settlement rules and order characteristics, and improving settlement accuracy.
[0032] First, it iterates through the range of special rules for matching, then uses the filtering formula for precise matching. If no special rule is matched, it automatically falls back to the general rule. The tiered logic covers all business scenarios, avoids rule matching omissions, reduces settlement anomalies, and improves the reliability and consistency of system settlement in complex business scenarios.
[0033] To prevent situations where the output results based on the matching formula and filtering formula differ significantly from the general rules, resulting in orders applicable to the general rules still being selected by special rules, this invention also automatically reverts to the general rules in the corresponding rule set for settlement when the order score output based on the filtering formula is not matched by a special rule or the matched score is lower than that of the general rules. This operation method ensures that when the special rule is matched first, the general rules can be used as a fallback, reducing the occurrence of situations where no vehicle is matched on the user's end due to this situation, which would affect the subsequent commission settlement.
[0034] Furthermore, the user interface within the rule configuration module adopts a multi-tab design, specifically including a settlement rule page, an operation record page, and a rule editing page. The configuration items on the rule editing page include the rule name, driver commission rate, transportation company commission rate, platform commission rate, and at least three settlement conditions from order category, vehicle usage scenario, service form, channel, business type, surcharge, and driver commission status. The rules configuration module adopts a multi-tab design, including three pages: settlement rules, operation records, and rule editing. The editing page has rich configuration options, covering third-party commission rates and at least three settlement conditions, supporting fine-grained differentiated configurations to adapt to commission requirements in various scenarios. The operation interface is clear and intuitive, reducing the threshold for rule configuration.
[0035] Furthermore, the settlement execution module remotely links with the financial systems of the transportation company and the platform. After the settlement execution module completes the allocation of the order cost, it synchronizes the settlement result to the financial systems of the transportation company and the platform that accepted the order. The settlement execution module remotely links with the transportation company and the platform's financial system, synchronizing settlement results instantly after cost allocation. No manual secondary data entry is required, achieving seamless integration of settlement and financial data, reducing data errors, improving financial reconciliation efficiency, and ensuring transparency and standardization of cost flows.
[0036] It is worth noting that the permission management module isolates data based on an organizational model. It generates access zones through permission separation, and users with permissions for that access zone can view and operate the data in that access zone. The access control module implements data isolation based on an organizational model. It divides access areas by separating permissions, allowing only authorized users to operate on data in their respective areas. This effectively prevents data leakage and unauthorized operations, ensuring the security of settlement data in multi-entity collaborative scenarios and meeting data management compliance requirements.
[0037] It is worth noting that the organizational model of the permission management module divides users into levels, including the platform, transportation companies, and drivers. Based on this level, detailed permission adjustments are made, including the platform's adjustment of the status of transportation companies, the transportation companies' adjustment of the status of drivers, and the adjustment of drivers' own data. By refining the user level division of the organizational model, the hierarchical permissions of the platform, transportation companies, and drivers are clearly defined, enabling the platform to manage transportation companies, transportation companies to regulate drivers, and drivers to manage their own data. The division of rights and responsibilities is clear, avoiding confusion of permissions and adapting to the management needs of multi-entity collaborative operation in ride-hailing.
[0038] It is worth mentioning that the settlement rules page provides entry points for creating new rules, batch associating them with transportation companies, and batch editing operations, which are used for batch data operation management by operations personnel. The operation log page records the creation, modification, and activation status change logs of rules and supports viewing rule modification details. The settlement rules page provides access to batch associate transportation companies and batch edit, simplifying batch operations for operations personnel; the operation record page retains complete logs of the entire rule lifecycle, supports traceability of modification details, solves the problems of cumbersome repetitive rule configuration and opaque historical records in traditional systems, and improves management efficiency and traceability.
[0039] It is worth noting that the rule configuration module can adjust the commission strategy according to the ride-hailing business scenario where multiple transportation companies cooperate, multiple order categories, and multiple vehicle usage scenarios coexist, and is based on the user interface operation. By enhancing the scenario adaptability of the rule configuration module, the commission strategy can be flexibly adjusted for multiple transportation capacity cooperation, multiple order categories, and multiple vehicle usage scenarios. All operations are completed based on a visual user interface, without the need for hard coding development, enabling rapid response to business changes and meeting the needs of precise operation of ride-hailing services.
[0040] Working Principle: This embodiment provides a ride-hailing operation settlement system based on configurable commission rates. In use, operators create a settlement rule set containing general and special rules according to business needs through the rule configuration module interface. The permission management module achieves data isolation based on an organizational model, ensuring that regional operators can only operate the rules of the corresponding transportation company. When a ride-hailing order from a company in the corresponding region initiates settlement, the settlement execution module calls the rule engine module. The rule engine module compares the order information with the effective rules to match the optimal special rule. That is, it first iterates through the range of special rules using a matching formula, then performs precise matching using a filtering formula. If no special rule is matched, it automatically falls back to the general rules. Then, it automatically completes the three-party cost allocation according to the commission rate set by the selected rule, and synchronizes the results to the financial system. Furthermore, all lifecycle changes, such as rule creation, modification, and activation, are recorded on the operation log page.
[0041] Example: Operations personnel create a set of rules for economy class business in Beijing through the rule configuration module: the general rule is set to 15% for drivers, 5% for transportation companies, and 80% for the platform. An additional special rule is added for airport orders, with the content being 14% for drivers, 5% for transportation companies, and 81% for the platform. A special rule is added for short-distance orders within 3 kilometers, with the content being 16% for drivers, 5% for transportation companies, and 79% for the platform. The access control module restricts the modification of this rule set to only Beijing operations personnel, and Shanghai operations personnel do not have the right to operate it. When an order departing from Beijing Airport is settled, the rules engine compares the order features and matches the special rules for airport orders, allocates the fees according to the corresponding proportion, and synchronizes with the financial system. If a typical Beijing order exceeding 3 kilometers is settled, and no special rules are matched, the general rules will be automatically triggered, and settlement will be based on the general rules. All rule creation and commission rate modification records are saved on the operation log page.
[0042] The embodiments disclosed in this invention are preferred embodiments, but are not limited thereto. Those skilled in the art can easily understand the spirit of this invention based on the above embodiments and make different extensions and variations, but as long as they do not depart from the spirit of this invention, they are all within the protection scope of this invention.
Claims
1. A ride-hailing operation settlement system based on configurable commission rates, characterized in that, include: The rule configuration module provides a user interface and can create rule sets and configure multi-dimensional settlement conditions. The rule engine module is used to store and manage the rule set created by the rule configuration module, and to match corresponding rules based on order features. The rule engine module also includes a matching unit for matching order features with corresponding rules, which performs rule matching on order features based on business dimensions and rule priorities. The settlement execution module, based on the corresponding rules matched by the rule engine module, completes the fee sharing among drivers, transportation companies, and the platform. The permission management module controls the initial threshold data in the rule configuration module, rule engine module, and settlement execution module based on the transportation company's permissions. The rule set includes several special rules and one general rule. The special rules are configured based on specific business scenarios and order characteristics, and are adjusted based on the rule configuration module.
2. The ride-hailing operation settlement system based on configurable commission rates according to claim 1, characterized in that, The matching logic of the matching unit is based on business dimension quantification weights and rule priority hierarchies, and its rule matching is based on the following formula: ； in, For the first The overall matching score of the rules, Configure the total number of dimensions for the settlement conditions supported by the system. For the first Business weight coefficients for each configuration dimension For the first Rule No. Matching values for each dimension; Based on the above formula, obtain the matching score between the current order and several rules, and then match the corresponding rules based on the score.
3. A ride-hailing operation settlement system based on a configurable commission rate according to claim 2, characterized in that, The matching unit matches corresponding rules based on a rule-based matching formula. If several rules have the same matching score for the same order, the matching data is filtered and optimized for that rule to obtain the optimal settlement rule. The filtering formula is as follows: ； in The optimal settlement rule for the final hit. This is the set of rules currently in effect. For the first The priority coefficient of the rule, For the first The final ranking score of the rules is determined by the rule with the highest score, which is the optimal rule.
4. A ride-hailing operation settlement system based on a configurable commission rate according to claim 3, characterized in that, The overall rule matching logic of the rule engine module is to first traverse all special rules for range matching based on the rule matching formula, and then perform precise matching based on the filtering formula. If no special rule is matched, it will automatically fall back to the general rule in the corresponding rule set for execution and settlement.
5. A ride-hailing operation settlement system based on a configurable commission rate according to claim 1, characterized in that, The user interface within the rule configuration module adopts a multi-tab design, specifically including a settlement rule page, an operation record page, and a rule editing page. The configuration items on the rule editing page include the rule name, driver commission rate, transportation company commission rate, platform commission rate, and at least three settlement conditions from the following: order category, vehicle usage scenario, service type, channel, business type, surcharge, and driver commission availability status.
6. A ride-hailing operation settlement system based on configurable commission rates according to claim 1, characterized in that, The settlement execution module remotely links with the internal financial systems of the transportation company and the platform. After the settlement execution module completes the allocation of the order cost, it synchronizes the settlement result to the financial systems of the transportation company and the platform that accepted the order.
7. A ride-hailing operation settlement system based on configurable commission rates according to claim 1, characterized in that, The permission management module isolates data based on an organizational model. It creates access zones through permission separation, and users with permissions for that access zone can view and operate the data in that access zone.
8. A ride-hailing operation settlement system based on a configurable commission rate according to claim 7, characterized in that, The organizational model of the permission management module divides users into levels, including the platform, transportation companies, and drivers. Based on this level, refined permission adjustments are made, including the platform's adjustment of the transportation company's status, the transportation company's adjustment of the driver's status, and the adjustment of the driver's own data. Data isolation is achieved based on the organizational model.
9. A ride-hailing operation settlement system based on a configurable commission rate according to claim 5, characterized in that, The settlement rules page provides entry points for creating new rules, batch associating them with transportation companies, and batch editing operations, which are used for batch data operation management by operations personnel. The operation log page records the creation, modification, and activation status changes of rules and supports viewing rule modification details.
10. A ride-hailing operation settlement system based on a configurable commission rate according to claim 5, characterized in that, The rule configuration module can adjust the commission strategy according to the ride-hailing business scenario where multiple transportation companies cooperate, multiple order categories, and multiple vehicle usage scenarios coexist, and it is based on the user interface operation.