CN113689170A

CN113689170A - Pricing processing method and device for delivery order and computer equipment

Info

Publication number: CN113689170A
Application number: CN202111007335.2A
Authority: CN
Inventors: 商建兵
Original assignee: Rajax Network Technology Co Ltd
Current assignee: Rajax Network Technology Co Ltd
Priority date: 2021-08-30
Filing date: 2021-08-30
Publication date: 2021-11-23

Abstract

The embodiment of the specification provides a pricing processing method and device for delivery orders and computer equipment, the scheme is provided with a pricing rule configuration interface for a user to configure pricing rules, wherein the pricing rules are composed of preconditions and rule factors, the rule factors represent at least one calculation expression required for calculating pricing of delivery orders, the precondition represents the condition that the pricing rule takes effect, and the user can configure a plurality of different pricing rules through the configuration interface, for the calculation expression, preset calculation programs are configured in advance, one preset calculation program can be combined with different parameter values and different preconditions, therefore, a plurality of different pricing rules are combined, and the different pricing rules can reuse the same preset calculation program, so that the development efficiency is obviously improved, and the different pricing rules can be flexibly expanded.

Description

Pricing processing method and device for delivery order and computer equipment

Technical Field

The embodiment of the specification relates to the technical field of internet, in particular to a pricing processing method and device for a delivery order and computer equipment.

Background

The distribution service brings convenience to people's life, at present, more and more service parties are provided for providing distribution service, and for the service parties, when a user inquires the price of the required distribution service, the user needs to be rapidly offered.

Disclosure of Invention

In order to overcome the problems in the related art, embodiments of the present specification provide a pricing processing method and apparatus for delivery orders, and a computer device.

According to a first aspect of embodiments herein, there is provided a pricing processing method for delivery orders, including:

providing a pricing rule configuration interface, wherein a configuration function of a precondition and a configuration function of a rule factor are provided in the configuration interface, and the precondition represents conditions required to be met by adopting the rule factor to perform pricing calculation on a delivery order; the rule factor characterizes at least one computational expression required for calculating the pricing of the delivery order; the configuration function of the rule factor is displayed with a plurality of preset calculation expressions, and each preset calculation expression corresponds to a preset calculation program;

acquiring a precondition configured by a user, required computational expressions in rule factors corresponding to the precondition and calling parameters of each required computational expression through the pricing rule configuration interface, and storing an acquired result as pricing rule data;

if a pricing request carrying order information of a delivery order is received, determining a precondition met by the delivery order by using stored pricing rule data, calling a preset calculation program corresponding to the calculation expression according to a calculation expression corresponding to the met precondition and an input value determined by the order information of the delivery order and the calling parameter, and determining pricing of the delivery order according to an output result of the preset calculation program.

According to a second aspect of embodiments herein, there is provided a pricing processing apparatus of a delivery order, including:

an interface providing module to: providing a pricing rule configuration interface, wherein a configuration function of a precondition and a configuration function of a rule factor are provided in the configuration interface, and the precondition represents conditions required to be met by adopting the rule factor to perform pricing calculation on a delivery order; the rule factor characterizes at least one computational expression required for calculating the pricing of the delivery order; the configuration function of the rule factor is displayed with a plurality of preset calculation expressions, and each preset calculation expression corresponds to a preset calculation program;

a storage module to: acquiring a precondition configured by a user, required computational expressions in rule factors corresponding to the precondition and calling parameters of each required computational expression through the pricing rule configuration interface, and storing an acquired result as pricing rule data;

a calculation module to: if a pricing request carrying order information of a delivery order is received, determining a precondition met by the delivery order by using stored pricing rule data, calling a preset calculation program corresponding to the calculation expression according to a calculation expression corresponding to the met precondition and an input value determined by the order information of the delivery order and the calling parameter, and determining pricing of the delivery order according to an output result of the preset calculation program.

According to a third aspect of embodiments herein, there is provided a computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the method for pricing a delivery order of the first aspect when executing the program.

The technical scheme provided by the embodiment of the specification can have the following beneficial effects:

in the embodiment of the specification, a pricing rule configuration interface is provided for a user to configure pricing rules, each pricing rule is composed of a precondition and a rule factor, each rule factor represents at least one calculation expression required for calculating pricing of a delivery order, each precondition represents a condition required to be met by the delivery order by adopting the rule factor to calculate the price, namely the condition required to be met by the rule factor to take effect, based on the condition, the user can configure a plurality of different pricing rules through the configuration interface, a preset calculation program is pre-configured for the calculation expressions, based on the configuration of different pricing rules, different parameter values and different preconditions can be provided, one preset calculation program can be combined with different parameter values and different preconditions, so that a plurality of different pricing rules are combined, and in the different pricing rules, the same preset calculation program is reused, so that the development efficiency is obviously improved, and different pricing rules can be flexibly expanded; after the configuration of the pricing rules by the user is received through the configuration interface, the pricing rules can be stored as pricing rule data, and based on the pricing rule data, the pricing of the delivery order can be calculated by using the pricing rule data after a price quote request carrying order information of the delivery order is received.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the specification.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present specification and together with the description, serve to explain the principles of the specification.

FIG. 1 is a flow chart illustrating a method for pricing a delivery order according to an exemplary embodiment of the present description.

FIG. 2A is a schematic diagram of a pricing rule configuration interface shown in the present specification according to an exemplary embodiment.

FIG. 2B is a schematic diagram of a pricing model shown herein according to an exemplary embodiment.

FIG. 2C is a schematic diagram of a pricing process, shown herein according to an exemplary embodiment.

Fig. 3 is a hardware configuration diagram of a computer device in which a pricing processing device for order delivery according to the present description is located.

FIG. 4 is a block diagram illustrating another delivery order pricing processing arrangement according to an exemplary embodiment of the present description.

Detailed Description

Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present specification. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the specification, as detailed in the appended claims.

The terminology used in the description herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the description. As used in this specification and the appended claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.

It should be understood that although the terms first, second, third, etc. may be used herein to describe various information, these information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, the first information may also be referred to as second information, and similarly, the second information may also be referred to as first information, without departing from the scope of the present specification. The word "if" as used herein may be interpreted as "at … …" or "when … …" or "in response to a determination", depending on the context.

In actual business, pricing of delivery orders may be affected by many factors, and different pricing strategies may be applied to different users based on different factors such as types of users, locations, types of items in delivery orders, weights of items, delivery distances, and the like. Based on this, the business side can be configured with pricing service, and can inquire out a matched pricing strategy and calculate the price quoted for the delivery order according to the order information of the delivery order of the user. Because there may be many pricing strategies, and because of the operation needs, the pricing strategies are also changed frequently, how to implement flexible expansion of the pricing scheme for delivering orders becomes a technical problem to be solved urgently.

As shown in fig. 1, fig. 1 is a flowchart of a pricing processing method for delivery orders according to an exemplary embodiment, including the following steps:

in step 102, providing a pricing rule configuration interface, wherein the configuration interface is provided with a configuration function of preconditions and a configuration function of rule factors, and the preconditions represent conditions which need to be met when a delivery order is priced and calculated by adopting the rule factors; the rule factor characterizes at least one computational expression required for calculating the pricing of the delivery order; the configuration function of the rule factor shows a plurality of preset calculation expressions, and each preset calculation expression corresponds to a preset calculation program.

In step 104, the preset condition configured by the user, the required computational expressions in the rule factors corresponding to the preset condition, and the calling parameters of each required computational expression are obtained through the pricing rule configuration interface, and the obtained result is stored as pricing rule data.

In step 106, if a pricing request carrying order information of a delivery order is received, a precondition that the delivery order meets is determined by using stored pricing rule data, a preset calculation program corresponding to the calculation expression is called according to the calculation expression corresponding to the met precondition and an input value determined by the order information of the delivery order and the calling parameter, and pricing of the delivery order is determined according to an output result of the preset calculation program.

The scheme of the embodiment of the description can be applied to a distribution scene, in the distribution service scene, a service side provides a distribution service for a user, if the user needs the distribution service of the service side, the user can send a request to the service side, and the service side can give out distribution pricing of a distribution order according to the distribution order of the user. Alternatively, the customer's delivery order may require reimbursement from the business party for a variety of issues, and the business party may be required to price the reimbursement for the delivery order. Or, after the delivery order of the user is placed, the delivery order needs to be cancelled for various reasons, and the business side needs to give pricing for cancelling the delivery order. Or, the delivery order of the user can also be insured, namely insurance purchased for the delivery order, and therefore, the business side can also price the insured delivery order according to the needs of the user. Of course, other pricing types can be flexibly configured according to needs in actual services.

In this embodiment, the pricing can be flexibly configured according to actual needs, for example, it can be an asset, and the asset can refer to an asset of business or exchange value, including but not limited to: monetary funds, virtual funds (e.g., virtual money, digital tickets, digital shares, virtual gifts, coupons, red packs or credits, etc. issued by a business or other entity) or credits (credit, which refers to a mutually trusted production and social relationship formed between people, between entities, and between transactions for goods, and can be a transaction tool), etc.

In actual business, the pricing of the delivery order is influenced by various factors, and the delivery order adopts different pricing strategies under different conditions; based on this, the pricing rule of this embodiment is composed of a precondition and a rule factor, where the rule factor represents at least one calculation expression required for calculating the price of the delivery order, and the precondition represents a condition that the delivery order needs to be satisfied by adopting the rule factor to perform price calculation, that is, a condition that the rule factor needs to be satisfied for taking effect, that is, a condition that the delivery order capable of adopting the rule factor to perform price calculation needs to be satisfied; for example, if a certain delivery order satisfies the precondition, it indicates that the certain delivery order hits the pricing rule, and the price of the delivery order can be calculated by using the rule factor corresponding to the precondition. In one pricing rule, there is one or more rule factors corresponding to the preconditions, and in the case of multiple rules, the pricing rule may further include a summary relationship of the multiple rule factors.

Wherein the rule factor characterizes at least one calculation expression required for calculating the price of the delivery order, a calculation expression describes the calculation way of pricing under certain constraints (conditions), that is, the calculation expression characterizes: a pricing target calculation mode under target constraint, wherein the preset calculation program comprises a subprogram corresponding to the target constraint and a subprogram corresponding to the target calculation mode; the target constraint includes any one of: a plurality of atomic constraints, a composite constraint in which any two or more of said atomic constraints are combined using logical operators.

By way of example, for "within a range of 3 to 10 kilometers in order distance, charge 1.5 dollars per 2 kilometers", wherein, the '1.5 yuan per 2 km charge' includes the constraint of the calculation mode 'x yuan per m km charge', the 'range of 3 to 10 km in order distance', namely the calculation mode 'x yuan per m km charge', and aiming at the 'x yuan per m km charge', a calculation program can be constructed in advance, i.e., to construct a "x-ary per m kilometers" calculation logic, such as f (x) m x, wherein f (x) is the settlement result output by the program, m is the kilometer value, x is the price per kilometer, it can be understood that, the calculation procedure requires the use of input parameters m and x, the input value of input parameter x being "1.5", the value of m being determined in combination with the delivery distance in the actual delivery order and "2 km".

Therefore, the embodiment decomposes the calculation expression into the target constraint and the target calculation mode, so that the expansion of the expression can be realized more flexibly, and different calculation expressions can be combined by different target constraints and different target calculation modes.

In some examples, the atomic constraint refers to an indivisible minimum constraint unit, including any one of: equivalence constraints, containment constraints, interval constraints, or intersection constraints;

the equivalence constraint is as follows: constraint that order information of the delivery order is equal to the calling parameter; as an example, an equivalence constraint may be a constraint that configures an expression with an item to be a particular value, such as the order type of a delivery order being a reservation order.

The inclusion constraint refers to: constraint that order information of the delivery order is contained in the call parameter; as an example, an inclusion constraint may configure a constraint that an item is included within certain specific values (e.g., a1, a2, a3..) such as the order information for a delivery order includes current weather condition information that is included in one of (slightly severe, severely severe, extremely severe), or in other words (slightly severe, severely severe, extremely severe) includes current weather condition information.

The interval constraint is that: constraint of the order information of the delivery order in an interval formed by the calling parameters; as an example, the interval constraint may configure a certain item in the interval from to, such as the order price for the delivery order being in the range of (100, 200).

The intersection constraint is that: constraint of intersection of the order information of the delivery order and the interval formed by the calling parameters; as an example, the intersection constraint may be

Wherein the content of the first and second substances,

is the meaning of an empty set; such as the disposition distance plus [0, 3 ]]Kilometer, plus 2 pieces, [3, 5 ]]Kilometer plus 3 blocks; if the order distance in the order information of the delivery order is 6 kilometers, the order is connected with [0, 3 ] according to the intersection constraint]And [3, 5 ]]Both intervals intersect.

Because the atomic constraint refers to an inseparable minimum constraint unit, a plurality of composite constraints can be combined based on the atomic constraint, the composite constraint refers to a constraint formed by combining a plurality of atomic constraints through different logical operators, and the logical operator can be any one of Boolean operators. By way of example, assuming A, B, C and D are atom constraints, one possible composite constraint is (NOT A OR B) AND (C OR D).

The foregoing example shows only one computational expression, and multiple computational expressions may be involved at a rule factor, for example:

charging 5 yuan below 3 kilometers in the order;

secondly, charging 1.5 yuan per 2 kilometers within the range of 3 to 10 kilometers in the order distance;

and thirdly, charging 3 yuan per 2 kilometers when the distance of the order is more than 10 kilometers.

The above price calculation with distance involves 3 calculation expressions, where:

the expression (r) can be understood as a calculation expression representing a fixed price, where the constraint to be satisfied is "3 km or less in order distance", and the calculation program is used to calculate the fixed price, and may be f (x) ═ n, and the input value of the parameter n is 5.

The expression (c) may be understood as an expression representing step-length pricing, where the constraint to be satisfied in the expression is "within a range of 3 to 10 kilometers in order distance", and the calculation program refers to a calculation program for increasing the set price according to the set step length, where the calculation program may be f (x) ═ m × x, the input value of the parameter x is "1.5", and the value of m needs to be determined by combining "2 kilometers" and the delivery distance in the actual delivery order.

