Method and device for generating business order data
By pre-setting authentication algorithms and generating business order data in third-party service platforms, the problem of insufficient load pressure and concurrency capabilities caused by frequent interaction between third-party service platforms and business party systems in traditional technology is solved, and concurrency capabilities and users are improved Experience.
Patent Information
- Application Number
- CN202110251111.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2016-12-19
- Publication Date
- 2024-11-01
- Estimated Expiration
- 2036-12-19
AI Technical Summary
In traditional technology, third-party service platforms need to frequently interact with the business party system when processing business requests, resulting in large load pressure on the business party system and limited concurrency capabilities, affecting the user experience.
By presetting the authentication algorithm corresponding to the business object in the third-party service platform, users are directly authenticated and business order data is generated after the payment operation is completed, reducing real-time interaction with the business party system and improving concurrency capabilities.
It effectively reduces the load pressure of the business party system, improves the concurrency capability of the third-party service platform, improves the user experience, and reduces the interaction frequency of the business party system.
Smart Images

Figure CN112927090B_ABST
Abstract
Description
[0001] This application is a divisional application of the invention patent application with application number 201611178175.7 filed on December 19, 2016 and entitled “Method and Device for Generating Business Order Data”. Technical Field
[0002] The present application relates to the field of computer technology, and in particular to a method and device for generating business order data. Background Art
[0003] In traditional technology, in the process of implementing a business, the user will first send a request to the third-party service platform. After receiving the request, the third-party service platform will forward it to the business system in real time, so that the business system will process the user's request and return the processing result to the user through the third-party service platform. However, in actual applications, in the process of implementing only one business, the user will frequently send multiple requests to the third-party service platform (for example, when implementing the user's insurance business, the user will send inquiry requests, insurance requests, and order requests to the Internet insurance platform (i.e., the third-party service platform) in turn). If the third-party service platform needs to forward each request to the business system for processing, it will cause a problem of high load pressure on the business system; in addition, the concurrency capacity of the third-party service platform will also be limited, which will cause a poor user experience. Summary of the invention
[0004] The present application describes a method and device for generating business order data to improve the concurrency capability of a third-party service platform.
[0005] In a first aspect, a method for generating business order data is provided, comprising:
[0006] The third-party service platform receives a service request sent by a user, wherein the service request includes identification information of a service object and description information of the user;
[0007] Determining an authentication algorithm corresponding to the business object according to the identification information of the business object;
[0008] authenticating the user according to the authentication algorithm and the description information;
[0009] After the user is authenticated, payment information corresponding to the service request is generated and the payment information is output;
[0010] Receiving payment result information sent by the third-party payment platform after completing the payment operation corresponding to the payment information;
[0011] Based on the payment result information, business order data corresponding to the business request is generated.
[0012] In a second aspect, a device for generating business order data is provided, comprising:
[0013] A receiving unit, configured to receive a service request sent by a user, wherein the service request includes identification information of a service object and description information of the user;
[0014] a determining unit, configured to determine an authentication algorithm corresponding to the business object according to the identification information of the business object received by the receiving unit;
[0015] an authentication unit, configured to authenticate the user according to the authentication algorithm determined by the determination unit and the description information;
[0016] A generating unit, configured to generate payment information corresponding to the service request and output the payment information after the authentication unit authenticates the user;
[0017] The receiving unit is further used to receive payment result information sent by the third-party payment platform after completing the payment operation corresponding to the payment information;
[0018] The generating unit is further configured to generate business order data corresponding to the business request according to the payment result information received by the receiving unit.
[0019] The method and device for generating business order data provided in this application enable the third-party service platform to directly obtain the authentication algorithm corresponding to the business request when receiving the business request sent by the user; and authenticate the user according to the authentication algorithm; after the authentication is passed, further generate the corresponding payment information; after the user performs the corresponding payment operation for the payment information, the third-party service platform can directly generate the business order data. That is, in this application, the third-party service platform can generate the business order data corresponding to the business request without real-time interaction with the business party system, that is, realize the business corresponding to the business request, thereby improving the concurrency capability of the third-party service platform. BRIEF DESCRIPTION OF THE DRAWINGS
[0020] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other accompanying drawings can be obtained based on these accompanying drawings without paying creative work.
[0021] Figure 1 This is the information interaction diagram between the traditional Internet insurance platform and the insurance company system;
[0022] Figure 2A schematic diagram of an application scenario of the method for generating business order data provided in this application;
[0023] Figure 3 A flow chart of a method for generating business order data provided by an embodiment of the present application;
[0024] Figure 4 Information interaction diagram between the Internet insurance platform and the insurance company system provided for this application;
[0025] Figure 5 A schematic diagram of a device for generating business order data provided in another embodiment of the present application. DETAILED DESCRIPTION
[0026] The embodiments of the present invention are described below in conjunction with the accompanying drawings.
[0027] The method and device for generating business order data provided in the embodiments of the present application are suitable for scenarios where users request to implement business through a third-party service platform.
[0028] For example, it is applicable to the scenario where users realize insurance business through the Internet insurance platform. The Internet insurance platform here may include an insurance business system and an insurance middle platform, wherein the insurance business system is used to receive user requests (such as inquiry requests, insurance requests, and order requests), and forward the received user requests to the insurance middle platform, which may include but is not limited to the insurance system of the shopping platform, the insurance system of the payment platform, and the financial insurance system; the insurance middle platform is used to respond to the user's request by interacting with the insurance company system (also known as the insurance institution) in real time when receiving the user's request forwarded by the insurance business system, so as to realize the user's insurance business.
[0029] In traditional technology, when implementing the user's insurance business, the information interaction diagram between the Internet insurance platform and the insurance company system can be as follows: Figure 1 As shown, Figure 1 The following steps may be included:
[0030] Step 110: The user sends a price inquiry request to the insurance business system.
[0031] The price inquiry request may include identification information of the insurance product selected by the user.
[0032] Step 120: The insurance business system forwards the quotation request to the financial super gateway through the insurance middle station.
[0033] The financial super gateway here belongs to the company where the Internet insurance platform is located.
[0034] Step 130: The financial super gateway synchronizes the above-mentioned quotation request to the insurance institution.
[0035] After receiving the inquiry request, the insurance institution may determine at least one insurance type included in the insurance product based on the identification information of the insurance product. Here, when the number of insurance types is one, the insurance type is the primary insurance; when the number of insurance types is multiple, it may include more than one primary insurance and multiple supplementary insurances; after determining at least one insurance type, the pricing rule corresponding to each insurance type in the at least one insurance type may be obtained. The pricing rule here may refer to an algorithm for pricing each insurance type, which may be defined by the insurance institution itself. It is understandable that the corresponding pricing rules may be different for different insurance types; finally, based on the pricing rules obtained for each insurance type, the price information of each insurance type is determined; and after summarizing the price information of each insurance type, the price information of the insurance product may be obtained.
[0036] Step 140: The insurance institution returns a response result of the inquiry request to the insurance business system through the insurance middle platform.
[0037] It is understandable that the response result here may include price information of the insurance product determined by the insurance agency.
[0038] After receiving the response result of the inquiry request, the insurance business system can output the price information of the insurance product requested by the user to the user, that is, display the price information of the insurance product requested by the user.
[0039] Step 150: The user sends an insurance request to the insurance business system.
[0040] The insurance request may include the identification information of the insurance product to be purchased by the user and the description information of the user. The description information of the user may include but is not limited to the following information: the age of the user, the gender of the user, and the identification of the user.
[0041] Step 160: The insurance business system sends an insurance request to the insurance middle office.
[0042] Here, after receiving the insurance request sent by the insurance business system, the insurance middle platform can generate an insurance order corresponding to the insurance request, wherein the insurance order can include identification information of the insurance product and description information of the user.
[0043] Step 170: The insurance middle platform synchronizes the insurance order to the insurance institution through the financial super gateway.
[0044] After receiving the insurance application, the insurance institution can determine at least one insurance type included in the insurance product based on the identification information of the insurance product; after determining at least one insurance type, the insurance institution can obtain the underwriting rules corresponding to each of the at least one insurance type. The underwriting rules here may refer to an algorithm for reviewing the insurance application. In an example, the underwriting rules may refer to an algorithm for reviewing the user's description information in the insurance application, that is, an algorithm for authenticating users who purchase insurance products. For example, the underwriting rules may be: gender: female; age: ≤30; salary: ≥5000, etc.; they may also be defined by the insurance institution itself. It is understandable that the corresponding underwriting rules for different insurance types may be different; finally, the user is authenticated based on the obtained underwriting rules for each insurance type and the user's description information.
[0045] Step 180: The insurance institution returns the review result of the insurance order to the insurance middle office.
[0046] The audit result here may refer to the result information of whether the insurance order has been audited or not; when the audit result is the result information of whether the insurance order has been audited, the insurance middle office may generate a payment order by calling the payment platform, and the payment order may include the identification information of the insurance product to be purchased by the user and the payment amount and other information.
[0047] Step 190: The insurance middle platform returns a response result of the insurance request to the insurance business system.
[0048] It is understandable that the response result here may include the payment order or the information that the insurance order has not been reviewed and approved.
[0049] After receiving the response result of the insurance request, the insurance business system can output or display the payment order or the information that the insurance order has not been approved to the user.
[0050] Step 200: The user sends a payment request to the insurance business system.
[0051] The payment request may include a payment order.
[0052] Step 210: The insurance business system forwards the payment request to the minimalist cashier.
[0053] The minimalist cashier here belongs to the above-mentioned payment platform. The minimalist cashier can perform corresponding payment operations according to the received payment request.
[0054] Step 220, the minimalist cashier returns the payment result to the insurance middle office.
[0055] After completing the corresponding payment operation, the minimalist cashier can return the payment result to the insurance middle office.
[0056] Step 230: The insurance middle platform sends a policy request to the insurance institution through the financial super gateway.
[0057] After receiving the payment result, if the payment result is information indicating successful payment, the insurance middle station can send a bill issuance request to the financial super gateway based on the payment result. The financial super gateway will then synchronize the bill issuance request to the insurance institution. The bill issuance request may include identification information of the insurance product purchased by the user.
[0058] Step 240: The insurance institution generates policy data.
[0059] After receiving the policy issuance request, the insurance institution can determine at least one insurance type included in the insurance product based on the identification information of the insurance product; after determining at least one insurance type, the policy issuance rule corresponding to each insurance type in the at least one insurance type can be obtained. The policy issuance rule here may refer to an algorithm that defines the information contained in the final generated policy data (also called a contract), which may be defined by the insurance institution itself. It can be understood that for different insurance types, the corresponding policy issuance rules may be different; finally, the policy data is generated based on the obtained policy issuance rules for each insurance type.
[0060] Step 250: The insurance institution returns a response result of the policy issuance request to the insurance middle office.
[0061] It is understandable that the response result here may include the policy data generated by the insurance institution. After receiving the response result, the insurance middle platform can also generate insurance order data defined by itself. This insurance order data corresponds to the policy data generated by the insurance institution, and is mainly used for subsequent claims and revision preservation services.
[0062] Step 260: The insurance middle platform returns the result information of the policy issuance request to the insurance business system.
[0063] If the result information of the policy issuance request here is information used to indicate that the policy issuance is successful, it may include insurance order data. It can be understood that the insurance order data corresponds one-to-one to the insurance policy data generated by the insurance institution; after receiving the insurance order data, the insurance business system can output or display the insurance order data to the user.
[0064] If the result information of the above order request is information used to indicate that the order has failed, a refund can be automatically made to the user.
[0065] from Figure 1It can be seen that every time the insurance middle platform receives a user request, it needs to interact with the insurance company system to respond to the request. In actual applications, the Internet insurance platform may receive hundreds of millions of user requests every day, which requires frequent information interaction between the Internet insurance platform and the insurance company system, which will cause a large load pressure on the insurance company system and limited concurrency capabilities of the Internet insurance platform.
[0066] To solve the above problems, this application proposes the following improvement ideas: the pricing rules, underwriting rules and order rules (collectively referred to as insurance rules) defined by the insurance company system are built into the insurance middle platform. After the insurance rules are built into the insurance middle platform, when the insurance middle platform receives the user's request forwarded by the insurance business system, the insurance middle platform can directly respond to the user's request according to the built-in insurance rules; after that, when the set sending cycle is reached, it will interact with the insurance company system. This can reduce the number of interactions between the Internet insurance platform and the insurance company system, thereby reducing the load pressure of the insurance company system, and can improve the concurrency capacity of the Internet insurance platform.
[0067] In fact, it is not limited to insurance products, but also many other businesses. In the process of implementing the business, it is usually necessary for the third-party service platform to frequently interact with the business system. For this reason, this application is passed Figure 2 and Figure 3 To illustrate the improvement solutions proposed in this application for all businesses.
[0068] Figure 2 A schematic diagram of an application scenario of the method for generating business order data provided in this application, Figure 2 In the process, the third-party service platform can preset the algorithm corresponding to the business object, such as pricing algorithm and / or authentication algorithm, etc. The algorithm can be defined by the business party system, and the above business objects include but are not limited to objects requested by business requests such as insurance products and financial products; the third-party service platform may not interact with the business party system in real time, but interact with the business party system periodically (such as in days or hours); the third-party payment platform can interact with the third-party service platform to realize payment operations for business objects; the business party system is used to realize the landing of data (such as the landing of insurance policy data). Specifically, before the sending cycle arrives, when the third-party service platform receives the user's business request, it can directly respond to the business request according to the preset algorithm, and finally generate the business order data corresponding to the business request; and after the sending cycle arrives, according to the business order data generated in the time segment, create a business order data file corresponding to the time segment, and send the created business order data file to the business party system, so as to realize the real landing of the data.
[0069] Figure 3 A flow chart of a method for generating business order data provided by an embodiment of the present application, Figure 3 In the method, the execution subject may be Figure 2 Third-party service platforms in the industry, such as Internet insurance platforms, such as Figure 3 As shown, the method may specifically include:
[0070] Step 310: The third-party service platform receives a service request sent by a user.
[0071] The service request may include the identification information of the service object and the description information of the user. The service request here includes but is not limited to the insurance request, etc. The description information of the user is input by the user, which may include but is not limited to the following information: the user's age, the user's gender, the user's identification and other information.
[0072] Optionally, when the business object included in the business request has attribute information such as price, for example, when the business object is an insurance product, the following steps may be further performed before step 310:
[0073] Step A: Receive a price inquiry request for a business object sent by a user.
[0074] The inquiry request may include identification information of the business object.
[0075] Step B: Determine at least one business unit included in the business object according to the identification information of the business object.
[0076] The business units here include main business units and additional business units. Specifically, when the number of the business unit is one, the one business unit is the main business unit; and when the number of the business units is multiple, it may include more than one main business unit and multiple additional business units.
[0077] Step C: Obtain a pricing algorithm corresponding to each business unit in at least one business unit.
[0078] Because different business units usually have different corresponding prices, it is necessary to first determine the pricing algorithm corresponding to each business unit contained in the business object. For example, different types of insurance included in an insurance product usually have different corresponding prices.
[0079] Step D: Determine the price information of each business unit based on the pricing algorithm.
[0080] Step E: Determine the price information of the business object based on the price information of each business unit.
[0081] After determining the price information of each business unit, the price information of the business object can be obtained by aggregating the price information of each business unit.
[0082] Step F: Return the price information of the business object to the user.
[0083] After viewing the price information of the business object, the user may send the above business request to the third-party service platform.
[0084] Step 320: Determine the authentication algorithm corresponding to the business object according to the identification information of the business object.
[0085] Wherein, step 320 may specifically include:
[0086] Determining at least one business unit included in the business object according to identification information of the business object;
[0087] Obtain an authentication algorithm corresponding to each business unit in at least one business unit.
[0088] The above authentication algorithm can be defined by the business party system. Specifically, the business party system defines the authentication algorithm based on the business unit dimension, that is, different business units have the same corresponding authentication algorithm. After the business party system defines the above authentication algorithm, it is manually or machine-set to the third-party service platform.
[0089] Specifically, based on the identification information of the business object, a business object can be uniquely determined, thereby determining at least one business unit contained in the business object; then the authentication algorithm corresponding to each business unit can be obtained. For example, based on the identification information of an insurance product, at least one insurance type contained in the insurance product can be determined; after determining at least one insurance type, the authentication algorithm corresponding to each insurance type can be obtained (such as the above-mentioned underwriting rules, also called underwriting algorithms).
[0090] Step 330: Authenticate the user based on the authentication algorithm and description information.
[0091] Here, taking the business object as an insurance product as an example, assuming that the insurance product only contains one main insurance type, and the underwriting algorithm corresponding to the main insurance type is: Gender: Female; Age: ≤30; Salary: ≥5000, and the user's description information is: Gender: Female; Age: 25; Salary: 8000. Because the user's description information meets the conditions set by the above underwriting rules, the authentication of the user is passed.
[0092] Of course, in actual applications, in the process of authenticating users, the recorded user information can also be obtained from a third-party service platform or a platform related thereto according to the information input by the user; then the user is authenticated according to the recorded user information and the information input by the user. For example, in the scenario where the user implements insurance business through an Internet insurance platform, assuming that the information input by the user includes the user's identification information (such as ID number), the user's transaction information can be obtained from a third-party payment platform according to the user's identification information. The transaction information here can usually reflect the user's consumption capacity; then the user is authenticated according to the user's transaction information and the information input by the user.
[0093] In addition, the business system can also feed back the user's historical behavior data to the third-party service platform, so that the third-party service platform can authenticate the user based on the information entered by the user and the historical behavior data. For example, in the scenario where the user purchases insurance through the Internet insurance platform, the insurance company system can return the user's historical claims information or insurance information to the Internet insurance platform; so that when the Internet insurance platform authenticates the user, it can authenticate the user based on the information entered by the user and the user's historical claims information or insurance information.
[0094] Step 340: after the user is authenticated, payment information corresponding to the business request is generated and output.
[0095] After the user is authenticated, payment information can be generated by calling a third-party payment platform, where the payment information may include identification information of the business object and payment amount, etc. In one example, the third-party service platform can generate a payment order by calling a third-party payment platform, and output the payment information to the user in the form of the payment order.
[0096] Step 350: receiving payment result information sent by the third-party payment platform after completing the payment operation corresponding to the payment information.
[0097] After sending the payment information to the user, the user can send a payment request to the third-party payment platform through the third-party service platform, so that the third-party payment platform performs the corresponding payment operation and sends payment result information to the third-party service platform, where the payment result information can refer to successful payment information or failed payment information.
[0098] Step 360: Generate business order data corresponding to the business request based on the payment result information.
[0099] Specifically, when the payment result information is information of successful payment, the third-party payment platform can be called to generate business order data corresponding to the business request, and the business order data can be output to the user, thereby realizing the business requested by the user.
[0100] From this, it can be seen that after the authentication algorithm is set on the third-party service platform, the third-party service platform can directly respond to the user's business request and generate business order data corresponding to the business request. This can avoid the problem of heavy load pressure on the business system and poor concurrency capability of the third-party service platform in traditional technology, where the third-party service platform needs to interact with the business system every time it receives a user's business request.
[0101] Optionally, in order to realize the actual landing of data, the present application can also set a sending cycle corresponding to the business object. In one example, when a certain business object has a relatively high real-time requirement, the set sending cycle can be in hours, that is, the business data file is sent to the business party system in the form of T+h, where T represents the day and h represents the hour; and when another business object has a relatively low real-time requirement, the set sending cycle can be in days, that is, the business data file is sent to the business party system in the form of T+1, where T+1 represents the next day. For example, when the business object is an insurance product, and the insurance product is return freight insurance, the set sending cycle can be in days; and when the insurance product is auto insurance or life insurance, the set sending cycle can be in hours.
[0102] When setting the sending cycle, assuming that the sending cycle is set to 8 hours, the third-party service platform will create a business order data file based on the generated business order data every 8 hours (that is, when the sending cycle arrives); and send the business order data file to the business party system; after receiving the business data file, the business party system will actually implement the data. For example, in the scenario of insurance business, the generated business order data file is an insurance order data file. After receiving the insurance order data file, the insurance company system generates policy data (also called policy contract) and returns the policy data to the user.
[0103] When the method for generating business order data of the present application is applied to the scenario of insurance business, Figure 2 The third-party service platform in the above-mentioned term may refer to an Internet insurance platform, wherein the Internet insurance platform includes: an insurance business system and an insurance middle platform; the business party system may refer to an insurance company system (also known as an insurance institution), and the information exchange between the Internet insurance platform and the insurance company system may be as follows: Figure 4 shown. Figure 4 The main steps are as follows:
[0104] Step 410: The user sends a price inquiry request to the insurance business system.
[0105] The inquiry request may include identification information of the insurance product selected by the user, wherein the insurance products include but are not limited to auto insurance, life insurance, and return freight insurance.
[0106] Step 420: The insurance business system forwards the quotation request to the insurance middle office.
[0107] Step 430: The insurance middle platform determines the price information of the insurance product.
[0108] Specifically, the insurance middle platform can determine at least one insurance type included in the insurance product based on the identification information of the insurance product. Here, when the number of insurance types is one, the insurance type is the main insurance; when the number of insurance types is multiple, it can include more than one main insurance and multiple supplementary insurances; after determining at least one insurance type, the pricing algorithm (also called pricing rule) corresponding to each insurance type in the at least one insurance type can be obtained. The pricing algorithm here may refer to an algorithm for how to price each insurance type, which may be defined by the insurance institution itself. It can be understood that for different insurance types, the corresponding pricing algorithms may be different; finally, based on the pricing algorithms obtained for each insurance type, the price information of each insurance type is determined; and after summarizing the price information of each insurance type, the price information of the insurance product can be obtained.
[0109] Step 440: The insurance middle platform returns the price information of the insurance product to the insurance business system.
[0110] After receiving the price information of the insurance product, the insurance business system displays the price information to the user.
[0111] Step 450: The user sends an insurance request to the insurance business system.
[0112] The insurance request may include the identification information of the insurance product to be purchased by the user and the description information of the user. The description information of the user may include but is not limited to the following information: the age of the user, the gender of the user, and the identification of the user.
[0113] Step 460: The insurance business system forwards the insurance request to the insurance middle office.
[0114] Here, after receiving the insurance request sent by the insurance business system, the insurance middle platform can generate an insurance order corresponding to the insurance request, wherein the insurance order can include identification information of the insurance product and description information of the user.
[0115] Step 470: The insurance middle office reviews the insurance order.
[0116] Specifically, after receiving the insurance order, the insurance middle station determines at least one insurance type included in the insurance product; after determining at least one insurance type, it can obtain the underwriting algorithm corresponding to each insurance type in the at least one insurance type. The underwriting algorithm here may refer to an algorithm for reviewing the insurance order. In an example, the underwriting algorithm may refer to an algorithm for reviewing the user's description information in the insurance order, that is, an algorithm for authenticating users who purchase insurance products. For example, the underwriting algorithm may be: gender: female; age: ≤30; salary: ≥5000, etc.; it may also be defined by the insurance institution itself. It can be understood that for different insurance types, the corresponding underwriting algorithms may be different; finally, the user is authenticated based on the obtained underwriting algorithm and the user's description information.
[0117] Of course, in actual applications, during the process of authenticating the user, the recorded user information can also be obtained from the Internet insurance platform or the third-party payment platform based on the information input by the user; then the user is authenticated based on the recorded user information and the information input by the user. For example, if the information input by the user includes the user's identification information (such as ID number), the user's transaction information can be obtained from the third-party payment platform based on the user's identification information. The transaction information here can usually reflect the user's consumption capacity; then the user is authenticated based on the user's transaction information and the information input by the user.
[0118] In addition, the insurance company system can also feedback the user's historical claims information or insurance information to the Internet insurance platform; so that when the Internet insurance platform authenticates the user, it can authenticate the user based on the information entered by the user and the user's historical claims information or insurance information.
[0119] Optionally, after the user authentication is passed, that is, after the insurance order is reviewed and approved, the insurance middle platform can also call the minimalist cashier to generate a corresponding payment order, which can include the identification information of the insurance product to be purchased by the user and the payment amount and other information.
[0120] Step 480: The insurance middle platform returns the payment order to the insurance business system.
[0121] After receiving the payment order, the insurance business system displays the payment order to the user.
[0122] It is understandable that after the user authentication fails, the insurance middle platform only returns the authentication failure result information to the business system and no longer executes the subsequent steps.
[0123] Step 490: The user sends a payment request to the insurance business system.
[0124] The payment request may include a payment order.
[0125] Step 4100: The insurance business system forwards the payment request to the minimalist cashier.
[0126] The minimalist cashier here belongs to a third-party payment platform. The minimalist cashier can perform corresponding payment operations according to the received payment request.
[0127] Step 4110, the minimalist cashier returns the payment result to the insurance middle office.
[0128] Step 4120, the insurance middle platform generates insurance order data.
[0129] After receiving the payment result, if the payment result is information indicating a successful payment, the insurance middle station can determine at least one insurance type included in the insurance product based on the identification information of the insurance product; after determining at least one insurance type, the order issuance algorithm for each insurance type in the at least one insurance type can be obtained. The order issuance algorithm here can refer to an algorithm that defines the information contained in the insurance order data finally generated, which can be defined by the insurance middle station itself. It can be understood that for different insurance types, the corresponding order issuance algorithms may be different; finally, the insurance order data is generated based on the order issuance algorithms of each insurance type obtained. In an example, the generated insurance order data may include but is not limited to the following information: information about the policyholder, information about the insured, insurance amount information, beneficiary information, premium information, insurance type information, insurer information, etc.
[0130] Step 4130: The insurance middle platform returns the insurance order data to the insurance business system.
[0131] After receiving the insurance order data, the insurance business system can output or display the insurance order data to the user.
[0132] Step 4140, when the sending cycle arrives, the insurance middle station creates an insurance order data file based on the generated insurance order data.
[0133] Step 4150: The insurance middle office sends the insurance order data file to the insurance institution.
[0134] Step 4160: The insurance institution returns the policy data to the insurance business system.
[0135] In order to realize the real landing of data, this application can also set corresponding sending cycles for different insurance products. In one example, when a certain insurance product has a relatively high real-time requirement, the set sending cycle can be in hours; when another insurance product has a relatively low real-time requirement, the set sending cycle can be in days. For example, when the insurance product is return freight insurance, the set sending cycle can be in days; and when the insurance product is auto insurance or life insurance, the set sending cycle can be in hours.
[0136] When setting the sending cycle, assuming that the sending cycle is set to 8 hours, the insurance middle platform will create an insurance order data file based on the generated insurance order data every 8 hours (that is, when the sending cycle arrives); and send the insurance order data file to the insurance institution; after receiving the insurance order data file, the insurance institution will actually implement the data. For example, generate insurance policy data (also called insurance policy contract) and return the insurance policy data to the user.
[0137] In order to enable those skilled in the art to more clearly understand the improvement ideas of the present application, the technical solution of the present application is summarized as follows:
[0138] 1) This application decomposes the real-time synchronous request link between users, Internet insurance platforms, and insurance company systems into a real-time request interaction link between users and Internet insurance platforms and a "T+1 / T+h" non-real-time interaction mode between Internet insurance platforms and insurance company systems, to achieve the function of quickly outputting insurance order data.
[0139] 2) The Internet insurance platform has pricing and underwriting capabilities, and does not need to rely on the insurance company system in real time, which improves the flexible processing capabilities of the Internet insurance platform and ensures the transaction concurrency and response time of the Internet insurance platform.
[0140] 3) The Internet insurance platform can output insurance order data to users in real time. For users, the long link of "user-Internet insurance platform-insurance company system" is changed to a short link of "user-Internet insurance platform", which reduces the number of links with failures in the request link, reduces the failure rate, shortens the response delay, and greatly improves the user experience.
[0141] 4) The Internet insurance platform and the insurance company system use periodic non-real-time interactions, which greatly reduces the frequency of access to the insurance company system and its load pressure, ensuring that it can provide services normally and stably.
[0142] Corresponding to the above-mentioned method for generating business order data, the embodiment of the present application also provides a device for generating business order data, such as Figure 5 As shown, the device comprises:
[0143] The receiving unit 501 is configured to receive a service request sent by a user, wherein the service request includes identification information of a service object and description information of the user.
[0144] The determining unit 502 is used to determine the authentication algorithm corresponding to the business object according to the identification information of the business object received by the receiving unit 501.
[0145] Optionally, the determining unit 502 may be specifically configured to:
[0146] Determining at least one business unit included in the business object according to identification information of the business object;
[0147] Obtain an authentication algorithm corresponding to each business unit in at least one business unit.
[0148] The authentication unit 503 is used to authenticate the user according to the authentication algorithm and description information determined by the determination unit 502.
[0149] The generating unit 504 is used to generate payment information corresponding to the service request and output the payment information after the authentication unit 503 successfully authenticates the user.
[0150] The receiving unit 501 is further used to receive payment result information sent by the third-party payment platform after completing the payment operation corresponding to the payment information.
[0151] The generating unit 504 is further configured to generate business order data corresponding to the business request according to the payment result information received by the receiving unit 501 .
[0152] Optionally, the device further comprises:
[0153] The judging unit 505 is used to judge whether the sending cycle has arrived, wherein the sending cycle corresponds to the service object.
[0154] The creating unit 506 is configured to create a service order data file according to the generated service order data when the judging unit 505 judges that the sending cycle has arrived.
[0155] The sending unit 507 is used to send the business order data file created by the creating unit 506 to the business party system.
[0156] Optionally, the device further includes: an acquisition unit 508 and a return unit 509;
[0157] The receiving unit 501 is further configured to receive a price inquiry request for a business object sent by a user, where the price inquiry request includes identification information of the business object.
[0158] The determining unit 502 is further configured to determine at least one business unit included in the business object according to the identification information of the business object received by the receiving unit 501 .
[0159] The acquisition unit 508 is used to acquire the pricing algorithm corresponding to each business unit in at least one business unit.
[0160] The determining unit 502 is further configured to determine the price information of each business unit according to the pricing algorithm obtained by the obtaining unit 508 .
[0161] The determining unit 502 is further configured to determine the price information of the business object according to the price information of each business unit.
[0162] The returning unit 509 is used to return the price information of the business object to the user.
[0163] Optionally, the receiving unit 501 is further configured to receive historical behavior data of the user sent by the business party system.
[0164] The authentication unit 503 is specifically used to authenticate the user according to the authentication algorithm, description information and historical behavior data of the user.
[0165] The functions of the various functional modules of the device of the embodiment of the present application can be implemented through the various steps of the above-mentioned method embodiment. Therefore, the specific working process of the device provided by the present application will not be repeated here.
[0166] The device for generating business order data provided by the present application comprises: a receiving unit 501 receives a business request sent by a user; a determining unit 502 determines an authentication algorithm corresponding to a business object according to identification information of the business object; an authentication unit 503 authenticates the user according to the authentication algorithm and description information; a generating unit 504 generates payment information corresponding to the business request after authenticating the user, and outputs the payment information to the user; the receiving unit 501 receives payment result information sent by the user after completing a payment operation corresponding to the payment information through a third-party payment platform; and the generating unit 504 generates business order data corresponding to the business request according to the payment result information. Thus, the concurrency capability of the device for generating business order data can be improved.
[0167] Those skilled in the art should be aware that in one or more of the above examples, the functions described in the present invention can be implemented by hardware, software, firmware or any combination thereof. When implemented by software, these functions can be stored in a computer-readable medium or transmitted as one or more instructions or codes on a computer-readable medium.
[0168] The specific implementation methods described above further illustrate the objectives, technical solutions and beneficial effects of the present invention in detail. It should be understood that the above description is only a specific implementation method of the present invention and is not intended to limit the scope of protection of the present invention. Any modifications, equivalent substitutions, improvements, etc. made on the basis of the technical solution of the present invention should be included in the scope of protection of the present invention.
Claims
1. A method for generating business order data, characterized in that: include: The third-party service platform receives a business request sent by a user, wherein the business request includes identification information of a business object of the business party system and description information of the user; Determine, according to the identification information of the business object, an authentication algorithm corresponding to the business object, wherein the authentication algorithm is defined by the business party system, and the determination process includes: determining, according to the identification information of the business object, at least one business unit included in the business object; obtaining an authentication algorithm corresponding to each business unit in the at least one business unit; Authenticating the user according to the authentication algorithm and the description information; After the user is authenticated, payment information corresponding to the service request is generated and the payment information is output; Receiving payment result information sent by the third-party payment platform after completing the payment operation corresponding to the payment information; Based on the payment result information, business order data corresponding to the business request is generated, and the business order data is output to the user, so that the third-party service platform implements the business corresponding to the business request without real-time interaction with the business party system.
2. The method according to claim 1, characterized in that: After generating the service order data corresponding to the service request, the method further includes: Determine whether a sending cycle has arrived, wherein the sending cycle corresponds to a business object; When the sending cycle arrives, creating a business order data file according to the generated business order data; Send the business order data file to the business party system.
3. The method according to claim 1, characterized in that Before the third-party service platform receives the service request sent by the user, the method further includes: receiving a price inquiry request for the business object sent by the user, wherein the price inquiry request includes identification information of the business object; Determining at least one business unit included in the business object according to the identification information of the business object; Obtaining a pricing algorithm corresponding to each business unit in the at least one business unit; Determine the price information of each business unit according to the pricing algorithm; Determining the price information of the business object according to the price information of each business unit; Returning price information of the business object to the user.
4. The method according to any one of claims 1 to 3, characterized in that: Also includes: Receive the historical behavior data of the user sent by the business party system; The authenticating the user according to the authentication algorithm and the description information includes: The user is authenticated according to the authentication algorithm, the description information and the historical behavior data of the user.
5. A device for generating business order data, applied to a third-party service platform, characterized in that: include: A receiving unit, configured to receive a service request sent by a user, wherein the service request includes identification information of a service object of a service party system and description information of the user; A determination unit is used to determine an authentication algorithm corresponding to the business object according to the identification information of the business object received by the receiving unit, wherein the authentication algorithm is defined by the business party system, and the determination process includes: determining at least one business unit included in the business object according to the identification information of the business object; and obtaining an authentication algorithm corresponding to each business unit in the at least one business unit; an authentication unit, configured to authenticate the user according to the authentication algorithm determined by the determination unit and the description information; A generating unit, configured to generate payment information corresponding to the service request and output the payment information after the authentication unit authenticates the user; The receiving unit is further used to receive payment result information sent by the third-party payment platform after completing the payment operation corresponding to the payment information; The generating unit is further used to generate business order data corresponding to the business request according to the payment result information received by the receiving unit, and output the business order data to the user, so that the third-party service platform can implement the business corresponding to the business request without real-time interaction with the business party system.
6. The device according to claim 5, characterized in that Also includes: A judging unit, used to judge whether a sending cycle has arrived, wherein the sending cycle corresponds to a business object; A creating unit, configured to create a service order data file according to the generated service order data when the judging unit judges that the sending cycle has arrived; A sending unit is used to send the business order data file created by the creating unit to the business party system.
7. The device according to claim 5, characterized in that Also includes: Get unit and return unit; The receiving unit is further configured to receive a price inquiry request for the business object sent by the user, wherein the price inquiry request includes identification information of the business object; The determining unit is further configured to determine at least one business unit included in the business object according to the identification information of the business object received by the receiving unit; The acquisition unit is used to acquire the pricing algorithm corresponding to each business unit in the at least one business unit; The determining unit is further configured to determine the price information of each business unit according to the pricing algorithm acquired by the acquiring unit; The determining unit is further configured to determine the price information of the business object according to the price information of each business unit; The returning unit is used to return the price information of the business object to the user.
8. The device according to any one of claims 5 to 7, characterized in that: The receiving unit is further configured to receive the historical behavior data of the user sent by the business party system; The authentication unit is specifically used to authenticate the user according to the authentication algorithm, the description information and the historical behavior data of the user.
9. A method for generating insurance order data, characterized in that: include: The third-party service platform receives an insurance request sent by a user, wherein the insurance request includes identification information of the insurance product in the insurance company system and description information of the user; Determine, according to the identification information of the insurance product, an underwriting rule corresponding to the insurance product, wherein the underwriting rule is defined by the insurance company system, and the determination process includes: determining, according to the identification information of the insurance product, at least one insurance type included in the insurance product; obtaining an underwriting rule corresponding to each insurance type in the at least one insurance type; Authenticating the user according to the underwriting rules and the description information; After the user is authenticated, payment information corresponding to the insurance request is generated and the payment information is output; Receiving payment result information sent by the third-party payment platform after completing the payment operation corresponding to the payment information; Based on the payment result information, insurance order data corresponding to the insurance request is generated, and the insurance order data is output to the user, so that the third-party service platform completes the insurance business corresponding to the insurance request without real-time interaction with the insurance company system.
10. The method according to claim 9, characterized in that After generating the insurance order data corresponding to the insurance request, the method further includes: Determine whether a sending cycle has arrived, wherein the sending cycle corresponds to an insurance product; When the sending cycle arrives, creating an insurance order data file according to the generated insurance order data; The insurance order data file is sent to the insurance company system.
11. The method according to claim 9, characterized in that Before the third-party service platform receives the insurance request sent by the user, it also includes: receiving a price inquiry request for the insurance product sent by the user, wherein the price inquiry request includes identification information of the insurance product; Determining at least one insurance type included in the insurance product according to the identification information of the insurance product; Obtaining a pricing algorithm corresponding to each insurance type in the at least one insurance type; Determine the price information of each insurance type according to the pricing algorithm; Determine the price information of the insurance product according to the price information of each insurance type; Returning price information of the insurance product to the user.
12. The method according to any one of claims 9 to 11, characterized in that: Also includes: Receiving the historical behavior data of the user sent by the insurance company system; The authenticating the user according to the underwriting rule and the description information includes: The user is authenticated according to the underwriting rules, the description information and the user's historical behavior data.
13. A device for generating insurance order data, applied to a third-party service platform, characterized in that: include: A receiving unit, configured to receive an insurance request sent by a user, wherein the insurance request includes identification information of the insurance product in the insurance company system and description information of the user; a determining unit, configured to determine an underwriting rule corresponding to the insurance product according to the identification information of the insurance product received by the receiving unit, wherein the underwriting rule is defined by the insurance company system, and the determining process includes: determining at least one insurance type included in the insurance product according to the identification information of the insurance product; and obtaining an underwriting rule corresponding to each insurance type in the at least one insurance type; an authentication unit, configured to authenticate the user according to the underwriting rule determined by the determination unit and the description information; A generating unit, configured to generate payment information corresponding to the insurance request and output the payment information after the authentication unit authenticates the user; The receiving unit is further used to receive payment result information sent by the third-party payment platform after completing the payment operation corresponding to the payment information; The generating unit is further used to generate insurance order data corresponding to the insurance request according to the payment result information received by the receiving unit, and output the insurance order data to the user, so that the third-party service platform can complete the insurance business corresponding to the insurance request without real-time interaction with the insurance company system.
14. The device according to claim 13, characterized in that Also includes: A judging unit, used to judge whether a sending cycle has arrived, wherein the sending cycle corresponds to an insurance product; A creating unit, configured to create an insurance order data file according to the generated insurance order data when the judging unit judges that the sending cycle has arrived; The sending unit is used to send the insurance order data file created by the creating unit to the insurance company system.
15. The device according to claim 13, characterized in that Also includes: Get unit and return unit; The receiving unit is further configured to receive a price inquiry request for the insurance product sent by the user, wherein the price inquiry request includes identification information of the insurance product; The determining unit is further configured to determine at least one insurance type included in the insurance product according to the identification information of the insurance product received by the receiving unit; The acquisition unit is used to acquire the pricing algorithm corresponding to each insurance type of the at least one insurance type; The determining unit is further configured to determine price information of each insurance type according to the pricing algorithm acquired by the acquiring unit; The determining unit is further used to determine the price information of the insurance product according to the price information of each insurance type; The returning unit is used to return the price information of the insurance product to the user.
16. The device according to any one of claims 13 to 15, characterized in that: The receiving unit is further used to receive the historical behavior data of the user sent by the insurance company system; The authentication unit is specifically used to authenticate the user according to the underwriting rules, the description information and the user's historical behavior data.
