Business processing method, device and equipment

Abstract

The embodiment of the present application provides a business processing method, device and equipment, the method comprising: receiving a business processing request, the business processing request including an identifier of a requested business and multiple user features; determining M first user features that have no dependency relationship with other user features, and N second user features that have a dependency relationship with each other among the multiple user features; performing verification processing on the M first user features to obtain a verification result of each first user feature; performing verification processing on the N second user features to obtain a verification result of at least one third user feature among the N second user features, the third user feature being dependent on other user features among the second user features and not being dependent on by other user features; performing business processing on the requested business according to the verification results of the M first user features and the verification results of at least one third user feature. The complexity of business maintenance is reduced.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of computer technology, and in particular, to a business processing method, device, and equipment. Background Art

[0002] For some services, when a user requests service processing, the service processing can only be carried out after verifying that the user's user characteristics meet the service requirements. For example, when a user purchases a financial product, the user can only purchase it if the user characteristics meet the requirements of the financial product.

[0003] In the related art, before performing business processing, it is necessary to design the verification logic corresponding to the business according to the business requirements, and verify the user characteristics of the user according to the verification logic, wherein the business requirements include multiple user characteristics and conditions that the user characteristics need to meet. However, in the actual application process, if the business requirements change (for example, the user characteristics in the business requirements change or the conditions that the user characteristics need to meet change), the verification logic corresponding to the business needs to be modified. In the above process, since the verification logic is used to verify the user characteristics, it is necessary to maintain the verification logic corresponding to the business. Due to the high complexity of the modification of the verification logic, the complexity of business maintenance is high. Summary of the invention

[0004] The embodiments of the present application provide a service processing method, apparatus and device, which reduce the complexity of service maintenance.

[0005] In a first aspect, an embodiment of the present application provides a service processing method, including:

[0006] receiving a service processing request, wherein the service processing request includes an identifier of a service to be requested and a plurality of user characteristics;

[0007] Determine M first user features and N second user features from the multiple user features, there is no dependency relationship between the first user feature and other user features, there is a dependency relationship between the N second user features, M is an integer, and N is a positive integer;

[0008] According to the service requirement information of the service to be requested, respectively verify the M first user characteristics to obtain a verification result of each first user characteristic;

[0009] According to the service requirement information of the service to be requested, verification processing is performed on the N second user features to obtain a verification result of at least one third user feature among the N second user features, where the third user feature depends on other user features among the second user features, and the third user feature is not dependent on other user features among the second user features;

[0010] The service to be requested is processed according to the verification results of the M first user characteristics and the verification result of the at least one third user characteristic.

[0011] In a possible implementation, verifying the N second user characteristics according to the service requirement information of the service to be requested includes:

[0012] Determine at least one dependency chain according to the dependency relationship between the N second user features, wherein 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 subsequent user feature;

[0013] According to the business requirement information of the to-be-requested business, the second user feature in each dependency chain is verified respectively.

[0014] In a possible implementation, for any dependency chain, verifying the second user feature in the dependency chain according to the service requirement information of the service to be requested includes:

[0015] Determine, according to the dependency relationship between the second user features in the dependency chain, a dependency depth K of each second user feature in the dependency chain, wherein the second user feature is dependent on K user features with different dependency depths, and K is an integer greater than or equal to 0;

[0016] According to the dependency depth K of each second user feature in the dependency chain and the service requirement information of the service to be requested, the second user features in the dependency chain are verified.

[0017] In a possible implementation, determining the dependency depth K of each second user feature in the dependency chain includes:

[0018] Initialize the dependency depth corresponding to each second user feature;

[0019] Determine the dependent user feature of the i-th second user feature in the dependency chain, update the dependency depth corresponding to the dependent user feature to the dependency depth of the i-th second user feature plus 1, determine the dependent user feature as the i+1-th second user feature, and the first user feature in the dependency chain is the third user feature in the dependency chain;

[0020] Here, the i is 1, 2, ..., X-1, and X is the number of second user features included in the dependency chain.

[0021] In a possible implementation, determining the dependency depth K of each second user feature in the dependency chain includes:

[0022] Determine that the dependency depth corresponding to the i-th second user feature in the dependency chain is i-1, wherein i is an integer greater than or equal to 1 and less than or equal to X, and X is the number of second user features included in the dependency chain.

[0023] In a possible implementation, verifying the second user features in the dependency chain according to the dependency depth K of each second user feature in the dependency chain and the service requirement information of the service to be requested includes:

[0024] In the order of dependency depth from high to low, and according to the business requirement information of the to-be-requested business, the second user characteristics in the dependency chain are verified in sequence.

[0025] In a possible implementation, performing service processing on the service to be requested according to the verification results of the M first user characteristics and the verification result of the at least one third user characteristic includes:

