CN113283983A - Service processing method, device and equipment - Google Patents

Service processing method, device and equipment Download PDF

Info

Publication number
CN113283983A
CN113283983A CN202110656583.3A CN202110656583A CN113283983A CN 113283983 A CN113283983 A CN 113283983A CN 202110656583 A CN202110656583 A CN 202110656583A CN 113283983 A CN113283983 A CN 113283983A
Authority
CN
China
Prior art keywords
user
verification
dependency chain
verification result
dependency
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202110656583.3A
Other languages
Chinese (zh)
Inventor
邵猛
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Agricultural Bank of China
Original Assignee
Agricultural Bank of China
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Agricultural Bank of China filed Critical Agricultural Bank of China
Priority to CN202110656583.3A priority Critical patent/CN113283983A/en
Publication of CN113283983A publication Critical patent/CN113283983A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/02Banking, e.g. interest calculation or account maintenance
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/30Authentication, i.e. establishing the identity or authorisation of security principals
    • G06F21/31User authentication

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • Computer Security & Cryptography (AREA)
  • Finance (AREA)
  • General Physics & Mathematics (AREA)
  • Accounting & Taxation (AREA)
  • Computer Hardware Design (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Development Economics (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Strategic Management (AREA)
  • Technology Law (AREA)
  • General Business, Economics & Management (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)

Abstract

The embodiment of the application provides a service processing method, a device and equipment, wherein the method comprises the following steps: receiving a service processing request, wherein the service processing request comprises an identifier of a service to be requested and a plurality of user characteristics; determining at least one dependency chain in the plurality of user characteristics, wherein the dependency chain comprises at least two user characteristics with dependency relationship, and a previous user characteristic in the dependency chain depends on a next user characteristic; determining a verification logic corresponding to each dependency chain; aiming at any dependency chain, determining a verification result corresponding to the dependency chain according to the dependency relationship among the user characteristics in the dependency chain and the verification logic corresponding to the dependency chain; and determining the verification results corresponding to the plurality of user characteristics according to the verification result corresponding to each dependency chain, and performing service processing on the service to be requested according to the verification results corresponding to the plurality of user characteristics. And the efficiency of service processing is improved.

Description

Service processing method, device and equipment
Technical Field
The present application relates to the field of financial technologies, and in particular, to a method, an apparatus, and a device for processing a service.
Background
A company's business system may recommend new products to different types of customers. For example, a bank may recommend to a teacher financial products that the teacher may purchase.
At present, when a business system determines whether a user can purchase a corresponding product, the business system can verify each user information of the user according to a product limiting condition, and when all user information is verified, it is determined that the user can purchase a new product. For example, if the bank's financial product is limited to teachers and is less than 40 years old, the user may purchase the financial product when both the user's professional information and age information are verified. However, as products are diversified, the number of restrictions on the products increases, and if the user information is verified for each restriction, the efficiency of the business process is low.
Disclosure of Invention
The embodiment of the application provides a service processing method, a service processing device and service processing equipment, which are used for solving the technical problem that the service processing efficiency is low in the prior art.
In a first aspect, the present application provides a service processing method, including:
receiving a service processing request, wherein the service processing request comprises an identifier of a service to be requested and a plurality of user characteristics;
determining at least one dependency chain in the plurality of user characteristics, wherein the dependency chain comprises at least two user characteristics with dependency relationship, and a previous user characteristic in the dependency chain depends on a next user characteristic;
determining a verification logic corresponding to each dependency chain, wherein the verification logic is used for indicating a logic relationship between a verification result corresponding to the dependency chain and a verification result corresponding to each user feature in the dependency chain;
aiming at any dependency chain, determining a verification result corresponding to the dependency chain according to the dependency relationship among the user characteristics in the dependency chain and the verification logic corresponding to the dependency chain;
and determining the verification results corresponding to the plurality of user characteristics according to the verification result corresponding to each dependency chain, and performing service processing on the service to be requested according to the verification results corresponding to the plurality of user characteristics.
In a possible implementation manner, determining a verification result corresponding to the dependency chain according to the dependency relationship between the user features in the dependency chain and the verification logic corresponding to the dependency chain includes:
determining a first user characteristic in the dependency chain, the first user characteristic not being dependent on other user characteristics in the dependency chain than the first user characteristic;
determining a first verification result corresponding to the first user characteristic;
and determining a verification result corresponding to the dependency chain according to the verification logic and the first verification result.
In one possible implementation, the verification logic is a first verification logic that is: if any user feature in the dependency chain is successfully verified, the dependency chain is successfully verified;
determining a verification result corresponding to the dependency chain according to the verification logic and the first verification result, including:
if the first verification result is successful, determining that the verification result corresponding to the dependency chain is successful;
and if the first verification result is verification failure, verifying other user characteristics except the first user characteristic in the dependency chain according to the first verification result to obtain a verification result corresponding to the dependency chain.
In a possible implementation manner, verifying the user characteristics other than the first user characteristic in the dependency chain to obtain a verification result corresponding to the dependency chain includes:
verifying the (N-i) th user feature in the dependency chain according to the dependency relationship in the dependency chain to obtain a verification result corresponding to the (N-i) th user feature, wherein N is the number of the user features included in the dependency chain;
and i sequentially takes 1, 2 and … …, and the verification result corresponding to the dependency chain is determined to be successful when the verification result corresponding to the (N-i) th user characteristic is successful, or the verification result corresponding to the dependency chain is determined to be failed until the verification result corresponding to the first user characteristic in the dependency chain is failed.
In one possible implementation, the verification logic is a second verification logic, and the second verification logic is: if all the user features in the dependency chain are verified successfully, the dependency chain is verified successfully;
determining a verification result corresponding to the dependency chain according to the verification logic and the first verification result, including:
if the first verification result is successful, verifying other user characteristics except the first user characteristic in the dependency chain according to the first verification result to obtain a verification result corresponding to the dependency chain;
and if the first verification result is verification failure, determining that the verification result corresponding to the dependency chain is verification failure.
In a possible implementation manner, verifying the user characteristics other than the first user characteristic in the dependency chain to obtain a verification result corresponding to the dependency chain includes:
verifying the (N-i) th user feature in the dependency chain according to the dependency relationship in the dependency chain to obtain a verification result corresponding to the (N-i) th user feature, wherein N is the number of the user features included in the dependency chain;
and i sequentially takes 1, 2 and … …, and the verification result corresponding to the dependency chain is determined to be verification failure until the verification result corresponding to the (N-i) th user feature is verification failure, or the verification result corresponding to the dependency chain is determined to be verification success until the verification result corresponding to the first user feature in the dependency chain is verification success.
In a possible implementation manner, determining the verification result corresponding to the plurality of user features according to the verification result corresponding to each dependency chain includes:
judging whether an independent user characteristic exists in the user characteristics, wherein the independent user characteristic does not exist a dependency relationship with other user characteristics in the user characteristics;
if yes, determining a verification result corresponding to the independent user features, and determining verification results corresponding to the plurality of user features according to the verification result corresponding to the independent user features and the verification result corresponding to each dependency chain;
if not, determining that the verification results corresponding to the multiple user characteristics are successful when the verification results corresponding to each dependency chain are successful; and when the dependency chain with verification failure exists in the at least one dependency chain, determining the verification result corresponding to the plurality of user characteristics as verification failure.
In a possible implementation manner, determining the verification results corresponding to the multiple user features according to the verification result corresponding to the independent user feature and the verification result corresponding to each dependency chain includes:
if the verification result corresponding to the independent user features is successful, and the verification result corresponding to each dependency chain is successful, determining the verification results corresponding to the multiple user features as successful verification;
and if the independent user characteristics have the user characteristics which fail to be verified or the at least one dependency chain has the dependency chain which fails to be verified, determining that the verification results corresponding to the plurality of user characteristics are failed to be verified.
In a possible implementation manner, performing service processing on the service to be requested according to the verification result corresponding to the plurality of user features includes:
if the verification results corresponding to the user characteristics are successful, processing the service to be requested according to the user characteristics;
and if the verification results corresponding to the user characteristics are verification failures, refusing to process the service to be requested.
In a second aspect, the present application provides a service processing apparatus, where the service processing apparatus includes a receiving module, a first determining module, a second determining module, a third determining module, and a fourth determining module, where:
the receiving module is used for receiving a service processing request, wherein the service processing request comprises an identifier of a service to be requested and a plurality of user characteristics;
the first determining module is configured to determine at least one dependency chain in the plurality of user features, where the dependency chain includes at least two user features having a dependency relationship, and a previous user feature in the dependency chain depends on a next user feature;
the second determining module is configured to determine a verification logic corresponding to each dependency chain, where the verification logic is configured to indicate a logical relationship between a verification result corresponding to the dependency chain and a verification result corresponding to each user feature in the dependency chain;
the third determining module is configured to determine, for any dependency chain, a verification result corresponding to the dependency chain according to a dependency relationship between user features in the dependency chain and a verification logic corresponding to the dependency chain;
the fourth determining module is configured to determine, according to the verification result corresponding to each dependency chain, the verification results corresponding to the multiple user characteristics, and perform service processing on the service to be requested according to the verification results corresponding to the multiple user characteristics.
In a possible implementation manner, the third determining module is specifically configured to:
determining a first user characteristic in the dependency chain, the first user characteristic not being dependent on other user characteristics in the dependency chain than the first user characteristic;
determining a first verification result corresponding to the first user characteristic;
and determining a verification result corresponding to the dependency chain according to the verification logic and the first verification result.
In a possible implementation manner, the third determining module is specifically configured to:
determining a verification result corresponding to the dependency chain according to the verification logic and the first verification result, including:
if the first verification result is successful, determining that the verification result corresponding to the dependency chain is successful;
and if the first verification result is verification failure, verifying other user characteristics except the first user characteristic in the dependency chain according to the first verification result to obtain a verification result corresponding to the dependency chain.
In a possible implementation manner, the third determining module is specifically configured to:
verifying the (N-i) th user feature in the dependency chain according to the dependency relationship in the dependency chain to obtain a verification result corresponding to the (N-i) th user feature, wherein N is the number of the user features included in the dependency chain;
and i sequentially takes 1, 2 and … …, and the verification result corresponding to the dependency chain is determined to be successful when the verification result corresponding to the (N-i) th user characteristic is successful, or the verification result corresponding to the dependency chain is determined to be failed until the verification result corresponding to the first user characteristic in the dependency chain is failed.
In a possible implementation manner, the third determining module is specifically configured to:
determining a verification result corresponding to the dependency chain according to the verification logic and the first verification result, including:
if the first verification result is successful, verifying other user characteristics except the first user characteristic in the dependency chain according to the first verification result to obtain a verification result corresponding to the dependency chain;
and if the first verification result is verification failure, determining that the verification result corresponding to the dependency chain is verification failure.
In a possible implementation manner, the third determining module is specifically configured to:
verifying the (N-i) th user feature in the dependency chain according to the dependency relationship in the dependency chain to obtain a verification result corresponding to the (N-i) th user feature, wherein N is the number of the user features included in the dependency chain;
and i sequentially takes 1, 2 and … …, and the verification result corresponding to the dependency chain is determined to be verification failure until the verification result corresponding to the (N-i) th user feature is verification failure, or the verification result corresponding to the dependency chain is determined to be verification success until the verification result corresponding to the first user feature in the dependency chain is verification success.
In a possible implementation manner, the fourth determining module is specifically configured to:
judging whether an independent user characteristic exists in the user characteristics, wherein the independent user characteristic does not exist a dependency relationship with other user characteristics in the user characteristics;
if yes, determining a verification result corresponding to the independent user features, and determining verification results corresponding to the plurality of user features according to the verification result corresponding to the independent user features and the verification result corresponding to each dependency chain;
if not, determining that the verification results corresponding to the multiple user characteristics are successful when the verification results corresponding to each dependency chain are successful; and when the dependency chain with verification failure exists in the at least one dependency chain, determining the verification result corresponding to the plurality of user characteristics as verification failure.
In a possible implementation manner, the fourth determining module is specifically configured to:
if the verification result corresponding to the independent user features is successful, and the verification result corresponding to each dependency chain is successful, determining the verification results corresponding to the multiple user features as successful verification;
and if the independent user characteristics have the user characteristics which fail to be verified or the at least one dependency chain has the dependency chain which fails to be verified, determining that the verification results corresponding to the plurality of user characteristics are failed to be verified.
In a possible implementation manner, the fourth determining module is specifically configured to:
if the verification results corresponding to the user characteristics are successful, processing the service to be requested according to the user characteristics;
and if the verification results corresponding to the user characteristics are verification failures, refusing to process the service to be requested.
In a third aspect, an embodiment of the present application provides a service processing device, including: a processor, a memory;
the memory stores computer-executable instructions;
the processor executes computer-executable instructions stored by the memory to cause the processor to perform the business process method of any one of the first aspects.
In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, where computer-executable instructions are stored, and when the computer-executable instructions are executed by a processor, the computer-readable storage medium is configured to implement the service processing method according to any one of the first aspect.
In a fifth aspect, the present invention also provides a computer program product comprising a computer program which, when executed by a processor, implements the steps of the business processing method according to any of the preceding claims.
The embodiment of the application provides a service processing method, a device and equipment, receiving a service processing request, wherein the service processing request comprises an identifier of a service to be requested and a plurality of user characteristics, determining at least one dependency chain in the plurality of user characteristics, the dependency chain comprises at least two user characteristics with dependency relationship, a previous user characteristic in the dependency chain depends on a next user characteristic, and determining a verification logic corresponding to each dependency chain, wherein the verification logic is used for indicating the logic relationship between the verification result corresponding to the dependency chain and the verification result corresponding to each user characteristic in the dependency chain, determining the verification result corresponding to the dependency chain according to the dependency relationship between each user characteristic in the dependency chain and the verification logic corresponding to the dependency chain aiming at any dependency chain, determining the verification result corresponding to the plurality of user characteristics according to the verification result corresponding to each dependency chain, and according to the verification results corresponding to the plurality of user characteristics, performing service processing on the service to be requested. In the method, when the user characteristics are verified, at least one dependency chain can be determined in the plurality of user characteristics, the verification logic corresponding to the dependency chain is determined, and the verification result of the dependency chain can be determined according to the dependency chain and the verification logic corresponding to the dependency chain.
Drawings
Fig. 1 is a schematic diagram of an application scenario provided in an embodiment of the present application;
fig. 2 is a schematic flowchart of a service processing method according to an embodiment of the present application;
fig. 3 is a schematic diagram of a service processing request according to an embodiment of the present application;
FIG. 4 is a schematic diagram of a dependency chain provided in an embodiment of the present application;
fig. 5 is a method for determining a verification result corresponding to a dependency chain according to an embodiment of the present disclosure;
FIG. 6 is a schematic diagram of a verification result for determining a dependency chain according to an embodiment of the present application;
fig. 7 is a flowchart of another method for determining a verification result corresponding to a dependency chain according to an embodiment of the present application;
fig. 8 is a schematic process diagram of a service processing method according to an embodiment of the present application;
fig. 9 is a schematic structural diagram of a service processing apparatus according to an embodiment of the present application;
fig. 10 is a schematic diagram of a hardware structure of a service processing device provided in the present application.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
In the related art, when a user purchases a product, a business system of a company verifies each user information of the user according to a restriction condition of the product, and determines whether the user can purchase the product. For example, if the financial product has the following constraints: and if the occupation is a teacher and the age is 20-40 years old, the occupation information and the age information of the user need to be verified, and the user can purchase the financial product after the verification of the occupation information and the age information is passed. However, as products are diversified, restrictions corresponding to the products increase, and the efficiency of service processing is low if verification is performed for each piece of user information based on the restrictions.
In order to solve the technical problem of low efficiency of service processing in the prior art, an embodiment of the present application provides a service processing method, receiving a service processing request, where the service processing request includes an identifier of a service to be requested and a plurality of user features, determining at least one dependency chain among the plurality of user features, where the dependency chain includes at least two user features having a dependency relationship, where a previous user feature in the dependency chain depends on a subsequent user feature, determining a verification logic corresponding to each dependency chain, where the verification logic is configured to indicate a logic relationship between a verification result corresponding to the dependency chain and a verification result corresponding to each user feature in the dependency chain, determine, for any one dependency chain, a user feature at an end of the dependency chain in the dependency chain, and determine a verification result of the user feature at the end of the dependency chain, and according to the verification logic and the verification result, and determining the verification result corresponding to the dependency chain. In the method, at least one dependency chain and verification logic corresponding to the dependency chain can be determined when the user features are verified, and since the dependency chain comprises a plurality of user features, the verification efficiency can be improved by verifying the dependency chain through the verification logic corresponding to the dependency chain, and further, the service processing efficiency is improved.
Next, an application scenario of the embodiment of the present application is described with reference to fig. 1.
Fig. 1 is a schematic diagram of an application scenario provided in an embodiment of the present application. Please refer to fig. 1, which includes: a client and a server. The client sends a service processing request to the server, wherein the service processing request comprises an identifier of a service to be requested and a plurality of user characteristics. The terminal equipment determines a dependency chain A and a dependency chain B according to a plurality of user characteristics. And the terminal equipment verifies the dependency chain A to obtain a verification result A corresponding to the dependency chain A, and the terminal equipment verifies the dependency chain B to obtain a verification result B corresponding to the dependency chain B. And the terminal equipment verifies the plurality of user characteristics according to the verification result A and the verification result B, and further performs service processing on the service to be requested according to the result of verifying the plurality of user characteristics. Therefore, when a plurality of user characteristics in the service request processing are verified, the terminal device can determine the dependency chain in the plurality of user characteristics and verify the dependency chain through the verification logic corresponding to the dependency chain.
The technical means shown in the present application will be described in detail below with reference to specific examples. It should be noted that the following embodiments may exist alone or in combination with each other, and description of the same or similar contents is not repeated in different embodiments.
Fig. 2 is a schematic flow chart of a service processing method according to an embodiment of the present application. Referring to fig. 2, the method may include:
s201, receiving a service processing request.
The execution main body of the embodiment of the application may be a terminal device, and may also be a service processing apparatus arranged in the terminal device. Wherein the service processing means may be implemented by a combination of software and/or hardware. Optionally, the terminal device is any device having a data processing function. For example, the terminal device may be a mobile phone, a computer, or the like.
The service processing request comprises an identification of the service to be requested and a plurality of user characteristics. The identifier of the service to be requested is the identifier of the service requested to be processed, and the service to be processed can be determined according to the identifier of the service to be requested. For example, the identifier of the service to be requested is an identifier corresponding to a service of purchasing a financial product of a bank, an identifier corresponding to a service of purchasing a book of a bookstore, and the like. For example, when a bank includes a plurality of financial products, a target financial product may be determined based on the identity of the service to be requested.
The user is characterized by user information corresponding to the service to be processed. For example, the user characteristics are information of a user who purchases a bank financial product, information of a user who purchases a book of a bookstore, and the like. For example, the user characteristics may include account information of the user, professional information of the user, gender information of the user, age information of the user, and the like.
Optionally, in an actual application process, when the service is purchasing a financial product of a bank, the financial product of a part of the bank includes a plurality of corresponding limiting conditions, and when the user characteristic satisfies the plurality of corresponding limiting conditions, the user may purchase the financial product. For example, when the limit condition for the financial product in the bank is that the age is greater than 20 years and less than 40 years, if the age of the user is 35 years, the user can purchase the financial product, and if the age of the user is 50 years, the user cannot purchase the financial product.
Optionally, the terminal device may obtain the service processing request in the client. For example, the terminal device may receive a service processing request sent by the client, and process the service according to the service processing request sent by the client.
Optionally, the terminal device may obtain the service processing request according to information input by the user. For example, when a user inputs a service processing request into a terminal device and the terminal device obtains the service processing request, the service may be processed.
Next, information included in the service processing request will be described with reference to fig. 3.
Fig. 3 is a schematic diagram of a service processing request according to an embodiment of the present application. See fig. 3, including the service processing request. The service processing request comprises an identifier of a service to be requested and a plurality of user characteristics. The identifier of the service to be requested is the identifier of the financial product A. The plurality of user characteristics includes an age of the user being 30 years, a occupation of the user being a teacher, a gender of the user being a male, and an account of the user being on a white list.
S202, determining at least one dependency chain in the plurality of user characteristics.
The dependency chain comprises at least two user features with dependency relationships. Wherein the dependency is used to indicate whether the authentication results between at least two user characteristics will interfere with each other. For example, if the verification result of the user feature a can be determined according to the verification result of the user feature B, the user feature a and the user feature B have a dependency relationship, and if the verification result of the user feature a cannot be determined by the verification result of the user feature B, the user feature a and the user feature B do not have a dependency relationship.
Optionally, the previous user characteristic in the dependency chain depends on the next user characteristic. For example, if the dependency chain includes user feature a, user feature B, and user feature C, the verification result of user feature a depends on the verification result of user feature B, and the verification result of user feature B depends on the verification result of user feature C. For example, the user characteristic a is that the occupation of the user is a teacher, the user characteristic B is that the age of the user is 30 years old, and if the user characteristic a and the user characteristic B need to be verified at the same time, or if any one of the user characteristics between the user characteristic a and the user characteristic B passes verification, the user can purchase a corresponding financial product, and then the user characteristic a and the user characteristic B have a dependency relationship.
Optionally, at least one dependency chain may be determined among the plurality of user characteristics according to the following possible implementation: and acquiring at least one limiting condition of a product corresponding to the identifier of the service to be requested and the dependency relationship between the limiting conditions. The limiting conditions are conditions which need to be met for purchasing products, dependency relations among the limiting conditions, dependency relations corresponding to the limiting conditions which need to be met for purchasing the products, and at least one dependency chain is determined in the plurality of user characteristics according to the dependency relations among the limiting conditions. For example, the product parameters corresponding to the product include occupation of a teacher and age of less than 30 years, and the occupation of the teacher and the age of less than 30 years have a dependency relationship, and if the user characteristics in the business processing request include occupation information of the user and age information of the user, it is determined that a dependency chain includes the occupation information of the user and the age information of the user.
The structure of the dependency chain determined by the plurality of user profiles is described in detail below with reference to fig. 4.
Fig. 4 is a schematic diagram of a dependency chain provided in an embodiment of the present application. See fig. 4, which includes user profile a, user profile B, and user profile C. The user characteristics A, B and C form a dependency chain. Wherein the user characteristic a depends on the user characteristic B, which depends on the user characteristic C.
And S203, determining the verification logic corresponding to each dependency chain.
The verification logic is used for indicating the logic relation between the verification result corresponding to the dependency chain and the verification result corresponding to each user characteristic in the dependency chain.
Optionally, the verification logic comprises a first verification logic or a second verification logic. And the first verification logic is used for verifying the dependency chain if any user characteristic in the dependency chain is successfully verified. For example, the dependency chain includes a user feature a, a user feature B, and a user feature C, when the verification logic is that any one user feature in the dependency chain is successfully verified and the dependency chain is successfully verified, if the verification result of the user feature a in the dependency chain is that the verification is passed, the verification result of the user feature B is that the verification is not passed, and the verification result of the user feature C is that the verification is not passed, the verification result of the dependency chain is that the verification is passed; and if the verification result of the user characteristic A in the dependency chain is that the verification fails, the verification result of the user characteristic B is that the verification fails, and the verification result of the user characteristic C is that the verification fails, the verification result of the dependency chain is that the verification fails.
The second authentication logic authenticates the dependency chain if all user features in the dependency chain are successfully authenticated. For example, the dependency chain includes a user feature a, a user feature B, and a user feature C, the verification logic is to verify all the user features in the dependency chain successfully, and if the verification result of the user feature a in the dependency chain is verification pass, the verification result of the user feature B is verification pass, and the verification result of the user feature C is verification pass, the verification result of the dependency chain is verification pass; and if the verification result of the user characteristic A in the dependency chain is that the verification is passed, the verification result of the user characteristic B is that the verification is passed, and the verification result of the user characteristic C is that the verification is not passed, the verification result of the dependency chain is that the verification is not passed.
Optionally, the verification logic may be determined according to at least one limiting condition of a product corresponding to the identifier of the service to be requested. For example, if the constraint a and the constraint B have a dependency relationship, and if the verification logic between the constraint a and the constraint B is successful in verifying any constraint in the dependency chain, the verification is successful for the dependency chain, then the dependency relationship exists between the user feature corresponding to the constraint a and the user feature corresponding to the constraint B, and if the verification logic of the dependency chain is successful in verifying any user feature in the dependency chain, the verification is successful for the dependency chain.
S204, aiming at any dependency chain, determining a verification result corresponding to the dependency chain according to the dependency relationship among the user characteristics in the dependency chain and the verification logic corresponding to the dependency chain.
The verification result corresponding to the dependency chain may be determined according to the following feasible implementation manners: a first user characteristic is determined in the dependency chain. Wherein the first user characteristic is other user characteristics in the dependency chain except the first user characteristic. For example, the dependency chain includes a user characteristic a, a user characteristic B, and a user characteristic C, and if the user characteristic a depends on the user characteristic B and the user characteristic B depends on the user characteristic C, the first user characteristic in the dependency chain is the user characteristic C. Optionally, the first user characteristic is a last user characteristic in the dependency chain. For example, if user characteristic a is the last user characteristic in the dependency chain, user characteristic a is the first user characteristic in the dependency chain.
And determining a first verification result corresponding to the first user characteristic. Optionally, the first verification result may be obtained according to the following feasible implementation manners: and determining a verification component corresponding to the first user characteristic according to the first user characteristic. In the actual application process, different user characteristics correspond to different verification components in the program, and the verification component corresponding to the first user characteristic can be determined according to the first preset relationship. The first preset relationship comprises at least one user characteristic and a verification component corresponding to each user characteristic. For example, the first preset relationship may be as shown in table 1:
TABLE 1
Figure BDA0003113125690000111
Figure BDA0003113125690000121
It should be noted that table 1 illustrates the first preset relationship by way of example only, and does not limit the first preset relationship.
For example, if the first user characteristic is user characteristic 1, determining that the verification component corresponding to the first user characteristic is verification component 1; if the first user characteristic is the user characteristic 2, determining that the verification component corresponding to the first user characteristic is the verification component 2; and if the first user characteristic is the user characteristic 3, determining that the verification component corresponding to the first user characteristic is the verification component 3.
And verifying the first user characteristic according to a verification component corresponding to the first user characteristic to obtain a first verification result. For example, if the first user characteristic is the age of the user, the verification component corresponding to the first user characteristic is verified by being aged less than 40 years old, and verified by being aged greater than or equal to 40 years old. For example, the verification component corresponding to the first user characteristic is a teacher or a doctor, if the first user characteristic is the teacher or the doctor, the first verification result is verification pass, and if the first user characteristic is a lawyer, the first verification result is verification fail.
And determining a verification result corresponding to the dependency chain according to the verification logic and the first verification result. For example, if the first verification result is that the verification is passed and the verification logic is the first verification logic, the verification result corresponding to the dependency chain is that the verification is passed, and if the first verification result is that the verification is not passed and the verification logic is the first verification logic, the verification result corresponding to the dependency chain is that the verification is not passed.
In the process of practical application, the first preset relationship can be stored in the database, and when the user characteristics are verified, the terminal device can directly call the verification component corresponding to the user characteristics in the database to verify the user characteristics, so that when the limiting conditions of the product change, only the verification component corresponding to the limiting conditions needs to be newly added in the database, a corresponding verification program does not need to be set for each product, and the complexity of the program is reduced.
Optionally, in the process of verifying the dependency chain, the user features in the dependency chain may be put into the stack according to the dependency order, and during verification, verification is started from the top of the stack, so as to obtain the verification result of the dependency chain.
Optionally, in an actual design of the verification program, the verification component of each user feature is integrated into abstract parameter verification (abstract paramverify), where the abstract paramverify includes a first verification method, and all the verification components need to cover the first verification method, so as to verify the user feature. For example, parameter set verification (ParamGroupVerify) is a verification component of user characteristics, and ParamGroupVerify includes the first verification method in abstract paramverify.
S205, according to the verification result corresponding to each dependency chain, the verification results corresponding to the multiple user characteristics are determined, and according to the verification results corresponding to the multiple user characteristics, service processing is performed on the service to be requested.
The verification results corresponding to the plurality of user features may be determined according to the following feasible implementation manners: and judging whether the independent user characteristics exist in the plurality of user characteristics. Wherein there is no dependency between the independent user characteristic and other user characteristics of the plurality of user characteristics. For example, the service processing request includes a user characteristic a, a user characteristic B, and a user characteristic C, and if the verification result of the user characteristic C is not related to the verification result of the user characteristic a and the verification result of the user characteristic B, it is determined that the user characteristic C is an independent user characteristic.
And if the independent user characteristics exist in the plurality of user characteristics, determining a verification result corresponding to the independent user characteristics, and determining the verification results corresponding to the plurality of user characteristics according to the verification results corresponding to the independent user characteristics and the verification results corresponding to each dependency chain. Optionally, the verification component corresponding to the independent user feature may be determined according to the independent user feature and the first preset relationship, and the independent user feature may be verified according to the verification component corresponding to the independent user feature, so as to obtain a verification result corresponding to the independent user feature.
Optionally, if the verification result corresponding to the independent user feature is successful, and the verification result corresponding to each dependency chain is successful, determining that the verification results corresponding to the multiple user features are successful. And if the user characteristics which fail to be verified exist in the independent user characteristics or the dependency chains which fail to be verified exist in at least one dependency chain, determining the verification results corresponding to the plurality of user characteristics as the verification failures. For example, the service processing request includes an independent user characteristic a, an independent user characteristic B and a dependent chain a, if the verification result of the independent user characteristic a is successful, the verification result of the independent user characteristic B is successful, and the verification result of the dependent chain a is successful, the verification results corresponding to the plurality of user characteristics are successful; and if the verification result of the independent user characteristic A is successful, the verification result of the independent user characteristic B is successful, and the verification result of the dependence chain A is failed, determining that the verification results corresponding to the plurality of user characteristics are failed.
Optionally, the service processing may be performed on the service to be requested according to the following feasible implementation manner: and if the verification results corresponding to the plurality of user characteristics are successful, processing the service to be requested according to the plurality of user characteristics. For example, if the verification result corresponding to the plurality of user features is successful, it may be determined that the user may purchase a product corresponding to the service.
And if the verification results corresponding to the plurality of user characteristics are verification failures, rejecting to process the service to be requested. For example, if the verification result corresponding to the plurality of user features is verification failure, it may be determined that the product corresponding to the business cannot be purchased.
The embodiment of the application provides a service processing method, which receives a service processing request, wherein the service processing request comprises an identifier of a service to be requested and a plurality of user features, at least one dependency chain is determined in the plurality of user features, the dependency chain comprises at least two user features with dependency relationship, the previous user feature in the dependency chain depends on the next user feature, a verification logic corresponding to each dependency chain is determined, the verification logic is used for indicating the logic relationship between the verification result corresponding to the dependency chain and the verification result corresponding to each user feature in the dependency chain, for any one dependency chain, a first user feature is determined in the dependency chain, a first verification result of the first user feature is determined, the verification result corresponding to the dependency chain is determined according to the verification logic and the first verification result, when an independent user feature exists in the plurality of user features, and determining the verification results of the plurality of user characteristics according to the verification results of the independent user characteristics and the verification results of the dependence chains, and performing service processing on the service to be requested according to the verification results corresponding to the plurality of user characteristics. In the method, at least one dependency chain and the verification logic corresponding to the dependency chain can be determined when the user characteristics are verified, and according to the first user characteristics in the dependency chain and the verification logic corresponding to the dependency chain, the verification result of the dependency chain can be rapidly determined, the verification efficiency of the dependency chain is improved, and the service processing efficiency is further improved.
On the basis of the embodiment shown in fig. 2, there are two possible implementations of determining the verification result corresponding to the dependency chain according to the verification logic and the first verification result, and the two possible implementations are described in detail below with reference to fig. 5 to 7.
Fig. 5 is a method for determining a verification result corresponding to a dependency chain according to an embodiment of the present disclosure. In the embodiment shown in fig. 5, the verification logic is the first verification logic, please refer to fig. 5, the method includes:
s501, judging whether the first verification result is successful.
Optionally, the first verification result is a verification result corresponding to the first user feature in the dependency chain.
If yes, go to step S502.
If not, go to step S503.
S502, according to the first verification logic, determining that the verification result corresponding to the dependency chain is successful.
And when the verification logic successfully verifies any user feature in the dependency chain and then successfully verifies the dependency chain, if the first verification result corresponding to the first user feature in the dependency chain is verification pass, determining that the verification result corresponding to the dependency chain is verification success.
S503, verifying other user characteristics except the first user characteristic in the dependency chain to obtain a verification result corresponding to the dependency chain.
Optionally, when the dependency chain includes the user characteristic a, the user characteristic B, and the user characteristic C, if the first user characteristic is the user characteristic C, the other user characteristics except the first user characteristic are the user characteristic a and the user characteristic B.
Optionally, the verification result corresponding to the dependency chain may be obtained according to the following feasible implementation manners: and verifying the N-i user characteristics in the dependency chain according to the dependency relationship in the dependency chain to obtain a verification result corresponding to the N-i user characteristics. N is the number of user features included in the dependency chain. For example, the dependency chain includes a user characteristic a, a user characteristic B, and a user characteristic C, where the user characteristic a depends on the user characteristic B, the user characteristic B depends on the user characteristic C, and if the verification result of the user characteristic C is that the verification fails, the user characteristic B is verified.
Optionally, i sequentially takes 1, 2, and … …, and when the verification result corresponding to the nth-i user characteristic is successful, the verification result corresponding to the dependency chain is determined to be successful. For example, the dependency chain includes a user feature a, a user feature B, and a user feature C, where the user feature a depends on the user feature B, and the user feature B depends on the user feature C, if the verification result of the user feature C is that verification fails, the user feature B is verified, if the verification result of the user feature B is that verification fails, the user feature a is verified, and if the verification result of the user feature a is that verification succeeds, the verification result corresponding to the dependency chain is that verification succeeds.
Optionally, i sequentially takes 1, 2, and … …, and when the verification result of the first user feature in the dependency chain is verification failure, it is determined that the verification result corresponding to the dependency chain is verification failure. For example, the dependency chain includes a user feature a, a user feature B, and a user feature C, where the user feature a depends on the user feature B, and the user feature B depends on the user feature C, if the verification result of the user feature C is that verification fails, the user feature B is verified, if the verification result of the user feature B is that verification fails, the user feature a is verified, and if the verification result of the user feature a is that verification fails, the verification result corresponding to the dependency chain is that verification fails.
This process of verifying the dependency chain is described below with reference to fig. 6.
Fig. 6 is a schematic diagram of a verification result for determining a dependency chain according to an embodiment of the present application. Please refer to fig. 6, which includes: user characteristics A, B and C. The user characteristics A, the user characteristics B and the user characteristics C form a dependency chain, wherein the user characteristics A depend on the user characteristics B, and the user characteristics B depend on the user characteristics C. User characteristic C is the first user characteristic in the dependency chain.
Referring to fig. 6, the user characteristic C is verified, when the user characteristic C fails to be verified, the user characteristic B is verified, when the user characteristic B succeeds to be verified, the user characteristic a does not need to be verified, and the verification result of the dependency chain is determined to be successful.
The embodiment of the application provides a service processing method, which includes judging whether a first verification result is successful, if so, determining that a verification result corresponding to a dependency chain is successful according to a first verification logic, and if not, verifying other user features except a first user feature in the dependency chain to obtain a verification result corresponding to the dependency chain. In the method, when the verification logic is the first verification logic, if the verification result of the first user characteristic is verification failure, the N-i user characteristics are sequentially verified, if all the N-i user characteristics are verification failure, the verification result of the dependence chain is verification failure, if any one user characteristic in the N-i user characteristics is verification success, other user characteristics do not need to be verified, and the verification result of the dependence chain is determined to be verification success, so that the verification efficiency of the dependence chain can be improved, and the service processing efficiency is further improved.
Fig. 7 is another method for determining a verification result corresponding to a dependency chain according to an embodiment of the present disclosure. Referring to fig. 7, the method includes:
s701, judging whether the first verification result is successful.
Optionally, the first verification result is a verification result corresponding to the first user feature in the dependency chain.
If not, go to step S702.
If yes, go to step S703.
S702, according to the second verification logic, determining that the verification result corresponding to the dependency chain is verification failure.
And if the verification logic is successful in verifying all the user characteristics in the dependency chain, the verification logic is successful in verifying the dependency chain, and if the first verification result corresponding to the first user characteristic in the dependency chain is failed in verification, the verification result corresponding to the dependency chain is determined to be failed in verification.
S703, verifying other user characteristics except the first user characteristic in the dependency chain to obtain a verification result corresponding to the dependency chain.
Optionally, the verification result corresponding to the dependency chain may be obtained according to the following feasible implementation manners: and verifying the N-i user characteristics in the dependency chain according to the dependency relationship in the dependency chain to obtain a verification result corresponding to the N-i user characteristics. N is the number of user features included in the dependency chain. For example, the dependency chain includes a user characteristic a, a user characteristic B, and a user characteristic C, where the user characteristic a depends on the user characteristic B, the user characteristic B depends on the user characteristic C, and if the verification result of the user characteristic C is that the verification fails, the user characteristic B is verified.
Optionally, i sequentially takes 1, 2, and … …, and when the verification result corresponding to the nth-i user characteristic is a verification failure, the verification result corresponding to the dependency chain is determined to be a verification failure. For example, the dependency chain includes a user feature a, a user feature B, and a user feature C, where the user feature a depends on the user feature B, and the user feature B depends on the user feature C, if the verification result of the user feature C is that the verification is successful, the user feature B is verified, if the verification result of the user feature B is that the verification is successful, the user feature a is verified, and if the verification result of the user feature a is that the verification is failed, the verification result corresponding to the dependency chain is that the verification is failed.
Optionally, i sequentially takes 1, 2, and … …, and when the verification result of the first user feature in the dependency chain is successful, it is determined that the verification result corresponding to the dependency chain is successful. For example, the dependency chain includes a user feature a, a user feature B, and a user feature C, where the user feature a depends on the user feature B, and the user feature B depends on the user feature C, if the verification result of the user feature C is that the verification is successful, the user feature B is verified, if the verification result of the user feature B is that the verification is successful, the user feature a is verified, and if the verification result of the user feature a is that the verification is successful, the verification result corresponding to the dependency chain is that the verification is successful.
The embodiment of the application provides a service processing method, which includes judging whether a first verification result is successful, if not, determining that a verification result corresponding to a dependency chain is failed according to a second verification logic, and if so, verifying other user features except a first user feature in the dependency chain to obtain a verification result corresponding to the dependency chain. In the method, when the verification logic is a second verification logic, if the verification result of the first user characteristic is successful, the N-i user characteristics are sequentially verified, if any one of the N-i user characteristics fails to be verified, the verification result of the dependence chain is failed to be verified, and if the first user characteristic in the N-i succeeds to be verified, the verification result of the dependence chain is determined to be successful, so that the verification efficiency of the dependence chain can be improved, and the service processing efficiency is further improved.
On the basis of any of the above embodiments, the following describes a procedure of the service processing method with reference to fig. 8.
Fig. 8 is a process schematic diagram of a service processing method according to an embodiment of the present application. See fig. 8, including the service processing request. The service processing request comprises an identifier of a service to be requested and a plurality of user characteristics. The identifier of the service to be requested is the identifier of the financial product A. The plurality of user characteristics includes an age of the user being 30 years, a occupation of the user being a teacher, a gender of the user being a male, and account information of the user.
Referring to fig. 8, the age of the user is 30 years, the occupation of the user is a teacher, and the gender of the user is male, and the account information of the user is an independent user characteristic. The dependencies and validation logic in the dependency chain are determined. Wherein the dependence relationship is that the age of the user is 30 years and the occupation of the user is teacher, and the occupation of the user is teacher and the gender of the user is male. The verification logic is a first verification logic. The first user characteristic in the dependency chain is that the user's gender is male.
Referring to fig. 8, when the verification result corresponding to the sex of the user being male fails, the professional of the user is verified for the teacher, when the verification result corresponding to the professional of the user being teacher succeeds, according to the first verification logic, verification of the age information of the user is not needed, verification of the dependency chain is determined to be successful, verification of the account information of the user is performed, and when the account information of the user is verified to be successful, verification of the characteristics of a plurality of users is determined to be successful, and the user can buy the financial product a. Therefore, when the professional of the user is successfully verified for the teacher, the age information of the user does not need to be verified, the verification efficiency of the dependence chain is improved, and the business processing efficiency is further improved.
Fig. 9 is a schematic structural diagram of a service processing apparatus according to an embodiment of the present application. The service processing apparatus 10 may be provided in a terminal device. Referring to fig. 9, the service processing apparatus 10 may include a receiving module 11, a first determining module 12, a second determining module 13, a third determining module 14, and a fourth determining module 15, where:
the receiving module 11 is configured to receive a service processing request, where the service processing request includes an identifier of a service to be requested and a plurality of user characteristics;
the first determining module 12 is configured to determine at least one dependency chain in the plurality of user features, where the dependency chain includes at least two user features having a dependency relationship, and a previous user feature in the dependency chain depends on a next user feature;
the second determining module 13 is configured to determine a verification logic corresponding to each dependency chain, where the verification logic is configured to indicate a logical relationship between a verification result corresponding to the dependency chain and a verification result corresponding to each user feature in the dependency chain;
the third determining module 14 is configured to, for any dependency chain, determine a verification result corresponding to the dependency chain according to a dependency relationship between user features in the dependency chain and a verification logic corresponding to the dependency chain;
the fourth determining module 15 is configured to determine, according to the verification result corresponding to each dependency chain, the verification results corresponding to the multiple user characteristics, and perform service processing on the service to be requested according to the verification results corresponding to the multiple user characteristics.
In a possible implementation, the third determining module 14 is specifically configured to:
determining a first user characteristic in the dependency chain, the first user characteristic not being dependent on other user characteristics in the dependency chain than the first user characteristic;
determining a first verification result corresponding to the first user characteristic;
and determining a verification result corresponding to the dependency chain according to the verification logic and the first verification result.
In a possible implementation, the third determining module 14 is specifically configured to:
determining a verification result corresponding to the dependency chain according to the verification logic and the first verification result, including:
if the first verification result is successful, determining that the verification result corresponding to the dependency chain is successful;
and if the first verification result is verification failure, verifying other user characteristics except the first user characteristic in the dependency chain according to the first verification result to obtain a verification result corresponding to the dependency chain.
In a possible implementation, the third determining module 14 is specifically configured to:
verifying the (N-i) th user feature in the dependency chain according to the dependency relationship in the dependency chain to obtain a verification result corresponding to the (N-i) th user feature, wherein N is the number of the user features included in the dependency chain;
and i sequentially takes 1, 2 and … …, and the verification result corresponding to the dependency chain is determined to be successful when the verification result corresponding to the (N-i) th user characteristic is successful, or the verification result corresponding to the dependency chain is determined to be failed until the verification result corresponding to the first user characteristic in the dependency chain is failed.
In a possible implementation, the third determining module 14 is specifically configured to:
determining a verification result corresponding to the dependency chain according to the verification logic and the first verification result, including:
if the first verification result is successful, verifying other user characteristics except the first user characteristic in the dependency chain according to the first verification result to obtain a verification result corresponding to the dependency chain;
and if the first verification result is verification failure, determining that the verification result corresponding to the dependency chain is verification failure.
In a possible implementation, the third determining module 14 is specifically configured to:
verifying the (N-i) th user feature in the dependency chain according to the dependency relationship in the dependency chain to obtain a verification result corresponding to the (N-i) th user feature, wherein N is the number of the user features included in the dependency chain;
and i sequentially takes 1, 2 and … …, and the verification result corresponding to the dependency chain is determined to be verification failure until the verification result corresponding to the (N-i) th user feature is verification failure, or the verification result corresponding to the dependency chain is determined to be verification success until the verification result corresponding to the first user feature in the dependency chain is verification success.
In a possible implementation manner, the fourth determining module 15 is specifically configured to:
judging whether an independent user characteristic exists in the user characteristics, wherein the independent user characteristic does not exist a dependency relationship with other user characteristics in the user characteristics;
if yes, determining a verification result corresponding to the independent user features, and determining verification results corresponding to the plurality of user features according to the verification result corresponding to the independent user features and the verification result corresponding to each dependency chain;
if not, determining that the verification results corresponding to the multiple user characteristics are successful when the verification results corresponding to each dependency chain are successful; and when the dependency chain with verification failure exists in the at least one dependency chain, determining the verification result corresponding to the plurality of user characteristics as verification failure.
In a possible implementation manner, the fourth determining module 15 is specifically configured to:
if the verification result corresponding to the independent user features is successful, and the verification result corresponding to each dependency chain is successful, determining the verification results corresponding to the multiple user features as successful verification;
and if the independent user characteristics have the user characteristics which fail to be verified or the at least one dependency chain has the dependency chain which fails to be verified, determining that the verification results corresponding to the plurality of user characteristics are failed to be verified.
In a possible implementation manner, the fourth determining module 15 is specifically configured to:
if the verification results corresponding to the user characteristics are successful, processing the service to be requested according to the user characteristics;
and if the verification results corresponding to the user characteristics are verification failures, refusing to process the service to be requested.
The service processing apparatus provided in the embodiment of the present application may execute the technical solutions shown in the foregoing method embodiments, and the implementation principles and beneficial effects thereof are similar, and are not described herein again.
The service processing device shown in the embodiment of the present application may be a chip, a hardware module, a processor, and the like. Of course, the service processing device may have other forms, and this embodiment of the present application is not particularly limited thereto.
Fig. 10 is a schematic diagram of a hardware structure of a service processing device provided in the present application. Referring to fig. 10, the service processing device 20 may include: a processor 21 and a memory 22, wherein the processor 21 and the memory 22 may communicate; illustratively, the processor 21 and the memory 22 communicate via a communication bus 23, the memory 22 is configured to store program instructions, and the processor 21 is configured to call the program instructions in the memory to execute the service processing method according to any of the above-described method embodiments.
Optionally, the service processing device 20 may further include a communication interface, which may include a transmitter and/or a receiver.
Optionally, the Processor may be a Central Processing Unit (CPU), or may be another general-purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of a method disclosed in connection with the present application may be embodied directly in a hardware processor, or in a combination of the hardware and software modules in the processor.
A readable storage medium having a computer program stored thereon; the computer program is configured to implement a service processing method as described in any of the above embodiments.
The embodiment of the application provides a computer program product, which comprises instructions, and when the instructions are executed, the instructions cause a computer to execute the service processing method.
All or a portion of the steps of implementing the above-described method embodiments may be performed by hardware associated with program instructions. The aforementioned program may be stored in a readable memory. When executed, the program performs steps comprising the method embodiments described above; and the aforementioned memory (storage medium) includes: read-only memory (ROM), RAM, flash memory, hard disk, solid state disk, magnetic tape (magnetic tape), floppy disk (flexible disk), optical disk (optical disk), and any combination thereof.
Embodiments of the present application are described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processing unit of a general purpose computer, special purpose computer, embedded processor, or other programmable terminal device to produce a machine, such that the instructions, which execute via the processing unit of the computer or other programmable terminal device, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable terminal equipment to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable terminal device to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
It will be apparent to those skilled in the art that various changes and modifications may be made in the embodiments of the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the embodiments of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to encompass such modifications and variations.
In the present application, the terms "include" and variations thereof may refer to non-limiting inclusions; the term "or" and variations thereof may mean "and/or". The terms "first," "second," and the like in this application are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. In the present application, "a plurality" means two or more. "and/or" describes the association relationship of the associated objects, meaning that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship.

Claims (13)

1. A method for processing a service, comprising:
receiving a service processing request, wherein the service processing request comprises an identifier of a service to be requested and a plurality of user characteristics;
determining at least one dependency chain in the plurality of user characteristics, wherein the dependency chain comprises at least two user characteristics with dependency relationship, and a previous user characteristic in the dependency chain depends on a next user characteristic;
determining a verification logic corresponding to each dependency chain, wherein the verification logic is used for indicating a logic relationship between a verification result corresponding to the dependency chain and a verification result corresponding to each user feature in the dependency chain;
aiming at any dependency chain, determining a verification result corresponding to the dependency chain according to the dependency relationship among the user characteristics in the dependency chain and the verification logic corresponding to the dependency chain;
and determining the verification results corresponding to the plurality of user characteristics according to the verification result corresponding to each dependency chain, and performing service processing on the service to be requested according to the verification results corresponding to the plurality of user characteristics.
2. The method according to claim 1, wherein determining the verification result corresponding to the dependency chain according to the dependency relationship between the user features in the dependency chain and the verification logic corresponding to the dependency chain comprises:
determining a first user characteristic in the dependency chain, the first user characteristic not being dependent on other user characteristics in the dependency chain than the first user characteristic;
determining a first verification result corresponding to the first user characteristic;
and determining a verification result corresponding to the dependency chain according to the verification logic and the first verification result.
3. The method of claim 2, wherein the authentication logic is a first authentication logic, the first authentication logic being: if any user feature in the dependency chain is successfully verified, the dependency chain is successfully verified;
determining a verification result corresponding to the dependency chain according to the verification logic and the first verification result, including:
if the first verification result is successful, determining that the verification result corresponding to the dependency chain is successful;
and if the first verification result is verification failure, verifying other user characteristics except the first user characteristic in the dependency chain according to the first verification result to obtain a verification result corresponding to the dependency chain.
4. The method according to claim 3, wherein verifying the user characteristics except the first user characteristic in the dependency chain to obtain a verification result corresponding to the dependency chain comprises:
verifying the (N-i) th user feature in the dependency chain according to the dependency relationship in the dependency chain to obtain a verification result corresponding to the (N-i) th user feature, wherein N is the number of the user features included in the dependency chain;
and i sequentially takes 1, 2 and … …, and the verification result corresponding to the dependency chain is determined to be successful when the verification result corresponding to the (N-i) th user characteristic is successful, or the verification result corresponding to the dependency chain is determined to be failed until the verification result corresponding to the first user characteristic in the dependency chain is failed.
5. The method of claim 2, wherein the authentication logic is a second authentication logic, the second authentication logic being: if all the user features in the dependency chain are verified successfully, the dependency chain is verified successfully;
determining a verification result corresponding to the dependency chain according to the verification logic and the first verification result, including:
if the first verification result is successful, verifying other user characteristics except the first user characteristic in the dependency chain according to the first verification result to obtain a verification result corresponding to the dependency chain;
and if the first verification result is verification failure, determining that the verification result corresponding to the dependency chain is verification failure.
6. The method according to claim 5, wherein verifying the user characteristics except the first user characteristic in the dependency chain to obtain a verification result corresponding to the dependency chain comprises:
verifying the (N-i) th user feature in the dependency chain according to the dependency relationship in the dependency chain to obtain a verification result corresponding to the (N-i) th user feature, wherein N is the number of the user features included in the dependency chain;
and i sequentially takes 1, 2 and … …, and the verification result corresponding to the dependency chain is determined to be verification failure until the verification result corresponding to the (N-i) th user feature is verification failure, or the verification result corresponding to the dependency chain is determined to be verification success until the verification result corresponding to the first user feature in the dependency chain is verification success.
7. The method according to any one of claims 1 to 6, wherein determining the verification result corresponding to the plurality of user features according to the verification result corresponding to each dependency chain comprises:
judging whether an independent user characteristic exists in the user characteristics, wherein the independent user characteristic does not exist a dependency relationship with other user characteristics in the user characteristics;
if yes, determining a verification result corresponding to the independent user features, and determining verification results corresponding to the plurality of user features according to the verification result corresponding to the independent user features and the verification result corresponding to each dependency chain;
if not, determining that the verification results corresponding to the multiple user characteristics are successful when the verification results corresponding to each dependency chain are successful; and when the dependency chain with verification failure exists in the at least one dependency chain, determining the verification result corresponding to the plurality of user characteristics as verification failure.
8. The method according to claim 7, wherein determining the verification results corresponding to the plurality of user features according to the verification results corresponding to the independent user features and the verification results corresponding to each dependency chain comprises:
if the verification result corresponding to the independent user features is successful, and the verification result corresponding to each dependency chain is successful, determining the verification results corresponding to the multiple user features as successful verification;
and if the independent user characteristics have the user characteristics which fail to be verified or the at least one dependency chain has the dependency chain which fails to be verified, determining that the verification results corresponding to the plurality of user characteristics are failed to be verified.
9. The method according to any one of claims 1 to 8, wherein performing service processing on the service to be requested according to the verification result corresponding to the plurality of user features comprises:
if the verification results corresponding to the user characteristics are successful, processing the service to be requested according to the user characteristics;
and if the verification results corresponding to the user characteristics are verification failures, refusing to process the service to be requested.
10. A service processing apparatus, comprising a receiving module, a first determining module, a second determining module, a third determining module, and a fourth determining module, wherein:
the receiving module is used for receiving a service processing request, wherein the service processing request comprises an identifier of a service to be requested and a plurality of user characteristics;
the first determining module is configured to determine at least one dependency chain in the plurality of user features, where the dependency chain includes at least two user features having a dependency relationship, and a previous user feature in the dependency chain depends on a next user feature;
the second determining module is configured to determine a verification logic corresponding to each dependency chain, where the verification logic is configured to indicate a logical relationship between a verification result corresponding to the dependency chain and a verification result corresponding to each user feature in the dependency chain;
the third determining module is configured to determine, for any dependency chain, a verification result corresponding to the dependency chain according to a dependency relationship between user features in the dependency chain and a verification logic corresponding to the dependency chain;
the fourth determining module is configured to determine, according to the verification result corresponding to each dependency chain, the verification results corresponding to the multiple user characteristics, and perform service processing on the service to be requested according to the verification results corresponding to the multiple user characteristics.
11. A traffic processing device, comprising: a processor and a memory;
the memory is used for storing a computer program;
the processor is configured to execute the computer program stored in the memory to implement the service processing method according to any one of claims 1 to 9.
12. A readable storage medium, on which a device control program is stored, which when executed by a processor, implements the service processing method according to any one of claims 1 to 9.
13. A computer program product comprising a computer program, characterized in that the computer program, when executed by a processor, implements the business process method of any one of claims 1 to 9.
CN202110656583.3A 2021-06-11 2021-06-11 Service processing method, device and equipment Pending CN113283983A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202110656583.3A CN113283983A (en) 2021-06-11 2021-06-11 Service processing method, device and equipment

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202110656583.3A CN113283983A (en) 2021-06-11 2021-06-11 Service processing method, device and equipment

Publications (1)

Publication Number Publication Date
CN113283983A true CN113283983A (en) 2021-08-20

Family

ID=77284550

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202110656583.3A Pending CN113283983A (en) 2021-06-11 2021-06-11 Service processing method, device and equipment

Country Status (1)

Country Link
CN (1) CN113283983A (en)

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103927464A (en) * 2013-01-11 2014-07-16 深圳市腾讯计算机系统有限公司 Common validation method, and method, device and system for generating two dimensional code
CN105871786A (en) * 2015-01-22 2016-08-17 阿里巴巴集团控股有限公司 User information authentication method, device and system
CN107395623A (en) * 2017-08-18 2017-11-24 广州视源电子科技股份有限公司 Interface access data verification method and device, computer-readable storage medium and equipment
US10078868B1 (en) * 2007-01-31 2018-09-18 Experian Information Solutions, Inc. System and method for providing an aggregation tool
WO2018209623A1 (en) * 2017-05-17 2018-11-22 Tink Labs Limited Systems, devices, and methods for performing verification of communications received from one or more computing devices
CN109901926A (en) * 2019-01-25 2019-06-18 平安科技(深圳)有限公司 Method, server and storage medium based on big data behavior scheduling application task
CN111176802A (en) * 2019-07-26 2020-05-19 腾讯科技(深圳)有限公司 Task processing method and device, electronic equipment and storage medium

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10078868B1 (en) * 2007-01-31 2018-09-18 Experian Information Solutions, Inc. System and method for providing an aggregation tool
CN103927464A (en) * 2013-01-11 2014-07-16 深圳市腾讯计算机系统有限公司 Common validation method, and method, device and system for generating two dimensional code
CN105871786A (en) * 2015-01-22 2016-08-17 阿里巴巴集团控股有限公司 User information authentication method, device and system
WO2018209623A1 (en) * 2017-05-17 2018-11-22 Tink Labs Limited Systems, devices, and methods for performing verification of communications received from one or more computing devices
CN107395623A (en) * 2017-08-18 2017-11-24 广州视源电子科技股份有限公司 Interface access data verification method and device, computer-readable storage medium and equipment
CN109901926A (en) * 2019-01-25 2019-06-18 平安科技(深圳)有限公司 Method, server and storage medium based on big data behavior scheduling application task
CN111176802A (en) * 2019-07-26 2020-05-19 腾讯科技(深圳)有限公司 Task processing method and device, electronic equipment and storage medium

Similar Documents

Publication Publication Date Title
US10230711B2 (en) System and methods for enhancing authentication procedures in an anti-fraud environment
CN107993053B (en) Claims data auditing method and device, computer equipment and storage medium
CN107797854B (en) Transaction file processing method and device, storage medium and computer equipment
CN110489415B (en) Data updating method and related equipment
CN106991326A (en) The upgrade method and its equipment of a kind of equipment firmware
CN110599174A (en) Block chain information processing method and related equipment
CN105719140A (en) Method and device for user information verification
EP3038317B1 (en) User authentication for resource transfer based on mapping of physiological characteristics
CN110245912A (en) A kind of electronic contract signature method, apparatus, storage medium and terminal device
CN111008206A (en) Method and device for storing state data of cross-chain transaction and storage medium
CN111145762B (en) Electronic certificate verification method and system based on voiceprint recognition
CN115131022A (en) Block chain-based digital asset transaction method, device, equipment and medium
WO2016188249A1 (en) Payment method, device and system
CN112037062B (en) Transaction consensus method, device, electronic equipment and readable storage medium
CN108431843B (en) Transaction processing method and device
CN113283983A (en) Service processing method, device and equipment
CN109544158B (en) Block data processing method and computer storage medium
CN111711523A (en) Item handling authority authorization method and device, computer equipment and storage medium
CN116707758A (en) Authentication method, equipment and server of trusted computing equipment
CN105471884A (en) Authentication method and server
US9998495B2 (en) Apparatus and method for verifying detection rule
CN114255134A (en) Account number disassembling method and device and storage medium
CN112529462A (en) Service verification method, device, server and storage medium
CN111681010A (en) Transaction verification method and device
CN115022864B (en) Verification method and device for subscription service

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination