Double-event-driven certificate expiration inspection method and device based on a chauffeur SaaS platform

Abstract

The application discloses a double-event-driven certificate expiration inspection method and device based on a chauffeur SaaS platform, and relates to the technical field of online car-hailing platform risk control. The method comprises the following steps: generating a business change event according to a dynamic change operation, and generating a time event at a predetermined time according to a certificate validity period; if the state version number carried by the event is not the latest, the event is discarded; if the event is a business change event, the current compliance state is calculated, the state is synchronized to an associated service provider when the state is not expired, and the time event is dynamically managed, and cross-service-provider collaborative interception is performed when the state is expired; if the event is a time event, the current compliance state is queried, and collaborative interception is performed when the state is expired. The application combines business changes and time events, eliminates monitoring blind spots, avoids decision conflicts through a version number mechanism, realizes cross-tenant collaborative interception by querying associated service providers, realizes real-time risk control, and improves the security and operation efficiency of a multi-tenant SaaS platform.

Description

Technical Field

[0001] This invention relates to the field of risk control technology for ride-hailing platforms, specifically to a dual-event-driven method and device for inspecting expired documents based on a chauffeur SaaS platform. Background Technology

[0002] In the ecosystem of ride-sharing platforms such as chauffeur services and freight services, the platform needs to provide unified services to several to hundreds of service providers (SPs, i.e., fleets or labor companies) and the massive number of drivers they manage. Ensuring that the core professional qualifications (such as driver's licenses) of every online driver remain valid is an inviolable safety red line for platform operations, as well as a fundamental requirement for fulfilling social responsibility and avoiding legal risks.

[0003] The current technical solution mainly has the following technical problems: First, inspections based on scheduled tasks have an inherent delay of several hours to several days, making it impossible to intercept expired items immediately.

[0004] Second, while real-time processing triggered by business events (such as drivers manually updating their documents) can achieve zero-latency response to changes, its inherent flaw is that it can only respond to changes and cannot detect the natural expiration of static data. For a driver who has never modified their information since registration, their documents will expire silently, creating a huge blind spot in monitoring.

[0005] Third, if the two independent logics mentioned above are mechanically combined, it will lead to a complex system architecture, inconsistent state calculation rules, waste of resources, and conflicting handling instructions.

[0006] Fourth, in multi-tenant scenarios, there is a lack of cross-service provider collaborative interception capabilities, making it impossible to achieve a complete ban on access if one point expires.

[0007] Therefore, there is an urgent need for a method to inspect expired driver's licenses that can integrate dual-path events and achieve real-time monitoring without blind spots. Summary of the Invention

[0008] In view of the above-mentioned defects or deficiencies in the prior art, the present invention provides a dual-event driven document expiration inspection method and device based on the chauffeur SaaS platform. By integrating business change events and time events into dual event sources, introducing a status version number verification mechanism, and cross-service provider collaborative interception based on relationship graphs, the present invention achieves blind-spot monitoring of document expiration, avoids conflicts between new and old events, and freezes the order-taking permissions of all associated fleets when one document expires.

[0009] One aspect of the present invention provides a dual-event-driven document expiration inspection method based on a designated driver SaaS platform, comprising the following steps: Based on the dynamic changes to the driver's license information captured in real time, a business change event is generated, and based on the validity period of the driver's license, a time event is generated at a predetermined time. If the status version number of the driver's license carried by the current event is not the latest status version number, then the current event is discarded; If the current event carries the latest status version number of the driver's license and the current event is a business change event, then the current compliance status of the driver's license is calculated based on the license information in the current event. If the current compliance status is not expired, then the status update information in the business change event is synchronously pushed to the backend of all service providers associated with the driver's license. Based on the updated license validity period, the time event preset based on the old validity period is canceled, and a new time event is re-registered. If the current compliance status is expired, then the pre-authorization rules of all service providers associated with the driver's license are queried, and based on the pre-authorization rules, the business interface of the ride-hailing SaaS platform is called to freeze the driver's order-taking permissions under all associated service providers. If the current event carries the latest version number of the driver's license and the current event is a time-based event, then the current compliance status of the driver's license is queried based on the license information in the current event; if the current compliance status is not expired, then the current processing is terminated; if the current compliance status is expired, then the pre-authorization rules of all service providers associated with the driver's license are queried, and according to the pre-authorization rules, the business interface of the ride-hailing SaaS platform is called to freeze the driver's order-taking permissions under all associated service providers.

[0010] Another aspect of the present invention provides a dual-event-driven document expiration inspection device based on a designated driver SaaS platform, comprising: The event generation module is used to dynamically generate business change events based on the driver's license information captured in real time, and to generate time events at predetermined times based on the validity period of the driver's license. The version verification module is used to discard the current event if the status version number of the driver's license carried by the current event is not the latest status version number. The first processing module is used to calculate the current compliance status of the driver's license based on the license information in the current event if the current event carries the latest status version number of the driver's license and the current event is a business change event; if the current compliance status is not expired, the status update information in the business change event is synchronously pushed to the backend of all service providers associated with the driver's license, and the time event preset based on the old validity period is canceled and a new time event is re-registered according to the updated license validity period; if the current compliance status is expired, the pre-authorization rules of all service providers associated with the driver's license are queried, and the business interface of the chauffeur SaaS platform is called to freeze the driver's order-taking permissions under all associated service providers according to the pre-authorization rules. The second processing module is used to query the current compliance status of the driver's license based on the license information in the current event if the current event carries the latest version number of the driver's license and the current event is a time-based event; if the current compliance status is not expired, the current processing is terminated; if the current compliance status is expired, the pre-authorization rules of all service providers associated with the driver's license are queried, and according to the pre-authorization rules, the business interface of the ride-hailing SaaS platform is called to freeze the driver's order-taking permissions under all associated service providers.

[0011] This invention provides a dual-event-driven document expiration inspection method and device based on a ride-hailing SaaS platform. By integrating business change events and time events, it eliminates the monitoring blind spot of natural expiration of static data; by introducing a status version number mechanism, it resolves decision conflicts in continuous event scenarios; and by querying related service providers and calling interfaces in parallel, it achieves cross-tenant collaborative interception. Compared with existing technologies, this invention reduces the risk control response latency from minutes to seconds, achieving real-time risk control with immediate interception of expired documents, while avoiding resource waste and rule conflicts, significantly improving the security and operational efficiency of multi-tenant SaaS platforms. Attached Figure Description

[0012] Other features, objects, and advantages of this application will become more apparent from the following detailed description of non-limiting embodiments with reference to the accompanying drawings: Figure 1 This is a flowchart illustrating a dual-event-driven document expiration inspection method based on a designated driver SaaS platform provided in one embodiment of this application; Figure 2 This is a schematic diagram of the structure of a dual-event-driven document expiration inspection device based on a designated driver SaaS platform provided in one embodiment of this application; Figure 3 This is a schematic diagram of the structure of an electronic device provided in one embodiment of this application. Detailed Implementation

[0013] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0014] I. Key Technical Terms To facilitate understanding of this invention, the key technical terms involved in this application will first be explained.

