A method for generating a public credit information report

Abstract

This invention discloses a method for generating public credit information reports, aiming to solve the problems of existing credit report query and generation systems, such as limited query dimensions, lack of security mechanisms for sensitive information queries, and inconvenience in report sharing and reuse. The method is executed by a server, including receiving report generation requests from user terminals and identifying query type identifiers; if it is a "domain-date query," the method obtains and verifies the target query domain and date range, determines whether it contains sensitive domains, requires biometric verification before querying and caching results, and directly queries non-sensitive domains. Credit information is obtained in parallel and integrated to generate a special report with a unique identifier, which is then notified to the user for download; if it is an "authorization code query," the method verifies the validity of the authorization code, and if valid, retrieves the associated already generated report. This invention supports flexible and accurate queries, ensures the security of sensitive information, achieves efficient report reuse through authorization codes, and reduces user burden and system load.

Description

Technical Field

[0001] This invention relates to the field of public credit information processing technology, specifically a method for generating public credit information reports. Background Technology

[0002] For a long time, small and medium-sized enterprises (SMEs) have frequently needed to apply for "certificates of no illegal or irregular records" from multiple administrative departments in their business activities such as financing and bidding. The process is cumbersome, time-consuming, and labor-intensive, which is one of the important reasons for the problems of "difficult and expensive financing." To solve this problem, the "credit certificate substitution" system has emerged, aiming to replace multiple traditional certificates with an integrated credit report.

[0003] However, existing credit report query and generation systems face the following technical challenges:

[0004] 1) The query dimensions are too limited to support users in making flexible and accurate filters based on administrative management areas and specific time ranges, resulting in redundant or missing report content;

[0005] 2) For credit information inquiries involving sensitive areas such as law enforcement agencies and the judiciary, there is a lack of security verification and process coordination mechanisms linked to department-specific security requirements (such as facial recognition and delayed result return);

[0006] 3) Sharing and reusing the report results is inconvenient, requiring repeated operations for each query, which increases the burden on users and the system load.

[0007] Therefore, there is an urgent need for a public credit information report generation method that can achieve refined querying, security and compliance, and support efficient reuse of results, in order to overcome the shortcomings of existing technologies. Summary of the Invention

[0008] The purpose of this invention is to overcome the shortcomings of the prior art and provide a method for generating public credit information reports. This method supports flexible queries by domain and time, integrates a special security processing procedure for sensitive information, and realizes secure sharing and reuse of reports through an authorization code mechanism, thereby solving the problems of single query dimensions, insufficient security protection for sensitive information queries, and inconvenience in report reuse in existing systems.

[0009] To achieve the above objectives, the present invention employs the following technical means:

[0010] A method for generating public credit information reports, executed by a server, includes the following steps:

[0011] Receive a report generation request initiated by a user terminal, wherein the request contains a query type identifier;

[0012] When the query type identifier indicates "domain-date query", the following steps are performed:

[0013] S11: Obtain at least one target query field and a specified target date range selected by the user from the request; wherein the target query field is selected from a predefined set of administrative management fields, the span of the target date range does not exceed a preset maximum number of years, and the end date is not later than a preset number of days before the report generation date;

[0014] S12: Determine whether the target query domain contains a preset sensitive domain;

[0015] If so, the biometric verification process for the user is triggered and completed. After the verification is successful, a query request is initiated to the corresponding sensitive data source. The query result returned by the data source after a preset processing period is received. If a repeated query request for the same user and the same sensitive area is received within the preset cache validity period, the cached result from the first query is returned directly.

[0016] If not, then a query request will be directly sent to the corresponding public credit information database;

[0017] S13: Based on the target query domain and the target date range, perform parallel queries and obtain the user's credit information in all selected domains;

[0018] S14: Integrate the acquired credit information by field and time, fill it into the preset report template, generate a special credit information report file, and assign a unique identifier to the report;

[0019] S15: After generating the report, send a notification to the user and provide a report download service;

[0020] When the query type identifier indicates "authorization code query", the following steps are performed:

[0021] S21: Obtain the authorization code entered by the user from the request;

[0022] S22: Verify the validity of the authorization code;

[0023] S23: If the authorization code is valid, retrieve the generated special credit information report file based on the unique report identifier associated with the authorization code and provide it to the user.

[0024] Preferably, in step S11, the target date range spans no more than 3 years, and the end date is no later than the 30th calendar day before the report generation date.