[0026] If the verification results of the M first user characteristics are successful, and the verification result of the at least one third user characteristic is successful, processing the requested service according to the at least one user characteristic;

[0027] If a verification result of a first user feature among the M first user features is verification failure, or a verification result of a third user feature among the at least one third user feature is verification failure, the requested service is refused to be processed.

[0028] In a second aspect, an embodiment of the present application provides a service processing device, including: a receiving module, a determining module, a verifying module and a processing module, wherein:

[0029] The receiving module is used to receive a service processing request, wherein the service processing request includes an identifier of the service to be requested and multiple user characteristics;

[0030] The determination module is used to determine M first user features and N second user features from the multiple user features, there is no dependency relationship between the first user feature and other user features, and there is a dependency relationship between the N second user features, M is an integer, and N is a positive integer;

[0031] The verification module is used to verify the M first user characteristics respectively according to the business requirement information of the service to be requested, and obtain a verification result of each first user characteristic;

[0032] The verification module is further used to, according to the service requirement information of the service to be requested, perform verification processing on the N second user characteristics to obtain a verification result of at least one third user characteristic among the N second user characteristics, wherein the third user characteristic depends on other user characteristics among the second user characteristics, and the third user characteristic is not dependent on other user characteristics among the second user characteristics;

[0033] The processing module is used to perform service processing on the service to be requested according to the verification results of the M first user characteristics and the verification result of the at least one third user characteristic.

[0034] In a possible implementation, the verification module is specifically used to:

[0035] Determine at least one dependency chain according to the dependency relationship between the N second user features, wherein 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 subsequent user feature;

[0036] According to the business requirement information of the to-be-requested business, the second user feature in each dependency chain is verified respectively.

[0037] In a possible implementation, the verification module is specifically used to:

[0038] For any dependency chain, determine the dependency depth K of each second user feature in the dependency chain according to the dependency relationship between the second user features in the dependency chain, where the second user feature is dependent on K user features with different dependency depths, where K is an integer greater than or equal to 0;

[0039] According to the dependency depth K of each second user feature in the dependency chain and the service requirement information of the service to be requested, the second user features in the dependency chain are verified.

[0040] In a possible implementation, the verification module is specifically used to:

[0041] Initialize the dependency depth corresponding to each second user feature;

[0042] Determine the dependent user feature of the i-th second user feature in the dependency chain, update the dependency depth corresponding to the dependent user feature to the dependency depth of the i-th second user feature plus 1, determine the dependent user feature as the i+1-th second user feature, and the first user feature in the dependency chain is the third user feature in the dependency chain;

[0043] Here, the i is 1, 2, ..., X-1, and X is the number of second user features included in the dependency chain.

[0044] In a possible implementation, the verification module is specifically used to:

[0045] Determine that the dependency depth corresponding to the i-th second user feature in the dependency chain is i-1, wherein i is an integer greater than or equal to 1 and less than or equal to X, and X is the number of second user features included in the dependency chain.

[0046] In a possible implementation, the verification module is specifically used to:

[0047] In the order of dependency depth from high to low, and according to the business requirement information of the to-be-requested business, the second user characteristics in the dependency chain are verified in sequence.

[0048] In a possible implementation manner, the processing module is specifically used to:

[0049] If the verification results of the M first user characteristics are successful, and the verification result of the at least one third user characteristic is successful, processing the requested service according to the at least one user characteristic;

[0050] If a verification result of a first user feature among the M first user features is verification failure, or a verification result of a third user feature among the at least one third user feature is verification failure, the requested service is refused to be processed.

[0051] In a third aspect, an embodiment of the present application provides a service processing device, including: a processor and a memory;

[0052] The memory stores computer-executable instructions;

[0053] The processor executes the computer-executable instructions stored in the memory, so that the processor executes the business processing method as described in any one of the first aspects.

[0054] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores computer execution instructions, and when the computer execution instructions are executed by a processor, they are used to implement the business processing method described in any one of the first aspects.

[0055] In a fifth aspect, an embodiment of the present application provides a computer program product, including a computer program, which, when executed by a processor, implements the business processing method shown in any one of the first aspects.

[0056] The business processing method provided in the embodiment of the present application obtains multiple user features of the user after receiving the business processing request of the user, and determines M first user features and N second user features from the multiple user features, wherein there is no dependency relationship between the first user features and other user features, and there is a dependency relationship between the N second user features. The M first user features and the N second user features are verified and processed respectively according to the business demand information of the requested business, and the business processing is performed on the requested business according to the verification results. In the above process, there is no need to design the verification logic of the business in advance, and there is no need to maintain the verification logic, thereby reducing the complexity of maintaining the business. BRIEF DESCRIPTION OF THE DRAWINGS