Expression c can also be understood as an expression representing step-length pricing, where the constraint to be satisfied is "10 km or more in order distance", and the calculation program is a calculation program for increasing the set price according to the set step length, where the calculation program may be f (x) ═ m × x, the input value of the parameter x is "3", and the value of m needs to be determined by combining "10 km" and the delivery distance in the actual delivery order.

From the above example, although the expressions (c) and (c) are different, the same calculation program can be used because the calculation logics are similar, and only the parameter input values used when the calculation program is called are different. Therefore, one calculation program can be multiplexed into a plurality of expressions, so that the development cost can be reduced remarkably.

In other examples, the expression may also be: and f, (x) a1+ a2+ a3., wherein the expression represents the accumulated composite pricing, namely the pricing result is obtained by accumulating a plurality of asset information a1, a2, a3 and the like. By way of example, taking claim pricing as an example, in some scenarios, the merchant requests claim pricing for delivery orders due to rider false deliveries, and pays a fixed amount of money, such as 5 dollars, for delivery fees paid by the merchant, since the merchant places an order and pays delivery fees for the delivery orders, and thus accumulates the fixed amount of the claim and the delivery fees paid by the merchant.

In other examples, the expression may also be an expression representing a pay pricing for the delivery order, for example, if the order is timed out for more than 10 minutes to pay the merchant a coupon.

In other examples, the expression may also be an expression representing a quote price, and as an example, the merchant applies for a 200-dollar claim for the delivery order, but the upper limit is limited to 100 in the pricing rules, so the expression may be f (x) min (the amount of the quote merchant applying for the claim, 100).

Based on this, in this embodiment, a plurality of different preset calculation programs may be preconfigured, a specific calculation program may be flexibly configured as needed, and according to the actual pricing rule needs, one preset calculation program may be used by a plurality of different expressions, for example, different parameter values and different preconditions may be combined with one preset calculation program to combine a plurality of different pricing rules, but in these different pricing rules, the same preset calculation program is multiplexed, and only different parameter values and preconditions need to be adopted, thereby significantly reducing the development difficulty. Wherein one of the preset computing programs may be used for a plurality of different pricing rules to call.

Based on this, in the solution of the embodiment of the present specification, a pricing rule configuration interface is provided for a user to configure a pricing rule, where the user may include a user having a configuration right for the pricing rule on a business side, such as an operator on the business side, or a developer of the pricing solution of the embodiment.

In some examples, the configuration function for the preconditions may specifically be an editing function of the preconditions, such that the user can edit the preconditions through the editing function.

In other examples, the configuration function of the preconditions may specifically be a selection function of the preconditions, for example, multiple preset preconditions may be configured in advance and displayed, and a user may select the required preconditions as needed. Based on the preset precondition, a plurality of preset preconditions can be determined in advance, for example, a plurality of historical pricing rules can be analyzed, and historical conditions related to each historical pricing rule can be analyzed to determine. Alternatively, the current pricing policy requirements may be obtained in advance and configured. The type of the preset preconditions may be determined by order type, delivery service type or geographical location, as examples, and the preconditions may include the following: any of an order channel, an order source, a base good, or a city rating.

The order channel represents a channel from which a delivery order is initiated, that is, a channel through which a user initiates a delivery order, such as an applet or an APP, different order channels may have different pricing strategies, and thus the order channel may be one of preset preconditions.

In practical applications, a service side may provide a plurality of different service platforms, such as a take-out platform, an online shopping platform, and the like, and different order channels may have different pricing strategies, so that the order channel may serve as one of the preset preconditions.

The base commodity characterizes the types of different delivery services provided by the business parties, such as crowd-sourced products, instant delivery products, college delivery products, and the like. Different commodities may have different pricing strategies and therefore the base commodity may be one of the preconditions.

The city grade represents the grade of the city where the user is located, different cities may have different pricing strategies, and therefore the city grade can be used as one of the preconditions.

The configuration interface in this embodiment provides a configuration function of a rule factor, and the configuration function of the rule factor may display a plurality of preset calculation expressions, so that a user may select a desired calculation expression. The rule factor characterizes at least one computational expression required to compute the price of the delivery order, and optionally, a plurality of rule factors may be prepared in advance using existing historical pricing rules, including, for example, one or more of: distance pricing, weight pricing, time period pricing, temporary pricing, etc.

As shown in fig. 2A, a schematic diagram of a pricing rule configuration interface is shown, as an example, the pricing rule configuration interface of a certain city is shown in the configuration interface, wherein a configuration function of preconditions is shown, and for example, for a channel source, a base commodity and an order type, a user can configure conditions of the channel source, the base commodity and the order type to which the pricing rule applies.

