CN113313530A - Business information pushing method, equipment, storage medium and product - Google Patents

Business information pushing method, equipment, storage medium and product Download PDF

Info

Publication number
CN113313530A
CN113313530A CN202110669545.1A CN202110669545A CN113313530A CN 113313530 A CN113313530 A CN 113313530A CN 202110669545 A CN202110669545 A CN 202110669545A CN 113313530 A CN113313530 A CN 113313530A
Authority
CN
China
Prior art keywords
verification
information
result
check
verification result
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
CN202110669545.1A
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 CN202110669545.1A priority Critical patent/CN113313530A/en
Publication of CN113313530A publication Critical patent/CN113313530A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION 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
    • G06Q30/00—Commerce
    • G06Q30/02—Marketing; Price estimation or determination; Fundraising
    • G06Q30/0207—Discounts or incentives, e.g. coupons or rebates
    • G06Q30/0224—Discounts or incentives, e.g. coupons or rebates based on user history
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION 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
    • G06Q30/00—Commerce
    • G06Q30/06—Buying, selling or leasing transactions
    • G06Q30/0601—Electronic shopping [e-shopping]
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION 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
    • G06Q30/00—Commerce
    • G06Q30/06—Buying, selling or leasing transactions
    • G06Q30/0601—Electronic shopping [e-shopping]
    • G06Q30/0631—Item recommendations
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/55—Push-based network services

Abstract

The application provides a method, equipment, a storage medium and a product for pushing service information, wherein the method comprises the following steps: acquiring characteristic information of a user; performing a verification operation on the attribute information to obtain a first verification result; determining a second verification result of the characteristic information according to the first verification result and verification passing conditions of the characteristic information, wherein the verification passing conditions comprise attribute information verification success and/or dependence information verification success; and when the second check result is that the check is successful, pushing the service information to the user. For products which are not suitable for all users, when service pushing is carried out, corresponding product parameter verification can be carried out on the users in advance, the service pushing is carried out on the users only when the users meet the condition that attribute information verification is successful and/or dependence information verification is successful, otherwise, the service pushing is not carried out, and therefore pertinence of service recommendation is improved, network resource waste is avoided, and the acceptance of the users on the products is improved.

Description

