CN113590252B - Information pushing method and device, electronic equipment and storage medium - Google Patents

Information pushing method and device, electronic equipment and storage medium Download PDF

Info

Publication number
CN113590252B
CN113590252B CN202110907444.3A CN202110907444A CN113590252B CN 113590252 B CN113590252 B CN 113590252B CN 202110907444 A CN202110907444 A CN 202110907444A CN 113590252 B CN113590252 B CN 113590252B
Authority
CN
China
Prior art keywords
service
target
information
policy data
account
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.)
Active
Application number
CN202110907444.3A
Other languages
Chinese (zh)
Other versions
CN113590252A (en
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.)
Beijing Dajia Internet Information Technology Co Ltd
Original Assignee
Beijing Dajia Internet Information Technology Co Ltd
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 Beijing Dajia Internet Information Technology Co Ltd filed Critical Beijing Dajia Internet Information Technology Co Ltd
Priority to CN202110907444.3A priority Critical patent/CN113590252B/en
Publication of CN113590252A publication Critical patent/CN113590252A/en
Application granted granted Critical
Publication of CN113590252B publication Critical patent/CN113590252B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/451—Execution arrangements for user interfaces
    • G06F9/453—Help systems
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90—Details of database functions independent of the retrieved data types
    • G06F16/95—Retrieval from the web
    • G06F16/953—Querying, e.g. by the use of web search engines
    • G06F16/9535—Search customisation based on user profiles and personalisation
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/445—Program loading or initiating
    • G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files

Abstract

The method obtains account identification of a target account carried in a service page request by receiving the service page request sent by a client, further determines service policy data hit by the account identification, obtains target service information corresponding to the hit service policy data according to the hit service policy data, and pushes the target service information to the client, so that the client can display the target service information in a corresponding service page. Because the content (i.e. the target service information) in the service page is determined based on the request of the target account and is strongly related to the target account, the target service information pushed to the service page can be different based on different target accounts, so that the personalized display of the service page is realized, and the self-help problem solving efficiency of the user can be improved.

Description