[0025] Preferably, in step S12, the sensitive area is the field of law enforcement agencies, the biometric verification process is face recognition, the preset processing cycle is 3 working days, and the cache validity period is 3 months.

[0026] Preferably, in step S13, the credit information includes administrative penalty information, administrative enforcement information, information on the list of seriously dishonest entities, and criminal judgment information.

[0027] Preferably, after generating the report, the method further includes: generating an authorization code that is uniquely linked to the report, the authorization code having an expiration period, which is used by other users to obtain the report through an "authorization code query".

[0028] Preferably, after generating the report, the method further includes sending a text message to the user containing a report generation notification.

[0029] Preferably, the server executing the method includes:

[0030] The request parsing module is used to receive and parse report generation requests and output query type identifiers;

[0031] The query control module, connected to the request parsing module, is used to route the request to the domain-date query process or the authorization code query process in response to the received query type identifier.

[0032] The parameter processing and verification module, connected to the query control module, is used to obtain and verify the target query domain and date range selected by the user when the query is routed to the domain-date query process.

[0033] The security collaboration processing module, connected to the parameter processing and verification module, is used to respond to the judgment that the target query domain contains a sensitive domain, manage the biometric verification process, and control the query and result caching and reuse of sensitive domain data sources.

[0034] The parallel query engine for credit information is connected to the parameter processing and verification module and the security collaborative processing module. It is used to initiate query requests to the data sources corresponding to each target query domain in parallel according to the verified query parameters, and to receive the returned credit information.

[0035] The report synthesis module, connected to the parallel query engine for credit information, is used to integrate the received credit information and generate a standardized special credit information report.

[0036] The report storage and authorization management module is connected to the query control module and the report synthesis module, respectively, and is used to store the generated reports, verify and retrieve the corresponding reports in response to the authorization code query process, and manage the authorization codes of the reports;

[0037] The notification and delivery module, connected to the report storage and authorization management module, is used to send report generation notifications and deliver report files to users.

[0038] Preferably, the method is implemented by a computer program, which, when executed by a processor, specifically implements the steps of receiving requests, determining query types, obtaining parameters, processing queries in sensitive areas, querying credit information, generating reports, and processing authorization code queries.

[0039] The present invention has the following beneficial effects:

[0040] 1. Supports refined queries: This invention allows users to flexibly filter credit information by administrative management field and specific time range through the "field-date query" process. This solves the problem of the single query dimension of the existing system, effectively avoids redundancy or missing report content, improves the relevance and practicality of the report, and can better meet users' personalized credit proof needs in different business activities.

[0041] 2. Ensuring the security and compliance of sensitive information queries: For credit information queries in sensitive fields, this invention integrates a biometric verification process and links it with the processing cycle and caching requirements of data sources in sensitive fields. This establishes a comprehensive security verification and process collaboration mechanism to ensure that sensitive information queries comply with the security standards of the relevant departments, thereby improving the security and compliance of information queries.

[0042] 3. Achieve efficient report reuse: This invention uses an authorization code mechanism to allow users to generate authorization codes with expiration dates for others to query generated reports, avoiding repeated query operations. This reduces users' time and effort costs, decreases the system's query load, and improves system operating efficiency.

[0043] 4. Improve query and report generation efficiency: The parallel query engine initiates query requests to various data sources, significantly shortening the time for obtaining credit information; at the same time, the standardized report generation process and templates ensure rapid report synthesis, improving overall report generation efficiency and enhancing user experience. Attached Figure Description

[0044] Figure 1 This is a flowchart of the generation method of the present invention;

[0045] Figure 2 This is a schematic diagram of the module connections of the server of the present invention. Detailed Implementation

[0046] The technical solution of the present invention will now be clearly and completely described with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0047] like Figure 1As shown, this invention provides a method for generating public credit information reports. This method is executed by a server, and the specific technical solution is as follows:

[0048] The method includes the following core steps: receiving a report generation request initiated by a user terminal, the request containing a query type identifier; and executing either a "domain-date query" process or an "authorization code query" process depending on the different query type identifiers.

[0049] 1. When the query type identifier indicates "Domain-Date Query", perform the following steps:

[0050] S11: Obtain at least one target query field and a specified target date range selected by the user from the request; wherein the target query field is selected from a predefined set of administrative management fields, the span of the target date range does not exceed a preset maximum year, and the end date is not later than a preset number of days before the report generation date.