Business information pushing method, equipment, storage medium and product
Technical Field
The present application relates to the field of network technologies, and in particular, to a method, an apparatus, a storage medium, and a product for pushing service information.
Background
With the development of network technology, a service publisher may publish different service information to a user in a network push manner, where the service information may specifically be to display at least one service object to the user, and the service object may be, for example, a product provided to the user. After receiving the service information pushed by the service publisher, the user may select one of the displayed service objects and apply for performing processing on the selected service object, for example, purchasing the product.
At present, a service publisher usually performs service push to multiple users at the same time, however, not all users are all suitable for products pushed by the service publisher, and thus, the existing service push method has a problem of low pertinence.
Disclosure of Invention
The application provides a method, equipment, a storage medium and a product for pushing service information, which are used for solving the problems in the prior art.
In a first aspect, the present application provides a method for pushing service information, including:
acquiring feature information of a user, wherein the feature information comprises attribute information of the user and dependency information which has a dependency relationship with the attribute information;
performing a verification operation on the attribute information to obtain a first verification result;
determining a second verification result of the characteristic information according to the first verification result and a verification passing condition of the characteristic information, wherein the verification passing condition comprises that attribute information verification is successful and/or dependency information verification is successful;
and when the second check result is that the check is successful, pushing service information to the user.
In some embodiments, the obtaining the feature information of the user includes:
acquiring attribute information;
and acquiring the dependency information corresponding to the attribute information according to a preset dependency relationship.
In some embodiments, the determining a second verification result of the feature information according to the first verification result and the verification passing condition of the feature information includes:
determining whether to execute verification operation on the dependent information according to a first verification result and a verification passing condition of the characteristic information;
if the fact that the verification operation is executed on the dependent information is determined, determining a second verification result of the characteristic information according to the first verification result and a third verification result of the dependent information;
and if the dependent information is determined not to be subjected to the verification operation, determining the first verification result as a second verification result of the characteristic information.
In some embodiments, when the verification passing condition includes that the attribute information verification is successful and the dependent information verification is successful, if the first verification result is verification success, it is determined that a verification operation is performed on the dependent information;
correspondingly, the determining a second check result of the feature information according to the first check result and the third check result of the dependency information includes:
if the third verification result is verification success, determining that the second verification result is verification success;
and if the third verification result is verification failure, determining that the second verification result is verification failure.
In some embodiments, when the verification passing condition includes that the attribute information verification is successful or the dependent information verification is successful, if the first verification result is verification failure, it is determined that a verification operation is performed on the dependent information;
correspondingly, the determining a second check result of the feature information according to the first check result and the third check result of the dependency information includes:
if the third verification result is verification failure, determining that the second verification result is verification failure;
and if the third verification result is verification success, determining that the second verification result is verification success.
In some embodiments, when the verification passing condition includes that the attribute information verification is successful and the dependent information verification is successful, if the first verification result is verification failure, it is determined that the verification operation is not performed on the dependent information;
correspondingly, the determining the first verification result as the second verification result of the feature information includes:
and determining that the second check result is check failure.
In some embodiments, when the verification passing condition includes that the attribute information verification is successful or the dependent information verification is successful, if the first verification result is verification success, it is determined that the verification operation is not performed on the dependent information;
correspondingly, the determining the first verification result as the second verification result of the feature information includes:
and determining that the second check result is successful.
In a second aspect, the present application provides a computer device comprising: the system comprises a memory, a processor and a computer program which is stored on the memory and can run on the processor, wherein the processor executes the program to realize the business information pushing method.
In a third aspect, the present application provides a computer-readable storage medium, in which computer-executable instructions are stored, and the computer-executable instructions are executed by a processor to implement the above-mentioned service information pushing method.
In a fourth aspect, the present application provides a computer program product, which includes a computer program, and when the computer program is executed by a processor, the computer program implements the pushing method of the service information.
According to the method, the device, the storage medium and the product for pushing the service information, when the product which is not suitable for all users is pushed with the service, corresponding product parameter verification can be carried out on the users in advance, the service is pushed to the users only when the users meet the requirement that attribute information verification is successful and/or dependence information verification is successful, otherwise, the service is not pushed, so that the pertinence of service recommendation is improved, network resource waste is avoided, and the acceptance of the products by the users is improved.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and together with the description, serve to explain the principles of the disclosure.
Fig. 1 is a schematic diagram of an application scenario of service push;
fig. 2 is a schematic diagram of a method for pushing service information according to an embodiment of the present application;
fig. 3 is a schematic diagram of a processing flow of a method for pushing service information according to an embodiment of the present application;
fig. 4 is a schematic diagram of a service information pushing apparatus provided in an embodiment of the present application;
fig. 5 is a schematic structural diagram of a computer device according to an embodiment of the present application.
With the foregoing drawings in mind, certain embodiments of the disclosure have been shown and described in more detail below. These drawings and written description are not intended to limit the scope of the disclosed concepts in any way, but rather to illustrate the concepts of the disclosure to those skilled in the art by reference to specific embodiments.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
The terminology used in the embodiments of the present application is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used in the embodiments of the present application, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.
It should be understood that the term "and/or" as used herein is merely one type of association that describes an associated object, meaning that three relationships may exist, e.g., a and/or B may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the characters "three" in this document generally indicate that the former and latter associated objects are in an "or" relationship.
The words "if", as used herein, may be interpreted as "at … …" or "at … …" or "in response to a determination" or "in response to a detection", depending on the context. Similarly, the phrases "if determined" or "if detected (a stated condition or event)" may be interpreted as "when determined" or "in response to a determination" or "when detected (a stated condition or event)" or "in response to a detection (a stated condition or event)", depending on the context.
It is also noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a good or system that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such good or system. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a commodity or system that includes the element.
With the development of network technology, a service publisher may publish different service information to a user in a network push manner, where the service information may specifically be to display at least one service object to the user, and the service object may be, for example, a product provided to the user. After receiving the service information pushed by the service publisher, the user may select one of the displayed service objects and apply for performing processing on the selected service object, for example, purchasing the product.
For example, fig. 1 is a schematic diagram of an application scenario of service push, as shown in fig. 1, the application scenario includes a user terminal 10 and a server 20, the server 20 serves as a provider of a service object, and the service object provided to the user terminal 10 may be a product. The user terminal 10 may be a device for the user to receive the service object, for example, the user terminal 10 may be a computer or a smart mobile device, and the product provided by the server 20 may be displayed through the screen of the user terminal 10, for example, product introduction information of the product may be displayed, or product purchase information of the product purchased by the user may be displayed.
At present, a service publisher usually performs service push to multiple users at the same time, however, not all users are all suitable for the product pushed by the service publisher, and a user suitable for the product may purchase the product, but a user not suitable for the product does not perform product purchase, thereby resulting in waste of network resources and low acceptance of the product by the user. Therefore, the existing service push method has the problem of low pertinence.
The application provides a method, a device, a storage medium and a product for pushing service information, and aims to solve the above technical problems in the prior art.
The main conception of the scheme of the application is as follows: for products which are not suitable for all users, when service pushing is carried out, corresponding service pushing conditions can be set, for example, service related information of the users is verified, and the like, so that when the service pushing is carried out, the service pushing is carried out only for the users with successful information verification, and for the users with failed information verification, the service pushing is not carried out, and therefore the pertinence of service recommendation is improved, the waste of network resources is avoided, and the acceptance of the users to the products is improved.
The following describes the technical solutions of the present application and how to solve the above technical problems with specific embodiments. The following several specific embodiments may be combined with each other, and details of the same or similar concepts or processes may not be repeated in some embodiments. Embodiments of the present application will be described below with reference to the accompanying drawings.
It is understood that the processing steps of the pushing method of the service information in the present application may be implemented by a device with a service information pushing function, such as the server 20 in fig. 1.
Fig. 2 is a schematic diagram of a method for pushing service information provided in an embodiment of the present application, and as shown in fig. 2, the method is explained by taking a method applied to a server as an example, and the method mainly includes the following steps:
s100, acquiring characteristic information of a user, wherein the characteristic information comprises attribute information of the user and dependency information which has a dependency relationship with the attribute information;
the characteristic information of the user corresponds to a product condition parameter of the business product, and the product condition parameter is used for verifying the product. The product parameter verification refers to verifying whether the characteristic information of the user meets a certain verification condition or not, and performing different processing according to a verification result.
For example, the characteristic information of the user may specifically refer to basic information such as gender, age, occupation, and the like of the user. The dependency information may specifically refer to a white list, a black list, whether the push belongs to the first push, and the like. The product verification can be to verify whether the basic information of the user, such as gender, age, occupation and the like, meets corresponding requirements, and to verify whether the user belongs to a white list user, a black list user and the like.
In addition, because of the variety of products, in order to facilitate management, the concept of a product factory is provided, and the product factory refers to the idea of dividing automobile manufacturing modularization into automobile body manufacturing, chassis manufacturing and the like by considering that the automobile manufacturing industry simplifies a manufacturing platform, and classifies, modularizes and parameterizes the products through product modeling. For most product innovation requirements, a basic product can be used as a template, and a new saleable product can be quickly assembled by setting and limiting values of relevant parameters.
In parameterizing a product plant, there may be dependencies between different product parameters. For example, a specific occupation to which a certain product is oriented is a teacher, and meanwhile, the business product is added with a white list function, so that the user can push the product as long as the user is in the white list, and the product is not limited to the occupation which must be the teacher.
Specifically, the parameter dependency means that when a product is pushed, a parameter of the product needs to be verified, and different parameters have dependency relationships, for example, the parameter a depends on the parameter B, so that if the parameter B passes the verification, the parameter a passes the result of the parameter B to verify the parameter a.
Optionally, when modeling a product, different product condition parameters may be set to have a dependency relationship for different products, and the dependency relationship may be divided into an and an or, where the and indicates that the final verification result is successful when both of the two parties verify successfully, or indicates that the final verification result is successful when either of the two parties verifies successfully.
Optionally, for different product condition parameters, corresponding parameter verification components may be designed in advance, and after the characteristic information of the user is obtained, product parameter verification is performed based on the characteristic information, so as to obtain corresponding verification results.
Optionally, parameter classification may be performed in advance for different product condition parameters, and product condition parameters belonging to the same class may have a dependency relationship, so as to form a product parameter dependency group. In addition, there may be a dependency relationship between different types of product condition parameters, which is not limited in this embodiment.
S200, performing verification operation on the attribute information to obtain a first verification result;
after acquiring the attribute information of the user and the dependency information having a dependency relationship with the attribute information, the server first performs a corresponding verification operation on the attribute information to obtain a first verification result.
For example, taking the attribute information of the user including the age as an example, if the age of the user is 26 years, and the parameter verification condition corresponding to the product is that the age is between 18 and 40 years, the server may determine that the age of the user meets the requirement, and that is, the first verification result is verification success.
In the embodiments of the present application, a successful verification means that the verification passes, and correspondingly, a failed verification means that the verification fails.
S300, determining a second verification result of the characteristic information according to the first verification result and verification passing conditions of the characteristic information, wherein the verification passing conditions comprise attribute information verification success and/or dependence information verification success;
since the dependency relationship of the product condition parameters includes two types, namely "and" or ", the verification passing condition of the feature information also includes two types, namely, the verification passing condition includes that the attribute information is verified successfully and/or the dependency information is verified successfully, so that the server can determine a second verification result of the feature information based on the first verification result and the verification passing condition of the feature information, and the second verification result is a final verification result of the user.
S400, when the second check result is that the check is successful, pushing the service information to the user.
After the server obtains the second check result, the second check result can be regarded as the final check result of the user, therefore, if the second check result is successful in check, the server pushes the service information to the user, otherwise, the server does not push the service information to the user.
The embodiment provides a method for pushing service information, which can be used for carrying out corresponding product parameter verification on a user in advance when a product which is not suitable for all users is pushed, and only when the user successfully verifies attribute information and/or successfully verifies dependent information, the service is pushed to the user, otherwise, the service is not pushed, so that the pertinence of service recommendation is improved, the waste of network resources is avoided, and the acceptance of the product by the user is improved.
In some embodiments, obtaining the characteristic information of the user comprises:
s110, acquiring attribute information;
and S120, acquiring the dependency information corresponding to the attribute information according to the preset dependency relationship.
Specifically, when the characteristic information of the user is obtained, the server first obtains the attribute information of the user, further determines whether the attribute information or the product service has a preset dependency relationship after obtaining the attribute information of the user, and if so, further obtains the dependency information corresponding to the attribute information according to the preset dependency relationship, thereby facilitating the verification of the product parameters.
It can be understood that if there are multiple layers of dependencies, all the information with dependencies can be checked by a recursive algorithm.
In some embodiments, determining the second verification result of the feature information according to the first verification result and the verification passing condition of the feature information includes:
s310, determining whether to execute verification operation on the dependent information according to the first verification result and the verification passing condition of the characteristic information;
s320, if the fact that the verification operation is executed on the dependent information is determined, determining a second verification result of the characteristic information according to the first verification result and a third verification result of the dependent information;
s330, if the fact that the verification operation is not executed on the dependent information is determined, the first verification result is determined to be a second verification result of the characteristic information.
Specifically, since the verification passing condition includes that the attribute information is successfully verified and/or the dependent information is successfully verified, after the server obtains the first verification result, it is determined whether the verification operation needs to be performed on the dependent information according to the first verification result and the verification passing condition of the feature information.
When the server determines that the verification operation needs to be executed on the dependent information, the server further executes the verification operation on the dependent information to obtain a third verification result of the dependent information, so that the server can determine a second verification result of the feature information according to the first verification result and the third verification result to obtain a final verification result of the user.
In addition, when the server determines that the verification operation does not need to be performed on the dependent information, the server may directly use the first verification result as the second verification result of the feature information, that is, use the first verification result as the final verification result of the user.
Therefore, based on different verification passing conditions, the server further determines whether verification operation needs to be executed on the dependent information, further determines a second verification result of the characteristic information, and obtains a final verification result of the user, so as to determine whether to push the service to the user.
In some embodiments, when the verification passing condition includes that the attribute information is verified successfully and the dependent information is verified successfully, if the first verification result is verification success, it is determined that the verification operation is performed on the dependent information;
correspondingly, determining a second check result of the feature information according to the first check result and a third check result of the dependency information, including: if the third verification result is successful, determining that the second verification result is successful; and if the third verification result is verification failure, determining that the second verification result is verification failure.
Specifically, when the verification passing condition includes that the attribute information is successfully verified and the dependent information is successfully verified, it is described that the dependency relationship between the attribute information and the dependent information is an and, at this time, if the first verification result is successful, the server cannot determine the final verification result of the user, and therefore, the verification operation needs to be performed on the dependent information.
If the third verification result is successful, the verification passing condition is that the attribute information verification is successful and the dependent information verification is successful, and the verification passing condition is met, so that the server can determine that the second verification result is successful, that is, the final verification result of the user is successful. For example, if the dependency information includes white list information, it is determined that the dependency information of the user is verified successfully if the user is in the white list.
In addition, if the third verification result is verification failure, since the verification passing conditions are attribute information verification success and dependent information verification success, and the verification passing conditions are not satisfied, the server can determine that the second verification result is verification failure, that is, the final verification result of the user is failure.
In some embodiments, when the verification passing condition includes that the attribute information verification is successful or the dependent information verification is successful, if the first verification result is verification failure, it is determined that the verification operation is performed on the dependent information;
correspondingly, determining a second check result of the feature information according to the first check result and a third check result of the dependency information, including: if the third verification result is verification failure, determining that the second verification result is verification failure; and if the third verification result is successful verification, determining that the second verification result is successful verification.
Specifically, when the verification passing condition includes that the attribute information is verified successfully or the dependent information is verified successfully, it is described that the dependency relationship between the attribute information and the dependent information is "or", at this time, if the first verification result is verification failure, the server cannot determine the final verification result of the user, and therefore, the verification operation needs to be performed on the dependent information.
If the third verification result is successful, the verification passing condition is that the attribute information verification is successful or the dependency information verification is successful, and the verification passing condition is met, so that the server can determine that the second verification result is successful, that is, the final verification result of the user is successful.
In addition, if the third verification result is a verification failure, since the verification passing condition is that the attribute information verification is successful or the dependent information verification is successful, and the verification passing condition is not satisfied, the server may determine that the second verification result is a verification failure, that is, determine that the final verification result of the user is a failure.
In some embodiments, when the verification passing condition includes that the attribute information is verified successfully and the dependent information is verified successfully, if the first verification result is verification failure, it is determined that the verification operation is not performed on the dependent information;
correspondingly, the determining the first check result as the second check result of the feature information includes: and determining that the second check result is a check failure.
Specifically, when the verification passing condition includes that the attribute information is successfully verified and the dependent information is successfully verified, it is described that the dependency relationship between the attribute information and the dependent information is an and, at this time, if the first verification result is a verification failure, since the server can directly determine that the final verification result of the user is a verification failure, it is not necessary to perform a verification operation on the dependent information.
Since the first check result is a check failure, the check passing conditions are an attribute information check success and a dependent information check success, and the current check result does not satisfy the check passing conditions, the server can determine that the second check result is a check failure, that is, the final check result of the user is a failure.
In some embodiments, when the verification passing condition includes that the attribute information verification is successful or the dependent information verification is successful, if the first verification result is successful, it is determined that the verification operation is not performed on the dependent information;
correspondingly, the determining the first check result as the second check result of the feature information includes: and determining that the second check result is successful.
Specifically, when the verification passing condition includes that the attribute information is verified successfully or the dependent information is verified successfully, it is described that the dependency relationship between the attribute information and the dependent information is "or", and at this time, if the first verification result is verified successfully, since the server can directly determine that the final verification result of the user is verified successfully, it is not necessary to perform verification operation on the dependent information.
The server can determine that the second verification result is successful, that is, the final verification result of the user is successful.
In some embodiments, the process flow of the present application is explained.
Fig. 3 is a schematic view of a processing flow of a method for pushing service information according to an embodiment of the present application, where as shown in fig. 3, the processing flow includes the following steps:
s1, acquiring attribute information of the user, and verifying the attribute information to obtain a first verification result;
s2, judging whether the first checking result is successful, if so, executing a step S3, and if not, executing a step S6;
s3, obtaining the dependency information which has dependency relationship with the attribute information, if the dependency relationship is AND, executing the step S4, if the dependency relationship is OR, executing the step S5;
s4, judging whether the third check result corresponding to the dependency information is successful, if so, determining that the final second check result is successful, and executing the step S9;
if the verification fails, determining that the final second verification result is verification failure;
s5, determining that the final second check result is successful, and executing the step S9;
s6, obtaining the dependency information which has dependency relationship with the attribute information, if the dependency relationship is AND, executing the step S7, if the dependency relationship is OR, executing the step S8;
s7, determining that the final second check result is check failure;
s8, judging whether the third check result corresponding to the dependency information is successful, if so, determining that the final second check result is successful, and executing the step S9;
and if the verification fails, determining that the final second verification result is verification failure.
And S9, pushing the service information to the user.
It should be understood that, although the respective steps in the flowcharts in the above-described embodiments are sequentially shown as indicated by arrows, the steps are not necessarily performed sequentially as indicated by the arrows. The steps are not performed in the exact order shown and may be performed in other orders unless explicitly stated herein. Moreover, at least some of the steps in the figures may include multiple sub-steps or multiple stages that are not necessarily performed at the same time, but may be performed at different times, in different orders, and may be performed alternately or at least partially with respect to other steps or sub-steps of other steps.
In some embodiments, a pushing device for service information is provided.
Fig. 4 is a schematic diagram of a service information pushing apparatus provided in an embodiment of the present application, and as shown in fig. 4, the apparatus includes:
an information obtaining module 100, configured to obtain feature information of a user, where the feature information includes attribute information of the user and dependency information that has a dependency relationship with the attribute information;
the first checking module 200 is configured to perform a checking operation on the attribute information to obtain a first checking result;
the second checking module 300 is configured to determine a second checking result of the feature information according to the first checking result and a checking passing condition of the feature information, where the checking passing condition includes that the attribute information is successfully checked and/or the dependent information is successfully checked;
and the service pushing module 400 is configured to push the service information to the user when the second check result is that the check is successful.
For specific limitation of the service information pushing device, reference may be made to the above limitation on the service information pushing method, which is not described herein again. All or part of the modules in the service information pushing device can be realized by software, hardware and a combination thereof. The modules can be embedded in a hardware form or independent from a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.
The application provides a service information pushing device, when a product which is not suitable for all users is pushed, corresponding product parameter verification can be carried out on the user in advance, service pushing is carried out on the user only when the user meets the condition that attribute information verification is successful and/or dependence information verification is successful, otherwise, service pushing is not carried out, accordingly, pertinence of service recommendation is improved, waste of network resources is avoided, and acceptance of the user on the product is improved.
In some embodiments, there is provided a computer device comprising: the system comprises a memory, a processor and a computer program stored on the memory and capable of running on the processor, wherein the processor executes the program to realize the steps of the method embodiments of the application.
Fig. 5 is a schematic structural diagram of a computer device according to an embodiment of the present application, and as shown in fig. 5, the computer device includes: a processor 111, and a memory 112.
The memory 112 is used for storing programs and data, and the processor 111 calls the programs stored in the memory to execute the technical scheme of any one of the method embodiments.
In the above computer devices, the memory and the processor are electrically connected directly or indirectly to enable data transmission or interaction. For example, the components may be electrically connected to each other via one or more communication buses or signal lines, such as a bus. The memory stores computer-executable instructions for implementing the data access control method, and includes at least one software functional module which can be stored in the memory in the form of software or firmware, and the processor executes various functional applications and data processing by running the software programs and modules stored in the memory.
The Memory may be, but is not limited to, a Random Access Memory (RAM), a Read Only Memory (ROM), a Programmable Read Only Memory (PROM), an Erasable Read Only Memory (EPROM), an electrically Erasable Read Only Memory (EEPROM), and the like. The memory is used for storing programs, and the processor executes the programs after receiving the execution instructions. Further, the software programs and modules within the aforementioned memories may also include an operating system, which may include various software components and/or drivers for managing system tasks (e.g., memory management, storage device control, power management, etc.), and may communicate with various hardware or software components to provide an operating environment for other software components.
The processor may be an integrated circuit chip having signal processing capabilities. The Processor may be a general-purpose Processor including a Central Processing Unit (CPU), a Network Processor (NP), and the like. The various methods, steps, and logic blocks disclosed in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
In some embodiments, a computer-readable storage medium having stored thereon computer-executable instructions for performing the steps of the method embodiments of the present application when executed by a processor is provided.
In some embodiments, a computer program product is provided, comprising a computer program which, when executed by a processor, performs the steps of the method embodiments of the present application.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware related to instructions of a computer program, which can be stored in a non-volatile computer-readable storage medium, and when executed, the computer program can include the processes of the embodiments of the methods described above. Any reference to memory, storage, database, or other medium used in the embodiments provided herein may include non-volatile and/or volatile memory, among others. Non-volatile memory can include read-only memory (ROM), Programmable ROM (PROM), Electrically Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDRSDRAM), Enhanced SDRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), Rambus Direct RAM (RDRAM), direct bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).
Other embodiments of the present disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the application disclosed herein. This application is intended to cover any variations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.
It will be understood that the present disclosure is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims (10)

