Data authorization processing method and device, equipment and storage medium

Abstract

The invention relates to the technical field of authorization control, and discloses a data authorization processing method and device, equipment and a storage medium, and the method comprises the steps: obtaining an authorization data item list associated with a financing product in response to an authorization request triggered by the financing product; dynamically configuring a standardized authorization process instance based on the authorization data item list, wherein the standardized authorization process instance comprises a plurality of authorization operation modules arranged according to a preset sequence; the standardized authorization process instance is embedded into the business process of the financing product through a pluggable module assembly; and executing the business process, and returning an authorization result of the target data item required by the financing product. According to the method, the associated authorization data item list is acquired in response to the authorization request of the financing product, so that the data authorization process is standardized and modularized, the experience of a user in different product processes is kept consistent, seamless connection between data authorization and a business process is realized, and the continuity of overall operation is improved.

Description

Technical Field

[0001] The present application relates to the field of authorization control technology, and in particular to a data authorization processing method, apparatus, device and storage medium. Background Art

[0002] Currently, there are many types of online financing products within the bank. Different financing products have developed their own data authorization processes. The processes are different and the development efficiency is low. The user experience of users in different products varies greatly. Summary of the Invention

[0003] The main purpose of this application is to provide a data authorization processing method, device, equipment and storage medium, aiming to solve the technical problems that different financing products develop their own data authorization processes, the development efficiency is low, and the user experience of users in different products varies greatly.

[0004] To achieve the above objectives, this application proposes a data authorization processing method, which includes:

[0005] In response to an authorization request triggered by a financing product, obtaining a list of authorization data items associated with the financing product;

[0006] Dynamically configuring a standardized authorization process instance based on the authorization data item list, wherein the standardized authorization process instance includes a plurality of authorization operation modules arranged in a preset order;

[0007] Embedding the standardized authorization process instance into the business process of the financing product through pluggable module components;

[0008] Execute the business process and return the authorization result of the target data item required by the financing product.

[0009] Optionally, the step of dynamically configuring a standardized authorization process instance based on the authorization data item list includes:

[0010] Acquire association relationship configuration according to preset business fields, wherein the preset business fields include authorized product fields, authorized data item fields, authorized agreement fields, and authorized object fields;

[0011] Based on memory cache and background thread scanning, monitor the change events of the financing product in the association relationship configuration in real time to obtain the change results;

[0012] generating an updated target association relationship configuration according to the change result and the authorization data item list, and determining an authorization protocol module corresponding to the authorization data item list based on the target association relationship configuration;

[0013] The authorization protocol module and the preset authorization operation module are combined in sequence to form the standardized authorization process instance.

[0014] Optionally, the step of generating an updated target association relationship configuration according to the change result and the authorized data item list, and determining an authorization protocol module corresponding to the authorized data item list based on the target association relationship configuration includes:

[0015] Parsing the protocol type identifier in the authorization data item list, and extracting the configuration update item of the change result to obtain the association relationship element;

[0016] Matching and reconstructing the protocol type identifier and the association relationship element to generate a target association relationship configuration;

[0017] The authorization protocol module corresponding to the authorization data item list is determined according to the target association relationship configuration.

[0018] Optionally, the association relationship elements include access configuration parameters in the authorization product field, process control identifiers in the authorization data item field, template version mapping in the authorization protocol field, and validation rule sets in the authorization object field;

[0019] The step of matching and reconstructing the protocol type identifier and the association relationship element to generate a target association relationship configuration includes:

[0020] Refresh the product access endpoint corresponding to the protocol type identifier according to the access configuration parameters;

[0021] reorganizing the data item authorization path corresponding to the protocol type identifier based on the process control identifier;

[0022] Updating the protocol template library index corresponding to the protocol type identifier through the template version mapping;

[0023] Updating the differential data check set according to the verification rule set;

[0024] A target association relationship configuration including the protocol type identifier is generated according to the product access endpoint, the data item authorization path, the protocol template library index and the differential data verification set.

[0025] Optionally, the step of determining the authorization protocol module corresponding to the authorized data item list according to the target association relationship configuration includes:

[0026] Parsing the effective scope of the authorization data in the target association relationship configuration and obtaining the authorization effectiveness process of the target association relationship configuration;

[0027] Based on the effective scope and the authorization effective process, an authorization protocol module is matched from a preset protocol module library.

[0028] Optionally, before the step of executing the business process and returning the authorization result of the target data item required for the financing product, the step further includes:

[0029] Divide the business process into multiple standardized steps to be executed in sequence according to the authorized operation module;

[0030] When detecting that a user performs an authorized operation, storing the user operation data in a structured storage unit according to the standardized steps;

[0031] When a process interruption is detected, the step identifier of the current interruption point is recorded;

[0032] When the user re-enters the process, the process is restored to the step corresponding to the interruption point based on the step identifier and the user operation data.

[0033] Optionally, the step of storing the user operation data in the structured storage unit according to the standardized steps when detecting that the user performs an authorized operation includes:

[0034] Construct a linked list node containing step identifier, step sequence number and operation timestamp;

[0035] Binding the field element data input by the user in each step to the corresponding linked list node;

[0036] The linked list node data is persistently stored in the structured storage unit through the asynchronous saving mechanism, and the step status identifier of the current linked list node is updated each time the step is switched.

[0037] In addition, to achieve the above-mentioned purpose, the present application also proposes a data authorization processing device, which includes:

[0038] a data acquisition module, configured to acquire a list of authorized data items associated with a financing product in response to an authorization request triggered by the financing product;