[0057] Figure 1 An architectural diagram of an application scenario provided in an embodiment of the present application;

[0058] Figure 2 A flowchart of a business processing method provided in an embodiment of the present application;

[0059] Figure 3 A flowchart of another business processing method provided in an embodiment of the present application;

[0060] Figure 4 A schematic diagram of the process of chain splitting provided in an embodiment of the present application;

[0061] Figure 5 A schematic diagram of the structure of a service processing device provided in an embodiment of the present application;

[0062] Figure 6 A schematic diagram of the structure of a business processing device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0063] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the present application. Instead, they are merely examples of devices and methods consistent with some aspects of the present application as detailed in the appended claims.

[0064] It should be noted that, in this article, the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the existence of other identical elements in the process, method, article or device including the element.

[0065] To facilitate understanding, first combine Figure 1 , the application scenarios to which the embodiments of the present application are applicable are described.

[0066] Figure 1 This is an architecture diagram of the application scenario provided by the embodiment of this application. Figure 1 , including electronic devices, which can perform business processing. The electronic device can obtain multiple user characteristics of the user and verify the multiple user characteristics. After the verification is passed, the electronic device can process the business requested by the user. For example, the user characteristics may include: the user's name, age, occupation, city, user type, etc.

[0067] The multiple user features include mutually independent user features and user features with dependencies. Mutually independent user features means that the verification of this feature does not need to rely on the verification results of other user features, and the verification of other user features does not need to rely on the verification results of this user feature. A user feature with dependencies means that the verification of this feature needs to rely on the verification results of other user features, and / or the verification of other user features needs to rely on the verification results of this user feature. For example, for the user features: name and occupation, the occupation is verified only when the verified name is in the whitelist. In this case, the occupation depends on the verification result of the name.

[0068] For example, see Figure 1 , assuming that user features include: A, B, C, D, E, F, G, H, I, where user features A and B are independent user features; user feature C depends on user feature D, and user feature D depends on user feature E; user feature F depends on user feature G and user feature H, and user feature G and user feature H depend on user feature I. Among them, user feature C-user feature E can be called a dependency chain, and user feature F-user feature I can be called a dependency chain.

[0069] In related technologies, it is necessary to design the verification logic corresponding to the business according to the business requirements and maintain the verification logic. When the business requirements change, the verification logic needs to be modified to adapt. For example, see Figure 1 , assuming that the business requirements no longer require verification of user feature G, the business logic corresponding to the business needs to be modified. The complexity of modifying the business logic is high, resulting in high complexity in business maintenance.

[0070] In order to solve the above technical problems, in an embodiment of the present application, after receiving a business processing request, multiple user characteristics of the user and the dependencies between the user characteristics are obtained, and the user characteristics are verified based on the dependencies between the multiple user characteristics. There is no need to design the verification logic of the business in advance, and there is no need to maintain the verification logic, thereby reducing the complexity of maintaining the business.

[0071] The technical solution shown in the present application is described in detail below through specific embodiments. It should be noted that the following embodiments can exist independently or in combination with each other, and the same or similar contents will not be described repeatedly in different embodiments.

[0072] Figure 2 A flowchart of a business processing method provided in an embodiment of the present application. Figure 2 , the method may include:

[0073] S201: Receive a business processing request.

[0074] The execution subject of the embodiment of the present application may be an electronic device, or a service processing device arranged in the electronic device. The service processing device may be implemented by software, or by a combination of software and hardware.

[0075] The service processing request is used to request processing of the service to be requested. The service processing request may include the identifier of the service to be requested and multiple user characteristics.

[0076] The service to be requested may be a user's request to purchase a preset object, for example, the preset object may be a commodity, a financial product, etc.

[0077] User characteristics refer to the characteristics of the user who requests the service to be requested. For example, user characteristics may include the user's age, occupation, gender, health status, etc.

[0078] Optionally, the electronic device may receive a service processing request sent by a client, or receive a service processing request input by a service person in the electronic device.

[0079] S202: Determine M first user features and N second user features from a plurality of user features.

[0080] Wherein, M is an integer and N is a positive integer. That is, M is an integer greater than or equal to 0, and N is an integer greater than or equal to 1.

[0081] There is no dependency relationship between the first user feature and other user features, that is, the first user feature does not depend on other user features (verification of the first user feature does not need to depend on the verification results of other user features), and other user features do not depend on the first user feature (verification of other user features does not need to depend on the verification results of the first user feature).

[0082] There is a dependency relationship between the N second user features. For example, there are one or more dependency chains among the N second user features.

