Joint lease scheduling method, apparatus and device, and storage medium

Abstract

The embodiment of the invention provides a joint lease scheduling method, apparatus and device, and a storage medium, and the method can detect current service demand information after obtaining a lease service reporting instruction, matches a target processing strategy according to the current service demand information, obtains service data based on the target processing strategy, and sends the service data to a lease server. And transmitting the business data to the united business system through the front-end service, so that the united business system executes business approval on the business data. And pushing the service approval conclusion to the leasing service system, and setting a log recording interface according to the service data and the service approval conclusion. Wherein the business data comprises at least one of credit auditing data, contract confirmation data, payment approval data, seal file data and loan state data. According to the method, the dispatching center can be used as a unified entrance, the dispersity and complexity of the interfaces are reduced by integrating and distributing the interfaces of the scenes, and the standardization degree and maintainability of the joint lease dispatching process are improved.

Description

Technical Field

[0001] The present application relates to the field of vehicle rental technology, and in particular to a joint rental scheduling method, apparatus, device, and storage medium. Background Art

[0002] Vehicle leasing is a service that transfers the right to use a vehicle to a lessee for a specific period of time, meeting the lessee's temporary vehicle needs. The platform that establishes a vehicle leasing business between lessees and managers is called a vehicle leasing platform or vehicle leasing system. The vehicle leasing platform enables the exchange of data, information, and instructions between lessees and managers to meet the interactive needs of the leasing business. The vehicle leasing platform can be used to perform business activities such as vehicle management, customer management, order management, billing management, and data analysis and reporting.

[0003] Taking the commercial vehicle business as an example, a commercial vehicle leasing platform can receive leasing applications from lessees and, based on these applications, send a business list to the management. After the management completes the business approval, the payment transaction is verified, enabling the commercial vehicle leasing business. To increase the scale and penetration of commercial vehicle leasing, the leasing platform can also collaborate with other manufacturers to jointly initiate leasing operations, forming a joint leasing business. However, due to the lack of unified interface management, various nodes in the commercial vehicle leasing system may adopt different interface standards or protocols. This results in fragmented interfaces and makes unified management difficult, impacting system scalability and maintenance efficiency.

[0004] Furthermore, due to the high degree of coupling between different business systems, business logic conversion and data processing are dispersed across various nodes, leading to strong interdependence between systems and making independent optimization or expansion difficult. Each business system may need to independently handle the logical conversion of order query information interfaces, resulting in code redundancy and repeated development, increasing maintenance costs. Furthermore, the commercial vehicle leasing system lacks a unified logging and anomaly warning mechanism, making problem troubleshooting difficult and impacting system reliability and stability. Summary of the Invention

[0005] In view of this, embodiments of the present application provide a joint leasing scheduling method, apparatus, device, and storage medium to solve the problem of low operation and maintenance efficiency of commercial vehicle leasing systems.

[0006] According to one aspect of the present application, a joint leasing scheduling method is provided, which is applied to a scheduling center, wherein the scheduling center establishes a communication connection with a leasing business system, and the scheduling center also establishes a communication connection with the joint business system through a front-end service; the method includes:

[0007] detecting current business demand information in response to a leasing business submission instruction, wherein the leasing business submission instruction is an instruction transmitted by the leasing business system to the dispatch center when submitting a submission;

[0008] Matching a target processing strategy according to the current business demand information, wherein the target processing strategy is one of multiple processing strategies pre-configured in the dispatch center;

[0009] Acquiring business data based on the target processing strategy, wherein the business data is data generated by the leasing business system according to the leasing business submission instruction; the business data includes one or more combinations of credit review data, contract confirmation data, payment approval data, seal document data, and loan status data;

[0010] The business data is transmitted to the joint business system through the front-end service, and the business approval conclusion of the joint business system based on the business data feedback is pushed to the leasing business system;

[0011] A log recording interface is set according to the business data and the business approval conclusion, and the log recording interface is used to provide log data for the leasing business system and the joint business system.

[0012] According to another aspect of the present application, a joint leasing scheduling device is provided, which is applied to a scheduling center. The scheduling center establishes a communication connection with a leasing business system. The scheduling center also establishes a communication connection with the joint business system through a front-end service. The device includes:

[0013] a demand detection module, configured to detect current business demand information in response to a leasing business submission instruction, wherein the leasing business submission instruction is an instruction transmitted by the leasing business system to the dispatch center when submitting a submission;

[0014] a strategy matching module, configured to match a target processing strategy according to the current business demand information, wherein the target processing strategy is one of a plurality of processing strategies pre-configured in the dispatching center;

[0015] a business data acquisition module, configured to acquire business data based on the target processing strategy, wherein the business data is data generated by the leasing business system according to the leasing business submission instruction; the business data includes one or more combinations of credit review data, contract confirmation data, payment approval data, seal document data, and loan status data;

[0016] A data push module, configured to transmit the business data to the joint business system through the front-end service, and to push the business approval conclusion of the joint business system based on the business data feedback to the leasing business system;

[0017] The interface setting module is used to set a log recording interface according to the business data and the business approval conclusion, and the log recording interface is used to provide log data for the leasing business system and the joint business system.

[0018] According to another aspect of the present application, a computer device is provided, including a storage medium, a processor, and a computer program stored on the storage medium and executable on the processor, wherein the processor implements the above-mentioned joint leasing scheduling method when executing the program.

[0019] According to another aspect of the present application, a storage medium is provided, on which a computer program is stored. When the program is executed by a processor, the above-mentioned joint leasing scheduling method is implemented.

[0020] By leveraging the above-described technical solutions, embodiments of the present application provide a joint leasing scheduling method, apparatus, device, and storage medium. After receiving a leasing business submission instruction, the method detects current business demand information and matches a target processing strategy based on the current business demand information. Based on the target processing strategy, the method then obtains business data and transmits the business data to a joint business system via a front-end service, enabling the joint business system to perform business approval on the business data. The business approval conclusion is then pushed to the leasing business system, and a logging interface is established based on the business data and the business approval conclusion. The business data includes at least one of credit review data, contract confirmation data, payment approval data, seal document data, and loan status data. The method utilizes a scheduling center as a unified entry point, integrating and distributing interfaces for various scenarios to reduce interface fragmentation and complexity, thereby improving the standardization and maintainability of the joint leasing scheduling process. Furthermore, the method supports multiple processing strategies and can be dynamically adjusted based on actual needs to meet the business requirements of different scenarios. The method also provides a unified information interface and a unified logging and early warning mechanism to facilitate subsequent problem tracing and data analysis.