[0039] A process configuration module, configured to dynamically configure a standardized authorization process instance based on the authorization data item list, wherein the standardized authorization process instance includes a plurality of authorization operation modules arranged in a preset order;

[0040] A process embedding module, used to embed the standardized authorization process instance into the business process of the financing product through a pluggable module component;

[0041] The business execution module is used to execute the business process and return the authorization result of the target data item required by the financing product.

[0042] In addition, to achieve the above-mentioned purpose, the present application also proposes a data authorization processing device, which includes: a memory, a processor, and a computer program stored on the memory and executable on the processor, wherein the computer program is configured to implement the steps of the data authorization processing method as described above.

[0043] In addition, to achieve the above-mentioned purpose, the present application also proposes a storage medium, which is a computer-readable storage medium. A computer program is stored on the storage medium, and when the computer program is executed by the processor, the steps of the data authorization processing method described above are implemented.

[0044] This application discloses a method for obtaining a list of authorized data items associated with a financing product in response to an authorization request triggered by the financing product; dynamically configuring a standardized authorization process instance based on the authorization data item list, wherein the standardized authorization process instance includes multiple authorization operation modules arranged in a preset order; embedding the standardized authorization process instance into the business process of the financing product through a pluggable module component; executing the business process and returning the authorization result of the target data item required by the financing product. By obtaining a list of associated authorized data items in response to the authorization request of the financing product, the data authorization process is standardized and modularized, allowing users to maintain a consistent experience across different product processes, achieving a seamless connection between data authorization and business processes, and improving the consistency of overall operations. BRIEF DESCRIPTION OF THE DRAWINGS

[0045] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0046] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0047] Figure 1 This is a flowchart of the first embodiment of the application data authorization processing method;

[0048] Figure 2 This is the business data authorization interaction flow chart for this application;

[0049] Figure 3 This is a flow chart of the second embodiment of the application data authorization processing method;

[0050] Figure 4 This is a hierarchical diagram of the embedded development model for this application authorization process;

[0051] Figure 5 A relationship diagram for the authorization management of this application;

[0052] Figure 6 This is a flowchart of the third embodiment of the application data authorization processing method;

[0053] Figure 7 This is a flowchart of the fourth embodiment of the application data authorization processing method;

[0054] Figure 8 This is a schematic diagram of the module structure of the data authorization processing device according to an embodiment of the present application;

[0055] Figure 9 This is a schematic diagram of the device structure of the hardware operating environment involved in the data authorization processing method in the embodiment of the present application.

[0056] The purpose, features and advantages of this application will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION

[0057] It should be understood that the specific embodiments described herein are merely used to explain the technical solutions of the present application and are not intended to limit the present application.

[0058] In order to better understand the technical solution of the present application, a detailed description will be given below in conjunction with the accompanying drawings and specific implementation methods.

[0059] The main solution of the embodiment of the present application is: in response to an authorization request triggered by a financing product, obtaining a list of authorization data items associated with the financing product; dynamically configuring a standardized authorization process instance based on the list of authorization data items, the standardized authorization process instance comprising multiple authorization operation modules arranged in a preset order; embedding the standardized authorization process instance into the business process of the financing product through a pluggable module component; executing the business process and returning the authorization result of the target data item required by the financing product.

[0060] Currently, there are many types of online financing products within the bank. Each product implements the data authorization process independently, and the processes are different. The development efficiency is low and it cannot provide a consistent experience for users. The data authorization process among peers is complicated and the operation threshold is high. Some of them require users to sign paper authorization letters offline and cannot be fully online. Signing paper authorization letters will lead to excessively high labor costs due to the geographical distance between users and account managers. Although other parts have online processes, if the process is interrupted, users need to start the operation again. The filled information will not be retained, and there is a lack of breakpoint resumption capability. Users have to repeat operations and the experience is poor.

[0061] Therefore, this application provides an authorization solution based on hot-swappable technology to achieve dynamic expansion of digital financing products and unified processes. The data authorization process is standardized and modularized. The user experience remains consistent in different product processes. The authorization process does not need to be repeatedly developed. The financing product process can be directly embedded in the authorization process. At the same time, data authorization is fully online, supporting user operation to resume breakpoints.

[0062] It should be noted that the execution subject of this embodiment can be a computing service device with data processing, network communication, and program execution functions, such as a computer, or an electronic device capable of performing the above functions. The following uses the authorization system as an example to illustrate this embodiment and the following embodiments.

[0063] Based on this, the embodiment of the present application provides a data authorization processing method, referring to Figure 1 , Figure 1 This is a flowchart of the first embodiment of the application data authorization processing method.

[0064] In this embodiment, the data authorization processing method includes:

[0065] Step S10: In response to the authorization request triggered by the financing product, a list of authorization data items associated with the financing product is obtained.

[0066] It should be noted that financing products are various types of financing services provided by financial institutions to customers, such as loans, letters of credit, factoring, etc. In data authorization scenarios, different financing products have different requirements for the use of customer data. For example, corporate loans may require authorization for corporate financial data, credit records, etc. An authorization request is a request initiated by the financing product system in the business process to the data authorization system to obtain user data access rights. This request usually contains information such as product identification and business scenario, which is used to inform the authorization system which data authorization is required. The authorized data item list is a collection of data items associated with a specific financing product that require user authorization to access.

