Real name authentication processing method, electronic device and computer program product

Abstract

The invention provides a real-name authentication processing method, electronic equipment and a computer program product, and the method comprises the steps: obtaining a real-name authentication request which comprises a target business identifier of a business to be subjected to real-name authentication; a preset real-name process configuration table is called, and the real-name process configuration table comprises the corresponding relation between different service identifiers and different real-name processes; determining a target real-name process matched with the service to be subjected to real-name authentication based on a corresponding relationship in a real-name process configuration table and the target service identifier; and performing real-name authentication on the to-be-real-name authentication service based on the target real-name process. Through the target service identifier and the real-name process configuration table, real-name authentication processing can be efficiently and conveniently carried out on the to-be-real-name authentication service, so that the labor cost and the computing power cost in the real-name authentication process are reduced.

Description

Technical Field

[0001] This invention relates to the field of real-name authentication technology, and in particular to a real-name authentication processing method, electronic device, and computer program product. Background Technology

[0002] According to relevant technologies, traditional wallet real-name authentication mechanisms typically adopt a "business-driven, process-independent" architecture, meaning that for each specific business scenario (such as payment, wealth management, credit, etc.), a corresponding real-name authentication process needs to be developed and deployed independently.

[0003] While this model can meet the compliance requirements of a single business, the real-name registration processes of different businesses have a high degree of overlap in modules such as identity verification rules, data interface calls, and risk control strategy configuration, resulting in the ineffective consumption of human resources, computing power, and storage resources. Summary of the Invention

[0004] This invention provides a real-name authentication processing method, electronic device, and computer program product, which enables efficient and convenient real-name authentication processing for different business types, thereby reducing labor and computing costs in the real-name authentication process.

[0005] This invention provides a real-name authentication processing method, the method comprising: obtaining a real-name authentication request, wherein the real-name authentication request includes a target business identifier of the business to be real-name authenticated; invoking a pre-set real-name process configuration table, wherein the real-name process configuration table includes a correspondence between different business identifiers and different real-name processes; determining a target real-name process matching the business to be real-name authenticated based on the correspondence in the real-name process configuration table and the target business identifier; and performing real-name authentication on the business to be real-name authenticated based on the target real-name process.

[0006] According to a real-name authentication processing method provided by the present invention, the real-name process is composed of multiple predefined atomic capability nodes linked in a specific order, each atomic capability node providing an independent real-name authentication sub-function; the target real-name process is composed of multiple predefined target atomic capability nodes linked in a specific order, each target atomic capability node providing an independent target real-name authentication sub-function; determining the target real-name process matching the business to be real-name authenticated based on the correspondence in the real-name process configuration table and the target business identifier specifically includes: determining the target real-name process matching the business to be real-name authenticated based on the correspondence in the real-name process configuration table and the target business identifier, and the target node order formed by multiple predefined target atomic capability nodes linked in a specific order in the target real-name process; performing real-name authentication on the business to be real-name authenticated based on the target real-name process specifically includes: sequentially calling and executing the corresponding target atomic capability nodes to perform real-name authentication on the business to be real-name authenticated according to the target node order formed by multiple predefined target atomic capability nodes linked in a specific order in the target real-name process.

[0007] According to a real-name authentication processing method provided by the present invention, before determining the target real-name process matching the business to be authenticated based on the correspondence in the real-name process configuration table and the target business identifier, the method further includes: calling a preset configured interface; the step of determining the target real-name process matching the business to be authenticated based on the correspondence in the real-name process configuration table and the target business identifier specifically includes: determining the target real-name process matching the business to be authenticated based on the correspondence in the real-name process configuration table and the target business identifier through the interface.

[0008] According to a real-name authentication processing method provided by the present invention, after the target nodes are sequentially called and executed to perform real-name authentication on the service to be authenticated based on the target node order formed by multiple predefined target atomic capability nodes linked in a specific order in the target real-name process, the method further includes: recording the execution status of the target atomic capability nodes in real time based on pointer recording, and forming a real-name serial record based on the execution status, so that if the real-name authentication process is interrupted, the interrupted target atomic capability node can be determined based on the execution status of the target atomic capability nodes in the real-name serial record, and the interrupted target atomic capability node can continue to execute.

[0009] According to a real-name authentication processing method provided by the present invention, the target atomic capability node includes different types of user authentication atomic capability nodes, which are arranged in series through a linked list data structure; the step of calling and executing the corresponding target atomic capability node to perform real-name authentication for the service to be authenticated specifically includes: calling and executing different types of user authentication atomic capability nodes to perform user authentication real-name authentication for the service to be authenticated according to the chain sequence.

