Scheduling and approval process control method and device for digital product online leasing

By building a cloud-native process control system on the online digital product rental platform and combining it with equipment scheduling and approval strategies, the problem of the separation between equipment scheduling and approval processes was solved, and efficient rental process management and improved user experience were achieved.

CN120612160AActive Publication Date: 2025-09-09BEIJING YUNLING ZHIXING NETWORK TECHNOLOGY CO LTD

Patent Information

Application Number
CN202511034432.9
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2025-07-25
Publication Date
2025-09-09
Estimated Expiration
2045-07-25

AI Technical Summary

Technical Problem

Existing online digital product rental platforms have a disconnect between equipment scheduling and approval processes and lack dynamic control capabilities, resulting in inefficient approval and inaccurate equipment scheduling. They are unable to meet large-scale, high-frequency rental needs, especially during peak periods, and lack a comprehensive assessment of multi-dimensional factors, which affects user experience.

Method used

A process control system is built using a cloud-native platform and an orchestrated workflow engine. The equipment resource scheduling module, approval strategy, and credit engine are combined to implement leasing application and process control. Equipment scheduling and conflict detection methods are designed, and a performance monitoring mechanism is introduced to support automatic flow and exception tolerance throughout the entire process, thus realizing the linkage between approval and scheduling.

Benefits of technology

It realizes the instant coordination and linkage between pre-lease approval and resource scheduling, improves process efficiency and resource utilization, reduces manual operation costs, adapts to the high concurrency requirements of multiple roles and multiple lease types, and improves user experience.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN120612160A_ABST
    Figure CN120612160A_ABST
Patent Text Reader

Abstract

The invention discloses a scheduling and approval process control method and device for digital product online leasing, and the method specifically comprises the steps: carrying out the cloud native operation environment preparation, building a process control system based on a workflow engine capable of being arranged, carrying out the system initialization, and carrying out the operation of a cloud server; comprising the steps of initializing a lease process engine, an equipment resource scheduling module, an approval strategy and credit engine and a performance monitoring and state management system; and then a lease application and process control method, an equipment scheduling and conflict detection method, an examination and approval execution and process driving method and a performance monitoring and state write-back method are designed in sequence. After a user submits a leasing request, generating an approval process and distributing the approval process to an approval node; executing resource allocation and locking after the approval is passed; an event-driven mechanism is adopted to manage state circulation of all stages of leasing, and reverse-driven scheduling adjustment of approval results is supported. According to the invention, the approval efficiency of online renting of digital products is improved, the manual intervention cost is reduced, and the rationality and traceability of equipment resource configuration are guaranteed.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the technical field of equipment leasing management, and in particular to a method and device for controlling a scheduling and approval process for online leasing of digital products. Background Art

[0002] With the widespread adoption of the "rent instead of buy" consumer philosophy and the development of the digital economy, online digital product rental services have rapidly emerged, becoming widely used in consumer electronics such as mobile phones, tablets, laptops, and photographic equipment. Compared to traditional purchasing models, online leasing offers significant advantages in terms of capital utilization, equipment upgrades, and flexible use, making it a key asset acquisition method for both individual consumers and small and medium-sized enterprises. However, existing leasing platforms still face significant technical limitations in equipment scheduling and pre-lease approval processes, making it difficult to support large-scale, high-frequency, and heterogeneous leasing needs.

[0003] On the one hand, current leasing systems generally lack intelligent mechanisms for dynamic control of approval processes. Approval paths are typically statically configured and unable to automatically adjust based on dynamic parameters such as user credit rating, lease amount, and lease term. While some platforms offer multi-level approval capabilities, these rigid process orchestration and frequent manual intervention lead to low approval efficiency and prone to bottlenecks, particularly during holidays and peak periods.

[0004] On the other hand, equipment scheduling and the approval process are often disconnected, making it difficult for the platform to accurately identify available equipment immediately after approval is completed. This leads to frequent issues with equipment being unavailable after approval, impacting the user experience. Equipment scheduling modules typically allocate equipment based solely on inventory quantities, lacking a comprehensive assessment of multiple factors such as the equipment's location, usage status, maintenance schedule, and historical usage history. Furthermore, the existing system lacks the ability to control scheduling behavior based on approval results, resulting in a closed loop between process management and resource allocation.

[0005] In multi-role collaborative scenarios, such as corporate group leasing and large-scale campus applications, problems such as slow approval processes, frequent lease term conflicts, and untraceable processes still exist, severely hindering the operational efficiency and service quality of digital product rental platforms. Therefore, a method and device for controlling equipment rental scheduling and approval processes is urgently needed, capable of flexibly configuring approval processes, enabling real-time scheduling strategy adjustments, and supporting full-process automation and fault tolerance to meet the increasingly complex and personalized needs of online leasing. Summary of the Invention

[0006] The purpose of the present invention is to provide a scheduling and approval process control method and device for online rental of digital products, which can realize automated approval and scheduling linkage for C-end or B-end users, reduce manual operation costs, reduce approval bottlenecks, and improve resource utilization and user experience.

[0007] The technical solution to achieve the purpose of the present invention is: a scheduling and approval process control method for online rental of digital products, comprising the following steps:

[0008] Step 1: First, prepare the cloud-native operating environment. Then, build a process control system based on the orchestrated workflow engine and initialize the system, including initializing the leasing process engine, equipment resource scheduling module, approval strategy and credit engine, and performance monitoring and status management system.

[0009] Step 2: Design the leasing application and process control method, including leasing request parameter modeling and access control, dynamic process path generation and approval strategy matching, approval node injection and task distribution mechanism, abnormal approval branching and process fault tolerance mechanism;

[0010] Step 3: Design equipment scheduling and conflict detection methods, including equipment resource status modeling and caching mechanism, intelligent scheduling strategy and priority control mechanism, lease conflict detection and dynamic scheduling adjustment, and linkage mechanism between scheduling and approval process;

[0011] Step 4: Design the approval execution and process driving methods, including approval node task allocation and triggering logic, automatic approval mechanism and system judgment logic, process state migration and execution advancement control, approval exception handling and process rollback mechanism;

[0012] Step 5. Design the performance monitoring and status writeback method, including the lease start and status perception trigger mechanism, performance process event management and dynamic log collection, lease end and return acceptance process control, credit score writeback and behavior feedback mechanism.

[0013] Furthermore, Step 1 includes Step 1.1, which is to deploy the basic resource layer on a cloud-native platform that supports containerized scheduling to complete the preparation of the cloud-native operating environment, as follows:

[0014] Step 1.1.1. Deploy the basic resource layer on a cloud-native platform that supports containerized scheduling, including the container runtime, orchestration platform, service registration and discovery module, configuration center, message queue, and log monitoring system. Each service module is deployed as a container image and logically isolated based on namespaces and service labels.

[0015] Step 1.1.2: When the service starts, read the dynamic parameters of the configuration center, including the database address, authentication policy, approval rule template, and scheduling algorithm policy, so that the system has cross-tenant, cross-process, and multi-device category configuration capabilities.

[0016] Furthermore, the process control system described in step 1 is constructed based on the programmable workflow engine and the system is initialized as follows:

[0017] Step 1.2: Initialize the leasing process engine as follows:

[0018] Step 1.2.1. Build a process control system based on a programmable workflow engine and load the leasing process definition model. This model uses BPMN or DSL to describe the approval paths, inter-node conditional judgment logic, rollback paths, and exception handling rules.

[0019] Step 1.2.2: The system registers built-in approval node types, including user identity determination node, amount threshold branch node, credit score determination node, manual approval node, and automatic approval node;

[0020] Step 1.2.3: The process engine dynamically loads platform rules through the configuration center, supporting matching different process templates based on device type, applicant role, and lease length parameters;

[0021] Step 1.3: Initialize the device resource scheduling module, as follows:

[0022] Step 1.3.1. The system synchronizes device metadata from the device asset management subsystem, including device ID, SKU model, status bit, geographic location, available time window, and historical usage records, and builds a resource status cache pool.

[0023] Step 1.3.2: The platform preloads the scheduling algorithm plug-in, and the administrator configures the activation policy in the console;

[0024] Step 1.3.3: The conflict detection module creates a resource occupancy map based on the current lease period, occupied resources, and equipment maintenance record data, which is used for real-time verification in the subsequent scheduling stage.

[0025] Step 1.4: Initialize the approval strategy and credit engine, as follows:

[0026] Step 1.4.1: The approval policy includes a table of approval permissions for different roles, a table of amount range control, and an approval timeout handling policy. These policies are configured in a rule tree or JSON format and are loaded by the policy management service and injected into the approval engine.

[0027] Step 1.4.3: The credit assessment module starts a local or external model inference engine, loads a lightweight scoring model, and connects to a third-party credit reporting service to complete user profile queries and trial-free judgments.

[0028] Step 1.5: Initialize the contract performance monitoring and status management system as follows:

[0029] Step 1.5.1. The performance monitoring module is used to monitor and record status throughout the entire lease lifecycle. During initialization, the system deploys a state controller to define the various states and transition relationships of the lease process, including application pending, approval pending, pending scheduling, leased, returned, maintenance pending, and completed, and binds corresponding event triggering logic.

[0030] Step 1.5.2: Connect the monitoring service to the log system, the device online status perception module, and the order data table to visualize the status and capture anomalies during the rental process.

[0031] Furthermore, the design lease application and process control method described in step 2 is as follows:

[0032] Step 2.1: Model the lease request parameters and perform access control, as follows:

[0033] Step 2.1.1: The user submits a device rental request through the rental application interface on the rental platform. The rental request contains multiple core parameters, including applicant identity information, device SKU number, desired rental period, rental type, delivery address, and whether to waive deposit. These core parameters are forwarded to the process control system via the unified access layer API Gateway and serialized into a JSON structure and passed to the rental application module.

[0034] Step 2.1.2: The system performs integrity and format checks on the lease parameters. If any fields are missing, formatted incorrectly, or exceed the specified field's permissions, the system will refuse to proceed to the main process and return the corresponding error code.

[0035] Step 2.1.3: The access layer performs security control operations such as access rate limiting, token verification, and signature verification to prevent illegal requests or repeated submissions from causing system pressure.

[0036] Step 2.1.4: After the parameter verification passes, the system binds the request context to the current user session, providing a user identification link for subsequent process control;

[0037] Step 2.2: Dynamically generate the process path and match it with the approval strategy, as follows:

