Personal information processing method, apparatus, device, and medium

Abstract

This application relates to the fields of data processing and artificial intelligence technology, and proposes a method, apparatus, device, and medium for processing personal information, applicable to fintech scenarios. The method includes: receiving an information processing request from a client page, the information processing request including at least business scenario parameters for identifying a target business scenario; obtaining target configuration information corresponding to the target business scenario and sending it to the client; responding to a user's selection instruction for a target document type on the client page, loading and activating a corresponding set of target verification sub-rules from business rule configuration information, the business rule configuration information pre-setting multiple sets of verification sub-rules bound to different document types; and performing verification on the input personal information based on the target verification sub-rules set, and outputting the verified standard personal information data. This technical solution improves business response efficiency and user experience.

Description

Technical Field

[0001] This application relates to the fields of data processing and human-computer interaction technology, and in particular to a method, apparatus, device and medium for processing personal information. Background Technology

[0002] In numerous business sectors such as fintech, insurance, healthcare, and e-commerce, the collection, verification, and processing of user personal information are fundamental and frequently occurring core scenarios, including account opening, real-name authentication, insurance purchase, medical appointment booking, and mailing address entry. Current technologies typically require the separate development of corresponding personal information processing pages for different business systems and scenarios to meet the personalized needs of the current situation. However, this traditional approach has many flaws and shortcomings, severely impacting development efficiency and maintenance costs, specifically as follows: 1) Severe duplication of development and waste of human resources: Different business systems and different business scenarios all require the separate development of personal information processing pages. Developers need to repeatedly write similar page code, validation logic and interaction logic, which not only increases the workload of development, but also leads to a significant increase in human resources costs and reduces development efficiency.

[0003] 2) High maintenance costs and difficulty in ensuring consistency: Each independently developed page requires dedicated personnel for maintenance. If the validation rules, interface style or interaction logic need to be modified, all related pages need to be modified one by one. Not only is the maintenance workload large, but it is also easy to have inconsistent modifications and rules, which affects user experience and business standardization.

[0004] 3) Poor scenario adaptability and insufficient scalability: Traditional pages use fixed validation rules, interface elements, and style designs, making it difficult to flexibly adapt to the differentiated needs of different business scenarios. When new business scenarios are added or existing scenario requirements change, large-scale modifications or even redevelopment of the page are required, resulting in poor scalability and an inability to quickly respond to business changes.

[0005] 4) Poor cross-environment data transmission: In multi-platform and multi-environment (such as mini-programs, web applications, and local applications) interaction scenarios, the format of personal information data is not uniform, which makes it impossible to achieve efficient interoperability. This causes users to repeatedly fill in personal information in different environments, which is cumbersome and also increases the risk of data redundancy and inconsistency.

[0006] In summary, existing methods of processing personal information suffer from problems such as redundant development, high maintenance costs, poor adaptability to different scenarios, and poor data transmission across environments, failing to meet the needs of efficient and flexible processing for multi-scenario and multi-platform businesses. Summary of the Invention

[0007] This application provides a method, apparatus, device, and medium for processing personal information, aiming to solve many technical problems in existing personal information processing methods, such as repetitive development, high maintenance costs, poor scenario adaptability, and poor cross-environment data transmission.

[0008] In a first aspect, embodiments of this application provide a method for processing personal information, which can be applied to scenarios such as fintech, insurance, and healthcare. The method includes: Receive an information processing request from a client page, wherein the information processing request includes at least business scenario parameters for identifying the target business scenario; Based on the business scenario parameters, obtain the target configuration information corresponding to the target business scenario, and send the target configuration information to the client. The configuration information includes business rule configuration information for defining the composition and verification rules of interface elements, and style configuration information for defining the visual appearance of the interface. In response to receiving a user's selection instruction for a target document type on the client page, the system loads and activates the corresponding target verification sub-rule set from the business rule configuration information according to the target document type. The business rule configuration information pre-sets multiple verification sub-rule sets that are respectively bound to different document types. Based on the activated set of target verification sub-rules, the personal information entered by the user on the client page is verified, and the verified standard personal information data is output.

[0009] Secondly, embodiments of this application provide a personal information processing device, the device comprising: A receiving module is used to receive information processing requests from a client page, wherein the information processing requests include at least business scenario parameters for identifying the target business scenario; The acquisition module is used to acquire target configuration information corresponding to the target business scenario based on the business scenario parameters, and send the target configuration information to the client. The configuration information includes business rule configuration information for defining the composition and verification rules of interface elements, and style configuration information for defining the visual appearance of the interface. The processing module is used to respond to receiving a user's selection instruction for a target document type on the client page, and to load and activate the corresponding target verification sub-rule set from the business rule configuration information according to the target document type. The business rule configuration information pre-sets multiple verification sub-rule sets that are respectively bound to different document types. The verification module is used to verify the personal information entered by the user on the client page based on the activated target verification sub-rule set, and output the verified standard personal information data.

[0010] Thirdly, a computer device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the steps of the aforementioned personal information processing method.