[0010] According to a real-name authentication processing method provided by the present invention, the step of calling and executing different types of user authentication atomic capability nodes to perform user authentication and real-name authentication on the service to be authenticated according to the chained order of the linked list specifically includes: when the user authentication atomic capability node to be executed is a first type of user authentication atomic capability node used to perform a first type of authentication verification, calling and executing the first type of user authentication atomic capability node to perform user authentication and real-name authentication on the service to be authenticated through the first type of authentication verification method; if the user authentication and real-name authentication on the service to be authenticated through the first type of authentication verification method is successful, then the user authentication and real-name authentication is completed and the subsequent target atomic capability node continues to be executed; if the user authentication and real-name authentication on the service to be authenticated through the first type of authentication verification method fails, then according to the chained order of the linked list, calling and executing a second type of user authentication atomic capability node used to perform a second type of authentication verification to perform user authentication and real-name authentication on the service to be authenticated through a second type of authentication verification method different from the first type of authentication verification method.

[0011] According to a real-name authentication processing method provided by the present invention, the method further includes: configuring an allowed number of authentication failures value for a user authentication atomic capability node based on user needs; and determining the failure of user authentication for the service to be authenticated through the first type of authentication verification method as follows: if the number of authentication failures for the service to be authenticated through the first type of authentication verification method reaches the allowed number of authentication failures value, it is determined that the user authentication for the service to be authenticated through the first type of authentication verification method has failed.

[0012] According to a real-name authentication processing method provided by the present invention, the atomic capability nodes include, in sequence, any one or more of the following: real-name verification atomic capability node, user authentication atomic capability node, card binding atomic capability node, information completion atomic capability node, file upload atomic capability node, account opening atomic capability node, and password setting atomic capability node.

[0013] The present invention also provides a real-name authentication processing device, the device comprising: an acquisition module, configured to acquire a real-name authentication request, wherein the real-name authentication request includes a target business identifier of the business to be real-name authenticated; an invocation module, configured to invoke a pre-set real-name process configuration table, wherein the real-name process configuration table includes a correspondence between different business identifiers and different real-name processes; a determination module, configured to determine a target real-name process matching the business to be real-name authenticated based on the correspondence in the real-name process configuration table and the target business identifier; and a real-name authentication module, configured to perform real-name authentication on the business to be real-name authenticated based on the target real-name process.

[0014] The present invention also provides an electronic device, 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 real-name authentication processing method as described above.

[0015] The present invention also provides a non-transitory computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the real-name authentication processing method as described above.

[0016] The present invention also provides a computer program product, including a computer program that, when executed by a processor, implements the real-name authentication processing method as described above.

[0017] This invention provides a real-name authentication processing method, electronic device, and computer program product. The method includes: obtaining a real-name authentication request, wherein the real-name authentication request includes a target business identifier for the business to be authenticated; invoking a pre-set real-name process configuration table, wherein the real-name process configuration table includes a correspondence between different business identifiers and different real-name processes; determining a target real-name process matching the business to be authenticated based on the correspondence in the real-name process configuration table and the target business identifier; and performing real-name authentication on the business to be authenticated based on the target real-name process. By using the target business identifier and the real-name process configuration table, real-name authentication of the business to be authenticated can be performed efficiently and conveniently, thereby reducing labor and computing costs in the real-name authentication process. Attached Figure Description

[0018] To more clearly illustrate the technical solutions in this invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this invention. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.

[0019] Figure 1This is a flowchart illustrating the real-name authentication processing method provided by the present invention.

[0020] Figure 2 This is a schematic diagram of the process for performing real-name authentication on the business to be authenticated based on the target real-name process provided by the present invention.

[0021] Figure 3 This is a schematic diagram of the process provided by the present invention, which calls and executes different types of user authentication atomic capability nodes in the chained order of the linked list to perform user authentication and real-name authentication for the service to be real-name authenticated.

[0022] Figure 4 This is a schematic diagram of the real-name authentication processing device provided by the present invention.

[0023] Figure 5 This is a schematic diagram of the structure of the electronic device provided by the present invention. Detailed Implementation

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

[0025] The real-name authentication method provided by this invention can be applied to online service platforms (such as e-commerce, financial services, or social platforms), which need to adopt different real-name authentication processes according to different business types. For ease of explanation, the example of a financial service business to be authenticated will be used.

[0026] Figure 1 This is a flowchart illustrating the real-name authentication processing method provided by the present invention.

[0027] The following will combine Figure 1 The process of the real-name authentication method provided by this invention will be described.

[0028] In an exemplary embodiment of the present invention, combined with Figure 1 As can be seen, the real-name authentication process may include steps 110 to 140, and each step will be described below.

[0029] In step 110, a real-name authentication request is obtained, wherein the real-name authentication request includes the target business identifier of the business to be real-name authenticated.

[0030] In one embodiment, a user can initiate a real-name authentication request through the platform client. For example, when applying for financial services, the client can generate a real-name authentication request. This request includes a target service identifier for the service to be authenticated, which can be used to uniquely identify the service to be authenticated. During application, the platform server can receive the real-name authentication request and parse out the target service identifier.