[0021] The above description is only an overview of the technical solution of the present application. In order to more clearly understand the technical means of the present application, it can be implemented in accordance with the contents of the specification. In order to make the above and other purposes, features and advantages of the present application more obvious and easy to understand, the specific implementation methods of the present application are listed below. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0023] Figure 1 A schematic diagram of the joint leasing platform structure provided in an embodiment of the present application;

[0024] Figure 2 A schematic diagram of the structure of a joint leasing platform including a dispatch center and front-end services provided in an embodiment of the present application;

[0025] Figure 3 A flowchart of the joint leasing scheduling method provided in an embodiment of the present application;

[0026] Figure 4 A schematic diagram of the timing relationship between risk control approval and contract confirmation provided in an embodiment of this application;

[0027] Figure 5 A schematic diagram of the credit review and approval process provided for an embodiment of this application;

[0028] Figure 6 A schematic diagram of the payment approval process provided for an embodiment of this application;

[0029] Figure 7 A schematic diagram of the relationship between the use of seals and the timing of loan disbursement provided in the embodiment of this application;

[0030] Figure 8 A schematic diagram of the structure of a joint leasing scheduling device provided in an embodiment of the present application;

[0031] Figure 9 A schematic diagram of the computer device structure provided in an embodiment of the present application. DETAILED DESCRIPTION

[0032] The present application will be described in detail below with reference to the accompanying drawings and in combination with embodiments. It should be noted that, unless there is a conflict, the embodiments and features in the embodiments of the present application can be combined with each other.

[0033] In some embodiments of this application, the joint leasing scheduling method can be applied to a vehicle leasing system. A vehicle leasing system is an online business system built for the vehicle leasing business, also known as a vehicle leasing platform. Vehicle leasing is a service that transfers the right to use a vehicle to a lessee for a specific period of time, and can be used to meet the lessee's temporary vehicle needs.

[0034] In some embodiments, the vehicle rental platform is an online platform with a server-client architecture. It enables the transfer of data, information, and instructions between lessees and managers to meet the interactive needs of the rental business. The vehicle rental platform can be used to perform business activities such as vehicle management, customer management, order management, billing management, and data analysis and reporting. For example, in the commercial vehicle business scenario, the commercial vehicle rental platform can receive rental applications from lessees and send a business list to the manager based on the rental application. After the manager completes the business approval, the platform verifies the payment transaction, thus enabling the commercial vehicle rental business.

[0035] In order to increase the scale and penetration rate of commercial vehicle leasing business, the operation and management of vehicle leasing business can also cooperate with other manufacturers to jointly lease and form a joint leasing business. In order to meet the data processing needs of the joint leasing business, a joint leasing platform can also be established. Figure 1 As shown, in some embodiments, the joint leasing platform may include a leasing business system and a joint business system. The leasing business system is a business system built by the leasing business operation and management party, while the joint business system is a business system built by other vendors. The leasing business system and the joint business system can establish a communication connection to enable data sharing and collaborative business data processing.

[0036] For example, a joint leasing platform is an online business platform jointly established by leasing business operator A and commercial vehicle manufacturer B. When a lessee places a vehicle leasing order for manufacturer B in operator A's leasing business system, they can first undergo business approval in operator A's leasing business system. Once approved by operator A's leasing business system, the leasing order is sent to manufacturer B's joint leasing system, which then undergoes further business approval. Once both the leasing business system and the joint leasing system have passed approval, operator A and manufacturer B jointly execute the leasing business.

[0037] However, due to the lack of unified interface management, various nodes in the commercial vehicle rental system may adopt different interface standards or protocols. This results in fragmented interfaces and makes unified management difficult, impacting system scalability and maintenance efficiency. Furthermore, due to the high degree of coupling between different business systems, business logic conversion and data processing are decentralized across various nodes, leading to strong interdependence between systems and making independent optimization or expansion difficult. Each business system may need to independently handle the logical conversion of order query information interfaces, resulting in code redundancy and repeated development, increasing maintenance costs. Furthermore, the commercial vehicle rental system lacks a unified logging and exception warning mechanism, making problem troubleshooting difficult and impacting system reliability and stability.

[0038] In order to solve the problem of low operation and maintenance efficiency of commercial vehicle leasing system, some embodiments of this application provide a joint leasing scheduling method, such as Figure 2 As shown, the method can be applied to a joint leasing platform, which may include a leasing business system, a joint business system, and a dispatch center. Accordingly, the method is specifically applied to the dispatch center of the joint leasing platform. In the joint leasing platform, the dispatch center establishes a communication connection with the leasing business system. The dispatch center also establishes a communication connection with the joint business system through front-end services to enable data sharing and collaborative processing between the leasing business system and the joint business system.

[0039] For example, a joint leasing platform formed by management party A and manufacturer B can pre-agree on orders, channels, products, and credit authorization methods. Among them, orders can include vehicle models, vehicle classification, guarantee methods, docking methods, order financing, etc. For example, the lessee can initiate an order including "heavy trucks - new vehicles - no guarantee - private - non-order financing" in the leasing business system of management party A. As a joint leasing channel of manufacturer B and management party A, the channel can be an independent network access channel, so it is a self-owned order channel without an input channel. The products of the joint leasing are independent joint leasing products. Credit authorization can support credit authorization for joint leasing and regular orders. If a joint leasing order is rejected by either party's risk control, it cannot be converted into a regular order, and vice versa.

[0040] The dispatch center, as the executive body of the joint leasing dispatch method, can be specifically deployed as an electronic device with data processing and communication capabilities. The electronic devices include but are not limited to computers, servers, mobile terminals, smart wearable devices, industrial control machines, online units, etc. For ease of description, the dispatch center is used as the executive body of the method in the embodiment of the present application. It should be understood that the method can also be applied to other types of executive bodies, which are no longer shown one by one in the embodiment of the present application. Figure 3 As shown, the method includes:

[0041] S101. In response to a leasing business submission instruction, detect current business demand information.