[0011] Fourthly, a computer-readable storage medium is provided, storing a computer program that, when executed by a processor, implements the steps of the aforementioned personal information processing method. In the scheme implemented by the above-mentioned personal information processing method, apparatus, device, and medium, an information processing request is received from a client page, the request including at least business scenario parameters for identifying a target business scenario; based on the business scenario parameters, target configuration information corresponding to the target business scenario is obtained, and the target configuration information is sent to the client, wherein the configuration information includes business rule configuration information for defining interface element composition and verification rules, and style configuration information for defining interface visual appearance; in response to receiving a user's selection instruction for a target document type on the client page, a corresponding target verification sub-rule set is loaded and activated from the business rule configuration information according to the target document type, wherein the business rule configuration information pre-sets multiple verification sub-rule sets respectively bound to different document types; based on the activated target verification sub-rule set, the personal information entered by the user on the client page is verified, and the verified standard personal information data is output. In this invention, by receiving information processing requests carrying business scenario parameters, the target business scenario can be accurately matched and the corresponding business rule configuration information and style configuration information can be retrieved. This avoids the problem of needing to develop separate personal information processing pages for different business scenarios in existing technologies, thereby reducing repetitive development workload and lowering labor costs. By pre-setting a set of verification sub-rules bound to different document types in the business rule configuration information, and dynamically loading and activating the corresponding set of verification sub-rules in response to the user's document type selection instruction, flexible adaptation of personal information verification rules is achieved. This solves the defects of fixed page verification rules and poor scenario adaptability in traditional pages, and improves the accuracy of personal information verification. At the same time, based on the activated set of verification sub-rules, the personal information input by the user is verified and standard personal information data is output, which standardizes the personal information format and lays the foundation for subsequent data processing. This solves the pre-existing pain points of high maintenance costs, difficulty in ensuring rule consistency, and poor cross-environment data transmission in existing technologies. Ultimately, it achieves standardized and dynamic adaptation of personal information processing, improves business response efficiency and user experience, and meets the efficient and flexible processing needs of multi-scenario and multi-platform businesses. Attached Figure Description

[0012] To more clearly illustrate the technical solutions of the embodiments of this application, the drawings used in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0013] Figure 1 A schematic flowchart of a personal information processing method according to an embodiment of this application is shown.

[0014] Figure 2 A schematic flowchart of step S104 in a personal information processing method according to an embodiment of this application is shown.

[0015] Figure 3 A schematic flowchart of a personal information processing method according to yet another embodiment of this application is shown.

[0016] Figure 4 A block diagram of a personal information processing apparatus according to an embodiment of this application is shown.

[0017] Figure 5 A schematic diagram of the structure of a computer device according to an embodiment of this application is shown.

[0018] Figure 6 Another structural schematic diagram of a computer device according to an embodiment of this application is shown. Detailed Implementation

[0019] To better understand the technical solution of this application, the embodiments of this application will be described in detail below with reference to the accompanying drawings.

[0020] It should be understood that the described embodiments are merely some, not all, of the embodiments in this application. All other embodiments obtained by those skilled in the art based on the embodiments in this application without inventive effort are within the scope of protection of this application.

[0021] The terminology used in the embodiments of this application is for the purpose of describing particular embodiments only and is not intended to be limiting of this application. The singular forms “a,” “the,” and “the” used in the embodiments of this application and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise.

[0022] The following detailed description of some embodiments of this application is provided in conjunction with the accompanying drawings. Unless otherwise specified, the following embodiments and features can be combined with each other.

[0023] It should be noted that the embodiments of this application can acquire and process relevant data based on artificial intelligence technology. Artificial intelligence is the theory, method, technology, and application system that uses digital computers or machines controlled by digital computers to simulate, extend, and expand human intelligence, perceive the environment, acquire knowledge, and use that knowledge to obtain optimal results.

[0024] The fundamental technologies of artificial intelligence generally include sensors, dedicated AI chips, cloud computing, distributed storage, big data server processing technology, operating / interactive systems, and mechatronics. Artificial intelligence software technologies mainly include computer vision, robotics, biometrics, speech processing, natural language processing, and machine learning / deep learning.

[0025] Please see Figure 1 , Figure 1 A schematic flowchart of a personal information processing method according to an embodiment of this application is shown.

[0026] like Figure 1 As shown, a personal information processing method according to an embodiment of this application includes: Step S101: Receive an information processing request from a client page, wherein the information processing request includes at least business scenario parameters for identifying the target business scenario; When a client (such as an insurance application page or a bank account opening page) needs to load a personal information entry module, it will send an information processing request to the server. This request is transmitted through URL parameters, the HTTP body, or a specific API interface, and must contain at least one business scenario parameter to uniquely identify the current target business scenario.

[0027] The information processing request includes at least business scenario parameters (i.e., businessScene parameters) to identify the target business scenario. Optionally, the information processing request may also include page element parameters, style identifier parameters, interaction control parameters, etc. The page element parameters are used to further accurately locate the combination configuration of interface elements, the style identifier parameters are used to specify the style configuration information that the client page needs to load, and the interaction control parameters include the go parameter and the returnUrl parameter, which are used to control the page interaction after the verification is completed.

[0028] For example, in an insurance business scenario, users need to register their personal information to conduct insurance business. The client page sends an information processing request to the server, which includes parameters such as businessScene="insurance" (identifying the insurance business scenario), page="1" (page element parameter, indicating the display of core elements such as name, document type, and document number), style="1" (style identifier parameter, indicating the loading of the general orange button style), and go="1" (interaction control parameter, indicating the return to the previous page after verification).

[0029] Step S102: Based on the business scenario parameters, obtain the target configuration information corresponding to the target business scenario, and send the target configuration information to the client. The configuration information includes business rule configuration information for defining the composition and verification rules of interface elements, and style configuration information for defining the visual appearance of the interface. Specifically, the server pre-stores a one-to-one correspondence between multiple business scenarios and configuration information, parses the received business scenario parameters, matches the corresponding business scenario, and retrieves the preset target configuration information for that business scenario. The target configuration information can be dynamically expanded and modified according to business needs, and the expansion and modifications take effect without system deployment, significantly improving business response efficiency.

[0030] Furthermore, if the information processing request also includes page element parameters and style identifier parameters, the server will jointly determine and retrieve the target configuration information based on the business scenario parameters, page element parameters, and style identifier parameters. For example, combining businessScene="insurance", page="1", and style="1", the server will retrieve the interface element combination configuration corresponding to page="1" (displaying name, ID type, and ID number), the style configuration corresponding to style="1" (orange button, 14-point font), and the validation rule configuration corresponding to the insurance business scenario under the insurance business scenario.