1. A method for pushing service information is characterized by comprising the following steps:
acquiring feature information of a user, wherein the feature information comprises attribute information of the user and dependency information which has a dependency relationship with the attribute information;
performing a verification operation on the attribute information to obtain a first verification result;
determining a second verification result of the characteristic information according to the first verification result and a verification passing condition of the characteristic information, wherein the verification passing condition comprises that attribute information verification is successful and/or dependency information verification is successful;
and when the second check result is that the check is successful, pushing service information to the user.
2. The method of claim 1, wherein the obtaining the feature information of the user comprises:
acquiring attribute information;
and acquiring the dependency information corresponding to the attribute information according to a preset dependency relationship.
3. The method according to claim 1, wherein the determining a second verification result of the feature information according to the first verification result and the verification passing condition of the feature information comprises:
determining whether to execute verification operation on the dependent information according to a first verification result and a verification passing condition of the characteristic information;
if the fact that the verification operation is executed on the dependent information is determined, determining a second verification result of the characteristic information according to the first verification result and a third verification result of the dependent information;
and if the dependent information is determined not to be subjected to the verification operation, determining the first verification result as a second verification result of the characteristic information.
4. The method according to claim 3, wherein when the verification passing condition includes that the attribute information is verified successfully and the dependent information is verified successfully, if the first verification result is verification success, it is determined that a verification operation is performed on the dependent information;
correspondingly, the determining a second check result of the feature information according to the first check result and the third check result of the dependency information includes:
if the third verification result is verification success, determining that the second verification result is verification success;
and if the third verification result is verification failure, determining that the second verification result is verification failure.
5. The method according to claim 3, wherein when the check-passing condition includes that the attribute information check is successful or the dependent information check is successful, if the first check result is a check failure, it is determined that a check operation is performed on the dependent information;
correspondingly, the determining a second check result of the feature information according to the first check result and the third check result of the dependency information includes:
if the third verification result is verification failure, determining that the second verification result is verification failure;
and if the third verification result is verification success, determining that the second verification result is verification success.
6. The method according to claim 3, wherein when the verification passing condition includes that the attribute information is verified successfully and the dependent information is verified successfully, if the first verification result is verification failure, it is determined that the verification operation is not performed on the dependent information;
correspondingly, the determining the first verification result as the second verification result of the feature information includes:
and determining that the second check result is check failure.
7. The method according to claim 3, wherein when the check-passing condition includes that the attribute information is successfully checked or the dependent information is successfully checked, if the first check result is successful, it is determined that the check operation is not performed on the dependent information;
correspondingly, the determining the first verification result as the second verification result of the feature information includes:
and determining that the second check result is successful.
8. A computer device, comprising: memory, processor and computer program stored on the memory and executable on the processor, the processor implementing the pushing method of service information according to any of the preceding claims 1-7 when executing the program.
9. A computer-readable storage medium, wherein computer-executable instructions are stored in the computer-readable storage medium, and when executed by a processor, the computer-executable instructions are configured to implement the method for pushing service information according to any one of claims 1 to 7.
10. A computer program product comprising a computer program, characterized in that the computer program, when being executed by a processor, implements the method for pushing service information according to any of the preceding claims 1-7.
CN202110669545.1A 2021-06-16 2021-06-16 Business information pushing method, equipment, storage medium and product Pending CN113313530A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202110669545.1A CN113313530A (en) 2021-06-16 2021-06-16 Business information pushing method, equipment, storage medium and product

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202110669545.1A CN113313530A (en) 2021-06-16 2021-06-16 Business information pushing method, equipment, storage medium and product