[0042] During operation, the joint leasing platform can interact with users through at least one of the leasing business system and the joint business system. A lessee can initiate a leasing business based on the leasing business system or the joint business system by sending a leasing business submission instruction to the leasing business system or the joint business system. The leasing business submission instruction is the instruction transmitted by the leasing business system to the dispatch center when submitting a request. In some embodiments, the leasing business submission instruction can also be the instruction transmitted by the joint business system to the dispatch center when submitting a request.

[0043] Leasing business submission instructions can be generated from business orders received by the lessee or manager. Specifically, when conducting vehicle leasing business, the lessee or manager can submit an order to the joint leasing platform. Upon receiving the submitted order, the leasing business system extracts the order information and generates a leasing business submission instruction based on it. The generated leasing business instruction can then be transmitted by the leasing business system to the joint leasing platform's dispatch center for unified management.

[0044] For example, when initiating a vehicle leasing business, the lessee or manager can enter basic order information through the order submission interface. This basic order information can include business models, such as joint leasing and conventional leasing. When selecting the joint leasing business model, you also need to select the joint leasing party, such as Manufacturer B. You must also set the regional group, business line, credit guarantee type, credit grantor, guarantee liability type, performance ownership structure, performance ownership, whether to finance the order, product type, vehicle classification, lease type, transfer type, whether to pre-register, payment method, mortgage model, contract version, signing method, whether to innovate the business, and funding source.

[0045] Basic order information can be entered through different terminal devices (clients), and the order submission interface displays differently on different types of terminal devices. For example, when the terminal device is a mobile device such as a mobile phone, the basic order information may be displayed as multiple selectable items arranged vertically. On the other hand, when the terminal device is a personal computer, the basic order information may be displayed as multiple selectable items arranged in a rectangular array.

[0046] Basic order information also supports multiple order entry methods. For example, order entry methods include pre-approval submission to APP & PC and direct submission to APP & PC, enabling unified order formats for heavy trucks, light trucks, and used vehicles. Furthermore, orders submitted as joint leasing business orders can be cloned, split, and used for single-link financing.

[0047] After receiving a rental business submission instruction, the dispatch center can respond to the instruction and detect current business demand information. Current business demand information is information that characterizes the business processing software and hardware requirements, determined based on the basic order information of the currently submitted order. In some embodiments, to detect current business demand information, after receiving the rental business submission instruction, the dispatch center can parse the basic order information from the instruction and read business demand-related items from the order information. Business demand-related items refer to information items within the basic order information that have specific requirements.

[0048] For example, when the basic order information includes user-defined items such as the business model, credit guarantee type, product type, and contract signing method, these items are referred to as business requirement-related items, as different content in these items will require different subsequent business processing methods. After receiving the rental business submission instruction, the dispatch center can read the basic order information from the instruction and extract the aforementioned information items from the basic order information to detect business requirement information.

[0049] In some embodiments, current business demand information can also be determined by monitoring current system operating parameters. For example, if the order submission time falls during the joint leasing platform's business data batching process, the joint leasing platform's business data batching process requires data processing resources. Therefore, after receiving the leasing business submission instruction, the current joint leasing platform's operating load can be monitored and the business demand information can be determined based on the operating load.

[0050] S102: Match a target processing strategy according to the current business demand information.

[0051] After detecting the current business demand information, the dispatch center can match the current business demand information among the pre-configured multiple processing strategies to determine the target processing strategy. The target processing strategy is one of the multiple processing strategies pre-configured in the dispatch center, that is, the processing strategy that meets the current business demand information among the multiple processing strategies.

[0052] For example, when the business model included in the basic information of the order is a joint leasing model, since the joint leasing model requires the joint business system to participate in the approval and processing of business data, the target processing strategy for achieving joint data approval and processing can be matched among multiple processing strategies.

[0053] In some embodiments, to match a target processing strategy, the dispatch center may, after obtaining current business demand information, extract business demand-related items from the current business information and generate a set of related items. Within the set of related items, multiple business demand-related items are sorted according to a preset business priority. Based on the business priority, processing strategies are then gradually filtered based on the business demand-related items in the set of related items to generate a multi-level set of candidate strategies, thereby selecting a target processing strategy from the set of candidate strategies.

[0054] For example, if the current business requirement information includes items such as business model, credit guarantee type, product type, and contract signing method, the dispatch center can first read the business model to determine a set of candidate strategies that meet the joint leasing model under the current business model, namely {Strategy 1, Strategy 2, ..., Strategy N}. Then, based on the credit guarantee type, it can determine a set of candidate strategies that meet the current credit guarantee type of no guarantee, namely {Strategy 2, Strategy 3, ..., Strategy N}. Similarly, the candidate set is gradually screened through multiple business requirement-related items to determine the target processing strategy that meets all business requirement-related items.

[0055] S103: Acquire business data based on the target processing strategy.

[0056] After obtaining the target processing strategy through matching, the dispatch center can obtain business data based on the target processing strategy. The business data is data generated by the leasing business system based on the leasing business submission instruction; the business data includes one or more combinations of credit review data, contract confirmation data, payment approval data, seal document data, and loan status data.

[0057] The data contained in business data can be generated and retrieved sequentially based on the approval and processing processes of the leasing business system and the joint business system. Specifically, after receiving a submitted order, the joint leasing platform can sequentially process risk control approval, contract confirmation, payment approval, and lease initiation, among other related data processing steps. The existence and content of each data processing step can be determined by the preceding processes. This means that credit review data can be generated during the risk control and approval process. This credit review data then influences the contract confirmation process, specifically the generation of contract confirmation data.

[0058] Business data can be generated by the leasing business system or the joint business system. To obtain business data, in some embodiments, the dispatch center can, after determining a target processing strategy, send a data acquisition request to the target business system based on the target processing strategy. The target business system is at least one of the leasing business system and the joint business system. After sending the data acquisition request to the target business system, the target business system can respond to the data acquisition request by extracting business data from the database and sending the business data to the dispatch center. The dispatch center can then obtain the business data by receiving the business data fed back by the target business system.

[0059] Obviously, to adapt to the business data generation process, the dispatch center can send multiple data acquisition requests to the target business system in sequence according to the current business processing progress. For example, after the dispatch center sends a data acquisition request to the target business system to obtain credit review data and obtains the credit review data, the dispatch center can monitor the approval progress of the credit review data and, after the credit review data is approved, send a data acquisition request to the target business system to obtain contract confirmation data.