[0031] In step 120, a pre-set real-name process configuration table is invoked, which includes the correspondence between different business identifiers and different real-name processes.

[0032] In one embodiment, the platform server can call a pre-set real-name process configuration table from a database or configuration file according to the real-name authentication request. The real-name process configuration table can be stored in key-value pair form, where the key is the business identifier and the value is the corresponding real-name process.

[0033] It should be noted that the name process configuration table is dynamic and updatable. For example, administrators can add new business identifiers and corresponding real-name processes through the management interface without modifying the code.

[0034] In step 130, based on the correspondence in the real-name process configuration table and the target business identifier, the target real-name process that matches the business to be real-name authenticated is determined.

[0035] In step 140, real-name authentication is performed on the business to be authenticated based on the target real-name process.

[0036] In one embodiment, the corresponding target real-name authentication process can be queried and matched based on the correspondence in the real-name authentication process configuration table and the target business identifier. Furthermore, based on the target real-name authentication process, real-name authentication is performed on the business to be authenticated.

[0037] In this embodiment, by using the target business identifier and the real-name authentication process configuration table, it is possible to quickly adapt to different business needs, support multiple real-name authentication processes, and avoid the limitations caused by hard coding. In addition, by using the real-name authentication process configuration table, the business identifier and the real-name authentication process are decoupled, so that when adding or modifying a business, only the configuration table needs to be updated without modifying the core code, thus reducing development and maintenance costs.

[0038] The real-name authentication processing method provided by this invention includes: obtaining a real-name authentication request, wherein the real-name authentication request includes a target business identifier of the business to be real-name authenticated; calling a pre-set real-name process configuration table, wherein the real-name process configuration table includes the correspondence between different business identifiers and different real-name processes; determining a target real-name process matching the business to be real-name authenticated based on the correspondence in the real-name process configuration table and the target business identifier; and performing real-name authentication on the business to be real-name authenticated based on the target real-name process. By using the target business identifier and the real-name process configuration table, real-name authentication of the business to be real-name authenticated can be performed efficiently and conveniently, thereby reducing labor and computing costs during the real-name authentication process.

[0039] Figure 2 This is a schematic diagram of the process for performing real-name authentication on the business to be authenticated based on the target real-name process provided by the present invention.

[0040] The following will combine Figure 2 The present invention describes the process of performing real-name authentication on the business to be authenticated based on the target real-name process.

[0041] In an exemplary embodiment of the present invention, the real-name process can be composed of multiple predefined atomic capability nodes linked in a specific order, and each atomic capability node provides an independent real-name authentication sub-function; the target real-name process can be composed of multiple predefined target atomic capability nodes linked in a specific order, and each target atomic capability node provides an independent target real-name authentication sub-function.

[0042] Combination Figure 2 As can be seen, based on the target real-name process, performing real-name authentication on the business to be real-name authenticated may include steps 210 and 220, which will be described in detail below.

[0043] In step 210, based on the correspondence in the real-name process configuration table and the target business identifier, the target real-name process matching the business to be real-name authenticated is determined, as well as the target node sequence formed by linking multiple predefined target atomic capability nodes in a specific order in the target real-name process.

[0044] In one embodiment, a series of atomic capability nodes can be predefined, wherein each node encapsulates an independent, reusable real-name authentication sub-function.

[0045] In another exemplary embodiment of the present invention, the atomic capability nodes may, in sequence, include any one or more of the following: real-name verification atomic capability node, user authentication atomic capability node, card binding atomic capability node, information completion atomic capability node, file upload atomic capability node, account opening atomic capability node, and password setting atomic capability node.

[0046] Atomic capability nodes can also provide extended access to capabilities. For example, information completion atomic capability nodes can access extended capabilities such as manual user input, OCR recognition, and NFC recognition.

[0047] In another embodiment, the real-name registration process configuration table not only records the correspondence between business identifiers and real-name registration processes, but also records the sequence of atomic capability nodes included in each real-name registration process and their execution order. During application, while determining the target real-name registration process based on the real-name registration process configuration table and the target business identifier, the sequence of target nodes constituting the process—formed by linking multiple predefined target atomic capability nodes in a specific order—can be further parsed. That is, it not only knows which target real-name registration process to execute, but also precisely knows which atomic nodes need to be executed sequentially, and their order.

[0048] In step 220, according to the target node order formed by linking multiple predefined target atomic capability nodes in a specific order in the target real-name process, the corresponding target atomic capability nodes are called and executed sequentially to perform real-name authentication on the business to be authenticated.