[0038] Step 2.2.1: After receiving the complete parameters, the rental application module encapsulates them into a process context object and passes it to the flowchart construction engine. At this stage, the system performs a multi-dimensional analysis of the parameters submitted by the applicant based on the process configuration rules set by the platform and generates an adapted approval path diagram.

[0039] Step 2.2.2: The path generation process is based on a comprehensive assessment of the following dimensions: First, user credit rating. Low-credit users must go through the full approval process, while high-credit users can enjoy automatic or simplified approval. Second, the rental amount. If the total rental amount exceeds the set threshold, a financial review node or supervisor approval node must be added. Third, the equipment risk factor. Different equipment types will have different approval processes. Fourth, factors such as the lease term limit, deposit ratio, and contract type in the business rules.

[0040] Step 2.2.3: Use BPMN modeling or DSL configuration to build a flowchart. The process engine generates a process template diagram and then generates a specific process instance. This instance is bound to a unique process ID and corresponds one-to-one with the rental order. It supports process tracking and status recovery. If the platform enables the process visualization option, the approver can view the complete process link and the current node progress on the workbench;

[0041] Step 2.3: Design the approval node injection and task distribution mechanism, as follows:

[0042] Step 2.3.1: After the flowchart is generated, the system will inject approval tasks based on the node definitions in the flowchart. Each approval node is considered a schedulable process task. The system automatically retrieves the approver based on the role binding logic in the node definition and queries their role identity, current available status, and approval permissions through the user service.

[0043] Step 2.3.2: Use a task distribution mechanism to support parallel and serial processing, as well as complex scenarios such as multi-person collaborative approval, preemptive approval, or countersignature processing;

[0044] Step 2.3.3: After being distributed, each approval task will enter the pending queue and be pushed to the target approver. The approver can view, approve, reject or transfer the task through the platform interface.

[0045] Step 2.3.4: The system sets a maximum response time for each approval node. If the time is exceeded, the timeout transfer policy or default processing policy will be automatically triggered, and the event will be written into the process log for audit purposes;

[0046] Step 2.3.5: Task status is managed by the process engine. The state machine migrates based on the task execution results and automatically enters the next process node. The state transitions between all nodes follow the defined transition rules, ensuring that the process can ultimately converge to two exit states: approved or rejected under different approval paths.

[0047] Step 2.4: Design abnormal approval branches and process fault tolerance mechanisms, as follows:

[0048] Step 2.4.1. Design an exception approval branch mechanism. During process operation, once the process engine detects that the configuration conditions trigger an exception condition node, it will automatically interrupt the original approval process and switch to the predefined exception handling flowchart;

[0049] Step 2.4.2: Configure the process instance recovery mechanism and snapshot rollback capability. After each process node is executed, the system will record a status snapshot. If a system exception occurs or an intermediate node fails to execute, it will roll back to the most recent valid state to avoid the entire process being invalidated and restarted.

[0050] Furthermore, the design device scheduling and conflict detection method described in step 3 is as follows:

[0051] Step 3.1: Model the device resource status, set up a device cache mechanism, and rank available devices through the device scheduling engine, as follows:

[0052] Step 3.1.1. The equipment scheduling system uniformly models all rentable equipment. Each device exists in the platform as a unique resource unit (RU), which includes multiple attributes such as device ID, SKU model, serial number, warehouse, status, current lease period, historical rental times and ratings, and geographic location.

[0053] Step 3.1.2: The system separates the basic information of the device from the dynamic state and models it separately. The static attributes are stored in the relational database, while the dynamic state is stored in the distributed cache.

[0054] Step 3.1.3: During the system initialization phase, all available devices in the inventory are loaded into the cache layer, and a status index and SKU inverted index are established so that the scheduling module can retrieve a list of matching devices when receiving a scheduling request.

[0055] Step 3.1.4: The system screens the candidate pool of devices based on warehouse location, device frequency, and warranty period, and then ranks them through the device scheduling engine.

[0056] Step 3.2: Design an intelligent scheduling strategy and priority control mechanism, as follows:

[0057] Step 3.2.1: The equipment scheduling process implements resource selection and allocation logic based on the scheduling strategy engine. The scheduling strategy is registered in a plug-in manner and supports a variety of scheduling algorithm combinations, including the optimal strategy based on geographical distance, the inventory balancing strategy, the anti-selection strategy based on equipment usage frequency, and the strategy based on the maximum lease continuity.

[0058] Step 3.2.2: The system configures different scheduling priority models for different SKUs or device types. The priority evaluation is calculated by a scoring function that comprehensively considers the device score, maintenance status, last return time, and predicted availability factor. The scheduling engine extracts the top N devices from the candidate device pool, sorts them by priority score, selects the first one as the target device, and simultaneously initiates a lock operation to the device management service.

[0059] In step 3.2.3, the locking operation uses Redis atomic operations or distributed locking mechanisms to prevent the same device from being occupied by multiple rental processes simultaneously in high-concurrency scenarios. After the lock is successful, the device's available time interval, rental flag, and order information will be written to the status cache and database, and subsequent processes and delivery will be synchronized.

[0060] Step 3.3: Design a lease conflict detection and scheduling dynamic adjustment mechanism, as follows:

[0061] Step 3.3.1. During the scheduling process, a lease conflict detection mechanism is set up to prevent devices from being repeatedly leased or having leases overlap. Each device maintains an occupied timeline structure, which represents the allocated future leases as a set of ordered intervals. When a new scheduling request comes in, the system compares the target lease with the device timeline to determine if there is an overlap. If there is a conflict, the system automatically tries the next device.

[0062] Step 3.3.2: The system sets up a flexible scheduling mechanism, which allows users to recommend alternative rental periods or alternative devices with similar SKU models when conflicts occur;

[0063] Step 3.3.3: After the resource is successfully locked, the system notifies the process engine through the event queue. The process node enters the resource confirmed state, and the approval process continues to the contract generation and payment stage.

[0064] Step 3.3.4: If the number of resource locking failures exceeds the threshold, the system will trigger an exception process, suspend the main process, and request the user to select a new device or modify the lease period;

[0065] Step 3.4: Design a linkage mechanism between scheduling and approval processes, as follows:

[0066] Step 3.4.1. Design a two-way trigger and binding mechanism for approval and scheduling to ensure consistent coordination between the leasing approval process and equipment scheduling. On the one hand, after the approval process reaches the approved point, the system automatically calls the equipment scheduling module to initiate resource matching operations. On the other hand, after the equipment scheduling is completed, the results are written back to the process engine through the message queue to update the current process status.

[0067] Step 3.4.2: Design the resource confirmation node in the process system as an asynchronous node that can monitor scheduling events. The entry condition depends not only on the upstream approval result, but also on whether the equipment scheduling is successful. If the scheduling fails, the node will remain in a suspended state and wait for processing; if it succeeds, the system will continue to execute subsequent tasks.

[0068] Step 3.4.3. The system sets a scheduling timeout recovery mechanism for the locked status to prevent inconsistencies between device locking and process timeouts. If the process does not enter the payment link or lease confirmation within the set time, the locked device will be automatically released and restored to a schedulable state, and the scheduling timeout event will be written into the audit log for the platform to analyze resource utilization and process bottlenecks.

[0069] Furthermore, the design approval execution and process driving method described in step 4 is as follows:

[0070] Step 4.1: Design the task allocation and triggering logic for the approval node, as follows:

[0071] Step 4.1.1: After a rental application is initiated, the process engine automatically instantiates the approval path based on the preloaded process template and creates process nodes one by one. When the process reaches an approval node, the system automatically assigns the approval task to the corresponding approver based on the node binding rules. The task assignment rules include multiple conditions such as the applicant's organizational structure, equipment type, amount and authority matching, and user risk level. The system obtains the list of currently available approvers by calling the user service and authority service, and selects the target approver based on the priority strategy.

[0072] Step 4.1.2: Once the task is successfully assigned, it enters the pending approval state and is pushed to the approver's workstation. The approver can perform operations through the web or mobile portal, including approval, rejection, transfer, countersign, and postscript. Approval operations are transactional operations. After receiving the approval action, the system immediately stores it in the database and notifies the process engine as an event to advance the process status. Approval tasks are traceable. Each approval record is associated with a unique ID, along with a timestamp, operator identity, approval opinion, and node context, which are used for process auditing and exception tracing.

[0073] Step 4.2: Design the automatic approval mechanism and system decision logic as follows:

[0074] Step 4.2.1. Design a conditional automatic approval mechanism to allow the system to automatically complete approval decisions under specific circumstances. The automatic approval trigger conditions are controlled by the approval policy configuration. When executing an approval node, the system will check whether the node meets the automatic approval conditions. If the conditions are met, the process engine will automatically execute the approval action and record the decision reason.

[0075] Step 4.2.2: The automatic approval process simultaneously calls multiple modules, including the credit scoring service, the rental behavior profile library, and the equipment scheduling status table, to form a basis for judgment. The configuration center then centrally manages the rule model to achieve platform-level adjustable configuration, dynamic adjustment, and version rollback.

[0076] Step 4.2.3: Each automatic approval process generates an approval log and adds an automatic approval tag to ensure complete visibility at the platform operation level.

[0077] Step 4.3: Design the process state transition and execution advancement control mechanism, as follows:

[0078] Step 4.3.1: After the approval node completes the operation, the process engine performs state transition operations based on the flow edges in the process definition diagram. The system maintains a state diagram for each process node, defining the predecessor state, successor state, branch conditions, and rollback path. After the approval action is triggered, the system determines whether the current node is a parallel gateway, exclusive gateway, or ordinary serial node, and determines the process direction accordingly.

[0079] Step 4.3.2: Write the progress record of the process status to the process instance table and publish the process events through Kafka for other modules to subscribe to, ensuring state consistency and time synchronization across services.

[0080] Step 4.4: Design the approval exception handling and process rollback mechanism, as follows:

[0081] Step 4.4.1. In actual operation, the approval process may be interrupted or abnormal due to timeouts, incorrect operations, or business changes. To ensure process continuity and data consistency, the system introduces an approval exception handling mechanism and process rollback control strategy. Each approval node can be configured with a timeout strategy, including automatic transfer, automatic rejection, and automatic approval options. Timeout events will be recorded in the exception log and trigger an alarm;