[0060] S104: delivering the business data to the joint business system through the front-end service, and pushing the business approval conclusion of the joint business system based on the business data feedback to the leasing business system.

[0061] After acquiring the business data, the dispatch center can transmit it to the joint business system through front-end services, allowing the joint business system to perform business approval on the business data. After performing business approval, the joint business system can provide feedback to the dispatch center regarding the business approval conclusion. The dispatch center can then receive the business approval conclusion provided by the joint business system based on the business data and push it to the leasing business system, thus enabling data transfer between the leasing business system and the joint business system.

[0062] During the data transmission process, the dispatch center can also record business data and business approval conclusions, and organize the recorded data into a formatted data form to provide log data for the leasing business system and the joint business system.

[0063] like Figure 4 As shown, in some embodiments, when the joint leasing platform conducts risk control approval, the dispatch center can first extract credit review data from the business data when executing the transmission of the business data to the joint business system through the front-end service, and when pushing the business approval conclusion of the joint business system based on the business data feedback to the leasing business system. The credit review data is the credit review information and credit review documents obtained by the leasing business system through the risk control approval interface when submitting the application. In some embodiments, during the risk control approval process, the dispatch center can first obtain the order identification information of the joint leasing order associated with the credit review data, and set the joint leasing order to a suspended state.

[0064] like Figure 5 As shown, after extracting the credit review data, the dispatch center can transmit the credit review data to the joint business system through the front-end service, receive the credit review and approval conclusion, and push the credit review and approval conclusion to the leasing business system. The credit review and approval conclusion is the conclusion information fed back by the joint business system based on the credit review data. Credit review log data is then generated based on the credit review data and the approval conclusion.

[0065] After receiving the credit review and approval conclusion, the dispatch center can read the credit review and approval status from the credit review and approval conclusion. The credit review and approval status can be either a credit review pass or a credit review fail status. The credit review pass status is the approval conclusion generated by the joint business system after an initial credit review pass or a reconsideration credit review pass. The credit review fail status is the approval conclusion generated by the joint business system after a reconsideration credit review fail. Based on the read credit review and approval status, if the credit review and approval status is a credit review pass status, first push data can be generated based on the order identification information and the first field combination, and the first push data can be sent to the leasing business system and the front-end service.

[0066] For example, for joint leasing orders, the dispatch center can add two new statuses to the risk control approval node: joint leasing credit review approval status and joint leasing credit review rejection status. The joint leasing credit review rejection status can be considered a final status, meaning it cannot be reviewed again. After extracting the credit review data, the dispatch center can suspend the joint leasing order corresponding to the credit review data. Upon receiving the risk control approval conclusion, the dispatch center will determine whether to push the order to the front-end service platform based on the credit review approval status in the credit review approval conclusion.

[0067] In any scenario, as long as the credit review and approval status in the credit review and approval conclusion is passed, it will be pushed to the front-end service platform. For example, according to the credit review and approval conclusion, when the approval result meets the order (including cloned orders) and the first credit review is passed or the order is reviewed and passed, the data can be pushed to the front-end service. The data pushed to the front-end service platform may include a first field combination, and the first field combination may include fields such as the management party order number, the capital party approval node, the capital party approval conclusion, and the capital party approval details. For example, in the first pushed data, the management party order number is PAZL××00001; the capital party approval node is credit review and approval; and the capital party approval conclusion is approved.

[0068] If the credit review and approval status is a credit review failure status, second push data is generated according to the order identification information and the second field combination, and the second push data is sent to the leasing business system.

[0069] For example, based on the credit review and approval conclusion, if the current order is determined to have been rejected by the first credit review, rejected again after reconsideration, or returned by risk control, the data push to the front-end service can be canceled, and a second push data can be pushed to the leasing business system. The second push data can also include fields such as the management party order number, the investor approval node, the investor approval conclusion, and the investor approval details. For example, in the second push data, the management party order number is PAZL××00002; the investor approval node is credit review approval; and the investor approval conclusion is approval rejection.

[0070] After receiving the credit review and approval conclusion from the joint business system, the dispatch center can modify the order status of the joint leasing order based on the credit review and approval conclusion. For example, after receiving the credit review and approval conclusion from Manufacturer B's joint business system, the dispatch center can set the order status of Manufacturer B's joint leasing order to "Joint leasing credit review and approval passed" and display it in the approved list.

[0071] That is, in some embodiments, the client can also display a credit review and approval list page. After the administrator approves the order credit review or skips the risk control node and pushes it to the joint lessee, the order status enters the "joint lessee credit review and approval" status, and the status of each order line on the credit review and approval list page is displayed as: "Joint lessee credit review and approval". After the joint lessee credit review and approval is completed and pushed to the administrator's leasing business system, it can receive BAPP displays of different statuses. For example, in the approval rejection status, the status of each order line in the credit review and approval list page can be displayed as: "Joint lessee credit review rejection"; and in the approval approval status, the status of each order line in the credit review and approval list page can be displayed as: "Joint lessee credit review passed".

[0072] In some embodiments, the scheduling center can record the new node of the joint lease approval through the historical record, and display the historical record on the client by providing an order details page. After the management party pushes the order to the joint tenant after the credit review and approval is passed, the order status of the order can be set to the "joint tenant credit review and approval" status, which is classified as the credit review and approval in the order list. When the credit review and approval conclusion is the credit review rejection status, the scheduling system can set the order status to the "joint tenant credit review rejection" status, which is classified as the credit review rejection in the order list. When the credit review and approval conclusion is the credit review approval status, the scheduling system can set the order status to the "contract confirmation" status, but add the "joint tenant approval approval" node to the approval history record, which is classified as the credit review approval in the order list. For the approval record, the scheduling center can add approval records on both the application (APP) side and the client (such as the PC side), and add the approval record of the joint tenant, and the default processor is "system".