Publications (1)

Publication Number Publication Date
CN113313530A true CN113313530A (en) 2021-08-27

Family

ID=77379128

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202110669545.1A Pending CN113313530A (en) 2021-06-16 2021-06-16 Business information pushing method, equipment, storage medium and product

Country Status (1)

Country Link
CN (1) CN113313530A (en)

Similar Documents

Publication Publication Date Title
CN109474578B (en) Message checking method, device, computer equipment and storage medium
CN109039751B (en) Method, device, computer equipment and storage medium for configuring route
CN107729452B (en) Webpage loading method and device, electronic equipment and computer readable storage medium
CN113448862B (en) Software version testing method and device and computer equipment
CN111858376A (en) Request message generation method and interface test method
CN108845869B (en) Concurrent request control method, device, computer equipment and storage medium
CN111124871A (en) Interface test method and device
CN111581078B (en) Business abnormality positioning method and device, computer equipment and storage medium
CN110855529B (en) Network information security monitoring method, device, server and readable storage medium
CN109658542B (en) Diagnostic parameter data verification method, diagnostic parameter data verification device, vehicle diagnostic equipment and storage medium
CN113656107A (en) Mobile application loading method and device and electronic equipment
CN113313530A (en) Business information pushing method, equipment, storage medium and product
CN112181836A (en) Test case generation method, system, device and storage medium
CN112559363A (en) Test case generation method, system, equipment and medium based on full link marking
CN112306041A (en) Vehicle configuration information writing method and device and electronic equipment
CN111047322A (en) Intelligent contract deployment method and device based on block chain and hardware equipment
CN111324540A (en) Interface testing method and device
CN114168108A (en) Code merging method and device, electronic equipment and computer readable storage medium
CN112115057A (en) Automatic test method, device and equipment for application program page building process
CN111563038A (en) SDK test method, device, computer equipment and computer readable storage medium
CN116993396B (en) Risk early warning method based on vehicle user tag and computer equipment
CN114124532B (en) Data transmission method and device, electronic equipment and storage medium
CN114911467B (en) Code detection method, device, electronic equipment and storage medium
CN115481028A (en) Test method and device in program development process and server
CN112464088B (en) Recommendation request response method and device and recommendation system development method

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