[0067] It is understood that the data authorization system continuously monitors authorization requests sent by the financing product system. These requests are usually triggered when a user enters a specific business process (such as a loan application). It then parses the product identifier (such as product code, business type, etc.) in the authorization request and locates the corresponding financing product configuration through a preset mapping relationship. Based on the configuration rules of the financing product (such as business type, risk level, etc.), it filters out the data items that require user authorization from the data dictionary or configuration library and generates a list of authorized data items.

[0068] Step S20: dynamically configuring a standardized authorization process instance based on the authorization data item list, wherein the standardized authorization process instance includes a plurality of authorization operation modules arranged in a preset order.

[0069] It should be noted that standardized authorization process instances are reusable individual authorization processes formed based on a combination of preset rules and modules. They are dynamically generated from a general authorization process template based on specific business needs. They contain all the steps and logic required to complete a specific authorization, ensuring the consistency and standardization of the authorization process in different scenarios. Authorization operation modules are standardized units with independent functions in the authorization process, such as identity verification modules, agreement signing modules, and data item selection modules. Each module corresponds to a specific step in the authorization process and can be maintained and reused independently. A complete authorization process is formed by combining different modules.

[0070] It should be understood that the pre-set order is the logical execution sequence of the authorization operation modules in the process, which is determined by business rules and compliance requirements. For example, the "Identity Verification" module must be completed before entering the "Agreement Signing" module to ensure that the process complies with laws and regulations and user experience logic.

[0071] In one example, when a financing product requires authorization of "corporate tax data" and "personal bank statements," the system parses the data items in the list and matches the "corporate tax information authorization module" and the "personal financial data authorization module." The modules are combined in a preset order of corporate authorization first and personal authorization later. The tax authority interface parameters are configured for the corporate tax information authorization module, and the bank data gateway parameters are configured for the personal bank statement module. Finally, a process instance containing the two modules is generated for the financing product to be embedded in the business process, with the tax authority interface parameters configured for the corporate tax information authorization module and the bank data gateway parameters configured for the personal bank statement module. The generated process instance containing the two modules is for the financing product to be embedded in the business process. The generated standardized authorization process instance is stored in the instance pool and can be called by the financing product system through the API interface, enabling one-time configuration and multiple reuse.

[0072] Step S30: embedding the standardized authorization process instance into the business process of the financing product through a pluggable module component.

[0073] It's important to note that the pluggable module component encapsulates the complete authorization process logic within the data authorization scenario. Business processes are the core operational procedures for financing products, such as loan applications, credit limit approvals, and contract signing. As a sub-step within the business process, the authorization process must be embedded at specific points to ensure data compliance.

[0074] It should be understood that before embedding a standardized authorization process instance into the business process of a financing product, it is necessary to pre-establish specifications for the interactive interface between the pluggable module component and the financing product system, and to determine the triggering nodes for the authorization link in the financing product business process. For example, in the loan application process, authorization for data collection is required before the user submits the materials, and in the credit limit approval process, the system automatically triggers a request for authorization to supplement data. When the pluggable module component is triggered to load, the configuration information of the standardized authorization process instance can be obtained from the server, and the authorization process page can be rendered in a specified location on the financing product interface (such as a pop-up window or embedded page) to achieve user interaction.

[0075] In one example, taking the enterprise supply chain finance product as an example, an authorization request is triggered at the node of submitting the financing application. The financing product system calls the pluggable module component through the API. The component pops up an authorization window on the product interface, displaying an authorization process instance containing the enterprise's industrial and commercial data, procurement contract data, and logistics data; after the user completes the authorization, the component returns the authorization result, and the business process enters the "risk assessment" stage. The system automatically obtains enterprise-related information based on the authorization data for risk control modeling.

[0076] Step S40: execute the business process and return the authorization result of the target data item required by the financing product.

[0077] It is understandable that after the pluggable module component loads the standardized authorization process instance, it guides the user to complete each authorization operation module in a preset order: the system records the user's operation trajectory in real time, including but not limited to: the selected authorization data items, the signed agreement version, the operation timestamp, the IP address, etc.; at the same time, the blockchain or hash algorithm is used to store key data (such as the agreement text, the authorization result) to ensure that it cannot be tampered with and meet the regulatory audit requirements. The data authorization is fully online and supports the resumption of user operations.

[0078] In one example, reference Figure 2 , Figure 2 This is the flow chart for the business data authorization interaction for this application. The user initiates a business application by opening the client through the APP / WeChat terminal, which triggers the APP / WeChat terminal to send the business application to the product system; after receiving the application, the product system initiates an authorization request to the unified authorization module and returns the authorization page address. The APP / WeChat terminal renders the authorization interaction page for the user terminal accordingly; after the user completes the authorization operation on the client side (i.e., APP / WeChat), the operation result is synchronized to the product system, and the product system confirms "authorization completed" and returns the authorization result after unified authorization processing; after obtaining the result, the product system continues to promote the business application operation for the user on the APP / WeChat terminal, realizing a complete closed loop from business initiation, authorization interaction to result feedback and business renewal. At the same time, the user can continue to initiate business application operations to the product system on the APP / WeChat terminal to ensure the orderly flow of data authorization links in the financing business.

[0079] In this embodiment, a method is disclosed for obtaining a list of authorized data items associated with a financing product in response to an authorization request triggered by the financing product; dynamically configuring a standardized authorization process instance based on the list of authorized data items, the standardized authorization process instance comprising multiple authorization operation modules arranged in a preset order; embedding the standardized authorization process instance into the business process of the financing product via a pluggable module component; executing the business process and returning the authorization result for the target data items required by the financing product. By obtaining a list of associated authorized data items in response to the authorization request of the financing product, the data authorization process is standardized and modularized, allowing users to maintain a consistent experience across different product processes, achieving a seamless connection between data authorization and business processes, and improving the consistency of overall operations.