[0073] After executing risk control approval and the risk control approval conclusion is approved, the dispatch center can perform contract confirmation. Specifically, when the dispatch center transmits the business data to the joint business system via the front-end service and pushes the business approval conclusion of the joint business system based on the business data to the leasing business system, it can first extract the contract confirmation data from the business data. The contract confirmation data is generated by the leasing business system based on the risk control approval conclusion. The contract confirmation status of the leasing business system is then determined based on the contract confirmation data, which can be either approved or rejected. If the contract confirmation status is rejected, the contract confirmation status is transmitted to the joint business system via the front-end service. If the contract confirmation status is approved, the contract confirmation status is transmitted to the joint business system via the front-end service. The dispatch center also obtains the electronic signing result and generates contract log data based on the electronic signing result. The electronic signing result is the identification information generated after the electronic signing between the leasing business system and the joint business system.

[0074] For example, to accommodate the needs of joint leasing, the dispatch center can add a unified contract confirmation node for both regular and joint leasing orders. Within the corresponding business processing node, the administrator can confirm the contract through the contract confirmation interface. This interface can include vehicle information, such as whether the vehicle is a light truck, the license plate is a blue plate, the pricing scheme is damage pricing, and the license plate city is AA province or BB city.

[0075] The contract confirmation interface can also be used to present additional information beyond the basic vehicle information, such as modifications and additions, the name of the actual seller of the vehicle, the name of the accessories seller, etc. Different information can be set with different operation methods and applicable situations. For example, the name of the modifications and additions is a required and editable field, and the specific name can be selected through the drop-down list control. The pricing plan for a single project is displayed when it is: "Accessories Financing" or "Vehicle Model Library Pricing-Accessories Financing", supports the entry of multiple companies, and cannot be repeatedly selected during verification.

[0076] The number of modifications and additions is also a required and editable field, and the specific field content can be entered through the input control. It is displayed when the pricing plan of the individual project is "Accessories Financing" or "Model Library Pricing-Accessories Financing", and it also supports entering multiple companies. The name of the actual seller of the vehicle is a required and editable field, and the specific field content can be entered through the input control. It is displayed when the vehicle classification of the individual project is a used car. The actual seller name of the vehicle can be entered manually, and multiple entries can be added, but they cannot be entered repeatedly.

[0077] The name of the accessories seller is a required and editable field. Specific field content can be entered through the input control. It will be displayed when "Accessory Financing" or "Vehicle Library Pricing - Accessory Financing" is selected as the pricing plan. It supports entering multiple parties and manual input, and cannot be entered repeatedly.

[0078] After the user confirms the contract through the contract confirmation interface of the leasing business system, contract confirmation data can be generated based on the contract confirmation result of the leasing business system and pushed to the joint business system, allowing the joint business system to process the contract confirmation status of the current order. In some embodiments, the dispatch center can push the contract confirmation data to the front-end service when the leasing business system submits the contract confirmation, and push it to the front-end service when the contract confirmation is returned, so as to transmit the contract confirmation data to the joint business system.

[0079] When the dispatch center pushes contract confirmation data to the joint business system, it can achieve this by combining fields associated with the contract confirmation. For example, this field combination could include the administrator's order number and the contract confirmation status. The Ping An order number is a string combination based on order numbering rules, such as PAZL××00002. The contract confirmation status could include specific information such as contract confirmation return or contract confirmation.

[0080] To improve the contract confirmation process, the dispatch center can also define variables involved in the lease contract through backend management, contract configuration, and the variable library. For example, variables can include capital contribution ratio, information confirmation form - vehicle purchase price, information confirmation form - purchase tax, information confirmation form - insurance premium, information confirmation form - accessories amount, vehicle seller, accessories seller, total amount due, repayment plan, name of modified and added items (per category), and quantity of modified and added items (per category). Among them, the investment ratio can be displayed according to the investment ratio displayed at the time of submission; Information Confirmation-Purchase Price is the total purchase price of all vehicles in a single contract, which can be displayed at the purchase price corresponding to the vehicle information; Information Confirmation-Purchase Tax is the total purchase tax of all vehicles in a single contract, that is, through purchase price * quantity (total of all types), which can be displayed through Vehicle Information-Purchase Tax; Information Confirmation-Insurance Premium is the total insurance premium of all vehicles in a single contract, and can also be displayed through Vehicle Information-Purchase Tax; Information Confirmation-Accessory Amount is the total accessory invoice financing amount of all vehicles in a single contract, which can be displayed through All Purchase Prices-Invoice Amount; The vehicle seller can take the name of the invoice issuer when the vehicle is classified as a new car, and take the name of the actual seller entered when the vehicle is classified as a used car; the accessory seller takes the name of the accessory seller entered.

[0081] The total amount payable is the total amount that the lessee needs to repay, that is, the lessee's deposit + total rent + retention price; the repayment plan format is that the first installment payable is RMB (first installment rent) ×× yuan, during the (first stage) period, the payable for each installment is RMB (first stage repayment amount) yuan, during the (second stage) period, the payable for each installment is RMB (second stage repayment amount) yuan, during the (third stage) period, the payable for each installment is RMB (third stage repayment amount) yuan... The last installment (that is, the (last installment number) period) payable is RMB (last installment rent + retention price of all vehicles) yuan.

[0082] The name of the modified and added object (single type) can be generated based on the accessories selected when the single project contract is confirmed; the quantity of the modified and added object (single type) can be generated based on the accessories selected when the single project contract is confirmed.

[0083] In addition to the aforementioned contract elements, the contract confirmation interface also displays rule judgment parameters. For example, rule judgment parameters may include generating rules for business model, joint lessee, role, project type, etc. Enumeration values ​​for business model may include conventional lease and joint lease; enumeration values ​​for joint lessee may include the joint lease name, such as FAW Fujie; enumeration values ​​for role may include actual user; and enumeration values ​​for project type may include natural person V1, natural person V2, legal person, legal person, etc.

[0084] When the contract confirmation is executed and the contract confirmation approval conclusion is approved, the dispatch center can execute the payment approval. Figure 6 As shown, in some embodiments, when the dispatch center transmits the business data to the joint business system via the front-end service and pushes the business approval conclusion feedbacked by the joint business system based on the business data to the leasing business system, the dispatch center can extract the payment approval data from the business data. The payment approval data includes the payment request information and payment request documents generated by the leasing business system in response to the payment request instruction after executing the electronic contract. The payment approval data is then transmitted to the joint business system via the front-end service, so that the joint business system performs payment request approval based on the payment approval data. The dispatch center then receives the payment request approval conclusion feedbacked by the joint business system and sends it to the leasing business system, thereby generating payment request log data based on the payment request approval conclusion. The payment request approval conclusion can be either a payment request approved or a payment request rejected.