[0082] Step 4.4.2: When a rejection occurs at an approval node, the system automatically determines whether the current node is a single point of failure on the critical path. If so, the entire process is terminated and the status is marked as approval failure. If the node can be rolled back, the system will roll back to the previous state or jump to the manual review node based on the policy.

[0083] Step 4.4.3. Set up the process recovery function. That is, when the system fails or the approver makes an erroneous operation, the administrator can view the process history snapshot through the audit interface and perform a node rollback operation under specific permissions. The process engine will restore the position before the interruption according to the timestamp and status and continue to advance the process.

[0084] Furthermore, the design performance monitoring and status write-back method described in step 5 is specifically as follows:

[0085] Step 5.1: Design the lease start and status awareness trigger mechanism as follows:

[0086] Step 5.1.1: Once the equipment is dispatched and delivered to the user by the logistics system, the system will switch the lease status from pending to leased after the user confirms receipt or the platform detects the logistics receipt event. This status change is uniformly distributed via the rental_start event in Kafka, which is monitored by the process engine and triggers the lease start node.

[0087] Step 5.1.2. The system supports multiple lease start calculation methods, including user active confirmation, automatic logistics receipt, and device power-on detection. If the platform deploys digital products that support IoT communication, the device will actively report the device identification and activation time after the first connection or activation, and the platform will use this to determine the actual start time of use. After the status changes, the platform will call the performance monitoring module to initiate monitoring tasks, including regular verification of device usage status, remaining lease time, and abnormal behavior collection, providing data support for subsequent renewal and breach detection.

[0088] Step 5.2: Design the event management and dynamic log collection method for the contract fulfillment process, as follows:

[0089] Step 5.2.1: While the device is in the leased state, the system continuously performs the fulfillment status monitoring task. The fulfillment monitoring module regularly collects user behavior, device status, and payment record data, including device online rate, whether it is offline for a long time, flashing / jailbreak detection, lease renewal reminder response, and user-initiated maintenance requests. All events are written to the fulfillment log table in chronological order. Each record is accompanied by fields such as device ID, user ID, event type, timestamp, and location. At the same time, it is written to the audit log and user profiling service;

[0090] Step 5.2.2: The system conducts risk assessment based on event weights. High-risk behaviors will trigger potential default warning events.

[0091] Step 5.2.3: Potential breach warning events reversely drive the performance monitoring node in the process engine. When the event meets the preset conditions, the system proactively inserts a manual intervention node, a lease termination judgment node, or a risk review process, forming a dynamic mechanism that coordinates process, performance, and status.

[0092] Step 5.3: Design the control method for the end-of-lease and return acceptance process, as follows:

[0093] Step 5.3.1: When the lease is about to end, the system pushes a renewal reminder through a scheduled task and presets a return reminder time window. If the user initiates a renewal, the system reactivates the lease application sub-process and reuses the original order; if the user does not renew the lease, the system enters the waiting for return state;

[0094] Step 5.3.2: The return process is triggered by the following methods: the user confirms the return on the platform, the pickup task is completed, and the platform verifies that the device has been returned to the warehouse. After the return process is initiated, the device enters the acceptance state. The system calls the operation and maintenance service module to perform software and hardware inspection tasks. The acceptance content includes appearance inspection, functional testing, serial number consistency comparison, and privacy clearance confirmation. The inspection results are returned to the process engine in a structured form.

[0095] Step 5.3.3: After acceptance, the process enters the lease completion node, and the system initiates the deposit release sub-process. If the equipment is intact and there are no abnormalities, the platform automatically initiates a deposit release request to the payment system. If the equipment is damaged, lost, or has outstanding accounts, the system calculates the amount to be deducted based on the compensation policy and generates an invoice, freezing part of the deposit or deducting liquidated damages.

[0096] Step 5.4: Design a credit score write-back and behavior feedback mechanism, as follows:

[0097] Step 5.4.1: After the lease process is closed, the platform will write the fulfillment performance of this order into the credit service module, recording the performance during the lease period in the form of behavioral factors, including whether the equipment was returned on time, whether it was in good condition, whether maintenance was required, whether renewal reminders were responded to, and whether compensation was incurred. The platform will then use the scoring model to adjust the user's credit rating.

[0098] Step 5.4.2: Credit scores determine future review exemption conditions and deposit policies, and also influence subsequent equipment scheduling priorities and service policies. High-credit users are offered review exemption privileges, advance booking privileges, and customized rental services. Meanwhile, low-credit users are restricted from renting high-value equipment or require a higher deposit ratio.

[0099] Step 5.4.3: Write back the credit score and synchronize it to the user profile library, recommendation system, and approval strategy engine to achieve a feedback loop of behavior-score-rules, providing a decision-making basis for the next round of leasing process.

[0100] A scheduling and approval process control device for online digital product leasing is provided. The device is used to implement the scheduling and approval process control method for online digital product leasing. The device includes first to fifth functional modules. The functional modules are specifically as follows:

[0101] The first functional module is used to deploy the basic resource layer on a cloud-native platform that supports containerized scheduling, build a process control system based on an orchestrated workflow engine, and perform system initialization, including initialization of the leasing process engine, equipment resource scheduling module, approval strategy and credit engine, and performance monitoring and status management system.

[0102] The second functional module is used to design the leasing application and process control methods, including leasing request parameter modeling and access control, dynamic process path generation and approval strategy matching, approval node injection and task distribution mechanism, abnormal approval branching and process fault tolerance mechanism;

[0103] The third functional module is used to design equipment scheduling and conflict detection methods, including equipment resource status modeling and caching mechanism, intelligent scheduling strategy and priority control mechanism, lease conflict detection and dynamic scheduling adjustment, and linkage mechanism between scheduling and approval process;

[0104] The fourth functional module is used to design the approval execution and process driving methods, including approval node task allocation and triggering logic, automatic approval mechanism and system judgment logic, process state migration and execution advancement control, approval exception handling and process rollback mechanism;

[0105] The fifth functional module is used to design performance monitoring and status writing back methods, including lease start and status perception trigger mechanism, performance process event management and dynamic log collection, lease end and return acceptance process control, credit score writing back and behavior feedback mechanism.

[0106] A mobile terminal includes a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the program, the scheduling and approval process control method for online rental of digital products is implemented.

[0107] A computer-readable storage medium stores a computer program, which, when executed by a processor, implements the steps of the scheduling and approval process control method for online rental of digital products.

[0108] Compared with the existing technology, the present invention has the following significant advantages: (1) It realizes the coordinated linkage between pre-lease approval and resource scheduling of online digital product leasing, that is, the approval result can immediately trigger the device scheduling behavior, thereby improving the overall flow efficiency; (2) It introduces a process engine mechanism, so that the approval path is automatically arranged according to dynamic parameters such as user credit, lease amount, and device type, thereby realizing the flexibility and differentiation of the approval process; (3) It builds a state-driven performance monitoring mechanism, which realizes the flow control of device status from pre-lease, during lease, and after lease; (4) It improves the overall concurrent processing capability, fault tolerance, and scalability of the system, and adapts to the rental service needs of multiple roles, multiple lease types, and high concurrent user access; (5) Under the premise of ensuring security and compliance, it realizes the automated approval and scheduling linkage for C-end or B-end users, effectively reducing manual operation costs, reducing approval bottlenecks, and improving resource utilization and user experience. It is suitable for scenarios such as digital product leasing platforms and shared device management systems. BRIEF DESCRIPTION OF THE DRAWINGS

[0109] Figure 1 It is a flow chart of the scheduling and approval process control method for online rental of digital products of the present invention. DETAILED DESCRIPTION

[0110] The present invention solves the problems of separation, inefficiency and inconsistency between equipment scheduling and approval processes in existing digital product online rental platforms by constructing a process-driven, data-linked and state-controllable scheduling and approval process control method and device for digital product online rental.

[0111] Combine Figure 1 The present invention provides a scheduling and approval process control method for online rental of digital products, comprising the following steps:

[0112] Step 1: First, prepare the cloud-native operating environment. Then, build a process control system based on the orchestrated workflow engine and initialize the system, including initializing the leasing process engine, equipment resource scheduling module, approval strategy and credit engine, and performance monitoring and status management system.

[0113] Step 2: Design the leasing application and process control method, including leasing request parameter modeling and access control, dynamic process path generation and approval strategy matching, approval node injection and task distribution mechanism, abnormal approval branching and process fault tolerance mechanism;

[0114] Step 3: Design equipment scheduling and conflict detection methods, including equipment resource status modeling and caching mechanism, intelligent scheduling strategy and priority control mechanism, lease conflict detection and dynamic scheduling adjustment, and linkage mechanism between scheduling and approval process;

[0115] Step 4: Design the approval execution and process driving methods, including approval node task allocation and triggering logic, automatic approval mechanism and system judgment logic, process state migration and execution advancement control, approval exception handling and process rollback mechanism;

[0116] Step 5. Design the performance monitoring and status writeback method, including the lease start and status perception trigger mechanism, performance process event management and dynamic log collection, lease end and return acceptance process control, credit score writeback and behavior feedback mechanism.

[0117] As a specific example, in step 1, to support the automated operation of the entire lease approval and scheduling process, the system must complete a series of module-level initialization operations at the initial deployment stage to ensure that each functional component has stable connection capabilities, configuration loading capabilities, service registration capabilities, and event response capabilities. The initialization process covers the process control core framework, lease request interface, equipment resource scheduling subsystem, approval flow engine, and performance monitoring and data persistence mechanism, as follows:

[0118] Step 1.1: Prepare the cloud-native operating environment.

[0119] Step 1.1.1. Deploy the basic resource layer on a cloud-native platform that supports containerized scheduling. This includes a container runtime such as Docker, an orchestration platform such as Kubernetes, a service registration and discovery module such as Consul or Eureka, a configuration center such as Nacos or Spring Cloud Config, a message queue such as Kafka, and a log monitoring system such as Prometheus or Grafana. Each service module is deployed as a container image and logically isolated based on namespaces and service labels.

[0120] Step 1.1.2: When the service starts, read the dynamic parameters of the configuration center, including database address, authentication policy, approval rule template, scheduling algorithm policy, etc., to ensure that the system has cross-tenant, cross-process, and multi-device configurability;

[0121] Step 1.2: Initialize the leasing process engine as follows:

[0122] Step 1.2.1. Build a process control system based on a choreographed workflow engine such as Camunda or Activiti, and load the leasing process definition model. This model uses BPMN or DSL to describe the approval paths, inter-node conditional judgment logic, rollback paths, and exception handling rules.