Information pushing method and device, electronic equipment and storage medium
Technical Field
The disclosure relates to the field of computer technology, and in particular, to a method, a device, an electronic device and a storage medium for pushing information.
Background
With the development of computer technology, various client applications emerge like spring bamboo shoots after rain. Typically, to give the user assistance in use, or collect usage questions and suggestions of user feedback, the client application will provide the user with a corresponding customer service page.
In the related art, the customer service page can show some common problems and solutions in a solidified form, however, the method cannot meet the personalized requirements of users, so that the efficiency of self-help problem solving of the users is low, and great working pressure is brought to the manual customer service.
Disclosure of Invention
The disclosure provides a method, a device, electronic equipment and a storage medium for pushing information, so as to at least solve the problem of low efficiency of self-help problem solving of users in the related technology. The technical scheme of the present disclosure is as follows:
according to a first aspect of an embodiment of the present disclosure, there is provided a method for pushing information, including:
receiving a service page request sent by a client, and acquiring an account identifier of a target account carried in the service page request, wherein the target account is a user account initiating the service page request;
determining service policy data hit by the account identification;
Acquiring target service information corresponding to the hit service policy data according to the hit service policy data;
pushing the target service information to the client so that the client displays the target service information in a corresponding service page
In one embodiment, the service policy data includes a plurality of service requirements configured in advance; the determining the service policy data hit by the account identification comprises: detecting the state of each service requirement in the service policy data according to the account identifier, wherein the state comprises one of a normal state and an abnormal state; and determining the detected service requirement of the abnormal state as the hit service policy data of the account identification.
In one embodiment, the service policy data has a plurality of groups, and each group of service policy data includes a plurality of service requirements configured in advance; the determining the service policy data hit by the account identification comprises: acquiring a pre-configured priority of each group of service policy data; detecting the state of each service requirement in the service strategy data according to the priority order of each group of the service strategy data and the account identifier; if any group of service policy data has abnormal service requirements, determining any group of service policy data as the service policy data hit by the account identifier.
In one embodiment, the service policy data further includes a priority of each of the service demands; the detecting the status of each service requirement in the service policy data includes: and detecting the state of the service demands according to the priority order of each service demand in the service policy data.
In one embodiment, the service policy data further includes abnormal account marking information corresponding to the service requirement; the detecting the status of the service requirement includes: if the account identifier exists in the abnormal account mark information corresponding to the service requirement is detected, determining that the service requirement is in an abnormal state; if the account identification does not exist in the abnormal account marking information corresponding to the service requirement, determining that the service requirement is in a normal state
In one embodiment, the service policy data further includes frequency limitation data corresponding to the service requirement; the detecting the status of the service requirement includes: acquiring historical behavior data corresponding to the account identifier; if the historical behavior data corresponding to the account identifier is detected to reach the frequency limit data corresponding to the service requirement, determining that the service requirement is in an abnormal state; and if the historical behavior data corresponding to the account identifier is detected not to reach the frequency limit data corresponding to the service requirement, determining that the service requirement is in a normal state.
In one embodiment, the obtaining, according to the hit service policy data, target service information corresponding to the hit service policy data includes: searching service information matched with the service requirement of the abnormal state in the hit service strategy data in preset service information; and determining the searched service information as target service information corresponding to the hit service policy data, wherein the service information is service prompt information corresponding to the service requirement.
In one embodiment, after the determining the target service information, the method further includes: sorting the target service information based on the priority order of the service demands matched with the target service information; the pushing the target service information to the client includes: and pushing the ordered target service information to the client.
In one embodiment, when there are multiple sets of service policy data hit by the account identifier, after determining the target service information, the method further includes: determining service policy data corresponding to the target service information; sorting the target service information based on the priority order of the service policy data; the pushing the target service information to the client includes: and pushing the ordered target service information to the client.
In one embodiment, when there are a plurality of target service information, the pushing the target service information to the client includes: acquiring the weight of each piece of target service information; sorting the target service information according to the weight of each target service information; and pushing the sorted target service information to the client.
In one embodiment, the obtaining the weight of each piece of the target service information includes: acquiring the historical pushing times of each piece of target service information; and determining the weight of the corresponding target service information according to the historical pushing times.
In one embodiment, the method further comprises: acquiring historical service data, and updating the service policy data or the service information according to the historical service data to obtain updated service policy data or updated service information; the history service data comprises history service data formed by processing a service page request of a client account by a server account; the obtaining the service policy data hit by the account identifier comprises the following steps: acquiring service policy data hit by the account identifier based on the updated service policy data; the searching the service information matched with the service requirement of the abnormal state in the hit service policy data in the preset service information comprises the following steps: and searching the updated service information for the service information matched with the service requirement in the abnormal state.
According to a second aspect of an embodiment of the present disclosure, there is provided an apparatus for pushing information, including:
the service page request receiving module is configured to execute a service page request sent by a receiving client, and acquire an account identifier of a target account carried in the service page request, wherein the target account is a user account initiating the service page request;
a policy processing module configured to perform determining service policy data hit by the account identification;
a target service information determining module configured to perform a process of acquiring target service information corresponding to the hit service policy data according to the hit service policy data;
and the information pushing module is configured to perform pushing of the target service information to the client so that the client can display the target service information in a corresponding service page.
In one embodiment, the service policy data includes a plurality of service requirements configured in advance, and the policy processing module further includes: a detection unit configured to perform detection of a state of each service requirement in the service policy data according to the account identification, the state including one of a normal state and an abnormal state; and a determining unit configured to perform determining the detected service demand of the abnormal state as the service policy data hit by the account identification.
In one embodiment, the service policy data has a plurality of groups, and each group of service policy data includes a plurality of service requirements configured in advance; the detection unit is configured to perform: acquiring a pre-configured priority of each group of service policy data; detecting the state of each service requirement in the service strategy data according to the priority order of each group of the service strategy data and the account identifier; the determination unit is further configured to perform: if any group of service policy data has abnormal service requirements, determining any group of service policy data as the service policy data hit by the account identifier.
In one embodiment, the service policy data further includes a priority of each of the service demands; the detection unit is further configured to perform: and detecting the state of the service demands according to the priority order of each service demand in the service policy data. In one embodiment, the service policy data further includes abnormal account marking information corresponding to the service requirement; the detection unit is configured to perform: if the account identifier exists in the abnormal account mark information corresponding to the service requirement is detected, determining that the service requirement is in an abnormal state; and if the account identification does not exist in the abnormal account marking information corresponding to the service requirement, determining that the service requirement is in a normal state.
In one embodiment, the service policy data further includes frequency limitation data corresponding to the service requirement; the detection unit is configured to perform: acquiring historical behavior data corresponding to the account identifier; if the historical behavior data corresponding to the account identifier is detected to reach the frequency limit data corresponding to the service requirement, determining that the service requirement is in an abnormal state; and if the historical behavior data corresponding to the account identifier is detected not to reach the frequency limit data corresponding to the service requirement, determining that the service requirement is in a normal state.
In one embodiment, the target service information determining module includes: a searching unit configured to perform searching for service information matching with the service requirement of the abnormal state in the hit service policy data in preset service information; and an information determining unit configured to perform determination of the searched service information as target service information corresponding to the hit service policy data, the service information being service hint information corresponding to the service requirement.
In one embodiment, the apparatus further comprises a ranking module configured to perform: sorting the target service information based on the priority order of the service demands matched with the target service information; the information push module is further configured to perform: and pushing the ordered target service information to the client.
In one embodiment, the ranking module is further configured to perform, when there are multiple sets of service policy data hit by the account identification: determining service policy data corresponding to the target service information; sorting the target service information based on the priority order of the service policy data; the information push module is further configured to perform: and pushing the ordered target service information to the client.
In one embodiment, when there are a plurality of the target service information, the ranking module is further configured to perform: acquiring the weight of each piece of target service information; sorting the target service information according to the weight of each target service information; the information push module is further configured to perform: and pushing the sorted target service information to the client.
In one embodiment, the ranking module is further configured to perform: acquiring the historical pushing times of each piece of target service information; and determining the weight of the corresponding target service information according to the historical pushing times.
In one embodiment, the apparatus further comprises an update module configured to perform: acquiring historical service data, and updating the service policy data or the service information according to the historical service data to obtain updated service policy data or updated service information; the history service data comprises history service data formed by processing a service page request of a client account by a server account; the policy processing module is further configured to perform: acquiring service policy data hit by the account identifier based on the updated service policy data; the lookup unit is further configured to perform: and searching the updated service information for the service information corresponding to the service requirement in the abnormal state in the hit service policy data.
According to a third aspect of embodiments of the present disclosure, there is provided an electronic device, comprising: a processor; a memory for storing the processor-executable instructions; wherein the processor is configured to execute the instructions to cause the electronic device to perform the method of pushing information described in any of the embodiments of the first aspect.
According to a fourth aspect of embodiments of the present disclosure, there is provided a storage medium, which when executed by a processor of an electronic device, enables the electronic device to perform the method of pushing information described in any one of the embodiments of the first aspect.
According to a fifth aspect of embodiments of the present disclosure, there is provided a computer program product comprising a computer program stored in a readable storage medium, from which at least one processor of a device reads and executes the computer program, causing the device to perform the method of pushing information as described in any one of the embodiments of the first aspect.
The technical scheme provided by the embodiment of the disclosure at least brings the following beneficial effects: the method comprises the steps of obtaining an account identifier of a target account carried in a service page request by receiving the service page request sent by a client, further determining service policy data hit by the account identifier, obtaining target service information corresponding to the hit service policy data according to the hit service policy data, and pushing the target service information to the client, so that the client can display the target service information in a corresponding service page. Because the content (i.e. the target service information) in the service page is determined based on the request of the target account and is strongly related to the target account, the target service information pushed to the service page can be different based on different target accounts, so that the personalized display of the service page is realized, and the self-help problem solving efficiency of the user can be improved.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the disclosure and together with the description, serve to explain the principles of the disclosure and do not constitute an undue limitation on the disclosure.
Fig. 1 is a schematic diagram illustrating a conventional customer service page push information scenario according to an exemplary embodiment.
Fig. 2 is an application environment diagram illustrating a method of pushing information according to an exemplary embodiment.
Fig. 3 is a flow chart illustrating a method of pushing information according to an exemplary embodiment.
FIG. 4 is a schematic diagram illustrating steps for obtaining hit service policy data, according to an example embodiment.
Fig. 5 is a schematic diagram of a push information scenario, according to an example embodiment.
Fig. 6 is a block diagram illustrating an apparatus for pushing information according to an exemplary embodiment.
Fig. 7 is a block diagram of an electronic device, according to an example embodiment.
Detailed Description
In order to enable those skilled in the art to better understand the technical solutions of the present disclosure, the technical solutions of the embodiments of the present disclosure will be clearly and completely described below with reference to the accompanying drawings.
It should be noted that the terms "first," "second," and the like in the description and claims of the present disclosure and in the foregoing figures are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments of the disclosure described herein may be capable of operation in sequences other than those illustrated or described herein. The implementations described in the following exemplary examples are not representative of all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with some aspects of the present disclosure as detailed in the accompanying claims.
In the conventional technology, as shown in fig. 1, in the implementation scheme of a customer service page in a client application, a user often clicks a customer service page entry, and a client requests a server to obtain data of page display based on the click of the user. After receiving the request, the server acquires the data of the current page from the customer service page configuration module, returns the data to the client, and finally renders and displays the data by the client. Because the traditional customer service page is a comparatively solidified display style, that is, each user can display the same content, the personalized requirements of the users can not be met. Therefore, each client application meets different personalized consultation requirements of the user by providing manual customer service. However, if the questions and answers presented by the customer service page are too hard to be cured, great working pressure is brought to the customer service, so that the customer consultation customer service does not respond for a long time or is queued for a long time, the use experience of the customer is seriously affected, the image of the client application is damaged, a great deal of loss of the customer of the client application is caused, and the development of the client application is very unfavorable.
Based on this, the disclosure provides a method for pushing information, which can be applied to an application environment as shown in fig. 2. The terminal 110 interacts with the server 120 through a network, and in particular, the terminal 110 may be, but not limited to, various personal computers, notebook computers, smartphones, tablet computers, and portable wearable devices, and the server 120 may be implemented by a stand-alone server or a server cluster formed by a plurality of servers.
In this embodiment, the terminal 110 is provided with a client of the application program, that is, a client application, and the server 120 is a background server corresponding to the client application. When a user (i.e. a target account) needs to enter a service page (i.e. a customer service page) of the client application, a corresponding service page request is initiated based on the client, wherein the service page request carries an account identifier of the target account. Specifically, the user may initiate the corresponding service page request by clicking on an entry of the service page presented in the client application. The client sends the service page request to the server 120 based on the request of the user, the server 120 receives the service page request, determines service policy data hit by the account identifier in the service page request, further obtains target service information corresponding to the hit service policy data according to the hit service policy data, and pushes the target service information to the client, so that the client can display the target service information in a corresponding service page, personalized display of the service page is realized, and the efficiency of self-help problem solving of the user is improved.
Fig. 3 is a flowchart illustrating a method of pushing information according to an exemplary embodiment, and as shown in fig. 3, the method is applied to the server in fig. 2 for illustration, and includes the following steps.
In step S310, a service page request sent by a client is received, and an account identifier of a target account carried in the service page request is obtained.
Wherein the service page request is an indication or command for requesting a service page. The target account is the user account that originated the service page request. The account identifier is a flag or symbol for identifying the user, and may be, for example, a user name of the user logging into the client application, or may be a phone number, mailbox, etc. associated with the user. In this embodiment, when a user (i.e., a target account) needs to enter a service page of a client, a corresponding service page request is initiated based on the client, where the service page request carries an account identifier of the target account. Specifically, the user may initiate the corresponding service page request by clicking on an entry of the service page presented in the client application. The client sends the service page request to the server based on the request of the user, and the server receives the service page request and acquires the account identification of the target account carried in the service page request.
In step S320, service policy data hit by the account identification is determined.
The service policy data comprise a plurality of preset service demands, and the hit service policy data refer to the predicted service demands of the target account corresponding to the account identifier. In particular, the service requirement may be a problem that the target account may face when using the client application, for example, whether the target account can log in to the client normally, whether personal information can be modified normally, whether a message can be sent normally, or the like. The hit service policy data refers to the predicted problem faced by the target account when using the client application, that is, the predicted service requirement matched with the target account, for example, the target account cannot normally log into the client, or cannot normally modify personal information, etc. In this embodiment, the service requirement matching the account identification of the target account is determined based on a number of service requirements configured in advance, that is, the service policy data hit by the account identification is determined.
In step S330, target service information corresponding to the hit service policy data is acquired based on the hit service policy data.
The target service information refers to service information corresponding to the predicted service demand of the target account. Specifically, the service information is service hint information, i.e. a solution, corresponding to the service requirement in the hit service policy data. For example, if the service policy data hitting the target account includes a service requirement that the personal information cannot be modified normally, the corresponding service information may include a common reason that the personal information cannot be modified normally, and a corresponding solution. Generally, the service information may be preconfigured and have a correspondence with the service requirement. Therefore, in the present embodiment, based on the service information configured in advance, the target service information corresponding to the service policy data hit by the account identification acquired in the above step can be determined.
In step S340, the target service information is pushed to the client.
The target service information is used for indicating the client to display the target service information in the corresponding service page.
In the method for pushing information, the account identifier of the target account carried in the service page request is obtained by receiving the service page request sent by the client, so that the service policy data hit by the account identifier is determined, the target service information corresponding to the hit service policy data is obtained according to the hit service policy data, and the target service information is pushed to the client, so that the client can display the target service information in the corresponding service page. Because the content (i.e. the target service information) in the service page is determined based on the request of the target account and is strongly related to the target account, the target service information pushed to the service page can be different based on different target accounts, so that the personalized display of the service page is realized, and the self-help problem solving efficiency of the user can be improved.
In an exemplary embodiment, as shown in fig. 4, in step S320, determining service policy data hit by the account identifier may be implemented specifically by the following steps:
in step S321, the status of each service requirement in the service policy data is detected according to the account identification.
The state of the service requirement includes that the service requirement is in a normal state or the service requirement is in an abnormal state. For example, regarding whether the target account can normally log in the service requirement of the client, if the target account can normally log in the client, the service requirement is indicated to be in a normal state, and if the target account cannot normally log in the client, the service requirement is indicated to be in an abnormal state. Because the service policy data includes a plurality of service requirements configured in advance, in this embodiment, based on the account identifier of the target account, the state of each service requirement in the service policy data can be detected, and then the service policy data hit by the account identifier is determined based on the subsequent steps.
Specifically, in an exemplary embodiment, the service policy data may further include abnormal account marking information corresponding to the service requirement, where the abnormal account marking information may be a black list, a limited account list, and the like. Therefore, if the account identifier of the target account exists in the abnormal account marking information corresponding to the service requirement is detected, determining that the service requirement is in an abnormal state; if the account identification of the target account does not exist in the abnormal account marking information corresponding to the service requirement, determining that the service requirement is in a normal state.
For example, if the preset service policy data includes: if the user can log in normally, the abnormal account marking information corresponding to the service requirement of the user can log in normally can be login black list information, namely, the user account in the black list is limited to log in. Therefore, by detecting whether the account identifier of the target account exists in the login blacklist, if the account identifier of the target account exists in the login blacklist, the target account is limited to be logged in, namely, the account identifier of the target account exists in the abnormal account mark information corresponding to the service requirement that whether the user can log in normally is detected, and the target account faces the service requirement that the user cannot log in normally, so that whether the service requirement that the user can log in normally is abnormal can be determined. Otherwise, if the account identifier of the target account does not exist in the login black list, the target account is indicated to be not limited to login, namely the target account can be normally logged in, so that whether the service requirement of the user for normally logging in is in a normal state or not.
For another example, if the preset service policy data includes: if the user can modify the service requirements of the image, the abnormal account indicia information corresponding to the service requirements of the user can modify the image may be a corresponding modified image limited account list. I.e. the user account in the list of presence modification image limited accounts will be limited to modification images. Therefore, by detecting whether the account identifier of the target account exists in the modified image limited account list, if the account identifier of the target account exists in the modified image limited account list, the target account is limited to be modified, namely, the account identifier of the target account exists in the abnormal account mark information corresponding to whether the user can modify the service requirement of the image is detected, and the target account faces the service requirement of the image which cannot be modified, so that whether the user can modify the service requirement of the image is abnormal can be determined. Otherwise, if the account identifier of the target account does not exist in the modified image limited account list, the target account is not limited to the modified image, that is, the target account can be modified normally, so that whether the service requirement of the user for modifying the image can be determined to be in a normal state. Because the embodiment detects the state of the service demand based on the account identifier and the abnormal account marking information corresponding to the service demand, the hit service policy data is determined, and the hit service policy data is strongly related to the target account, thereby being beneficial to realizing personalized display of the service page.
In an exemplary embodiment, the service policy data may further include frequency limitation data corresponding to the service requirement, where the frequency limitation data refers to frequency control data, and is frequency for controlling user behavior. Thus, in this embodiment, historical behavior data corresponding to the account identifier may be acquired; if the historical behavior data corresponding to the account identifier is detected to reach the frequency limit data corresponding to the service requirement, determining that the service requirement is in an abnormal state; if the historical behavior data corresponding to the account identifier is detected not to reach the frequency limit data corresponding to the service requirement, the service requirement is determined to be in a normal state.
For example, if the preset service policy data includes: whether the user can modify the service requirement of the password, and the frequency limit data corresponding to the service requirement are: a user may not modify the password more than 3 times in a given time. The historical modification password number of the target account in the appointed time can be obtained, and whether the historical modification password number of the target account reaches the corresponding frequency limit data is judged. Specifically, if the number of times of historical password modification of the target account in the designated time is 4 and exceeds 3 times in the frequency limit data, it indicates that the number of times of historical password modification of the target account is detected to reach the corresponding frequency limit data, so that the target account faces a service requirement that the password cannot be modified, and it can be determined whether the service requirement that the corresponding user can modify the password is in an abnormal state. If the historical password modification number of the target account in the designated time is 1, and the historical password modification number of the target account does not reach 3 times in the frequency limit data, the historical password modification number of the target account does not reach the corresponding frequency limit data, and the target account can carry out password modification operation, so that whether the service requirement of the corresponding user for password modification can be determined to be in a normal state. In the embodiment, the state of the service requirement is detected based on the account identifier and the frequency limit data corresponding to the service requirement, so that the hit service policy data is determined, and the hit service policy data is strongly related to the target account, thereby being beneficial to realizing personalized display of the service page.
It will be appreciated that for different service requirements, at least one of the corresponding abnormal account flag information and the frequency limitation data may be set based on actual service requirements, and the specific data in the above embodiments are merely for illustrating the principles of the present disclosure and are not intended to limit the protection scope of the present disclosure.
In step S322, the service requirement of the detected abnormal state is determined as the service policy data hit by the account identification.
The hit service policy data refers to the predicted problem faced by the target account when the client application is used, that is, the predicted service requirement of the abnormal state matched with the target account. Specifically, after the detection in the above steps, if the service requirement of the abnormal state matched with the account identifier is detected, the service requirement of the abnormal state is determined as hit service policy data.
In the above embodiment, the state of each service requirement in the service policy data is detected through the account identifier, and the detected service requirement in the abnormal state is determined as the service policy data hit by the account identifier. Because the embodiment detects the state of each service requirement in the service policy data based on the account identification, the hit service policy data is further determined, so that the hit service policy data is strongly related to the target account, and personalized display of the service page is further facilitated.
In an exemplary embodiment, the service policy data may also include a priority for each service requirement. The priority of the service demands is used for detecting the sequence of the state of each service demand in the service policy data. Therefore, in this embodiment, the priority ranking is performed on the service demands in the service policy data according to the priority of each service demand in the service policy data, so as to obtain ranked service policy data, and then the status of each service demand in the ranked service policy data is detected in sequence. In particular, the priority of the service demand may be determined based on the frequency with which the history of service demands hits, e.g., higher priority may be set for service demands with higher history hit frequency and lower priority may be set for service demands with lower history hit frequency. Therefore, the state of each service requirement in the service policy data can be detected and processed in sequence, so that the data processing efficiency is improved.
In an exemplary embodiment, there may be multiple sets of service policy data, and each set of service policy data may include a plurality of service requirements configured in advance, and determining the service policy data hit by the account identifier may further include: acquiring the priority of each set of service policy data which is preconfigured; detecting the state of each service requirement in the service strategy data according to the priority order of each group of service strategy data and the account identifier; if the abnormal state service requirement exists in any group of service policy data, determining any group of service policy data as the service policy data hit by the account identification. The priority of each group of service policy data is the sequence for detecting each group of service policy data. Specifically, the priority of the service policy data may be determined based on the frequency of hits by the history of the service policy data, for example, higher priority may be set to service policy data having a higher history hit frequency, and lower priority may be set to service policy data having a lower history hit frequency.
Therefore, in this embodiment, priority ranking is performed on each group of service policy data according to the priority of each group of service policy data, so as to obtain ranked service policy data, and then the ranked service policy data is detected in sequence. It can be understood that, when each set of service policy data is detected, the priority of each service requirement in the set of service policy data may be referred to for detection in sequence, and specific detection processes may refer to the above embodiment, which is not described in detail in this embodiment. In this embodiment, when detecting that there is an abnormal service requirement in a certain group of service policy data, the service policy data hit by the account identifier is determined. So that when detecting multiple groups of service policy data, the data can be processed in sequence according to the priority of each group of service policy data to improve the data processing efficiency
In an exemplary embodiment, in step S330, obtaining target service information corresponding to the hit service policy data according to the hit service policy data may specifically include: searching service information matched with the service requirement in the abnormal state in the hit service policy data in preset service information, and determining the searched service information as target service information corresponding to the hit service policy data. The service information is preset service prompt information corresponding to the service requirement, namely the solution. For example, for a service requirement where the target account cannot modify the password, its corresponding service information may include the common cause of failure to modify the password and the corresponding solution. Since the hit service policy data is the predicted service requirement of the abnormal state corresponding to the account identifier, the service information found based on the service requirement of the abnormal state is required by the target account, and is defined as the target service information. And because the target service information corresponds to the service requirement of the target account, the target service information can be displayed in the corresponding service page by the client by returning the target service information to the client, so that the personalized service page is realized, the self-help problem solving efficiency of the user is improved, and the user experience of using the client is also improved.
In an exemplary embodiment, the method for pushing information may further include: and acquiring historical service data, and updating service policy data or service information according to the historical service data, so as to obtain updated service policy data or updated service information. The historical service data comprises historical service data formed by processing a service page request of a client account by a server account. In particular, the historical service data may be data generated based on manual customer service to address user service needs, including corresponding service needs and corresponding solutions generated under the direction of manual customer service. In this embodiment, in order to further improve the efficiency of self-help problem solving by the user, the service policy data or the service information can be updated continuously for the historical service data generated by the manual customer service requirement solving, so that the original service policy data and service information are expanded, further, the service policy data hit by the account identifier is determined based on the updated service policy data, so as to improve the hit rate, and the service information corresponding to the service requirement in the abnormal state in the hit service policy data is searched in the updated service information, so that the workload of the manual customer service is reduced, and the efficiency of self-help problem solving is improved.
In an exemplary embodiment, after determining the target service information, the method may further include: and ordering the target service information based on the priority order of the service demands matched with the target service information. Specifically, because the target service information is obtained by searching for service requirements based on an abnormal state and has a corresponding priority for each service requirement, in this embodiment, the target service information is ordered based on the priority order of the service requirements matched with the target service information, and then the ordered target service information is pushed to the client. The client can realize personalized service pages based on the ordered target service information, so that the self-help problem solving efficiency of the user can be improved, and the experience of the user in using the client can be improved.
In an exemplary embodiment, when there are multiple sets of service policy data hit by the account identifier, after determining the target service information, the method may further include: and determining service policy data corresponding to the target service information, and sequencing the target service information based on the priority order of the service policy data. Specifically, since the target service information is obtained by searching for the service requirement based on the abnormal state in the service policy data, the service policy data has a corresponding priority for each group. Therefore, in this embodiment, service policy data corresponding to the service requirement matched with the target service information may be determined, and then the target service information is ordered based on the priority order of the service policy data corresponding to each target service information, so as to push the ordered target service information to the client. The client can realize personalized service pages based on the ordered target service information, so that the self-help problem solving efficiency of the user can be improved, and the experience of the user in using the client can be improved.
In an exemplary embodiment, when there are multiple target service information, pushing the target service information to the client specifically includes: acquiring the weight of each piece of target service information; sorting the target service information according to the weight of each target service information; and pushing the sorted target service information to the client. Wherein the weight refers to the relative importance of the target service information. Since the target service information is service information matching the hit service policy data, which is found in the preset service information, there may be a corresponding weight for each of the preset service information. For the abnormal service requirement in the hit service policy data, there is a corresponding target service information. Therefore, in this embodiment, based on the preset service information and the corresponding weight, the service information and the corresponding weight corresponding to the service requirement in the abnormal state in the service policy data of each hit may be searched, so as to obtain the target service information and the corresponding weight corresponding to the service requirement in the abnormal state in the service policy data of each hit. In one implementation, the weight of the target service information may also be determined based on the historical number of pushes of the target service information. For example, the higher the history push number is, the higher the weight is corresponding to the target service information, and the lower the history push number is, the lower the weight is corresponding to the target service information. Because the target service information is the service information corresponding to the service requirement in the abnormal state in the hit service policy data, when the number of times that a certain target service information history is pushed is greater, the requirement amount of the target service information is higher, that is, the service requirement corresponding to the target service information is a history common requirement.
Based on this, after the weight of each target service information is obtained, the target service information may be further ranked according to the weight of each target service information, for example, the target service information may be ranked according to the order of the weights from high to low, and the ranked target service information may be pushed to the client. Because the target service information is determined based on the service requirement of the abnormal state in the hit service policy data and is required by the predicted target account, the target service information can be ranked based on the weight of each target service information and the ranked target service information can be pushed to the client, so that the client can realize a personalized service page based on the ranked target service information, the self-help problem solving efficiency of the user can be improved, and the user experience of using the client can be improved.
In an exemplary embodiment, the method for pushing information of the present disclosure is further described below, and in this embodiment, the high-frequency problem (i.e. service requirement) of the customer service page (i.e. service page) is analyzed and judged in a personalized manner, so as to form corresponding service policy data. For example, on a customer service page of a social client, account problems occur more frequently, and the number of accesses of users is also higher. The account number problem can be divided into the problems of failed user head portrait replacement, failed user nickname replacement, abnormal account number and the like. When a user enters a customer service page, the reasons such as updating of the head portrait, updating of the nickname, abnormal account number and the like of the user can be limited through personalized judgment, if the target user is found to be in a limited state, for example, the target user cannot update the head portrait, the reason that the user cannot update the head portrait and the solution can be placed at a more obvious position of the customer service page, so that the clicking rate of the user is improved, the basic problem of the user can be effectively solved, and the problem that the manual customer service intervention is required by the user and the manual customer service pressure is too high is avoided. Based on the method, more types of strategy judging modules, such as an interaction strategy judging module, an account strategy judging module and the like, can be updated and perfected, and the reason that the user enters the customer service page can be predicted more efficiently through the continuous perfecting strategy judging module, so that the problem of the user is solved more effectively, and the user experience is improved.
Specifically, as shown in fig. 5, the high-frequency problems common to the user are first combed according to the problems solved by the manual customer service history, and the problems are classified and summarized. For example, taking a customer service page of a social client as an example, the customer service page is divided from a large aspect into account questions AccountQuest and social interaction questions InterctQuest based on the problems solved by history, and of course, based on actual conditions, more kinds of questions can be expanded, and in this embodiment, only account questions and social interaction questions are exemplified. For each type of problem, a corresponding policy judgment module may be formed, for example, for an account problem accountequest, a corresponding account policy judgment module may be formed, and for a social interaction problem intersectant, a corresponding social interaction policy judgment module may be formed. While each policy judgment module may have a corresponding policy priority, in addition, each question may have a corresponding question priority for a plurality of questions within one policy judgment module. For example, if the account class problem accountequest based on the priority summary is as follows:
LoginStatus (1) user login
Modification of the password by ModifyPasswordStatus (2)
bindwobilePhoneStatus (3) binding handset
Modification of head portraits by a ModifyUserHeadStatus (4)
Modifying user nicknames with a modified usernamestatus (5)
f. Etc.
If the social interaction type problem interaction based on priority summary is as follows:
sendnitifystatus (1) send message
Comment by publishcomintStatus (2)
c publishP Hotostatus (3) published works
d. Etc.
After the policy configuration information (which can be understood as the service policy data and the service requirement) is set, when a user initiates a customer service page request through a client, the client requests the customer service page data to the server, and the server performs corresponding policy judgment based on a policy judgment module, for example, if the corresponding policy priority is obtained to be higher than that of the social interaction policy judgment module, the account policy judgment is performed first to judge whether the target user has a common account problem, and the called interface API is as follows:
a.canLoginSuccess () can log in or not
b.canmodifypassword () whether the password can be modified
c.CanBindMobilePhone () can bind to a handset
d.canmod ifyuserhead () whether the header can be modified
e.canmod ifyusername () whether a user nickname can be modified
If the account policy judgment module judges that the following return result is obtained:
then, judging social interaction strategies according to strategy priorities, and judging current common social behavior of the target user in sequence, wherein details are not repeated here, and the obtained results are assumed to be as follows:
and synthesizing the strategy judgment results, and returning the following results:
wherein the problem of "false" results in a hit strategy. The service end requests some common problem page resources (namely service information) from the customer service page configuration module based on the hit strategy in the returned result, and searches matched resources according to the hit strategy. For example, for the hit account problems, for example, the password modification failure and the head portrait modification failure are hit, the common cause of the password modification failure, the common cause of the head portrait modification failure and the corresponding solutions and weights are searched, and for the hit social interaction type problems, the corresponding common cause, solution and weights are searched, and the ranking is performed based on the corresponding weights, so that the higher-weight ranking is performed at the front position. The ordered data is returned to the client, the client effectively renders the data and displays the data with higher weight at a conspicuous position, so that a user can see personalized customer service pages, and after the user usually sees common reasons of the problems, the user can process the data by referring to corresponding solutions, thereby avoiding the intervention of calling manual customer service.
It should be understood that, although the steps in the flowcharts of fig. 1-5 are shown in order as indicated by the arrows, these steps are not necessarily performed in order as indicated by the arrows. The steps are not strictly limited to the order of execution unless explicitly recited herein, and the steps may be executed in other orders. Moreover, at least a portion of the steps of fig. 1-5 may include multiple steps or stages that are not necessarily performed at the same time, but may be performed at different times, nor does the order in which the steps or stages are performed necessarily occur sequentially, but may be performed alternately or alternately with at least a portion of the steps or stages in other steps or other steps.
Fig. 6 is a block diagram of an apparatus for pushing information, according to an example embodiment. Referring to fig. 6, the apparatus includes a service page request receiving module 602, a policy processing module 604, a target service information determining module 606, and an information pushing module 608.
The service page request receiving module 602 is configured to execute receiving a service page request sent by a client, and obtain an account identifier of a target account carried in the service page request, where the target account is a user account initiating the service page request;
A policy processing module 604 configured to execute service policy data that determines that the account identification hits;
a target service information determining module 606 configured to perform a process of acquiring target service information corresponding to the hit service policy data according to the hit service policy data;
an information pushing module 608 is configured to perform pushing the target service information to the client, so that the client displays the target service information in a corresponding service page.
In an exemplary embodiment, the service policy data includes a plurality of service requirements configured in advance, and the policy processing module further includes: a detection unit configured to perform detection of a state of each service requirement in the service policy data according to the account identification, the state including one of a normal state and an abnormal state; and a determining unit configured to perform determining the detected service demand of the abnormal state as the service policy data hit by the account identification.
In an exemplary embodiment, the service policy data has a plurality of groups, and each group of service policy data includes a plurality of service requirements configured in advance; the detection unit is configured to perform: acquiring a pre-configured priority of each group of service policy data; detecting the state of each service requirement in the service strategy data according to the priority order of each group of the service strategy data and the account identifier; the determination unit is further configured to perform: if any group of service policy data has abnormal service requirements, determining any group of service policy data as the service policy data hit by the account identifier.
In an exemplary embodiment, the service policy data further includes a priority of each of the service demands; the detection unit is further configured to perform: and detecting the state of the service demands according to the priority order of each service demand in the service policy data. In an exemplary embodiment, the service policy data further includes abnormal account marking information corresponding to the service requirement; the detection unit is configured to perform: if the account identifier exists in the abnormal account mark information corresponding to the service requirement is detected, determining that the service requirement is in an abnormal state; and if the account identification does not exist in the abnormal account marking information corresponding to the service requirement, determining that the service requirement is in a normal state.
In an exemplary embodiment, the service policy data further includes frequency limitation data corresponding to the service requirement; the detection unit is configured to perform: acquiring historical behavior data corresponding to the account identifier; if the historical behavior data corresponding to the account identifier is detected to reach the frequency limit data corresponding to the service requirement, determining that the service requirement is in an abnormal state; and if the historical behavior data corresponding to the account identifier is detected not to reach the frequency limit data corresponding to the service requirement, determining that the service requirement is in a normal state.
In an exemplary embodiment, the target service information determining module includes: a searching unit configured to perform searching for service information matching with the service requirement of the abnormal state in the hit service policy data in preset service information; and an information determining unit configured to perform determination of the searched service information as target service information corresponding to the hit service policy data, the service information being service hint information corresponding to the service requirement.
In an exemplary embodiment, the apparatus further comprises a ranking module configured to perform: sorting the target service information based on the priority order of the service demands matched with the target service information; the information push module is further configured to perform: and pushing the ordered target service information to the client.
In an exemplary embodiment, the ranking module is further configured to perform, when there are multiple sets of service policy data hit by the account identification: determining service policy data corresponding to the target service information; sorting the target service information based on the priority order of the service policy data; the information push module is further configured to perform: and pushing the ordered target service information to the client.
In an exemplary embodiment, when there are a plurality of the target service information, the ranking module is further configured to perform: acquiring the weight of each piece of target service information; sorting the target service information according to the weight of each target service information; the information push module is further configured to perform: and pushing the sorted target service information to the client.
In an exemplary embodiment, the ranking module is further configured to perform: acquiring the historical pushing times of each piece of target service information; and determining the weight of the corresponding target service information according to the historical pushing times.
In an exemplary embodiment, the apparatus further comprises an update module configured to perform: acquiring historical service data, and updating the service policy data or the service information according to the historical service data to obtain updated service policy data or updated service information; the history service data comprises history service data formed by processing a service page request of a client account by a server account; the policy processing module is further configured to perform: acquiring service policy data hit by the account identifier based on the updated service policy data; the lookup unit is further configured to perform: and searching the updated service information for the service information corresponding to the service requirement in the abnormal state in the hit service policy data.
The specific manner in which the various modules perform the operations in the apparatus of the above embodiments have been described in detail in connection with the embodiments of the method, and will not be described in detail herein.
Fig. 7 is a block diagram illustrating a device S00 for pushing information according to an exemplary embodiment. For example, device S00 may be a server. Referring to fig. 7, device S00 includes a processing component S20 that further includes one or more processors, and memory resources represented by memory S22, for storing instructions, such as applications, executable by processing component S20. The application program stored in the memory S22 may include one or more modules each corresponding to a set of instructions. Further, the processing component S20 is configured to execute instructions to perform the above-described method of pushing information.
Device S00 can also include a power component S24 configured to perform power management of device S00, a wired or wireless network interface S26 configured to connect device S00 to a network, and an input/output (I/O) interface S28. Device S00 may operate based on an operating system stored in memory S22, such as Windows Server, mac OS X, unix, linux, freeBSD, or the like.
In an exemplary embodiment, a computer readable storage medium is also provided, such as a memory S22, comprising instructions executable by a processor of the device S00 to perform the above method. The storage medium may be a computer readable storage medium, which may be, for example, ROM, random Access Memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, etc.
In an exemplary embodiment, a computer program product is also provided, comprising a computer program which, when executed by a processor, performs the above-described method of pushing information.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This disclosure is intended to cover any adaptations, uses, or adaptations of the disclosure following the general 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 is to be understood that the present disclosure is not limited to the precise arrangements and instrumentalities shown in the drawings, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims (20)