[0049] In another embodiment, the target atomic capability nodes can be sequentially called and executed according to the target node order formed by linking multiple predefined target atomic capability nodes in a specific order in the target real-name authentication process. During application, if the atomic capability nodes include, in a specific order, the following atomic capability nodes: real-name verification atomic capability node, user authentication atomic capability node, card binding atomic capability node, information completion atomic capability node, file upload atomic capability node, account opening atomic capability node, and password setting atomic capability node, then during the real-name verification process, these atomic capability nodes need to be executed sequentially to complete the real-name verification process. The execution result (success / failure and output data) of each node will serve as the input for subsequent nodes or the basis for judging the entire process. Only when all target atomic capability nodes are successfully executed in sequence can the real-name authentication be considered ultimately successful.

[0050] In this embodiment, by breaking down the complex real-name authentication process into independent atomic capability nodes, new real-name authentication processes that adapt to different business security levels and scenario requirements can be quickly constructed by freely combining and sorting nodes, without developing any new code. In addition, since the function of each node is independent, modifying, upgrading or replacing a node will not affect the normal operation of other nodes, greatly improving the maintainability of the system.

[0051] In an exemplary embodiment of the present invention, the following description continues using the previously described embodiments as examples. Before determining the target real-name authentication process (corresponding to step 130) that matches the business to be real-name authenticated based on the correspondence in the real-name process configuration table and the target business identifier, the real-name authentication processing method may further include the following steps: Call the pre-configured interface; Based on the correspondence in the real-name authentication process configuration table and the target business identifier, the target real-name authentication process matching the business to be authenticated (corresponding to step 130) can be determined in the following ways: By using the interface, based on the corresponding relationship in the real-name process configuration table and the target business identifier, the target real-name process that matches the business to be real-name authenticated is determined.

[0052] In one embodiment, a pre-configured interface can be invoked. Further, the interface internally receives and processes query requests, and determines the target real-name authentication process matching the business to be authenticated based on the target business identifier and the corresponding relationship in the queried real-name process configuration table. In this embodiment, the query logic for real-name process configuration data is encapsulated in an independent interface, achieving decoupling between the core business processing logic and data access details, resulting in a higher degree of platform modularity and clearer division of responsibilities.

[0053] In yet another exemplary embodiment of the present invention, the following description continues using the previously described embodiments as examples. After sequentially calling and executing the corresponding target atomic capability nodes to perform real-name authentication on the business to be authenticated, based on the target node order formed by linking multiple predefined target atomic capability nodes in a specific order in the target real-name process, the real-name authentication processing method may further include the following steps: Based on pointer recording, the execution status of the target atomic capability node is recorded in real time, and a real-name serial record is formed based on the execution status. This enables the interrupted target atomic capability node to be identified based on the execution status of the target atomic capability node in the real-name serial record after the real-name authentication process is interrupted, and the interrupted target atomic capability node to continue execution.

[0054] In one embodiment, the pointer record can be considered a state recording mechanism used to identify the current execution position. The specific position of this pointer (i.e., the identifier of the currently executed atomic capability node) will be recorded in real time in the real-name log. The pointer record can be updated when the target real-name process is started, after each atomic capability node is successfully executed, or after execution failure.

[0055] In another embodiment, a real-name authentication record can be created. During application, the status field of the target atomic capability node is updated in real time based on the real-name authentication record. This field accurately identifies which target atomic capability node the current process has reached and its execution status (success or failure), thus forming a complete, continuous, and traceable real-name authentication record. This record completely depicts the execution trajectory of the authentication process. Because the real-name authentication record records the execution status of the target atomic capability node, after the real-name authentication process is interrupted, the interrupted target atomic capability node can be determined based on the execution status of the target atomic capability node in the real-name authentication record, and the interrupted target atomic capability node can continue execution. This embodiment solves the pain point of having to start authentication from the beginning after the process is interrupted due to network fluctuations, application anomalies, or user voluntary exit. Users can continue to complete authentication from the breakpoint, avoiding repeated operations. This advantage is particularly significant in long processes, directly improving user satisfaction and authentication completion rate.

[0056] In another embodiment, the target real-name process adopts a linked list data structure, which can connect different atomic nodes. There are pointers between nodes, and the snapshot information of the linked list execution is recorded. In this way, if the user exits at any time and re-enters the real-name process, the previous nodes will not be executed repeatedly, thus ensuring the orderliness of the unified real-name process.

[0057] In yet another exemplary embodiment of the present invention, the target atomic capability node may include different types of user authentication atomic capability nodes, which are arranged in series using a linked list data structure; wherein, calling and executing the corresponding target atomic capability node to perform real-name authentication for the pending real-name authentication business can be implemented in the following manner: Following the chained order, different types of user authentication atomic capability nodes are called and executed to perform user authentication and real-name authentication for the pending real-name authentication business.

[0058] In one embodiment, the target atomic capability node may include different types of user authentication atomic capability nodes, such as facial recognition user authentication atomic capability nodes, bank card verification user authentication atomic capability nodes, and mobile phone number authentication user authentication atomic capability nodes. These different types of user authentication atomic capability nodes are not simply listed, but are arranged in a linked list data structure. For example, their linked order is: facial recognition user authentication atomic capability node, bank card verification user authentication atomic capability node, and mobile phone number authentication user authentication atomic capability node.