The configuration interface further shows a configuration function of the rule factor, for example, the related rule factor includes rules such as distance pricing, weight pricing, time interval pricing, temporary pricing, passenger order pricing, and the like, each rule factor includes at least one expression, such as the distance pricing rule factor shown in fig. 2A, as described in the foregoing embodiment, for the distance pricing rule factor, two preset calculation expressions are displayed in the configuration interface, and a user can select a calculation expression required to be calculated in the rule factor, as shown in fig. 2A, the configuration interface provides the configuration function to the user in a check box manner, and the user can select the calculation expression required by the rule factor through the check box.

Also, a configuration function of the call parameter for each calculation expression is provided, as shown in fig. 2A, which may specifically be an editing function of the adjustment parameter, and the user may input a parameter value of the adjustment parameter through the editing function, for example, in "□ yuan is added for every □ km" in fig. 2A, the user edits to "1 yuan is added for every 3 km".

Based on this, the preset condition configured by the user, the required computational expressions in the rule factors corresponding to the preset condition, and the calling parameters of each required computational expression can be obtained through the pricing rule configuration interface, and the obtained result is stored as pricing rule data. Through the record of the pricing rule data, if a price quotation request of a delivery order is received, price quotation can be quickly provided for a requester. The requestor in this embodiment refers to a party that has a need for the delivery service of the business party. As an example, the price quote request carries order information of a delivery order, the order information of this embodiment refers to information related to the delivery order and required for calculating price quote, and in practical application, the order information required to be carried in the price quote request may be flexibly configured according to the requirement of a pricing rule. By way of example, the order information may include information about the requestor, information about items to be delivered in the delivery order, information about the delivery address, and the like.

Because the pricing rule data records a precondition, a calculation expression required in a rule factor corresponding to the precondition, and a calling parameter of each required calculation expression, the calculation expression corresponding to the determined satisfied precondition can be obtained after the precondition satisfied by the delivery order is determined from the stored pricing rule data through order information, further, the calculation expression corresponds to a preset calculation program, an input value of the program needs to be determined when the preset calculation program is called, the input value is determined through the order information of the delivery order and an input value determined by the calling parameter, based on the input value, the preset calculation program performs calculation by using the input value, and the offer of the delivery order is determined according to an output result of the preset calculation program.

In some examples, the rule factors also characterize a number of computational expressions and summary relationships required to compute the price of a delivery order; the determining the price quote of the delivery order according to the output result of the preset calculation program includes: and summarizing the quoted prices of the delivery orders according to the summarizing relationship according to the output results of the preset calculation programs.

As an example, taking the expression (i) to the expression (iii) as an example, the rule factor in the pricing rule relates to the 3 expressions, and the rule factor represents 3 calculation expressions and summary relations required for the price of the delivery order; if the delivery distance of the delivery order is 12 kilometers, the results of each calculation expression (calculated and output by the calculation program of each calculation expression) are respectively calculated according to the 3 calculation expressions and then summarized, and the quoted price of the delivery order can be obtained.

FIG. 2B is a schematic diagram of a pricing model shown herein according to an exemplary embodiment; taking the distribution scenario as an example, the pricing rules of this embodiment may optionally be classified based on actual service needs, for example, the classification may be divided into four categories, i.e., an insurance rule, a cancellation rule, a distribution rule, and a reimbursement rule, and in actual application, the rules may be flexibly configured as needed.

Different types of pricing rules may have different scope of action that describes which scope the pricing rules act on, through which the speed of querying the pricing rules may also be increased, e.g. one pricing rule may act in the scope of beijing, shanghai, guangzhou of brand a linked store, brand B linked store. By way of example, the scope of action may include an action object and an action area, and the action object may include a merchant, a merchant type, a store, and the like; the action area comprises city grade templates, cities, trade circles or grids and the like.

In this embodiment, a rule factor (i.e., the pricing factor in fig. 2B) is also included in the pricing rule, and the rule factor represents a factor that affects the price in the pricing rule, such as a weight price or a time period price. By way of example, the weight-added price factor, the distance-added price factor, the claim payment factor, the complaint payment factor, the age payment factor, the charge cancellation factor, etc. may be included, and in practical applications, the configuration may be flexible as required. Wherein, a plurality of rule factors of the same type can exist in one pricing rule, and the final pricing is summarized by the calculation results of the rule factors. These rule factors of the same type may be distinguished by preconditions, which characterize the conditions that the delivery order needs to satisfy for price calculation using the rule factors, i.e., determine whether the rule factors are used for calculation in the price inquiry process. As an example, preconditions may include: the order channel, the order source, the basic commodities and the city grade can be flexibly configured according to the requirement in practical application.

In this embodiment, the rule factor represents at least one calculation expression required for calculating the price of the delivery order, and optionally, a plurality of preset calculation expressions may be preconfigured in the rule factor, where each preset calculation expression corresponds to a preset calculation program.