[0051] As a further optimization, the target date range spans no more than 3 years, and the cutoff date is no later than the 30th calendar day before the report generation date. This setting ensures both the timeliness and relevance of the query information, and also meets the regular time requirements of administrative departments for credit information queries.

[0052] S12: Determine whether the target query domain contains a preset sensitive domain;

[0053] If so, the biometric verification process for the user is triggered and completed. After the verification is successful, a query request is initiated to the corresponding sensitive data source. The query result returned by the data source after a preset processing period is received. If a repeated query request for the same user and the same sensitive area is received within the preset cache validity period, the cached result from the first query is returned directly.

[0054] If not, a query request will be directly initiated to the corresponding public credit information database.

[0055] Specifically, the sensitive area is preferably the law enforcement field, and the corresponding biometric verification process is facial recognition. This verification method is convenient and highly secure, meeting the strict security requirements of law enforcement agencies for information retrieval. The preset processing cycle is set to 3 working days, which is suitable for the normal processing time limit of credit information retrieval in the law enforcement field. The cache validity period is set to 3 months, which can avoid the waste of system resources caused by repeated queries in a short period of time, and ensure the timeliness of sensitive information.

[0056] S13: Based on the target query domain and the target date range, perform parallel queries and obtain the user's credit information across all selected domains. This credit information includes administrative penalty information, administrative enforcement information, information on seriously dishonest entities, and criminal judgment information, covering core credit evaluation information in the administrative and judicial fields, and meeting the user's credit verification needs in scenarios such as financing and bidding.

[0057] S14: Integrate the acquired credit information by field and time, fill it into the preset report template, generate a special credit information report file, and assign a unique identifier to the report. The setting of the unique identifier provides the basis for the storage, retrieval, and authorized sharing of subsequent reports.

[0058] S15: After the report is generated, a notification is sent to the user, and the report download service is provided. Preferably, an SMS message containing a report generation notification is sent to the user to ensure that the user is aware of the report generation status in a timely manner and can complete the download.

[0059] Furthermore, after generating the report, the method also includes: generating an authorization code bound to the unique identifier of the report. This authorization code has an expiration date and can be used by other users to obtain the report through an "authorization code query". The expiration date of the authorization code can be flexibly set according to the actual application scenario, which ensures both the security of report sharing and efficient reuse.

[0060] 2. When the query type identifier indicates "authorization code query", perform the following steps:

[0061] S21: Obtain the authorization code entered by the user from the request;

[0062] S22: Verify the validity of the authorization code, including whether the authorization code exists and whether it is within the validity period;

[0063] S23: If the authorization code is valid, retrieve the generated special credit information report file based on the unique report identifier associated with the authorization code and provide it to the user; if the authorization code is invalid, return an invalid authorization code prompt to the user and guide the user to re-enter it or regenerate the report through the "domain-date query" process.

[0064] like Figure 2 As shown, to implement the above method, the server executing the method includes the following functional modules:

[0065] The request parsing module receives and parses report generation requests, and outputs a query type identifier. This module is the entry point of the entire system and is responsible for accurately identifying the user's query request type.

[0066] The query control module, connected to the request parsing module, is used to route the request to the domain-date query process or the authorization code query process in response to the received query type identifier; it plays a core role in request distribution and process control, ensuring that different types of query requests can accurately enter the corresponding processing flow.

[0067] The parameter processing and verification module, connected to the query control module, is used to obtain and verify the target query domain and date range selected by the user when the query is routed to the domain-date query process. The verification includes whether the target query domain belongs to a predefined set and whether the date range conforms to preset rules, so as to ensure the legality and validity of the query parameters.

[0068] The security collaboration processing module, connected to the parameter processing and verification module, is used to respond to the judgment that the target query domain contains sensitive domains, manage the biometric verification process, and control the query and result caching and reuse of sensitive domain data sources. This module is the key to ensuring the security and compliance of sensitive information queries and realizes linkage and collaboration with the security requirements of sensitive domain departments.

[0069] The parallel query engine for credit information, connected to the parameter processing and verification module and the security collaborative processing module, is used to initiate query requests in parallel to the data sources corresponding to each target query domain based on the verified query parameters, and receive the returned credit information. The parallel query method greatly improves the efficiency of information acquisition and shortens the report generation time.