[0015] Business Change Event: This refers to an event triggered by a driver's or service provider administrator's proactive action to dynamically change document information. This event carries the updated document information, driving the system to respond in real-time to human-caused changes.

[0016] Time-based events: These are events that are automatically generated at a predetermined time based on the driver's license's expiration date. These events are used to capture the natural expiration of licenses due to the passage of time, without requiring manual triggering.

[0017] Status Version Number: A monotonically increasing integer identifier or timestamp assigned to each driver's license to indicate the update order of the license status. The version number increments each time the license status changes.

[0018] Current compliance status: This refers to the validity assessment result of the driver's license at a specific moment, including valid, near-expiration, and expired status. Valid status indicates that the license's expiration date is later than the current system time; near-expiration status indicates that the remaining days of the license's validity period are less than a preset threshold; expired status indicates that the license's validity period is earlier than the current system time. Non-expired status is a collective term for valid and near-expiration statuses.

[0019] Service provider backend: refers to the management system owned by the fleet or labor service company that has joined the ride-hailing SaaS platform, which is used to manage the qualifications and order-taking permissions of its drivers.

[0020] Mapping Relationship Graph: A pre-built data structure used to record the binding relationship between driver's licenses and service providers.

[0021] Pre-authorization rules: Automated processing policies pre-configured by service providers on the platform, such as automatically freezing order-accepting permissions when a driver's license expires. The platform automatically executes these rules when conditions are met, without requiring manual confirmation.