[0085] For example, after a submitted order passes risk control approval and contract confirmation, the dispatch center can set the submitted order to a pending payment status, and the leasing business system of management party A will first conduct payment approval. If the payment approval is rejected, the leasing business system can return the payment approval, receive the revised order information submitted by the client, and then conduct payment approval again. After the payment approval is passed, payment approval data can be generated based on the approval results and sent to the joint business system of manufacturer B, which will then conduct payment approval again. If the payment approval is passed, the current submitted order is set to a pending payment status. If the payment approval is rejected, the current submitted order is set to a payment approval rejected status, thus ending the payment approval process.

[0086] Therefore, the dispatch center can add two new statuses to the joint leasing order risk control approval node: Joint Leasing Payment Approved and Joint Leasing Payment Approval Rejected (Final Status). After the final payment approval node (model approval, business approval, and final payment review) passes, the fields, images, and status are pushed to the joint business system. The system then receives feedback on the payment approval conclusion, indicating either a payment approval approved or a payment approval rejected status.

[0087] When transmitting payment approval data to the joint business system through front-end services, the dispatch center can also define push data based on the payment approval data. For example, the push data may include fields such as the management party's order number, the investor's approval node, the investor's approval conclusion, and the investor's approval details. The enumerated values ​​of the investor's approval node can include credit approval, payment approval, etc.; the investor's approval conclusion can include approval results such as approved and rejected; and the investor's approval details can transmit the rejection reason when the approval is rejected.

[0088] After receiving payment approval confirmation from the joint business system, the dispatch center can set the joint leasing order to the payment waiting stage and simultaneously send a payment trigger command to both the leasing business system and the joint business system to control the client's display of the payment approval list page. For example, after the administrator's order payment approval is pushed to the joint leasing party, the order enters the "Joint Leasing Party Payment Approval" state, with each order row displayed as "Joint Leasing Payment Approval." Users can click on any order in the payment approval list page to access the order details page. Furthermore, after the administrator's order payment approval is pushed to the joint leasing party, the order enters the "Joint Leasing Party Payment Approval" state.

[0089] When payment approval is rejected, the dispatch center can cancel the order directly, but the historical record will show the joint lessee's payment rejection. The approval record for the joint lessee can be added to the approval history, with the default personnel set to "system." The dispatch center can define operational approval policies through the backend system, operational configuration, and operational approval policies. Defined operational approval policies can be modified for all orders with certain requirements. For example, a new operational approval policy can be added through operational configuration, with the first type of approval policy being the lessee; the second type of policy being the financial lease information confirmation letter, which is classified as the contract's operational approval policy.

[0090] Accordingly, through operational configuration, new policy configuration information fields can be added. For example, if the configuration type is a system field, the corresponding file name or field name can be business model, joint lessor, name of modified and added object, quantity of modified and added objects, name of the actual vehicle seller, name of the accessories seller, etc. Different policy configuration information fields can have different type classifications. For example, the type classifications of business model and joint lessor are system fields for product information; the type classifications of modified and added object name, quantity of modified and added objects, name of the actual vehicle seller, and name of the accessories seller are basic project information.

[0091] When payment approval is executed and the payment approval result is passed, the dispatch center can start the rental business. Figure 7 As shown, when the dispatch center transmits the business data to the joint business system via the front-end service and pushes the business approval conclusion fed back by the joint business system based on the business data to the leasing business system, it can first extract the seal file data from the business data. The seal file data is the file generated by the leasing business system when the payment request approval conclusion is approval. The dispatch center then transmits the seal file data to the joint business system via the front-end service, so that the joint business system executes the seal application on the seal file data. The dispatch center then receives the joint seal application data fed back by the joint business system and sends the joint seal application data to the leasing business system, thereby generating seal application log data based on the joint seal application data.

[0092] For example, after the dispatch center determines that the payment has been approved based on the payment approval conclusion, it can set the order node as the waiting payment node. The waiting payment node can be set with corresponding judgment logic, that is, based on the judgment conditions such as GPS installation status and lease start date, a new judgment condition is added to determine whether both parties have completed the contract and passed the signature verification. If all conditions are met, the project lease process can be carried out; if the original judgment conditions such as GPS installation status and lease start date are not met, the condition test can be performed through prompts or waiting for a set period until all judgment conditions are met; if the contract between the two parties is not completed or the signature verification is not passed, it will automatically return to the contract confirmation node for manual operation and offline communication. For the lease process, the status of each node in the return scenario can be recorded through historical records. If there is no human approval, the default display is "system". It is also possible to increase the display of abnormal nodes and the transmission of information within the site.

[0093] When an order reaches the stage where both parties sign and wait for payment, the contract can be signed first by the management party's leasing business system. After the contract is signed, the text will be transmitted to the joint business system. After the joint business system completes the contract, it will be transmitted back to the leasing business system for signature verification. During the signing and verification process, the dispatch center can achieve data transmission by pushing data. That is, the pushed data includes basic information such as the management party's order number, as well as contract list information such as contract type code, contract name, file key, etc. Among them, the contract type code can include a list of contracts that need to be signed by the joint business parties, such as the main financial leasing contract, company confirmation letter, etc.

[0094] The dispatch center receives joint seal data from the joint business system, which can include basic information such as the order number, electronic signing result (successful or failed), and the reason for the failure. It can also include a list of contracts sealed by the joint lessee, such as the contract type code, contract name, and file key.

[0095] In some embodiments, when the dispatch center transmits the business data to the joint business system via the front-end service and pushes the business approval conclusion of the joint business system based on the business data to the leasing business system, it may first extract the loan status data from the business data. The loan status data includes one or more combinations of loan information status, loan result files, repayment plan files, repayment result files, and overdue result files. The dispatch center then transmits the loan status data to the joint business system via the front-end service and generates loan log data based on the loan status data.

[0096] For example, during the lease initiation process, the dispatch center can call the product module to perform joint lease calculations. The returned repayment schedule, cash flow, and income and expenditure schedule are divided into "general table," "manager table," and "joint tenant table." Loan disbursement information and status are then pushed to the joint tenants via push notifications. This push notification information can include fields such as the manager order number, manager contract number, disbursement date, and terminal price, forming the loan status data. A T+1 day push notification can also be generated for the T-day loan disbursement results and repayment schedule.