[0031] The business rule configuration information also includes interface element combination configuration. This configuration defines the core elements related to personal information entry and interaction that need to be displayed on the client-side page (such as a name input box, a document type dropdown, and a submit button). The server can dynamically adjust the interface element combination configuration based on business scenario parameters to control the display and hiding of core elements. For example, in a simple registration scenario, unnecessary elements such as date of birth and gender are hidden; in a detailed registration scenario, all elements are displayed.

[0032] The style configuration information includes font, color value, and layout-related style data. The server pre-stores multiple sets of style configuration information (such as general styles, financial industry-specific styles, and medical industry-specific styles), and supports receiving new style files uploaded by clients to expand and replace the style configuration information. After replacement, it is immediately applied to the client page rendering of the corresponding business scenario without system release, flexibly adapting to the style requirements of different platforms and different businesses.

[0033] Step S103: In response to receiving the user's selection instruction for the target document type on the client page, load and activate the corresponding target verification sub-rule set from the business rule configuration information according to the target document type, wherein the business rule configuration information pre-sets multiple verification sub-rule sets that are respectively bound to different document types; In this step, after receiving the target configuration information sent by the backend, the client loads the business rule configuration information and style configuration information, and renders the client page. The user selects a target document type (such as ID card, passport, household registration book, etc.) on the client page. The client responds to the user's selection by sending the target document type information to the backend. The backend, based on the target document type, loads and activates the corresponding target verification sub-rule set from the business rule configuration information. The business rule configuration information pre-sets multiple verification sub-rule sets bound to different document types.

[0034] Specifically, the different document types include ID cards and non-ID cards (passports, household registration books, military officer certificates), and the corresponding verification sub-rules are divided into ID card verification sub-rules and non-ID card verification sub-rules. The ID card verification sub-rules set includes at least verification items for name, document type, and document number. For example, the name verification requirement is 2-10 Chinese characters, and the document number verification requirement is an 18-digit valid ID card number. The non-ID card verification sub-rules set includes at least verification items for name, document type, document number, date of birth, and gender. For example, the passport number verification requirement is a specific format, and the date of birth verification requirement is a YYYY-MM-DD format.

[0035] For example, if a user selects an ID card as the target document type, the backend loads and activates the ID card verification sub-rule set, which includes verification rules for name, document type, and document number; if the user selects a passport as the target document type, the backend loads and activates the non-ID card verification sub-rule set, which includes verification rules for name, document type, document number, date of birth, and gender.

[0036] Meanwhile, the client can update the page in real time based on the newly loaded rule set. For example, it can hide or show input items that are strongly related to document type, such as "date of birth" and "gender," and update the corresponding validation logic and prompts. This allows the validation logic to switch dynamically and seamlessly as the user selects on the same page.

[0037] Step S104: Based on the activated target verification sub-rule set, perform verification on the personal information entered by the user on the client page, and output the verified standard personal information data.

[0038] In this step, after the user fills in the information, the client first performs real-time front-end validation using the currently active set of validation sub-rules. Once validation passes, the data and the currently effective validation rule identifier are submitted to the server. The server then performs final validation based on the same set of rules. After all validations pass, the server standardizes the personal information (e.g., formatting dates, using standardized encoding) and outputs a structured, standardized personal information data that meets business requirements.

[0039] In one embodiment, optionally, after the step of loading and activating the target verification sub-rule set according to the target document type, the method further includes: Based on the target validation sub-rule set, the user interface and interaction logic of the client page are updated in real time, and the update includes at least one of the following: Update the list of personal information input fields that need to be filled in on the client page; Update the validation logic applied to each personal information input field; Update the prompts corresponding to each input item and validation logic.

[0040] In this embodiment, after loading and activating the target validation sub-rule set, the server will synchronously send the interface update instruction corresponding to the target validation sub-rule set to the client. After receiving the instruction, the client will dynamically update the user interface and interaction logic of the current page in real time based on the validation items, validation standards and prompt specifications contained in the target validation sub-rule set. This ensures that the content and validation logic displayed on the client page are completely matched with the activated validation sub-rule set, improving the relevance and convenience of user operations, while ensuring the standardization of personal information entry.

[0041] For example, assuming the target business scenario is personal information registration for government services, the server-side pre-configured business rules bind sets of verification sub-rules for two document types: ID card and passport. The ID card verification sub-rule set includes three verification items: name, document type, and document number. The passport verification sub-rule set includes five verification items: name, document type, document number, date of birth, and gender. When a user selects "ID card" as the target document type on the client page, the server loads and activates the ID card verification sub-rule set, then sends an interface update command to the client. The client performs the following update operations based on this command: First, it updates the list of personal information input items, displaying only the name input box, the document type dropdown (with "ID card" selected by default), and the document number input box, hiding the date of birth and gender-related input items to prevent users from seeing unnecessary information and reduce operational interference; Second, it updates the verification logic for each input item. For the name input item, the verification logic is updated to "2-10 Chinese characters, excluding special characters," and for the document number input item, the verification logic is updated to "2-10 Chinese characters, excluding special characters." The new verification logic is "18-digit valid ID card number, the 18th digit can be a number or an X (uppercase)", ensuring that the verification logic accurately matches the ID card verification requirements; thirdly, the corresponding prompt information has been updated. Below the name input box, the prompt "Please enter your real name of 2-10 Chinese characters, excluding special characters" is displayed, and below the ID number input box, the prompt "Please enter an 18-digit valid ID card number, the last digit can be an X (uppercase)" is displayed. At the same time, real-time verification prompts are set up. When the user enters content that does not conform to the verification logic (such as entering a 17-digit ID card number), a prompt "ID card number format is incorrect, please enter an 18-digit valid ID card number" will pop up immediately to guide the user to correct the input.