[0022] Collaborative interception operation: When the system determines that a driver's license has expired, it simultaneously freezes the order-taking permissions of all service providers associated with that driver, achieving collaborative risk control across all service providers.

[0023] II. Method Examples This embodiment provides a dual-event-driven document expiration inspection method based on a designated driver SaaS platform, including the following steps: Step S101: Generate a business change event based on the dynamic change operation of the driver's license information captured in real time, and generate a time event at a predetermined time based on the validity period of the driver's license.

[0024] Specifically, the system needs to monitor two types of risk triggers in real time: human intervention and the passage of time. Therefore, this embodiment sets up two parallel event generation channels.

[0025] The first channel is for generating business change events. The system intercepts document information operations (such as uploading new documents, modifying validity periods, and approval) in the driver's app or the service provider's management backend, capturing dynamic change operations in real time. When such an operation is captured, the system encapsulates it into a structured event object. This object contains at least the event type (identified as a business change event), document identifier, updated document information (such as validity period), operation timestamp, and current status version number. This event is sent to the unified event processing module, which is a message queue or data channel that centrally receives various events. The unified event processing module then distributes the events to downstream processing modules in the order they arrive.

[0026] The second channel is the time-based event generation channel. Upon the initial entry of each driver's license record into the database or its update via a business change event, the system immediately reads its expiration date and calculates a predetermined trigger time based on that date. This trigger time is typically set to midnight of the day following the expiration date, or any future time accurate to the second. The system associates this trigger time with the license identifier and stores it in the persistent task queue of the distributed scheduler. When the system time reaches this predetermined time, the scheduler automatically wakes up and generates a time event. This event includes at least the event type (identified as a time event), the license identifier, and the predetermined trigger timestamp. This event is also published to the unified event bus.

[0027] This step addresses the problem in existing technologies where a single event source cannot simultaneously cover both dynamic changes and static expiration risk scenarios. Business change events ensure zero-latency response to manual update operations; time-based events, through a pre-scheduling mechanism, ensure that the natural expiration of static data is captured in a timely manner, fundamentally eliminating monitoring blind spots. Ultimately, this achieves full coverage of risk triggering sources; any change in document status will be perceived by the system and converted into a unified event format, laying the foundation for subsequent consistency processing.

[0028] Step S102: If the status version number of the driver's license carried by the current event is not the latest status version number, then discard the current event.

[0029] Specifically, the system maintains a monotonically increasing status version number for each driver's license. This version number automatically increments by 1 each time the license status changes (including expiration date updates, compliance status changes, etc.). Each event, when generated, carries the license version number it was based on at the time of generation. When an event is submitted to the unified event processing module, the system first extracts the license identifier and its accompanying version number from the event. Then, the system queries the current latest version number of the license (i.e., the version number recorded after the last status change). The version number carried by the event is compared with the latest version number. If the version number carried by the event is equal to the latest version number, it means that the event was generated based on the latest state, the verification is successful, and it will proceed to the next processing step.