[0083] Configuration information corresponding to the service to be requested may be preset, the configuration information including dependency relationships between multiple user features corresponding to the service to be requested, and accordingly, M first user features and N second user features may be determined from the multiple user features according to the dependency relationships.

[0084] S203: According to the service requirement information of the service to be requested, respectively verify the M first user characteristics to obtain a verification result of each first user characteristic.

[0085] The business requirement information includes the verification condition corresponding to each first user feature. For any first user feature, if the first user feature meets the corresponding verification condition, the verification result corresponding to the first user feature is determined to be a successful verification; if the first user feature does not meet the corresponding verification condition, the verification result corresponding to the first user feature is determined to be a failed verification.

[0086] S204: Verify the N second user characteristics according to the service requirement information of the service to be requested, and obtain a verification result of at least one third user characteristic among the N second user characteristics.

[0087] The third user feature depends on other user features in the second user feature, and the third user feature is not dependent on other user features in the second user feature. That is, the third user feature is the first user feature in the dependency chain. For example, see Figure 1 For the dependency chain (including user feature C-user feature E), the third user feature is user feature C, and for the dependency chain (including user feature F-user feature I), the third user feature is user feature F.

[0088] The N second user features may be verified in the following manner: at least one dependency chain is determined according to the dependency relationship between the N second user features, and the second user features in each dependency chain are verified according to the service requirement information of the service to be requested. The dependency chain includes at least two user features with a dependency relationship, and the previous user feature in the dependency chain depends on the next user feature.

[0089] For each dependency chain, the second user feature in each dependency chain is verified respectively, and a verification result of the third user feature in the dependency chain can be obtained, wherein the third user feature is the first user feature in the dependency chain.

[0090] S205: Perform service processing on the requested service according to the verification results of the M first user characteristics and the verification result of the at least one third user characteristic.

[0091] If the verification results of the M first user characteristics are successful, and the verification result of at least one third user characteristic is successful, it is determined that the user characteristic verification of the user is successful. In this case, the requested service can be processed according to at least one user characteristic.

[0092] If the verification result of the first user feature in the M first user features is verification failure, or the verification result of the third user feature in at least one third user feature is verification failure, it is determined that the user feature verification of the user fails. In this case, the processing of the requested service can be rejected.

[0093] The business processing method provided in the embodiment of the present application obtains multiple user features of the user after receiving the business processing request of the user, and determines M first user features and N second user features from the multiple user features, wherein there is no dependency relationship between the first user features and other user features, and there is a dependency relationship between the N second user features. The M first user features and the N second user features are verified and processed respectively according to the business demand information of the requested business, and the business processing is performed on the requested business according to the verification results. In the above process, there is no need to design the verification logic of the business in advance, and there is no need to maintain the verification logic, thereby reducing the complexity of maintaining the business.

[0094] Based on any of the above embodiments, Figure 3 , the above business processing method is explained in detail.

[0095] Figure 3 A flowchart of another business processing method provided in an embodiment of the present application. Figure 3 , the method may include:

[0096] S301: Receive a business processing request.

[0097] S302: Determine M first user features and N second user features from a plurality of user features.

[0098] It should be noted that the execution process of S301-S302 can refer to the execution process of S201, and will not be repeated here.

[0099] S303: Determine at least one dependency chain according to the dependency relationship between the N second user features.

[0100] The dependency chain includes at least two user features having a dependency relationship, and the first user feature in the dependency chain depends on the second user feature.

[0101] The N second user features may be chained according to the dependency relationship between the N second user features, so as to allocate the second user features with the dependency relationship to the same dependency chain.

[0102] Next, combine Figure 4 , the chain splitting process is explained.

[0103] Figure 4 This is a flowchart of the chain splitting process provided by the embodiment of this application. Figure 4 ,Initially, the N second user features include user feature A, user feature B, user feature C, user feature D, user feature E, and user feature F, and the dependency chain is empty.

[0104] Take out any user feature A from the N second user features, and determine that the user feature that user feature A depends on is user feature B, then a dependency chain 1 can be formed based on this: user feature A depends on user feature B, and then determine that the user feature that user feature B depends on is user feature D from the N user features, and update dependency chain 1 based on this: user feature A depends on user feature B, and user feature B depends on user feature D. Since user feature D has no dependent user features, the update of dependency chain 1 is completed.

[0105] Take out any user feature F from the N second user features, and determine that the user feature on which user feature F depends is user feature E, then we can form dependency chain 2: user feature F depends on user feature E, then search for the user feature on which user feature E depends among the N user features, assuming that user feature E does not depend on any user feature, then determine that the remaining user feature C among the N second user features depends on user feature E, then we can update dependency chain 2: user feature C depends on user feature E, and user feature E depends on user feature F.