[0080] Reference Figure 3 , Figure 3 This is a flow chart of the second embodiment of the application data authorization processing method. Based on the above-mentioned first embodiment, the second embodiment of the application data authorization processing method is proposed.

[0081] In the second embodiment, step S20 includes:

[0082] Step S201 : obtaining association relationship configuration according to a preset business domain, wherein the preset business domain includes an authorized product domain, an authorized data item domain, an authorized protocol domain, and an authorized object domain.

[0083] It should be noted that preset business areas are pre-defined logical groupings with clear business boundaries and functions, used to categorize and manage the core elements of the authorization process. In data authorization scenarios, these typically include: 1. The authorization product area, which is responsible for access management of each financing product and the authorization system, and the scope of authorization data effectiveness; 2. The authorization data item area, which primarily handles the authorization process for each data item and the authorization effectiveness process corresponding to the data management system; 3. The authorization agreement area, which is responsible for managing the differences between the standard agreement and the branch's personalized agreement for each data item, as well as retaining the signed authorization agreement text; 4. The authorization object area, which is responsible for differentiated data verification and customer notification between different authorization objects.

[0084] It should be understood that the association configuration describes the logical relationships between business areas and is used to guide the dynamic generation of the authorization process. For example, it specifies which data items need to be associated with a financing product, which authorization agreement should be signed for specific data items, and the identity verification process applicable to different authorization recipients (enterprises / individuals).

[0085] In one example, reference Figure 4 , Figure 4This is a hierarchical diagram of the embedded development model for this application authorization process. From top to bottom, it is divided into the channel layer, business layer, and data layer.

[0086] As the entry point for the authorization system to interact with customers, the channel layer should choose to process as little business logic as possible to reduce processing pressure. At the same time, it can bring together various business access points such as "Enterprise Online Banking Ubank", "Enterprise Online Banking APP", "Enterprise Annotation Mini Program", "Bank APP", etc. as the front-end channel for users to initiate business actions.

[0087] The business layer involves four areas: authorized products, authorized data items, authorization agreements, and authorized objects. Through configuration, these areas are sequentially combined to form an authorization process instance. Authorized products include various types of financing products awaiting authorization, such as Product A and Product B. Authorized data items include multi-dimensional data categories such as credit data, tax data, electricity usage data, invoice data, corporate financing credit data, and cash flow credit information. Authorization agreements include standard agreements and regionally customized agreement texts. Authorized objects distinguish between borrowing enterprises, affiliated enterprises, and other entities. Each business domain collaboratively supports the authorization business logic.

[0088] The data layer is based on databases and message queues, providing data storage and circulation capabilities for upper-level business operations. At the same time, it uses message middleware to decouple face-to-face business processing and process processing, thereby improving the high concurrency capability of face-to-face business processing.

[0089] Step S202 , based on memory cache and background thread scanning, monitor the change event of the financing product in the association relationship configuration in real time to obtain the change result.

[0090] It should be noted that the memory cache is used to store the relationship configuration between financing products and authorization data items, supporting fast query and real-time update. The background thread scans the changes in the relationship configuration according to the preset cycle. This thread does not affect the execution of the main business process and completes data monitoring and updates in an asynchronous manner. The change event is a notification mechanism triggered by the system when the relationship configuration of the financing product changes (such as adding new data items, modifying the authorization agreement). The change result is the result data generated by the system after processing the change event, which contains the difference information before and after the configuration change (such as which data items have been added, which protocol versions have been modified), and is used for dynamic adjustment of subsequent processes.

[0091] In one example, reference Figure 5 , Figure 5This is a relationship diagram for authorization management of this application. The authorization application is the starting point of the process. The user / system initiates the authorization demand (such as financing products triggering data authorization) and specifies the permissions that need to be obtained. The application is then preliminarily verified to check the basic conditions (such as user identity validity and application data integrity) and screen out situations that clearly do not meet the authorization requirements. An authorization application can be for multiple authorization objects, and each authorization object can have multiple authorization agreements, and each authorization agreement corresponds to an authorization data item.

[0092] It is understandable that the authorization system designs the authorization process as a page module component. When financing products need data authorization, this component is embedded in the product application process to complete the corresponding data authorization. At the same time, the authorization system abstracts authorization management into the relationship between authorization application, authorization object, authorization agreement, and authorization data item. When a product has a new type of data authorization requirement, it uses memory caching and background thread scanning for changes to monitor the product-authorization data item relationship configuration in real time, obtain a list of data items that the product currently needs to authorize, dynamically load the authorization agreement module based on the list, sign one or more authorization agreements, and ultimately complete the authorization of the required data items.

[0093] Step S203: generating an updated target association relationship configuration according to the change result and the authorized data item list, and determining the authorization protocol module corresponding to the authorized data item list based on the target association relationship configuration.

[0094] It should be noted that the target relationship configuration is a new configuration that adapts to current business needs after adjusting the original relationship configuration based on the change results.

[0095] It is understandable that the original configuration should be adjusted according to the change results, the new data items should be associated with products and object fields, the protocol template mapping rules should be updated, the requirements of the authorized data item list should be integrated into the configuration, and the target association relationship configuration should be generated to ensure that the configuration fits the current business.