1. A method of pushing information, the method comprising:
receiving a service page request sent by a client, and acquiring an account identifier of a target account carried in the service page request, wherein the target account is a user account initiating the service page request;
determining hit service policy data of the account identifier, wherein the hit service policy data is based on a problem faced by a target account when a client application is used, and the predicted service requirement of the target account corresponding to the account identifier;
acquiring target service information corresponding to the hit service policy data according to the hit service policy data, wherein the target service information is service information corresponding to the predicted service demand of the target account;
pushing the target service information to the client so that the client displays the target service information in a corresponding service page;
The service policy data has a plurality of groups, each group of service policy data comprises a plurality of service demands which are preconfigured, the service policy data also comprises the priority of each service demand, and the determining the service policy data hit by the account identifier comprises the following steps:
acquiring a pre-configured priority of each group of service policy data;
detecting the state of the service requirement according to the priority sequence of each group of service strategy data and the account identifier and the priority sequence of each service requirement in the service strategy data, wherein the state comprises one of a normal state and an abnormal state;
if any group of service policy data has abnormal service requirements, determining any group of service policy data as the service policy data hit by the account identifier.
2. The method of claim 1, wherein the service policy data further includes abnormal account marking information corresponding to the service requirement; the detecting the status of the service requirement includes:
if the account identifier exists in the abnormal account mark information corresponding to the service requirement is detected, determining that the service requirement is in an abnormal state;
And if the account identification does not exist in the abnormal account marking information corresponding to the service requirement, determining that the service requirement is in a normal state.
3. The method of claim 1, wherein the service policy data further comprises frequency limitation data corresponding to the service requirement; the detecting the status of the service requirement includes:
acquiring historical behavior data corresponding to the account identifier;
if the historical behavior data corresponding to the account identifier is detected to reach the frequency limit data corresponding to the service requirement, determining that the service requirement is in an abnormal state;
and if the historical behavior data corresponding to the account identifier is detected not to reach the frequency limit data corresponding to the service requirement, determining that the service requirement is in a normal state.
4. The method of claim 1, wherein the obtaining, based on the hit service policy data, target service information corresponding to the hit service policy data comprises:
searching service information matched with the service requirement of the abnormal state in the hit service strategy data in preset service information;
And determining the searched service information as target service information corresponding to the hit service policy data, wherein the service information is service prompt information corresponding to the service requirement.
5. The method of claim 1, wherein after the determining the target service information, the method further comprises:
sorting the target service information based on the priority order of the service demands matched with the target service information;
the pushing the target service information to the client includes:
and pushing the ordered target service information to the client.
6. The method of claim 4, wherein, when there are multiple sets of service policy data hit by the account identification, after the determining the target service information, the method further comprises:
determining service policy data corresponding to the target service information;
sorting the target service information based on the priority order of the service policy data;
the pushing the target service information to the client includes:
and pushing the ordered target service information to the client.
7. The method of claim 4, wherein when there are a plurality of the target service information, the pushing the target service information to the client includes:
Acquiring the weight of each piece of target service information;
sorting the target service information according to the weight of each target service information;
and pushing the sorted target service information to the client.
8. The method of claim 7, wherein the obtaining the weight of each of the target service information comprises:
acquiring the historical pushing times of each piece of target service information;
and determining the weight of the corresponding target service information according to the historical pushing times.
9. The method according to claim 4, wherein the method further comprises:
acquiring historical service data, and updating the service policy data or the service information according to the historical service data to obtain updated service policy data or updated service information; the history service data comprises history service data formed by processing a service page request of a client account by a server account;
the determining the service policy data hit by the account identification comprises: determining the service policy data hit by the account identifier based on the updated service policy data;
the searching the service information matched with the service requirement of the abnormal state in the hit service policy data in the preset service information comprises the following steps: and searching the updated service information for the service information matched with the service requirement in the abnormal state.
10. An apparatus for pushing information, the apparatus comprising:
the service page request receiving module is configured to execute a service page request sent by a receiving client, and acquire an account identifier of a target account carried in the service page request, wherein the target account is a user account initiating the service page request;
a policy processing module configured to perform determining service policy data hit by the account identification, the service policy data including a number of service requirements that are preconfigured, the hit service policy data being predicted service requirements of a target account corresponding to the account identification based on a problem faced by the target account when using the client application;
a target service information determining module configured to perform obtaining target service information corresponding to the hit service policy data according to the hit service policy data, the target service information being service information corresponding to a predicted service demand of a target account;
the information pushing module is configured to perform pushing of the target service information to the client so that the client displays the target service information in a corresponding service page;
The service policy data comprises a plurality of groups, each group of service policy data comprises a plurality of service demands which are preconfigured, the service policy data also comprises the priority of each service demand, and the policy processing module further comprises:
a detection unit configured to perform acquisition of a priority of each set of service policy data configured in advance; detecting the state of the service requirement according to the priority sequence of each group of service strategy data and the account identifier and the priority sequence of each service requirement in the service strategy data, wherein the state comprises one of a normal state and an abnormal state;
and the determining unit is configured to execute the determination of any group of service policy data as the service policy data hit by the account identification if the abnormal state service requirement exists in any group of service policy data.
11. The apparatus of claim 10, wherein the service policy data further includes abnormal account marking information corresponding to the service requirement; the detection unit is configured to perform:
if the account identifier exists in the abnormal account mark information corresponding to the service requirement is detected, determining that the service requirement is in an abnormal state;
And if the account identification does not exist in the abnormal account marking information corresponding to the service requirement, determining that the service requirement is in a normal state.
12. The apparatus of claim 10, wherein the service policy data further comprises frequency limitation data corresponding to the service requirement; the detection unit is configured to perform:
acquiring historical behavior data corresponding to the account identifier;
if the historical behavior data corresponding to the account identifier is detected to reach the frequency limit data corresponding to the service requirement, determining that the service requirement is in an abnormal state;
and if the historical behavior data corresponding to the account identifier is detected not to reach the frequency limit data corresponding to the service requirement, determining that the service requirement is in a normal state.
13. The apparatus of claim 10, wherein the target service information determination module comprises:
a searching unit configured to perform searching for service information matching with the service requirement of the abnormal state in the hit service policy data in preset service information;
and an information determining unit configured to perform determination of the searched service information as target service information corresponding to the hit service policy data, the service information being service hint information corresponding to the service requirement.
14. The apparatus of claim 10, further comprising a ranking module configured to perform:
sorting the target service information based on the priority order of the service demands matched with the target service information;
the information push module is further configured to perform: and pushing the ordered target service information to the client.
15. The apparatus of claim 14, wherein when there are multiple sets of service policy data hit by the account identification, the ranking module is further configured to perform:
determining service policy data corresponding to the target service information; sorting the target service information based on the priority order of the service policy data;
the information push module is further configured to perform: and pushing the ordered target service information to the client.
16. The apparatus of claim 14, wherein when there are a plurality of the target service information, the ranking module is further configured to perform:
acquiring the weight of each piece of target service information; sorting the target service information according to the weight of each target service information;
The information push module is further configured to perform: and pushing the sorted target service information to the client.
17. The apparatus of claim 16, wherein the ranking module is further configured to perform:
acquiring the historical pushing times of each piece of target service information;
and determining the weight of the corresponding target service information according to the historical pushing times.
18. The apparatus of claim 13, wherein the apparatus further comprises an update module configured to perform:
acquiring historical service data, and updating the service policy data or the service information according to the historical service data to obtain updated service policy data or updated service information; the history service data comprises history service data formed by processing a service page request of a client account by a server account;
the policy processing module is further configured to perform: acquiring service policy data hit by the account identifier based on the updated service policy data;
the lookup unit is further configured to perform: and searching the updated service information for the service information matched with the service requirement of the abnormal state in the hit service strategy data.
19. An electronic device, comprising:
a processor;
a memory for storing the processor-executable instructions;
wherein the processor is configured to execute the instructions to implement the method of pushing information as claimed in any one of claims 1 to 9.
20. A computer readable storage medium, characterized in that instructions in the computer readable storage medium, when executed by a processor of an electronic device, enable the electronic device to perform the method of pushing information according to any one of claims 1 to 9.
CN202110907444.3A 2021-08-09 2021-08-09 Information pushing method and device, electronic equipment and storage medium Active CN113590252B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202110907444.3A CN113590252B (en) 2021-08-09 2021-08-09 Information pushing method and device, electronic equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202110907444.3A CN113590252B (en) 2021-08-09 2021-08-09 Information pushing method and device, electronic equipment and storage medium