[0106] After determining that at least one dependency chain is obtained, the processing process for each dependency chain is the same. In the following S304-S305, the processing process for any dependency chain is taken as an example for description.

[0107] S304: Determine the dependency depth K of each second user feature in the dependency chain according to the dependency relationship between the second user features in the dependency chain.

[0108] The second user feature corresponds to a dependency depth of K, which can also be understood as: the second user feature is dependent on K user features with different dependency depths. In the first dependency chain, assuming that the previous user feature depends on the next user feature, the dependency depth K corresponding to the second user feature refers to the position K of the second user feature in the dependency chain (the second user feature is the Kth user feature in the dependency chain). For example, see Figure 1 , for the dependency chain (including user feature C-user feature E), the dependency depth of user feature C is 0, the dependency depth of user feature D is 1, and the dependency depth of user feature E is 2. For the dependency chain (including user feature F-user feature I), the dependency depth of user feature F is 0, the dependency depths of user features G and user features H are 1, and the dependency depth of user feature I is 2.

[0109] Optionally, the dependency depth of each second user feature in the dependency chain may be determined in at least two of the following ways:

[0110] First way:

[0111] Initialize the dependency depth corresponding to each second user feature, determine the dependent user feature of the i-th second user feature in the dependency chain, update the dependency depth corresponding to the dependent user feature to the dependency depth of the i-th second user feature plus 1, and determine the dependent user feature as the i+1-th second user feature. Where i is 1, 2, ..., X-1, and X is the number of second user features included in the dependency chain. The first user feature in the dependency chain is the third user feature in the dependency chain.

[0112] The dependency depth corresponding to each second user feature in the dependency chain may be initialized to 0, and the first second user feature may be determined in the dependency chain, and the first second user feature is not dependent on other user features. The dependent user feature of the first second user feature is determined, and the dependency depth of the dependent user feature is updated by the dependency depth corresponding to the first second user feature plus 1. The dependent user feature of the first second user is determined as the second second user feature, and the dependent user feature of the second second user feature is determined, and the dependency depth of the dependent user feature of the second second user feature is updated to the dependency depth of the second second user feature plus 1, and the above process is repeated until i is X.

[0113] For example, see Figure 1 , assuming that the dependency chain is: user feature C depends on user feature D, and user feature D depends on user feature E. Then the dependency depths of user feature C, user feature D, and user feature E can be initialized to 0 respectively, and the first second user feature in the dependency chain is determined to be user feature C, then the dependent user feature of user feature C is determined to be user feature D in the dependency chain, then the dependency depth of user feature D is updated to the dependency depth of user feature C plus 1. Since the dependency depth of user feature C is 0, the dependency depth of user feature D after update is 1. Then user feature D is determined to be the second user feature, and the dependent user feature of user feature D is determined to be user feature E, then the dependency depth of user feature E is updated to the dependency depth of user feature D plus 1. Since the dependency depth of user feature D is 1, the dependency depth of user feature E after update is 2. That is, the dependency depth of user feature C is 0, the dependency depth of user feature D is 1, and the dependency depth of user feature E is 2.

[0114] Second way:

[0115] The dependency depth corresponding to the i-th second user feature in the dependency chain is determined to be i-1, where i is an integer greater than or equal to 1 and less than or equal to X, and X is the number of second user features included in the dependency chain.

[0116] In this manner, the sequence number (position) i of each second user feature in the dependency chain may be determined, and the dependency depth corresponding to the i-th second user feature may be determined as i-1.

[0117] For example, see Figure 1 , assuming that the dependency chain is: user feature C depends on user feature D, and user feature D depends on user feature E. It can be determined that the sequence number of user feature C in the dependency chain is 1, the sequence number of user feature D is 2, and the sequence number of user feature E is 3. Then it can be determined that the dependency depth of user feature C is 0, the dependency depth of user feature D is 1, and the dependency depth of user feature E is 2.

[0118] In this manner, the dependency depth of the user feature can be determined according to the sequence number of the user feature, so that the efficiency of determining the dependency depth of the user feature is high.

[0119] S305 . Verify the second user features in the dependency chain according to the dependency depth K of each second user feature in the dependency chain and the business requirement information of the requested business, and obtain a verification result of the third user feature in the dependency chain.

[0120] The third user feature in the dependency chain refers to the first user feature in the dependency chain. That is, the third user feature is a user feature with a dependency depth of 0 in the dependency chain.

[0121] The second user characteristics in the dependency chain may be verified in the following manner: in descending order of dependency depth, the second user characteristics in the dependency chain are verified in sequence according to the business requirement information of the business to be requested.