[0070] The report synthesis module, connected to the parallel query engine for credit information, is used to integrate the received credit information and generate standardized special credit information reports. Through preset report templates, it ensures that the report format is uniform and the content is standardized, thereby improving the readability and authority of the report.

[0071] The report storage and authorization management module is connected to the query control module and the report synthesis module, respectively. It is used to store the generated reports, verify and retrieve the corresponding reports in response to the authorization code query process, and manage the authorization codes of the reports. It realizes the persistent storage of reports and the centralized management of authorization information, and provides data support for report reuse.

[0072] The notification and delivery module, connected to the report storage and authorization management module, is used to send report generation notifications and deliver report files to users, ensuring that users can obtain the report generation status in a timely manner and complete the report download, thereby improving the user experience.

[0073] Furthermore, the method is implemented through a computer program, which, when executed by a processor, specifically performs the steps of receiving requests, determining query types, obtaining parameters, processing queries in sensitive areas, querying credit information, generating reports, and processing authorization code queries. This computer program can be stored in a computer-readable storage medium for easy deployment and execution.

[0074] Example 1

[0075] Financing scenarios for SMEs – Multi-domain “domain-date lookup” and authorization code reuse, including sensitive sectors

[0076] [Scenario Background] A small and medium-sized manufacturing enterprise (SME A) intends to apply for a working capital loan from a bank. The bank requires the enterprise to provide credit information reports from market supervision, taxation, and law enforcement agencies for the past three years. The enterprise needs to generate the reports on its own and then provide them to the bank for verification through an authorization code.

[0077]

Execution Steps

[0078] Step 1: Company A initiates a report generation request through its enterprise terminal (the webpage of the public credit information service platform on a computer). The query type in the request is identified as "domain-date query". The target query domain is selected as "market supervision", "taxation" and "law enforcement agencies". The target date range is specified as June 1, 2022 to May 31, 2025 (the report generation date is June 30, 2025, which meets the date range requirements).

[0079] Step 2: After the server request parsing module parses the request, it outputs the "Domain-Date Query" identifier, and the query control module routes the request to the Domain-Date Query process.

[0080] Step 3: The parameter processing and verification module obtains and verifies the target query domain and date range, confirming that all three belong to the predefined domain set, the date range spans 3 years, and the deadline is May 31, 2025 (30 days from the generation date). The verification is successful.

[0081] Step 4: The security collaboration processing module determines that the target domain includes the sensitive domain "law enforcement agencies" and sends a facial recognition request to Enterprise A's terminal; the enterprise's representative completes facial recognition through the terminal's camera, and after the server verifies the result, it initiates a query request to the data source in the law enforcement agency domain; at the same time, the parameter processing and verification module initiates a query request to the public credit information database in the market supervision and taxation fields.

[0082] Step 5: The credit information parallel query engine processes queries from three domains in parallel: the market supervision domain returns the warning and penalty information of enterprise A in 2023 for non-standard product labeling in real time; the tax domain returns the information of enterprise A that has no tax arrears or tax penalties in the past 3 years in real time; the law enforcement agency domain data source returns the information of enterprise A that has no criminal record or public security penalty record in the past 3 years after 3 working days. The server caches the results of the law enforcement agency domain (the cache is valid for 3 months).

[0083] Step 6: The report synthesis module integrates information according to the categories of "Market Supervision - 2023", "Taxation - 2022-2025" and "Law Enforcement Agency - 2022-2025", fills in the special credit report template, generates the report file and assigns a unique identifier "XYBG20250630001".

[0084] Step 7: The report storage and authorization management module stores the report and generates an authorization code “SQ20250630001” (valid for 1 month) bound to a unique identifier.

[0085] Step 8: The notification and delivery module sends an SMS notification to the mobile phone number registered with Company A: "Your public credit information report has been generated. Unique identifier: XYBG20250630001, authorization code: SQ20250630001 (valid for 1 month). Please log in to the platform to download: [Download Link]". After Company A's representative logs in to the platform, downloads the report, verifies that it is correct, and then informs the lending bank of the authorization code.

[0086] Step 9: Bank staff initiate an "authorization code query" request through the bank terminal and enter the authorization code "SQ20250630001"; after the server verifies the validity of the authorization code, it retrieves the report based on the associated unique identifier and provides it to the bank staff for viewing and downloading, thus completing the report reuse.

[0087] Example 2