[0123] Step 1.2.2: The system registers built-in approval node types, including user identity determination node, amount threshold branch node, credit score determination node, manual approval node, and automatic approval node;

[0124] Step 1.2.3: The process engine dynamically loads platform rules through the configuration center, and supports matching different process templates based on device type, applicant role, and lease length parameters.

[0125] The launch of the process engine indicates that the platform has the ability to generate an approval link for any rental request and automatically advance it.

[0126] Step 1.3: Initialize the device resource scheduling module, complete resource library loading, scheduling strategy registration, and conflict detection rule initialization, as follows:

[0127] Step 1.3.1: The system synchronizes device metadata from the device asset management subsystem, including device ID, SKU model, status bit, geographic location, available time window, historical usage records, etc., and builds a resource status cache pool;

[0128] Step 1.3.2: The platform preloads scheduling algorithm plug-ins, such as priority queue scheduling, area priority scheduling, lowest frequency priority scheduling, and rule-weighted mixed scheduling. Administrators can configure and enable policies in the console.

[0129] Step 1.3.3: The conflict detection module creates a resource occupancy map based on the current lease period, occupied resources, and equipment maintenance record data, so that real-time verification can be achieved in the subsequent scheduling stage.

[0130] Step 1.4: Initialize the approval policy and credit engine. During the startup phase, the system loads the approval policy template and credit model into the approval subsystem. The details are as follows:

[0131] Step 1.4.1: The approval policy includes a table of approval permissions for different roles, a table of amount range control, and an approval timeout handling policy. These policies are configured in a rule tree or JSON format and are loaded by the policy management service and injected into the approval engine.

[0132] Step 1.4.3: The credit assessment module launches a local or external model inference engine, loads lightweight scoring models, such as credit segmentation models and risk factor models, and connects to third-party credit reporting services, such as Sesame Credit and Tongdun Technology, to complete user profile queries and trial-free judgments.

[0133] After initialization, the approval system and credit service can work together to determine whether the user enters the automatic approval process branch, thereby reducing manual intervention.

[0134] Step 1.5: Initialize the contract performance monitoring and status management system as follows:

[0135] Step 1.5.1. The performance monitoring module is used to monitor status and record behavior throughout the entire lease lifecycle. During initialization, the system deploys a state controller, defines the various states of the lease process and their transition relationships, and binds corresponding event triggering logic. The states include application pending, approval pending, pending scheduling, leased, returned, maintenance pending, and completed.

[0136] In step 1.5.2, connect the monitoring service to the log system, the device online status awareness module (such as the IoT device status reporting interface), and the order data table to visualize the status of the rental process and detect anomalies. The state controller has self-healing capabilities and can trigger interrupt recovery or manual intervention prompts for events such as process freezes, node timeouts, and user defaults.

[0137] As a specific example, in step 2, we designed a rental application and process control method. Considering that in the process control system for online digital product rentals, the initial step in the rental business is the user submitting a rental application. This application is not only the entry point for the entire process control, but also the trigger source for dynamic process generation, approval policy binding, and equipment scheduling preparation. To achieve the complete construction and efficient advancement from user intent to system process instances, we designed a configurable, scalable, and traceable rental application and process control method, covering key links such as structured encapsulation of rental parameters, dynamic decision-making on approval paths, flowchart instance injection, and process state machine binding. The details are as follows:

[0138] Step 2.1: Model the lease request parameters and perform access control, as follows:

[0139] Step 2.1.1. The user submits a device rental request through the rental application interface on the rental platform frontend. The rental request contains multiple core parameters, including but not limited to the applicant's identity information, device SKU number, desired rental period (start and end time), rental type (standard lease, rent-to-own, flexible renewal, etc.), delivery address, and whether or not to waive deposit. This data is forwarded to the rental process control system via the unified access layer (API Gateway) and serialized into a JSON structure and passed to the rental application module.

[0140] Step 2.1.2: The system performs integrity and format checks on the lease parameters. If any fields are missing, formatted incorrectly, or exceed the specified field's permissions, the system will immediately reject the request and return an error code.

[0141] Step 2.1.3: The access layer performs access frequency limiting, token verification, and signature verification security control operations to prevent illegal requests or repeated submissions from causing system pressure.

[0142] Step 2.1.4: After the parameter verification passes, the system binds the request context to the current user session, providing a user identification link for subsequent process control;

[0143] Step 2.2: Dynamically generate the process path and match it with the approval strategy, as follows:

[0144] Step 2.2.1: After receiving all the parameters, the rental application module encapsulates them into a process context object and passes it to the flowchart construction engine. At this stage, the system performs a multi-dimensional analysis of the parameters submitted by the applicant based on the "process configuration rules" set by the platform and generates an adapted approval path diagram;

[0145] Step 2.2.2: The path generation process is based on a comprehensive assessment of the following dimensions: First, user credit rating. Low-credit users must go through the full approval process, while high-credit users can enjoy automatic or simplified approval. Second, the rental amount. If the total rental amount exceeds the set threshold, a financial review node or supervisor approval node must be added. Third, the equipment risk factor. Different equipment types (such as high-value photography equipment vs. ordinary tablets) will have different approval processes. Fourth, factors such as the rental period limit, deposit ratio, and contract type specified in the business rules.

[0146] Step 2.2.3: Use BPMN modeling or DSL configuration to build a flowchart. The process engine generates a process template diagram and, based on this, a specific process instance. This instance is bound to a unique process ID and corresponds one-to-one with the rental order, supporting process tracking and status recovery. If the platform enables process visualization, the approver can view the entire process chain and the current node progress on the workbench, improving the explainability and transparency of the approval process.

[0147] Step 2.3: Design the approval node injection and task distribution mechanism, as follows:

[0148] Step 2.3.1: After the flowchart is generated, the system will inject approval tasks based on the node definitions in the flowchart. Each approval node is considered a "schedulable process task." The system automatically retrieves the approver based on the role binding logic in the node definition (e.g., "Level 1 approval is completed by the head of the applicant's department") and queries their role identity, current available status, and approval permissions through the user service.

[0149] Step 2.3.2: Use a task distribution mechanism that supports parallel and serial processing, as well as multi-person collaborative approval, preemptive approval, or countersignature processing for complex scenarios;

[0150] Step 2.3.3: After being distributed, each approval task will enter the pending queue and be pushed to the target approver. The approver can view, approve, reject or transfer the task through the platform interface;

[0151] Step 2.3.4: The system sets a maximum response time for each approval node. If the time is exceeded, the "timeout transfer to review" policy or "default processing" policy will be automatically triggered, and the event will be written into the process log for audit purposes;

[0152] Step 2.3.5: Task status is managed by the process engine. The state machine migrates based on the task execution results and automatically enters the next process node. State migration between all nodes follows strictly defined transition rules to ensure that the process can ultimately converge to the two exit states of "approved" or "approval rejected" under different approval paths.

[0153] Step 2.4: Design abnormal approval branches and process fault tolerance mechanisms, as follows:

[0154] Step 2.4.1. Considering the complexities of digital product leasing, such as user profile discrepancies, tight equipment inventory, and risk anomaly warnings, an exception approval branch mechanism is designed. During process execution, once the process engine detects that a configuration condition triggers an "abnormal condition node," such as a low risk score, failed deposit payment, or equipment scheduling failure, the original approval process will be automatically interrupted and switched to a predefined exception handling flowchart. For example, if a user's credit is insufficient, the system will automatically insert a "manual review" node and notify the risk control administrator to intervene in the review. In the event of a device conflict, the process will switch to the "alternative device selection and approval" process.

[0155] Step 2.4.2: To enhance the robustness of the process, configure the process instance recovery mechanism and the "snapshot rollback" capability. After each process node is executed, the system will record a status snapshot. If a system exception occurs or an intermediate node fails to execute, it can be rolled back to the most recent valid state, avoiding the entire process from being invalidated and restarted, thereby improving system stability and user experience.

[0156] As a specific example, in step 3, we design a device scheduling and conflict detection method. The device scheduling module is used to intelligently match the optimal device resources and perform inventory locking, resource allocation, and scheduling operations based on the current lease application and approval status during the lease approval process. Considering the wide variety of digital products, dynamic changes in inventory status, overlapping and conflicting lease periods, and other issues, the system has designed a set of device scheduling and conflict detection methods that combine real-time and optimization capabilities to ensure accurate and efficient resource allocation, and to maintain consistency and linkage with the lease process status. The details are as follows:

[0157] Step 3.1: Model the device resource status, set up a device cache mechanism, and rank available devices through the device scheduling engine, as follows:

[0158] Step 3.1.1. The equipment scheduling system uniformly models all rentable equipment. Each device exists in the platform as a unique resource unit (RU), which includes multiple attributes such as device ID, SKU model, serial number, warehouse, status, current lease period, historical rental times and ratings, and geographic location.

[0159] Step 3.1.2: The system separates and models the basic device information from the dynamic state. Static attributes are stored in a relational database, while the dynamic state is stored in a distributed cache (such as Redis) to improve high-concurrency read and write performance.

[0160] Step 3.1.3: During the system initialization phase, all available devices in the inventory are loaded into the cache layer, and a status index and SKU inverted index are established to facilitate the scheduling module to quickly retrieve the matching device list when receiving a scheduling request;

[0161] Step 3.1.4: The system screens the candidate pool of devices based on warehouse location, device frequency, and warranty period, and then ranks them through the device scheduling engine.

[0162] Step 3.2: Design an intelligent scheduling strategy and priority control mechanism, as follows:

[0163] Step 3.2.1: The device scheduling process implements resource selection and allocation logic based on the scheduling strategy engine. Scheduling strategies are registered as plug-ins and support a variety of scheduling algorithm combinations, including the optimal strategy based on geographical distance (selecting equipment in the warehouse closest to the user), the inventory balancing strategy (reducing the concentration of inventory of the same SKU in a single warehouse), the anti-selection strategy based on device usage frequency (preferring less frequently used devices to balance the load), and the strategy based on lease continuity maximization (avoiding device idle fragmentation).

[0164] Step 3.2.2: The system configures different scheduling priority models for different SKUs or device types. The priority evaluation is calculated by a scoring function that comprehensively considers the device score, maintenance status, last return time, and predicted availability factor. The scheduling engine extracts the top N devices from the candidate device pool, sorts them by priority score, selects the first one as the target device, and simultaneously initiates a "lock" operation to the device management service;