[0122] The dependency chain includes the tail second user feature and the non-tail second user feature. The tail second user feature refers to the last second user feature in the dependency chain, and the last second user feature does not depend on other user features in the dependency chain. The verification process of the tail second user feature and the non-tail second user feature is different. The verification process of these two types of second user features is described below.

[0123] For the second user feature at the end, the verification condition corresponding to the second user feature at the end can be obtained in the business demand information, and the second user feature at the end can be verified according to the verification condition. For example, it is determined whether the second user feature at the end satisfies the verification condition. If so, the second user feature at the end is verified, and if not, the second user feature at the end is verified.

[0124] For the non-tail-end second user feature, the dependent user feature of the non-tail-end second user feature can be determined, and the verification result corresponding to the dependent user feature can be obtained; the verification condition corresponding to the non-tail-end second user feature can also be obtained in the business demand information, and the non-tail-end second user feature can be verified according to the verification result corresponding to the dependent user feature and the verification condition corresponding to the non-tail-end second user feature. Specifically, the following two possible implementation methods can be included:

[0125] In one possible implementation, if the verification result corresponding to the dependent user feature is a successful verification, the non-tail-end second user feature is verified according to the verification condition corresponding to the non-tail-end second user feature; if the verification result corresponding to the dependent user feature is a failed verification, it is determined that the verification result corresponding to the non-tail-end second user feature is also a failed verification.

[0126] In another possible implementation, if the verification result corresponding to the dependent user feature is a successful verification, the verification condition corresponding to the successful verification result is obtained, and the non-tail-end second user feature is verified through the verification condition; if the verification result corresponding to the dependent user feature is a failed verification, the verification condition corresponding to the failed verification result is obtained, and the non-tail-end second user feature is verified through the verification condition.

[0127] For example, see Figure 1, assuming that the dependency chain is: user feature C depends on user feature D, and user feature D depends on user feature E. Then, user feature E can be verified first according to the verification condition corresponding to user feature E, and verification result 1 of user feature E can be obtained. Then, user feature D can be verified according to verification result 1 and the verification condition corresponding to user feature D, and verification result 2 of user feature D can be obtained. Then, user feature E can be verified according to verification result 2 and the verification condition corresponding to user feature E, and verification result 3 of user feature E can be obtained. User feature E is the third user feature in the dependency chain.

[0128] Through the above S304 - S305 , the verification result of the third user feature in each dependency chain can be obtained.

[0129] S306: According to the service requirement information of the service to be requested, respectively verify the M first user characteristics to obtain a verification result of each first user characteristic.

[0130] It should be noted that the execution process of S306 can refer to the execution process of S203, which will not be described in detail here.

[0131] S307: Perform service processing on the requested service according to the verification results of the M first user characteristics and the verification result of the at least one third user characteristic.

[0132] It should be noted that the execution process of S307 can refer to the execution process of S205, which will not be described in detail here.

[0133] The business processing method provided in the embodiment of the present application obtains multiple user features of the user after receiving the business processing request of the user, and determines M first user features and N second user features from the multiple user features, wherein there is no dependency relationship between the first user feature and other user features, and there is a dependency relationship between the N second user features. At least one dependency chain is determined among the N second user features, and the M first user features and the user features in each dependency chain are verified and processed respectively according to the business demand information of the requested business, and the business processing is performed on the requested business according to the verification results. In the above process, there is no need to design the verification logic of the business in advance, and there is no need to maintain the verification logic, thereby reducing the complexity of maintaining the business.

[0134] Figure 5 This is a schematic diagram of the structure of a service processing device provided in an embodiment of the present application. Figure 5 The service processing device 10 may include: a receiving module 11, a determining module 12, a verifying module 13 and a processing module 14, wherein:

[0135] The receiving module 11 is used to receive a service processing request, wherein the service processing request includes an identifier of the service to be requested and multiple user characteristics;

[0136] The determining module 12 is used to determine M first user features and N second user features from the multiple user features, there is no dependency relationship between the first user features and other user features, and there is a dependency relationship between the N second user features, M is an integer, and N is a positive integer;

[0137] The verification module 13 is used to verify the M first user characteristics respectively according to the business requirement information of the requested service to obtain a verification result of each first user characteristic;

[0138] The verification module 13 is further used to verify the N second user features according to the service requirement information of the service to be requested, and obtain a verification result of at least one third user feature among the N second user features, wherein the third user feature depends on other user features among the second user features, and the third user feature is not dependent on other user features among the second user features;

[0139] The processing module 14 is configured to perform service processing on the service to be requested according to the verification results of the M first user characteristics and the verification result of the at least one third user characteristic.

[0140] The business processing device 10 shown in the embodiment of the present application can execute the technical solution shown in the above method embodiment, and its implementation principle and beneficial effects are similar, which will not be repeated here.