[0059] Furthermore, during the authentication process, different types of user authentication atomic capability nodes can be called and executed starting from the first node pointed to by the head pointer, according to the chained order of the linked list, thereby realizing user authentication and real-name authentication for the real-name authentication business.

[0060] Figure 3 This is a schematic diagram of the process provided by the present invention, which calls and executes different types of user authentication atomic capability nodes in the chained order of the linked list to perform user authentication and real-name authentication for the service to be real-name authenticated.

[0061] The following will combine Figure 3 The process of calling and executing different types of user authentication atomic capability nodes to perform user authentication and real-name authentication for the service to be real-name authenticated, according to the chained order of the linked list, is described.

[0062] In an exemplary embodiment of the present invention, combined with Figure 3 As can be seen, according to the chained order, calling and executing different types of user authentication atomic capability nodes to perform user authentication and real-name authentication for the business to be real-name authenticated may include steps 310 to 330, which will be described in detail below.

[0063] In step 310, if the currently required user authentication atomic capability node is a first-type user authentication atomic capability node used for performing first-type authentication verification, the first-type user authentication atomic capability node is invoked and executed to perform user authentication and real-name authentication for the service to be authenticated through the first-type authentication verification method. In one embodiment, if the currently required user authentication atomic capability node is a first-type user authentication atomic capability node used for performing first-type authentication verification, the first-type user authentication atomic capability node can be invoked and executed, thereby performing user authentication and real-name authentication for the service to be authenticated according to the first-type authentication verification method (e.g., the corresponding face recognition user authentication atomic capability node). If the node executes successfully, authentication is passed, and the process can end normally or continue to execute subsequent nodes. If the node executes unsuccessfully (e.g., insufficient face similarity), the second-type user authentication atomic capability node for second-type authentication verification is invoked to perform user authentication and real-name authentication for the service to be authenticated through the second-type authentication verification method, which is different from the first-type authentication verification method.

[0064] In step 320, if the user authentication and real-name authentication of the service to be real-name authenticated is successful through the first type of authentication verification method, then the user authentication and real-name authentication is completed and the subsequent target atomic capability nodes are executed.

[0065] In step 330, if the user authentication and real-name authentication of the business to be real-name authenticated fails through the first type of authentication verification method, then according to the chain sequence, the second type of user authentication atomic capability node for performing the second type of authentication verification is called and executed, so as to perform user authentication and real-name authentication of the business to be real-name authenticated through the second type of authentication verification method, which is different from the first type of authentication verification method.

[0066] In one embodiment, if the user authentication and real-name authentication for the real-name authentication business is successful through the first type of authentication verification method, the authentication is passed, and the process can end normally or continue to execute subsequent nodes, that is, complete the user authentication and real-name authentication and continue to execute the subsequent target atomic capability nodes.

[0067] In another embodiment, if the user authentication for the business to be authenticated fails using the first type of authentication verification method, the system will not deem the entire authentication process a failure. During application, the system can call and execute the second type of user authentication atomic capability node for performing the second type of authentication verification according to the chained order. This allows for user authentication for the business to be authenticated using a second type of authentication verification method (e.g., the corresponding bank card verification user authentication atomic capability node), which differs from the first type of authentication verification method. Furthermore, the system can comprehensively judge or continue attempting to complete the current authentication based on the execution result of this subsequent node.

[0068] In this embodiment, the pain point of a single point of failure in the traditional linear process, which leads to the failure of the entire authentication process, is solved. When a certain authentication method (such as facial recognition) temporarily fails due to lighting or angle issues, the system provides alternative authentication paths of different types (such as bank card verification), thereby providing users with more opportunities to complete authentication and directly improving the overall real-name authentication pass rate of the business.

[0069] In yet another exemplary embodiment of the present invention, the real-name authentication processing method may further include the following steps: Based on user needs, configure the allowed number of authentication failures for the user's authentication atomic capability node; If the user authentication and real-name authentication of the service to be real-name authenticated fails using the first type of authentication verification method, the following methods can be used to determine this: If the number of failed authentication attempts for real-name authentication using the first type of authentication method reaches the allowed number of failed authentication attempts, then the real-name authentication attempt for real-name authentication using the first type of authentication method is deemed to have failed.

[0070] In one embodiment, before the process execution, a failure count threshold, i.e., the allowed number of authentication failures, can be loaded and initialized for each node. Furthermore, when execution reaches a first-type user authentication atomic capability node (e.g., a face recognition user authentication atomic capability node) used for performing first-type authentication verification, the user's initial verification may fail. In this case, the system will not immediately determine that the node's authentication has failed and jump to subsequent nodes, but will instead check whether the verification failure has reached the preset allowed number of authentication failures for that node.