[0030] If the version number carried by the event is less than the latest version number, it means that the event was generated based on an outdated state. For example, after the document is updated, the old time event arrives only due to network delay. In this case, the system simply discards the event without taking any action.

[0031] This step resolves decision conflicts in continuous event scenarios. A typical scenario involves a driver submitting a new, valid document via a business change event when their existing document is about to expire. The system updates the status and re-registers a new time event, but the older time event (based on the old expiration date) may arrive later due to queue congestion. Without a version verification mechanism, the system might incorrectly assume the document has expired and block it. The version verification mechanism ensures that only events based on the latest status are processed, thus avoiding erroneous decisions.

[0032] Step S103: If the current event carries the latest status version number of the driver's license and the current event is a business change event, then calculate the current compliance status of the driver's license based on the license information in the current event; if the current compliance status is not expired, then push the status update information in the business change event to the backend of all service providers associated with the driver's license, cancel the time event preset based on the old validity period according to the updated license validity period, and re-register the new time event; if the current compliance status is expired, then query the pre-authorization rules of all service providers associated with the driver's license, and according to the pre-authorization rules, call the business interface of the ride-hailing SaaS platform to freeze the driver's order-taking permissions under all associated service providers.

[0033] Specifically, after version verification passes, the system divides the processing flow into two branches based on the event type field: the business change event branch and the time event branch. This step is the business change event branch, and the following process is executed: The system extracts document information (such as the updated expiry date) from business change events and calls the global status decision-maker to calculate the current compliance status. The calculation logic is as follows: compare the document's expiry date with the current system time. If the expiry date is later than the current system time, the compliance status is valid. If the expiry date is earlier than or equal to the current system time, further judgment is made: if the difference between the expiry date and the current system time is within a preset threshold (such as 30 days), the compliance status is nearing expiry; otherwise, it is expired.

[0034] Furthermore, when the calculated current compliance status is non-expired (valid or nearing expiration), the system executes the following sub-steps: 1) Status update information is pushed synchronously. The system encapsulates the updated status of the certificate, including certificate identifier, current compliance status, and expiration date, into status update information. It then uses a mapping graph to identify all service providers with which the certificate is bound. Next, the system concurrently calls the backend interfaces of each service provider to push the status update information to them in real time. This push is a proactive notification, eliminating the need for service providers to poll.

[0035] 2) Dynamic management of time events Based on the updated document validity period, the system performs two operations: First, it sends a command to the distributed scheduler to cancel all untriggered time events pre-set based on the old validity period; second, it recalculates the scheduled trigger time based on the new validity expiry date and registers a new time event with the scheduler. This ensures that future expiry checks are always based on the latest validity period.

[0036] Furthermore, when the calculated current compliance status is expired, the system performs the following coordinated interception operations: First, check the pre-authorization rules of all service providers associated with the driver's license. For example, each service provider may have configured a rule to freeze order-taking permissions when the license expires.

[0037] Then, based on these rules, the system generates a freeze instruction for each service provider and uses a distributed coordinating executor to call the business interface of the ride-hailing SaaS platform in parallel to freeze the driver's order-taking permissions under all these service providers. This operation either succeeds entirely or rolls back entirely, meaning that the order-taking permissions of all associated service providers are either frozen simultaneously or not frozen at all, ensuring consistency by preventing partial freezing and partial unfrozen situations.

[0038] Furthermore, in the business change event branch, when the calculated current compliance status is non-expired, the system will further determine the driver's previous compliance status (i.e., the status before this update). If the previous compliance status was expired, it means that the driver's order-taking permission was previously frozen due to expired documents, and now compliance has been restored by updating the documents. At this time, the system includes a restoration instruction in the status update information pushed by the system. After receiving this information, each service provider's backend automatically restores the driver's order-taking permission under its jurisdiction. This restoration operation corresponds to the freezing operation and is also executed in parallel to ensure the consistency of permission status.