The computational expression describes the way in which the price is computed under certain constraints (conditions). As an example, the constraints of a computational expression (i.e., the assertions in FIG. 2B) can include atomic constraints (assertions) and compound constraints (assertions). Optionally, the atomic assertions may include equivalence assertions, interval assertions, inclusion assertions, intersection assertions, and the like; the composite assertion can comprise an aging claim assertion, a fee canceling assertion or a pressure balancing assertion, and can be flexibly configured according to needs in practical application.

The expression in this embodiment further includes a price definition, which may also be referred to as a price policy, that is, the calculation manner in the foregoing description; for example, in the foregoing example, "x dollars per m kilometer" is defined as a price for one step size, and other price definitions can be defined as a fixed price, a price paid by the amount of the claim applied by the merchant, and the like. Optionally, the price definition may include two types, that is, an atomic price definition and a composite price definition, where the atomic price definition may include multiple calculation expressions such as a fixed price, a step price, a quoted price, or a coupon-based price, and the composite price definition may include a calculation expression of an accumulated composite price, and each calculation expression may be implemented in advance with a calculation logic, that is, a preset calculation program.

With the above-described processing, the quotation can be made quickly. As an example, as shown in fig. 2C, another pricing processing diagram shown in an embodiment of this specification is that, if a price quote request carrying order information of a delivery order is received, a precondition that the delivery order meets may be determined by using stored pricing rule data, rule factors are calculated after being sorted according to priorities of the conditions in the precondition, the calculated rule factors are determined to meet the precondition by the precondition, calculation expressions are sequentially executed based on the rule factors, the executed calculation expressions are expressions that are predicated successfully, calculation results of the expressions are summarized into results of the rule factors according to price definition calculation results, and results of the rule factors are summarized into a final price quote result by traversing all the calculation expressions to obtain a final price quote.

Therefore, the embodiment designs a set of pricing model which is relatively perfect, high in expansibility, flexible and universal, so that the price calculating process of the distribution order is clear and easy to understand, and the subsequent development and maintenance cost is reduced on the basis of meeting the service requirement. The model has better expansibility and flexibility, if a new rule factor is supported, only the new rule factor and the new expression are needed to be realized, and because the rule factor and the expression encapsulate corresponding calculation logics, the main body price calculation logic does not need to be changed; after the assertion and the price definition are abstracted, in most cases, based on the existing atomic implementation, different atomic assertions and price definitions are combined into a new expression so as to meet the new business requirements, and even if the existing assertion or price definition cannot meet the new business, the new atomic assertions and price definitions can be expanded to implement the new atomic assertions and price definitions. If the expression assertions or price definitions to be defined are indeed complex and special, new composite assertions/price definitions can still be implemented to meet the differentiation requirements. Because the model expression transport capacity pricing rich domain knowledge such as pricing factors, action ranges, expressions, assertions, price definitions, preconditions and the like is abstracted, although the model expression transport capacity pricing rich domain knowledge has various pricing rules of different types, the model is isomorphic, and the price calculation engine does not need to be realized in multiple sets and is simple and efficient. The models related to the pricing factors encapsulate respective computing logic, and all the models can be flexibly expanded and rapidly support business development.

The pricing rule data may be stored in a database, that is, the configuration of the user is acquired through a configuration interface, and the acquired result is stored in the database as the pricing rule data. After the pricing request is obtained, the required pricing rule can be searched from the pricing rule data stored in the database. In other examples, in order to process the quote more quickly, it is optional that a part of the pricing rule data in the database is stored in the cache; the cache is a temporary switch between the CPU and the memory, and the read-write speed of the cache is high, and in this embodiment, at least part of pricing rule data in the database is stored in the cache, so when the stored pricing rule data is needed to determine the precondition that the delivery order meets, whether pricing rule data recording the precondition that the delivery order meets is found from each piece of pricing rule data stored in the cache, and if the pricing rule data can be found, the pricing rule of the delivery order that requires pricing can be quickly obtained from the cache to perform price calculation. If not, the pricing rule data recording the precondition met by the delivery order can be searched from the database.

In some examples, the pricing rule data stored in the cache may be obtained from a database, and the pricing rule data stored in the cache may be all or part of the pricing rule data stored in the database; optionally, in order to ensure the storage performance of the cache, after the pricing rule data recording the precondition that the delivery order meets is searched in the database, the searched pricing rule data is written into the cache, that is, if the pricing rule data is not required by the pricing request after being stored, the pricing rule data is stored in the database, and if the pricing rule data is required by the pricing request, because the data is not stored in the cache, the data needs to be searched and read from the database, and in this embodiment, the data is written into the cache at the same time, so that the storage efficiency of the storage can be improved.