[0042] For example, when a user switches the target document type to "passport," the server reloads and activates the corresponding set of verification sub-rules for passports, and simultaneously sends an interface update command. Upon receiving the command, the client executes the corresponding update operation again: updating the personal information input list by adding a date of birth input box and a gender radio button (male / female) to the existing name, document type, and document number input fields, ensuring that all input fields required for passport verification are displayed correctly; and updating the verification logic for each input field, changing the document number verification logic to "conforms to passport number format (e.g., E + 8 digits, G + 8 digits, etc.)," ​​and adding a date of birth verification logic to "conforms to YYYY- The system requires users to enter their passport number in MM-DD format and within a reasonable range for the date of birth (e.g., from 1900 to the present). The new gender validation logic is "required, and only male or female can be selected." Corresponding prompts have been updated: the prompt for the ID number input box is now "Please enter a passport number in the correct format (e.g., E12345678, G87654321)"; below the date of birth input box, it displays "Please enter your date of birth in YYYY-MM-DD format (e.g., 1990-01-01)"; and next to the gender radio button, it displays "Please select gender." Real-time validation prompts for each input item are updated synchronously to ensure accurate validation guidance for every piece of information entered by the user.

[0043] Through the aforementioned real-time update operations, the client page can dynamically adapt the displayed content, verification logic, and prompts based on the user's selected document type. This avoids displaying invalid input items, simplifies the user operation process, and improves the user experience. Furthermore, it ensures that the verification logic highly matches the requirements of the current document type, reducing invalid input and verification errors, further improving the accuracy and efficiency of personal information verification. It also makes the entire personal information processing flow more flexible and standardized, better adapting to the differentiated needs of different document types, and providing strong support for the subsequent output of standard personal information data. Simultaneously, the server only needs to send an update command, and the client can dynamically adjust the interface and interaction logic without reloading the entire page, improving page response speed and further optimizing the user experience. This demonstrates the core advantage of dynamic adaptation in this solution, effectively compensating for the shortcomings of traditional fixed pages that cannot dynamically adjust according to document type.

[0044] In one embodiment, optionally, the information processing request further includes a style identifier parameter; Step S102 above includes: Based on the business scenario parameters and the style identifier parameters, obtain the corresponding style resource file as the style configuration information; The style resource file is stored and loaded independently of the application logic code of the client page, and modifications and updates to the style resource file do not depend on the release of the application logic code.

[0045] In addition to business scenario parameters, the information processing request sent by the client also carries style identifier parameters. These parameters specify the style resource files that the client page needs to load, and different style identifier parameters correspond to different style resource files. For example, the style identifier parameter for the government service scenario is "styleId=govStyle1", and the style identifier parameter for the financial real-name authentication scenario is "styleId=financeStyle1".

[0046] After receiving the information processing request, the server parses both the business scenario parameters and the style identifier parameters. Based on the combination of these two parameters, it retrieves the corresponding style resource file from the server's style resource library, which is then used as the style configuration information in the target configuration information. For example, when the business scenario parameter is "businessScene=government" and the style identifier parameter is "styleId=govStyle1", the server retrieves a style resource file specific to government services; when the business scenario parameter is "businessScene=finance" and the style identifier parameter is "styleId=financeStyle1", it retrieves a style resource file specific to the financial industry.

[0047] In this system, style resource files are independent of the application logic code on the client-side page. They are stored separately in a style resource library on the server and employ an independent loading mechanism. When the client renders the page, it first loads the application logic code and then retrieves the corresponding style resource file from the server using style identifier parameters, thus separating style from logic. When the page style needs to be modified (e.g., changing the button color from blue to dark gray in a government service scenario), only the corresponding style resource file needs to be modified on the server side. There is no need to modify the client-side application logic code or publish the application logic code. After the modification is completed, the updated style resource file will be automatically retrieved the next time the client loads the page, enabling rapid style updates and reducing maintenance costs.

[0048] By obtaining the corresponding style configuration information through style identifier parameters, the separation of page style and application logic is achieved, breaking the limitation of style and code binding. The independent storage and updating of style resource files can complete style adjustments without modifying the front-end application logic code or system release, which greatly reduces style maintenance costs and improves style update efficiency. At the same time, it supports flexible switching of multiple style resources, which can quickly adapt to the visual needs of different platforms and different business scenarios, enhancing the versatility and scalability of the page.

[0049] In one embodiment, optionally, the information processing request further includes page element parameters; The step of obtaining target configuration information corresponding to the target business scenario based on the business scenario parameters includes: Based on the business scenario parameters and the page element parameters, obtain the business rule configuration information corresponding to the target business scenario, so as to control the client page to render the combination of personal information input items corresponding to the page element parameters.

[0050] In addition to business scenario parameters, the information processing request sent by the client also carries page element parameters. These parameters specify the combination of personal information input items to be rendered on the client page, with different page element parameters corresponding to different combinations of input items. For example, the page element parameter for "Basic Information Registration" is "elementId=basicInfo", and the page element parameter for "Detailed Information Registration" is "elementId=detailInfo".

[0051] After receiving the information processing request, the server parses the business scenario parameters and page element parameters. Based on the combination of the two, it retrieves the business rule configuration information corresponding to the target business scenario from the server's configuration storage module. This configuration information is used to control the client page to render the combination of personal information input items corresponding to the page element parameters. When the business scenario parameter is "businessScene=government" and the page element parameter is "elementId=basicInfo", the server-side obtains the business rule configuration information and controls the client page to render only the basic input item combination (name, ID type, ID number). When the page element parameter is "elementId=detailInfo", the server-side obtains the business rule configuration information and controls the client page to render the detailed input item combination (name, ID type, ID number, contact number, home address). At the same time, the corresponding set of validation sub-rules will also be expanded synchronously (adding validation items for contact number and home address). If a scenario does not require displaying the ID number, the corresponding page element parameter (such as "elementId=noIdCard") can be configured to control the client page to hide the ID number input item, realizing flexible control of input item combinations and adapting to the differentiated needs of different business scenarios.

[0052] In addition, for less frequently used page elements, corresponding element configurations can be added in the business rule configuration information on the server side, and new page element parameters can be assigned. This allows for the extended display of page elements without modifying the front-end code, making it quick and efficient.