[0097] S105: Setting a log recording interface according to the business data and the business approval conclusion.

[0098] Since the dispatching center can also record business data and business approval conclusions during the data transmission process, and organize the recorded data into formatted data form to provide log data for the leasing business system and the joint business system, the dispatching center can also set up a log recording interface based on the business data and the business approval conclusion after transmitting the business data, wherein the log recording interface is used to provide log data for the leasing business system and the joint business system.

[0099] In other words, the joint leasing platform, while introducing a dispatch center and achieving unified interface management, can also centralize logging functions in the dispatch center through a unified logging and early warning mechanism, facilitating subsequent problem tracing and data analysis. This unified early warning function allows for timely detection and handling of system anomalies, improving system robustness and availability.

[0100] By applying the technical solutions of the above embodiments, the joint leasing scheduling method described in the above embodiments realizes unified interface management by introducing a scheduling center module. The scheduling center serves as a unified entrance, integrating and distributing interfaces of various scenarios, reducing the dispersion and complexity of interfaces, improving the standardization and maintainability of the system, and providing a unified order query information interface to avoid multiple business systems from developing and maintaining related logic separately. The method can also reduce the degree of coupling and realize a "zero-intrusion" design, that is, through the strategy pattern (Strategy Pattern) and Handler processing method, the business logic conversion is centralized in the scheduling center, reducing the direct dependency between business systems, making the system more flexible and easy to expand. The uncoupled design concept ensures that each business system can run and upgrade independently, and will not cause compatibility problems due to changes in other systems. The method can also enhance the flexibility and scalability of the system, that is, the scheduling center supports multiple processing strategies and can be dynamically adjusted according to actual needs to meet the business needs in different scenarios. A new joint party (Facade) mode is added to simplify the access process of external systems and improve user experience.

[0101] The method can unify the logging and early warning mechanisms, centrally processing the logging function in the dispatch center to facilitate subsequent problem tracing and data analysis. It can achieve a unified early warning function, timely detect and handle system anomalies, and improve the robustness and availability of the system. It can also reduce duplicate development and lower costs. By centralizing business logic conversion in the dispatch center, it avoids repeated development of the same functional modules in various business systems, saving development time and resource investment. In addition, the method can also improve the maintainability and testability of the joint leasing platform. That is, through unified interface management and centralized logic processing, the complexity of the system is reduced, facilitating subsequent maintenance and upgrades. It is easy to perform unit testing and integration testing on the dispatch center to ensure high-quality delivery of the system.

[0102] In some embodiments, as a specific implementation of the joint leasing scheduling method described in the above embodiments, some embodiments of the present application also provide a joint leasing scheduling device, such as Figure 8 As shown, the device can be applied to a dispatching center, the dispatching center establishes a communication connection with a leasing business system, and the dispatching center also establishes a communication connection with a joint business system through a front-end service; the device includes:

[0103] a demand detection module, configured to detect current business demand information in response to a leasing business submission instruction, wherein the leasing business submission instruction is an instruction transmitted by the leasing business system to the dispatch center when submitting a submission;

[0104] a strategy matching module, configured to match a target processing strategy according to the current business demand information, wherein the target processing strategy is one of a plurality of processing strategies pre-configured in the dispatching center;

[0105] a business data acquisition module, configured to acquire business data based on the target processing strategy, wherein the business data is data generated by the leasing business system according to the leasing business submission instruction; the business data includes one or more combinations of credit review data, contract confirmation data, payment approval data, seal document data, and loan status data;

[0106] A data push module, configured to transmit the business data to the joint business system through the front-end service, and to push the business approval conclusion of the joint business system based on the business data feedback to the leasing business system;

[0107] The interface setting module is used to set a log recording interface according to the business data and the business approval conclusion, and the log recording interface is used to provide log data for the leasing business system and the joint business system.

[0108] It should be noted that for other corresponding descriptions of the functional units involved in a joint leasing scheduling device provided in an embodiment of the present application, reference can be made to the corresponding descriptions in the joint leasing scheduling method provided in the above embodiment, and will not be repeated here.

[0109] like Figure 9 As shown, an embodiment of the present application also provides a computer device, which can be specifically a personal computer, a server, a network device, etc. The computer device includes a bus, a processor, a memory and a communication interface, and may also include an input and output interface and a display device. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and computer program in the non-volatile storage medium. The database of the computer device is used to store location information. The network interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, the steps in each method embodiment are implemented.

[0110] Those skilled in the art will understand that the structure of the above-mentioned computer device is only a partial structure related to the solution of the present application and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components, or combine certain components, or have a different component arrangement.

[0111] In one embodiment, a computer-readable storage medium is further provided. The computer-readable storage medium may be non-volatile or volatile, and stores a computer program thereon. When the computer program is executed by a processor, the steps in the above-mentioned method embodiments are implemented.

[0112] In one embodiment, a computer program product is further provided, including a computer program, which implements the steps in the above method embodiments when executed by a processor.

[0113] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties.

[0114] Those skilled in the art will understand that all or part of the processes in the above-mentioned embodiment methods can be implemented by instructing related hardware through a computer program. The computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods.

[0115] Among them, any reference to memory, database or other media used in the embodiments provided in this application may include at least one of non-volatile and volatile memory. Non-volatile memory may include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical storage, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc.

[0116] Volatile memory may include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM may be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM).

[0117] The database involved in each embodiment provided herein may include at least one of a relational database and a non-relational database. Non-relational databases may include, but are not limited to, distributed databases based on blockchain. The processor involved in each embodiment provided herein may be, but is not limited to, a general-purpose processor, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, and the like.

[0118] The technical features of the above embodiments can be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0119] The above-described embodiments merely represent several implementation methods of the present application. While the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the present application. It should be noted that a person of ordinary skill in the art may make various modifications and improvements without departing from the spirit of the present application, and these modifications and improvements fall within the scope of protection of the present application. Therefore, the scope of protection of the present application shall be determined by the appended claims.

Claims

