Policy-based information processing method, electronic device, and storage medium
By synchronizing terminal rule information during page operation and determining strategies based on rule scripts, generating strategy retrieval requests, and fetching and rendering display information, the problem of low information push efficiency is solved, and timely display and efficient delivery of information are achieved.
Patent Information
- Application Number
- CN202210602232.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2022-05-30
- Publication Date
- 2024-11-22
- Estimated Expiration
- 2042-05-30
AI Technical Summary
In existing technologies, information push methods cause users to skip information if they cannot view it in time, resulting in information loss, long response time, and low efficiency.
When synchronization conditions are met, the system synchronizes and stores the rule information, determines the strategy based on the rule script, generates a strategy retrieval request, pulls the strategy data, and renders and displays it. By combining the mechanism of server-side push and client-side retrieval, the system ensures the timely display of information.
It improves the efficiency and accuracy of information display, ensures that information is displayed at the right time, reduces the probability of users missing information, and increases the reach of strategies.
Smart Images

Figure CN114968528B_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of computer technology, and in particular to a policy-based information processing method, an electronic device and a storage medium. Background Art
[0002] When users browse and use the websites and apps (Applications) provided by the platform, the platform sometimes provides some information, such as event news and recommended news, to users so that they can understand the information they need. For example, the discount information of shopping streets can be pushed on shopping websites.
[0003] This type of information may appear in a variety of ways such as opening screen messages and pop-up windows, and may also be triggered by the user's browsing time, triggering method, etc. However, sometimes it takes a long time to obtain the message, resulting in a response time process. The user may choose to skip it without viewing it, thereby missing the information. Summary of the invention
[0004] The embodiment of the present application provides a policy-based information processing method to improve the efficiency of information display.
[0005] Correspondingly, the embodiment of the present application also provides an electronic device and a storage medium to ensure the implementation and application of the above system.
[0006] In order to solve the above problems, the embodiment of the present application discloses a policy-based information processing method, the method comprising:
[0007] When the synchronization condition is met, the rule information corresponding to the synchronization end rule is stored, and the rule information includes a rule script;
[0008] During the page running process, the hit strategy is determined based on the rule script, a strategy acquisition request is generated, and the strategy acquisition request is sent;
[0009] receiving policy data corresponding to the policy;
[0010] Rendering is performed according to the policy data, and corresponding display information is displayed.
[0011] Optionally, when the synchronization condition is met, the rule information corresponding to the synchronization end rule includes at least one of the following steps:
[0012] When it is detected that the page status meets the acquisition conditions, a rule pull request is generated and sent to pull the rule information of the corresponding rule;
[0013] Receive rule information of the end rule fed back by the server, where the end rule is converted from the hit cloud rule, and the hit cloud rule is determined according to the cloud event corresponding to the user behavior.
[0014] Optionally, during the page running process, determining the hit strategy based on the rule script and generating a strategy acquisition request include:
[0015] During the page operation, detection is performed based on the rule script;
[0016] When a rule hit is detected, the corresponding rule identifier, page identifier, and page associated parameters are determined;
[0017] A policy acquisition request is generated based on the rule identifier, the page identifier, and the page associated parameters.
[0018] Optionally, it also includes: after detecting that the embedded data triggers an end event in the page, generating and sending an end event request.
[0019] Optionally, the strategy data includes delivery data, rendering configuration data, and tracking point data; and rendering according to the strategy data includes:
[0020] The delivery data is rendered according to the rendering configuration data, and the embedding data is added to the display information obtained by rendering.
[0021] Optionally, generating a display result according to the display information includes:
[0022] A rendering result is determined according to the display information, and the display result is generated using the rendering result and the strategy identifier.
[0023] The embodiment of the present application also discloses a policy-based information processing method, characterized in that the method includes:
[0024] When the synchronization condition is met, the rule information of the originating end rule is sent to synchronize the rule to the client, wherein the rule information includes the rule script;
[0025] Receive a policy acquisition request, where the policy acquisition request is generated based on the policy hit by the rule script;
[0026] Determining policy data corresponding to the policy according to the policy acquisition request;
[0027] The policy data of the policy is issued so that the corresponding display information is rendered and displayed on the client according to the policy.
[0028] Optionally, when the synchronization condition is met, issuing rule information of the rule includes:
[0029] Receive a rule pull request, and obtain rule information of the terminal rule according to the rule pull request;
[0030] The rule information is sent.
[0031] Optionally, when the synchronization condition is met, issuing rule information of the rule includes:
[0032] Based on the cloud events corresponding to the user behaviors, determine the hit cloud rules, and convert the cloud rules into terminal rules;
[0033] Obtain rule information of the terminal rule, and send the rule information.
[0034] Optionally, determining the policy data corresponding to the policy according to the policy acquisition request includes:
[0035] Determine the rule identifier, page identifier and page associated parameters according to the policy acquisition request;
[0036] Determine delivery data according to the rule identifier and the page associated parameters, wherein the delivery data includes static data and dynamic data;
[0037] Determine rendering configuration data and embedding data according to the rule identifier, page identifier and page associated parameters;
[0038] The delivery data, rendering configuration data and embedding point data are used to form strategy data.
[0039] Optionally, determining the policy data corresponding to the policy according to the policy acquisition request includes:
[0040] Get the policy request triggered by the end event to determine whether there is a cloud rule;
[0041] If no cloud rule exists, determining policy data for the corresponding policy;
[0042] If a cloud rule exists, the policy data of the policy is matched according to the cloud rule.
[0043] Optionally, analyzing the display result to determine the policy processing result includes:
[0044] Analyze the strategy data to determine corresponding operation results;
[0045] The strategy data is analyzed to determine the user's fatigue information.
[0046] The embodiment of the present application also discloses a policy-based information processing device, the device comprising:
[0047] A rule synchronization module, used to synchronize and store rule information corresponding to the end rule when the synchronization condition is met, wherein the rule information includes a rule script;
[0048] A policy request module is used to determine the hit policy based on the rule script during the page running process, generate a policy acquisition request, and send the policy acquisition request; receive policy data corresponding to the policy;
[0049] A display module, used to render according to the policy data and display corresponding display information;
[0050] The result feedback module is used to generate a display result according to the display information, and feed back the display result to analyze the strategy processing result.
[0051] The embodiment of the present application also discloses a policy-based information processing device, the device comprising:
[0052] A rule sending module, used for sending rule information of terminal rules when synchronization conditions are met, so as to synchronize the rules to the client, wherein the rule information includes rule scripts;
[0053] A policy delivery module is used to receive a policy acquisition request, the policy acquisition request is generated according to the policy hit by the rule script; determine the policy data of the corresponding policy according to the policy acquisition request; and deliver the policy data of the policy so that the client renders and displays the corresponding display information according to the policy;
[0054] The analysis module is used to receive the display results; analyze the display results and determine the policy processing results.
[0055] The embodiment of the present application further discloses an electronic device, including: a processor; and a memory, on which executable code is stored. When the executable code is executed by the processor, the method described in the embodiment of the present application is executed.
[0056] The embodiments of the present application also disclose one or more machine-readable media on which executable codes are stored. When the executable codes are executed by a processor, the method described in the embodiments of the present application is executed.
[0057] Compared with the prior art, the embodiments of the present application have the following advantages:
[0058] In an embodiment of the present application, when the synchronization conditions are met, the rule information corresponding to the synchronization end rule is stored, and the rule information includes a rule script. Therefore, during the running of the page, the hit strategy is determined based on the rule script, a policy acquisition request is generated, and the policy data is pulled according to the policy acquisition request, so as to realize a mechanism combining server-side push with terminal-side pull to effectively ensure the reach of the strategy, render according to the policy data, and display the corresponding display information to ensure the display of information. BRIEF DESCRIPTION OF THE DRAWINGS
[0059] Figure 1is an interactive schematic diagram of a policy-based information processing method according to an embodiment of the present application;
[0060] Figure 2 is a flowchart of the steps of an embodiment of a policy-based information processing method of the present application;
[0061] Figure 3 is a flowchart of another embodiment of a policy-based information processing method of the present application;
[0062] Figure 4 is a schematic diagram of a synchronization example of a terminal rule in an embodiment of the present application;
[0063] Figure 5 It is a schematic diagram of an example of triggering and policy delivery based on cloud rules in an embodiment of the present application;
[0064] Figure 6 It is a schematic diagram of an example of triggering and policy delivery based on terminal rules in an embodiment of the present application;
[0065] Figure 7 is a schematic diagram of a strategy display example based on a cache strategy in an embodiment of the present application;
[0066] Figure 8 It is a schematic diagram of the structure of an exemplary device provided by an embodiment of the present application. DETAILED DESCRIPTION
[0067] In order to make the above-mentioned objects, features and advantages of the present application more obvious and easy to understand, the present application is further described in detail below in conjunction with the accompanying drawings and specific implementation methods.
[0068] The embodiments of the present application can be applied to information publishing scenarios, such as sending information on websites and client pages. The triggering and display of information can follow certain rules and strategies, so as to provide users with appropriate information in appropriate scenarios and provide better service and product experience.
[0069] Reference Figure 1 , showing an interactive schematic diagram of a policy-based information processing method in an embodiment of the present application.
[0070] Step 102: When the synchronization condition is met, the client requests rule information corresponding to the synchronization end rule, and the rule information includes a rule script.
[0071] In the embodiment of the present application, the synchronization of rules can adopt a mechanism of active request and passive acquisition linkage. That is, the client can actively request the required rules, and the server can also send the rules to the client for synchronization under certain conditions. For example, in the case of page startup, switching, etc., the client can be triggered to actively pull the rules. For example, some behaviors of the user on the page, such as staying on the page for more than a threshold, can trigger the server to send the rules to the client.
[0072] When the synchronization conditions are met, the rule information corresponding to the synchronization end rule includes at least one of the following steps: when it is detected that the page status meets the acquisition conditions, a rule pull request is generated and sent to pull the rule information of the corresponding rule; the rule information of the end rule fed back by the server is received, and the end rule is converted from the hit cloud rule, and the hit cloud rule is determined based on the cloud event corresponding to the user behavior.
[0073] Among them, the page state can be detected to determine whether the page state meets the acquisition conditions. For example, if the page state is a startup state, a switching state, etc., it can be determined that the acquisition conditions are met, and a rule pull request is generated accordingly and sent to the server. Among them, page startup may include a cold start of the page, the start of the foreground and background switching, etc., and the page switching may be a switch between different aspects, or a switch between the login state, etc. The above-mentioned change in the page state can be used as a synchronization opportunity to trigger the active pull of the end rule. In an embodiment of the present application, the rule information of the end rule may include rule parameters, rule scripts, and configuration data, and the configuration data includes event configuration data and rendering configuration data, wherein the rule parameters may include parameters such as rule identifiers and rule names. Among them, the rule script is a script for executing rule judgment, and the event configuration data is the configuration data of the event corresponding to the rule, such as configuration data for the corresponding behavior of the event. Among them, the code logic level corresponding to the end rule is the script name + version number, and a unique Key value is calculated based on the script name + version number. The end rule pushed each time + the end rule set pulled on the end is a Key value array. The rule script is used to calculate the user's terminal behavior event sequence, such as determining whether the user enters the homepage and stays on the homepage for 30 seconds. The rendering configuration data is used to configure the rendering data corresponding to the rule, such as the configuration data of the POP pop-up layer style contact, such as the H5 address corresponding to the web page undertaken by the pop-up layer, and the associated properties of the component rendering, including the Z-axis order, whether it is modal, whether it supports clicking the mask to close, etc.
[0074] The client can directly pull the rule information of the rule from the server, or first pull the event configuration information, end rule information, and then pull the rule script and rendering configuration respectively. The server can also determine that the synchronization conditions are met based on the events of the page, and then actively send the rule information, which is described in the following embodiments. Among them, the end can first pull the end rules, and then the server can increment other end rules based on the detected events.
[0075] Step 104: the server downloads the rule information of the outgoing rule.
[0076] The server can synchronize the rule information of the terminal rules with the client when the synchronization conditions are met. The client can actively pull the terminal rules, and the corresponding server can receive the rule pull request, obtain the rule information of the terminal rules according to the rule pull request, and send the rule information.
[0077] In some other examples, the server can also actively send rules to the client when the cloud rules are hit. Among them, the rule information of the rules sent when the synchronization conditions are met includes: based on the cloud events corresponding to the user behavior, determine the hit cloud rules, and convert the cloud rules into terminal rules; obtain the rule information of the terminal rules and send the rule information. The user's operation behavior in the page can also be detected to determine the event corresponding to the user behavior. The hit rules can be determined based on time, such as the user's behavior of receiving red envelopes corresponds to the red envelope receiving event, and the user's behavior of staying on the page for more than 15 seconds corresponds to the user stay event, etc. The event and the hit rules can be a real-time computing task, so as to match the event based on the user behavior and determine the hit rules. Cloud rules can be understood as cloud event sequences, and whether the rule is hit can be detected after the cloud event occurs. For example, "users receive new red envelopes to guide users to use red envelope strategies", where the calculation of "users receive new red envelopes and do not use them" corresponds to a real-time calculation task on the Omega platform, which is performed by Blink. Cloud rules refer to cloud event sequences. The cloud event corresponds to the behavior event "users receive new red envelopes" in the cloud rule. The corresponding Blink calculation is a judgment logic instruction. When the calculation task returns true, it means that the cloud event is hit, and then the "whether the red envelope is used" is calculated synchronously. If it is also satisfied, it means that the cloud rule is successfully hit. The cloud rule can be converted into an end rule, and then the rule information of this section of the rule is sent to the client.
[0078] Among them, the end rule may correspond to a full amount of strategy hit population rules. The full amount of strategy hit population rules refers to the aggregation of end rules associated with the full platform strategy. For example, if there are strategies A, B, and C on the platform, and the associated rules are Ra, Rb, and Rc, then [Ra, Rb, Rc] is returned. The end rule may be the end rule converted from the hit cloud rule. For example, a cloud rule strategy is "private chat with 2 sellers and both are replied to, and the specified guidance strategy is put on the private chat page", and the cloud rule is "private chat with 2 sellers and no reply", the rule can be converted into the end rule "enter the private chat page" + cloud rule "private chat with 2 sellers and no reply", so that when the user enters the private chat page, the end rule can be triggered, and the corresponding cloud rule calculation is performed on the server at the same time. If the end rule + cloud rule are satisfied at the same time, it means that the rule is successfully triggered.
[0079] In the embodiment of the present application, after the first synchronization of the end rules, incremental synchronization can be performed again through the segment rules. Among them, the code logic level corresponding to the end rules is the script name + version number, and a unique Key value is calculated based on the script name + version number. The end rules pushed each time + the end rule set pulled on the end is a Key value array, so that each time an end rule push request is made, an incremental addition operation is performed based on the Key value array.
[0080] Step 106: The client locally stores the rule information of the terminal rule.
[0081] The client can store the received end rules. When the end rules are synchronized to the client locally, it can also test whether the end rules are timely rules. Timely rules are set rules. When configuring the rules, a flag will be written to identify the timely rules. Whether the rules contain the flag can be determined to determine whether they are timely rules. Timely rules mean that the end rules can be calculated regardless of any page. The corresponding non-timely rules mean that this end rule can only take effect on a specific page.
[0082] Step 108: During the page execution process, the client determines the hit policy based on the rule script and generates a policy acquisition request.
[0083] When the page is running, the client can detect the behavior information through the rule script, determine the hit rule event based on the behavior information, and then detect the hit corresponding target rule, and then obtain the policy corresponding to the target rule, and generate a policy acquisition request.
[0084] Wherein, during the page running process, the hit strategy is determined based on the rule script, and a strategy acquisition request is generated, including: during the page running process, detection is performed based on the rule script; when a rule hit is detected, the corresponding rule identifier, page identifier and page associated parameters are determined; based on the rule identifier, page identifier and page associated parameters, a strategy acquisition request is generated. The hit rule event is determined based on the behavior information, and then the corresponding target rule is detected to obtain the rule identifier, page identifier and page associated parameters, such as the touch point or event corresponding to the user behavior. Then, the strategy acquisition request can be generated based on the rule identifier, page identifier and page associated parameters as parameters.
[0085] Step 110: The client sends the policy acquisition request.
[0086] Step 112: The server determines the policy data corresponding to the policy according to the policy acquisition request.
[0087] After receiving the policy acquisition request, the server can determine the policy data of the corresponding policy based on the policy acquisition request. Wherein, the policy data of the corresponding policy determined according to the policy acquisition request includes: determining the rule identifier, page identifier and page-related parameters according to the policy acquisition request; determining the delivery data according to the rule identifier and page-related parameters, and the delivery data includes static data and dynamic data; determining the rendering configuration data and the buried point data according to the rule identifier, page identifier and page-related parameters; and using the delivery data, rendering configuration data and buried point data to constitute the policy data. The rule identifier, page identifier and page-related parameters can be obtained from the policy acquisition request, and the delivery data can be determined based on the rule identifier and page-related parameters. Wherein, the policy includes policy data such as users, rules, contacts, static data and dynamic data, where the static data and dynamic data can be delivery data, that is, the data delivered by the page rendering display, static data such as the style of the red envelope, the text display style, etc., and dynamic data is changeable data, such as numbers, names, titles, etc. The rendering configuration data and the embedding data can also be determined based on the rule identifier, the page identifier and the page associated parameters, wherein the rendering configuration data is the rendering configuration data of the component corresponding to the strategy, such as the touch point rendering type, coordinates, whether to refresh the data each time, the terminal cache time, whether to display modally, etc. The embedding data is the data corresponding to the touch points in the page. The delivery data, rendering configuration data and embedding data are used to form the strategy data.
[0088] In some optional embodiments, the determining of the policy data of the corresponding policy according to the policy acquisition request includes: judging whether there is a cloud rule for the policy acquisition request triggered by the terminal event; if there is no cloud rule, determining the policy data of the corresponding policy; if there is a cloud rule, matching the policy data of the policy according to the cloud rule. After receiving the policy acquisition request, it can also be determined whether the event or rule corresponds to a cloud rule. If the corresponding cloud rule is detected, the cloud rule can be calculated, and the policy is determined according to the hit cloud rule and the policy data is returned. If there is no cloud rule, the policy data of the policy corresponding to the terminal rule is obtained.
[0089] Step 114: The server sends the policy data of the policy.
[0090] Step 116: The client renders according to the policy data and displays corresponding presentation information.
[0091] The client can render based on the policy data to display the corresponding display information. The information of the policy can be displayed, such as displaying red envelopes and amounts, and displaying information such as gifts pushed to users. The policy data includes delivery data, rendering configuration data and embedding data; the rendering according to the policy data includes: rendering the delivery data according to the rendering configuration data, and adding embedding data to the rendered display information. The delivery data can be rendered based on the rendering configuration data to obtain display information, and embedding points can be added to the display information based on the rendering configuration data and the embedding data.
[0092] The client can also generate a display result according to the display information and feed back the display result. The server analyzes the display result and determines the policy processing result.
[0093] Generating the display result according to the display information includes: determining the rendering result according to the display information, and generating the display result using the rendering result and the strategy identifier. During the display process, display results can also be obtained, including display results such as strategy exposure (successful rendering), strategy click events, and strategy close events, which are reported through a designated reporting interface. The reported data includes a strategy ID, a reporting type, and a buried point data. The reporting type can be a processing type of the data corresponding to the display information, such as exposure type, click type, active click close type, passive close type, etc.
[0094] After receiving the display result, the server can analyze the display result. In an optional embodiment, the analysis of the display result to determine the strategy processing result includes: analyzing the strategy data to determine the corresponding operation result; analyzing the strategy data to determine the user's fatigue information. For example, the result of whether the strategy corresponds to the display information successfully or not can analyze the strategy's reach rate. Among them, reach rate = strategy exposure / strategy hit delivery. Another example is that fatigue detection can be performed based on the display result to analyze fatigue information, including strategy fatigue detection, strategy group fatigue detection, resource position fatigue detection, industry fatigue detection, etc. The corresponding strategy processing result is obtained. Among them, strategy fatigue detection and strategy group fatigue detection can be determined based on the number of strategy delivery times, reach rate, user feedback results, etc. Resource position fatigue detection is fatigue information displayed in the resource position on the page, wherein the resource position is the location where the resource information is displayed on the page. In this example, the display information can be displayed, and the fatigue of the display information displayed on the resource position can be determined. Industry fatigue detection can detect the fatigue of the corresponding display information in the industry's strategy.
[0095] In summary, when the synchronization conditions are met, the rule information corresponding to the synchronization end rules can be stored, and the rule information includes the rule script. Therefore, during the page running process, the hit strategy is determined based on the rule script, and a policy acquisition request is generated. According to the policy acquisition request, the policy data is pulled, and a mechanism combining server-side push and end-side pull is implemented to effectively ensure the reach of the strategy, and rendering is performed according to the policy data, and the corresponding display information is displayed.
[0096] It is also possible to generate a display result based on the display information and feed back the display result to analyze the strategy processing result, so that the strategy's reach can be detected and analyzed for subsequent adjustments.
[0097] The embodiments of the present application can be applied in a variety of fields, such as in the operation field, to issue policies, which can improve the efficiency and reach rate of operation policies to users, ensure that policies are delivered to users in a timely and reliable manner, and improve the impact on user operations.
[0098] Based on the above embodiments, the present application also provides a policy-based information processing method, which is applied to the client side to ensure the implementation of the policy. Figure 2 As shown:
[0099] Step 202: When the synchronization condition is met, the rule information corresponding to the synchronization end rule is stored, and the rule information includes a rule script.
[0100] When the synchronization conditions are met, the rule information corresponding to the synchronization end rule includes at least one of the following steps: when it is detected that the page status meets the acquisition conditions, a rule pull request is generated and sent to pull the rule information of the corresponding rule; the rule information of the end rule fed back by the server is received, and the end rule is converted from the hit cloud rule, and the hit cloud rule is determined based on the cloud event corresponding to the user behavior.
[0101] Step 204: during the page running process, determine the hit policy based on the rule script, generate a policy acquisition request, and send the policy acquisition request.
[0102] The method of generating a policy acquisition request by determining a hit policy based on the rule script during the page running process includes: performing detection based on the rule script during the page running process; determining the corresponding rule identifier, page identifier and page associated parameters when a rule hit is detected; and generating a policy acquisition request based on the rule identifier, page identifier and page associated parameters.
[0103] After the embedded data triggers the end event on the page, an end event request is generated and sent. Then the strategy acquisition request is triggered.
[0104] Step 206: Receive policy data corresponding to the policy.
[0105] Step 208: Rendering is performed according to the policy data, and corresponding display information is displayed.
[0106] The strategy data includes delivery data, rendering configuration data and tracking data; the rendering according to the strategy data includes: rendering the delivery data according to the rendering configuration data, and adding tracking data to the display information obtained by rendering.
[0107] Generating a display result according to the display information includes:
[0108] A rendering result is determined according to the display information, and the display result is generated using the rendering result and the strategy identifier.
[0109] Step 210: Generate a display result according to the display information, and feed back the display result to analyze the policy processing result.
[0110] On the basis of the above embodiments, the embodiments of the present application also provide a policy-based information processing method, which is applied to the server side to ensure the implementation of the policy. Figure 3 As shown:
[0111] Step 302: When the synchronization condition is met, the rule information of the originating rule is sent to synchronize the rule to the client, wherein the rule information includes a rule script.
[0112] In which, a rule pull request is received, rule information of the terminal rule is obtained according to the rule pull request, and the rule information is sent. In another example, based on the cloud event corresponding to the user behavior, the hit cloud rule is determined, and the cloud rule is converted into the terminal rule; the rule information of the terminal rule is obtained, and the rule information is sent.
[0113] Step 304: receiving a policy acquisition request, wherein the policy acquisition request is generated based on the policy hit by the rule script.
[0114] Step 306: Determine policy data corresponding to the policy according to the policy acquisition request.
[0115] The policy data of the corresponding policy is determined according to the policy acquisition request, including: determining the rule identifier, page identifier and page associated parameters according to the policy acquisition request; determining the delivery data according to the rule identifier and page associated parameters, and the delivery data includes static data and dynamic data; determining the rendering configuration data and the embedding data according to the rule identifier, page identifier and page associated parameters; and using the delivery data, rendering configuration data and embedding data to form the policy data.
[0116] The method of determining the policy data of the corresponding policy based on the policy acquisition request includes: judging whether there is a cloud rule for the policy acquisition request triggered by the terminal event; if there is no cloud rule, determining the policy data of the corresponding policy; if there is a cloud rule, matching the policy data of the policy according to the cloud rule.
[0117] The server can query strategies based on page identification, user, rule, delivery time, etc. In the process of traversing strategies, it can also filter based on blacklists and whitelists and perform fatigue detection. For example, if a strategy can only be delivered once a day, it will not be delivered again after it has been delivered once. Then it can also detect the client version and other information to determine the required strategy. Among them, strategies can also correspond to arrangement rules, such as blacklists, whitelists, top tags, setting strategy priorities according to resource positions, strategy algorithm selection, and strategy evaluation, so as to assist in the selection of strategies based on arrangement rules.
[0118] Step 308: Send policy data of the policy so that the client can render and display corresponding display information according to the policy.
[0119] The display result may also be received, analyzed, and the policy processing result may be determined.
[0120] The analyzing the display result to determine the policy processing result includes: analyzing the policy data to determine the corresponding operation result; analyzing the policy data to determine the user's fatigue information.
[0121] In the embodiment of the present application, since the backend cannot perceive the user's page information in real time, the synchronization model is designed using a push-pull + cache approach, wherein the triggering of end rules uses a synchronous model, and the triggering of cloud rules and third-party rules uses an asynchronous model.
[0122] In an embodiment of the present application, the server may provide multiple service components to provide different services. For example, the strategy delivery component (Luxury) is used to execute the configuration, delivery and data evaluation of the strategy. The rule calculation engine (Walle) is used to determine the sequence of user behavior events, which can be configured with corresponding rule scripts. The contact configuration platform (Poplayer) is used to configure the contacts within the page, such as the contact configuration of the pop-up layer component style on the App side, that is, to configure the framework of the rich and diverse pop-up layers deployed in any page in the App. The real-time traffic regulation component (Omega) is used to perform real-time traffic regulation based on the user's real-time behavior after satisfying certain rule calculations. The dynamic material library (TPP) is used to provide dynamic data for the strategy. The data analysis component (OTS) is used to analyze data, such as fatigue data, display results, reach rate, etc.
[0123] The process of the synchronization model of the end rule is as follows: Figure 4 As shown:
[0124] Step 402: When the client detects that the page status meets the acquisition conditions, it generates and sends a rule pull request.
[0125] Among them, the timing for the client side to pull the end rules can be page (APP) cold start, page (APP) front and back switching, APP login status switching, etc. Based on the rule pull request, the end rules can be pulled in full.
[0126] Step 404: The policy delivery component on the server side obtains rule information and provides feedback.
[0127] Among them, the end rules can be fully pulled, that is, the end rules stored in the server are fully synchronized to the client. Among them. The feedback data can include the full amount of policy hit crowd rules, the end rules converted by the hit cloud rules, and event configuration data, etc. The policy hit crowd rules refer to the aggregation of end rules associated with the full platform policy. For example, if there are policies A, B, and C on the platform, and the associated rules are Ra, Rb, and Rc, then [Ra, Rb, Rc] are returned. The end rules converted by the hit cloud rules, for example, a cloud rule strategy is "private chat with 2 sellers and both are replied to, and the specified guidance strategy is put on the private chat page", where the cloud rule is "private chat with 2 sellers and no reply", the rule can be converted into the end rule "enter the private chat page" + cloud rule "private chat with 2 sellers and no reply", so that when the user enters the private chat page, the end rule can be triggered, and the corresponding cloud rule calculation is synchronously performed in Omega. If the end rule + cloud rule are satisfied at the same time, it means that the rule is successfully triggered.
[0128] Step 406: The client sends a script pull request.
[0129] Step 408: The rule calculation engine at the server side obtains the script data and provides feedback.
[0130] After obtaining the rules, the client can pull the script data from the server. The rule calculation engine on the server can obtain the rule script and then send it to the client.
[0131] Step 410: The client sends a configuration pull request.
[0132] Step 412: The contact configuration platform on the server side obtains rendering configuration data and returns it.
[0133] Rendering configuration data, such as the configuration data of the POP pop-up layer style contacts, such as the H5 address corresponding to the web page undertaken by the pop-up layer, and the associated properties when the component is rendered, including the Z-axis order, whether it is modal, whether it supports clicking on the mask to close, etc.
[0134] This enables the synchronization process of end-side pulling.
[0135] The triggering and policy delivery process based on cloud rules is as follows: Figure 5 As shown:
[0136] Step 502: The policy delivery component of the server detects a hit cloud event.
[0137] Step 504: the policy delivery component sends a cloud rule calculation request to the real-time traffic control component.
[0138] Step 506: The real-time traffic control component feeds back the cloud rule calculation result.
[0139] Step 508: The policy delivery component converts the cloud rules into terminal rules.
[0140] Among them, there are corresponding real-time computing tasks running in the real-time traffic regulation component, such as "users receive new red envelopes to guide users to use red envelope strategies", where the calculation of "users receive new red envelopes and do not use them" corresponds to a real-time computing task on the Omega platform, and Blink is responsible for real-time computing. Cloud rules refer to cloud event sequences. The cloud event corresponds to the behavior event "users receive new red envelopes" in the cloud rule. The corresponding Blink calculation is a judgment logic instruction. When the calculation task returns true, it means that the cloud event is hit, and then the "whether the red envelope is used" is calculated synchronously. If it is also satisfied, it means that the cloud rule is successfully hit. Feedback the calculation result of the cloud rule hit, which can be 0 or 1, or true / false, etc. As the calculation result. After the cloud rule hits, it can be converted into an end rule and added to the end rule database.
[0141] Step 510: The policy delivery component incrementally synchronizes terminal rules to the client.
[0142] The code logic level corresponding to the end rule is the rule script name + version number. A unique Key value is calculated based on the script hit + version number. The end rule pushed each time + the end rule set pulled on the end is a Key value array. In this way, whenever an end rule push request is made, an incremental operation can be performed based on the Key value array.
[0143] Step 512: The client determines that the terminal rule is a timely rule.
[0144] Timely rules are set rules. When configuring rules, a flag is written to identify the timely rules. Whether the rule contains the flag can determine whether it is a timely rule. Timely rules refer to end rules that can be calculated regardless of any page. The corresponding non-timely rules refer to end rules that can only take effect on a specific page.
[0145] Step 514: The client sends a policy acquisition request to the policy delivery component.
[0146] After the cloud rule is converted into the terminal rule and issued, it can be determined that the user currently hits the terminal rule, so a policy acquisition request can be generated to request policy data from the server. The requested policy data includes a rule identifier, a page identifier, and page associated parameters.
[0147] Step 516: The strategy delivery component requests dynamic data from the dynamic material library.
[0148] Step 518: The dynamic material library feeds back dynamic data.
[0149] Step 520: The strategy delivery component generates strategy data and provides feedback.
[0150] Step 522: The client performs rendering based on the policy data.
[0151] For example, in the POP pop-up contact style strategy, the first rendering step is for the client to pull up the View layer of the Poplayer component container, and the second rendering step is to render the actual strategy delivery data in the View layer, such as rendering the Webview H5 page.
[0152] Step 524: The client determines the contact type.
[0153] If the display information is triggered, such as when a user clicks or browses, the contact point is triggered, and the contact point type can be determined first.
[0154] Step 526: The client sends a policy acquisition request to the policy delivery component.
[0155] Among them, the first type is the client dynamic component rendering type, which can send a policy acquisition request to the policy delivery component after being triggered. The second type is the client's Webview component, which can send a policy acquisition request after being triggered.
[0156] Step 528: The strategy delivery component requests dynamic data from the dynamic material library.
[0157] Step 530: The dynamic material library feeds back dynamic data.
[0158] Step 532: The strategy delivery component generates strategy data and provides feedback.
[0159] Step 534: The client performs rendering based on the policy data.
[0160] Step 536: The client generates a display result according to the display information and feeds back the display result.
[0161] During the display process, you can also obtain display results, including strategy exposure (successful rendering), strategy click events, strategy close events, and other display results, which are reported through the specified reporting interface. The reported data includes strategy ID, reporting type, and tracking data. The reporting type can be the processing type of the data corresponding to the display information, such as exposure type, click type, active click close type, passive close type, etc. After receiving the display results, the strategy delivery component can report the display results to the data analysis component.
[0162] The data analysis component can analyze the policy data to determine the corresponding operation results, such as analyzing the reach rate of the policy, and tracking and analyzing subsequent operations, such as whether the policy is triggered, etc. It can also analyze the effectiveness of the policy, such as analyzing the effectiveness based on the reach rate, tracking results, etc. The policy data can also be analyzed to determine the user's fatigue information.
[0163] This realizes a mechanism that combines cloud-side push with terminal-side pull to effectively ensure the reach of the strategy.
[0164] The triggering and policy delivery process based on terminal rules is as follows: Figure 6 As shown:
[0165] Step 602, the client detects tracking points based on user behavior and determines the hit-end events.
[0166] Among them, most user behavior events will have tracking points on the end, such as exposure, click, close, etc. Based on tracking points, user behavior can be detected to determine the hit end events, such as entering a certain page event, stay time trigger event, click event, IPV trigger event, etc.
[0167] Step 604: The client reports the terminal event to the real-time traffic regulation component.
[0168] After an end event is detected, the log corresponding to the end event can be determined and reported. The log generally includes various data corresponding to the behavior, such as the exposed object, the clicked / closed object, the time point, link tracking data, etc. This data can be dynamically expanded based on demand.
[0169] Step 606: The real-time traffic regulation component performs log normalization processing.
[0170] Step 608: The client determines the hit strategy based on the rule script.
[0171] The client can run the rule script to determine the end rule corresponding to the end event, and thus determine the strategy corresponding to the end rule as the hit strategy. The rule script can determine the rule corresponding to the behavior, such as whether a certain page is entered and stayed for a period of time, or whether a certain button is clicked, etc., corresponding to a certain rule.
[0172] Step 610: The client sends a policy acquisition request to the policy delivery component.
[0173] Step 612: The policy delivery component determines whether there is a cloud rule.
[0174] Step 614: the policy delivery component sends a cloud rule calculation request to the real-time traffic control component.
[0175] Step 616, the real-time traffic control component feeds back the cloud rule calculation results.
[0176] Step 618: The strategy delivery component requests fatigue information from the data analysis component.
[0177] Step 620: The data analysis component returns fatigue information to the strategy delivery component.
[0178] Step 622: The strategy delivery component generates strategy data and provides feedback.
[0179] Among them, if there is no cloud rule, the strategy delivery component can determine the strategy data and feedback. If there is a cloud rule and the cloud rule is hit, it can request fatigue information from the data analysis component, such as strategy fatigue, strategy group fatigue, resource position fatigue, industry fatigue, etc., and then determine the corresponding strategy and strategy data.
[0180] The data analysis component generally determines the fatigue level of the three dimensions of exposure, click, and close. It will make fatigue judgments based on the strategy data reported by the above data collection. For example, if a user specifies that strategy A can only be launched once a day, then each time the strategy is launched, it will be determined whether there is an exposure data record for the user with the strategy on that day.
[0181] Step 624: The client caches the policy data and renders it for display.
[0182] Step 626: The client reports the display result.
[0183] The client can detect whether the display time of the display data exceeds the time threshold. If it does not exceed the time threshold, the display result can be obtained and reported. If it exceeds the time threshold, the display can continue or determine whether it needs to be refreshed or closed.
[0184] Step 628: The client determines the contact type.
[0185] If the display information is triggered, such as when a user clicks or browses, the contact point is triggered, and the contact point type can be determined first.
[0186] Step 630: The client sends a policy acquisition request to the policy delivery component.
[0187] The first type is the client-side dynamic componentized rendering type, which can send a policy acquisition request to the policy delivery component after being triggered. Among them, the second type is the client's Webview component, which can send a policy acquisition request after being triggered.
[0188] Step 632: The strategy delivery component requests dynamic data from the dynamic material library.
[0189] Step 634: the dynamic material library feeds back dynamic data.
[0190] Step 636: The strategy delivery component generates strategy data and provides feedback.
[0191] Step 638: The client performs rendering based on the policy data.
[0192] Step 640: The client generates a display result according to the display information and feeds back the display result.
[0193] Step 642: The strategy delivery component reports and displays the results to the data analysis component.
[0194] The data analysis component can analyze the policy data to determine the corresponding operation results, such as analyzing the reach rate of the policy, and tracking and analyzing subsequent operations, such as whether the policy is triggered, etc. It can also analyze the effectiveness of the policy, such as analyzing the effectiveness based on the reach rate, tracking results, etc. The policy data can also be analyzed to determine the user's fatigue information.
[0195] Based on the above embodiment, the strategy can also be displayed based on the strategy cache, such as Figure 7 As shown:
[0196] Step 702: The client detects whether there is a cache policy.
[0197] When the APP starts displaying pages, the user's operation of starting the page can hit the corresponding end event and comply with the end rule. If the hit end rule has a strategy in the local cache, it can be rendered and displayed based on the strategy.
[0198] Step 704: The client renders and displays based on the policy data.
[0199] Step 706: The client determines whether the display duration exceeds a time threshold.
[0200] Step 708: The client reports the display result to the strategy delivery component.
[0201] Step 710: The strategy delivery component reports and displays the results to the data analysis component.
[0202] Step 712: The client determines whether the policy data needs to be refreshed.
[0203] Step 714: The client sends a policy acquisition request to the policy delivery component.
[0204] Step 716: The strategy delivery component generates strategy data and provides feedback.
[0205] Step 718: The client performs rendering based on the policy data.
[0206] Step 720: The client generates a display result according to the display information and feeds back the display result.
[0207] Step 722: The strategy delivery component reports and displays the results to the data analysis component.
[0208] The embodiment of the present application can integrate synchronization rules and policies to solve the problem of policy access efficiency. Through the combination of push-pull + response + cache, the problem of loss caused by various anomalies in the policy delivery process can be solved, and the policy access rate can be improved. In addition, a synchronization solution can be provided for cloud rules and third-party access to ensure the access rate.
[0209] It should be noted that, for the method embodiments, for the sake of simplicity, they are all expressed as a series of action combinations, but those skilled in the art should be aware that the embodiments of the present application are not limited by the described order of actions, because according to the embodiments of the present application, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all preferred embodiments, and the actions involved are not necessarily required by the embodiments of the present application.
[0210] On the basis of the above-mentioned embodiment, this embodiment further provides a local operation device of a web page, which is applied in a terminal device.
[0211] A storage module is used to locally store the presentation dependency data corresponding to the web page;
[0212] a processing and analysis module, configured to intercept a request of the web page and read the first page data in the demonstration dependency data when the web page is started; and, in response to an operation of the web page, obtain corresponding interface data from the demonstration dependency data, and determine corresponding second page data according to the interface data;
[0213] The display module is used for displaying a first page of the webpage according to the first page data; and displaying a second page according to the second page data.
[0214] In summary, the demonstration dependency data corresponding to the web page can be saved locally. When the web page is started, the request of the web page is intercepted, and the first page data in the local demonstration dependency data is read. The first page of the web page is displayed according to the first page data, so that the web page can be started based on the local data, and in response to the operation of the web page, the corresponding interface data is obtained from the demonstration dependency data, the corresponding second page data is determined according to the interface data, the second page is displayed according to the second page data, and the demonstration operation is implemented based on the corresponding page operation of the local data, so as to realize the operation of the web page without the server.
[0215] The processing and analysis module is used to intercept the request corresponding to the web page through a web proxy; read the demonstration dependency data according to the request to determine the corresponding interface data; and determine the bound page data according to the interface data as the first page data.
[0216] The processing and analysis module is also used to intercept login requests through a web proxy; determine login data based on the demonstration dependency data, and complete login processing according to the login data.
[0217] The processing and analysis module is used to query the interface data corresponding to the login request in the demonstration dependency data; determine the login logic information based on the interface data; if the login logic information is the first type of information, obtain the login state flag, and return the login state flag to complete the login processing; if the login logic information is the second type of information, obtain the page data with the login state, return the page data and render and display it to complete the login processing.
[0218] The processing and analysis module is used to determine the operation logic information according to the interface data, and obtain the corresponding second page data according to the operation logic information; the display module is used to render the second page data and display the second page.
[0219] The processing and analysis module is used to query the demonstration dependency data according to the request in response to the operation of the web page; determine the interface usage identifier in the demonstration dependency data, and determine the corresponding interface data according to the interface usage identifier.
[0220] The processing and analysis module is also used to provide a scene list window; in response to the selection of scene information in the scene list window, start the scene operation window corresponding to the scene information; and start the web page agent in the scene operation window to perform agent processing of the web page operation.
[0221] On the basis of the above embodiments, this embodiment further provides a policy-based information processing device, which is applied in a terminal device.
[0222] A rule synchronization module, used to synchronize and store rule information corresponding to the end rule when the synchronization condition is met, wherein the rule information includes a rule script;
[0223] A policy request module is used to determine the hit policy based on the rule script during the page running process, generate a policy acquisition request, and send the policy acquisition request; receive policy data corresponding to the policy;
[0224] A display module, used to render according to the policy data and display corresponding display information;
[0225] The result feedback module is used to generate a display result according to the display information, and feed back the display result to analyze the strategy processing result.
[0226] When the synchronization conditions are met, the rule information corresponding to the synchronization end rule is stored, and the rule information includes the rule script. Therefore, during the page running process, the hit strategy is determined based on the rule script, and a strategy acquisition request is generated. The strategy data is pulled according to the strategy acquisition request, and a mechanism combining server-side push and end-side pull is implemented to effectively ensure the policy is reached. The policy data is rendered and the corresponding display information is displayed to ensure the display of information. The display result can also be generated based on the display information, and the display result is fed back to analyze the strategy processing result, so that the policy reach can be detected and analyzed to facilitate subsequent adjustments.
[0227] Optionally, a rule synchronization module is used to generate and send a rule pull request when it detects that the page status meets the acquisition conditions, so as to pull the rule information of the corresponding rule; receive the rule information of the end rule fed back by the server, wherein the end rule is converted from the hit cloud rule, and the hit cloud rule is determined based on the cloud event corresponding to the user behavior.
[0228] The policy request module is used to perform detection based on the rule script during page operation; when a rule hit is detected, determine the corresponding rule identifier, page identifier and page associated parameters; and generate a policy acquisition request based on the rule identifier, page identifier and page associated parameters.
[0229] The policy request module is also used to generate and send an end event request after detecting an end event triggered by embedded data in the page.
[0230] The strategy data includes delivery data, rendering configuration data and tracking data; the display module is used to render the delivery data according to the rendering configuration data and add tracking data to the display information obtained by rendering.
[0231] The result feedback module is used to determine the rendering result according to the display information, and generate the display result using the rendering result and the strategy identifier.
[0232] On the basis of the above-mentioned embodiment, this embodiment further provides a policy-based information processing device, which is applied to an electronic device at a server end.
[0233] A rule sending module, used for sending rule information of terminal rules when synchronization conditions are met, so as to synchronize the rules to the client, wherein the rule information includes rule scripts;
[0234] A policy delivery module is used to receive a policy acquisition request, the policy acquisition request is generated according to the policy hit by the rule script; determine the policy data of the corresponding policy according to the policy acquisition request; and deliver the policy data of the policy so that the client renders and displays the corresponding display information according to the policy;
[0235] The analysis module is used to receive the display results; analyze the display results and determine the policy processing results.
[0236] The rule issuing module is used to receive a rule pulling request, obtain the rule information of the terminal rule according to the rule pulling request, and send the rule information.
[0237] The rule sending module is used to determine the hit cloud rule based on the cloud event corresponding to the user behavior, and convert the cloud rule into the terminal rule; obtain the rule information of the terminal rule, and send the rule information.
[0238] The policy issuing module is used to determine the rule identifier, page identifier and page-related parameters based on the policy acquisition request; determine the delivery data based on the rule identifier and page-related parameters, and the delivery data includes static data and dynamic data; determine the rendering configuration data and the embedding data based on the rule identifier, page identifier and page-related parameters; and use the delivery data, rendering configuration data and embedding data to form the policy data.
[0239] The policy issuing module is used to determine whether there is a cloud rule for the policy acquisition request triggered by the terminal event; if there is no cloud rule, determine the policy data of the corresponding policy; if there is a cloud rule, match the policy data of the policy according to the cloud rule.
[0240] The analysis module is used to analyze the policy data to determine the corresponding operation results; and to analyze the policy data to determine the user's fatigue information.
[0241] The embodiment of the present application can integrate synchronization rules and policies to solve the problem of policy access efficiency. Through the combination of push-pull + response + cache, the problem of loss caused by various anomalies in the policy delivery process can be solved, and the policy access rate can be improved. In addition, a synchronization solution can be provided for cloud rules and third-party access to ensure the access rate.
[0242] The embodiment of the present application also provides a non-volatile readable storage medium, which stores one or more modules (programs). When the one or more modules are applied to a device, the device can execute instructions (instructions) of each method step in the embodiment of the present application.
[0243] The present application embodiment provides one or more machine-readable media, on which instructions are stored, and when executed by one or more processors, an electronic device executes one or more methods as described in the above embodiments. In the present application embodiment, the electronic device includes a server, a terminal device, and the like.
[0244] The embodiments of the present disclosure may be implemented as a device configured as desired using any appropriate hardware, firmware, software, or any combination thereof, and the device may include electronic devices such as a server (cluster), a terminal, etc. Figure 8 An exemplary apparatus 800 that can be used to implement various embodiments described in this application is schematically illustrated.
[0245] For one embodiment, Figure 8 An exemplary apparatus 800 is shown having one or more processors 802, a control module (chip set) 804 coupled to at least one of the processor(s) 802, a memory 806 coupled to the control module 804, a non-volatile memory (NVM) / storage device 808 coupled to the control module 804, one or more input / output devices 810 coupled to the control module 804, and a network interface 812 coupled to the control module 804.
[0246] The processor 802 may include one or more single-core or multi-core processors, and the processor 802 may include any combination of general-purpose processors or special-purpose processors (such as graphics processors, application processors, baseband processors, etc.). In some embodiments, the device 800 can be used as a server, terminal, or other device described in the embodiments of the present application.
[0247] In some embodiments, the apparatus 800 may include one or more computer-readable media (e.g., memory 806 or NVM / storage device 808) having instructions 814 and one or more processors 802 combined with the one or more computer-readable media and configured to execute the instructions 814 to implement a module to perform the actions described in the present disclosure.
[0248] For one embodiment, the control module 804 may include any suitable interface controller to provide any suitable interface to at least one of the processor(s) 802 and / or any suitable device or component in communication with the control module 804 .
[0249] The control module 804 may include a memory controller module to provide an interface to the memory 806. The memory controller module may be a hardware module, a software module, and / or a firmware module.
[0250] The memory 806 may be used, for example, to load and store data and / or instructions 814 for the device 800. For one embodiment, the memory 806 may include any suitable volatile memory, such as a suitable DRAM. In some embodiments, the memory 806 may include double data rate type four synchronous dynamic random access memory (DDR4 SDRAM).
[0251] For one embodiment, control module 804 may include one or more input / output controllers to provide an interface to NVM / storage device 808 and input / output device(s) 810 .
[0252] For example, NVM / storage 808 may be used to store data and / or instructions 814. NVM / storage 808 may include any suitable non-volatile memory (e.g., flash memory) and / or may include any suitable non-volatile storage device(s) (e.g., one or more hard disk drives (HDDs), one or more compact disk (CD) drives, and / or one or more digital versatile disk (DVD) drives).
[0253] NVM / storage device 808 may include storage resources that are part of the device on which apparatus 800 is installed, or it may be accessible to the device without being part of the device. For example, NVM / storage device 808 may be accessed via (one or more) input / output devices 810 over a network.
[0254] (One or more) input / output devices 810 may provide an interface for the apparatus 800 to communicate with any other appropriate device, and the input / output device 810 may include a communication component, an audio component, a sensor component, etc. The network interface 812 may provide an interface for the apparatus 800 to communicate through one or more networks, and the apparatus 800 may wirelessly communicate with one or more components of a wireless network according to any of one or more wireless network standards and / or protocols, for example, accessing a wireless network based on a communication standard, such as WiFi, 2G, 3G, 4G, 5G, etc., or a combination thereof for wireless communication.
[0255] For one embodiment, at least one of the processor(s) 802 may be packaged together with the logic of one or more controllers (e.g., a memory controller module) of the control module 804. For one embodiment, at least one of the processor(s) 802 may be packaged together with the logic of one or more controllers of the control module 804 to form a system-in-package (SiP). For one embodiment, at least one of the processor(s) 802 may be integrated on the same die with the logic of one or more controllers of the control module 804. For one embodiment, at least one of the processor(s) 802 may be integrated on the same die with the logic of one or more controllers of the control module 804 to form a system-on-chip (SoC).
[0256] In various embodiments, the device 800 may be, but is not limited to, a terminal device such as a server, a desktop computing device, or a mobile computing device (e.g., a laptop computing device, a handheld computing device, a tablet computer, a netbook, etc.). In various embodiments, the device 800 may have more or fewer components and / or different architectures. For example, in some embodiments, the device 800 includes one or more cameras, a keyboard, a liquid crystal display (LCD) screen (including a touch screen display), a non-volatile memory port, multiple antennas, a graphics chip, an application-specific integrated circuit (ASIC), and a speaker.
[0257] Among them, the main control chip can be used as a processor or control module in the detection device, sensor data, location information, etc. are stored in a memory or NVM / storage device, the sensor group can be used as an input / output device, and the communication interface may include a network interface.
[0258] The embodiment of the present application also provides an electronic device, including: a processor; and a memory, on which executable code is stored, and when the executable code is executed, the processor executes one or more methods as described in the embodiment of the present application. In the embodiment of the present application, the memory can store various data, such as target files, file and application association data, and user behavior data, so as to provide a data basis for various processing.
[0259] The embodiments of the present application also provide one or more machine-readable media on which executable codes are stored. When the executable codes are executed, the processor executes one or more methods described in the embodiments of the present application.
[0260] As for the device embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.
[0261] The various embodiments in this specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts between the various embodiments can be referenced to each other.
[0262] The embodiments of the present application are described with reference to the flowcharts and / or block diagrams of the methods, terminal devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing terminal device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing terminal device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.
[0263] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing terminal device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce a manufactured product including an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.
[0264] These computer program instructions can also be loaded onto a computer or other programmable data processing terminal device so that a series of operating steps are executed on the computer or other programmable terminal device to produce a computer-implemented process, thereby providing instructions for executing on the computer or other programmable terminal device to implement the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.
[0265] Although the preferred embodiments of the present application have been described, those skilled in the art may make additional changes and modifications to these embodiments once they have learned the basic creative concept. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and all changes and modifications that fall within the scope of the embodiments of the present application.
[0266] Finally, it should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or terminal device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or terminal device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or terminal device including the elements.
[0267] The above is a detailed introduction to a policy-based information processing method, an electronic device and a storage medium provided by the present application. Specific examples are used in this article to illustrate the principles and implementation methods of the present application. The description of the above embodiments is only used to help understand the method of the present application and its core idea. At the same time, for general technical personnel in this field, according to the idea of the present application, there will be changes in the specific implementation method and application scope. In summary, the content of this specification should not be understood as a limitation on the present application.
Claims
1. A policy-based information processing method, characterized in that: The method comprises: When the synchronization condition is met, the rule information corresponding to the synchronization end rule is stored, and the rule information includes a rule script; During the running of the page, detection is performed based on the rule script; When a rule hit is detected, the corresponding rule identifier, page identifier, and page associated parameters are determined; Generate a policy acquisition request based on the rule identifier, the page identifier and the page associated parameters; receiving policy data corresponding to the policy; Rendering is performed according to the policy data, and corresponding display information is displayed.
2. The method according to claim 1, characterized in that When the synchronization condition is met, the rule information corresponding to the synchronization end rule includes at least one of the following steps: When it is detected that the page status meets the acquisition conditions, a rule pull request is generated and sent to pull the rule information of the corresponding rule; Receive rule information of the end rule fed back by the server, where the end rule is converted from the hit cloud rule, and the hit cloud rule is determined according to the cloud event corresponding to the user behavior.
3. The method according to claim 1, characterized in that Also includes: After the embedded data triggers an end event on the page, an end event request is generated and sent.
4. The method according to claim 1, characterized in that: The strategy data includes delivery data, rendering configuration data and embedding data; the rendering according to the strategy data includes: The delivery data is rendered according to the rendering configuration data, and the embedding data is added to the display information obtained by rendering.
5. A policy-based information processing method, characterized in that: The method comprises: When the synchronization condition is met, the rule information of the originating end rule is sent to synchronize the rule to the client, wherein the rule information includes the rule script; Receive a policy acquisition request, where the policy acquisition request is generated based on the policy hit by the rule script; Determining policy data corresponding to the policy according to the policy acquisition request; Sending policy data of the policy so that corresponding display information is rendered and displayed on the client according to the policy; The determining of the policy data corresponding to the policy according to the policy acquisition request includes: Determine the rule identifier, page identifier and page associated parameters according to the policy acquisition request; Determine delivery data according to the rule identifier and the page associated parameters, wherein the delivery data includes static data and dynamic data; Determine rendering configuration data and embedding data according to the rule identifier, page identifier and page associated parameters; The delivery data, rendering configuration data and embedding point data are used to form strategy data.
6. The method according to claim 5, characterized in that The rule information of the rule issued when the synchronization condition is met includes: Receive a rule pull request, and obtain rule information of the terminal rule according to the rule pull request; The rule information is sent.
7. The method according to claim 5, characterized in that The rule information of the rule issued when the synchronization condition is met includes: Based on the cloud events corresponding to the user behaviors, determine the hit cloud rules, and convert the cloud rules into terminal rules; Obtain rule information of the terminal rule, and send the rule information.
8. The method according to claim 5, characterized in that The determining of the policy data corresponding to the policy according to the policy acquisition request includes: Get the policy request triggered by the end event to determine whether there is a cloud rule; If no cloud rule exists, determining policy data for the corresponding policy; If a cloud rule exists, the policy data of the policy is matched according to the cloud rule.
9. An electronic device, comprising: processor; and a memory having executable codes stored thereon, wherein when the executable codes are executed by a processor, the method according to any one of claims 1 to 8 is executed.
10. One or more machine-readable media having executable codes stored thereon, and when the executable codes are executed by a processor, the method according to any one of claims 1 to 8 is performed.