[0141] In a possible implementation manner, the verification module 13 is specifically used to:

[0142] Determine at least one dependency chain according to the dependency relationship between the N second user features, wherein 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 subsequent user feature;

[0143] According to the business requirement information of the to-be-requested business, the second user feature in each dependency chain is verified respectively.

[0144] In a possible implementation manner, the verification module 13 is specifically used to:

[0145] For any dependency chain, determine the dependency depth K of each second user feature in the dependency chain according to the dependency relationship between the second user features in the dependency chain, where the second user feature is dependent on K user features with different dependency depths, where K is an integer greater than or equal to 0;

[0146] According to the dependency depth K of each second user feature in the dependency chain and the service requirement information of the service to be requested, the second user features in the dependency chain are verified.

[0147] In a possible implementation manner, the verification module 13 is specifically used to:

[0148] Initialize the dependency depth corresponding to each second user feature;

[0149] Determine the dependent user feature of the i-th second user feature in the dependency chain, update the dependency depth corresponding to the dependent user feature to the dependency depth of the i-th second user feature plus 1, determine the dependent user feature as the i+1-th second user feature, and the first user feature in the dependency chain is the third user feature in the dependency chain;

[0150] Here, the i is 1, 2, ..., X-1, and X is the number of second user features included in the dependency chain.

[0151] In a possible implementation manner, the verification module 13 is specifically used to:

[0152] Determine that the dependency depth corresponding to the i-th second user feature in the dependency chain is i-1, wherein i is an integer greater than or equal to 1 and less than or equal to X, and X is the number of second user features included in the dependency chain.

[0153] In a possible implementation manner, the verification module 13 is specifically used to:

[0154] In the order of dependency depth from high to low, and according to the business requirement information of the to-be-requested business, the second user characteristics in the dependency chain are verified in sequence.

[0155] In a possible implementation manner, the processing module 14 is specifically used to:

[0156] If the verification results of the M first user characteristics are successful, and the verification result of the at least one third user characteristic is successful, processing the requested service according to the at least one user characteristic;

[0157] If a verification result of a first user feature among the M first user features is verification failure, or a verification result of a third user feature among the at least one third user feature is verification failure, the requested service is refused to be processed.

[0158] The business processing device 10 shown in the embodiment of the present application can execute the technical solution shown in the above method embodiment, and its implementation principle and beneficial effects are similar, which will not be repeated here.

[0159] Figure 6 This is a schematic diagram of the structure of a service processing device provided in an embodiment of the present application. Figure 6 The service processing device 20 may include: a memory 21 and a processor 22. Exemplarily, the memory 21 and the processor 22 are interconnected via a bus 23.

[0160] The memory 21 is used to store program instructions;

[0161] The processor 22 is used to execute the program instructions stored in the memory, so as to enable the service processing device 20 to execute any of the service processing methods shown above.

[0162] Figure 6 The business processing device shown in the embodiment can execute the technical solution shown in the above method embodiment, and its implementation principle and beneficial effects are similar, which will not be repeated here.

[0163] An embodiment of the present application provides a computer-readable storage medium, in which computer-executable instructions are stored. When the computer-executable instructions are executed by a processor, they are used to implement the above-mentioned business processing method.

[0164] The embodiment of the present application may also provide a computer program product, including a computer program, which can implement the above-mentioned business processing method when executed by a processor.

[0165] All or part of the steps of implementing the above-mentioned method embodiments can be completed by hardware related to program instructions. The aforementioned program can be stored in a readable memory. When the program is executed, the steps of the above-mentioned method embodiments are executed; and the aforementioned memory (storage medium) includes: read-only memory (English: read-only memory, abbreviated: ROM), RAM, flash memory, hard disk, solid state drive, magnetic tape (English: magnetic tape), floppy disk (English: floppy disk), optical disc (English: optical disc) and any combination thereof.

[0166] The embodiments of the present application are described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processing unit of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processing unit of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0167] These computer program instructions may also be stored in a computer readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer readable memory produce an article of manufacture including an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0168] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0169] Obviously, those skilled in the art can make various changes and modifications to the embodiments of the present application without departing from the spirit and scope of the present application. Thus, if these 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 include these modifications and variations.

[0170] In the present application, the term "include" and its variations may refer to non-restrictive inclusion; the term "or" and its variations may refer to "and / or". The terms "first", "second", etc. in this application are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. In the present application, "plurality" refers to two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B may mean: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the previously associated objects are in an "or" relationship.

Claims