[0053] The above solution combines page element parameters with business scenario parameters to achieve flexible control over the combination of personal information input items. It can accurately display required input items and hide unnecessary ones according to the needs of different business scenarios, avoiding operational interference caused by redundant input items and improving user efficiency. Simultaneously, it supports rapid expansion of page elements without modifying the front-end code; new display modules can be added simply by configuring new page element parameters on the server side. This further enhances the scalability and adaptability of the solution, meeting the differentiated needs of different business scenarios for page elements and reducing the development and maintenance costs of customized pages.

[0054] In one embodiment, optionally, the different document types include ID cards and non-ID cards, and the corresponding verification sub-rule sets are divided into ID card verification sub-rule sets and non-ID card verification sub-rule sets; The set of ID card verification sub-rules includes at least verification items for name, document type, and document number, while the set of non-ID card verification sub-rules includes at least verification items for name, document type, document number, date of birth, and gender.

[0055] In this embodiment, different document types are divided into two main categories: ID cards and non-ID cards. Non-ID cards include common document types such as passports, household registration books, and military officer certificates. The server-side business rule configuration information binds a corresponding set of verification sub-rules to each document type to achieve categorized verification. The ID card verification sub-rule set contains at least three core verification items: name, document type, and document number. Depending on the `businessScene` parameter, additional verification items (such as mobile phone number, date of birth, and gender) can be flexibly added. The specific verification standards for each item are as follows: (1) Name: 2-10 Chinese characters, excluding special characters, numbers and letters, and must be consistent with the name on the ID card; (2) Document type: Fixed as "ID card", cannot be modified, and must be consistent with the selected target document type; (3) ID number: 18-digit valid ID number, the first 6 digits are the address code, the middle 8 digits are the birth date code (in YYYYMMDD format), the 17th digit is the gender code (odd numbers are male, even numbers are female), and the 18th digit is the check code (can be a number or uppercase X). (4) Optional verification items (configured according to businessScene parameters): mobile phone number (11-digit valid mobile phone number), date of birth (consistent with the date of birth code in the ID number), gender (consistent with the gender code in the ID number).

[0056] The set of non-ID card verification sub-rules must contain at least 5 core verification items, specifically: name, document type, document number, date of birth, and gender. The specific verification standards for each item are as follows (taking passport and household registration book as examples): (1) Name: 2-10 Chinese characters, may include pinyin (such as the pinyin corresponding to the English name on the passport), but does not include special characters; (2) Document type: Fixed to the corresponding non-ID card type (such as "passport" or "household registration book"), cannot be modified, and must be consistent with the selected target document type; (3) Document number: conforms to the corresponding document number format, such as passport is “letter + 8 digits” (e.g. E12345678, G87654321), and household registration book is in the format prescribed by the local household registration management department; (4) Date of birth: conforms to the YYYY-MM-DD format, and the date of birth is within the range of January 1, 1900 to the current date, consistent with the date of birth on the certificate; (5) Gender: Required. You can only choose "male" or "female" and it must be consistent with the gender on your ID.

[0057] By categorizing and binding a set of verification sub-rules, and combining this with the flexible configuration of businessScene parameters, we can achieve accurate verification for different document types and scenarios, avoiding verification errors caused by uniform verification rules, while also supporting the addition of verification items at any time.

[0058] like Figure 2 As shown, in one embodiment, optionally, step S104 specifically includes: Step S201: Receive the personal information input by the user and the identifier of the activated target verification sub-rule set sent by the client; and match and compare the personal information item by item according to the target verification sub-rule set. After the client completes the input of personal information, it sends the user's personal information (such as name, ID type, ID number, etc.) and the activated target verification sub-rule set identifier (such as "idCardRule", corresponding to the ID card verification sub-rule set) to the server, requesting the server to perform verification. After receiving the above data, the server retrieves the corresponding verification sub-rule set according to the target verification sub-rule set identifier, and then matches and compares the user's personal information item by item according to the verification items in the verification sub-rule set to ensure that each piece of information meets the corresponding verification standard.

[0059] Step S202: If all items of the personal information meet the verification requirements, the verification is successful and standard personal information data is generated. In this step, if all the personal information entered by the user meets the requirements of the set of validation sub-rules, such as the name "Zhang San" (2-10 Chinese characters), the document type "ID card" (matching the activated rule), the document number "110101199001011234" (18 digits valid), and the mobile phone number "13800138000" (11 digits valid), then the server determines that the validation is successful, generates standardized personal information data (uniform format and standardized information), stores it in the unified data storage module, and feeds back the validation result and standard personal information data to the client. The client displays a "Validation Successful" prompt and performs subsequent interactive operations according to the go parameter and returnUrl parameter to complete the personal information entry.

[0060] Step S203: If there are any non-compliant items in the personal information, a verification prompt including the non-compliant items and correction suggestions is generated and fed back to the client until the verification is successful.

[0061] In this step, if the user's entered personal information contains any discrepancies, such as the name "Zhang San 123" (containing numbers, violating name verification rules) or the ID number "11010119900101123" (only 17 digits, violating ID number verification rules), the server determines that the verification has failed and generates a verification prompt containing specific discrepancies and correction suggestions, such as "Name format incorrect, please enter 2-10 Chinese characters, excluding numbers and special characters; ID number format incorrect, please enter an 18-digit valid ID number." This prompt is then sent to the client. After receiving the verification prompt, the client displays it to the user, guiding them to correct the input errors. After the user corrects the errors, they send their personal information back to the server for verification. This process is repeated until the verification passes, generating standard personal information data.

[0062] In this way, the dual verification mechanism of front-end verification and server-side secondary verification ensures the accuracy and standardization of personal information, effectively avoiding invalid or incorrect input. When verification fails, specific non-compliance items and correction suggestions are provided, which can accurately guide users to correct errors, improving user experience and verification efficiency. After verification, standardized personal information data is generated, ensuring the uniformity of data format.