[0165] In step 3.2.3, the locking operation uses Redis atomic operations or distributed locking mechanisms to ensure that the same device is not occupied by multiple rental processes simultaneously in high-concurrency scenarios. After the lock is successful, the device's available time interval, rental flag, and order information will be written to the status cache and database to ensure that subsequent processes and deliveries are synchronized.

[0166] Step 3.3: Design a lease conflict detection and scheduling dynamic adjustment mechanism, as follows:

[0167] Step 3.3.1. During the scheduling process, a lease conflict detection mechanism is set up to prevent devices from having duplicate leases or overlapping leases. Each device maintains an "occupancy timeline structure" that represents the allocated future leases as a set of ordered intervals. When a new scheduling request comes in, the system compares the target lease with the device's timeline to determine if there is an overlap. If there is a conflict, the system automatically tries the next device.

[0168] Step 3.3.2: The system sets up a "flexible scheduling" mechanism, which allows users to recommend alternative rental periods or alternative devices with similar SKU models when conflicts occur, further improving the scheduling success rate. For example, if a user applies to rent a certain model of laptop A for 5 days on May 1st, and the system detects that the device has been reserved until May 3rd, it can recommend adjusting the rental start date to May 6th, or selecting model B with the same configuration;

[0169] Step 3.3.3: The scheduling result not only determines the equipment allocation but also drives the execution of the "Resource Confirmation" node in the leasing process. After the resource is successfully locked, the system notifies the process engine through the event queue, and the process node enters the "Resource Confirmed" state. The approval process can continue to the contract generation and payment stage.

[0170] Step 3.3.4: If the number of resource locking failures exceeds the threshold, the system will trigger an exception process, suspend the main process, and request the user to select a new device or modify the lease period;

[0171] Step 3.4: Design a linkage mechanism between scheduling and approval processes, as follows:

[0172] Step 3.4.1. Design a two-way trigger and binding mechanism for "approval-scheduling" to ensure that the lease approval process and equipment scheduling are consistent and coordinated. On the one hand, after the approval process reaches the "approved" node, the system automatically calls the equipment scheduling module to initiate resource matching operations. On the other hand, after the equipment scheduling is completed, its results are written back to the process engine through the message queue to update the current process status.

[0173] Step 3.4.2: Design the "Resource Confirmation" node in the process system as an asynchronous node that can monitor scheduling events. Its entry condition depends not only on the upstream approval result but also on whether the equipment scheduling is successful. If the scheduling fails, the node will remain in the "suspended" state and wait for processing; if it succeeds, the system will continue to execute subsequent tasks. The entire process has state linkage, consistency verification, and failure rollback capabilities.

[0174] Step 3.4.3. The system sets a "scheduling timeout recovery mechanism" for the locked status to prevent inconsistencies between device locking and process timeouts. If the process does not enter the payment link or lease confirmation within the set time, the locked device will be automatically released and restored to a schedulable state, and the scheduling timeout event will be written into the audit log for the platform to analyze resource utilization and process bottlenecks.

[0175] As a specific example, the approval execution and process-driven methods are designed in step 4. The approval stage is the core link to ensure the legality, compliance, security and controllability of leasing. To achieve efficient distribution of approval nodes, automated judgment, process status linkage and abnormal closed-loop processing, the system has built a set of approval execution and process-driven mechanisms based on the process engine that support dynamic paths, conditional triggering, task scheduling and rollback compensation. Approval nodes can support manual approval, system automatic approval, and multi-role parallel, serial or conditional jump paths, making the leasing process more flexible and controllable. The details are as follows:

[0176] Step 4.1: Design the task allocation and triggering logic for the approval node, as follows:

[0177] Step 4.1.1: After a rental application is initiated, the process engine automatically instantiates the approval path based on the preloaded process template and creates process nodes one by one. When the process reaches a certain approval node, the system automatically assigns the approval task to the corresponding approver based on the node binding rules. The task assignment rules include multiple conditions such as the applicant's organizational structure, equipment type, amount and authority matching, and user risk level. The system obtains the list of currently available approvers by calling the user service and authority service, and selects the target approver based on priority strategies (such as proximity, load balancing, and historical response speed).

[0178] Step 4.1.2: Once the task is successfully assigned, it enters the pending approval state and is pushed to the approver's workstation. The approver can perform operations through the web or mobile portal, including approval, rejection, transfer, countersign, and postscript. Approval operations are transactional operations. After receiving the approval action, the system immediately stores it in the database and notifies the process engine as an event to advance the process status. Approval tasks are traceable. Each approval record is associated with a unique ID, along with a timestamp, operator identity, approval opinion, and node context, which are used for process auditing and exception tracing.

[0179] Step 4.2: Design the automatic approval mechanism and system decision logic as follows:

[0180] Step 4.2.1: To improve approval efficiency and reduce the frequency of manual intervention, a conditional automatic approval mechanism has been designed to allow the system to automatically complete approval decisions under specific circumstances. The trigger conditions for automatic approval are controlled by the approval policy configuration, for example: the user's credit rating is higher than the platform threshold and has no history of lease defaults, the lease amount is lower than the exemption limit, and the equipment inventory is sufficient and is a low-risk category. When executing an approval node, the system will check whether the node meets the automatic approval conditions. If the conditions are met, the process engine will automatically execute the "Agree" action and record the reason for the judgment;

[0181] Step 4.2.2: The automatic approval process simultaneously calls multiple modules, including the credit scoring service, the rental behavior profile library, and the equipment scheduling status table, to form a basis for judgment. The configuration center then centrally manages the rule model to achieve platform-level adjustable configuration, dynamic adjustment, and version rollback.

[0182] Step 4.2.3: Each automatic approval process generates an approval log and adds the "Automatic Approval" tag to ensure complete visibility at the platform operation level.

[0183] Step 4.3: Design the process state transition and execution advancement control mechanism, as follows:

[0184] Step 4.3.1: After the approval node completes the operation, the process engine performs state migration operations based on the flow edges (Sequence Flow) in the process definition diagram. The system maintains a state diagram for each process node, defining its predecessor state, successor state, branch conditions, and rollback path. After the approval action is triggered, the system determines whether the current node is a parallel gateway, exclusive gateway, or ordinary serial node, and determines the process direction accordingly.

[0185] For example, if the amount exceeds the threshold, the approval process will generate two approval nodes in parallel, one for the department head and one for the financial auditor. Both tasks must be completed before the process can proceed. If either node is rejected, the process will terminate or enter the review process. The process supports dynamic path decision-making, meaning that certain approval nodes are only activated when preconditions are met, such as "inserting a contract review node only when the lease period exceeds 60 days."

[0186] Step 4.3.2: Write the progress record of the process status to the process instance table and publish the process events through Kafka for other modules (such as equipment scheduling, contract generation, payment services, etc.) to subscribe to, ensuring state consistency and time synchronization across services;

[0187] Step 4.4: Design the approval exception handling and process rollback mechanism, as follows:

[0188] Step 4.4.1. In actual operation, the approval process may be interrupted or abnormal due to timeouts, incorrect operations, business changes, etc. To ensure process continuity and data consistency, the system introduces an approval exception handling mechanism and process rollback control strategy. Each approval node can be configured with a "timeout strategy", including automatic transfer, automatic rejection, and automatic approval options. Timeout events will be recorded in the exception log and trigger an alarm;

[0189] Step 4.4.2: When a rejection occurs at an approval node, the system automatically determines whether the current node is a single point of failure on the critical path. If so, the entire process is terminated and the status is marked as "Approval Failed." If the node can be rolled back, such as a partial rejection during a parallel review, the system will roll back to the previous state or jump to the manual review node based on the policy.

[0190] Step 4.4.3: Set up the "Process Recovery" function. This means that if a system failure or an approver's error occurs, the administrator can view historical snapshots of the process through the audit interface and, under specific permissions, perform a node rollback. The process engine will then restore the process to its previous position based on timestamps and status, continuing the process. This mechanism ensures process stability and fault tolerance in complex processes.

[0191] As a specific example, the performance monitoring and status writeback method designed in step 5 not only emphasizes the front-end flow efficiency of lease application, approval, and scheduling, but also focuses on the performance process monitoring and status-driven feedback mechanism of the equipment during the lease period. The system achieves transparent management of the performance status from "lease start" to "return acceptance" through full-process tracking and state machine-driven control of the lease life cycle, and links business process advancement and credit system updates at each key node, ultimately forming a closed-loop, auditable, and feedback-based performance control method, as follows:

[0192] Step 5.1: Design the lease start and status awareness trigger mechanism as follows:

[0193] Step 5.1.1: Once the equipment is dispatched and delivered to the user by the logistics system, the system will switch the lease status from "pending fulfillment" to "renting" after the user confirms receipt or the platform detects the logistics receipt event. This status change is uniformly distributed via the rental_start event in Kafka, which is monitored by the process engine and triggers the "lease start" node.

[0194] Step 5.1.2. The system supports multiple lease start calculation methods, including active user confirmation, automatic logistics receipt, and device power-on detection. If the platform deploys digital products that support IoT communication, such as smartphones and wearable devices, the devices will actively report the device identification and activation time after the first connection or activation, and the platform will accurately determine the actual start time based on this. After the status changes, the platform will call the performance monitoring module to initiate monitoring tasks, including regular verification of device usage status, remaining lease time, and abnormal behavior collection, providing data support for subsequent renewal and breach detection.

[0195] Step 5.2: Design the event management and dynamic log collection method for the contract fulfillment process, as follows:

[0196] Step 5.2.1: While the device is in the "rental" state, the system continuously performs the fulfillment status monitoring task. The fulfillment monitoring module regularly collects user behavior, device status, and payment record data, including device online rate, whether it is offline for a long time, flashing / jailbreak detection, lease renewal reminder response, and user-initiated maintenance requests. All events are written to the "Fulfillment Log Table" in chronological order. Each record is accompanied by fields such as device ID, user ID, event type, timestamp, and location. At the same time, it is written to the audit log and user profiling service;

[0197] Step 5.2.2: The system performs a risk assessment based on event weights. For example, high-risk behaviors such as equipment being offline for three consecutive days or frequently refusing renewal reminders will trigger a "potential breach of contract warning" event.