Publications (2)

Publication Number Publication Date
CN113590252A CN113590252A (en) 2021-11-02
CN113590252B true CN113590252B (en) 2024-04-16

Family

ID=78256338

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202110907444.3A Active CN113590252B (en) 2021-08-09 2021-08-09 Information pushing method and device, electronic equipment and storage medium

Country Status (1)

Country Link
CN (1) CN113590252B (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114595393A (en) * 2022-03-21 2022-06-07 北京有竹居网络技术有限公司 Data processing method and device

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103996131A (en) * 2014-04-30 2014-08-20 杭州顺网科技股份有限公司 Method for precision advertising at online game players
CN105610929A (en) * 2015-12-24 2016-05-25 北京奇虎科技有限公司 Personalized data pushing method and device
CN111429171A (en) * 2020-03-04 2020-07-17 支付宝(杭州)信息技术有限公司 Information display method, server, device and system
CN111523922A (en) * 2020-04-01 2020-08-11 北京三快在线科技有限公司 Information pushing method and system, computer device and cloud server system

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200219123A1 (en) * 2019-01-04 2020-07-09 Hyundai Card Co., Ltd. Server, method and recording medium storing commands for managing customers

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103996131A (en) * 2014-04-30 2014-08-20 杭州顺网科技股份有限公司 Method for precision advertising at online game players
CN105610929A (en) * 2015-12-24 2016-05-25 北京奇虎科技有限公司 Personalized data pushing method and device
CN111429171A (en) * 2020-03-04 2020-07-17 支付宝(杭州)信息技术有限公司 Information display method, server, device and system
CN111523922A (en) * 2020-04-01 2020-08-11 北京三快在线科技有限公司 Information pushing method and system, computer device and cloud server system

Also Published As

Publication number Publication date
CN113590252A (en) 2021-11-02

Similar Documents

Publication Publication Date Title
CN110099059B (en) Domain name identification method and device and storage medium
EP2805265B1 (en) System and method for improving access to search results
CN109873745B (en) Communication control method, communication control device and storage medium
WO2020019564A1 (en) Search ranking method and apparatus, electronic device and storage medium
CN112035638B (en) Information processing method, device, storage medium and equipment
CN108600779B (en) Target object operation method and device based on video content
CN110457097B (en) Page response control method and device, computer equipment and storage medium
US20210390006A1 (en) Method and electronic device for querying application programming interfaces of webpage
CN113590252B (en) Information pushing method and device, electronic equipment and storage medium
CN110737891A (en) host intrusion detection method and device
US20070055733A1 (en) Method, server and program product for delivering messages
CN109978114B (en) Data processing method, device, server and storage medium
CN106789973B (en) Page security detection method and terminal equipment
US20150149928A1 (en) Method, system and device for implementing an instant messaging application
CN109492149B (en) Crawler task processing method and device
CN115202599A (en) Screen projection display method and related device
CN113065054B (en) Request processing method, request processing device, electronic equipment and storage medium
JP2017529587A (en) Determining the contribution of various user interactions to conversions
CN112182520B (en) Identification method and device of illegal account number, readable medium and electronic equipment
CN112990830B (en) Role switching method and device in file access process and computing equipment
US11275797B2 (en) Information processing apparatus correcting access frequency of shared information, information processing system, and non-transitory computer readable medium
US9582368B2 (en) Method and apparatus for text input protection
CN114327693A (en) AB experiment method and system, terminal device and storage medium
CN113420713A (en) Abnormity monitoring method and device, electronic equipment and computer readable medium
CN112035773A (en) Data processing method and server side equipment

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
GR01 Patent grant
GR01 Patent grant