[0063] like Figure 3 As shown, in one embodiment, optionally, the method further includes: Step S301: In response to the configuration extension request for the new business scenario, establish a mapping relationship between the new business scenario parameters and the newly added configuration information; The newly added configuration information includes newly added business rule configuration information and / or newly added style configuration information.

[0064] In this embodiment, when a new business scenario (such as medical registration personal information registration) needs to be added, the administrator sends a configuration extension request for the new business scenario through the configuration management interface on the server. The request includes the identifier of the new business scenario (such as "businessScene=medical") and the newly added configuration information (new business rule configuration information and new style configuration information).

[0065] For example, based on the needs of medical registration scenarios, corresponding business rule configuration information can be added, including pre-set sets of verification sub-rules for two document types: ID card and household registration book (the ID card verification sub-rule set is consistent with the government service scenario, and the household registration book verification sub-rule set includes five verification items: name, document type, document number, registered address, and date of birth), as well as page element combination configurations (such as basic input item combinations: name, document type, document number; detailed input item combinations: add contact number, department of visit); at the same time, exclusive verification items (such as department of visit verification) can be added according to the special needs of medical scenarios, so as to realize the flexible expansion of verification rules.

[0066] For example, based on the visual needs of the medical industry, new style resource files specific to medical scenarios (such as green buttons, 13-point Microsoft YaHei font, and simple layout) can be added and stored independently in the style resource library on the server side, with the corresponding style identifier parameter "styleId=medicalStyle1" assigned. If there are special style requirements for medical scenarios, new style files can be uploaded through the file upload system to generate new style resources without modifying the front-end code.

[0067] The server responds to the configuration extension request, establishes a unique mapping relationship between the new business scenario parameter ("businessScene=medical") and the newly added configuration information (new business rule configuration information, new style configuration information), and stores it in the server's configuration storage module to ensure that when the client sends the business scenario parameter, it can accurately retrieve the corresponding configuration information.

[0068] Once the configuration extension is complete, it takes effect immediately without system deployment. When a client sends an information processing request carrying "businessScene=medical", the server can accurately retrieve the newly added configuration information based on the business scenario parameters, enabling rapid adaptation to new business scenarios without redeveloping client pages or modifying application logic code, thus significantly improving the efficiency of business expansion.

[0069] In one embodiment, optionally, the information processing request sent by the client may carry interaction control parameters, including a go parameter and a returnUrl parameter, which are used to control the page interaction after verification. After the server-side verification is completed, corresponding interaction instructions are generated according to the parsing rules of these two parameters and fed back to the client. The specific rules are as follows: The go parameter: It is used to control page closing or returning to a specific level. If the value of the go parameter is 0, it controls the client to close the current webview (applicable to scenarios such as mini-programs and web-side embedding); if the value of the go parameter is a non-zero number (such as 1, 2), it controls the client to return to the page at the corresponding level (for example, go = 1 returns to the previous page, go = 2 returns to the previous two pages); if the go parameter is not carried, it defaults to returning to the previous page.

[0070] The returnUrl parameter: It is used to specify the target page for the client to jump to. When it is necessary to jump to a specific page, the client carries the returnUrl parameter in the information processing request (such as "returnUrl= / insurance / confirm"). After the server-side verification passes, a jump instruction is generated to guide the client to jump to the target page; at the same time, parameters related to standard personal information data can be dynamically supplemented after the returnUrl parameter (such as "returnUrl= / insurance / confirm?id=123&name=张三"), where id is the unique identifier of the standard personal information data, which is convenient for the target page to obtain personal information and realizes the coherent connection of the business process.

[0071] For example, after the user completes personal information verification in the financial real-name authentication scenario, if the information processing request carries go = 0, the client closes the current webview; if it carries returnUrl= / finance / pay?id=123, the client jumps to the payment page and carries the personal information identifier for the payment page to call.

[0072] In one embodiment, optionally, the client can also send a member list query request, carrying a business scenario parameter (businessScene). After receiving the request, the server retrieves all standard personal information data added by the current user from the unified data storage module. Then, based on the target validation sub-rule set corresponding to the business scenario parameter, it validates the personal information of each member, filters out the member data that meets the validation requirements, integrates it into member list data (including core information such as member name, ID type, and ID number), and feeds it back to the client. The client renders and displays the member list. If a member's personal information does not meet the validation rules of the current business scenario (e.g., the current scenario businessScene=1, requiring 3 ID card validation items, but the member's ID card number is missing), the server excludes the member during filtering or marks the member as "unselectable" in the member list. When the user clicks on the member, the client pops up a message stating "The member's information does not meet the validation rules of the current scenario and cannot be selected."