[0198] Step 5.2.3: The "Potential Default Warning" event reversely drives the "Performance Monitoring Node" in the process engine. When the event meets the preset conditions, the system proactively inserts a manual intervention node, a lease termination judgment node, or a risk review process, forming a dynamic mechanism that coordinates "process-performance-status";

[0199] Step 5.3: Design the control method for the end-of-lease and return acceptance process, as follows:

[0200] Step 5.3.1: When the lease is about to end, the system pushes a renewal reminder through a scheduled task and presets a "return reminder" time window. If the user initiates a renewal, the system reactivates the lease application sub-process and reuses the original order; if the user does not renew the lease, the system enters the "waiting for return" state;

[0201] Step 5.3.2: The return process is triggered by the following methods: the user confirms the return on the platform, the pickup task is completed, and the platform verifies that the device has been returned to the warehouse. After the return process is initiated, the device enters the "Inspection" state, and the system calls the operation and maintenance service module to perform software and hardware inspection tasks. The inspection content includes appearance inspection, functional testing, serial number consistency comparison, and privacy clearance confirmation. The inspection results are returned to the process engine in a structured form.

[0202] Step 5.3.3: After the acceptance is completed, the process enters the "Lease Completed" node, and the system initiates the deposit release sub-process. If the equipment is intact and there are no abnormalities, the platform automatically initiates a "deposit release" request to the payment system. If the equipment is damaged, lost, or has outstanding accounts, the system calculates the amount to be deducted based on the compensation policy and generates an invoice, freezing part of the deposit or deducting liquidated damages.

[0203] Step 5.4: Design a credit score write-back and behavior feedback mechanism, as follows:

[0204] Step 5.4.1: After the lease process is closed, the platform will write the order's fulfillment performance into the credit service module, recording the lease performance in the form of "behavioral factors," including whether the equipment was returned on time, whether it was in good condition, whether maintenance was required, whether renewal reminders were responded to, and whether compensation was incurred. The platform will then use the scoring model to adjust the user's credit rating.

[0205] Step 5.4.2: Credit scores not only determine future review exemption conditions and deposit policies, but also influence subsequent equipment scheduling priorities and service policies. High-credit users are offered review exemption privileges, advance booking privileges, and customized rental services. Meanwhile, low-credit users are restricted from renting high-value equipment or require a higher deposit ratio.

[0206] Step 5.4.3: Write back the credit score and synchronize it to the user profile library, recommendation system, and approval strategy engine to achieve a "behavior-score-rule" feedback loop, providing a decision-making basis for the next round of leasing process.

[0207] The present invention also provides a scheduling and approval process control device for online digital product leasing, which is used to implement the scheduling and approval process control method for online digital product leasing. The device includes first to fifth functional modules, and the functional modules are specifically as follows:

[0208] The first functional module is used to deploy the basic resource layer on a cloud-native platform that supports containerized scheduling, build a process control system based on an orchestrated workflow engine, and perform system initialization, including initialization of the leasing process engine, equipment resource scheduling module, approval strategy and credit engine, and performance monitoring and status management system.

[0209] The second functional module is used to design the leasing application and process control methods, including leasing request parameter modeling and access control, dynamic process path generation and approval strategy matching, approval node injection and task distribution mechanism, abnormal approval branching and process fault tolerance mechanism;

[0210] The third functional module is used to design equipment scheduling and conflict detection methods, including equipment resource status modeling and caching mechanism, intelligent scheduling strategy and priority control mechanism, lease conflict detection and dynamic scheduling adjustment, and linkage mechanism between scheduling and approval process;

[0211] The fourth functional module is used to design the approval execution and process driving methods, including approval node task allocation and triggering logic, automatic approval mechanism and system judgment logic, process state migration and execution advancement control, approval exception handling and process rollback mechanism;

[0212] The fifth functional module is used to design performance monitoring and status writing back methods, including lease start and status perception trigger mechanism, performance process event management and dynamic log collection, lease end and return acceptance process control, credit score writing back and behavior feedback mechanism.

[0213] The present invention also provides a mobile terminal, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the program, the scheduling and approval process control method for online rental of digital products is implemented.

[0214] The present invention also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps in the scheduling and approval process control method for online rental of digital products.

[0215] The present invention will be further described in detail below with reference to the accompanying drawings and specific embodiments.

[0216] Example

[0217] This invention deploys a basic resource layer on a cloud-native platform that supports containerized scheduling. It builds a process control system based on an orchestrated workflow engine, encompassing lease application, dynamic approval, intelligent scheduling, and contract performance monitoring. After a user submits a lease request, the system automatically generates an approval process based on their credit rating, lease term, and equipment type, and distributes it to the relevant approval nodes. Once approved, the scheduling module allocates and locks resources based on real-time inventory, geographic location, and equipment status. The system uses an event-driven mechanism to manage the state transitions at each lease stage, and supports scheduling adjustments driven by approval results.

[0218] This example demonstrates the entire process of renting a digital camera online. The details are as follows:

[0219] Assume that user A is a registered user with real-name authentication information on the platform and a credit rating of B (medium). He now wants to rent a high-end digital camera (model SKU: D-Canon-5D) for a short-term photography mission from June 10, 2025 to June 17, 2025. The platform system is deployed in a Kubernetes-based public cloud environment. The process control engine is implemented using Camunda, the device management uses a combination of Redis cache and MySQL, and the message bus uses Kafka.

[0220] 1. Lease application submission and process generation

[0221] User A initiates a rental application through the front-end mini-program, selecting the device model "D-Canon-5D," entering a rental period of "7 days," selecting a delivery address, and submitting a deposit. The front-end calls the platform gateway API / rental / submit and submits a structured request body.

[0222] After completing token verification, the gateway routes the data to the "rental application module," which first verifies the legitimacy of the parameters, including the legality of the SKU, the reasonableness of the lease period, and whether the credit rating meets the rental requirements. The request is then encapsulated as a RentalRequestContext object and passed to the Camunda process engine.

[0223] The process engine identifies the user's credit rating as B, and the lease term and amount do not exceed the approval threshold. It matches the process template flow_template_basic_review and generates a process instance ProcessInstanceID=R-02345, which includes two approval nodes: department head approval and system automatic credit assessment node.

[0224] 2. Approval Task Execution and Status Advancement

[0225] The process engine enters the first approval node, the "System Credit Judgment Node." This node calls the credit service and checks the user's credit score, which is 675. The deposit-free rule fails to trigger, but the automatic approval conditions are met (the platform configures manual credit approval for credit-free applications at a level of C or higher). The system automatically marks this node as "Approved" and writes it to the approval log.

[0226] The process enters the "Supervisor Approval" node, where B, head of the platform's leasing department, receives the task push. B reviews the process flow diagram in the web-based approval workbench, confirms the user identity is correct, and manually clicks "Agree." The process engine records the approver, approval opinion, and approval timestamp, and generates an "Approval Completed" event, which is sent to the Kafka topic approval_events.

[0227] 3. Device Scheduling and Resource Locking

[0228] The approval event is subscribed to by the device scheduling module, which then begins executing resource matching logic. Based on the SKU D-Canon-5D, the system searches the Redis cache for all devices with an "available" status and no lease conflicts. It then selects the device numbered "DEV-00567," located in the Chengdu warehouse, closest to the user, with a high rating and the highest scheduling priority.

[0229] The system performs a device lock operation and successfully obtains the Redis distributed lock lock:device:DEV-00567. The status is written as "pending shipment", the device is bound to order "R-02345", and the data is written to the database and device log.

[0230] After the process engine monitors the scheduling result event, the process advances to the "Resource Confirmation" node and the status changes to "Pending Payment".

[0231] 4. Payment Completion and Lease Start

[0232] User A completes the rent and deposit payment through the payment platform. The platform receives the payment callback event / callback / payment, confirming the successful payment. The system updates the order status to "Paid," and the process moves to the "Awaiting Fulfillment" stage.

[0233] The device is shipped by the platform's third-party logistics. After the logistics sign, the event device_delivered is reported to Kafka. The process engine captures it and switches it to the "rental" state. The performance monitoring task is automatically started and the device usage status is periodically recorded.

[0234] V. Contract Performance Monitoring and Lease Expiration

[0235] During the rental process, the platform recorded the device's daily online status, user usage behavior, and whether any warning events were triggered. No breach of contract or maintenance requests occurred. After the rental period ended on June 17, User A clicked "Confirm Return" on the app, and the platform initiated the device return process.

[0236] The operation and maintenance personnel complete the equipment appearance, function and data inspection in the warehouse. The system determines that the "equipment is intact", and the deposit is automatically unfrozen and returned to the user's account through the payment system.

[0237] 6. Process Closure and Rating Feedback

[0238] The process engine enters the "Lease Completed" node, marking the entire process instance as "Ended." The fulfillment record is written into the "User Credit Profile Library." User A receives a complete fulfillment record, and the system increases their credit score by 15 points. The "No Manual Approval" rule is automatically triggered for the next lease.

[0239] The present invention improves the approval efficiency of online digital product rentals, reduces manual intervention costs, and ensures the rationality and traceability of device resource allocation. It is suitable for scenarios such as digital product rental platforms and shared device management systems.

[0240] The above are only preferred embodiments of the present invention. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present invention. These improvements and modifications should also be regarded as the scope of protection of the present invention.

Claims

1. A scheduling and approval process control method for online rental of digital products, characterized by: The following steps are involved: Step 1: First, prepare the cloud-native operating environment. Then, build a process control system based on the orchestrated workflow engine and initialize the system, including initializing the leasing process engine, equipment resource scheduling module, approval strategy and credit engine, and performance monitoring and status management system. Step 2: Design the leasing application and process control method, including leasing request parameter modeling and access control, dynamic process path generation and approval strategy matching, approval node injection and task distribution mechanism, abnormal approval branching and process fault tolerance mechanism; Step 3: Design equipment scheduling and conflict detection methods, including equipment resource status modeling and caching mechanism, intelligent scheduling strategy and priority control mechanism, lease conflict detection and dynamic scheduling adjustment, and linkage mechanism between scheduling and approval process; Step 4: Design the approval execution and process driving methods, including approval node task allocation and triggering logic, automatic approval mechanism and system judgment logic, process state migration and execution advancement control, approval exception handling and process rollback mechanism; Step 5. Design the performance monitoring and status writeback method, including the lease start and status perception trigger mechanism, performance process event management and dynamic log collection, lease end and return acceptance process control, credit score writeback and behavior feedback mechanism.