[0039] Step S104: If the current event carries the latest status version number of the driver's license and the current event is a time-based event, then query the current compliance status of the driver's license based on the license information in the current event; if the current compliance status is not expired, then terminate this process; if the current compliance status is expired, then query the pre-authorization rules of all service providers associated with the driver's license, and according to the pre-authorization rules, call the business interface of the ride-hailing SaaS platform to freeze the driver's order-taking permissions under all associated service providers.

[0040] This step is a time-event branch, and the following process is executed: The system retrieves the current compliance status of a document from the database based on the document identifier carried in the time event. This query does not rely on the information in the event itself, as the time event only contains the trigger signal and not the latest document status. The query method is the same as for the business change event branch, i.e., comparing the expiration date with the current system time.

[0041] If the current compliance status is "not expired," it means the document is still valid or only nearing its expiration date, requiring no action. The system will terminate this process without taking any further action.

[0042] If the current compliance status is expired, it means that the certificate has expired naturally. The system will perform the same collaborative interception operation as the business change event branch, that is, query the pre-authorization rules of the associated service providers and call the interface in parallel to freeze the driver's order-taking permissions under all associated service providers.

[0043] Steps S103 and S104 address the issues of simplistic handling strategies and lack of cross-tenant collaboration in existing technologies. By differentiating event types and compliance statuses, differentiated processing is achieved: business change events are used to update statuses and dynamically adjust future inspection plans, while time-based events are used to capture static expirations. Simultaneously, through querying mapping graphs and parallel API calls, collaborative risk control is implemented, enabling a single point of expiration to trigger a blanket ban across the entire system.

[0044] To better understand this invention, the following describes in detail the complete process of the method of this invention from event generation to completion of processing, using a specific application scenario as an example.

[0045] A ride-hailing SaaS platform has two service providers: SP_A (Fleet A) and SP_B (Fleet B). Driver Li is registered to accept orders on both SP_A and SP_B. His driver's license number is D-123456, and its expiration date is December 31, 2025. Both SP_A and SP_B have configured the same pre-authorization rule on the platform: when a driver's license status becomes expired, the system automatically freezes his order-accepting privileges.

[0046] Phase 1: The document expires naturally, triggering a full network blockade.

[0047] The time is 00:00:01 on January 1, 2026. Mr. Li's driver's license expired yesterday, but neither he nor the two car fleets were aware of it.

[0048] At this time, the pre-scheduled time event on December 31, 2025, is triggered on time. The distributed scheduler generates a time event containing: event type = time event, document identifier = D-123456, and scheduled trigger time = 2026-01-01 00:00:01.

[0049] The event was submitted to the unified event processing center. The version verification module found that the latest status version number of document D-123456 was V1 (it has not been updated since registration), and the version number carried by the event was also V1, so the verification passed.

[0050] Since the event type is a time-based event, the process proceeds to the second processing module. The system queries the current compliance status based on the document identifier D-123456: the current system time is 2026-01-01, and the expiration date is 2025-12-31. The system calculates that the current compliance status equals the expired status.

[0051] The system then queries all service providers associated with document D-123456. Through the mapping graph, it identifies two service providers, SP_A and SP_B. The system retrieves the pre-authorization rules for SP_A and SP_B, both configured to freeze order-taking permissions. The system generates two freeze commands and uses a distributed coordinating executor to call the business interface of the ride-hailing SaaS platform in parallel, simultaneously freezing Mr. Li's order-taking permissions under both SP_A and SP_B. SP_A and SP_B's backends receive notifications almost simultaneously: driver Mr. Li's order-taking permissions have been automatically frozen due to expired documents. Thus, a complete closed loop of natural document expiration → real-time interception is completed.

[0052] Phase Two: Document renewal triggers a full-network release.

[0053] On the morning of January 2, 2026, Mr. Li discovered he was unable to accept orders, so he immediately went to the traffic police department to obtain a new driver's license, valid until December 31, 2028. He uploaded a photo of the new driver's license through the SP_A driver app.

