Fund supervision system and method based on driving training industry
By designing a fund supervision system in the driver training industry, a closed-loop collaboration among students, driving schools, banks, and regulatory authorities is achieved, solving the problem of missing fund supervision, improving supervision efficiency and system scalability, and adapting to the industry's large-scale needs.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- WUHAN MUCANG TECH CO LTD
- Filing Date
- 2025-12-31
- Publication Date
- 2026-05-12
AI Technical Summary
The driver training industry suffers from a lack of financial oversight, manifested in problems such as driving schools absconding with funds, difficulties in refunding students, and instructors demanding bribes and kickbacks. Existing regulatory schemes have not formed a closed-loop collaborative mechanism among students, driving schools, banks, and regulatory authorities, and the system architecture has poor scalability, making it difficult to handle massive amounts of student data and cross-entity data interaction needs.
Design a fund supervision system for the driver training industry, including a client layer, a server layer, and a collaboration layer. A closed-loop collaboration among students, driving schools, banks, and regulatory authorities is achieved through an access control module. The server layer capabilities are extended using containers to adapt to different driving school system interfaces, thereby realizing full-process fund supervision.
It has enabled data connectivity among students, driving schools, banks, and regulatory authorities, improving the efficiency and security of fund supervision, adapting to the growth in the number of driving schools and the scale of students, and meeting the needs of large-scale industry applications.
Smart Images