2. The scheduling and approval process control method for online digital product leasing according to claim 1 is characterized in that: Step 1 includes step 1.1, which involves deploying the basic resource layer on a cloud-native platform that supports containerized scheduling and completing the preparation of the cloud-native operating environment. The details are as follows: Step 1.1.

1. Deploy the basic resource layer on a cloud-native platform that supports containerized scheduling, including the container runtime, orchestration platform, service registration and discovery module, configuration center, message queue, and log monitoring system. Each service module is deployed as a container image and logically isolated based on namespaces and service labels. Step 1.1.2: When the service starts, read the dynamic parameters of the configuration center, including the database address, authentication policy, approval rule template, and scheduling algorithm policy, so that the system has cross-tenant, cross-process, and multi-device category configuration capabilities.

3. The scheduling and approval process control method for online digital product leasing according to claim 2 is characterized in that: Build a process control system based on the choreographed workflow engine described in step 1 and initialize the system as follows: Step 1.2: Initialize the leasing process engine as follows: Step 1.2.

1. Build a process control system based on a programmable workflow engine and load the leasing process definition model. This model uses BPMN or DSL to describe the approval paths, inter-node conditional judgment logic, rollback paths, and exception handling rules. Step 1.2.2: The system registers built-in approval node types, including user identity determination node, amount threshold branch node, credit score determination node, manual approval node, and automatic approval node; Step 1.2.3: The process engine dynamically loads platform rules through the configuration center, supporting matching different process templates based on device type, applicant role, and lease length parameters; Step 1.3: Initialize the device resource scheduling module, as follows: Step 1.3.

1. The system synchronizes device metadata from the device asset management subsystem, including device ID, SKU model, status bit, geographic location, available time window, and historical usage records, and builds a resource status cache pool. Step 1.3.2: The platform preloads the scheduling algorithm plug-in, and the administrator configures the activation policy in the console; Step 1.3.3: The conflict detection module creates a resource occupancy map based on the current lease period, occupied resources, and equipment maintenance record data, which is used for real-time verification in the subsequent scheduling stage. Step 1.4: Initialize the approval strategy and credit engine, as follows: Step 1.4.1: The approval policy includes a table of approval permissions for different roles, a table of amount range control, and an approval timeout handling policy. These policies are configured in a rule tree or JSON format and are loaded by the policy management service and injected into the approval engine. Step 1.4.3: The credit assessment module starts a local or external model inference engine, loads a lightweight scoring model, and connects to a third-party credit reporting service to complete user profile queries and trial-free judgments. Step 1.5: Initialize the contract performance monitoring and status management system as follows: Step 1.5.

1. The performance monitoring module is used to monitor and record status throughout the entire lease lifecycle. During initialization, the system deploys a state controller to define the various states and transition relationships of the lease process, including application pending, approval pending, pending scheduling, leased, returned, maintenance pending, and completed, and binds corresponding event triggering logic. Step 1.5.2: Connect the monitoring service to the log system, the device online status perception module, and the order data table to visualize the status and capture anomalies during the rental process.

4. The scheduling and approval process control method for online digital product leasing according to claim 1 is characterized in that: The design lease application and process control method described in step 2 is as follows: Step 2.1: Model the lease request parameters and perform access control, as follows: Step 2.1.1: The user submits a device rental request through the rental application interface on the rental platform. The rental request contains multiple core parameters, including applicant identity information, device SKU number, desired rental period, rental type, delivery address, and whether to waive deposit. These core parameters are forwarded to the process control system via the unified access layer API Gateway and serialized into a JSON structure and passed to the rental application module. Step 2.1.2: The system performs integrity and format checks on the lease parameters. If any fields are missing, formatted incorrectly, or exceed the specified field's permissions, the system will refuse to proceed to the main process and return the corresponding error code. Step 2.1.3: The access layer performs security control operations such as access rate limiting, token verification, and signature verification to prevent illegal requests or repeated submissions from causing system pressure. Step 2.1.4: After the parameter verification passes, the system binds the request context to the current user session, providing a user identification link for subsequent process control; Step 2.2: Dynamically generate the process path and match it with the approval strategy, as follows: Step 2.2.1: After receiving the complete parameters, the rental application module encapsulates them into a process context object and passes it to the flowchart construction engine. At this stage, the system performs a multi-dimensional analysis of the parameters submitted by the applicant based on the process configuration rules set by the platform and generates an adapted approval path diagram. Step 2.2.2: The path generation process is based on a comprehensive assessment of the following dimensions: First, user credit rating. Low-credit users must go through the full approval process, while high-credit users can enjoy automatic or simplified approval. Second, the rental amount. If the total rental amount exceeds the set threshold, a financial review node or supervisor approval node must be added. Third, the equipment risk factor. Different equipment types will have different approval processes. Fourth, factors such as the lease term limit, deposit ratio, and contract type in the business rules. Step 2.2.3: Use BPMN modeling or DSL configuration to build a flowchart. The process engine generates a process template diagram and then generates a specific process instance. This instance is bound to a unique process ID and corresponds one-to-one with the rental order. It supports process tracking and status recovery. If the platform enables the process visualization option, the approver can view the complete process link and the current node progress on the workbench; Step 2.3: Design the approval node injection and task distribution mechanism, as follows: Step 2.3.1: After the flowchart is generated, the system will inject approval tasks based on the node definitions in the flowchart. Each approval node is considered a schedulable process task. The system automatically retrieves the approver based on the role binding logic in the node definition and queries their role identity, current available status, and approval permissions through the user service. Step 2.3.2: Use a task distribution mechanism to support parallel and serial processing, as well as complex scenarios such as multi-person collaborative approval, preemptive approval, or countersignature processing; Step 2.3.3: After being distributed, each approval task will enter the pending queue and be pushed to the target approver. The approver can view, approve, reject or transfer the task through the platform interface. Step 2.3.4: The system sets a maximum response time for each approval node. If the time is exceeded, the timeout transfer policy or default processing policy will be automatically triggered, and the event will be written into the process log for audit purposes; Step 2.3.5: Task status is managed by the process engine. The state machine migrates based on the task execution results and automatically enters the next process node. The state transitions between all nodes follow the defined transition rules, ensuring that the process can ultimately converge to two exit states: approved or rejected under different approval paths. Step 2.4: Design abnormal approval branches and process fault tolerance mechanisms, as follows: Step 2.4.

1. Design an exception approval branch mechanism. During process operation, once the process engine detects that the configuration conditions trigger an exception condition node, it will automatically interrupt the original approval process and switch to the predefined exception handling flowchart; Step 2.4.2: Configure the process instance recovery mechanism and snapshot rollback capability. After each process node is executed, the system will record a status snapshot. If a system exception occurs or an intermediate node fails to execute, it will roll back to the most recent valid state to avoid the entire process being invalidated and restarted.

5. The scheduling and approval process control method for online digital product leasing according to claim 1 is characterized in that: The design device scheduling and conflict detection method described in step 3 is as follows: Step 3.1: Model the device resource status, set up a device cache mechanism, and rank available devices through the device scheduling engine, as follows: Step 3.1.

1. The equipment scheduling system uniformly models all rentable equipment. Each device exists in the platform as a unique resource unit (RU), which includes multiple attributes such as device ID, SKU model, serial number, warehouse, status, current lease period, historical rental times and ratings, and geographic location. Step 3.1.2: The system separates the basic information of the device from the dynamic state and models it separately. The static attributes are stored in the relational database, while the dynamic state is stored in the distributed cache. Step 3.1.3: During the system initialization phase, all available devices in the inventory are loaded into the cache layer, and a status index and SKU inverted index are established so that the scheduling module can retrieve a list of matching devices when receiving a scheduling request. Step 3.1.4: The system screens the candidate pool of devices based on warehouse location, device frequency, and warranty period, and then ranks them through the device scheduling engine. Step 3.2: Design an intelligent scheduling strategy and priority control mechanism, as follows: Step 3.2.1: The equipment scheduling process implements resource selection and allocation logic based on the scheduling strategy engine. The scheduling strategy is registered in a plug-in manner and supports a variety of scheduling algorithm combinations, including the optimal strategy based on geographical distance, the inventory balancing strategy, the anti-selection strategy based on equipment usage frequency, and the strategy based on the maximum lease continuity. Step 3.2.2: The system configures different scheduling priority models for different SKUs or device types. The priority evaluation is calculated by a scoring function that comprehensively considers the device score, maintenance status, last return time, and predicted availability factor. The scheduling engine extracts the top N devices from the candidate device pool, sorts them by priority score, selects the first one as the target device, and simultaneously initiates a lock operation to the device management service. In step 3.2.3, the locking operation uses Redis atomic operations or distributed locking mechanisms to prevent the same device from being occupied by multiple rental processes simultaneously in high-concurrency scenarios. After the lock is successful, the device's available time interval, rental flag, and order information will be written to the status cache and database, and subsequent processes and delivery will be synchronized. Step 3.3: Design a lease conflict detection and scheduling dynamic adjustment mechanism, as follows: Step 3.3.

1. During the scheduling process, a lease conflict detection mechanism is set up to prevent devices from being repeatedly leased or having leases overlap. Each device maintains an occupied timeline structure, which represents the allocated future leases as a set of ordered intervals. When a new scheduling request comes in, the system compares the target lease with the device timeline to determine if there is an overlap. If there is a conflict, the system automatically tries the next device. Step 3.3.2: The system sets up a flexible scheduling mechanism, which allows users to recommend alternative rental periods or alternative devices with similar SKU models when conflicts occur; Step 3.3.3: After the resource is successfully locked, the system notifies the process engine through the event queue. The process node enters the resource confirmed state, and the approval process continues to the contract generation and payment stage. Step 3.3.4: If the number of resource locking failures exceeds the threshold, the system will trigger an exception process, suspend the main process, and request the user to select a new device or modify the lease period; Step 3.4: Design a linkage mechanism between scheduling and approval processes, as follows: Step 3.4.

1. Design a two-way trigger and binding mechanism for approval and scheduling to ensure consistent coordination between the leasing approval process and equipment scheduling. On the one hand, after the approval process reaches the approved point, the system automatically calls the equipment scheduling module to initiate resource matching operations. On the other hand, after the equipment scheduling is completed, the results are written back to the process engine through the message queue to update the current process status. Step 3.4.2: Design the resource confirmation node in the process system as an asynchronous node that can monitor scheduling events. The entry condition depends not only on the upstream approval result, but also on whether the equipment scheduling is successful. If the scheduling fails, the node will remain in a suspended state and wait for processing; if it succeeds, the system will continue to execute subsequent tasks. Step 3.4.