[0088] SME Bidding Scenarios – Domain-Date Query and Reuse of Duplicate Queries in a Single Non-Sensitive Domain

[0089] [Scenario Background] A small and medium-sized construction company, B, participated in a government engineering project bidding. The bidding party required the provision of credit information reports in the housing and construction sector for the past two years. After the initial query, company B found that some information in the report was incomplete and needed to query the same report in the same sector and date range again one month later.

[0090]

Execution Steps

[0091] Step 1: Company B initiates a report generation request via mobile APP, with the query type identified as "domain-date query", the target query domain selected as "housing and construction", and the specified date range as July 1, 2023 to June 30, 2025 (the report generation date is July 1, 2025, which meets the requirements).

[0092] Step 2: After the server request parsing module parses the request, the query control module routes it to the domain-date query process.

[0093] Step 3: The parameter processing and verification module verifies the predefined non-sensitive domain, with a date range spanning 2 years and a deadline of 30 days from the generation date. The verification passes.

[0094] Step 4: Since there are no sensitive areas, directly initiate a query request to the public credit information database for the housing and construction sector.

[0095] Step 5: The parallel query engine for credit information receives real-time information from the housing and construction sector, including the safety production compliance record of a certain project of Company B in 2024, with no administrative penalty information, but some project filing information is incomplete.

[0096] Step 6: The report synthesis module integrates information to generate a report, assigns a unique identifier "XYBG20250701002", and generates an authorization code "SQ20250701002" after the report is stored. The notification module sends an SMS notification to Enterprise B to download the report.

[0097] Step 7: One month later, Company B needs to supplement its bidding materials and initiates another "domain-date query" request for the same domain (housing and construction) and the same date range. The server security collaborative processing module detects that the duplicate query is for the same user and the same non-sensitive domain, and directly retrieves the cached result of the first query (the cache validity period of the query result for non-sensitive domains is the same as that for sensitive domains, which is 3 months), without having to query the housing and construction data source again.

[0098] Step 8: The report synthesis module regenerates the report based on the cached results (supplementing and improving the display of filing information), assigns a new unique identifier "XYBG20250801003", generates a new authorization code and notifies Enterprise B to download it, greatly reducing the query time.

[0099] Example 3

[0100] SME Qualification Application Scenarios – “Field-Date Inquiry” for Multiple Sensitive Fields (Extended)

[0101] [Scenario Background] A catering company, C, intends to apply for the renewal of its "Food Business License". The regulatory authorities require the company to provide credit information reports on market supervision, law enforcement agencies (fire safety field), and environmental protection (sewage discharge field) for the past three years. Among these, law enforcement agencies (fire safety) and environmental protection (sewage discharge) have been expanded to be sensitive areas.

[0102]

Execution Steps

[0103] Step 1: Enterprise C initiates a "Domain-Date Query" request through the terminal, selecting the target domain as "Market Supervision", "Law Enforcement Agency (Fire Safety)" and "Environmental Protection (Sewage Discharge)", with a date range from July 1, 2022 to June 30, 2025 (generation date July 1, 2025).

[0104] Step 2: After parsing the request, the server routes it to the domain-date query process. The parameter validation module confirms that all three domains belong to the predefined set (the sensitive domain is expanded to include sub-domains of law enforcement agencies and environmental protection agencies), and the date range meets the requirements.

[0105] Step 3: The security collaboration processing module determines that there are two sensitive areas, triggers facial recognition verification, and after successful verification, initiates query requests to the law enforcement agency (fire safety) and environmental protection (sewage discharge) data sources respectively; at the same time, it initiates query requests to the market supervision field.

[0106] Step 4: Parallel query engine processes queries: In the market supervision field, it returns information on no food quality penalties for enterprise C in the past 3 years; in the law enforcement agency (fire safety) field, it returns the 2024 fire safety inspection qualification record after 3 working days; in the environmental protection (sewage discharge) field, it returns information on no sewage discharge exceeding the standard penalties in the past 3 years after 3 working days. The results for the two sensitive fields are cached.

[0107] Step 5: The report synthesis module integrates information by domain and time, generates a special report containing information from three domains, assigns a unique identifier "XYBG20250701004", generates an authorization code, and sends an SMS notification to enterprise C to download it.

[0108] Step 6: After downloading the report, Company C submits it to the regulatory authority. The regulatory authority initiates an inquiry using the authorization code provided by the company to verify the authenticity and validity of the report information, thus smoothly advancing the qualification renewal approval process.