1. A business processing method, characterized in that: include: receiving a service processing request, wherein the service processing request includes an identifier of a service to be requested and a plurality of user characteristics; Determine M first user features and N second user features from the multiple user features, there is no dependency relationship between the first user feature and other user features, there is a dependency relationship between the N second user features, M is an integer, and N is a positive integer; According to the business requirement information of the service to be requested, the M first user characteristics are respectively verified to obtain a verification result of each first user characteristic; wherein the business requirement information includes a verification condition corresponding to each first user characteristic and a verification condition corresponding to the second user characteristic; According to the service requirement information of the service to be requested, verification processing is performed on the N second user features to obtain a verification result of at least one third user feature among the N second user features, where the third user feature depends on other user features among the second user features, and the third user feature is not dependent on other user features among the second user features; The service to be requested is processed according to the verification results of the M first user characteristics and the verification result of the at least one third user characteristic.

2. The method according to claim 1, characterized in that According to the service requirement information of the service to be requested, verification processing is performed on the N second user characteristics, including: Determine at least one dependency chain according to the dependency relationship between the N second user features, wherein 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 subsequent user feature; According to the business requirement information of the to-be-requested business, the second user feature in each dependency chain is verified respectively.

3. The method according to claim 2, characterized in that For any dependency chain, according to the business requirement information of the service to be requested, verifying the second user feature in the dependency chain includes: Determine, according to the dependency relationship between the second user features in the dependency chain, a dependency depth K of each second user feature in the dependency chain, wherein the second user feature is dependent on K user features with different dependency depths, and K is an integer greater than or equal to 0; According to the dependency depth K of each second user feature in the dependency chain and the service requirement information of the service to be requested, the second user features in the dependency chain are verified.

4. The method according to claim 3, characterized in that Determining the dependency depth K of each second user feature in the dependency chain includes: Initialize the dependency depth corresponding to each second user feature; Determine the dependent user feature of the i-th second user feature in the dependency chain, update the dependency depth corresponding to the dependent user feature to the dependency depth of the i-th second user feature plus 1, determine the dependent user feature as the i+1-th second user feature, and the first user feature in the dependency chain is the third user feature in the dependency chain; Here, the i is 1, 2, ..., X-1, and X is the number of second user features included in the dependency chain.

5. The method according to claim 3, characterized in that: Determining the dependency depth K of each second user feature in the dependency chain includes: Determine that the dependency depth corresponding to the i-th second user feature in the dependency chain is i-1, wherein i is an integer greater than or equal to 1 and less than or equal to X, and X is the number of second user features included in the dependency chain.

6. The method according to any one of claims 3 to 5, characterized in that: According to the dependency depth K of each second user feature in the dependency chain and the service requirement information of the service to be requested, the second user features in the dependency chain are verified, including: In the order of dependency depth from high to low, and according to the business requirement information of the to-be-requested business, the second user characteristics in the dependency chain are verified in sequence.

7. The method according to any one of claims 1 to 5, characterized in that: According to the verification results of the M first user characteristics and the verification result of the at least one third user characteristic, performing service processing on the service to be requested includes: If the verification results of the M first user characteristics are successful, and the verification result of the at least one third user characteristic is successful, processing the requested service according to the at least one user characteristic; If a verification result of a first user feature among the M first user features is verification failure, or a verification result of a third user feature among the at least one third user feature is verification failure, the requested service is refused to be processed.

8. A service processing device, characterized in that: include: A receiving module, a determining module, a verifying module and a processing module, wherein: The receiving module is used to receive a service processing request, wherein the service processing request includes an identifier of the service to be requested and multiple user characteristics; The determination module is used to determine M first user features and N second user features from the multiple user features, there is no dependency relationship between the first user feature and other user features, and there is a dependency relationship between the N second user features, M is an integer, and N is a positive integer; The verification module is used to verify the M first user characteristics respectively according to the business requirement information of the service to be requested, and obtain the verification result of each first user characteristic; wherein the business requirement information includes the verification condition corresponding to each first user characteristic and the verification condition corresponding to the second user characteristic; The verification module is further used to, according to the service requirement information of the service to be requested, perform verification processing on the N second user characteristics to obtain a verification result of at least one third user characteristic among the N second user characteristics, wherein the third user characteristic depends on other user characteristics among the second user characteristics, and the third user characteristic is not dependent on other user characteristics among the second user characteristics; The processing module is used to perform service processing on the service to be requested according to the verification results of the M first user characteristics and the verification result of the at least one third user characteristic.

9. A service processing device, characterized in that: include: Processor, memory; The memory stores computer-executable instructions; The processor executes the computer-executable instructions stored in the memory, so that the processor executes the business processing method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer-executable instructions, which are used to implement the business processing method according to any one of claims 1 to 7 when executed by a processor.

11. A computer program product, characterized in that It comprises a computer program, which, when executed by a processor, implements the business processing method shown in any one of claims 1 to 7.

Images