It can be seen from the above embodiments that, in the solution of the embodiment of the present specification, a pricing rule configuration interface is provided for a user to configure pricing rules, where a pricing rule is composed of preconditions and rule factors, where the rule factors represent at least one calculation expression required for calculating the price of a delivery order, and the preconditions represent conditions that the delivery order needs to satisfy for calculating the price by using the rule factors, that is, conditions that the rule factors need to satisfy when the rule factors take effect, based on which, the user can configure a plurality of different pricing rules through the configuration interface, for the calculation expressions, preset calculation programs are preconfigured, based on which, the configurations of different pricing rules will have different parameter values and different preconditions, and one preset calculation program can be combined with different parameter values and different preconditions to combine a plurality of different pricing rules, in the different pricing rules, the same preset calculation program is reused, so that the development efficiency is obviously improved, and different pricing rules can be flexibly expanded; on the basis of meeting the service requirement, the subsequent development and maintenance cost can be reduced. After the configuration of the pricing rule by the user is received through the configuration interface, the pricing rule data can be stored, and based on the data, after a quotation request carrying the order information of the delivery order is received, the quotation of the delivery order can be calculated by using the pricing rule data.

By utilizing the scheme, on the basis of the existing rule factors, if new rule factors need to be supported, only new rule factors and expressions need to be realized, and because the rule factors and the expressions encapsulate corresponding computational logics, the main body computational logic does not need to be changed; for the computational expression, because the constraint and the computational mode are abstracted from the computational expression, a preset computational program is realized for the computational mode, and different constraint and preset computational programs can be combined into a new computational expression to meet new service requirements. Even if the existing constraint and calculation mode can not meet the new service, the new constraint and calculation mode can be expanded to be realized, and if the new pricing rule is complex and special, the new expression can be quickly expanded to meet the differentiation requirement by the abstraction of the calculation expression.

Corresponding to the embodiment of the pricing processing method of the delivery order, the specification also provides an embodiment of a pricing processing device of the delivery order and a computer device applied to the pricing processing device.

The embodiment of the pricing processing device for order delivery in the specification can be applied to computer equipment, such as a server or terminal equipment. The device embodiments may be implemented by software, or by hardware, or by a combination of hardware and software. The software implementation is taken as an example, and as a logical device, the device is formed by reading corresponding computer program instructions in the nonvolatile memory into the memory for operation through the processor in which the file processing is located. From a hardware aspect, as shown in fig. 3, a hardware structure diagram of a computer device where a pricing processing device for order delivery is located in the present specification is shown, except for the processor 310, the memory 330, the network interface 320, and the nonvolatile memory 340 shown in fig. 3, in an embodiment, a computer device where a pricing processing device 331 for order delivery is located may also include other hardware according to an actual function of the computer device, which is not described again.

As shown in fig. 4, fig. 4 is a block diagram of a pricing processing device for delivery orders shown in the present specification according to an exemplary embodiment, the device comprising:

an interface providing module 41 for: providing a pricing rule configuration interface, wherein a configuration function of a precondition and a configuration function of a rule factor are provided in the configuration interface, and the precondition represents conditions required to be met by adopting the rule factor to calculate the price of a delivery order; the rule factor characterizes at least one computational expression required to compute a price for a delivery order; the configuration function of the rule factor is displayed with a plurality of preset calculation expressions, and each preset calculation expression corresponds to a preset calculation program;

a storage module 42 for: acquiring a precondition configured by a user, required computational expressions in rule factors corresponding to the precondition and calling parameters of each required computational expression through the pricing rule configuration interface, and storing an acquired result as pricing rule data;

a calculation module 43 for: if a quotation request carrying order information of a delivery order is received, determining a precondition met by the delivery order by using stored pricing rule data, calling a preset calculation program corresponding to the calculation expression according to a calculation expression corresponding to the met precondition and an input value determined by the order information of the delivery order and the calling parameter, and determining the quotation of the delivery order according to an output result of the preset calculation program.

In some examples, the rule factors characterize a plurality of computational expressions and summary relationships required to compute the price of a delivery order;

the computing module is further configured to: and summarizing the quoted prices of the delivery orders according to the summarizing relationship according to the output results of the preset calculation programs.

In some examples, the storage module is further configured to: storing the obtained result in a database as pricing rule data; part of pricing rule data in the database is stored in a cache;

the computing module is further configured to:

searching whether pricing rule data recording a precondition met by the delivery order exist in each piece of pricing rule data stored in the cache;

and if the preset condition is not found from the cache, searching pricing rule data recording the preset condition met by the delivery order from the database.

In some examples, the computing module is further to: and after searching and recording pricing rule data of the precondition met by the delivery order from the database, writing the searched pricing rule data into the cache.