[0054] The system captures this dynamic change operation in real time and generates a business change event. This event includes: event type = business change event, document identifier = D-123456, updated document information (valid until 2028-12-31), operation timestamp, and version number V2 (automatically incremented by the system).

[0055] The event enters the unified event handling module. The version verification module compares the event and finds that the version number V2 carried by the event is equal to the current latest version number V2 (the version number has been updated to V2 since the last expiration state), so the verification passes.

[0056] Since the event type is a business change event, the process enters the first processing module. The system compares the updated validity period (2028-12-31) in the event with the current system time (2026-01-02) to calculate the current compliance status = validity status.

[0057] The system then executes the non-expired status processing procedure: (1) The status update information (certificate identifier D-123456, current compliance status = valid, new validity period 2028-12-31) is simultaneously pushed to the backend of SP_A and SP_B. At the same time, since the previous compliance status was expired, the status update information carries a recovery instruction. After receiving the information, the backends of SP_A and SP_B automatically restore Mr. Li's order-taking permissions.

[0058] (2) The system sends an instruction to the distributed scheduler to cancel the time event that has not yet been triggered and is pre-set based on the old validity period (2025-12-31). In fact, the event has already been triggered and processed in the first phase, but the system still performs cleanup logic to ensure that there are no remnants. Then, the system recalculates the scheduled trigger time as 2029-01-01 00:00:01 based on the new validity period 2028-12-31, and registers a new time event with the scheduler.

[0059] At this point, Mr. Li's order-taking permissions in SP_A and SP_B were simultaneously restored, and the system also reset future expiration checkpoints. The entire process required no manual intervention, achieving a fully automated closed loop from risk perception to handling and recovery.

[0060] As can be seen from the above embodiments, the dual-event-driven method provided by the present invention can achieve second-level response and network-wide collaborative handling regardless of whether the risk originates from the natural passage of time or human operation, significantly improving the risk control capabilities of multi-tenant SaaS platforms.

[0061] III. Device Examples See Figure 2 Another embodiment of the present invention provides a dual event-driven document expiration inspection device 200 based on a chauffeur SaaS platform, including an event generation module 201, a version verification module 202, a first processing module 203, and a second processing module 204. The device 200 is capable of executing the dual event-driven document expiration inspection method based on a chauffeur SaaS platform in the method embodiment.

[0062] Specifically, the dual-event-driven document expiration inspection device 200 based on the designated driver SaaS platform includes: The event generation module 201 is used to generate business change events based on the dynamic change operations of the driver's license information captured in real time, and to generate time events at a predetermined time based on the validity period of the driver's license. Version verification module 202 is used to discard the current event if the status version number of the driver's license carried by the current event is not the latest status version number; The first processing module 203 is used to calculate the current compliance status of the driver's license based on the license information in the current event if the current event carries the latest status version number of the driver's license and the current event is a business change event; if the current compliance status is not expired, the status update information in the business change event is synchronously pushed to the backend of all service providers associated with the driver's license, and the time event preset based on the old validity period is canceled and a new time event is re-registered according to the updated license validity period; if the current compliance status is expired, the pre-authorization rules of all service providers associated with the driver's license are queried, and the business interface of the chauffeur SaaS platform is called to freeze the driver's order-taking permissions under all associated service providers according to the pre-authorization rules. The second processing module 204 is used to query the current compliance status of the driver's license based on the license information in the current event if the current event carries the latest status version number of the driver's license and the current event is a time event; if the current compliance status is not expired, the current processing is terminated; if the current compliance status is expired, the pre-authorization rules of all service providers associated with the driver's license are queried, and according to the pre-authorization rules, the business interface of the chauffeur SaaS platform is called to freeze the driver's order-taking permissions under all associated service providers.