[0073] The client page provides "Add Member," "Delete Member," and "Edit Member" buttons. When a user clicks the corresponding button, the client sends a corresponding member operation request (the add request carries the personal information to be added, the delete request carries the member's unique identifier, and the edit request carries the modified personal information). After receiving the request, the server performs the corresponding operation: when adding a member, the personal information is verified, and after successful verification, it is stored in the unified data storage module; when deleting a member, the corresponding data is deleted based on the unique identifier; when editing a member, the modified personal information is verified, and after successful verification, the data is updated. After all operations are completed, the server synchronously sends the processing results back to the client, and the client updates the member list.

[0074] Like the add member page and edit page, the member list page supports the `go` and `returnUrl` parameters. If these two parameters are included in the request, the page interaction will be executed according to the parameter rules; otherwise, it will default to returning to the previous page, conforming to the requirements in the handover document. Additionally, the "Add," "Delete," and "Edit" buttons can be hidden or shown via parameters (e.g., in a scenario where only viewing members is allowed, but modification is not, the corresponding button will be hidden).

[0075] The server performs standardized format conversion on the verified personal information data and stores it in a unified data storage module. At the same time, the client supports storing the standard personal information data locally (such as localStorage or sessionStorage on the web) to ensure that the data can be retrieved at any time.

[0076] After outputting the verified standard personal information data, the method further includes: The standard personal information data is transmitted to the target application via a data transfer adapter; The data transfer adapter is configured to automatically detect the current operating environment and, based on the detection result, invoke a data communication interface adapted to that environment to perform data transfer. The data communication interface includes at least one of the following: a mini-program framework API for a mini-program environment, a Web Storage API for a web browser environment, and an event bus or bridge communication interface for a hybrid application environment.

[0077] For example, after the personal information verification is completed on the mini-program side, standard personal information data can be transmitted to the webview embedded in the mini-program or to other related mini-programs through the built-in interface of WeChat mini-program (wx.miniProgram.postMessage), so as to realize data communication within the mini-program and between the mini-program and the webview.

[0078] For example, when a user navigates from the current application to another application, the current application stores standard personal information data in localStorage or sessionStorage. After navigating to the target application, the target application retrieves the personal information by reading the data in localStorage or sessionStorage, thus enabling cross-application data transfer without requiring the user to fill in the information repeatedly.

[0079] If local application data transfer is used, after the local application (such as PC client or mobile APP) completes the personal information verification, it will transfer the standard personal information data to other modules within the application or to the associated local application through the EventBus event listening mechanism, thereby realizing data interoperability between local applications and within the application.

[0080] By employing the aforementioned cross-application data transfer methods, we can ensure the smooth transmission of data from various channels, enabling the interoperability of personal information across multiple platforms and applications, further enhancing user experience and reducing repetitive operations.

[0081] like Figure 4 As shown, in a second aspect, embodiments of this application provide a personal information processing device 40, the device comprising: Receiving module 41 is used to receive an information processing request from a client page, wherein the information processing request includes at least business scenario parameters for identifying the target business scenario; The acquisition module 42 is used to acquire target configuration information corresponding to the target business scenario based on the business scenario parameters, and send the target configuration information to the client. The configuration information includes business rule configuration information for defining the composition and verification rules of interface elements, and style configuration information for defining the visual appearance of the interface. Processing module 43 is used to respond to receiving a user's selection instruction for a target document type on the client page, and to load and activate the corresponding target verification sub-rule set from the business rule configuration information according to the target document type, wherein the business rule configuration information pre-sets multiple verification sub-rule sets that are respectively bound to different document types; The verification module 44 is used to verify the personal information entered by the user on the client page based on the activated target verification sub-rule set, and output the verified standard personal information data.

[0082] In one embodiment, optionally, the apparatus further includes: The update module is used to update the user interface and interaction logic of the client page in real time according to the target validation sub-rule set, wherein the update includes at least one of the following: Update the list of personal information input fields that need to be filled in on the client page; Update the validation logic applied to each personal information input field; Update the prompts corresponding to each input item and validation logic.

[0083] In one embodiment, optionally, the information processing request further includes a style identifier parameter; The acquisition module is used for: Based on the business scenario parameters and the style identifier parameters, obtain the corresponding style resource file as the style configuration information; The style resource file is stored and loaded independently of the application logic code of the client page, and modifications and updates to the style resource file do not depend on the release of the application logic code.

[0084] In one embodiment, optionally, the information processing request further includes page element parameters; The acquisition module is used for: Based on the business scenario parameters and the page element parameters, obtain the business rule configuration information corresponding to the target business scenario, so as to control the client page to render the combination of personal information input items corresponding to the page element parameters.

[0085] In one embodiment, optionally, the different document types include ID cards and non-ID cards, and the corresponding verification sub-rule sets are divided into ID card verification sub-rule sets and non-ID card verification sub-rule sets; The set of ID card verification sub-rules includes at least verification items for name, document type, and document number, while the set of non-ID card verification sub-rules includes at least verification items for name, document type, document number, date of birth, and gender.

[0086] In one embodiment, optionally, the verification module includes: The receiving unit is configured to receive the personal information input by the user and the identifier of the activated target verification sub-rule set sent by the client, and to match and compare the personal information item by item according to the target verification sub-rule set; The generation unit is used to generate standard personal information data if all items of the personal information meet the verification requirements and the verification passes. The prompting unit is used to generate a verification prompt, including the non-compliance item and correction suggestions, if there are any non-compliance items in the personal information, and send it back to the client until the verification is successful.

[0087] In one embodiment, optionally, the apparatus further includes: The relationship establishment module is used to respond to configuration extension requests for new business scenarios and establish a mapping relationship between new business scenario parameters and newly added configuration information. The newly added configuration information includes newly added business rule configuration information and / or newly added style configuration information.

[0088] Thirdly, a computer device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the steps of the aforementioned personal information processing method.

[0089] Fourthly, a computer-readable storage medium is provided, which stores a computer program that, when executed by a processor, implements the steps of the aforementioned personal information processing method.

[0090] For specific limitations regarding the personal information processing device, please refer to the limitations on personal information processing methods above, which will not be repeated here. Each module in the aforementioned personal information processing device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in a computer device in hardware form, or stored in the memory of a computer device in software form, so that the processor can call and execute the operations corresponding to each module.

[0091] The software tools or components not belonging to our company that appear in the embodiments of this application are merely examples and do not represent actual use.

[0092] In one embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be as follows: Figure 5 As shown. The computer device includes a processor, memory, network interface, and database connected via a system bus. The processor provides computing and control capabilities. The memory includes non-volatile and / or volatile storage media and internal memory. The non-volatile storage media stores the operating system, computer programs, and database. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The network interface is used to communicate with external clients via a network connection. When the computer program is executed by the processor, it implements the functions or steps of a personal information processing method on the server side.

[0093] In one embodiment, a computer device is provided, which may be a client, and its internal structure diagram may be as follows: Figure 6 As shown, the computer device includes a processor, memory, network interface, display screen, and input devices connected via a system bus. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The network interface is used to communicate with an external server via a network connection. When the computer program is executed by the processor, it implements the functions or steps of a personal information processing method on the client side.

[0094] It should be understood that the processor can be a Central Processing Unit (CPU), but it can also be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. Among these, a general-purpose processor can be a microprocessor or any conventional processor.

[0095] In one embodiment, a computer device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the method described in any one of the first aspect embodiments.

[0096] It should be noted that the functions or steps that can be implemented by the computer-readable storage medium or electronic device described above can be referred to the relevant descriptions in the foregoing method embodiments. To avoid repetition, they will not be described one by one here.

[0097] It should be understood that the term "and / or" used in this article is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Additionally, the character " / " in this article generally indicates that the preceding and following related objects have an "or" relationship.

[0098] It should be understood that although the terms "first," "second," etc., may be used to describe the setting units in the embodiments of this application, these setting units should not be limited to these terms. These terms are only used to distinguish the setting units from each other. For example, without departing from the scope of the embodiments of this application, the first setting unit may also be referred to as the second setting unit, and similarly, the second setting unit may also be referred to as the first setting unit.

[0099] Depending on the context, the word "if" as used here can be interpreted as "when," "when," "in response to determination," or "in response to detection." Similarly, depending on the context, the phrase "if determination" or "if detection (of the stated condition or event)" can be interpreted as "when determination," "in response to determination," "when detection (of the stated condition or event)," or "in response to detection (of the stated condition or event)."

[0100] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0101] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or in a combination of hardware and software functional units.