Figure CN122022975A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the intersection of fund supervision technology and information technology in the driver training industry, and in particular to a fund supervision system and method based on the driver training industry. Background Technology
[0002] With the rapid development of the driver training industry, the number of driving schools has surged. However, the lack of financial supervision within the industry has become increasingly prominent, manifesting in problems such as driving schools absconding with funds, difficulties in student refunds, and instructors demanding bribes and kickbacks. These issues severely damage students' rights and disrupt industry order. To address these problems, the driver training industry urgently needs to establish a financial supervision system, but existing technology has the following key shortcomings: 1. Insufficient collaboration among multiple roles: The existing regulatory scheme has not formed a closed-loop collaboration mechanism among students, driving schools, banks, and regulatory authorities. Information is fragmented among the various entities, making it impossible for regulatory authorities to keep track of fund flows and training progress in real time. There are barriers to data exchange between banks, driving schools, and platforms, resulting in supervision becoming a mere formality.
[0003] 2. Poor system architecture scalability: Most existing driver training-related systems are designed for single functions (such as only handling registration or only recording training), which makes it difficult to handle massive amounts of student data, concurrent access from multiple driving schools, and cross-entity data interaction needs, and they cannot quickly adapt to changes in industry policies or business models.
[0004] Therefore, a new financial supervision system based on the driver training industry is urgently needed to solve the above problems. Summary of the Invention
[0005] In view of this, this application provides a fund supervision system and method based on the driver training industry, which can realize the coordination of the entire process of "registration-payment-training-disbursement-supervision", improve the efficiency of fund supervision, and also meet the access needs of multiple driving schools and a large number of students.
[0006] The first aspect of this application provides a fund supervision system based on the driver training industry. The architecture of the fund supervision system includes: a client layer, a server layer, and a collaboration layer. The server layer includes a main server, a first container for carrying business services, a second container for carrying data synchronization services, a third container for carrying interface adaptation services, and a fourth container for carrying fund supervision services. The client layer includes student-side devices, driving school-side devices, bank-side devices, and regulatory department-side devices that communicate with the server layer. The collaboration layer includes an access control module, which is used to configure tuition payment permissions for student-side devices and provide tuition payment permissions to driving school-side devices. The system includes permissions to report training progress and receive fund transfers, permissions to create fund supervision accounts and monitor fund inflows and outflows to the bank-side device, and permissions to supervise funds to the regulatory authority-side device. Specifically, the student-side device is used to transfer tuition fees paid by students into the fund supervision account. The driving school-side device is used to send the students' training progress to the collaboration layer for authenticity verification. After successfully verifying the authenticity of the training progress, the collaboration layer sends a fund transfer instruction to the bank-side device. The bank-side device then transfers funds from the fund supervision account to the driving school-side device according to the fund transfer instruction and sends the fund transfer result to the regulatory authority-side device.
[0007] In one possible implementation, the collaboration layer further includes a real-time data synchronization module; the driving school terminal device is also used to synchronously send the training progress to the student terminal device according to the real-time data synchronization module; the bank terminal device is also used to synchronously send the fund transfer result to the student terminal device and the driving school terminal device according to the real-time data synchronization module.
[0008] In one possible implementation, the collaboration layer further includes a business logic linkage module; the business logic linkage module is used to set the fund disbursement ratio corresponding to different training progress; the business logic linkage module is also used to verify the training progress, and after the training progress is successfully verified, send the fund transfer instruction to the bank-side device, wherein the fund transfer instruction carries the fund disbursement ratio corresponding to the training progress; the bank-side device transfers the funds in the fund supervision account to the driving school-side device according to the fund transfer instruction, including: the bank-side device responds to the fund transfer instruction and transfers the tuition fees paid by the students in the fund supervision account to the driving school-side device according to the fund disbursement ratio.
[0009] In one possible implementation, the architecture of the fund supervision system further includes an adaptation layer; the adaptation layer is deployed on the server layer and is used to convert the non-standard interfaces of multiple heterogeneous driving school terminal devices into preset universal interfaces.
[0010] In one possible implementation, the adaptation layer includes an interface standardization conversion module and a data format unification module; the interface standardization conversion module is used to convert all non-standard interfaces into the preset general interface; the data format unification module is used to define a standard data format and convert the non-standard data format in the training progress into the standard data format.
[0011] In one possible implementation, the student-side device includes a driving school information query module, an online registration module, a tuition payment module, a fund flow query module, a training progress viewing module, and a complaint feedback module; the driving school-side device includes an onboarding review module, a course management module, a teaching progress reporting module, a fund transfer application module, an account query module, and a credit rating receiving module; the bank-side device includes a supervisory account management module, a fund flow monitoring module, a transfer execution module, and a transaction record synchronization module; and the regulatory authority-side device includes an industry data statistics module, a fund flow supervision module, a driving school compliance review module, and a complaint handling tracking module.
[0012] In one possible implementation, the driving school terminal device is further configured to send driving school qualification information to the regulatory department terminal device based on the onboarding review module; the regulatory department terminal device is further configured to review the driving school qualification of the driving school based on the driving school qualification information.
[0013] In one possible implementation, the architecture of the fund supervision system further includes a database layer; the collaboration layer is deployed between the database layer and the server layer; the database layer is used to store student information, driving school qualification information, training course data, fund transaction records, and training progress data.
[0014] Secondly, this application also provides a fund supervision method based on the driver training industry, applied to the fund supervision system based on the driver training industry described in the first aspect; the fund supervision method includes: receiving tuition fees paid by students through a student terminal device and transferring the tuition fees into a fund supervision account created by a bank terminal device; responding to a fund transfer request sent by a driving school terminal device, and performing an authenticity comparison of the student's training progress carried in the fund transfer request through a collaborative layer; after the collaborative layer successfully verifies the authenticity of the training progress, the collaborative layer sends a fund transfer instruction to the bank terminal device; after the bank terminal device receives the fund transfer instruction, it transfers the funds in the fund supervision account to the driving school terminal device according to the fund transfer instruction, and sends the fund transfer result to the regulatory department terminal device.
[0015] In one possible implementation, before receiving tuition fees paid by students through the student terminal device, the method further includes: sending the driving school's qualification information to the regulatory authority terminal device through the driving school terminal device; reviewing the driving school's qualifications through the regulatory authority terminal device; and receiving tuition fees paid by students through the student terminal device, which includes receiving the tuition fees through the student terminal device if the regulatory authority terminal device approves the driving school's qualifications.
[0016] Compared with related technologies, the embodiments of this application have at least the following advantages: by setting up student-end devices, driving school-end devices, bank-end devices, and regulatory department-end devices at the client layer, and by configuring tuition payment permissions for the student-end devices, providing the driving school-end devices with permissions to report student training progress and receive fund transfers, providing the bank-end devices with permissions to create fund supervision accounts and monitor fund inflows and outflows, and providing the regulatory department-end devices with fund supervision permissions through the permission control module of the collaboration layer, each device on the client side only has the functions configured by the permission control module, thereby ensuring the reliability and security of the entire "registration-payment-training-disbursement-supervision" process. Furthermore, tuition fees paid by students are channeled into a fund supervision account via the student-side device. As the student's training progresses, the driving school-side device sends the training progress information to the collaboration layer for verification. Once the collaboration layer successfully verifies the authenticity of the training progress, it sends a fund transfer instruction to the bank-side device. The bank-side device then transfers funds from the fund supervision account to the driving school-side device according to the instruction and sends the transfer result to the regulatory authority's device. This forms a closed-loop collaboration mechanism among students, driving schools, banks, and regulatory authorities, establishing a data link between them and achieving full-process collaboration from "registration-payment-training-disbursement-supervision." This solves the problem of information fragmentation among various stakeholders in the industry and improves regulatory efficiency. In addition, since the server layer includes a main server, a first container for business services, a second container for data synchronization services, a third container for interface adaptation services, and a fourth container for fund supervision services, the server layer's capabilities are horizontally expanded by increasing the number of containers to adapt to the growth in the number of driving schools and the scale of students, meeting the needs of large-scale industry applications.
[0017] The technical effects achieved by the second aspect are similar to those achieved by the corresponding technical means in the first aspect, and will not be elaborated further here. Attached Figure Description
[0018] Figure 1 A schematic diagram of the functional modules of a fund supervision system based on the driver training industry provided in an embodiment of this application; Figure 2A data interaction flowchart of a student terminal device, a driving school terminal device, a bank terminal device, and a regulatory authority terminal device provided in an embodiment of this application; Figure 3 A flowchart illustrating a method for fund supervision in the driver training industry, as provided in an embodiment of this application. Detailed Implementation
[0019] To better understand the above-mentioned objectives, features, and advantages of this application, the application will be described in detail below with reference to the accompanying drawings and specific embodiments. It should be noted that, unless otherwise specified, the embodiments and features described in these embodiments can be combined with each other.
[0020] The following description sets forth many specific details to provide a full understanding of this application. The described embodiments are only some, not all, of the embodiments of this application.
[0021] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein in the specification of this application is for the purpose of describing particular embodiments only and is not intended to be limiting of this application.
[0022] It should be further noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.
[0023] In this application, "at least one" means one or more, and "more than one" means two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. The terms "first," "second," "third," "fourth," etc. (if present) in the specification, claims, and drawings of this application are used to distinguish similar objects, not to describe a specific order or sequence.
[0024] In the embodiments of this application, the terms "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.
[0025] For ease of understanding, some concepts related to the embodiments of this application are illustrated and explained by way of example for reference.
[0026] Database layer: Utilizes a MySQL database cluster deployed on a cloud server to store core data such as student information, driving school qualification information, training course data, financial transaction records, training progress data, and credit rating data. The database layer supports data sharding and backup mechanisms to ensure data security and access efficiency. At the same time, encryption algorithms are used to encrypt and store financial transaction data and sensitive user information.
[0027] Server layer: Deploy 1 ECS master server and 4 containers to respectively host business services, data synchronization services, interface adaptation services, and fund supervision services; The server layer adopts a load balancing mechanism, which can dynamically allocate resources according to concurrent access volume, support horizontal scaling, and meet the access needs of multiple driving schools and a large number of students.
[0028] Client layer: Adapted to multiple terminals (iOS, Android, Harmony), including student client (embedded module in Driving Test Encyclopedia APP), driving school client (driving school management system), bank client (dedicated regulatory account operation interface), and regulatory department client (regulatory back-end system). Each client communicates with the server layer through standardized interfaces.
[0029] Please refer to Figure 1 , Figure 1 This is a schematic diagram of the functional modules of the fund supervision system for the driver training industry based on this application. For ease of explanation, the structural schematic diagram of the embodiment of the fund supervision system for the driver training industry only shows the parts related to the embodiment of this application. Those skilled in the art will understand that the illustrated structure does not constitute a limitation on the device, and may include more or fewer components than shown, or combine certain components, or have different component arrangements.
[0030] The driver training industry-based fund supervision system 10 includes a client layer 11, a server layer 12, and a collaboration layer 13. The server layer 12 includes a main server 121, a first container 122 for carrying business services, a second container 123 for carrying data synchronization services, a third container 124 for carrying interface adaptation services, and a fourth container 125 for carrying fund supervision services. The client layer 11 includes student-side devices 111, driving school-side devices 112, bank-side devices 113, and regulatory department-side devices 114 that communicate with the server layer 12. The collaboration layer 13 includes an access control module 131, which is used to configure tuition payment permissions for student-side devices 111 and configure permissions for driving school-side devices. Device 112 provides permissions for reporting student training progress and receiving fund transfers, permissions for creating a fund supervision account and monitoring fund inflows and outflows to bank device 113, and permissions for fund supervision to regulatory device 114. Specifically, student device 111 is used to transfer tuition fees paid by students into the fund supervision account, and driving school device 112 is used to send student training progress to collaboration layer 13 for authenticity verification. After successful verification of the training progress, collaboration layer 13 sends a fund transfer instruction to bank device 113. Bank device 113 then transfers funds from the fund supervision account to driving school device 112 according to the fund transfer instruction and sends the fund transfer result to regulatory device 114.
[0031] In some embodiments, the student-side device 111 is developed based on iOS 12.0+ and Android 8.0+ systems and integrated into the Driving Test Encyclopedia APP; the driving school-side device 112 supports Windows Server 2016+ and Mac OS X 10.15+ systems and provides a web-based management backend; the bank-side device 113 and the regulatory authority-side device 114 provide dedicated web access interfaces and support mainstream browsers (Chrome 90+, Edge 90+).
[0032] In some embodiments, server layer 12 adopts Nginx load balancing mechanism and Redis caching service, with core interface response time ≤500ms, supporting concurrent access by 100,000 students.
[0033] In some embodiments, the permission control module 131 assigns permissions to the four roles based on the RBAC (Role-Based Access Control) model: the student role can only access its own registration, payment, and progress data; the driving school role can only access the driving school's student data, course data, and fund transfer records; the bank role can only access the fund transfer data of the regulatory account; and the regulatory department role can access all data but has no fund operation permissions.
[0034] In some embodiments, the collaboration layer 13 further includes a real-time data synchronization module 132. The driving school device 112 is also used to send the training progress to the student device 111 in real-time according to the real-time data synchronization module 132. The bank device 113 is also used to send the fund transfer result to the student device 111 and the driving school device 112 in real-time according to the real-time data synchronization module 132.
[0035] Specifically, the real-time data synchronization module 132 adopts WebSocket real-time push technology and a timed fetch backup mechanism. Key operations such as student payment and driving school progress reporting trigger real-time push, while non-critical data is fetched every 5 seconds to ensure that the data synchronization delay is ≤3 seconds. At the same time, a message queue (RabbitMQ) is used to cache concurrent requests to avoid data congestion.
[0036] In some embodiments, the collaboration layer 13 further includes a business logic linkage module 133; the business logic linkage module 133 is used to set the fund disbursement ratio corresponding to different training progress; the business logic linkage module 133 is also used to verify the training progress, and after the training progress is successfully verified, it sends a fund transfer instruction to the bank terminal device 113, wherein the fund transfer instruction carries the fund disbursement ratio corresponding to the training progress; the bank terminal device 113 transfers the funds in the fund supervision account to the driving school terminal device 112 according to the fund transfer instruction, including: the bank terminal device 113 responds to the fund transfer instruction and transfers the tuition fees paid by the students in the fund supervision account to the driving school terminal device 112 according to the fund disbursement ratio.
[0037] Specifically, the business logic linkage module 133 configures "training progress - fund disbursement" rules through the rule engine. For example: 20% of tuition is disbursed upon completion of Subject 1 training; 30% upon completion of Subject 2 training; 30% upon completion of Subject 3 training; and the remaining 20% upon obtaining a driver's license. These rules support visual configuration and can be adjusted according to industry policies. This method strongly links training progress with fund disbursement, ensuring that tuition fees are used for their intended purpose. It prevents driving schools from misappropriating tuition fees at the architectural level, while also compelling driving schools to improve teaching quality and promoting standardized industry development.
[0038] In some embodiments, the collaboration layer 13 further includes a data verification module 134, which verifies the authenticity of training progress data by connecting to the traffic management department's subject examination system and the driving school's GPS system.
[0039] In some embodiments, the architecture of the fund supervision system 10 further includes an adaptation layer 14; the adaptation layer 14 is deployed on the server layer 12 and is used to convert the non-standard interfaces of the multiple heterogeneous driving school terminal devices 112 into preset universal interfaces.
[0040] In some embodiments, the adaptation layer 14 includes an interface standardization conversion module 141 and a data format unification module 142; the interface standardization conversion module 141 is used to convert non-standard interfaces into preset general interfaces; the data format unification module 142 is used to define standard data formats and convert non-standard data formats in the training progress into standard data formats.
[0041] In some embodiments, the adaptation layer 14 further includes a compatibility testing module 143. The compatibility testing module 143 has built-in automated test scripts, which automatically send test data during the docking process to detect the integrity and accuracy of data transmission. If data loss occurs, a retransmission mechanism is triggered, and if the format is incorrect, a specific error field is returned to indicate the error.
[0042] Specifically, the adaptation layer 14 is designed to solve the problem of interfacing with different heterogeneous management systems of driving schools. It adopts a modular architecture and includes an interface standardization conversion module 141, a data format unification module 142, and a compatibility testing module 143. The adaptation layer 14 predefines the interface protocols of various mainstream driving school management systems. The interface conversion module 141 converts the non-standard interfaces of heterogeneous systems into platform-wide interfaces. The data format unification module 142 converts training progress data and registration data in different formats into standard JSON format. The compatibility testing module 143 automatically detects data loss, format errors, and other problems during the interfacing process and provides feedback on repair suggestions.
[0043] More specifically, the interface standardization conversion module 141 predefines interface protocol libraries for 10 mainstream driving school management systems (such as driving school smart management PaaS platforms and traditional registration systems). The interface mapping relationship is defined through XML configuration files. When the driving school system initiates a connection request, the corresponding protocol is automatically matched and converted into the platform's RESTful API interface.
[0044] The data format unification module 142 uses JSON Schema to define standard data formats (such as training progress data including four required fields: student ID, subject name, completion time, and review status). It automatically parses and converts non-standard data (such as XML and CSV formats) reported by driving schools to ensure data structure consistency.
[0045] It is worth noting that the modular design and standardized interface scheme of the adaptation layer 14 effectively solves the technical difficulties of incompatibility between interfaces and data format differences of different driving school management systems, reduces system integration costs, and improves the accuracy (error rate less than 0.01%) and real-time performance (delay ≤ 3 seconds) of data transmission.
[0046] In some embodiments, the architecture of the fund supervision system further includes a database layer 15; a collaboration layer 13 is deployed between the database layer 15 and the server layer 12; the database layer 15 is used to store student information, driving school qualification information, training course data, fund transaction records, and training progress data.
[0047] It is worth noting that Database Layer 15 supports data sharding and backup mechanisms to ensure data security and access efficiency. Simultaneously, it uses encryption algorithms to encrypt and store financial transaction data and sensitive user information. Through encrypted database storage, role-based access control, and distributed backup mechanisms, the security of sensitive user information and financial transaction data is guaranteed. Real-time data synchronization across four terminals enables full-process traceability of fund flows and training progress, enhancing user trust and industry regulatory transparency.
[0048] In some embodiments, the database layer 15 adopts a MySQL 8.0 cluster, deployed on two cloud servers (configuration: 8 cores, 16GB memory, 1TB SSD storage), supports master-slave replication backup, and stores different types of data such as student information, financial data, and training data in data shards to improve query efficiency.
[0049] It is worth noting that the fund supervision system 10 in this embodiment includes a client layer 11, a server layer 12, and a database layer 15. The three-layer distributed architecture, combined with load balancing and dynamic resource allocation mechanisms, supports concurrent access by 100,000 students. The server layer capacity can be horizontally expanded by increasing the number of containers to adapt to the growth of the number of driving schools and the scale of students, thus meeting the needs of large-scale industry applications.
[0050] In some embodiments, the student terminal device 111 integrates a driving school information query module, an online registration module, a tuition payment module, a fund flow query module, a training progress viewing module, and a complaint feedback module; students can submit registration information, pay tuition fees to the supervision account, and check the tuition payment status and training progress through the student terminal device 111, realizing fully autonomous operation.
[0051] The driving school terminal device 112 includes an onboarding review module, a course management module, a teaching progress reporting module, a fund transfer application module, an account query module, and a credit evaluation receiving module. Driving schools can use the driving school terminal device 112 to submit qualifications, upload courses, report student training progress in real time, and receive fund transfers and credit evaluation results.
[0052] The bank-side device 113 includes a supervisory account management module, a fund flow monitoring module, a transfer execution module, and a transaction record synchronization module. The bank establishes a dedicated supervisory account through the bank-side device 113 to monitor the inflow (payment by students) and outflow (payment to driving schools) of funds in real time, executes fund transfers according to platform instructions, and synchronizes transaction records to the database layer 15.
[0053] The regulatory authority terminal device 114 includes an industry data statistics module, a fund flow monitoring module, a driving school compliance review module, and a complaint handling tracking module. Through the regulatory authority terminal device 114, regulatory authorities can view the fund monitoring data of the entire industry and the compliance status of driving schools in real time, track the progress of complaint handling, and achieve macro-level supervision.
[0054] It is worth noting that in some embodiments, the student-side device 111 also integrates a refund application module, which supports initiating refunds according to the proportion of uncompleted training stages; the driving school-side device 112 includes a refund processing module for confirming refund applications; and the bank-side device 113 includes a refund execution module for returning student funds to the original payment method according to instructions.
[0055] To facilitate understanding, the following will be combined with... Figure 2 The fund supervision process in this embodiment will be explained in detail below: Please refer to Figure 2 This is a data interaction flowchart for the student terminal device 111, driving school terminal device 112, bank terminal device 113, and regulatory authority terminal device 114 provided in the embodiments of this application.
[0056] The fund supervision process in this embodiment includes the following steps: 1. Driving schools submit qualification information through driving school terminal device 112. After being reviewed and approved by regulatory department terminal device 114, the information is uploaded to database layer 15 through the adaptation layer 14 and connected to its own management system.
[0057] 2. Students can use the student terminal device 111 to query driving school and course information, submit registration information, and pay tuition fees to a dedicated bank supervision account through the online payment sub-module. The payment record is synchronized to the database layer 15.
[0058] 3. The driving school reports the training progress of students (such as passing the subject test) through the driving school terminal device 112. The adaptation layer 14 standardizes the progress data and transmits it to the collaboration layer 13.
[0059] 4. The collaboration layer 13 determines whether the fund disbursement conditions are met according to the preset linkage rules. If the conditions are met, it sends a transfer instruction to the bank terminal device 113.
[0060] 5. The bank terminal device 113 performs the transfer operation, transferring the corresponding proportion of tuition fees to the driving school account, and at the same time updating the fund transaction record and synchronizing it to the database layer 15.
[0061] 6. The student terminal device 111, the driving school terminal device 112, and the regulatory department terminal device 114 can respectively query the fund flow, disbursement progress, and training progress data through the corresponding modules, realizing full transparency of the process.
[0062] It is worth noting that after the deployment of the fund supervision system 10 in this embodiment, it meets the following performance indicators: (1) Concurrent access support: It supports 100,000 students to operate online at the same time, and the response time of core interfaces such as registration and payment is ≤500ms; (2) Data synchronization delay: The data synchronization delay of the four terminals is ≤3 seconds, and the success rate of fund transaction record synchronization is 100%; (3) Heterogeneous system adaptation: It is compatible with more than 80% of driving school management systems on the market, and the connection success rate is ≥98%; (4) Data security: User sensitive information is encrypted and stored, fund transaction records cannot be tampered with, the database supports automatic fault switching, and the data loss rate is 0; (5) Availability: The fund supervision system 10 has an availability of ≥99.9% throughout the year and supports 7×24 hours of uninterrupted operation.
[0063] Compared with related technologies, the embodiments of this application have at least the following advantages: by setting up student-end devices, driving school-end devices, bank-end devices, and regulatory department-end devices at the client layer, and by configuring tuition payment permissions for the student-end devices, providing the driving school-end devices with permissions to report student training progress and receive fund transfers, providing the bank-end devices with permissions to create fund supervision accounts and monitor fund inflows and outflows, and providing the regulatory department-end devices with fund supervision permissions through the permission control module of the collaboration layer, each device on the client side only has the functions configured by the permission control module, thereby ensuring the reliability and security of the entire "registration-payment-training-disbursement-supervision" process. Furthermore, tuition fees paid by students are channeled into a fund supervision account via the student-side device. As the student's training progresses, the driving school-side device sends the training progress information to the collaboration layer for verification. Once the collaboration layer successfully verifies the authenticity of the training progress, it sends a fund transfer instruction to the bank-side device. The bank-side device then transfers funds from the fund supervision account to the driving school-side device according to the instruction and sends the transfer result to the regulatory authority's device. This forms a closed-loop collaboration mechanism among students, driving schools, banks, and regulatory authorities, establishing a data link between them and achieving full-process collaboration from "registration-payment-training-disbursement-supervision." This solves the problem of information fragmentation among various stakeholders in the industry and improves regulatory efficiency. In addition, since the server layer includes a main server, a first container for business services, a second container for data synchronization services, a third container for interface adaptation services, and a fourth container for fund supervision services, the server layer's capabilities are horizontally expanded by increasing the number of containers to adapt to the growth in the number of driving schools and the scale of students, meeting the needs of large-scale industry applications.
[0064] Based on the same idea as the fund supervision system based on the driver training industry in the above embodiments, this application also provides a fund supervision method based on the driver training industry, which can be applied to the above-mentioned fund supervision system based on the driver training industry.
[0065] Please refer to Figure 3 This is a flowchart of a fund supervision method based on the driver training industry provided in an embodiment of this application.
[0066] The specific process of this embodiment is as follows: Figure 3 As shown, it includes the following steps: S301: Receive tuition fees paid by students through the student terminal device and transfer the tuition fees to the fund supervision account created by the bank terminal device.
[0067] In some embodiments, before receiving tuition fees paid by students through the student terminal device, the method further includes: sending the driving school's qualification information to the regulatory authority terminal device through the driving school terminal device; reviewing the driving school's qualifications through the regulatory authority terminal device; and receiving tuition fees paid by students through the student terminal device, including: receiving tuition fees through the student terminal device if the regulatory authority terminal device approves the driving school's qualifications.
[0068] S302: In response to the fund transfer request sent by the driving school terminal device, the collaboration layer performs a verification of the student's training progress carried in the fund transfer request.
[0069] S303: After the collaboration layer successfully verifies the authenticity of the training progress, the collaboration layer sends a fund transfer instruction to the bank terminal device.
[0070] S304: After receiving the fund transfer instruction at the bank terminal, the bank transfers the funds in the fund supervision account to the driving school terminal according to the fund transfer instruction, and sends the fund transfer result to the regulatory authority terminal.
[0071] In some embodiments, fund disbursement adopts a targeted transfer method, and the bank's terminal device can only transfer funds to the driving school's pre-set compliant account to ensure that the funds are used for their designated purpose.
[0072] Compared with related technologies, the embodiments of this application have at least the following advantages: by setting up student-end devices, driving school-end devices, bank-end devices, and regulatory department-end devices at the client layer, and by configuring tuition payment permissions for the student-end devices, providing the driving school-end devices with permissions to report student training progress and receive fund transfers, providing the bank-end devices with permissions to create fund supervision accounts and monitor fund inflows and outflows, and providing the regulatory department-end devices with fund supervision permissions through the permission control module of the collaboration layer, each device on the client side only has the functions configured by the permission control module, thereby ensuring the reliability and security of the entire "registration-payment-training-disbursement-supervision" process. Furthermore, tuition fees paid by students are channeled into a fund supervision account via the student-side device. As the student's training progresses, the driving school-side device sends the training progress information to the collaboration layer for verification. Once the collaboration layer successfully verifies the authenticity of the training progress, it sends a fund transfer instruction to the bank-side device. The bank-side device then transfers funds from the fund supervision account to the driving school-side device according to the instruction and sends the transfer result to the regulatory authority's device. This forms a closed-loop collaboration mechanism among students, driving schools, banks, and regulatory authorities, establishing a data link between them and achieving full-process collaboration from "registration-payment-training-disbursement-supervision." This solves the problem of information fragmentation among various stakeholders in the industry and improves regulatory efficiency. In addition, since the server layer includes a main server, a first container for business services, a second container for data synchronization services, a third container for interface adaptation services, and a fourth container for fund supervision services, the server layer's capabilities are horizontally expanded by increasing the number of containers to adapt to the growth in the number of driving schools and the scale of students, meeting the needs of large-scale industry applications.
[0073] The foregoing has provided a detailed description of the fund supervision system and method for the driver training industry provided in this application. Specific examples have been used to illustrate the principles and implementation methods of this application. The descriptions of the above embodiments are only for the purpose of helping to understand the method and core ideas of this application. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of this application. Therefore, the content of this specification should not be construed as a limitation of this application.
Claims
1. A fund supervision system based on the driver training industry, characterized in that, The architecture of the fund supervision system includes: a client layer, a server layer, and a collaboration layer; The server layer includes a main server, a first container for carrying business services, a second container for carrying data synchronization services, a third container for carrying interface adaptation services, and a fourth container for carrying fund supervision services. The client layer includes student terminal devices, driving school terminal devices, bank terminal devices, and regulatory department terminal devices that communicate with the server layer. The collaboration layer includes an access control module, which is used to configure tuition payment permissions for the student terminal device, provide the driving school terminal device with permissions to report student training progress and receive fund transfers, provide the bank terminal device with permissions to create fund supervision accounts and monitor fund inflows and outflows, and provide fund supervision permissions for the regulatory department terminal device. The student-side device is used to transfer tuition fees paid by students into the fund supervision account. The driving school-side device is used to send the training progress of students to the collaboration layer for authenticity comparison. After the collaboration layer successfully verifies the authenticity of the training progress, it sends a fund transfer instruction to the bank-side device. The bank-side device transfers the funds in the fund supervision account to the driving school-side device according to the fund transfer instruction, and sends the fund transfer result to the regulatory department-side device.
2. The fund supervision system based on the driver training industry according to claim 1, characterized in that, The collaboration layer also includes a real-time data synchronization module; The driving school terminal device is also used to synchronously send the training progress to the student terminal device according to the real-time data synchronization module. The bank-side device is also used to synchronously send the fund transfer result to the student-side device and the driving school-side device according to the real-time data synchronization module.
3. The fund supervision system based on the driver training industry according to claim 2, characterized in that, The collaboration layer also includes a business logic linkage module; The business logic linkage module is used to set the fund disbursement ratio corresponding to different training progress. The business logic linkage module is also used to verify the training progress. After the training progress is successfully verified, the module sends the fund transfer instruction to the bank terminal device. The fund transfer instruction carries the fund disbursement ratio corresponding to the training progress. The bank-side device transfers funds from the fund supervision account to the driving school-side device according to the fund transfer instruction, including: The bank-side device responds to the fund transfer instruction and transfers the tuition fees paid by the student from the fund supervision account to the driving school-side device according to the fund allocation ratio.
4. The fund supervision system based on the driver training industry according to claim 1, characterized in that, The architecture of the fund supervision system also includes an adaptation layer; The adaptation layer is deployed on the server layer and is used to convert the non-standard interfaces of multiple heterogeneous driving school terminal devices into preset universal interfaces.
5. The fund supervision system based on the driver training industry according to claim 4, characterized in that, The adaptation layer includes an interface standardization conversion module and a data format unification module; The interface standardization conversion module is used to convert all non-standard interfaces into the preset universal interface; The data format unification module is used to define a standard data format and convert non-standard data formats in the training progress into the standard data format.
6. The fund supervision system based on the driver training industry according to claim 1, characterized in that, The student terminal device includes a driving school information query module, an online registration module, a tuition payment module, a fund flow query module, a training progress viewing module, and a complaint feedback module; The driving school terminal device includes an onboarding review module, a course management module, a teaching progress reporting module, a fund transfer application module, an account query module, and a credit rating receiving module; The bank-side device includes a regulatory account management module, a fund flow monitoring module, a transfer execution module, and a transaction record synchronization module; The regulatory department's terminal device includes an industry data statistics module, a fund flow monitoring module, a driving school compliance review module, and a complaint handling and tracking module.
7. The fund supervision system based on the driver training industry according to claim 6, characterized in that, The driving school terminal device is also used to send driving school qualification information to the regulatory department terminal device according to the onboarding review module; The regulatory authority's terminal device is also used to review the driving school's qualifications based on the driving school's qualification information.
8. The fund supervision system based on the driver training industry according to any one of claims 1 to 7, characterized in that, The architecture of the fund supervision system also includes a database layer; The collaboration layer is deployed between the database layer and the server layer; The database layer is used to store the student information, the driving school's qualification information, training course data, financial transaction records, and training progress data.
9. A fund supervision method based on the driver training industry, characterized in that, Applied to the fund supervision system as described in any one of claims 1 to 8; The fund supervision methods include: The tuition fees paid by students are received through the student terminal device and then transferred to a fund supervision account created by the bank terminal device. In response to a fund transfer request sent by the driving school's terminal device, the collaboration layer performs a verification of the student's training progress carried in the fund transfer request. After the collaboration layer successfully verifies the authenticity of the training progress, the collaboration layer sends a fund transfer instruction to the bank terminal device. After receiving the fund transfer instruction, the bank-side device transfers the funds in the fund supervision account to the driving school-side device according to the fund transfer instruction, and sends the fund transfer result to the regulatory authority-side device.
10. The fund supervision method based on the driver training industry according to claim 9, characterized in that, Before receiving tuition fees paid by students through the student terminal device, the method further includes: The driving school's qualification information is sent to the regulatory authority's terminal device via the driving school's terminal device; The driving school's qualifications are reviewed through the regulatory authority's terminal device; Receiving tuition fees paid by students through the student terminal device includes: Once the driving school's qualifications are approved by the regulatory authority's terminal device, the tuition fee will be received through the student's terminal device.