[0096] Step S204: Combine the authorization protocol module and the preset authorization operation module in sequence to form the standardized authorization process instance.

[0097] It should be noted that the preset authorization operation modules are pre-defined standardized components that implement a single authorization operation function, such as the identity verification module, the data item checking module, and the result feedback module. Each module focuses on solving the interaction and logic of a link in the authorization process.

[0098] It should be understood that the execution order of modules should be determined based on business logic and the rationality of user operations. Following the conventional logic of first verifying identity, then presenting the agreement, then confirming data authorization, and finally feeding back the results, the authorization protocol module should be embedded in the appropriate location and the modules should be connected in series. Through a process engine or configuration tool, the sequenced modules can be combined into a coherent process. Data transmission rules and exception handling logic between modules can be configured to form an independently run, standardized authorization process instance for the business system to call and execute authorization tasks. This allows for the efficient construction of an authorization process that adapts to the business, improving development reusability and process standardization.

[0099] In this embodiment, by obtaining the relationship configuration through preset business fields, such as authorized products, data items, protocols, object fields, etc., it is possible to quickly respond to changes in the authorization requirements of financing products, ensure the dynamic update and accuracy of the authorization process instances, solve the problem of lack of flexibility and standardization of protocol management in the existing technology, and improve the configuration efficiency of the authorization process.

[0100] Reference Figure 6 , Figure 6 This is a flow chart of the third embodiment of the application data authorization processing method. Based on the above second embodiment, the third embodiment of the application data authorization processing method is proposed.

[0101] In the second embodiment, step S203 includes:

[0102] Step S2031: Parse the protocol type identifier in the authorization data item list, extract the configuration update item of the change result, and obtain the association relationship element.

[0103] It should be noted that the protocol type identifier is an identification code used to distinguish different authorization protocol types in the authorization data item list; the configuration update item is a specific configuration change unit disassembled from the change result, and is the basic content that constitutes the association relationship adjustment, such as the authorization process control identifier change of a single data item and the update record of a certain protocol template version; the association relationship element is a set of key information that describes the association logic of various fields (products, data items, protocols, objects) in the authorization process, covering product access parameters, data item process control rules, protocol template mapping relationships, authorization object verification rules, etc., and is the core content of building / adjusting the association relationship configuration.

[0104] Step S2032: Match and reconstruct the protocol type identifier and the association relationship element to generate a target association relationship configuration.

[0105] Furthermore, in order to generate a target association relationship configuration including a protocol type identifier, a structured data foundation is provided for accurate matching of the authorization protocol module, thereby improving the standardization and scalability of the process configuration. The association relationship elements include the access configuration parameters in the authorization product field, the process control identifier in the authorization data item field, the template version mapping in the authorization protocol field, and the validation rule set in the authorization object field; the step S2032 may include:

[0106] Refresh the product access endpoint corresponding to the protocol type identifier according to the access configuration parameters; reorganize the data item authorization path corresponding to the protocol type identifier based on the process control identifier; update the protocol template library index corresponding to the protocol type identifier through the template version mapping; update the differentiated data verification set according to the verification rule set; generate a target association relationship configuration containing the protocol type identifier based on the product access endpoint, the data item authorization path, the protocol template library index and the differentiated data verification set.

[0107] It is understandable that the access configuration parameters define how the financing product connects to the data provider's system. The product access endpoint is the specific interface address exposed by the data provider's system for data exchange. The process control identifier indicates the mark of the processing rules for each data item in the authorization process. The data item authorization path is the sequence of processing steps that each data item must go through in the authorization process. The template version mapping contains the correspondence between the protocol type and the specific protocol template version. The protocol template library index is the unique identifier of the protocol template in the repository. The validation rule set is a set of validation logic formulated for different authorization objects and data item types. The differentiated data validation set is a set of validation conditions for specific data items that are dynamically generated according to the validation rules.

[0108] In one example, the system extracts the access configuration parameters corresponding to the protocol type (such as the new API address and encryption key) from the change results, updates the product access endpoint information, and verifies the connectivity and permissions of the new endpoint to ensure that the product can access the data normally. When the authorization path is reorganized, the process control identifier is parsed, and the position and processing method of the data item in the authorization path are adjusted. For example, the enterprise social security data is adjusted from an optional authorization item to a mandatory authorization item, and a new screening step is added as a pre-verification for credit authorization. The latest protocol version is then determined through template version mapping, and the protocol template library index is updated to point to the latest protocol text storage location. Exclusive verification conditions are generated for each data item according to the verification rule set to ensure the generation of differentiated verification sets. Finally, the updated access endpoint, authorization path, protocol index, and verification set are integrated and associated with the protocol type identifier to form a complete configuration object.

[0109] Step S2033: Determine the authorization protocol module corresponding to the authorization data item list according to the target association relationship configuration.

[0110] Furthermore, in order to match the authorization protocol module from the preset protocol module library based on the effective scope and process, the rapid calling and reuse of the protocol module is achieved, which reduces the duplication of development work and improves the efficiency and consistency of authorization protocol management. The step S2033 may include:

[0111] Parse the effective scope of the authorization data in the target association relationship configuration and obtain the authorization effective process of the target association relationship configuration; match the authorization protocol module from the preset protocol module library based on the effective scope and the authorization effective process.