3. The system sets a scheduling timeout recovery mechanism for the locked status to prevent inconsistencies between device locking and process timeouts. If the process does not enter the payment link or lease confirmation within the set time, the locked device will be automatically released and restored to a schedulable state, and the scheduling timeout event will be written into the audit log for the platform to analyze resource utilization and process bottlenecks.

6. The scheduling and approval process control method for online digital product leasing according to claim 1 is characterized in that: The design approval execution and process-driven approach described in step 4 is as follows: Step 4.1: Design the task allocation and triggering logic for the approval node, as follows: Step 4.1.1: After a rental application is initiated, the process engine automatically instantiates the approval path based on the pre-loaded process template and creates process nodes one by one. When the process reaches an approval node, the system automatically assigns the approval task to the corresponding approver based on the node binding rules. Task assignment rules include multiple criteria such as the applicant's organizational structure, device type, amount and authority matching, and user risk level. The system obtains a list of currently available approvers by calling the user service and authority service, and selects the target processor based on the priority strategy. Step 4.1.2: Once the task is successfully assigned, it enters the pending approval state and is pushed to the approver's workstation. The approver can perform operations through the web or mobile portal, including approval, rejection, transfer, countersign, and postscript. Approval operations are transactional operations. After receiving the approval action, the system immediately stores it in the database and notifies the process engine as an event to advance the process status. Approval tasks are traceable. Each approval record is associated with a unique ID, along with a timestamp, operator identity, approval opinion, and node context, which are used for process auditing and exception tracing. Step 4.2: Design the automatic approval mechanism and system decision logic as follows: Step 4.2.

1. Design a conditional automatic approval mechanism to allow the system to automatically complete approval decisions under specific circumstances. The automatic approval trigger conditions are controlled by the approval policy configuration. When executing an approval node, the system will check whether the node meets the automatic approval conditions. If the conditions are met, the process engine will automatically execute the approval action and record the decision reason. Step 4.2.2: The automatic approval process simultaneously calls multiple modules, including the credit scoring service, the rental behavior profile library, and the equipment scheduling status table, to form a basis for judgment. The configuration center then centrally manages the rule model to achieve platform-level adjustable configuration, dynamic adjustment, and version rollback. Step 4.2.3: Each automatic approval process generates an approval log and adds an automatic approval tag to ensure complete visibility at the platform operation level. Step 4.3: Design the process state transition and execution advancement control mechanism, as follows: Step 4.3.1: After the approval node completes the operation, the process engine performs state transition operations based on the flow edges in the process definition diagram. The system maintains a state diagram for each process node, defining the predecessor state, successor state, branch conditions, and rollback path. After the approval action is triggered, the system determines whether the current node is a parallel gateway, exclusive gateway, or ordinary serial node, and determines the process direction accordingly. Step 4.3.2: Write the progress record of the process status to the process instance table and publish the process events through Kafka for other modules to subscribe to, ensuring state consistency and time synchronization across services. Step 4.4: Design the approval exception handling and process rollback mechanism, as follows: Step 4.4.

1. In actual operation, the approval process may be interrupted or abnormal due to timeouts, incorrect operations, or business changes. To ensure process continuity and data consistency, the system introduces an approval exception handling mechanism and process rollback control strategy. Each approval node can be configured with a timeout strategy, including automatic transfer, automatic rejection, and automatic approval options. Timeout events will be recorded in the exception log and trigger an alarm; Step 4.4.2: When a rejection occurs at an approval node, the system automatically determines whether the current node is a single point of failure on the critical path. If so, the entire process is terminated and the status is marked as approval failure. If the node can be rolled back, the system will roll back to the previous state or jump to the manual review node based on the policy. Step 4.4.

3. Set up the process recovery function. That is, when the system fails or the approver makes an erroneous operation, the administrator can view the process history snapshot through the audit interface and perform a node rollback operation under specific permissions. The process engine will restore the position before the interruption according to the timestamp and status and continue to advance the process.

7. The scheduling and approval process control method for online digital product leasing according to claim 1 is characterized in that: The design compliance monitoring and status write-back method described in step 5 is as follows: Step 5.1: Design the lease start and status awareness trigger mechanism as follows: Step 5.1.1: Once the equipment is dispatched and delivered to the user by the logistics system, the system will switch the lease status from pending to leased after the user confirms receipt or the platform detects the logistics receipt event. This status change is uniformly distributed via the rental_start event in Kafka, which is monitored by the process engine and triggers the lease start node. Step 5.1.

2. The system supports multiple lease start calculation methods, including user active confirmation, automatic logistics receipt, and device power-on detection. If the platform deploys digital products that support IoT communication, the device will actively report the device identification and activation time after the first connection or activation, and the platform will use this to determine the actual start time of use. After the status changes, the platform will call the performance monitoring module to initiate monitoring tasks, including regular verification of device usage status, remaining lease time, and abnormal behavior collection, providing data support for subsequent renewal and breach detection. Step 5.2: Design the event management and dynamic log collection method for the contract fulfillment process, as follows: Step 5.2.1: While the device is in the leased state, the system continuously performs the fulfillment status monitoring task. The fulfillment monitoring module regularly collects user behavior, device status, and payment record data, including device online rate, whether it is offline for a long time, flashing / jailbreak detection, lease renewal reminder response, and user-initiated maintenance requests. All events are written to the fulfillment log table in chronological order. Each record is accompanied by fields such as device ID, user ID, event type, timestamp, and location. At the same time, it is written to the audit log and user profiling service; Step 5.2.2: The system conducts risk assessment based on event weights. High-risk behaviors will trigger potential default warning events. Step 5.2.3: Potential breach warning events reversely drive the performance monitoring node in the process engine. When the event meets the preset conditions, the system proactively inserts a manual intervention node, a lease termination judgment node, or a risk review process, forming a dynamic mechanism that coordinates process, performance, and status. Step 5.3: Design the control method for the end-of-lease and return acceptance process, as follows: Step 5.3.1: When the lease is about to end, the system pushes a renewal reminder through a scheduled task and presets a return reminder time window. If the user initiates a renewal, the system reactivates the lease application sub-process and reuses the original order; If the user does not renew the lease, the system enters the waiting for return state; Step 5.3.2: The return process is triggered by the following methods: the user confirms the return on the platform, the pickup task is completed, and the platform verifies that the device has been returned to the warehouse. After the return process is initiated, the device enters the acceptance state. The system calls the operation and maintenance service module to perform software and hardware inspection tasks. The acceptance content includes appearance inspection, functional testing, serial number consistency comparison, and privacy clearance confirmation. The inspection results are returned to the process engine in a structured form. Step 5.3.3: After acceptance, the process enters the lease completion node, and the system initiates the deposit release sub-process. If the equipment is intact and there are no abnormalities, the platform automatically initiates a deposit release request to the payment system. If the equipment is damaged, lost, or has outstanding accounts, the system calculates the amount to be deducted based on the compensation policy and generates an invoice, freezing part of the deposit or deducting liquidated damages. Step 5.4: Design a credit score write-back and behavior feedback mechanism, as follows: Step 5.4.1: After the lease process is closed, the platform will write the fulfillment performance of this order into the credit service module, recording the performance during the lease period in the form of behavioral factors, including whether the equipment was returned on time, whether it was in good condition, whether maintenance was required, whether renewal reminders were responded to, and whether compensation was incurred. The platform will then use the scoring model to adjust the user's credit rating. Step 5.4.2: Credit scores determine future review exemption conditions and deposit policies, and also influence subsequent equipment scheduling priorities and service policies. High-credit users are offered review exemption privileges, advance booking privileges, and customized rental services. Meanwhile, low-credit users are restricted from renting high-value equipment or require a higher deposit ratio. Step 5.4.3: Write back the credit score and synchronize it to the user profile library, recommendation system, and approval strategy engine to achieve a feedback loop of behavior-score-rules, providing a decision-making basis for the next round of leasing process.

8. A scheduling and approval process control device for online rental of digital products, characterized in that: The device is used to implement the scheduling and approval process control method for online rental of digital products as described in any one of claims 1 to 7. The device includes a first functional module to a fifth functional module, and the functional modules are specifically as follows: The first functional module is used to deploy the basic resource layer on a cloud-native platform that supports containerized scheduling, build a process control system based on an orchestrated workflow engine, and perform system initialization, including initialization of the leasing process engine, equipment resource scheduling module, approval strategy and credit engine, and performance monitoring and status management system. The second functional module is used to design the leasing application and process control methods, including leasing request parameter modeling and access control, dynamic process path generation and approval strategy matching, approval node injection and task distribution mechanism, abnormal approval branching and process fault tolerance mechanism; The third functional module is used to design equipment scheduling and conflict detection methods, including equipment resource status modeling and caching mechanism, intelligent scheduling strategy and priority control mechanism, lease conflict detection and dynamic scheduling adjustment, and linkage mechanism between scheduling and approval process; The fourth functional module is used to design the approval execution and process driving methods, including approval node task allocation and triggering logic, automatic approval mechanism and system judgment logic, process state migration and execution advancement control, approval exception handling and process rollback mechanism; The fifth functional module is used to design performance monitoring and status writing back methods, including lease start and status perception trigger mechanism, performance process event management and dynamic log collection, lease end and return acceptance process control, credit score writing back and behavior feedback mechanism.

9. A mobile terminal comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein: When the processor executes the program, the scheduling and approval process control method for online rental of digital products as described in any one of claims 1 to 7 is implemented.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the steps of the scheduling and approval process control method for online rental of digital products as described in any one of claims 1 to 7 are implemented.

Citation Information

Patent Citations

  • Method and apparatus for online rental of vehicles

    CA2963015A1

  • Automatic process system and method

    CN112561494A

  • Automobile financing leasing method and device, storage medium and electronic equipment

    CN117273875A

  • Internet-based vehicle rental management system and device, and storage medium

    CN119558948A

  • Container leasing contract management system and method

    CN120047221A

Cited By

  • Rental business order tracking method and system

    CN121437108A

  • Workflow-based multi-terminal scene arrangement and one-key linkage method and system

    CN121907702A

  • Intelligent management and scheduling method and system for management and control cabinet of mobile portable terminal

    CN121920791A