[0063] It should be noted that the technical solutions corresponding to the dual event-driven document expiration inspection device 200 based on the chauffeur SaaS platform provided in this embodiment, which can be used to execute various method embodiments, have similar implementation principles and technical effects to the methods, and will not be repeated here.

[0064] Figure 3 This is a schematic diagram of an electronic device 300 provided in another embodiment of the present invention. The electronic device 300 is used to implement the dual-event-driven document expiration inspection method based on a ride-hailing SaaS platform in the method embodiment. The electronic device 300 in the embodiments of the present invention may include, but is not limited to, smartphones, tablets, PCs, laptops, etc. Figure 3 The electronic device 300 shown is merely an example and should not be construed as limiting the functionality and scope of use of the embodiments of the present invention.

[0065] like Figure 3As shown, the electronic device 300 may include a processing device (e.g., a central processing unit, a graphics processing unit, etc.) 301, which can perform various appropriate actions and processes to implement the methods of the embodiments described herein, based on a program stored in a read-only memory (ROM) 302 or a program loaded from a storage device 308 into a random access memory (RAM) 303. The RAM 303 also stores various programs and data required for the operation of the electronic device 300. The processing device 301, ROM 302, and RAM 303 are interconnected via a bus 305. An input / output (I / O) interface 304 is also connected to the bus 305.

[0066] Typically, the following devices can be connected to I / O interface 304: input devices 306 including, for example, touchscreens, touchpads, keyboards, mice, cameras, microphones, accelerometers, gyroscopes, etc.; output devices 307 including, for example, liquid crystal displays (LCDs), speakers, vibrators, etc.; storage devices 308 including, for example, magnetic tapes, hard disks, etc.; and communication devices 309. Communication device 309 allows electronic device 300 to communicate wirelessly or wiredly with other devices to exchange data. Although Figure 3 An electronic device 300 with various devices is shown; however, it should be understood that it is not required to implement or possess all of the devices shown. More or fewer devices may be implemented or possessed alternatively.

[0067] The above description is merely a preferred embodiment of the present invention. Those skilled in the art should understand that the scope of disclosure in this invention is not limited to the specific combination of the above-described technical features, but should also cover other technical solutions formed by any combination of the above-described technical features or their equivalents without departing from the above-described concept. For example, technical solutions formed by substituting the above features with (but not limited to) technical features with similar functions disclosed in this invention.

Claims

1. A dual-event-driven document expiration inspection method based on a designated driver SaaS platform, characterized in that, Includes the following steps: Based on the dynamic changes to the driver's license information captured in real time, a business change event is generated, and based on the validity period of the driver's license, a time event is generated at a predetermined time. If the status version number of the driver's license carried by the current event is not the latest status version number, then the current event is discarded; If the current event carries the latest status version number of the driver's license and the current event is a business change event, then the current compliance status of the driver's license is calculated based on the license information in the current event. If the current compliance status is not expired, the status update information in the business change event will be synchronously pushed to the backend of all service providers associated with the driver's license. Based on the updated validity period of the license, the time event preset based on the old validity period will be canceled, and a new time event will be re-registered. If the current compliance status is expired, the pre-authorization rules of all service providers associated with the driver's license will be queried, and based on the pre-authorization rules, the business interface of the ride-hailing SaaS platform will be called to freeze the driver's order-taking permissions under all associated service providers. If the current event carries the latest status version number of the driver's license and the current event is a time-based event, then the current compliance status of the driver's license will be queried based on the license information in the current event. If the current compliance status is not expired, the current process will be terminated; if the current compliance status is expired, the pre-authorization rules of all service providers associated with the driver's license will be queried, and the business interface of the chauffeur SaaS platform will be called to freeze the driver's order-taking permissions under all associated service providers according to the pre-authorization rules.