1. A joint leasing scheduling method, characterized in that: Applied to a dispatching center, the dispatching center establishes a communication connection with a leasing business system, and the dispatching center also establishes a communication connection with a joint business system through a front-end service; the method includes: detecting current business demand information in response to a leasing business submission instruction, wherein the leasing business submission instruction is an instruction transmitted by the leasing business system to the dispatch center when submitting a submission; Matching a target processing strategy according to the current business demand information, wherein the target processing strategy is one of multiple processing strategies pre-configured in the dispatch center; Acquiring business data based on the target processing strategy, wherein the business data is data generated by the leasing business system according to the leasing business submission instruction; the business data includes one or more combinations of credit review data, contract confirmation data, payment approval data, seal document data, and loan status data; The business data is transmitted to the joint business system through the front-end service, and the business approval conclusion of the joint business system based on the business data feedback is pushed to the leasing business system; A log recording interface is set according to the business data and the business approval conclusion, and the log recording interface is used to provide log data for the leasing business system and the joint business system.

2. The method according to claim 1, characterized in that The process of transmitting the business data to the joint business system through the front-end service, and pushing the business approval conclusion of the joint business system based on the business data feedback to the leasing business system, includes: Extracting credit review data from the business data, wherein the credit review data is the credit review information and credit review documents obtained by the leasing business system through the risk control approval interface when submitting a submission; delivering the credit review data to the joint business system through the front-end service; Receiving a credit review and approval conclusion, and pushing the credit review and approval conclusion to the leasing business system, wherein the credit review and approval conclusion is conclusion information fed back by the joint business system based on the credit review data; Generate credit review log data based on the credit review data and the approval conclusion.

3. The method according to claim 2, characterized in that The process of transmitting the business data to the joint business system through the front-end service, and pushing the business approval conclusion of the joint business system based on the business data feedback to the leasing business system, includes: Extracting the contract confirmation data from the business data, the contract confirmation data being data generated by the leasing business system according to the credit review and approval conclusion; Determining the contract confirmation status of the leasing business system according to the contract confirmation data, wherein the contract confirmation status is a passed status or a returned status; If the contract confirmation status is a return status, the contract confirmation status is transmitted to the joint business system through the front-end service; If the contract confirmation status is passed, the contract confirmation status is passed to the joint business system through the front-end service, and the electronic signing result is obtained, and contract log data is generated based on the electronic signing result; the electronic signing result is the identification information generated after the leasing business system and the joint business system execute the electronic signing.

4. The method according to claim 3, characterized in that The process of transmitting the business data to the joint business system through the front-end service, and pushing the business approval conclusion of the joint business system based on the business data feedback to the leasing business system, includes: Extracting the payment approval data from the business data, the payment approval data including payment request information and payment request files generated by the leasing business system in response to the payment request instruction after executing the electronic contract signing; The payment approval data is transmitted to the joint business system through the front-end service, so that the joint business system performs payment request approval based on the payment approval data; receiving a payment request approval conclusion fed back by the joint business system, and sending the payment request approval conclusion to the leasing business system; the payment request approval conclusion is either payment request approval passed or payment request approval failed; Generate payment request log data based on the payment request approval conclusion.

5. The method according to claim 4, characterized in that The process of transmitting the business data to the joint business system through the front-end service, and pushing the business approval conclusion of the joint business system based on the business data feedback to the leasing business system, includes: Extracting the seal document data from the business data, the seal document data being a document generated by the leasing business system through the execution of the seal when the payment request approval conclusion is that the payment request is approved; The seal document data is transmitted to the joint business system through the front-end service, so that the joint business system executes the seal application for the seal document data; receiving the joint seal usage data fed back by the joint business system, and sending the joint seal usage data to the leasing business system; Seal usage log data is generated based on the joint seal usage data.

6. The method according to claim 5, characterized in that The process of transmitting the business data to the joint business system through the front-end service, and pushing the business approval conclusion of the joint business system based on the business data feedback to the leasing business system, includes: Extracting the loan status data from the business data, the loan status data including one or more combinations of loan information status, loan result file, repayment plan file, repayment result file, and overdue result file; Transmitting the loan status data to the joint business system through the front-end service; Generate loan log data based on the loan status data.

7. The method according to claim 2, characterized in that The process of transmitting the business data to the joint business system through the front-end service, and pushing the business approval conclusion of the joint business system based on the business data feedback to the leasing business system, includes: Obtaining order identification information of the joint rental order associated with the credit review data; Setting the joint rental order to a pending state; After receiving the credit review and approval conclusion, the credit review and approval status is read from the credit review and approval conclusion, where the credit review and approval status is a credit review passed status or a credit review failed status; the credit review passed status is an approval conclusion generated by the joint business system after the initial credit review passed or the reconsideration credit review passed; the credit review failed status is an approval conclusion generated by the joint business system after the reconsideration credit review failed; If the credit review and approval status is a credit review passed status, generating first push data according to the order identification information and the first field combination, and sending the first push data to the leasing business system and the front-end service; If the credit review and approval status is a credit review failure status, second push data is generated according to the order identification information and the second field combination, and the second push data is sent to the leasing business system.

8. A joint leasing scheduling device, characterized in that: Applied to a dispatching center, the dispatching center establishes a communication connection with a leasing business system, and the dispatching center also establishes a communication connection with a joint business system through a front-end service; the device includes: a demand detection module, configured to detect current business demand information in response to a leasing business submission instruction, wherein the leasing business submission instruction is an instruction transmitted by the leasing business system to the dispatch center when submitting a submission; a strategy matching module, configured to match a target processing strategy according to the current business demand information, wherein the target processing strategy is one of a plurality of processing strategies pre-configured in the dispatching center; a business data acquisition module, configured to acquire business data based on the target processing strategy, wherein the business data is data generated by the leasing business system according to the leasing business submission instruction; the business data includes one or more combinations of credit review data, contract confirmation data, payment approval data, seal document data, and loan status data; A data push module, configured to transmit the business data to the joint business system through the front-end service, and to push the business approval conclusion of the joint business system based on the business data feedback to the leasing business system; The interface setting module is used to set a log recording interface according to the business data and the business approval conclusion, and the log recording interface is used to provide log data for the leasing business system and the joint business system.

9. A computer device comprising a storage medium, a processor, and a computer program stored on the storage medium and executable on the processor, wherein: When the processor executes the computer program, the method according to any one of claims 1 to 7 is implemented.

10. A storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the method according to any one of claims 1 to 7 is implemented.

Images