[0112] It should be noted that the effective scope refers to the effective usage boundary of the authorized data item, including the time range, space range, data range and usage scenarios, etc. This range is determined by business rules and compliance requirements, and is used to limit the use of data beyond the scope. The authorization effectiveness process defines the complete execution logic of the authorization from application to formal effectiveness, including the approval nodes after the agreement is signed, data encryption rules, and the docking process with the data provider. For example, the corporate credit authorization is required to be electronically signed by the legal person, automatically verified by the system, and confirmed by the credit center before it is considered effective. The preset protocol module library is a collection of standardized protocol function modules that are pre-developed and stored. Each module corresponds to a type of authorization scenario (such as credit authorization, tax authorization), and contains complete logic such as agreement text generation, signing interaction, and effectiveness notification, and supports quick calling through configuration.

[0113] It should be understood that by parsing the authorization data effectiveness scope and authorization effectiveness process in the target association relationship configuration, matching authorization protocol modules can be screened from the preset protocol module library: first, extract the key parameters of the effectiveness scope and the node requirements of the effectiveness process, and then search the protocol module library according to the preset matching rules to find modules that are compatible with the effectiveness conditions, and inject the effectiveness parameters into the module to generate an adapted authorization protocol process, ensuring that the authorization scope is compliant and the process steps are complete, so as to realize dynamic and accurate calling of the protocol module.

[0114] In this embodiment, by matching and reconstructing the protocol type identifier and the association relationship element to generate the target association relationship configuration, the integration and dynamic adaptation of multi-dimensional business rules in the authorization process are achieved; the consistency of the authorization protocol module with the actual business needs is ensured, and the process interruption or error caused by mismatch of configuration information is avoided, thereby improving the reliability and flexibility of the authorization process.

[0115] Reference Figure 7 , Figure 7 This is a flow chart of the fourth embodiment of the application data authorization processing method. Based on the above embodiments, the fourth embodiment of the application data authorization processing method is proposed.

[0116] In the fourth embodiment, before step S40, the following steps are included:

[0117] Step S401: Divide the business process into a plurality of standardized steps to be executed in sequence according to the authorization operation module.

[0118] It is understandable that the business process of financing products is divided into standardized steps that are connected in sequence according to authorization operation modules such as "identity verification module", "data item checking module", "agreement signing module", etc. For example, user identity verification is first completed through the identity verification module, and then the data item checking module guides the user to select the authorization scope, and finally the electronic signing is completed through the agreement signing module. Each step is executed in a preset order to form a structured authorization path, which is not only convenient for users to understand the operation, but also can improve the efficiency of process construction through module reuse, ensuring the standardization and traceability of the authorization process in different business scenarios.

[0119] Step S402: When it is detected that the user performs an authorization operation, the user operation data is stored in a structured storage unit according to the standardized steps.

[0120] Furthermore, in order to provide an orderly storage structure for user operation data, the field element data is bound to the corresponding node to ensure the relevance and traceability of the data and steps. The step S402 may include:

[0121] Construct a linked list node containing a step identifier, a step sequence number, and an operation timestamp; bind the field element data entered by the user in each step to the corresponding linked list node; persistently store the linked list node data in a structured storage unit through an asynchronous save mechanism, and update the step status identifier of the current linked list node each time the step is switched.

[0122] In one example, the authorization system designed the user authorization process into six steps: selecting and confirming the authorization scope, identity verification, filling in the authorization fields, previewing and reading the authorization agreement, signing the agreement, and completing the authorization. The system unifies the data for these six steps, storing them in a linked list format. Fields such as the current step, operation time, and step number are designed, and a timer is used to save user operation data every 15 seconds. When a user exits and re-enters the authorization process, the system automatically searches for the most recently saved data draft based on the user's information, automatically jumps to the step where the draft was stored, and refills the stored information, allowing the user to continue from the point of interruption.

[0123] Step S403: When a process interruption is detected, the step identifier of the current interruption point is recorded.

[0124] It should be understood that during the execution of the authorization process, the system continuously monitors the user's operational status and the system operating environment. When a process interruption event is detected (such as a user closing a page or an interface timeout), the system immediately captures the identifier of the currently executing step and associates it with the user's unique identifier, the interruption timestamp, and other information, storing it in the interruption record database. This operation ensures that the breakpoint location can be accurately identified when the process resumes, avoiding repeated operations for the user, improving the user experience, and protecting data integrity.

[0125] Step S404 : When the user re-enters the process, the process is restored to the step corresponding to the interruption point based on the step identifier and the user operation data.

[0126] It is understandable that when a user re-enters the authorization process, the system first searches the interruption record database using the user's unique identifier to obtain the identifier of the most recently interrupted step and associated operation data, such as selected data items such as "bank statements" and "credit reports." The system then parses the sequential position of the interruption point in the process based on the step identifier, loads all linked list node data before that step from the structured storage unit, and automatically backfills the user's completed operation information, such as automatically checking confirmed data items, displaying completed identity information, and jumping the page to the interrupted step, such as the authorization scope confirmation interface. Users can continue the operation directly from the breakpoint without having to start from the beginning, reducing repetitive work.

[0127] In this embodiment, when a process interruption is detected, the interruption point step identifier is recorded, which solves the problem of having to start from the beginning after the process is interrupted in the prior art; when the user re-enters the process, the process is restored to the interruption point based on the identifier and data, which reduces repeated operations and improves the user experience. It is especially suitable for complex authorization scenarios with many operation steps.

[0128] It should be noted that the above examples are only used to understand this application and do not constitute a limitation on the data authorization processing method of this application. More simple transformations based on this technical concept are all within the scope of protection of this application.