[0071] If the current number of failures (e.g., 1 time) does not reach the threshold (3 times), the system will guide the user to retry the current node (e.g., re-perform face comparison) and accumulate the number of failures. Only when the number of consecutive or accumulated verification failures reaches or exceeds the preset allowed number of authentication failures (the 3rd attempt also fails) will the system finally determine that the user authentication for the real-name authentication business has failed using the first type of authentication verification method. Once the node is determined to have failed, the system will trigger subsequent logic, calling and executing the second type of user authentication atomic capability node for performing the second type of authentication verification according to the chain sequence, so as to perform user authentication for the real-name authentication business using the second type of authentication verification method, which is different from the first type of authentication verification method.

[0072] In this embodiment, a distinction is effectively made between transient and accidental failures (such as a user not holding their ID card securely the first time or an unnatural facial expression) and persistent and fundamental failures (such as incorrect ID information or an operation not performed by the user). For the former, the system provides the user with a valuable retry opportunity, avoiding a one-time operational error that directly leads to process degradation or the use of alternative solutions. This makes the authentication process more tolerant of minor, temporary user errors, greatly improving the user experience.

[0073] As described above, the real-name authentication processing method provided by this invention subdivides the real-name process into different atomic capability nodes, and orchestrates different atomic capability nodes according to business requirements. This better meets business needs and provides support for multiple authentication types, with degradeable configuration, higher real-name authentication pass rate, faster access efficiency, and more flexible capability support. The highly modular design enables flexible business adaptation capabilities, reduces maintenance complexity, simplifies the access process for new services, and improves the real-name authentication pass rate.

[0074] The real-name authentication processing device provided by the present invention is described below. The real-name authentication processing device described below can be referred to in correspondence with the real-name authentication processing method described above.

[0075] Figure 4 This is a schematic diagram of the real-name authentication processing device provided by the present invention.

[0076] The following will combine Figure 4 The structure of the real-name authentication processing device provided by the present invention will be described.

[0077] In an exemplary embodiment of the present invention, combined with Figure 4 As can be seen, the real-name authentication processing device may include an acquisition module 410, a calling module 420, a determination module 430, and a real-name module 440. Each module will be described in detail below.

[0078] The acquisition module 410 can be configured to acquire a real-name authentication request, wherein the real-name authentication request includes the target business identifier of the business to be real-name authenticated. The calling module 420 can be configured to call a pre-set real-name process configuration table, wherein the real-name process configuration table includes the correspondence between different business identifiers and different real-name processes; The determination module 430 can be configured to determine a target real-name process that matches the business to be real-name authenticated based on the correspondence in the real-name process configuration table and the target business identifier. The real-name module 440 can be configured to perform real-name authentication on the business to be real-name authenticated based on the target real-name process.

[0079] In an exemplary embodiment of the present invention, the real-name process is composed of multiple predefined atomic capability nodes linked in a specific order, and each atomic capability node provides an independent real-name authentication sub-function; the target real-name process is composed of multiple predefined target atomic capability nodes linked in a specific order, and each target atomic capability node provides an independent target real-name authentication sub-function. The determination module 430 can determine the target real-name process that matches the business to be real-name authenticated based on the correspondence in the real-name process configuration table and the target business identifier in the following way: Based on the correspondence in the real-name process configuration table and the target business identifier, determine the target real-name process that matches the business to be real-name authenticated, and the target node order formed by linking multiple predefined target atomic capability nodes in a specific order in the target real-name process; The real-name module 440 can perform real-name authentication on the business to be authenticated based on the target real-name process in the following ways: Based on the target node order formed by linking multiple predefined target atomic capability nodes in a specific order in the target real-name process, the corresponding target atomic capability nodes are called and executed sequentially to perform real-name authentication on the business to be authenticated.

[0080] In an exemplary embodiment of the present invention, the determining module 430 may further be configured to: Call the pre-configured interface; The determination module 430 can determine the target real-name process that matches the business to be real-name authenticated based on the correspondence in the real-name process configuration table and the target business identifier in the following way: Through the interface, based on the correspondence in the real-name process configuration table and the target business identifier, a target real-name process matching the business to be real-name authenticated is determined.

[0081] In an exemplary embodiment of the present invention, the real-name module 440 can also be configured to: Based on pointer recording, the execution status of the target atomic capability node is recorded in real time, and a real-name serial record is formed based on the execution status. This enables the interrupted target atomic capability node to be identified based on the execution status of the target atomic capability node in the real-name serial record after the real-name authentication process is interrupted, and the interrupted target atomic capability node to continue execution.

[0082] In an exemplary embodiment of the present invention, the target atomic capability node includes different types of user authentication atomic capability nodes, and the different types of user authentication atomic capability nodes are arranged in series through a linked list data structure; The real-name module 440 can invoke and execute the corresponding target atomic capability node to perform real-name authentication for the service to be authenticated in the following ways: Following the chained order, different types of user authentication atomic capability nodes are called and executed to perform user authentication and real-name authentication for the service to be authenticated.