2. The dual-event-driven document expiration inspection method based on a designated driver SaaS platform according to claim 1, characterized in that, The dynamic change operation of driver's license information includes at least one of the following: Drivers can upload new document information through the client, modify their current document information, and the service provider administrator can review or update the driver's document information in the background.

3. The dual-event-driven document expiration inspection method based on a designated driver SaaS platform according to claim 1, characterized in that, The step of synchronously pushing the status update information of the business change event to the backend of all service providers associated with the driver's license includes: Query the pre-built mapping graph of driver's licenses and service providers to identify all service providers that are bound to the current driver's license; The status update information is pushed in real time to the back-end system of each service provider that is currently associated with the driver's license.

4. The dual-event-driven document expiration inspection method based on a designated driver SaaS platform according to claim 1, characterized in that, The current compliance status includes valid status, near-expiration status, and expired status. The near-expiration status indicates that the remaining days of the certificate's validity period are less than a preset threshold. The non-expired status includes valid status and near-expiration status.

5. The dual-event-driven document expiration inspection method based on a designated driver SaaS platform according to claim 1, characterized in that, The step of synchronously pushing the status update information of the business change event to the backend of all service providers associated with the driver's license if the current compliance status is not expired includes: If the current compliance status is not expired and the driver's license was previously expired, the recovery instruction carried in the status update information will enable the service providers' backends to restore the driver's order-accepting permissions.

6. A dual-event-driven document expiration inspection device based on a designated driver SaaS platform, characterized in that, include: The event generation module is used to dynamically generate business change events based on the driver's license information captured in real time, and to generate time events at predetermined times based on the validity period of the driver's license. The version verification module is used to discard the current event if the status version number of the driver's license carried by the current event is not the latest status version number. The first processing module is used to calculate the current compliance status of the driver's license based on the license information in the current event if the current event carries the latest status version number of the driver's license and the current event is a business change event. If the current compliance status is not expired, the status update information in the business change event will be synchronously pushed to the backend of all service providers associated with the driver's license. Based on the updated validity period of the license, the time event preset based on the old validity period will be canceled, and a new time event will be re-registered. If the current compliance status is expired, the pre-authorization rules of all service providers associated with the driver's license will be queried, and based on the pre-authorization rules, the business interface of the ride-hailing SaaS platform will be called to freeze the driver's order-taking permissions under all associated service providers. The second processing module is used to query the current compliance status of the driver's license based on the license information in the current event if the current event carries the latest status version number of the driver's license and the current event is a time event. If the current compliance status is not expired, the current process will be terminated; if the current compliance status is expired, the pre-authorization rules of all service providers associated with the driver's license will be queried, and the business interface of the chauffeur SaaS platform will be called to freeze the driver's order-taking permissions under all associated service providers according to the pre-authorization rules.

7. The dual-event-driven document expiration inspection device based on a designated driver SaaS platform according to claim 6, characterized in that, The dynamic change operation of driver's license information includes at least one of the following: Drivers can upload new document information through the client, modify their current document information, and the service provider administrator can review or update the driver's document information in the background.

8. A dual-event-driven document expiration inspection device based on a designated driver SaaS platform according to claim 6, characterized in that, The first processing module is also used for: Query the pre-built mapping graph of driver's licenses and service providers to identify all service providers that are bound to the current driver's license; The status update information is pushed in real time to the back-end system of each service provider that is currently associated with the driver's license.

9. A dual-event-driven document expiration inspection device based on a designated driver SaaS platform according to claim 6, characterized in that, The current compliance status includes valid status, near-expiration status, and expired status. The near-expiration status indicates that the remaining days of the certificate's validity period are less than a preset threshold. The non-expired status includes valid status and near-expiration status.

10. A dual-event-driven document expiration inspection device based on a designated driver SaaS platform according to claim 6, characterized in that, The first processing module is also used for: If the current compliance status is not expired and the driver's license was previously expired, the recovery instruction carried in the status update information will enable the service providers' backends to restore the driver's order-accepting permissions.

Images