[0129] This application also provides a data authorization processing device, please refer to Figure 8 , the data authorization processing device includes:

[0130] A data acquisition module 10 is configured to acquire a list of authorized data items associated with a financing product in response to an authorization request triggered by the financing product;

[0131] A process configuration module 20, configured to dynamically configure a standardized authorization process instance based on the authorization data item list, wherein the standardized authorization process instance includes a plurality of authorization operation modules arranged in a preset order;

[0132] A process embedding module 30, configured to embed the standardized authorization process instance into the business process of the financing product through a pluggable module component;

[0133] The business execution module 40 is used to execute the business process and return the authorization result of the target data item required by the financing product.

[0134] The data authorization processing device provided in this application, which utilizes the data authorization processing method described in the aforementioned embodiments, can address the technical issues of developing separate data authorization processes for different financing products, resulting in low development efficiency and significant differences in user experience across different products. Compared to the prior art, the data authorization processing device provided in this application offers the same beneficial effects as the data authorization processing method described in the aforementioned embodiments. Other technical features of the data authorization processing device are the same as those disclosed in the aforementioned embodiments and are not further elaborated upon here.

[0135] The present application provides a data authorization processing device, which includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the data authorization processing method in the above-mentioned embodiment one.

[0136] Reference below Figure 9 , which shows a schematic diagram of the structure of a data authorization processing device suitable for implementing an embodiment of the present application. The data authorization processing device in the embodiment of the present application may include, but is not limited to, mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Portable Application Descriptions), PMPs (Portable Media Players), in-vehicle terminals (such as in-vehicle navigation terminals), and fixed terminals such as digital TVs and desktop computers. Figure 9 The data authorization processing device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0137] like Figure 9As shown, the data authorization processing device may include a processing device 1001 (e.g., a central processing unit, a graphics processing unit, etc.), which can perform various appropriate actions and processes based on programs stored in a read-only memory 1002 or programs loaded from a storage device 1003 into a random access memory 1004. The random access memory 1004 also stores various programs and data required for the operation of the data authorization processing device. The processing device 1001, the read-only memory 1002, and the random access memory 1004 are interconnected via a bus 1005. An input / output interface 1006 is also connected to the bus. Typically, the following systems can be connected to the input / output interface 1006: an input device 1007 including, for example, a touch screen, touchpad, keyboard, mouse, image sensor, microphone, accelerometer, gyroscope, etc.; an output device 1008 including, for example, a liquid crystal display (LCD), speaker, vibrator, etc.; a storage device 1003 including, for example, a magnetic tape, hard disk, etc.; and a communication device 1009. The communication device 1009 can allow the data authorization processing device to communicate with other devices wirelessly or by wire to exchange data. Although the figure shows a data authorization processing device with various systems, it should be understood that it is not required to implement or have all of the systems shown. More or fewer systems may be implemented or have alternatively.

[0138] In particular, according to the embodiments disclosed in the present application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, the embodiments disclosed in the present application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program comprising program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network via a communication device, or installed from a storage device 1003, or installed from a read-only memory 1002. When the computer program is executed by the processing device 1001, the above-mentioned functions defined in the method of the embodiment disclosed in the present application are performed.

[0139] The data authorization processing device provided in this application, utilizing the data authorization processing method described in the aforementioned embodiment, can address the technical issues of developing separate data authorization processes for different financing products, resulting in low development efficiency and significant differences in user experience across different products. Compared to the prior art, the beneficial effects of the data authorization processing device provided in this application are the same as those of the data authorization processing method described in the aforementioned embodiment. Other technical features of this data authorization processing device are the same as those disclosed in the aforementioned embodiment and are not further elaborated here.

[0140] It should be understood that the various parts disclosed in this application can be implemented using hardware, software, firmware, or a combination thereof. In the description of the above embodiments, specific features, structures, materials, or characteristics can be combined in any one or more embodiments or examples in a suitable manner.

[0141] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

[0142] The present application provides a computer-readable storage medium having computer-readable program instructions (ie, computer program) stored thereon, wherein the computer-readable program instructions are used to execute the data authorization processing method in the above embodiment.

[0143] The computer-readable storage medium provided in this application may be, for example, a USB flash drive, but is not limited to electrical, magnetic, optical, electromagnetic, infrared or semiconductor systems, systems or devices, or any combination thereof. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In this embodiment, the computer-readable storage medium may be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, system or device. The program code contained on the computer-readable storage medium may be transmitted using any appropriate medium, including but not limited to: wires, optical cables, RF (Radio Frequency), etc., or any suitable combination thereof.

[0144] The computer-readable storage medium may be included in the data authorization processing device; or it may exist independently without being assembled into the data authorization processing device.

[0145] The computer-readable storage medium carries one or more programs. When the one or more programs are executed by the data authorization processing device, the data authorization processing device executes the data authorization processing method described above.

[0146] Computer program code for performing the operations of the present application may be written in one or more programming languages, or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a stand-alone software package, partially on the user's computer and partially on a remote computer, or entirely on the remote computer or server. In cases involving a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., through the Internet using an Internet service provider).

[0147] The flowcharts and block diagrams in the accompanying drawings illustrate the possible implementation architecture, functions and operations of the systems, methods and computer program products according to various embodiments of the present application. In this regard, each box in the flowchart or block diagram can represent a module, program segment or part of code, and the module, program segment or part of code contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in an order different from that marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and / or flowchart, as well as the combination of boxes in the block diagram and / or flowchart, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or can be implemented using a combination of dedicated hardware and computer instructions.