[0083] In an exemplary embodiment of the present invention, the real-name module 440 can perform user authentication and real-name authentication for the service to be authenticated by calling and executing different types of user authentication atomic capability nodes in the order of the linked list according to the chain sequence: When the user authentication atomic capability node that needs to be executed is the first type of user authentication atomic capability node used to perform the first type of authentication verification, the first type of user authentication atomic capability node is invoked and executed to perform user authentication and real-name authentication for the real-name authentication service through the first type of authentication verification method. If the user authentication and real-name authentication of the business to be real-name authenticated is successful through the first type of authentication verification method, the user authentication and real-name authentication is completed and the subsequent target atomic capability nodes are executed. If the user authentication and real-name authentication of the business to be real-name authenticated fails through the first type of authentication verification method, then according to the chain sequence, the second type of user authentication atomic capability node for performing the second type of authentication verification is called and executed, so as to perform user authentication and real-name authentication of the business to be real-name authenticated through the second type of authentication verification method, which is different from the first type of authentication verification method.

[0084] In an exemplary embodiment of the present invention, the real-name module 440 can also be configured to: Based on user needs, configure the allowed number of authentication failures for the user's authentication atomic capability node; The real-name module 440 can implement user authentication for the service to be authenticated through the first type of authentication verification method in the following way: Real-name authentication failure. If the number of failed authentication attempts for the user authentication and real-name authentication of the service to be authenticated through the first type of authentication verification method reaches the allowed number of authentication failures, it is determined that the user authentication and real-name authentication of the service to be authenticated through the first type of authentication verification method has failed.

[0085] In an exemplary embodiment of the present invention, the atomic capability nodes include, in sequence, any one or more of the following: real-name verification atomic capability node, user authentication atomic capability node, card binding atomic capability node, information completion atomic capability node, file upload atomic capability node, account opening atomic capability node, and password setting atomic capability node.

[0086] Figure 5 An example is a schematic diagram of the physical structure of an electronic device, such as... Figure 5 As shown, the electronic device may include a processor 510, a communications interface 520, a memory 530, and a communication bus 540, wherein the processor 510, communications interface 520, and memory 530 communicate with each other via the communication bus 540. The processor 510 can call logical instructions in the memory 530 to execute a real-name authentication processing method. This method includes: obtaining a real-name authentication request, wherein the real-name authentication request includes a target service identifier for the service to be authenticated; calling a pre-set real-name process configuration table, wherein the real-name process configuration table includes a correspondence between different service identifiers and different real-name processes; determining a target real-name process matching the service to be authenticated based on the correspondence in the real-name process configuration table and the target service identifier; and performing real-name authentication on the service to be authenticated based on the target real-name process.

[0087] Furthermore, the logical instructions in the aforementioned memory 530 can be implemented as software functional units and, when sold or used as independent products, can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0088] On the other hand, the present invention also provides a computer program product, which includes a computer program that can be stored on a non-transitory computer-readable storage medium. When the computer program is executed by a processor, the computer can execute the real-name authentication processing method provided by the above methods. The method includes: obtaining a real-name authentication request, wherein the real-name authentication request includes a target business identifier of the business to be real-name authenticated; calling a pre-set real-name process configuration table, wherein the real-name process configuration table includes a correspondence between different business identifiers and different real-name processes; determining a target real-name process matching the business to be real-name authenticated based on the correspondence in the real-name process configuration table and the target business identifier; and performing real-name authentication on the business to be real-name authenticated based on the target real-name process.

[0089] In another aspect, the present invention also provides a non-transitory computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the real-name authentication processing method provided by the above methods. The method includes: obtaining a real-name authentication request, wherein the real-name authentication request includes a target service identifier for the service to be authenticated; invoking a pre-set real-name process configuration table, wherein the real-name process configuration table includes a correspondence between different service identifiers and different real-name processes; determining a target real-name process matching the service to be authenticated based on the correspondence in the real-name process configuration table and the target service identifier; and performing real-name authentication on the service to be authenticated based on the target real-name process.

[0090] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without any creative effort.

[0091] Through the above description of the embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus necessary general-purpose hardware platforms, and of course, it can also be implemented by hardware. Based on this understanding, the above technical solutions, in essence or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in the various embodiments or some parts of the embodiments.

[0092] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and not to limit them; 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; and these 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.

Claims

1. A real name authentication processing method characterized by comprising: The method includes: Obtain a real-name authentication request, wherein the real-name authentication request includes the target business identifier of the business to be real-name authenticated; Call the pre-set real-name process configuration table, wherein the real-name process configuration table includes the correspondence between different business identifiers and different real-name processes; Based on the correspondence in the real-name process configuration table and the target business identifier, determine the target real-name process that matches the business to be real-name authenticated; Based on the target real-name process, real-name authentication is performed on the business to be real-name authenticated.