[0102] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium. When executed, the computer program can include the processes of the embodiments of the above methods. Any references to memory, storage, databases, or other media used in the embodiments provided in this application can include non-volatile and / or volatile memory. Non-volatile memory may include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory may include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), dual data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), RAMbus direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), etc.

[0103] The above-described embodiments are only used to illustrate the technical solutions of the present invention, and are not intended to limit it. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention, and should all be included within the protection scope of the present invention.

Claims

1. A method for processing personal information, characterized in that, The method includes: Receive an information processing request from a client page, wherein the information processing request includes at least business scenario parameters for identifying the target business scenario; Based on the business scenario parameters, obtain the target configuration information corresponding to the target business scenario, and send the target configuration information to the client. The configuration information includes business rule configuration information for defining the composition and verification rules of interface elements, and style configuration information for defining the visual appearance of the interface. In response to receiving a user's selection instruction for a target document type on the client page, the system loads and activates the corresponding target verification sub-rule set from the business rule configuration information according to the target document type. The business rule configuration information pre-sets multiple verification sub-rule sets that are respectively bound to different document types. Based on the activated set of target verification sub-rules, the personal information entered by the user on the client page is verified, and the verified standard personal information data is output.

2. The method according to claim 1, characterized in that, After the step of loading and activating the corresponding set of target verification sub-rules from the business rule configuration information according to the target document type, the method further includes: Based on the target validation sub-rule set, the user interface and interaction logic of the client page are updated in real time, and the update includes at least one of the following: Update the list of personal information input fields that need to be filled in on the client page; Update the validation logic applied to each personal information input field; Update the prompts corresponding to each input item and validation logic.

3. The method according to claim 1, characterized in that, The information processing request also includes style identifier parameters; The step of obtaining target configuration information corresponding to the target business scenario based on the business scenario parameters includes: Based on the business scenario parameters and the style identifier parameters, the corresponding style resource file is obtained as the style configuration information.

4. The method according to claim 1, characterized in that, The information processing request also includes page element parameters; The step of obtaining target configuration information corresponding to the target business scenario based on the business scenario parameters includes: Based on the business scenario parameters and the page element parameters, obtain the business rule configuration information corresponding to the target business scenario, so as to control the client page to render the combination of personal information input items corresponding to the page element parameters.

5. The method according to claim 1, characterized in that, The business scenario parameters include the businessScene parameter. The information processing request carries the businessScene parameter through the URL of the client page. Different values ​​of the businessScene parameter correspond to different target business scenarios, and each target business scenario corresponds to unique target configuration information.

6. The method according to claim 1, characterized in that, The verification of personal information based on the target verification sub-rule set specifically includes: Receive the user's personal information and the activated target verification sub-rule set identifier sent by the client, and match and compare the personal information item by item according to the target verification sub-rule set; If all items of the personal information meet the verification requirements, the verification passes and standard personal information data is generated. If any of the personal information is inconsistent, a verification prompt including the inconsistent information and correction suggestions will be generated and sent to the client until the verification is successful.

7. The method according to claim 1, characterized in that, The method further includes: In response to configuration extension requests for new business scenarios, establish a mapping relationship between new business scenario parameters and newly added configuration information; The newly added configuration information includes newly added business rule configuration information and / or newly added style configuration information.

8. A personal information processing device, characterized in that, The device includes: A receiving module is used to receive information processing requests from a client page, wherein the information processing requests include at least business scenario parameters for identifying the target business scenario; The acquisition module is used to acquire target configuration information corresponding to the target business scenario based on the business scenario parameters, and send the target configuration information to the client. The configuration information includes business rule configuration information for defining the composition and verification rules of interface elements, and style configuration information for defining the visual appearance of the interface. The processing module is used to respond to receiving a user's selection instruction for a target document type on the client page, and to load and activate the corresponding target verification sub-rule set from the business rule configuration information according to the target document type. The business rule configuration information pre-sets multiple verification sub-rule sets that are respectively bound to different document types. The verification module is used to verify the personal information entered by the user on the client page based on the activated target verification sub-rule set, and output the verified standard personal information data.

9. A computer device, characterized in that, include: At least one processor; And, a memory communicatively connected to the at least one processor; The memory stores instructions that can be executed by the at least one processor; The instructions are configured to perform the method described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, The device stores computer-executable instructions for performing the method as described in any one of claims 1 to 7.

Images