[0148] The modules described in the embodiments of the present application may be implemented in software or hardware, wherein the name of a module does not necessarily limit the unit itself.

[0149] The computer-readable storage medium provided in this application is a computer-readable storage medium that stores computer-readable program instructions (i.e., a computer program) for executing the aforementioned data authorization processing method. This computer-readable storage medium can address the technical issues of low development efficiency of data authorization processes developed for different financing products and significant differences in user experience across different products. Compared to the prior art, the beneficial effects of the computer-readable storage medium provided in this application are the same as those of the data authorization processing method provided in the aforementioned embodiments, and are not further elaborated here.

[0150] The above description is only part of the embodiments of the present application and does not limit the patent scope of the present application. All equivalent structural transformations made by using the contents of the present application specification and drawings under the technical concept of the present application, or direct / indirect application in other related technical fields are included in the patent protection scope of the present application.

Claims

1. A data authorization processing method, characterized in that: The data authorization processing method includes: In response to an authorization request triggered by a financing product, obtaining a list of authorization data items associated with the financing product; Dynamically configuring a standardized authorization process instance based on the authorization data item list, wherein the standardized authorization process instance includes a plurality of authorization operation modules arranged in a preset order; Embedding the standardized authorization process instance into the business process of the financing product through pluggable module components; Execute the business process and return the authorization result of the target data item required by the financing product.

2. The data authorization processing method according to claim 1, characterized in that: The step of dynamically configuring a standardized authorization process instance based on the authorization data item list includes: Acquire association relationship configuration according to preset business fields, wherein the preset business fields include authorized product fields, authorized data item fields, authorized agreement fields, and authorized object fields; Based on memory cache and background thread scanning, monitor the change events of the financing product in the association relationship configuration in real time to obtain the change results; generating an updated target association relationship configuration according to the change result and the authorization data item list, and determining an authorization protocol module corresponding to the authorization data item list based on the target association relationship configuration; The authorization protocol module and the preset authorization operation module are combined in sequence to form the standardized authorization process instance.

3. The data authorization processing method according to claim 2, characterized in that: The step of generating an updated target association relationship configuration according to the change result and the authorization data item list, and determining the authorization protocol module corresponding to the authorization data item list based on the target association relationship configuration includes: Parsing the protocol type identifier in the authorization data item list, and extracting the configuration update item of the change result to obtain the association relationship element; Matching and reconstructing the protocol type identifier and the association relationship element to generate a target association relationship configuration; The authorization protocol module corresponding to the authorization data item list is determined according to the target association relationship configuration.

4. The data authorization processing method according to claim 3, wherein: The association relationship elements include access configuration parameters in the authorization product field, process control identifiers in the authorization data item field, template version mapping in the authorization protocol field, and validation rule sets in the authorization object field; The step of matching and reconstructing the protocol type identifier and the association relationship element to generate a target association relationship configuration includes: Refresh the product access endpoint corresponding to the protocol type identifier according to the access configuration parameters; reorganizing the data item authorization path corresponding to the protocol type identifier based on the process control identifier; Updating the protocol template library index corresponding to the protocol type identifier through the template version mapping; Updating the differential data check set according to the verification rule set; A target association relationship configuration including the protocol type identifier is generated according to the product access endpoint, the data item authorization path, the protocol template library index and the differential data verification set.

5. The data authorization processing method according to claim 3, wherein: The step of determining the authorization protocol module corresponding to the authorization data item list according to the target association relationship configuration includes: Parsing the effective scope of the authorization data in the target association relationship configuration and obtaining the authorization effectiveness process of the target association relationship configuration; Based on the effective scope and the authorization effective process, an authorization protocol module is matched from a preset protocol module library.

6. The data authorization processing method according to claim 1, wherein: Before the step of executing the business process and returning the authorization result of the target data item required for the financing product, the method further includes: Divide the business process into multiple standardized steps to be executed in sequence according to the authorized operation module; When detecting that a user performs an authorized operation, storing the user operation data in a structured storage unit according to the standardized steps; When a process interruption is detected, the step identifier of the current interruption point is recorded; When the user re-enters the process, the process is restored to the step corresponding to the interruption point based on the step identifier and the user operation data.

7. The data authorization processing method according to claim 6, characterized in that: The step of storing the user operation data in the structured storage unit according to the standardized steps when detecting that the user performs the authorization operation includes: Construct a linked list node containing step identifier, step sequence number and operation timestamp; Binding the field element data input by the user in each step to the corresponding linked list node; The linked list node data is persistently stored in the structured storage unit through the asynchronous saving mechanism, and the step status identifier of the current linked list node is updated each time the step is switched.

8. A data authorization processing device, characterized in that: The device comprises: a data acquisition module, configured to acquire a list of authorized data items associated with a financing product in response to an authorization request triggered by the financing product; A process configuration module, configured to dynamically configure a standardized authorization process instance based on the authorization data item list, wherein the standardized authorization process instance includes a plurality of authorization operation modules arranged in a preset order; A process embedding module, used to embed the standardized authorization process instance into the business process of the financing product through a pluggable module component; The business execution module is used to execute the business process and return the authorization result of the target data item required by the financing product.

9. A data authorization processing device, characterized in that: The device includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program is configured to implement the steps of the data authorization processing method according to any one of claims 1 to 7.

10. A storage medium, characterized in that: The storage medium is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by a processor, the steps of the data authorization processing method according to any one of claims 1 to 7 are implemented.

Images