2. The real-name authentication processing method according to claim 1, characterized by, The real-name authentication process consists of multiple predefined atomic capability nodes linked in a specific order, with each atomic capability node providing an independent real-name authentication sub-function; the target real-name authentication process consists of multiple predefined target atomic capability nodes linked in a specific order, with each target atomic capability node providing an independent target real-name authentication sub-function. The step of determining the target real-name authentication process matching the business to be authenticated based on the correspondence in the real-name authentication process configuration table and the target business identifier specifically includes: Based on the correspondence in the real-name process configuration table and the target business identifier, determine the target real-name process that matches the business to be real-name authenticated, and the target node order formed by linking multiple predefined target atomic capability nodes in a specific order in the target real-name process; The step of performing real-name authentication on the business to be authenticated based on the target real-name process specifically includes: Based on the target node order formed by linking multiple predefined target atomic capability nodes in a specific order in the target real-name process, the corresponding target atomic capability nodes are called and executed sequentially to perform real-name authentication on the business to be authenticated.

3. The real-name authentication processing method according to claim 1 or 2, characterized by, Before determining the target real-name authentication process matching the business to be authenticated based on the correspondence in the real-name authentication process configuration table and the target business identifier, the method further includes: Call the pre-configured interface; The step of determining the target real-name authentication process matching the business to be authenticated based on the correspondence in the real-name authentication process configuration table and the target business identifier specifically includes: Through the interface, based on the correspondence in the real-name process configuration table and the target business identifier, a target real-name process matching the business to be real-name authenticated is determined.

4. The real-name authentication processing method according to claim 2, characterized by, After the method proceeds by sequentially calling and executing the corresponding target atomic capability nodes to perform real-name authentication on the service to be authenticated, based on the target node order formed by linking multiple predefined target atomic capability nodes in a specific order during the target real-name process, the method further includes: Based on pointer recording, the execution status of the target atomic capability node is recorded in real time, and a real-name serial record is formed based on the execution status. This enables the interrupted target atomic capability node to be identified based on the execution status of the target atomic capability node in the real-name serial record after the real-name authentication process is interrupted, and the interrupted target atomic capability node to continue execution.

5. The real-name authentication processing method according to claim 2, characterized by, The target atomic capability nodes include different types of user authentication atomic capability nodes, which are arranged in series using a linked list data structure; the step of calling and executing the corresponding target atomic capability node to perform real-name authentication for the service to be authenticated specifically includes: Following the chained order, different types of user authentication atomic capability nodes are called and executed to perform user authentication and real-name authentication for the service to be real-name authenticated.

6. The real-name authentication processing method according to claim 5, characterized by, The process of calling and executing different types of user authentication atomic capability nodes to perform user authentication and real-name authentication for the service to be authenticated, according to the chained order, specifically includes: When the user authentication atomic capability node that needs to be executed is the first type of user authentication atomic capability node used to perform the first type of authentication verification, the first type of user authentication atomic capability node is invoked and executed to perform user authentication and real-name authentication for the real-name authentication service through the first type of authentication verification method. If the user authentication and real-name authentication of the business to be real-name authenticated is successful through the first type of authentication verification method, the user authentication and real-name authentication is completed and the subsequent target atomic capability nodes are executed. If the user authentication and real-name authentication of the business to be real-name authenticated fails through the first type of authentication verification method, then according to the chain sequence, the second type of user authentication atomic capability node for performing the second type of authentication verification is called and executed, so as to perform user authentication and real-name authentication of the business to be real-name authenticated through the second type of authentication verification method, which is different from the first type of authentication verification method.

7. The real-name authentication processing method according to claim 6, characterized by, The method further includes: Based on user needs, configure the allowed number of authentication failures for the user's authentication atomic capability node; If the user authentication and real-name authentication of the service to be real-name authenticated fails using the first type of authentication verification method, the following method shall be used to determine the failure: If the number of failed authentication attempts for the user authentication and real-name authentication of the service to be authenticated through the first type of authentication verification method reaches the allowed number of authentication failures, it is determined that the user authentication and real-name authentication of the service to be authenticated through the first type of authentication verification method has failed.

8. The real-name authentication processing method according to claim 2, characterized by, The atomic capability nodes, in sequence, include any one or more of the following: real-name verification atomic capability node, user authentication atomic capability node, card binding atomic capability node, information completion atomic capability node, file upload atomic capability node, account opening atomic capability node, and password setting atomic capability node.

9. An electronic device comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the real-name authentication processing method as described in any one of claims 1 to 8.

10. A computer program product comprising a computer program, characterized in that, When the computer program is executed by the processor, it implements the real-name authentication processing method as described in any one of claims 1 to 8.

Images