[0109] The examples provided in this invention are not intended to limit the implementation. Those skilled in the art will recognize that various variations or modifications can be made based on the above description. It is neither necessary nor possible to exhaustively list all possible implementations, and any obvious variations or modifications derived therefrom are still within the scope of this invention.

Claims

1. A method for generating a public credit information report, characterized in that, This method is executed by the server and includes the following steps: Receive a report generation request initiated by a user terminal, wherein the request contains a query type identifier; When the query type identifier indicates "domain-date query", the following steps are performed: S11: Obtain at least one target query field and a specified target date range selected by the user from the request; wherein the target query field is selected from a predefined set of administrative management fields, the span of the target date range does not exceed a preset maximum number of years, and the end date is not later than a preset number of days before the report generation date; S12: Determine whether the target query domain contains a preset sensitive domain; If so, the biometric verification process for the user is triggered and completed. After the verification is successful, a query request is initiated to the corresponding sensitive data source. The query result returned by the data source after a preset processing period is received. If a repeated query request for the same user and the same sensitive area is received within the preset cache validity period, the cached result from the first query is returned directly. If not, then a query request will be directly sent to the corresponding public credit information database; S13: Based on the target query domain and the target date range, perform parallel queries and obtain the user's credit information in all selected domains; S14: Integrate the acquired credit information by field and time, fill it into the preset report template, generate a special credit information report file, and assign a unique identifier to the report; S15: After generating the report, send a notification to the user and provide a report download service; When the query type identifier indicates "authorization code query", the following steps are performed: S21: Obtain the authorization code entered by the user from the request; S22: Verify the validity of the authorization code; S23: If the authorization code is valid, retrieve the generated special credit information report file based on the unique report identifier associated with the authorization code and provide it to the user.

2. The method for generating a public credit information report according to claim 1, characterized in that, In step S11, the target date range spans no more than 3 years, and the cutoff date is no later than the 30th calendar day before the report generation date.

3. The method for generating a public credit information report according to claim 1, characterized in that, In step S12, the sensitive area is the law enforcement agency area, the biometric verification process is face recognition, the preset processing cycle is 3 working days, and the cache validity period is 3 months.

4. The method for generating a public credit information report according to claim 1, characterized in that, In S13, the credit information includes administrative penalty information, administrative enforcement information, information on the list of seriously dishonest entities, and criminal judgment information.

5. The method for generating a public credit information report according to claim 1, characterized in that, After generating the report, the method further includes: generating an authorization code that is uniquely linked to the report, the authorization code having an expiration period, which is used by other users to obtain the report through an "authorization code query" method.

6. The method for generating a public credit information report according to claim 1, characterized in that, After the report is generated, it also includes sending a text message to the user containing a notification that the report has been generated.

7. The method for generating a public credit information report according to claim 1, characterized in that, The server that performs the method includes: The request parsing module is used to receive and parse report generation requests and output query type identifiers; The query control module, connected to the request parsing module, is used to route the request to the domain-date query process or the authorization code query process in response to the received query type identifier. The parameter processing and verification module, connected to the query control module, is used to obtain and verify the target query domain and date range selected by the user when the query is routed to the domain-date query process. The security collaboration processing module, connected to the parameter processing and verification module, is used to respond to the judgment that the target query domain contains a sensitive domain, manage the biometric verification process, and control the query and result caching and reuse of sensitive domain data sources. The parallel query engine for credit information is connected to the parameter processing and verification module and the security collaborative processing module. It is used to initiate query requests to the data sources corresponding to each target query domain in parallel according to the verified query parameters, and to receive the returned credit information. The report synthesis module, connected to the parallel query engine for credit information, is used to integrate the received credit information and generate a standardized special credit information report. The report storage and authorization management module is connected to the query control module and the report synthesis module, respectively, and is used to store the generated reports, verify and retrieve the corresponding reports in response to the authorization code query process, and manage the authorization codes of the reports; The notification and delivery module, connected to the report storage and authorization management module, is used to send report generation notifications and deliver report files to users.

8. The method for generating a public credit information report according to claim 1, characterized in that, The method is implemented by a computer program, which, when executed by a processor, specifically implements the steps of receiving requests, determining query types, obtaining parameters, processing queries in sensitive areas, querying credit information, generating reports, and processing authorization code queries.

Images