In some examples, the computational expression characterizes: a pricing target calculation mode under target constraint, wherein the preset calculation program comprises a subprogram corresponding to the target constraint and a subprogram corresponding to the target calculation mode; the target constraints include: any one of a plurality of atomic constraints, or a composite constraint in which any two or more of the atomic constraints are combined using logical operators.

In some examples, the atomic constraints include any one of:

equivalence constraints, containment constraints, interval constraints, or intersection constraints;

the equivalence constraint is as follows: constraint that order information of the delivery order is equal to the calling parameter;

the inclusion constraint refers to: constraint that order information of the delivery order is contained in the call parameter;

the interval constraint is that: constraint of the order information of the delivery order in an interval formed by the calling parameters;

the intersection constraint is that: and (4) constraint that the order information of the delivery order is intersected with the interval formed by the calling parameters.

Accordingly, the present specification also provides a computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements an embodiment of the pricing processing method for the aforementioned delivery orders when executing the program.

The implementation process of the function and the action of each module in the pricing processing device for the delivery order is specifically detailed in the implementation process of the corresponding step in the pricing processing method for the delivery order, and is not described herein again.

For the device embodiments, since they substantially correspond to the method embodiments, reference may be made to the partial description of the method embodiments for relevant points. The above-described embodiments of the apparatus are merely illustrative, wherein the modules described as separate parts may or may not be physically separate, and the parts displayed as modules may or may not be physical modules, may be located in one place, or may be distributed on a plurality of network modules. Some or all of the modules can be selected according to actual needs to achieve the purpose of the solution in the specification. One of ordinary skill in the art can understand and implement it without inventive effort.

The foregoing description has been directed to specific embodiments of this disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.

The steps of the above methods are divided for clarity, and the implementation may be combined into one step or split some steps, and the steps are divided into multiple steps, so long as the same logical relationship is included, which are all within the protection scope of the present patent; it is within the scope of the patent to add insignificant modifications to the algorithms or processes or to introduce insignificant design changes to the core design without changing the algorithms or processes.

Other embodiments of the present description will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This specification is intended to cover any variations, uses, or adaptations of the specification following, in general, the principles of the specification and including such departures from the present disclosure as come within known or customary practice within the art to which the specification pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the specification being indicated by the following claims.

It will be understood that the present description is not limited to the precise arrangements described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present description is limited only by the appended claims.

The above description is only a preferred embodiment of the present disclosure, and should not be taken as limiting the present disclosure, and any modifications, equivalents, improvements, etc. made within the spirit and principle of the present disclosure should be included in the scope of the present disclosure.

Claims

1. A method of pricing a delivery order, comprising:

2. The method of claim 1, said rule factors characterizing a plurality of computational expressions and summary relationships required to compute prices for delivery orders;

the determining pricing of the delivery order according to the output result of the preset calculation program includes:

and summarizing the pricing of the distribution order according to the summarizing relationship according to the output result of each preset calculation program.

3. The method of claim 1, the storing of the obtained results as pricing rule data, comprising: storing the obtained result in a database as pricing rule data; part of pricing rule data in the database is stored in a cache;

the determining the precondition satisfied by the delivery order using the stored pricing rule data comprises:

4. The method of claim 3, after searching the database for pricing rule data that records preconditions satisfied by the delivery order, further comprising:

and writing the searched pricing rule data into the cache.

5. The method of claim 1, the computational expression characterizing: a pricing target calculation mode under target constraint, wherein the preset calculation program comprises a subprogram corresponding to the target constraint and a subprogram corresponding to the target calculation mode; the target constraints include: any one of a plurality of atomic constraints, or a composite constraint in which any two or more of the atomic constraints are combined using logical operators.

6. The method of claim 5, the atomic constraints comprising any one of:

7. A pricing processing apparatus of delivery orders, comprising:

a calculation module to: if a quotation request carrying order information of a delivery order is received, determining a precondition met by the delivery order by using stored pricing rule data, calling a preset calculation program corresponding to the calculation expression according to a calculation expression corresponding to the met precondition and an input value determined by the order information of the delivery order and the calling parameter, and determining pricing of the delivery order according to an output result of the preset calculation program.

8. The apparatus of claim 7, said rule factors characterizing a plurality of computational expressions and summary relationships required to compute prices for delivery orders;

the computing module is further configured to:

and summarizing the quoted prices of the delivery orders according to the summarizing relationship according to the output results of the preset calculation programs.

9. The apparatus of claim 7, the computational expression characterizing: a pricing target calculation mode under target constraint, wherein the preset calculation program comprises a subprogram corresponding to the target constraint and a subprogram corresponding to the target calculation mode; the target constraints include: any one of a plurality of atomic constraints, or a composite constraint in which any two or more of the atomic constraints are combined using logical operators.

10. The apparatus of claim 9, the atomic constraints comprising any one of:

11. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the method of any of claims 1 to 6 when executing the program.